cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

141
Views
0
Helpful
2
Replies
Highlighted
Beginner

High CPU Usage Cisco Nexus3064

Hi!

I'm facing a strange problem in my nexus switch.

The CPU is always at 90% usage, even without any traffic. 

The current traffic now is 1.6GB and cpu 90%.

 

 

show system resources
Load average: 1 minute: 3.23 5 minutes: 3.11 15 minutes: 3.00
Processes : 375 total, 5 running
CPU states : 36.5% user, 52.5% kernel, 11.0% idle
CPU0 states : 30.0% user, 60.0% kernel, 10.0% idle
CPU1 states : 43.0% user, 45.0% kernel, 12.0% idle
Memory usage: 3785228K total, 2171868K used, 1613360K free

 

 

sh processes cpu sort | ex 0.0

PID Runtime(ms) Invoked uSecs 1Sec Process
----- ----------- -------- ----- ------ -----------
3296 1178788837 2147483647 453 9.7% bcm_usd
3612 1329672163 2147483647 359 9.2% ntpd
3261 1546168315 2013682339 767 7.8% syslogd
3486 429 3577 119 3.4% netstack
7 73945828 2147483647 31 0.9% ksoftirqd/1

CPU util : 34.0% user, 64.0% kernel, 2.0% idle

 

 Software
BIOS: version 4.0.0
loader: version N/A
kickstart: version 6.0(2)U3(8)
system: version 6.0(2)U3(8)
Power Sequencer Firmware:
Module 1: version v4.1
BIOS compile time: 12/06/2016
kickstart image file is: bootflash:///n3000-uk9-kickstart.6.0.2.U3.8.bin
kickstart compile time: 4/15/2015 22:00:00 [04/16/2015 05:57:00]
system image file is: bootflash:///n3000-uk9.6.0.2.U3.8.bin
system compile time: 4/15/2015 22:00:00 [04/16/2015 07:18:23]

 

 

2 REPLIES 2
VIP Expert

Re: High CPU Usage Cisco Nexus3064

Hi,

It appears that none of the processes are running that high (according to "sh processes cpu sort | ex 0.0") you posted.  So, something else is eating up all the CPUs. I could not find a bug associated with this but you may want to open a ticket with TAC as this may be a known bug to them.

HTH

VIP Advisor

Re: High CPU Usage Cisco Nexus3064

bcm_usd process there was one bug CSCuh79034 which affected 5.0(3)U5(1d) release however this should be fixed with your current 6.0(2).XX

 

Opening the TAC case will be your best option if this is effecting production environment..

BB
*** Rate All Helpful Responses ***
CreatePlease to create content
Content for Community-Ad