Cisco N5K-C5010P-BF Troubleshooting Guide - Page 10
show cores, process log, show processes log details, copy core, PID ftp, show version - image
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 10 highlights
Troubleshooting Basics Chapter 1 Troubleshooting Overview Send document comments to [email protected]. Service: clis hap reset Version: 4.2(1)N2(1) 2) At 841383 usecs after Sat Nov 6 14:56:25 2010 Reason: Reset triggered due to HA policy of Reset Service: clis hap reset Version: 4.2(1)N2(1) • Use the show cores command to determine if a core file was recorded. You also can use the show process log command to display the processes and if a core was created. switch#show process log Process PID clis 4023 clis 4155 Normal-exit ----------- N N Stack ----- Y Y Core ----- Y N Log-create-time Sat Nov 6 15:14:53 2010 Sat Nov 6 14:56:18 2010 • Use the show processes log details command to provide useful information about the reason for the crash: switch# show processes log details Service: clis Description: CLI Server Started at Sat Nov 6 14:59:10 2010 (882984 us) Stopped at Sat Nov 6 15:14:53 2010 (614588 us) Uptime: 15 minutes 43 seconds Start type: SRV_OPTION_RESTART_STATELESS (23) Death reason: SYSMGR_DEATH_REASON_FAILURE_SIGNAL (2) Last heartbeat 9.35 secs ago RLIMIT_AS: 687474867 System image name: n5000-uk9.4.2.1.N2.1.bin System image version: 4.2(1)N2(1) S0 PID: 4023 Exit code: signal 11 (core dumped) Threads: 4026 4024 4025 • Note the module-number and the PID number in the output of the show cores command for the process that crashed. (Usually the module number is 1 for a Nexus 5000 switch.) switch#show cores Module-num Instance-num ---------- ------------ 1 1 Process-name -----------clis PID --4023 Core-create-time Nov 6 15:20 • Use the copy core://module-id/PID ftp: command to export the file and contact the TAC to obtain an analysis of the file. • Obtain the timestamp of the crash with the show version, show system reset-reason, or show cores commands. With the show logging command, review the events that happened just before the crash. switch# show logging [snip] 2010 Nov 6 08:00:50 TTPSW-5020SF1 %$ VDC-1 %$ %STP-2-BLOCK_BPDUGUARD: Received BPDU on port Ethernet103/1/1 with BPDU Guard enabled. Disabling port. 2010 Nov 6 08:00:51 TTPSW-5020SF1 %$ VDC-1 %$ %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet103/1/1 is down (Error disabled. Reason:BPDUGuard) 2010 Nov 6 14:56:18 TTPSW-5020SF1 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "clis" (PID 4155) hasn't caught signal 11 (core will be saved). Cisco Nexus 5000 Series Troubleshooting Guide 1-2 OL-25300-01