Process Monitoring Commands; Monitoring Cpu Usage And Using Syslog Messages - 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

Chapter 8
Process Monitoring and Troubleshooting
recent start time: Wed Jul
recent normal end time: n/a
recent abnormal end time: n/a
number of times started: 1
number of times ended normally: 0
number of times ended abnormally: 2
most recent 10 process start times:
--------------------------
Wed Jul
--------------------------
most recent 10 process end times and types:
cumulative process available time: 162 hours 20 minutes 51 seconds 452 milliseco
nds
cumulative process unavailable time: 0 hours 0 minutes 0 seconds 0 milliseconds
process availability:
number of abnormal ends within the past 60 minutes (since reload): 0
number of abnormal ends within the past 24 hours (since reload): 0
number of abnormal ends within the past 30 days (since reload): 2
The vital system processes are: qnet, gsp, qsm, redcon, netio, ifmgr, fgid_aggregator, fgid_server,
fgid_allocator,fsdb_server, fsdb_aserver, fabricq_mgr, fia_driver, shelfmgr, and lrd on the RP and
fabricq_mgr, ingressq, egressq, pse_driver, fia_driver, cpuctrl, and pla_server on the line card.
It is also important to regularly check if critical or vital processes are in a blocked state. See the
processes blocked Command" section on page 8-178
blocked state.

Process Monitoring Commands

Use the following commands to monitor processes:
You can also use the monitor processes and monitor threads commands to determine the top processes
and threads based on CPU usage.
Tip
The top processes command displays almost real-time CPU and memory utilization, and updates several
times per minute. The show processes cpu command displays data that has been collected for all process
IDs over the past one, five and 15 minute intervals. Both methods provide valuable information.

Monitoring CPU Usage and Using Syslog Messages

Wdsysmon continuously monitors the system to ensure that no high priority thread is waiting and
provides a procedure to recover from high-priority CPU usage. When a process is determined to be a
CPU-hog, it is terminated and a coredump of the process is captured and stored on the configured device
(exception choice) to aid debugging. For information on troubleshooting high CPU usage, see the
"Troubleshooting High CPU Utilization and Process Timeouts" section on page
OL-21483-02
5 15:17:48 2006
1.000000000
top command—Displays real-time CPU usage statistics on the system. See the
section on page
1-10.
show processes pidin command—Displays raw output of all processes, including their state.
show processes blocked command—Displays details about reply, send, and mutex blocked
processes. See the
"show processes blocked Command" section on page 8-178
5 15:17:48 2006
for information on checking if processes are in the
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
Monitoring CPU Usage and Using Syslog Messages
"top Command"
8-185.
"show
8-183

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents