These counters are documented in the IEEE 802.1AX standard as follows:
The number of frames received that either - Carry the Slow Protocols Ethernet Type value (IEEE Std 802.3 Annex 57A.4), but contain an unknown PDU, or - Are addressed to the Slow Protocols group MAC Address (IEEE Std 802.3 Annex 57A.3), but do not carry the Slow Protocols Ethernet Type.
- The number of frames received that carry the Slow Protocols Ethernet Type value (IEEE Std 802.3 Annex 57A.4), but contain a badly formed PDU or an illegal value of Protocol Subtype (IEEE Std 802.3 Annex 57A.3).
The references to Annex 57A.3 and 57A.4 of the IEEE 802.3 standard simply mean frames that are sent with a destination MAC address of 01-80-C2-00-00-02 and an Ethernet type field value of 0x8809.
The above isn't overly helpful other than to tell you that the Nexus believes there's something in the LACPDU received from the neighbour that is not as per the standard.
I think the next step would be to capture the LACPDU received from the device attached to eth125/1/9 and try to figure out what's wrong with it. You should be able to capture the LACPDU with ethanalyzer using the following:
ethanalyzer local interface inbound-hi display-filter "eth.src == xx:xx:xx:xx:xx:xx and eth.dst == 01:80:c2:00:00:02" detail
Obviously replace xx:xx:xx:xx:xx:xx with the MAC address of the link partner.
As the interface is on a FEX then presumably it's connected to a server of some sort. Do you have more than one server connected in this way and if so are they all displaying the same behaviour? What's the OS type and NIC driver version?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...