Cisco N5K-C5010P-BF Troubleshooting Guide - Page 10

show cores, process log, show processes log details, copy core, PID ftp, show version - image

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

Send document comments to [email protected].
1-2
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 1
Troubleshooting Overview
Troubleshooting Basics
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
Normal-exit
Stack
Core
Log-create-time
---------------
------
-----------
-----
-----
---------------
clis
4023
N
Y
Y
Sat Nov
6 15:14:53 2010
clis
4155
N
Y
N
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
Process-name
PID
Core-create-time
----------
------------
------------
---
----------------
1
1
clis
4023
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).