Table of Contents
Advertisement
Configuring and Managing Embedded Event Manager Policies
Display Available Policies: Example
This is the sample output from the show event manager policy available command displaying available
policies:
RP/0/RSP0/CPU0:router# show event manager policy available
No.
1
2
3
4
5
Display Embedded Event Manager Process: Example
Reliability metric data is kept for each process handled by the System Manager. This data includes standby
processes running on either the primary or backup hardware card. Data is recorded in a table indexed by
hardware card disk ID plus process pathname plus process instance for those processes that have multiple
instances. This is the sample output from the show event manager metric process command displaying
reliability metric data:
RP/0/RSP0/CPU0:router# show event manager metric process all location 0/1/CPU0
=====================================
job id: 78, node name: 0/1/CPU0
process name: wd-critical-mon, instance: 1
--------------------------------
last event type: process start
recent start time: Mon Sep 10 21:36:49 2007
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: 0
most recent 10 process start times:
--------------------------
Mon Sep 10 21:36:49 2007
--------------------------
most recent 10 process end times and types:
cumulative process available time: 59 hours 33 minutes 42 seconds 638 milliseconds
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): 0
=====================================
job id: 56, node name: 0/1/CPU0
process name: dllmgr, instance: 1
--------------------------------
last event type: process start
recent start time: Mon Sep 10 21:36:49 2007
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: 0
most recent 10 process start times:
--------------------------
Mon Sep 10 21:36:49 2007
--------------------------
Type
Time Created
system
Mon Mar 15 21:32:14 2004
system
Mon Mar 15 21:32:14 2004
system
Mon Mar 15 21:32:16 2004
system
Mon Mar 15 21:32:16 2004
system
Mon Mar 15 21:32:16 2004
1.000000000
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
Display Available Policies: Example
Name
periodic_diag_cmds.tcl
periodic_proc_avail.tcl
periodic_sh_log.tcl
tm_cli_cmd.tcl
tm_crash_hist.tcl
81
Advertisement
Table of Contents
