show critmon context
To display information about the context for the wd-critical-mon process, use the show critmon context command in EXEC mode.
show critmon context {all | deadline [client client-name] | ticker | watcher} location {node-id | all}
Syntax Description
all |
Displays all context information for the wd-critical-mon process. |
deadline |
Displays the context information for the deadline monitoring client application. |
client |
(Optional) Displays information only for the specified client. |
client-name |
Name of the client. |
ticker |
Displays information for the ticker context for the wd-critical-mon process. |
watcher |
Displays information for the watcher context for the wd-critical-mon process. |
location |
Specifies a node to filter. |
node-id |
Node ID. The node-id argument is entered in the rack/slot/module notation. |
all |
Specifies all locations. |
Command Default
No default behavior or values
Command Modes
EXEC mode
Command History
Release |
Modification |
---|---|
Release 3.6.0 |
This command was introduced. |
Usage Guidelines
Use the show critmon context command to display information about the context for the wd-critical-mon process.
Task ID
Task ID |
Operations |
---|---|
cisco-support |
read |
Examples
The following sample output is from the show critmon context command:
RP/0/RP0/CPU0:router# show critmon context all location all
------------------------------------------------------------------------------
Ticker context info (Node: 0/5/CPU0)
------------------------------------------------------------------------------
CPU# : 0
Ticker counter : 2245
Ticker last ran timestamp : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Watcher context info (Node: 0/5/CPU0)
------------------------------------------------------------------------------
Watcher counter : 751
Watcher last ran : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Deadline monitoring context info (Node: 0/5/CPU0)
------------------------------------------------------------------------------
Client : wdsysmon
PunchTimestamp : 02/10/2008 01:11:09
PunchCounter : 226
------------------------------------------------------------------------------
Ticker context info (Node: 0/4/CPU0)
------------------------------------------------------------------------------
CPU# : 0
Ticker counter : 74
Ticker last ran timestamp : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Watcher context info (Node: 0/4/CPU0)
------------------------------------------------------------------------------
Watcher counter : 24
Watcher last ran : 02/10/2008 01:11:09
------------------------------------------------------------------------------
Deadline monitoring context info (Node: 0/4/CPU0)
------------------------------------------------------------------------------
Client : wdsysmon
PunchTimestamp : 02/10/2008 01:11:10
PunchCounter : 8
------------------------------------------------------------------------------
Ticker context info (Node: 0/2/CPU0)
------------------------------------------------------------------------------
CPU# : 0
Ticker counter : 61
Ticker last ran timestamp : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Watcher context info (Node: 0/2/CPU0)
------------------------------------------------------------------------------
Watcher counter : 21
Watcher last ran : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Deadline monitoring context info (Node: 0/2/CPU0)
------------------------------------------------------------------------------
Client : wdsysmon
PunchTimestamp : 02/10/2008 01:11:09
PunchCounter : 6
------------------------------------------------------------------------------
Ticker context info (Node: 0/1/CPU0)
------------------------------------------------------------------------------
CPU# : 0
Ticker counter : 2093
Ticker last ran timestamp : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Watcher context info (Node: 0/1/CPU0)
------------------------------------------------------------------------------
Watcher counter : 703
Watcher last ran : 02/10/2008 01:11:10
------------------------------------------------------------------------------
Deadline monitoring context info (Node: 0/1/CPU0)
------------------------------------------------------------------------------
Client : wdsysmon
PunchTimestamp : 02/10/2008 01:11:09
PunchCounter : 211
This table describes the significant fields shown in the display.
Field |
Description |
---|---|
Ticker context info |
wd-critical-mon process ticker context information for the node. |
CPU |
CPU number. |
Ticker counter |
Current counter for the wd-critical-mon ticker thread. The ticker counter field specifies the number of times the ticker thread was run. |
Ticker last ran timestamp |
Timestamp for the last time the wd-critical-mon ticker thread was run. |
Watcher context info |
wd-critical-mon watcher thread context information that is used for the node. |
Watcher counter |
Current counter for the wd-critical-mon watcher thread. The watcher counter field specifies the number of times the watcher thread was run |
Watcher last ran |
Timestamp that is used for the last run of the wd-critical-mon watcher thread. |
Deadline monitoring context info |
wd-critical-mon deadline monitoring information that is used for the node. |
Client |
Client name for deadline monitoring. |
PunchTimestamp |
Timestamp that is used for the last run of the client application. |
PunchCounter |
Current counter for the deadline monitoring client. This field specifies the number of times that the client application can punch the counter. |