I am having some weird events coming up when I telnet into 1234P switches. I have multiple Polycom phones hanging off these switches. I am currently running Firmware release R10.5.1 Below is the error I am receiving. Has anyone else had this trouble or is it nothing I should worry with? I get these on every switch I have and every port a polycom is plugged into. I have attempted to change the port on the switch to match the error it is giving me but then it just changes the error.
2000.03.22 02:33:44 LLDP LLDP: Speed Duplex mis-match on swx 0/2. Speed/Duplex: "100M/full-duplex" Neighbor Speed/Duplex: "10M/full-duplex"
2000.03.22 02:33:55 LLDP LLDP: Speed Duplex mis-match on swx 0/24. Speed/Duplex: "100M/full-duplex" Neighbor Speed/Duplex: "10M/full-duplex"
2000.03.22 02:34:14 LLDP LLDP: Speed Duplex mis-match on swx 0/2. Speed/Duplex: "100M/full-duplex" Neighbor Speed/Duplex: "10M/full-duplex"
2000.03.22 02:34:25 LLDP LLDP: Speed Duplex mis-match on swx 0/24. Speed/Duplex: "100M/full-duplex" Neighbor Speed/Duplex: "10M/full-duplex"
2000.03.22 02:34:44 LLDP LLDP: Speed Duplex mis-match on swx 0/2. Speed/Duplex: "100M/full-duplex" Neighbor Speed/Duplex: "10M/full-duplex"
Thanks again
We have seen this as well. It's a cosmetic bug, and the phones are properly negotiating 100 full. It's annoying but harmless. The command "no events" will allow you to see what you're typing on the CLI by suppressing the output.
We have seen this as well. It's a cosmetic bug, and the phones are properly negotiating 100 full. It's annoying but harmless. The command "no events" will allow you to see what you're typing on the CLI by suppressing the output.
I'm curious what model Polycom phones, and what version of firmwares (BootROM/Firmware) - I'd like to report the problem with Polycom, if it's a current issue on supported phones.
These range from Soundpoint Ip330s- 750s all are Soundpoint IP phones. The firmware running on them is 4.0.3.7562. These are hosted phones that the config is managed by our SIP provider.
I recently ran into this as well with the same switch and phones. I just went to each individual phones menu and disabled the lldp setting and it fixed it at one location. Before I had a chance to do that step at the main location it corrected itself when I went to phone version 4.0.4 from version 4.0.3.
I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post to unmark it and select another in its place with the applicable buttons. If you have any additional information on this that others may benefit from, please come back to this post to provide an update. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.
Thanks,
Noor
We have this also either turn off LLDP on the switch port or each Polycom phone has a setting to also turn off LLDP just below the VLAN tag ... hope this helps!
pjones0033
brentm is correct that this issue has already been resolved by Polycom. The fix for this software issue is in the UC 4.0.4 Polycom software release. Here is the excerpt from the release notes.
82914/79065 The phones now report correct LAN port mode in LLDP Operational MAU Type.
Thanks,
Charles
As an update, in R10.11.0 AOS, a switchport command was added that allows an AOS switch the ability to ignore these LLDP speed-duplex mismatch messages. If you add the command "no lldp receive 802.3-info mac-phy-config" to any applicable switchports, the switch will no longer log every LLDP update indicating a mismatch as an event in the event-history.