8-181
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
OL-21483-02
Chapter 8 Process Monitoring and Troubleshooting
Process States
The process ospf is given a Job ID of 250. This Job ID never changes on a running router. Within the
ospf process there are 7 threads, each with their own Thread ID or TID. For each thread, the stack space
for each thread, the priority of each thread, and the thread state is listed. Table 8-1 lists the thread states.
The PID is 299228. This number changes each time the process is restarted. The Respawn count
indicates how many times the process has restarted and the Process state should show the RUN state.
Synchronous Message Passing
The message passing life cycle is as follows:
1. A server creates a message channel.
2. A client connects to a channel of a server (analogous to posix open).
3. A client sends a message to a server (MsgSend) and waits for a reply and blocks.
4. The server receives (MsgReceive) a message from a client, processes the message and replies to the
client.
5. The client unblocks and processes the reply from the server.
This blocking client-server model is synchronous message passing. This means the client sends a
message and blocks. The server receives the message, processes it, replies back to the client, and then
the client unblocks. The specific details are as follows.
1. Server is waiting in RECEIVE state
2. Client sends a message to the server and becomes BLOCKED
3. Server receives the message and unblocks (if waiting in receive state)
4. Client moves to the REPLY state
5. Server moves to the RUNNING state
6. Server processes the message
7. Server replies to the client
8. Client unblocks
Use the show processes command to display the states the client and servers are in. Table 8-1 lists the
thread states.
Blocked Processes and Process States
Use the show processes blocked command to display the processes that are in blocked state.
Synchronized message passing enables you to track the life cycle of inter-process communication
between the different threads. At any point in time a thread can be in a specific state. A blocked state can
be a symptom of a problem. This does not mean that if a thread is in blocked state then there is a
problem—blocked threads are normal. Using the show processes blocked command is sometimes a
good way to start troubleshooting operating system-type problems. If there is a problem, for example the
CPU is high, then use the show processes blocked command to determine if anything looks abnormal
(what is not normal for your functioning router). This provides a baseline for you to use as a comparison
when troubleshooting process life cycles.
At any point in a time a thread can be in a particular state. Table 8-1 lists the thread states.
To Next Page
Loading...
Need help?
General
