Cisco ASR 9000 Serie Configuration Manuals page 120

Embedded Event Manager Event Registration Tcl Command Extensions
node
queue_priority
maxrun
nice
tag
If an optional argument is not specified, the event matches all possible values of the argument. If multiple
arguments are specified, the process event will be raised when all the conditions are matched.
Result String
None
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
104
Configuring and Managing Embedded Event Manager Policies
(Optional) The node name is a string that consists of
the word "node" followed by two fields separated by
a slash (/), using the following format:
node<slot-number>/<cpu-number>
The slot-number is the hardware slot number. The
cpu-number is the hardware CPU number. For
example, the SP CPU in a Supervisor card on a Cisco
Catalyst 6500 series switch located in slot 0 would
be specified as node0/0. The RP CPU in a Supervisor
card on a Cisco Catalyst 6500 series switch located
in slot 0 would be addressed as node0/1. If the node
argument is not specified, the default node
specification is always the regular expression pattern
match of * representing all applicable nodes.
(Optional) Priority level at which the script will be
queued; normal priority is greater than low priority
but less than high priority. The priority here is not
execution priority, but queuing priority. If this
argument is not specified, the default priority is
normal.
(Optional) Maximum run time of the script (specified
in SSSSSSSSSS[.MMM] format, where SSSSSSSSSS
must be an integer representing seconds between 0
and 4294967295, inclusive, and where MMM must
be an integer representing milliseconds between 0
and 999). If this argument is not specified, the default
20-second run-time limit is used.
(Optional) Policy run-time priority setting. When the
nice argument is set to 1, the policy is run at a
run-time priority that is less than the default priority.
The default value is 0.
Tag is acceptable but ignored. Cisco IOS EEM scripts
with the tag option can run in an Cisco IOS XR
software environment without any error. Since
Cisco IOS XR software does not support multiple
events, the tag has no effect.