Hi,
I am currently trying to get a better understanding of DCBX and therefore connected a CNA to my N5k.
There the problems start:
1. It looks like there is a bug in the NX-OS 4.1(3)N2(1) because the commands show lldp interface ethernet x/y and show lldp neighbours
show the same output.
nex5010-lct(config-if)# show lldp neighbors
LLDP Neighbors
Remote Peers Information on interface Eth2/1
Remote peer's MSAP: length 7 Bytes:
00 00 c9 93 2d c3 32
LLDP TLV's
LLDP TLV type:Chassis ID LLDP TLV Length: 7
LLDP TLV type:Port ID LLDP TLV Length: 2
LLDP TLV type:Time to Live LLDP TLV Length: 2
LLDP TLV type:Port Description LLDP TLV Length: 8
LLDP TLV type:System Name LLDP TLV Length: 29
LLDP TLV type:System Description LLDP TLV Length: 45
LLDP TLV type:System capabilities LLDP TLV Length: 4
LLDP TLV type:LLDP Organizationally Specific LLDP TLV Length: 60
LLDP TLV type:END of LLDPDU LLDP TLV Length: 0
nex5010-lct(config-if)# show lldp interface ethernet 2/1
tx_enabled: TRUE
rx_enabled: TRUE
dcbx_enabled: TRUE
Port MAC address: 00:0d:ec:e6:31:b0
Remote Peers Information
Remote peer's MSAP: length 7 Bytes:
00 00 c9 93 2d c3 32
LLDP TLV's
LLDP TLV type:Chassis ID LLDP TLV Length: 7
LLDP TLV type:Port ID LLDP TLV Length: 2
LLDP TLV type:Time to Live LLDP TLV Length: 2
LLDP TLV type:Port Description LLDP TLV Length: 8
LLDP TLV type:System Name LLDP TLV Length: 29
LLDP TLV type:System Description LLDP TLV Length: 45
LLDP TLV type:System capabilities LLDP TLV Length: 4
LLDP TLV type:LLDP Organizationally Specific LLDP TLV Length: 60
LLDP TLV type:END of LLDPDU LLDP TLV Length: 0
I was expecting a detailed output like it is available in IOS for LLDP.
Is this a known bug?
2. I tried to workarounf this problem by simply capturing some LLDP packets but there I came to the second problem.
Wireshark is currently not capable of interpreting organization specific TLV type 127.
So does anyone know if there is a workaround on this?
Thanks!
