High CPU Usage per Chassis and Blade for Cisco Nexus

Vendor

Cisco

Description

Indeni will alert when CPU usage per chassis and blade is high.

Remediation Steps

Determine the cause for the high CPU usage of the listed CPUs.

1. Run the "show processes cpu" NX-OS command in order to show the CPU usage at the process level

2. Use the "show processes cpu history" command to display the CPU usage for the last 60 seconds, 60 minutes, and 72 hours. Be sure to check the average CPU usage (#) and the spikes (*).

3. A quick way to determine the cause of high CPU usage is to use the "show system internal processes cpu" NX-OS command. This command was added in Release 6.2 and displays the CPU usage information for all threads that belong to a specific PID. Mostly likely, high CPU usage triggered by traffic would cause Netstack, as well as other features and processes such as Address Resolution Protocol (ARP) and Internet Group Management Protocol (IGMP), to run high.

4. Review the logs for relevant findings.

5. For more information please review: High CPU Troubleshooting Guide.

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show system resources" command. The output includes a table with the device's CPU (per core) utilization statistics and memory information (total, used and free).

Why is this important?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show system resources" command. The output includes a table with the device's CPU (per core) utilization statistics and memory information (total, used and free).

Without Indeni how would you find this?

It is possible to poll this data through SNMP.


View Source Code