Plantronics + Polycom. Now together as Poly Logo

IP6000 - Failed to get boot parameters via DHCP

SOLVED
urchin8
Occasional Visitor

IP6000 - Failed to get boot parameters via DHCP

Hi all, long term Polycom user but first time poster.  My question is regarding an IP6000 2201-15600-001 and a Juniper SRX210 firewall with POE.  The phone is plugged directly into a fast ethernet POE port on the SRX, and the SRX is also serving DHCP.  I have tried 3.3.5, 4.0.4, 4.0.7, and 4.0.11 all with the same results. 

 

With this configuration, the phone fails to get an IP address.  From a DHCP debug on the SRX, I see the DISCOVER from the phone, the OFFER from the SRX, but then no REQUEST from the phone.  The DISCOVER / OFFER keeps trying for a while until the phone gives up. 

 

However if I put a Cisco 3560 in between the 2 devices, it works fine.  An IP550 or Snom 320 plugged directly into the SRX also works flawlessly.  I have tried disabling CDP and LLDP on the phone and setting up LLDP / LLDP-MED with a voice vlan on the SRX, also no effect. 

 

Any ideas?  I've been banging my head against this on and off for the last 2 days.  

 

Thanks!

 

Message 1 of 5
1 ACCEPTED SOLUTION

Accepted Solutions
urchin8
Occasional Visitor

Re: IP6000 - Failed to get boot parameters via DHCP

Uhhhhh.... wow... As a last resort I set it to 10mbit full duplex and it magically worked.  I had tried hardcoding to 100 full before and it did not work.  Guess there is some incompatibility between the SRX and Polycom autonegotiation.  Happy to look deeper into it if there is a need... For now I'll just leave it at 10mbit I guess!  

View solution in original post

Message 4 of 5
4 REPLIES 4
SteffenBaierUK
Polycom Employee & Community Manager

Re: IP6000 - Failed to get boot parameters via DHCP

Hello urchin8,

welcome to the Polycom Community.

What Updater Version aka BootROM is on the phone?

 

If using UC Software 4.0.11 it should be 5.0.11

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. My official "day" Job is 3rd Level support at Poly but I am unable to provide official support via the community.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 5
urchin8
Occasional Visitor

Re: IP6000 - Failed to get boot parameters via DHCP

Right now it's 4.5.0.0093 because I downgraded to use application 3.3.5.  I can upgrade to any version you would like for testing, please just specify it.  Thanks.  DHCP log below:

 

Dec 23 00:24:23 sendmsg() from 0.0.0.0 to port 68 at 255.255.255.255 via routing instance default sucess
Dec 23 00:24:23 sent packet from 0.0.0.0 to 255.255.255.255 port 68 out interface vlan.110 routing instance default
Dec 23 00:24:23 ==> DHCPOFFER [done]
Dec 23 00:24:23 RELEASE LEASE [0x580500:2]: `00:04:f2:xx:xx:xx' (dhcpd_protocol_dhcp.c:415)
Dec 23 00:24:23 <== DHCPDISCOVER [done]
Dec 23 00:24:31 received packet from 0.0.0.0 port 68 interface vlan.110 routing instance default
Dec 23 00:24:31 Link local IP: 0
Dec 23 00:24:31 -- looking for pool with subnet 10.25.110.1, prefix length 32
Dec 23 00:24:31 -- [pfxlen 24] Found pool `10.25.110.0/24'
Dec 23 00:24:31 Decoding packet from 0.0.0.0
Dec 23 00:24:31 parsing options from packet
Dec 23 00:24:31 option `dhcp-message-type' code 53 extracted from buffer
Dec 23 00:24:31 option `dhcp-lease-time' code 51 extracted from buffer
Dec 23 00:24:31 option `dhcp-parameter-request-list' code 55 extracted from buffer
Dec 23 00:24:31 option `Vendor-Indentifying Vendor-Specific Information' code 125 extracted from buffer
Dec 23 00:24:31 option `vendor-class-identifier' code 60 extracted from buffer
Dec 23 00:24:31 looking for overloaded options
Dec 23 00:24:31 looking up message type
Dec 23 00:24:31 Processing DHCP packet
Dec 23 00:24:31 <== DHCPDISCOVER
Dec 23 00:24:31 Looking for a lease w/hardware address `00:04:f2:xx:xx:xx'
Dec 23 00:24:31 ...and no client identifier
Dec 23 00:24:31 ...and subnet 10.25.110.0/24
Dec 23 00:24:31 Found matching lease entry for `00:04:f2:xx:xx:xx'
Dec 23 00:24:31 Lease #1...
Dec 23 00:24:31 ...correctly has no client identifier
Dec 23 00:24:31 ...has the correct subnet
Dec 23 00:24:31 found: 08, satisfies: 0a, exact: 0a
Dec 23 00:24:31 REFERENCE LEASE [0x580500:2]: `00:04:f2:xx:xx:xx' (dhcpd_lease.c:973)
Dec 23 00:24:31 Exact match
Dec 23 00:24:31 ==> DHCPOFFER
Dec 23 00:24:31 -- looking for pool with subnet 10.25.110.103, prefix length 32
Dec 23 00:24:31 -- [pfxlen 24] Found pool `10.25.110.0/24'
Dec 23 00:24:31 flushed options on binding
Dec 23 00:24:31 set next server address to 0.0.0.0
Dec 23 00:24:31 set client address to 10.25.110.103
Dec 23 00:24:31 found option `boot-server' code 66 in `Pool' scope 0x576000
Dec 23 00:24:31 Default lease time 1 day obtained from `Global' scope
Dec 23 00:24:31 Flag = 4 Expiry = 17158 days, 16 hours, 24 minutes, 31 seconds
Dec 23 00:24:31 Flag = 4 17158 days, 16 hours, 24 minutes, 23 seconds
Dec 23 00:24:31 Using default lease time of 1 day
Dec 23 00:24:31 Maximum lease time infinite obtained from `Global' scope
Dec 23 00:24:31 adding option `subnet-mask' code 1 to binding
Dec 23 00:24:31 adding option `broadcast-address' code 28 to binding
Dec 23 00:24:31 client requested option `subnet-mask' code 1
Dec 23 00:24:31 client requested option `time-offset' code 2
Dec 23 00:24:31 client requested option `router' code 3
Dec 23 00:24:31 client requested option `time-servers' code 4
Dec 23 00:24:31 client requested option `name-server' code 6
Dec 23 00:24:31 client requested option `domain-name' code 15
Dec 23 00:24:31 client requested option `ntp-servers' code 42
Dec 23 00:24:31 client requested option `server-identifier' code 54
Dec 23 00:24:31 client requested option code 160
Dec 23 00:24:31 client requested option `boot-server' code 66
Dec 23 00:24:31 client requested option `vendor-encap-options' code 43
Dec 23 00:24:31 client requested option code 128
Dec 23 00:24:31 client requested option code 144
Dec 23 00:24:31 client requested option code 157
Dec 23 00:24:31 client requested option code 191
Dec 23 00:24:31 found option `subnet-mask' code 1 in `Binding' scope 0x57fc00
Dec 23 00:24:31 serving option `subnet-mask' code 1 to client
Dec 23 00:24:31 skipping option code 2, not found in scope
Dec 23 00:24:31 found option `router' code 3 in `Pool' scope 0x576000
Dec 23 00:24:31 serving option `router' code 3 to client
Dec 23 00:24:31 skipping option code 4, not found in scope
Dec 23 00:24:31 found option `name-server' code 6 in `Pool' scope 0x576000
Dec 23 00:24:31 serving option `name-server' code 6 to client
Dec 23 00:24:31 found option `domain-name' code 15 in `Pool' scope 0x576000
Dec 23 00:24:31 serving option `domain-name' code 15 to client
Dec 23 00:24:31 skipping option code 42, not found in scope
Dec 23 00:24:31 skipping option code 43, not found in scope
Dec 23 00:24:31 skipping option code 54, not found in scope
Dec 23 00:24:31 found option `boot-server' code 66 in `Pool' scope 0x576000
Dec 23 00:24:31 serving option `boot-server' code 66 to client
Dec 23 00:24:31 skipping option code 125, not found in scope
Dec 23 00:24:31 skipping option code 128, not found in scope
Dec 23 00:24:31 skipping option code 144, not found in scope
Dec 23 00:24:31 skipping option code 157, not found in scope
Dec 23 00:24:31 found option `<dynamic>' code 160 in `Pool' scope 0x576000
Dec 23 00:24:31 serving option `<dynamic>' code 160 to client
Dec 23 00:24:31 skipping option code 191, not found in scope
Dec 23 00:24:31 Packing 82 bytes of options
Dec 23 00:24:31 packing option `dhcp-message-type' code 53 with 1 bytes of data
Dec 23 00:24:31 packing option `server-identifier' code 54 with 4 bytes of data
Dec 23 00:24:31 packing option `dhcp-lease-time' code 51 with 4 bytes of data
Dec 23 00:24:31 packing option `subnet-mask' code 1 with 4 bytes of data
Dec 23 00:24:31 packing option `router' code 3 with 4 bytes of data
Dec 23 00:24:31 packing option `name-server' code 6 with 8 bytes of data
Dec 23 00:24:31 packing option `domain-name' code 15 with 6 bytes of data
Dec 23 00:24:31 packing option `boot-server' code 66 with 13 bytes of data
Dec 23 00:24:31 packing option `<dynamic>' code 160 with 20 bytes of data
Dec 23 00:24:31 link/encap does not support media based routes, broadcasting the response
Dec 23 00:24:31 sendmsg() from 0.0.0.0 to port 68 at 255.255.255.255 via routing instance default sucess
Dec 23 00:24:31 sent packet from 0.0.0.0 to 255.255.255.255 port 68 out interface vlan.110 routing instance default
Dec 23 00:24:31 ==> DHCPOFFER [done]
Dec 23 00:24:31 RELEASE LEASE [0x580500:2]: `00:04:f2:xx:xx:xx' (dhcpd_protocol_dhcp.c:415)
Dec 23 00:24:31 <== DHCPDISCOVER [done]
Dec 23 00:24:31 .. Walking leases on entry 0x5527c0
Dec 23 00:24:51 REFERENCE LEASE [0x580500:2]: `00:04:f2:xx:xx:xx' (dhcpd_lease.c:1123)
Dec 23 00:24:51 .... Walking lease 0x580500
Dec 23 00:24:51 RELEASE LEASE [0x580500:2]: `00:04:f2:xx:xx:xx' (dhcpd_lease.c:1129)

Message 3 of 5
urchin8
Occasional Visitor

Re: IP6000 - Failed to get boot parameters via DHCP

Uhhhhh.... wow... As a last resort I set it to 10mbit full duplex and it magically worked.  I had tried hardcoding to 100 full before and it did not work.  Guess there is some incompatibility between the SRX and Polycom autonegotiation.  Happy to look deeper into it if there is a need... For now I'll just leave it at 10mbit I guess!  

View solution in original post

Message 4 of 5
SteffenBaierUK
Polycom Employee & Community Manager

Re: IP6000 - Failed to get boot parameters via DHCP

Hello Hello urchin8,

unsure why you obscure your MAC address.

 

You would need to run a currently supported software version like UC Software 4.0.11 and the BootROM aka updater 5.0.11

 

We would need logs of this but without an IP address the phone cannot upload these.

 

I suggest you raise a ticket.

 

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

If this is some sort of an Internet discounter please post your phone's MAC address so I can look up who would be able to support you.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. My official "day" Job is 3rd Level support at Poly but I am unable to provide official support via the community.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 5 of 5