Cisco Nexus 7000 Series NX-OS Troubleshooting Guide -- Troubleshooting Tools and Methodology

2013-06-18T16:35:14Z

Using the show processes cpu Command:

← Older revision		Revision as of 16:35, 18 June 2013
(2 intermediate revisions not shown)
Line 606:		Line 606:
	*Invoked = Number of times the process has been invoked.		*Invoked = Number of times the process has been invoked.
	*uSecs = Average CPU time, in microseconds, for each process invocation.		*uSecs = Average CPU time, in microseconds, for each process invocation.
-	*~~1Sec~~ = Percentage of CPU utilization for the last one ~~second~~.	+	*5Sec = Percentage of CPU utilization for the last five seconds.
		+	*1Min = Percentage of CPU utilization for the last one minute.
		+	*5Min = Percentage of CPU utilization for the last five minutes.
		+
		+

	:switch# '''show processes cpu'''		:switch# '''show processes cpu'''
-	<~~pre~~>PID Runtime(ms) Invoked uSecs ~~1Sec~~ Process	+
-	----- ----------- -------- ----- ----- -----------	+	<PRE>
-	1 ~~2264 108252~~ 20 0 init	+	PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
-	2 ~~950 211341 4~~ 0 ~~migration/~~0	+	----- ----------- -------- ----- ------ ------ ------ --- -----------
-	3 ~~1154 32833341~~ 0 0 ~~ksoftirqd~~/0	+	1 8911 155817 57 0.00% 0.00% 0.00% - init
-	4 ~~609~~ ~~419568 1~~ 0 ~~desched~~/0	+	2 10 1164 9 0.00% 0.00% 0.00% - kthreadd
-	5 ~~758~~ ~~214253 3~~ 0 ~~migration~~/1	+	3 141 14264 9 0.00% 0.00% 0.00% - migration/0
-	6 ~~2462 155309355~~ 0 0 ~~ksoftirqd~~/1	+	4 16482 4043851 4 0.00% 0.00% 0.00% - ksoftirqd/0
-	7 ~~2496 392083 6~~ 0 ~~desched~~/1	+	5 0 10 50 0.00% 0.00% 0.00% - watchdog/0
-	8 ~~443 282990 1~~ 0 ~~events/~~0	+	6 152 19714 7 0.00% 0.00% 0.00% - migration/1
-	9 ~~578 260184 2~~ 0 ~~events~~/1	+	7 3721 835769 4 0.00% 0.00% 0.00% - ksoftirqd/1
-	10 ~~56 2681~~ 21 0 ~~khelper~~	+	8 0 2 0 0.00% 0.00% 0.00% - watchdog/1
-	15 0 30 25 0 ~~kthread~~	+	9 180 18351 9 0.00% 0.00% 0.00% - migration/2
-	24 0 2 5 0 ~~kacpid~~	+	10 5158 1301899 3 0.00% 0.00% 0.00% - ksoftirqd/2
-	~~103 81~~ 89 ~~914~~ 0 ~~kblockd/~~0	+	11 0 6 2 0.00% 0.00% 0.00% - watchdog/2
-	~~104 56~~ ~~265~~ ~~213~~ 0 ~~kblockd~~/1	+	12 127 13678 9 0.00% 0.00% 0.00% - migration/3
-	~~117~~ 0 5 17 0 ~~khubd~~	+	13 27544 6820337 4 0.00% 0.00% 0.00% - ksoftirqd/3
-	~~184~~ 0 ~~3 3~~ 0 ~~pdflush~~	+	14 0 6 2 0.00% 0.00% 0.00% - watchdog/3
-	~~185 1796~~ ~~104798~~ 17 0 ~~pdflush~~	+	15 12293 362753 33 0.00% 0.00% 0.00% - migration/4
-	~~187~~ 0 ~~2 3~~ 0 ~~aio~~/0	+	16 471881 1406804 335 0.00% 0.00% 0.00% - ksoftirqd/4
-	~~188~~ 0 2 3 0 ~~aio~~/1	+	17 0 5 2 0.00% 0.00% 0.00% - watchdog/4
-	~~189~~ 0 ~~1 3~~ 0 ~~SerrLogKthread~~	+	18 11175 330024 33 0.00% 0.00% 0.00% - migration/5
-	...</~~pre~~>	+	19 24256 508868 47 0.00% 0.00% 0.00% - ksoftirqd/5
		+	20 0 3 1 0.00% 0.00% 0.00% - watchdog/5
		+	21 12023 352503 34 0.00% 0.00% 0.00% - migration/6
		+	...
		+	</PRE>
		+
	=== Using the show system resource Command ===		=== Using the show system resource Command ===

Cisco Nexus 7000 Series NX-OS Troubleshooting Guide -- Troubleshooting Installs, Upgrades, and Reboots

2013-06-14T21:13:55Z

Recoverable System Restarts:

← Older revision		Revision as of 21:13, 14 June 2013
(2 intermediate revisions not shown)
Line 926:		Line 926:
	Stack: 128 bytes. ESP 7FFFF830, TOP 7FFFFCD0</pre>		Stack: 128 bytes. ESP 7FFFF830, TOP 7FFFFCD0</pre>

-	7. Enter the '''system cores tftp:'''<nowiki>[</nowiki>//''servername''<nowiki>][</nowiki>/''path''] command to configure the system to use TFTP to send the core dump to a TFTP server.	+
		+	7. Enter the '''system cores''' <nowiki>{[</nowiki>''tftp:''<nowiki>[</nowiki>//''servername''<nowiki>]</nowiki>/<nowiki>[</nowiki>''path''/<nowiki>] \|</nowiki> ''scp:''<nowiki>[</nowiki>//<nowiki>[</nowiki>''username@''<nowiki>]</nowiki>''server''<nowiki>][</nowiki>/''path''<nowiki>] \|</nowiki> ''sftp:''<nowiki>[</nowiki>//''[username@''<nowiki>]</nowiki>''server''<nowiki>][</nowiki>/''path''<nowiki>]]</nowiki> ''vrf ''<nowiki>{</nowiki>''vrf-name'' <nowiki>\|</nowiki> ''default'' <nowiki>\|</nowiki> ''management''<nowiki>} \|</nowiki> ''slot0:''<nowiki>[</nowiki>''path''<nowiki>]}</nowiki> command to configure the system to use TFTP to send the core dump to a TFTP server.
		+

	This command causes the system to enable the automatic copy of core files to a TFTP server. For example, the following command sends the core files to the TFTP server with the IP address 10.1.1.1:		This command causes the system to enable the automatic copy of core files to a TFTP server. For example, the following command sends the core files to the TFTP server with the IP address 10.1.1.1:
Line 941:		Line 943:
	*The maximum number of times that a process can be restarted is part of the high-availability (HA) policy for any process. (This parameter is not configurable.) If the process restarts more than the maximum number of times, the older core files are overwritten.		*The maximum number of times that a process can be restarted is part of the high-availability (HA) policy for any process. (This parameter is not configurable.) If the process restarts more than the maximum number of times, the older core files are overwritten.
	*The maximum number of core files that can be saved for any process is part of the HA policy for any process. (This parameter is not configurable, and it is set to three.)		*The maximum number of core files that can be saved for any process is part of the HA policy for any process. (This parameter is not configurable, and it is set to three.)
		+
		+	Note:
		+
		+	When using the system cores command with the scp or sftp option, you also need to generate a passwordless SSH using the following:
		+
		+	username admin keypair generate rsa force
		+	username admin keypair export bootflash:key_rsa rsa force
		+	copy bootflash:key_rsa.pub scp://<userid>@<server>/<dir>/ vrf management
		+
		+	On the specified <server>, enter the following:
		+
		+	cat key_rsa.pub >> $HOME/.ssh/authorized_keys
		+

	8. Determine the cause and resolution for the restart condition by contacting your technical support representative and asking the representative to review your core dump.		8. Determine the cause and resolution for the restart condition by contacting your technical support representative and asking the representative to review your core dump.

DocWiki - Changes related to "Cisco Nexus 7000 Series NX-OS Troubleshooting Guide -- Troubleshooting vPCs" [en]

Cisco Nexus 7000 Series NX-OS Troubleshooting Guide -- Troubleshooting Tools and Methodology

Cisco Nexus 7000 Series NX-OS Troubleshooting Guide -- Troubleshooting Installs, Upgrades, and Reboots