cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
967
Views
0
Helpful
3
Replies

Periodic CPU high on Nexus 7010

k.ramalingam
Level 1
Level 1

Hi Experts,

There are times the Nexus CPU goes high around 70% but its not a constant occurance. Is there something to worry. Quite hard to find out which process caused it as it happens very brief.

The version of Nexus OS

HDC-CS-L01-01# sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php

Software
  BIOS:      version 3.17.0
  loader:    version N/A
  kickstart: version 4.2(2a)
  system:    version 4.2(2a)
  BIOS compile time:       03/23/08
  kickstart image file is: bootflash:/n7000-s1-kickstart.4.2.2a.bin
  kickstart compile time:  9/25/2009 9:00:00 [09/28/2009 06:06:24]
  system image file is:    bootflash:/n7000-s1-dk9.4.2.2a.bin
  system compile time:     9/25/2009 9:00:00 [09/28/2009 06:35:38]


Hardware
  cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")
  Intel(R) Xeon(R) CPU         with 4135852 kB of memory.
  Processor Board ID JAF1408AELS

  Device name: HDC-CS-L01-01
  bootflash:    2000880 kB
  slot0:              0 kB (expansion flash)

Kernel uptime is 30 day(s), 15 hour(s), 32 minute(s), 33 second(s)

Last reset
  Reason: Unknown
  System version: 4.2(2a)
  Service:

plugin
  Core Plugin, Ethernet Plugin

CMP (Module 6) ok
CMP Software
  CMP BIOS version:        02.01.05
  CMP Image version:       4.2(1) [build 4.2(1)]
  CMP BIOS compile time:   8/ 4/2008 19:39:40
  CMP Image compile time:  1/5/2010 1:00:00

CMP (Module 5) ok
CMP Software
  CMP BIOS version:        02.01.05
  CMP Image version:       4.2(1) [build 4.2(1)]
  CMP BIOS compile time:   7/13/2008 19:44:27
  CMP Image compile time:  9/25/2009 9:00:00

Thanks

3 Replies 3

Tharak Abraham
Level 3
Level 3

Ram,

Need more outputs like "sh process" et al to see whats hogging your CPU.

Only issue is every time we login to check the cpu after receiving the alert, the cpu is back at 2%.

The best way is to open a TAC case for these issues if its in production.

If not we have to enable logging and enable cpu-queue debugs and tshoot (not recommended in production)

"sh process mem" can help sometimes;

I dont remember if NX-OS shows "sh cpu history" with corresponding PID mapped against the spiked CPU ?

Review Cisco Networking products for a $25 gift card