Process Monitoring - Cisco CRS-1 - Carrier Routing System Router Troubleshooting Manual

Ios xr troubleshooting guide
Hide thumbs Also See for CRS-1 - Carrier Routing System Router:
Table of Contents

Advertisement

Process Monitoring

Table 8-1
If the State is:
DEAD
RUNNING
READY
STOPPED
SEND
RECEIVE
REPLY
STACK
WAITPAGE
SIGSUSPEND
SIGWAITINFO
NANOSLEEP
MUTEX
CONDVAR
JOIN
INTR
SEM
To troubleshoot a blocked process, use the procedure in the
on page
Process Monitoring
Significant events of the sysmgr are stored in /tmp/sysmgr.log. The log is a wrapping buffer and is useful
for troubleshooting. Use the show processes aborts location node-id all command or the show sysmgr
trace verbose | include PROC_ABORT command to display an overview of abnormally terminated
processes.
Because the sysmgr is already monitoring all processes on the system it is not necessarily required to
monitor vital processes by external management tools. But, you can use the show fault manager metric
process pid location node-id command to check critical processes on a regular basis (for example, twice
each day). The command output provides information including the abort behavior and the reason of the
particular process.
The following example shows OSPF critical process details. Check the number of times the process
ended abnormally and the number of abnormal ends within the past time periods.
RP/0/RP0/CPU0:router# show fault manager metric process ospf location
=====================================
job id: 269, node name: 0/RP0/CPU0
process name: ospf, instance: 1
--------------------------------
last event type: process start
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
8-182
Thread States
8-188.
Chapter 8
The Thread is:
Dead. The Kernel is waiting to release the threads resources.
Actively running on a CPU.
Not running on a CPU but is ready to run.
Suspended (SIGSTOP signal).
Waiting for a server to receive a message.
Waiting for a client to send a message.
Waiting for a server to reply to a message.
Waiting for more stack to be allocate.
Waiting for the process manager to resolve a page fault.
Waiting for a signal.
Waiting for a signal.
Sleeping for a period of time.
Waiting to acquire a mutex.
Waiting for a conditional variable to be signaled.
Waiting for the completion of another thread.
Waiting for an interrupt.
Waiting to acquire a semaphore.
"Troubleshooting a Process Block" section
Process Monitoring and Troubleshooting
OL-21483-02

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents