cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10147
Views
5
Helpful
1
Comments

 

 

Introduction

 

This document discuss about the High CPU Utilization on Nexus 5010 and related bug information.

 

Core Issue

 

High CPU Utilization on Nexus 5010

 

Resolution

 

Intermittent High CPU spikes observed under the show process CPU history is expected normal activity on Cisco Nexus 5000 switch. This brief High CPU utilization could be caused by platform processes and does not affect the normal functioning of the switch.

 

Using the show process cpu history command on a switch with little traffic would show the following:

 

switch# show processes cpu history

 

    211122112323122212111111111193211112111152112221112222122112

 

    068760965840725240962130210254094430654360576635870512734431

 

100                             #                              

 

90                             #                              

 

80                             #                              

 

70                             #                              

 

60                             #           #                  

 

50                             #           #                  

 

40          #                  #           #                  

 

30     #   ## #  #             ##          #   ##     #       

 

20 ################ ###        ####   ###  #################  #

 

10 ############################################################

 

    0....5....1....1....2....2....3....3....4....4....5....5....

 

              0    5    0    5    0    5    0    5    0    5   

 

               CPU% per second (last 60 seconds)

 

                      # = average CPU%

 

     1      1   1          1  1                     1      1   

 

    906557580987095557477660850989669699968987795968078578509685

 

    500168220197069036851800640710741407559320077351025190708567

 

100 **      *   **         *  **       **      *    *      **  

 

90 **      *** **         ** ** *  * *** **   * *  * *    ** *

 

80 **   * *******   * *   ** ****  * *** ***  * * ** * ** ** *

 

70 **   * *******   * *** ** ***** * ********** ****** ** ****

 

60 *** ** ********  * ****** ************************* ********

 

50 ************************************************************

 

40 ************************************************************

 

30 *******************************************************#****

 

20 ############################################################

 

10 ############################################################

 

    0....5....1....1....2....2....3....3....4....4....5....5....

 

              0    5    0    5    0    5    0    5    0    5   

 

               CPU% per minute (last 60 minutes)

 

              * = maximum CPU%   # = average CPU%

 

    323322422222554232222224422225225222222232333522222432225555222222222342

 

    046933526726792664338535533350361672443333087873334873290257433572422603

 

100                                                                        

 

90                                                                        

 

80                                                                        

 

70                                                                        

 

60             **                               *            **           

 

50       *     **         **    *  *            *     *    ****           

 

40   **  *     *** *      **    *  *          ***     **   ****         **

 

30 * **  * ** ******   ** **   ** ****     * *****    **  *****   **    **

 

20 ########################################################################

 

10 ########################################################################

 

    0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.

 

              0    5    0    5    0    5    0    5    0    5    0    5    0

 

                   CPU% per hour (last 72 hours)

 

                  * = maximum CPU%   # = average CPU%

 

Using the show processes cpu sort command, you might see CPU utilization spikes caused by platform processes.

 

switch# show processes cpu sort | exc 0.0

 

PID    Runtime(ms)  Invoked   uSecs  1Sec    Process

 

-----  -----------  --------  -----  ------  -----------

 

4425         2488   4460919      0   23.5%  statsclient

 

4296         2343   7178248      0   17.6%  pfma

 

4404           40  71615766      0    2.0%  gatosusd

 

CPU util  :   13.9% user,   23.8% kernel,   62.4% idle

 

switch#

 

This activity is normal for the switch and does not affect traffic because all traffic is switched by hardware ASICs and not by the CPU. Therefore intermittent high CPU observed in Nexus 5000 is expected and does not affect the normal functioning of the switch. However, the high CPU utilization could also be related to any of the following bugs.

 

Related Bug Information

 

For detailed information on the following bugs refer to Bug Toolkit

 

CSCte81951 -The command show system resources shows incorrect CPU Utilization.

 

CSCth19083 - Nexus 5000 integrated with a DCNM server, shows High CPU from the SSH process.

CSCto47633 -Nexus 5000shows high CPU in wwn_manager when FCOE is enabled.

CSCtd04122 -Nexus 5000 reports high CPU via SNMP.

 

CSCth08102 - The command show system resources shows "nan% user" instead of valid numbers

CSCtq05808 - Nexus 5000 reports high CPU utilization due to vlan manager and snmpd processes

Related Information

Cisco Nexus 5000 Troubleshooting Guide



 


 

 
 
  
Comments

Can you please tell this ?

While booting the router processor does post and during post process will the processor use its RAM?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: