TX packets overrun for Cisco

Vendor

Cisco

Description

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

Remediation Steps

Packet overruns usually occur when there are too many packets being inserted into the port's memory buffer, faster than the rate at which the kernel is able to process them.

In a small number of cases, the overrun counter may be incremented because of a software defect. However, in the majority of cases, it indicates that the receiving capability of the interface was exceeded. Nothing can be done on the device that reports overruns. If possible, the rate that frames are coming should be controlled at the remote end of the connection.

1. Run the "show interface" command to review the interface overrun & underun counters and the bitrate. Consider to configure the "load-interval 30" interface sub command to improve the accuracy of the interface measurements.

2. If the number of overruns is high, the hardware should be upgraded.

In case of high bandwidth utilization:

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.

2. If the interface bitrate is too high and close to the upper bandwidth limit consider to use multiple links with the port-channel technology or upgrade the bandwidth of the link

3. Consider to implement QoS in case of high bandwidth utilization.

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?

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.

Without Indeni how would you find this?

It is possible to poll this data through SNMP.


View Source Code