Cisco IP Phones failed to get IP from the DHCP server.
The DHCP scope configured on the Windows server is as below for the Cisco IP Phones.
IP Range: 10.136.x.x to 10.136.x.x
DNS Servers: a.b.c.d
DNS Domain Name: XYZ.com
TFTP Server: 10.136.123.11
The network is configured to relay the DHCP request to the above server.
However, the phones doesn't get the IP from the DHCP server.
Configuring the DHCP on the Cisco Router on the same site, works fine. Phones get the IP. Disabled the DHCP server on the Router after testing.
Moving the phones to default VLAN (where computers are connected), phones get the IP from the Windows DHCP server.
Issue only with the scope configured for the phones (the above said scope) on the Windows Server.
Moved the phone back to voice vlan.
Did the packet captures on the DHCP server.
Packet shows the DHCP server offering the IP with the below TFTP details:
The TFTP IP address configured on the server is 10.136.123.11. But the captures shows 3 different TFTP IP's:
Option: (150) TFTP Server Address Length: 14 TFTP Server Address: 188.8.131.52 TFTP Server Address: 184.108.40.206 TFTP Server Address: 220.127.116.11 [Expert Info (Error/Protocol): Option length isn't a multiple of 4] [Option length isn't a multiple of 4] [Severity level: Error] [Group: Protocol]
The TFTP IP configured is taken as ASCII Character and the server converts it into Decimal. So, the converted Decimal values are seen in the captures.
The above Decimal is split into 3 different IP's - 18.104.22.168, 22.214.171.124, 126.96.36.199 and then 49.
The above format doesn't match the option length which should be multiple of 4. So, we see the error "Option length isn't a multiple of 4".
Please see the below link for the option length calculation: (search for the "option lenght isn't a multiple of 4")
Phones rejected with the error DHCP: ERROR parsing options -- cnt = -1, tag = 49, len = 0
The TFTP option input value might be either configured to accept different Data Type like text or word or url instead of IP Address and then convert to decimal like above case or the TFTP option would have corrupted in the DHCP server.
Delete the TFTP Predefined value from the Microsoft Windows DHCP server.
DHCP Server > IPv4 > Right Click > Set Predefined Value > Search for Option "150 TFTP Server" under Option name Drop down > Delete.
To Add the the value, go to the same page and Click on "Add".
Add the Option Type with the name as "TFTP Server", Data Type as "IP Address" and the code as "150".
Now, configure the TFTP option for the Voice Scope. Goto DHCP Server > Scope configured for Phones > Scope Option > Right Click > Configure Options > Scroll Down to select "150 TFTP Server" added above and add the IP address > Apply > Ok.
Reset the phone from the CUCM or Power cycle to send out the DHCP request.
Now the phones get the correct IP address with the option 150. The packet capture shows the correct TFTP IP.
Hi This may have been asked / answered before but I was wondering if anyone knows if it'd be possible to stack a 9200 & 9300 switch together? I've read through the white papers which only mention the 9300 & 9300L not working in a mixed s...
Hello, I am newbie, i replaced 2 switches with vlan33 protected by FW with 4 cisco 2x sg350x and 2x SX350X in Hybrid stack. The stack is now accessible from vlan1 and vlan33. Removing FW I have to filter accesses in http https from vlan1 to vla...
Hi. Are there any guides on how best to handle voice services on a SDA network? I have a PoC setup working nicely for data, with .1x auth on the switchports, but I'm struggling to understand how to add the IP phones into the mix, now that there...
Good day, I'm using Packet Tracer 8 on MacOs and whenever I open the terminal to configure a switch or router, the terminal is just a plain black screen with a cursor, the commands I type don't even work. Does anyone know how to fix this? Thank you
Leopold Fisher, Cisco Meraki IoT specialist, will introduce you to new and innovative additions to the Meraki portfolio coming in April 2021.
Meraki Vision Session
MV smart camera range is getting big...