Odd routing issue involving Procurve 2930

[spgsitsupport]

IP Phone gets DHCP from Core 5900 on Vlan21

Works fine:

Core 5900 G3/0/1 tagged Vlan 21 connects to Juniper voice router (set also as tagged Vlan21)

Fails:
- from Core I can ping both, IP Phone & Voice router
- from router can NOT ping either core or phone

Core 5900 G3/0/1 tagged Vlan 21 connects to Provurve 1/17 tagged Vlan21

Procurve 1/19 tagged Vlan 21 connects to Juniper voice router (set also as tagged Vlan21)

It just makes no sense to me that plugging Procurve in the middle of the path stops communication

Anybody has any idea what else to check?

Thanks

Seb

[-Alex-]

Hello  spgsitsupport,

You are right it does make no sense. 

You may check if there is no ACL or if the vlan is properly used for voice, I mean the traffic is properly in vlan 21.

2930 supports vlan and this should not be the problem.

Are you able to ping the phone from the core and are you able to ping the voice router from the 2930?

[spgsitsupport]

2930 Vlan 21 is set to VOICE on all devices

There are no ACLs that touch Vlan 21 (on either 5900 core or Procurve)

To ping voice router from 2930 I would need to connect laptop to one of the tagged ports, because 2930 does not have IP addressing for this Vlan (all routing is done on core)

[-Alex-]

Hello pgsitsupport,

Could you please not define vlan 21 on 2930 as voice but as normal vlan and see if tagged on the proper it will work.

Also you may check the following link:

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03386522

Hope this helps!

[spgsitsupport]

It makes no difference if I define Vlan 21 as Voice on 29330 or not (tried both)

Still no communication

I do not see the link relevant (di I miss something?)

[-Alex-]

Hello spgsitsupport,

The link includes the information and possible troubleshooting of the voice vlan.

Also it provides an example to add a PC or laptop to e port of the voice vlan which is untagged so that the PC will work in the vlan and test it if it will get the proper ip address and connectivity.

If the vlan has been created and configured and as normal vlan with proper ports tagged it should pass the passing traffic. As you said you have configured it properly. 

I would double check if the vlan is created with vlan command.

Then would check if the vlan is working by connecting a device to a port which belongs to the vlan and try to ping the voice router.

I would double check if the port is with proper tagged/untagged traffic. I would check other vlans if they are working through the switch. 

I would check the spanning tree too.

Also I would reboot 2930 if none of the above works..

It should pass vlan traffic as it is pass through traffic. Please check with other vlans if it working and the previous steps, otherwise from the information shared so far nothing leads to such behaviour as to block certain vlan.

Hope this helps!