locked
Microsoft DHCP and Polycom Aries phones with VLANs - Not joining VLAN RRS feed

  • Question

  • We've retooled our topology over the weekend (http://social.technet.microsoft.com/Forums/en-US/ocsvoice/thread/259b1fd0-f063-4ed7-802b-0cd54dc2ba5a) to segment our Polycom CX600 phones to their own voice VLAN 99 (which is well under the 512 to avoid issues with these devices) using Dell PowerEdge 7000 series switches. Im using Microsoft DHCP, and have setup an additional network adapter in that VLAN on the DHCP server so I do not need a helper address.

    I'm starting to go crazy because I've followed Jeff's instructions (http://blog.schertz.name/2011/01/manual-vlan-configuration-for-lync-phone-edition/) to the letter and no matter what the phones do they just will not attach to the right VLAN. I've spent about 8 hours with Dell over the weekend to make sure that I had 802.1x authorization turned off and the Voice VLAN settings were setup properly but when I run the test-CsPhoneBootstrap command I dont see any reference to the MSCPEPhone option:

    VERBOSE: Workflow Instance Id 503bb071-c155-46a7-bff9-214f1ee9513c, started.
            Constructing a dhcp packet
            Adding dhcp option PARAMETER_REQUEST_LIST
            Successfully added dhcp option
            Adding dhcp option VENDOR_CLASS_IDENTIFIER
            Successfully added dhcp option
            Successfully constructed dhcp packet
            =======================PACKET BEGIN==============================
            op: 1
            htype: 1
            hlen: 6
            hops: 0
            xid: 199
            secs: 0
            flags: 0
            ciaddr: 172.20.99.50
            yiaddr: 0.0.0.0
            siaddr: 0.0.0.0
            giaddr: 0.0.0.0
            chaddr:  PV? ♦
            sname:
            file:

            magic: 99.130.83.99
            Message Type : DHCPINFORM
            Option43 :
            Option55 : 7☻x+
            Option60 : <♀MS-UC-Client
            Option120 :
            Other options :
            =======================PACKET END================================
            Trying to open an udp connection
            Remote IP : 255.255.255.255
            Local IP : 172.20.99.50
            Udp connection successfully created
            Sending packet
            Remote IP : 255.255.255.255
            Remote port : 67
            Packet send successfully
            Data received
            Remote IP : 172.20.99.253
            Remote Port : 67
            Data length : 377
            Data value : ☻☺♠ ?       ?¶c2             PV? ♦


                     c?Sc5☺♣6♦?¶c?☺♦??? +_☺♀MS-UC-Client☻♣https♥‼pool.ad.local
    ♦♥443♣%/CertProv/CertProvisioningService.svc
    ☻ c?♥NAPx▬ ♦pool☻ad♥local ?
            Constructing a dhcp packet from received raw data
            Extracting DHCP Options
            DHCP Packet successfully constructed
            =======================PACKET BEGIN==============================
            op: 2
            htype: 1
            hlen: 6
            hops: 0
            xid: 199
            secs: 0
            flags: 0
            ciaddr: 172.20.99.50
            yiaddr: 0.0.0.0
            siaddr: 0.0.0.0
            giaddr: 0.0.0.0
            chaddr:  PV? ♦
            sname:
            file:

            magic: 99.130.83.99
            Message Type : DHCPACK
            Option43 : ☺♀MS-UC-Client☻♣https♥‼pool.ad.local♦♥443♣%/CertProv/Ce
    rtProvisioningService.svc
    ☻ c?♥NAP
            Option55 :
            Option60 :
            Option120 :  ♦pool☻ad♥local
            Other options : 6♦?¶c?☺♦???
            =======================PACKET END================================
            Return value for dhcp option : SIP_SERVER
            Return value for dhcp suboption : VENDOR_SPECIFIC_INFORMATION.1
            Return value for dhcp option : VENDOR_SPECIFIC_INFORMATION
            Successfully extracted suboption value
            Return value for dhcp suboption : VENDOR_SPECIFIC_INFORMATION.2
            Return value for dhcp option : VENDOR_SPECIFIC_INFORMATION
            Successfully extracted suboption value
            Return value for dhcp suboption : VENDOR_SPECIFIC_INFORMATION.3
            Return value for dhcp option : VENDOR_SPECIFIC_INFORMATION
            Successfully extracted suboption value
            Return value for dhcp suboption : VENDOR_SPECIFIC_INFORMATION.4
            Return value for dhcp option : VENDOR_SPECIFIC_INFORMATION
            Successfully extracted suboption value
            Return value for dhcp suboption : VENDOR_SPECIFIC_INFORMATION.5
            Return value for dhcp option : VENDOR_SPECIFIC_INFORMATION
            Successfully extracted suboption value
            Disconnecting
            Connecting to web service : http://pool.ad.local/CertProv/CertProv
    isioningService.svc
            Using anonymous authentication
            Successfully created connection proxy and website bindings
            Attempting to download certificate root chain
            request created
            GetRootCertChain() webservice call successful
            Connecting to web service : https://pool.ad.local:443/WebTicket/We
    bTicketService.svc
            Using PIN authentication
            Successfully created connection proxy and website bindings
            Requesting new web ticket

     

    At this point Dell tier 2/3 have vetted this as a Microsoft issue, and provided me a 4 line command that they use in their environment to make it work but Im not having any luck. Could there be something that I'm missing to actually make it work?

    Monday, August 22, 2011 6:58 PM

Answers

All replies

  • Just wanted to share that Ive resolved the issue!

    On the Dell 7000 series switches I had the port configuration right, which is:

    interface Gi1/0/1

    switchport mode general

    switchport general allowed vlan add 10 tagged

    voice vlan 10

    voice vlan auth disable

    However ultimately my issue is that the CX-series phones we have are running the UTM code (build 107) and once I followed Jeff's instructions (http://blog.schertz.name/2011/01/updating-lync-phone-edition-devices/) to push out the CU3 code (build 296) the phones were able to operate on Layer 3.

    One important key to emphasize is that the CX series phones do not support 802.1x authentication (http://knowledgebase-iframe.polycom.com/kb/documentLinkInt.do?micrositeID=&micrositeID=&externalID=10076) so the "voice vlan auth disable" is key as well.

    Hope this helps someone else!

    • Marked as answer by C Blackburn Tuesday, August 23, 2011 11:37 AM
    Tuesday, August 23, 2011 11:37 AM
  • Hi thetootall,

    Thank you for sharing your solution. It is very beneficial for others.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, August 24, 2011 1:37 AM