LAN Routing
cancel
Showing results for 
Search instead for 
Did you mean: 

New core switch VLANs not routing

 
BGW
Occasional Visitor

New core switch VLANs not routing

Hello all- I've inherited an HP Procurve infrastructure after years in a Cisco environment. I'm having some trouble getting newly created VLANs on the 5406zl core switch to route. It was my understanding that after creating the VLAN and assigning it an IP address (which would then be used as the default gateway for that VLAN) that the 5406 would automatically create the routing for the directly connected VLANs, but that doesn't seem to be the case. For example, these VLANs were created prior to my arrival, and you can see that they appear in the routing as they should.

 

vlan 64

   name “Bldg1_Wired_Users"

   untagged F17-F20

   ip helper-address 10.28.0.10

   ip helper-address 10.28.0.3

   ip address 172.17.64.1 255.255.252.0

   tagged A5,A13,A15,A19,B7

   exit

vlan 68

   name “Bldg1_Wired_Phones"

   ip helper-address 10.28.0.10

   ip helper-address 10.28.0.3

   ip address 172.17.68.1 255.255.252.0

   tagged A5,A13,A15,A19,B7

   exit

vlan 72

   name "Bldg1_Wireless_Users"

   ip helper-address 10.28.0.10

   ip helper-address 10.28.0.3

   ip address 172.17.72.1 255.255.252.0

   tagged A5,A13,A15,A19,B7

   exit

 

172.17.64.0/22     Bldg1_Wire... 64   connected            1          0    

172.17.68.0/22     Bldg1_Wire... 68   connected            1          0    

172.17.72.0/22     Bldg1_Wire... 72   connected            1          0    

 

So I've created 2 new VLANs as below

 

vlan 16

   name "RAP_WLAN"

   untagged F15-F16

   ip helper-address 10.28.0.10

   ip helper-address 10.28.0.3

   ip address 172.17.16.1 255.255.255.0

   tagged E3

   exit

vlan 18

   name “Legacy_WLAN"

   ip address 172.17.18.1 255.255.254.0

   exit

 

But when I run a show ip route, you can see that we have no routing for those VLANs:

 

  172.17.12.0/23     Management      12   connected            1          0    

  172.17.17.0/24     Aruba_WLAN      17   connected            1          0    

  172.17.64.0/22     Bldg1_Wire... 64   connected            1          0    

 

I've restarted the core a couple of times to no avail. Any ideas anyone has would be most welcome. Thanks for your help!

3 REPLIES
johnk3r
Respected Contributor

Re: New core switch VLANs not routing

Hello !

You have a device connected at both VLAN you created ?

**************************************
ATP FLEXNETWORK V3 | ACSA
BGW
Occasional Visitor

Re: New core switch VLANs not routing

There is nothing connected to these VLANs yet. I cannot even ping the IPs yet, and I know that the gateway IPs for the other VLANs were ping-able before something was physically connected to them. I've tagged and untagged ports with these VLANs as well, just so they'd be associated with something but nothing seems to be working. 

Vince-Whirlwind
Honored Contributor

Re: New core switch VLANs not routing

It's the same on a Cisco switch: the VLAN interface doesn't come up until you have an active device in the VLAN.

 

That one used to get me every time.