Aries (CX600) phones and LLDP RRS feed

  • Question

  • Hi,

    I have an issue with the CX600 phones (assuming this applies to all Aries phones, though) using LLDP. LLDP is the protocol that the phones speak with the network switches to automatically determine what VLAN the phone should be on.

    Under normal circumstances, this is working. For VLANs 1-512 the phone is able to properly negiotate the correct VLAN and will connect just fine.

    However, if you have a VLAN ID of anything greater than 512, the phone is unable to hop on to that VLAN & just stays on the default.

    I have opened cases with PSS and Polycom, but wanted to put this out there just in case anyone has seen similar results.

    Also - we are using the CU1 updates for the phones & the switches fully support LLDP and the required IEE standards.



    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    Thursday, February 3, 2011 2:32 PM

All replies

  • Matt.

    I have the same issues as you are seeing and that Jeff blogged about: http://blog.schertz.name/2011/01/manual-vlan-configuration-for-lync-phone-edition/


    Mark King | MVP: Lync Server | MCTS:UC Voice | MCSE: Messaging | MCITP:Enterprise Messaging | www.unplugthepbx.com
    Thursday, February 3, 2011 11:21 PM
  • Thanks, this solved my problem. More info for completeness.

    I have tested an Aastra 6725ip phone running Lync 2010 phone edition version 7577.107 with a HP Procurve 5400 series L2 switch, where the voice VLAN is tagged and the data VLAN untagged. I can confirm that if the voice VLAN ID is greater than 512, the switch correctly sends the VLAN ID in the network policy LLDP-MED TLV but the phone cannot process it. Changing the VLAN ID < 512 fixes the problem. This makes me believe that the problem is with Lync 2010 phone edition OS, not with the phone vendor.


    HP Procurve config:

    interface A16
       name "AastraPhone"

    interface A20
       name "Uplink"

    vlan 119
       name "data-vlan"
       untagged A16
       no ip address
       tagged B20
       ip igmp
       no ip igmp querier

    vlan 120
       name "voice-vlan"
       tagged A16,B20
       no ip address
       ip igmp
       no ip igmp querier

    Saturday, February 12, 2011 2:58 AM
  • Jeff's blog does not address or identify the VLAN ID value problem during an LLDP-MED transaction.
    Saturday, February 12, 2011 3:45 AM
  • That is correct, the issues is related to the Lync Phone Edition software and not the hardware, and only applies to VLAN IDs greater than 511 when passed via LLDP.  Using the DHCP option method will allow the LPE devices to correctly connect to VLAN IDs higher than 511.  The Microsoft PSS ticket Matt opened should get the resolution into a future cumulative update package.
    Jeff Schertz, Microsoft Solutions Architect - Polycom | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Sunday, February 13, 2011 2:22 PM
  • The latest update for the phones (CU3) which was released this week fixes the LLDP problem.

    Get it here:

    For Polycom phones: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23866

    For Aastra phones: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18390


    • Proposed as answer by Adminiuga Monday, August 1, 2011 7:34 PM
    Wednesday, July 27, 2011 10:47 PM