223
Step Command Remarks
4. Configure the actions
to take when the event
occurs.
• Configure the action to execute a
command:
action number cli command-line
• Configure a reboot action (MSR
2600/MSR 3600):
action number reboot [ subslot
subslot-number ]
• Configure a reboot action (MSR 5600):
action number reboot [ slot slot-number
[ subslot subslot-number ] ]
• Configure a logging action:
action syslog priority level facility
local-number msg msg-body
• Configure an active/standby switchover
action:
action number switchover
By default, a monitor
policy does not
contain any actions.
Repeat this step to
add up to 232 actions
to the policy.
You can reference a variable
name in the $variable_name
format instead of specifying a
specific value for an argument
when you define an action.
5. (Optional.) Assign a
user role to the policy.
user-role role-name
By default, a monitor
policy contains user
roles that its creator
had at the time of
policy creation.
A monitor policy supports up to
64 valid user roles. User roles
added after this limit is reached
do not take effect.
6. (Optional.) Configure
the maximum policy
runtime.
running-time time
The default runtime is 20
seconds.
7. Enable the policy.
commit
By default,
CLI-defined policies
are not enabled.
A CLI-defined policy can take
effect only after you perform this
step.
Configuring a monitor policy by using Tcl
Step Command Remarks
1. Edit a Tcl script file
(see Table 31).
N/A The supported Tcl version is 8.5.8.
2. Download the file to
the device by using
FTP or TFTP.
N/A
For more information about using FTP and
TFTP, see Fundamentals Configuration
Guide.
3. Enter system view.
system-view
N/A
