Cisco ASR 9000 Serie

ExampleDescriptionEnvironment Variable
http://www.example.com/fm/interface_tm.cgiURL location to which the crash
report is sent.
_crash_reporter_url
This table describes the EEM environment variables that must be set before the tm_fsys_usage.tcl sample
policy is run.
Table 16: Environment Variables Used in the tm_fsys_usage.tcl Policy
ExampleDescriptionEnvironment Variable
0-59/1 0-23/1 * * 0-7CRON specification that is used in
the event_register Tcl command
extension. If unspecified, the
tm_fsys_usage.tcl policy is
triggered once per minute. This
variable is optional and need not
be specified.
_tm_fsys_usage_cron
1When this variable is set to a value
of 1, disk usage information is
displayed for all entries in the
system. This variable is optional
and need not be specified.
_tm_fsys_usage_debug
disk2:98000000Free byte threshold for systems or
specific prefixes. If free space falls
below a given value, a warning is
displayed. This variable is optional
and need not be specified.
_tm_fsys_usage_freebytes
nvram:25
disk2:5
Disk usage percentage thresholds
for systems or specific prefixes. If
the disk usage percentage exceeds
a given percentage, a warning is
displayed. If unspecified, the
default disk usage percentage is 80
percent for all systems. This
variable is optional and need not
be specified.
_tm_fsys_usage_percent
Registration of Some EEM Policies
Some EEM policies must be unregistered and then reregistered if an EEM environment variable is modified
after the policy is registered. The event_register_ xxx statement that appears at the start of the policy contains
some of the EEM environment variables, and this statement is used to establish the conditions under which
the policy is run. If the environment variables are modified after the policy has been registered, the conditions
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
84
Configuring and Managing Embedded Event Manager Policies
EEM Event Detector Demo: Example