8-194
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
OL-21483-02
Chapter 8 Process Monitoring and Troubleshooting
Troubleshooting High CPU Utilization and Process Timeouts
22 tcp
23 tcp
24 tcp
25 tcp
26 tcp
27 tcp
28 tcp
29 tcp
30 tcp
31 tcp
32 tcp
33 tcp
34 tcp
35 tcp
36 tcp
37 tcp
38 tcp
39 tcp
40 tcp
41 tcp
Troubleshooting a Hardware Failure
Hardware failure can have a major impact on the normal operation of CPU. If a problem is detected,
messages can be obtained from the syslog or you can get a node name from the output of the show
processes command with the blocked keyword.
Troubleshooting SNMP Timeouts
This section explains how to troubleshoot a typical SNMP timeout scenario.
The service provider typically initiates an SNMP query by means of an SNMP server in the network
operations center. When you set up an SNMP query on an SNMP server, you set the parameters of the
query, including a timer. If the timer expires before the server receives the query results, this means the
query has timed out. If the requested SNMP query involves a large amount of data from the Cisco CRS-1
(and this is generally true for SNMP queries), the Cisco CRS-1 might experience very high CPU
utilization as it searches for the data. The Cisco CRS-1 might not be able to complete the query and data
transfer before the timer on the SNMP server expires.
To correct a problem with SNMP timeouts, set the timer on the SNMP server to a higher value.
Process timeouts can also occur if communication among multiple process causes high CPU utilization.
For information about this scenario, see the “Troubleshooting Communication Among Multiple
Processes” section on page 8-194.
Troubleshooting Communication Among Multiple Processes
If communication among multiple processes is causing high CPU utilization, you must stop the request
process (for example, Simple Network Management Protocol [SNMP], Internet Control Message
Protocol [ICMP], or TCP).
To check the communication blocks among multiple processes, use the show processes command. Use
the blocked keyword (multiple times) to display details about the blocked process. Use the cpu keyword
(multiple times) to display the CPU usage for each process.