279
The following matrix shows the subslot subslot-number option and hardware compatibility:
MSR954 (JH296A/JH297A/JH298A/JH299A/JH373A) No
MSR958 (JH300A/JH301A) No
MSR1002-4/1003-8S No
MSR2003 No
MSR2004-24/2004-48 No
MSR3012/3024/3044/3064 No
MSR4060/4080 Yes
Usage guidelines
You can configure a series of actions to be executed in response to the event specified in a monitor
policy. If two actions have the same ID, the most recent one takes effect.
EAA executes the actions in ascending order of action IDs. When you add actions to a policy, you
must make sure the execution order is correct.
The reboot action configured with this command reboots devices or cards without saving the running
configuration. If you want to save the running configuration, use the action cli command to configure
reboot actions.
When you define an action, you can specify a value or specify a variable name for an argument. For
more information about using EAA environment variables, see "rtm environment."
Examples
# (Distributed devices in standalone mode/centralized devices in standalone mode.) Configure an
action for the CLI-defined policy test to reboot the device.
<Sysname> system-view
[Sysname] rtm cli-policy test
[Sysname-rtm-test] action 3 reboot
# (Centralized devices in IRF mode.) Configure an action for the CLI-defined policy test to reboot
IRF member device 1.
<Sysname> system-view
[Sysname] rtm cli-policy test
[Sysname-rtm-test] action 3 reboot slot 1
# (Distributed devices in IRF mode.) Configure an action for the CLI-defined policy test to reboot IRF
member device 1.
<Sysname> system-view
[Sysname] rtm cli-policy test
[Sysname-rtm-test] action 3 reboot chassis 1
action switchover
Use action switchover to add an active/standby switchover action to a monitor policy.
Use undo action to remove an action.
Syntax
action number switchover
undo action number
To Next Page
Loading...
Need help?
General
