1920S 24G Access the IP management through another VLAN

[ViniciusSilva]

Hello all.

I'm starting to work with 1920S switchs and want to remote management the Switch through a different VLAN. 

Example: I have configured 2 VLAN in the Switch. VLAN 103 its for my hosts and VLAN 254 its for management. I create a VLAN inferface with de IP 10.32.255.45 to VLAN 254 and connect this switch to my core through SFP. When I used a host in VLAN 254 (ex: 10.35.255.60) I was able to access the management interface correctly, but with a host in the VLAN 103 (103..100.0.1) I cannot ping or access the Switch. this not happend with my 1950 that are already configured.

Its possible to access de management IP in another VLAN than the management VLAN configured?

Thanks in advance.

[parnassus]

How the uplink to your core infrastructure is configured from transported VLAN standpoint?

If your Core Switch already routes VLAN 103 and VLAN 254 then it's a matter of understanding if your Core Switch can transport those VLANs over its downlink to the HPE 1920S Switch (considering IP Routing disabled on 1920S).

[ViniciusCouto]

Hello Parnassus.

My uplink is transporting both VLAN to 1920 correctly, and I can access the VLAN interfaces 103 (103.1.200.1) and 254 (10.32.255.254) configured in the core from a host conected to the 1920S.

From a host connected in the VLAN 103 on my core I can ping the management IP 10.32.255.45, but when i put the IP on the browser the management page dont appear. When I put the host on the 254 vlan on the core and make the same process then the configuration page load. I can only access the management web page when I'm connected to a port in the VLAN 254.

[ViniciusCouto]

By the way sorry by the change of user but I can access the older one anymore.

[parnassus]

I suspect that on your 1920S if a VLAN "n" is set as the "Management VLAN" then it is forced to not partecipate to IPv4 routing (if routing is enabled Globally and for every other VLAN you configured).

Can you share sanitized configuration? on a classic ProCurve/Aruba it should be a matter of seconds to fix that.

[ViniciusCouto]

Hello Paranassus.

Follows the current configuration of the Switch. When I changed the "Management Port" to "none" I was able to access the configuration page from another Switch (in this case from the core switch) but only in the same VLAN as the management VLAN (254). When I try to access from a different VLAN I still cannot access the switch.

Thank you for your support.

Current Configuration:

System Description "HPE OfficeConnect Switch 1920S 24G 2SFP JL381A
System Software Version "PD.02.10"
System Up Time "0 days 1 hrs 4 mins 35 secs"
Additional Packages HPE QOS,HPE IPv6 Management,HPE Routing
Current SNTP Synchronized Time: SNTP Client Mode Is Disabled

vlan database
vlan 103,123,150,224,228,254,4093
vlan name 103 "Rede Corporativa"
vlan name 123 "Rede Inews"
vlan name 150 "Rede Telefonia"
vlan name 224 "WiFi Convidados"
vlan name 228 "WiFi Corporativo"
vlan name 254 "Gerenciamento de Rede"
vlan name 4093 "Dummy 1920S"
vlan routing 254 1
exit
network mgmt_vlan 254
ip http secure-server
configure
time-range Schedule-1
exit
time-range Schedule-2
exit
ip routing
no username guest
line console
exit
line telnet
exit
line ssh
exit
interface 26
addport TRK 1
exit
snmp-server sysname "VG-SA505045"
snmp-server location "2 Piso ADM"
snmp-server contact "TI Ramal 447"

interface 1
bandwidth 100000
vlan pvid 123
vlan participation exclude 1,103
vlan participation include 123
ip mtu 1500
exit
interface 2
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 3
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 4
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 5
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 6
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 7
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 8
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 9
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 10
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 11
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 12
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 13
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 14
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 15
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 16
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 17
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 18
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 19
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 20
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 21
vlan pvid 103
vlan participation exclude 1,123
vlan participation include 103
exit
interface 22
vlan pvid 103
vlan participation exclude 1
vlan participation include 103
exit
interface 23
bandwidth 100000
vlan pvid 103
vlan participation exclude 1,254
vlan participation include 103,224
vlan tagging 224
ip mtu 1500
exit
interface 24
vlan pvid 254
vlan participation exclude 1
vlan participation include 254
exit
interface 25
vlan pvid 4093
vlan participation exclude 1,123
vlan participation include 4093
exit
interface TRK 1
vlan pvid 4093
vlan participation exclude 1
vlan participation include 103,123,150,224,228,254,4093
vlan tagging 103,123,150,224,228,254
exit
interface vlan 254
bandwidth 10000
routing
ip address 10.32.255.45 255.255.254.0
ip mtu 1500
no ip unreachables
no ip redirects
exit
ip route 10.32.254.0 255.255.254.0 10.32.255.254
exit

[parnassus]

Couldn't be that "network mgmt_vlan 254" is preventing the VLAN 254 to partecipate to IPv4 routing?

[ViniciusCouto]

I believe so but if I don't put the 254 VLAN as management VLAN I can't access the web interface. Looking into the manual I found that the access to the web interface is only achieve by the management VLAN configured on the "Get Connected" tab. If this is the case I don't believe that I will be able to access the switch through another VLAN. This is a major problem that I wasn't expected and a major flaw in the 1920S series.

[crubiolo]

Good morning, I have the same problem. Did you find the solution?