Polycom Trio 8800 DHCP

[Anonymous]

I have run into an issue with my Polycom 8800 where DHCP immediately fails on the device. I have tested various different ports, cables, tagged and untagged the port, and have not come to a solution. Last week I factory reset the device, and today I am having the same issue. I found an old polycom laying around and was able to get DHCP enabled on that specific device, but I am not having any luck with my Trio 8800. Has anyone else run into this issue?

Thanks. 

[SteffenBaierUK]

Hello @PCCAirframe,

welcome to the Polycom Community.

It is always useful to include the currently used UC Software version as issues experienced or a question asked may already be addressed in a newer release.

This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.

The above is also stated in the "Must Read First" and is the absolute minimum requirement every new post should include. .

In addition providing us with this basic information gives Polycom an idea what Software Versions are used in the field and avoids wasting time trying to troubleshoot issues which have already been addressed.

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP or UC Software Version of my Phone?
Resolution: Please check here

Posting some logs may give us an Idea?

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

[Anonymous]

We have several hundred Cisco 3850 switches, all with a very uniform configuration. When a Trio 8800 is connected directly to a switch port, it is unable to acquire an IP address via DHCP. The DHCP server never receives the incoming DHCPDISCOVER. If I plug another device into the port, it receives an IP just fine. Software on phone is 5.4.5.9658. I've enabled LLDP on switch. I've increase power on switch port to 30W. Oddly enough, if I plug the phone into a desktop Linksys LGS116P switch (with POE+), it procures an IP just fine.

In both cases, the Cisco switch ports are defined IDENTICALLY. If I default the power to 15.4W, the phone complains about having less than 13W.
The switch port has both a data VLAN and a VOICE VLAN configured.  In any case, we're not seeing traffic at the DHCP server.

[SteffenBaierUK]

Hello @Fitzie,

welcome to the Polycom Community.

Aug 24, 2015 Question:What basic network data is send and received by a Polycom phone?

Resolution: Please check this post => here <=

most likely we need to see this in support. If you copy a 000000000000.cfg on a USB Stick you should be able to get some logs.

Also please get a wireshark trace from a spanned port directly on the phone end.

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

End Customers are unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter providing your MAC address or your Polycom devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Polycom device from.

If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

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

[Anonymous]

Not sure how to copy the 000000000000.cfg file, but here are some pcaps from the switch port.

fitzcap1.pcap is the failed Polycom 8800 attempt on a 3850 switch port.  DHCPDISCOVER gets sent, but not received.

fitzcap2.pcap is an a successful Avaya phone on the same switch port.

fitzcap3a.pcap is the Polycom attached directly to a linksys switch, which is in turn connected to the 3850.  The ports are configured similarly

LLDP is enabled with CIsco defaults, as is CDP.

[Anonymous]

Did you get a solution to this? We are experiencing exactly the same with 8800's and Cisco stack.

Thanks

[Anonymous]

Ok, so we found the issue. If you use the Cisco dedicated VLAN option it does not like it. Either change the switch port config to not use the voice VLAN setting and assign the VLAN as a user port or disable VLAN discovery on the devices.

Hope this helps someone else.

Thanks

[SteffenBaierUK]

Hi

Can you paste your config?

Regards

Steffen Baier