5320 Phones Not Connecting via DHCP

[DND ON]

After replacing Cisco 1841 routers with Cisco 4321 units at two locations, the 5320 phones are no longer able to connect via DHCP. We can see that the phones are assigned a valid IP address, but they don’t accept it. The phones just hang on DHCP Discovery.

These are small offices, with just a couple of IP phones connected to HX controllers at remote sites. It’s a flat network with fiber connecting the sites, no VPNs. I assigned a static IP address to the phones, and they immediately come up.

These phones have been in service for months, and this issue started when the routers were replaced. My Cisco guy doesn’t have an answer, because he can see that a valid IP address has been assigned. I’ve included the log file from the router. Anyone maybe have a clue?


*Nov 24 20:24:52.687: DHCPD: Sending notification of DISCOVER:
*Nov 24 20:24:52.687:   DHCPD: htype 1 chaddr 0800.0f83.fa6d   <<<< Phone’s MAC address
*Nov 24 20:24:52.687:   DHCPD: remote id 020a00000a1e0e0101000000
*Nov 24 20:24:52.687:   DHCPD: interface = GigabitEthernet0/0/1
*Nov 24 20:24:52.687:   DHCPD: class id 697070686f6e652e6d6974656c2e636f6d00
*Nov 24 20:24:52.687: DHCPD: Sending notification of DISCOVER:
*Nov 24 20:24:52.687:   DHCPD: htype 1 chaddr 0800.0f83.fa6d
*Nov 24 20:24:52.687:   DHCPD: remote id 020a00000a1e0e0101000000
*Nov 24 20:24:52.687:   DHCPD: interface = GigabitEthernet0/0/1
*Nov 24 20:24:52.687:   DHCPD: class id 697070686f6e652e6d6974656c2e636f6d00
*Nov 24 20:24:52.688: DHCPD: FSM state change INVALID
*Nov 24 20:24:52.688: DHCPD: Workspace state changed from INIT to INVALID
*Nov 24 20:24:52.688: DHCPD: classname not set in msg
*Nov 24 20:24:52.688: DHCPD: Allocated binding 7F8E5452BA88
*Nov 24 20:24:52.688: DHCPD: Adding binding to radix tree (10.30.14.118)
*Nov 24 20:24:52.688: DHCPD: Adding binding to hash tree 7F8E5452BA88
*Nov 24 20:24:52.688: DHCPD:dhcpd_binding_add_to_mac_hash: index- 247 add binding 7F8E5452BA88
*Nov 24 20:24:52.688: DHCPD: assigned IP address 10.30.14.118 to client 0108.000f.83fa.6d.   <<<<< IP address assignment
*Nov 24 20:24:54.687: DHCPD: Sending notification of DISCOVER:
*Nov 24 20:24:54.687:   DHCPD: htype 1 chaddr 0800.0f83.fa6d
*Nov 24 20:24:54.687:   DHCPD: remote id 020a00000a1e0e0101000000
*Nov 24 20:24:54.687:   DHCPD: interface = GigabitEthernet0/0/1
*Nov 24 20:24:54.687:   DHCPD: class id 697070686f6e652e6d6974656c2e636f6d00
*Nov 24 20:24:56.688: DHCPD: Sending notification of DISCOVER:
*Nov 24 20:24:56.688:   DHCPD: htype 1 chaddr 0800.0f83.fa6d
*Nov 24 20:24:56.688:   DHCPD: remote id 020a00000a1e0e0101000000
*Nov 24 20:24:56.688:   DHCPD: interface = GigabitEthernet0/0/1
*Nov 24 20:24:56.688:   DHCPD: class id 697070686f6e652e6d6974656c2e636f6d00
*Nov 24 20:24:56.688: DHCPD: Sending notification of DISCOVER:
*Nov 24 20:24:56.688:   DHCPD: htype 1 chaddr 0800.0f83.fa6d
*Nov 24 20:24:56.688:   DHCPD: remote id 020a00000a1e0e0101000000
*Nov 24 20:24:56.688:   DHCPD: interface = GigabitEthernet0/0/1
*Nov 24 20:24:56.688:   DHCPD: class id 697070686f6e652e6d6974656c2e636f6d00
*Nov 24 20:24:56.688: DHCPD: FSM state change INVALID
*Nov 24 20:24:56.688: DHCPD: Workspace state changed from INIT to INVALID   <<<<Phone did not accept or reject the IP address assignment.
*Nov 24 20:24:56.688: DHCPD: Found previous server binding
*Nov 24 20:24:56.688: DHCPD: classname not set in msgu all

[bluewhite4]

So if the router is the DHCP source, does it have the Mitel DHCP options programmed into it?

[DND ON]

I believe so. Is there a complete list in case he missed one?

[bluewhite4]

http://www.mitelforums.com/articles/3300/Mitel-3300-DHCP-Options.php

Should get you there.

[DND ON]

Those are 3300 options, not the same as I have for the 5000. I am having him double check for 43, 125, 128 to 130.

[bluewhite4]

Those are 3300 options, not the same as I have for the 5000.

For 5320 phones, they should be the same options regardless if it's for a 3300 or a 5000 I believe.

[DND ON]

Messing up my quote tags!

[DND ON]

Forgot to update this…

Confirmed that Mitel DHCP options are configured in the routers, unknown why they won’t accept an IP address via DHCP. We’ve moved on, leaving the phones with static addresses. It’s just not worth the time to pursue this for one or two phones.