Restricts actions automatically called by rules to predefined thresholds. Each action can be restricted by port, minimum interval or an eligible time window. For example, a reboot may be called by a rule but be cancelled because a reboot has occurred within the past 3 hours. The reboot will not execute outside the cron-time mask, if one has been set.
CLI resource: system
Uplogix system: All
LMS offerings: All
config restrict [no] <“actionName”> [“port”] [-i <#>] [-m <time>]
[no] - remove existing restrictions on this action.
port# – restrict the action only on this port.
-i – minimum interval in seconds before this action executes again.
-m – specifies when the action may execute, in cron format. For example, 6-0 restricts the specified action to occur only on Saturdays (day 6) and Sundays (day 0).
For information about using cron format, see About cron format
The jobs that can be restricted depend on what can be scheduled on the device. The following jobs are defined:
The event action inside a rule can override restrictions with an optional force flag.
This example restricts cycling power to no more than every 3 hours. The -i interval parameter is given in seconds.
[admin@UplogixLM]# config restrict powerCycle –i 10800
This example restricts rebooting port 1/4 except on weekends:
[admin@UplogixLM]# config restrict reboot port1/4 -m "* * * * 0,6"
1.1 - This command was introduced.