Setting up VLAN Tagging for IP phones on HP switched network

[Crono]

Hello all,

We are starting to roll out IP phones here in our office. We want to make use of the built in switch on the Mitel phones that allow the phone and a PC to run off of one data port. However our phone system is on a different subnet from our data network.

We are using HP ProCurve 5406 switches. Can someone post a basic how to of how I would procede to get this to work?

Thanks for your time.

 

[kwbMitel]

This is kind of a broad question.

Can you be more specific?

 

[Crono]

Hi kwb,

Sorry, I knew it was pretty vague. I have trouble typing out a questions sometimes. I'll try to reword:

We have a Mitel 3300 ICP and are on a network using HP ProCurve 5406 managed switches.

Right now we are digital phones but want to roll out IP phones in the near future.

What I want to do is utilize the PC port on the Mitel IP phones so that the PC and phone share the same port on the switch.

The phone system and the data network are on different subnets so I know without a doubt that I need to do some VLAN tagging. I was hoping someone would give me some pointers on VLAN tagging. Based on what I have researched so far I am going to take an educated guess:

1. Create two VLANs (untagged for Data, tagged for Phone)

2. Tag the ports that are connected to the phone system

3. Set the other ports as tagged and untagged and then manually set the IP phone to look for VLAN 2 (the Phone VLAN).

My guess is that the PC data will go on the untagged VLAN while the Phone will use VLAN 2.

Set QoS so that VLAN2 has priority.


Am I getting this right?

 

[andy4uk]

Hi Crono, is this what your after..??

Switch Configuration - VLAN - VLAN Port Assignment

Port DEFAULT_VLAN voice_VLAN
---- + ------------ ------------
1 | Untagged Tagged (Router port)
2 | No Untagged (3300 ICP port)
3 | Untagged No (data connection only)
4 | Untagged Tagged (IP phone plus data)
5 | No Tagged (IP phone only)
6 | Untagged No
7 | Untagged No
8 | Untagged No
9 | Untagged No
10 | Untagged No
11 | Untagged No
12 | Untagged No

 

[Lundah]

There's a bit more to it than that. The IP phones will first come up on the default (data) VLAN, so you need to set up your DHCP server on that VLAN with the correct DHCP options to point the IP phones to the Voice VLAN. This is in the documentation from both HP and Mitel. Also, make sure you turn off the Voice VLAN on the switchport facing your Data VLAN's DHCP server, this can cause problems with phones not seeing the Mitel 3300 ICP.

 

[kwbMitel]

1. Create two VLANs (untagged for Data, tagged for Phone)
(YES)

2. Tag the ports that are connected to the phone system.
(NO) The 3300 connects to a port that is untagged for the voice and none(disabled) for the default Vlan

3. Set the other ports as tagged and untagged and then manually set the IP phone to look for VLAN 2 (the Phone VLAN).
(YES AND NO) Ports with Phones AND PC's get Both VLANS with the Voice VLAN as Tagged. Servers, printers, etc should not have access to the Voice Vlan (Especially the DHCP server on the Data VLAN) The phones do not have to be statically assigned to the Vlan. The phone can be told via options in the Data DHCP Server what vlan it should be on.

My guess is that the PC data will go on the untagged VLAN while the Phone will use VLAN 2. (Yes)

Set QoS so that VLAN2 has priority. (Done via DHCP or Static settings)


Am I getting this right? (Pretty close)


VLAN/ DHCP Registration Flow for DHCP

Plug in phone
Phone requests DHCP on Default Vlan
DHCP Delivers Options 128,129,130, 132 and 133 to phone.
Phone recognises Via 132(vlan), 133(Priority) that it should be on different VLAN
Phone ACK's IP but releases it back to DHCP server
Phone resubmits TAGGED DHCP request on Voice vlan.
3300 "Hears" request and provides appropriate options.
Phone continues to load and proceeds to the registration process.

You can statically assign the VLAN and Priority to avoid the first DHCP cycle but it adds a lot of overhead if you're thinking of activating a lot of sets.