TX packets dropped for Cisco Nexus




Indeni tracks the number of packets that had issues and alerts if the ratio is too high.

Remediation Steps

Packet drops usually occur when the rate of packets transmitted is higher than the device ability to handle.
1. Run the "show interface" command to review the interface counters and the bitrate. Consider to configure the "load-interval 30" interface sub command to improve the accuracy of the interface measurements. Check for traffic bursts and high traffic utilization.
2. Use the "show hardware rate-limit" NX-OS command (if supported) to determine if packets are being dropped because of a rate limit.
3. Execute the "show policy-map interface control-plane" NX-OS command to determine if packets are being dropped because of a QoS policy.
4. Use the "show hardware internal statistics rates" to determine if packets are being dropped by the hardware.
5. Run the "show hardware internal statistics pktflow all" NX-OS command to display per ASIC statistics, including packets into and out of the ASIC. This command helps to identify where packet loss is occurring.

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show interface" command. The output includes all the interface related information and statistics.

Why is this important?

Capture the interface Transmitted Packets counter. Knowing the amount of bytes and packets flowing through an interface can help estimate an interface's performance and utilization.

Without Indeni how would you find this?

It is possible to poll this data through SNMP.

View Source Code