08-18-2011 08:06 AM - edited 03-16-2019 06:33 AM
Have Avaya 1220 and 1230 IP phones. Cisco 3560 power switches, current IOS. Lldp turned on globally, using network policy to assign voice vlan to the interface (nothing else is configured in the network policy for the interfaces except the voice vlan number). The phones boot up fine, they use lldp to discover the voice vlan, voice quality is good, we are in test mode and not doing any Qos.
Here is the problem on every switch where the phones are connected:
sh lldp traffic
LLDP traffic statistics:
Total frames out: 77247
Total entries aged: 7
Total frames in: 19709
Total frames received in error: 19709
Total frames discarded: 0
Total TLVs discarded: 19709
Total TLVs unrecognized: 0
The switch ports themselves report no CRC or other errors.
I did a "debug lldp error" and for each interface, every 30 seconds (advertising interval) I got: "LLDP malformed optional TLV 127 found - ignored"
Should I be concerned?
Debbi
08-22-2011 09:28 AM
Hi Debbi,
I think you may be encountering bug ID
CSCsj87991
Symptom:
A switch configured for LLDP may not correctly report the enabled capabilities
of the switch in the LLDP TLV.
Workaround:
none
Further Problem Description:
System capabilities are correctly displayed, but the enabled capabilities are
not identified if the device is configured as a Layer 2 device only.
switch>sh lldp entry *
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other
< output snipped>
System Capabilities: B,R
Enabled Capabilities:
This may cause problems with 3rd party phones that rely on this LLDP TLV to
identify the switch.
Acording to the bug it is fixed in IOS versions:-
Fixed-In
12.2(44)SE
12.2(52)EY
HTH
Alex
08-22-2011 11:04 AM
Thank you for your kind reply. I should have listed my IOS versions in my description. The two switches I am seeing this on currently are:
Cisco 3560 runnning 12.2(58)SE1 ipbase k9
Cisco 2960S running 12.2(53)SE2 universal k9
So I believe these would have the bug fix.
Debbi
08-22-2011 04:43 PM
Debbi
I have tried the bug search again and google.
I cant find a match for your errors
If it is not service affecting then ignore it.
If you are concerned then I can only advise you raise a TAC case.
HTH
Alex
10-21-2011 01:07 PM
I'm seeing the same error with Avaya phones (both H.323 and SIP), so I did a little digging. I ran a packet trace to look at the contents of the LLDP packet. The phones are sending lots of TLV 127 (Organizationally specific). Wireshare doesn't know how to decode them, and IOS is probably reportin the same thing in its traffic statistics.
What is interesting is that the Organization Unique Code that is being transmitted is 0x00400d which Lannet Data Communications. HOWEVER, 0x00040d is Avaya. I wonder if there is a mistake in the firmware on the phones.
02-06-2012 01:02 AM
I'm seeing the same errors and the phones are not getting the correct voice vlan, they are stuck in the default untagged vlan, and in the LLDP output it is showing "no vlan advertised", is this the same bug ?
11-08-2017 10:16 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide