VLAN routing help with e3800 and 2910al

[GreenEnvy]

Hello all,

We're in the process of setting up a Shoretel VoIP phone system. We got all new Procurve switches to go with them.

The switches are: 2x HP E3800-48Port-POE+, with stacking modules/cables, and 1 HP 2910al-48Port-POE+

I have setup several VLAN's, in addition to the default VLAN of 1:

401 - Servers

402 - Voice (where the phones are on)

403 - Print

404 - Workstation

499 - Storage (iSCSI traffic between our SAN and ESXi servers)

I'm only working with Vlan 1 and 402 right now. We are moving from a flat layout (no vlans) to this VLAN'd setup, so so far everything is just on 1 except the phones. 499 is also setup and working fine.

On the 3800 stack:

IP's are:

VLAN 1 = 10.4.1.105/22

VLAN 402 = 10.4.7.105/22

On the 2910al:

VLAN 1 = 10.4.1.101/22

VLAN 402 = 10.4.7.101/22

I've currently got IP routing enabled on the 3800 stack, but not on the 2910 (tried it both ways doesn't seem to work).

The command I used here was: "ip routing"

I haven't setup anything else routing wise that I can think of.

Ports 1-28 on the 2910 are setup with Vlan 1 untagged, and vlan 402 tagged.

Ports 1/1-1/48, and 2/1-2/47 are setup with vlan 1 untagged and vlan 402 tagged

Ports 48 on the 2910 and 2/48 on the 3800 stack are setup with all the vlan's marked as tagged. They are connected with a normal cat6 cable (waiting for the 10gb module to come in for the 2910, at which point they will be using the fiber spf's).

I can connect to devices within the same vlan without any issue across the switches.

The problem is that I can't route between the vlan's, and I am not sure why.

I think how i want this to work, is the 3800 stack will act as a router for all the VLAN's, and the 2910 won't do any routing. We have a watchguard firewall that connects to the WAN, but I'd prefer it not to our routing between vlan's.

Here is what I get when I do "show ip route" on the 3800 stack:

IP Route Entries

Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 10.4.0.253 1 static 1 1
10.4.0.0/22 DEFAULT_VLAN 1 connected 1 0
10.4.4.0/22 BuVoice 402 connected 1 0
10.4.8.0/22 BuPrint 403 connected 1 0
10.4.12.0/22 BuWorkStation 404 connected 1 0
10.4.16.0/22 BuServer 401 connected 1 0
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
192.168.99.192/26 BuStorage 499 connected 1 0

And here it is on the 2910 (which I currently have set to "no ip routing"

Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 10.4.0.253 1 static 1 1
10.4.0.0/22 DEFAULT_VLAN 1 connected 1 0
10.4.4.0/22 BuVoice 402 connected 1 0
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
192.168.99.192/26 BuStorage 499 connected 1 0

On the 3800 stack, if I SSH into it and try pinging all the vlan IP's assigned to it, I can do that. However if I connect to a device on one of those vlan's, I can't ping a device on a different vlan. I can't even ping the gateway of the other vlan.

gvrp is disabled, vrrp is disabled. 

I feel like I am missing something simple, but I don't have the VLAN experience to know what I am missing. I tried looking at our Nortel/Avaya switches in another office to see how they are setup, but didn't find any clues there.

Can anyone help?

Thanks

[GreenEnvy · Accepted solution]

Turns out having management enabled on VLAN1 was the problem. It won't route with management turned on.

Turned that off for vlan1 and all started working.

[CactusCraig]

I have 4 1910's on my network and am about to deploy a VOIP system.

The phones have gigabit switches in them for the computers to pass thru.

I am quite confused how to set this all up. We currently have 0 vlans.

anyone have a step by step that will help me?

1) Creating the VLAN

2) Assigning Ports to the Voice VLAN

3) Setting up DHCP only for the Voice Vlan

4) Allowing the Voice VLan to talk to the regular Lan for Web Access to phones, pbx, voicemail to email functionality, etc.

Any help is much appreciated. Thank you.

[ateslick]

I;m working on the same model switch ---but in a very remote and very live environment --with high profile management --daisy chained down stream....

I was wondering - didn't disabling management on vlan1 - hinder your ability to access the switch. I thought that what the management term was used for - access of the switch that is.