topic Re: HP5412zl VOIP VLAN Assignments Issue in Switches, Hubs, and Modems

HP5412zl VOIP VLAN Assignments Issue

Steve K Harris — Wed, 03 Nov 2010 21:45:19 GMT

Hi experts,

I am trying to setup 200 ININ SIP 100 VOIP stations on my HP Procurve 5412zl switch as follows:

These VOIP Appliances are class 1 POe devices and my switch is Poe as well also they do not have LED/LCD screens that I can

use to set configuration settings with.

Issue:

I need to use 1 port on the switch to connect both the VOIP appliance and the PC where the PC gets an IP on VLAN3 and the

Appliance gets an IP on VLAN5 (the VOIP VLAN)

The VOIP appliance has a 1 port switch on it to use to connect the PC through it.

Problem:

The problem is that I cannot get the two device to get IP's from different VLANS.

I setup a port(I2) as an untagged member of VLAN3 and a tagged member of VLAN5(voip) but both devices get a VLAN3(data) IP

address.

I have done this before and can't remember the additional steps needed to make this work.

I need to get this working by tomorrow and urgently need some assistance from an HP Procurve expert :-)

I have followed the following advice from the documentation for my switch.(see below)

I have also copied my config to the bottom of this post.

Voice VLANs

Configuring voice VLANs separates voice traffic from data traffic and shields your voice traffic from broadcast storms. This

section describes how to configure the switch for voice VLAN operation.
Operating Rules for Voice VLANs

You must statically configure voice VLANs. GVRP and dynamic VLANs do not support voice VLAN operation.

Configure all ports in a voice VLAN as tagged members of the VLAN. This ensures retention of the QoS (Quality of Service)

priority included in voice VLAN traffic moving through your network.

If a telephone connected to a voice VLAN includes a data port used for connecting other networked devices (such as PCs) to

the network, then you must configure the port as a tagged member of the voice VLAN and a tagged or untagged member of the

data VLAN you want the other networked device to use.

Tagged/Untagged VLAN Membership: If the appliances using a voice VLAN transmit tagged VLAN packets, then configure the

member ports as tagged members of the VLAN. Otherwise, configure the ports as untagged members.

Config:

ProCurve J8698A Switch 5412zl
Software revision K.14.60

HP 5412zl 10th Floor# config t
HP 5412zl 10th Floor(config)# show config

Startup configuration:

; J8698A Configuration Editor; Created on release #K.14.60

hostname "HP 5412zl 10th Floor"
time timezone -480
time daylight-time-rule Continental-US-and-Canada
module 1 type J8702A
module 2 type J8705A
module 3 type J8702A
module 4 type J8702A
module 5 type J8702A
module 6 type J8702A
module 7 type J8702A
module 9 type J8705A
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged B1-B24,C1,G13-G24,I1,I3-I4,I6,I8-I24
ip address 192.168.1.2 255.255.255.0
tagged I5
no untagged A1-A24,C2-C24,D1-D24,E1-E24,F1-F24,G1-G12,I2,I7
exit
vlan 2
name "Corporate"
untagged A1-A24,C2-C24,E1-E24,G1-G12
ip helper-address 192.168.1.16
ip address 192.168.2.1 255.255.255.0
tagged B23
exit
vlan 3
name "Call Center 1"
untagged D1-D24,F1-F24,I2
ip helper-address 192.168.1.16
ip address 192.168.3.1 255.255.255.0
tagged B23
exit
vlan 4
name "Call Center 2"
ip helper-address 192.168.1.16
ip address 192.168.4.1 255.255.255.0
tagged B23
exit
vlan 5
name "VOIP"
ip helper-address 192.168.1.16
ip address 192.168.5.1 255.255.255.0
tagged B23,D1-D24,F1-F24,I2
exit
vlan 40
name "WLAN"
untagged I5,I7
tagged B23
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
console inactivity-timer 30
no dhcp-relay hop-count-increment
logging 192.168.1.12
logging severity info
qos udp-port ipv4 range 16386 25386 dscp 101110
qos udp-port ipv4 range 8000 8010 dscp 101110
qos udp-port ipv4 range 2222 2268 dscp 101110
qos udp-port ipv4 5060 dscp 011000
timesync sntp
sntp unicast
sntp 30
sntp server priority 1 192.168.1.1 3
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip route 10.181.204.0 255.255.255.0 192.168.1.19
snmp-server community "public" unrestricted
snmp-server contact "IT Administrator" location "10th Floor"
no autorun
password manager
password operator

HP 5412zl 10th Floor(config)#

Re: HP5412zl VOIP VLAN Assignments Issue

Jeff Carrell — Wed, 03 Nov 2010 22:06:02 GMT

Sounds to me as if the VoIP phones are configured to "speak" untagged to start with.

Various systems I've setup required me to have the phone configuration info be tftp downloaded to the phone, via a tftp server config parameter in the DHCP server (in your case VLAN3 scopes).

The phone gets a vlan3 addr, gets its tftp server addr, does a tftp d/l, in the config file there parameters to make the phone reconfig to speak tagged, then reboot itself. Then the phone comes up speaking tagged and now gets a vlan5 addr and communicates to the phone server.

To me it looks like you have no ports untagged in vlan5...is the phone server in a different vlan? (or is it speaking tagged)

hth...Jeff

Re: HP5412zl VOIP VLAN Assignments Issue

Jeff Carrell — Wed, 03 Nov 2010 22:08:58 GMT

I also meant to say, the few brands of VoIP phones I have played with default to speaking untagged. That is why I had to go through the steps I did, as they had to be controlled based on a downloaded config file.

hth...Jeff

Re: HP5412zl VOIP VLAN Assignments Issue

Steve K Harris — Thu, 04 Nov 2010 00:06:29 GMT

Thanks Jeff ! !

This actually makes a lot of sense and has put me on the right track to getting this resolved.

Some additional info:

The vendor has specified option 160 in the DHCP scope with the address to their provisioning server which is on the other side of an MPLS link.
However I do not have end to end connectivity with it until tomorrow which might explain why it's not working yet based upon the info you provided :-)

Re: HP5412zl VOIP VLAN Assignments Issue

Steve K Harris — Thu, 04 Nov 2010 00:15:17 GMT

Jeff just to confirm,

If I want the PC's in the data VLAN3 and the phones in the voice VLAN5, I need to have the ports untagged in VLAN3 and tagged in VLAN5 correct ?

But intially I need to have both devices in VLAN3 so the phones can get the config from the provisioning server via option 160 in VLAN3 correct ?

Re: HP5412zl VOIP VLAN Assignments Issue

Jeff Carrell — Thu, 04 Nov 2010 02:16:09 GMT

Steve asked: to confirm,

If I want the PC's in the data VLAN3 and the phones in the voice VLAN5, I need to have the ports untagged in VLAN3 and tagged in VLAN5 correct ?

But initially I need to have both devices in VLAN3 so the phones can get the config from the provisioning server via option 160 in VLAN3 correct ?
----

Yep, that (all the above) should do it :-)

Of course let us know when it all works :-)

hth...Jeff

Re: HP5412zl VOIP VLAN Assignments Issue

Steve K Harris — Thu, 04 Nov 2010 23:14:12 GMT

Will do !

I am very close now and found out from the hardware provider that there is a bug in the current firmware that causes a problem with VLAN discovery and results in both devices obtaining IP's from the native data VLAN.

Apparently LLDP support has been added in this next version so I turned that on in anticipation of the fix.

Problem now is that I cannot contact their update server due to a routing issue either in the switch or the MPLS router....not sure which is the culprit at this time.

Starting a separate post for that.