Hi All,

We have an issue where our LPE devices (CX3000 and CX600) are booting on our Voice VLAN (using LLDP configured on a HP Procurve 2610) but the IP address the device gets leased is from our Data VLAN. A Windows 2003 DHCP server manages DHCP requests for the Data VLAN (VLAN ID 1) and a Mitel Controller 3300 manages DHCP requests for the Voice VLAN (VLAN ID 6). I used WireShark to trace the packets on the port the LPE device is connected to and found that both Mitel Controller and Windows DHCP server offered an address from their Scope but for some reason the LPE device is acknowledging the VLAN ID 1.

Both 'Better Together' and PIN authentication modes fail as the device still gets an incorrect IP address. Our standard Mitel phones boot with no issues and get assinged the correct IP address.

The scopes are setup as follows:
Windows DHCP Server: Scope 10.60.50.0
Mitel Controller: Scope 10.60.51.0

I did manage to get my CX600 to work by disabling DHCP services on the Windows Server then performing Hard Reset on the phone. All went through ok as the phone was leased an IP on the Voice VLAN. Another way I got it to work was by statically assigning VLAN 6 to the port the phone was plugged in to. However, because we use the  LPE devices as a bridge for the Desktop PCs we will need to allocate multiple VLANs across ports so that we can seperate Voice and Data traffic to employ QoS.

We're running Lync Enterprise Edition. Front End Server version = 4.0.7577.184
CX600 version = 4.0.7577.4066

Hardware were using:
Procurve 2610 48port POE switch.
Mitel 3300 Controller (DHCP server for Voice VLAN)
Windows 2003 server (DHCP server for Data VLAN)
LPE Devices: CX600 and CX3000

Are you using Option 43 on the Microsoft DHCP SERVER?
Vendor class = CPE-OCPHONE?
This must be removed if LLDP is used

Hi,

Please refer to Jeffs blog to check your VLAN configuration:

http://blog.schertz.name/2011/01/manual-vlan-configuration-for-lync-phone-edition/

Regards,

Kent

Thanks Johan, no we are not using Option 43 as we rely on LLDP.

Hi Kent-Huang,

We are not manually configuring VLANs because we use LLDP.

I wonder if there is some form of built in preference for LPE Polycom phones to use Windows DHCP server over a Mitel Controller.

As a workaround we are looking to move the DHCP scopes from Mitel controller to the Windows DHCP server and setting up a DHCP IP helpers/Relay agent. However, a resolution would be great, otherwise we have to make this change across every site that has a LPE device presence.

I've also requested support from Mitel but am still waiting for a response.

Thanks

Which version is your HP procurve  because If found this :

HP ProCurve 2610 series switched have an LLDP bug which prevents Polycom phones from getting proper VLAN information in ProCurve firmware version 11.55 through 11.69. 11.54 and 11.70 do not have this issue.

Because if your device is in the right VLAN , it must not receive DHCP response from a DHCP server placed on another VLAN or your VLANS are not isolated.

RGDS

JMF

• Proposed as answer by FRANCOIS Jean-Marc Wednesday, May 23, 2012 7:25 AM
• Unproposed as answer by Paul Cook - Perth, WA Tuesday, May 29, 2012 3:15 AM

Which version is your HP procurve  because If found this :

HP ProCurve 2610 series switched have an LLDP bug which prevents Polycom phones from getting proper VLAN information in ProCurve firmware version 11.55 through 11.69. 11.54 and 11.70 do not have this issue.

Because if your device is in the right VLAN , it must not receive DHCP response from a DHCP server placed on another VLAN or your VLANS are not isolated.

RGDS

JMF

• Proposed as answer by FRANCOIS Jean-Marc Wednesday, May 23, 2012 7:25 AM
• Unproposed as answer by Paul Cook - Perth, WA Tuesday, May 29, 2012 3:15 AM

Thanks Francios. We're running R.11.07. I'd like to think this bug you mention is the problem, but the LPE does go on the correct VLAN so I'm incline to think that LLDP is working. Also, the above doesn't explain why if I turn off DHCP services on the Windows DHCP server, the LPE device succesfully gets a DHCP lease from the Mitel controller.

Having thought more about this, I think the best approach would be to manage the Voice VLAN DHCP scope on the Windows DHCP server anyway. I'm not sure whether its possible for the Mitel Controller to publish the Lync specific DHCP scope options.

Thanks

• Marked as answer by Paul Cook - Perth, WA Monday, May 07, 2012 12:56 AM
• Unmarked as answer by Paul Cook - Perth, WA Tuesday, May 08, 2012 12:54 AM

Thanks Francios. We're running R.11.07. I'd like to think this bug you mention is the problem, but the LPE does go on the correct VLAN so I'm incline to think that LLDP is working. Also, the above doesn't explain why if I turn off DHCP services on the Windows DHCP server, the LPE device succesfully gets a DHCP lease from the Mitel controller.

Having thought more about this, I think the best approach would be to manage the Voice VLAN DHCP scope on the Windows DHCP server anyway. I'm not sure whether its possible for the Mitel Controller to publish the Lync specific DHCP scope options.

Thanks

• Marked as answer by Paul Cook - Perth, WA Monday, May 07, 2012 12:56 AM
• Unmarked as answer by Paul Cook - Perth, WA Tuesday, May 08, 2012 12:54 AM

Paul,

I was wondering if you found a resolution to your problem.  I am having a similar issue using LLDP.  I'm running DHCP on windows 2008.  I'm Cisco 3560's for data and voice.  My DHCP server is in the data vlan and I have a helper address on my voice vlan and the ports are configured for data and voice vlans.

When I plug in a phone it gets the correct voice vlan id, but it receives an ip address in the data vlan.  If I remove the data vlan from the switch port it receives an ip in the correct scope.  Unfortunately I have a lot of users at this site that need to plug their PC's into their phones.  Any info would be much appreciated.

Hi Josh,

This is still an issue for us and i'm starting to think its a DHCP Scope or Switch configuration issue rather than LLDP or LPE device. I'm not a networking guy so I can only go by good guess work and research. However, I do have an answer or two that I hope help your situation!

How are your scopes configured? The following article http://support.microsoft.com/kb/120932 dictates that your scope ranges should include the VLAN IP address of the switch that forwards (relays) your DHCP requests. That way it knows which DHCP scope to grab an IP from.

Have you used Wireshark before? I suggest you do some packet sniffing on the port your VOIP phone is connected to and use the following filter "udp.port eq 67 and udp.port eq 68" you'll need to clear the filter to see the Gratuitous ARP (once the phone has accepted a DHCP offer from the DHCP server it sends out a Gratuitous ARP which is the device sending a broadcast saying "DHCP server has given me this IP address, i just want to make sure noone else is using it!!"

I've not had much time to spend on this issue so haven't made much progress. I think my next job will be to run wireshark on the DHCP servers port and make sure the switch is relaying the DHCP packet correctly (i.e. putting the correct GIADDR data in).

Let me know how you go!

There may be some useful tips here too http://www.experts-exchange.com/Hardware/Networking_Hardware/Switches/Q_27264485.html

I ran into a similar situation, where a client had a DHCP server for the data VLAN and on a Cisco 3560 L3 switch we were running DHCP for the voice VLAN. The Polycom's would sometimes get an IP from the data VLAN and sometimes from the voice VLAN.  To resolve the issue we had to find the port that the client DHCP server was on, change it from a dynamic auto trunk port to an access port and remove the voice vlan 200 setting.  Once we did that the phones consistently are only getting DHCP from the voice VLAN.

• Proposed as answer by Olwen Davies Monday, April 13, 2015 5:28 AM

I ran into a similar situation, where a client had a DHCP server for the data VLAN and on a Cisco 3560 L3 switch we were running DHCP for the voice VLAN. The Polycom's would sometimes get an IP from the data VLAN and sometimes from the voice VLAN.  To resolve the issue we had to find the port that the client DHCP server was on, change it from a dynamic auto trunk port to an access port and remove the voice vlan 200 setting.  Once we did that the phones consistently are only getting DHCP from the voice VLAN.

• Proposed as answer by Olwen Davies Monday, April 13, 2015 5:28 AM

I am still working on this issue but have had it for some time now, having had to set the phones to manual DG. It seems that the trunk port in use for our VMWare server seems to cause this phenomenon, so when I moved the DHCP scope to a physical server on an access port as described, this issue seems to have stopped.