hold-clear seconds
no hold-clear
config>vrrp>policy>priority-event>port-down
config>vrrp>policy>priority-event>lag-port-down
config>vrrp>policy>priority-event>route-unknown
Supported on all 7210 SAS platforms as described in this document
This command configures the hold clear time for the event.
The hold-clear time is used to prevent blackhole conditions when a virtual router instance advertises itself as a master before other conditions associated with the cleared event have had a chance to enter a forwarding state.
no hold-clear
Specifies the amount of time in seconds by which the effect of a cleared event on the associated virtual router instance is delayed.
hold-set seconds
no hold-set
config>vrrp>policy>priority-event>host-unreachable
config>vrrp>policy>priority-event>lag-port-down
config>vrrp>policy>priority-event>port-down
config>vrrp>policy>priority-event>route-unknown
Supported on all 7210 SAS platforms as described in this document
This command specifies the amount of time that must pass before the set state for a VRRP priority control event can transition to the cleared state to dampen flapping events. A flapping event continually transitions between clear and set.
The hold-set command is used to dampen the effect of a flapping event. The hold-set value is loaded into a hold-set timer that prevents a set event from transitioning to the cleared state until it expires.
Each time an event transitions between cleared and set, the timer is loaded and begins a countdown to zero. When the timer reaches zero, the event is allowed to enter the cleared state. Entering the cleared state is dependent on the object controlling the event, conforming to the requirements defined in the event. It is possible, on some event types, to have another set action reload the hold-set timer. This extends the amount of time that must expire before entering the cleared state.
When the hold-set timer expires and the event meets the cleared state requirements or is set to a lower threshold, the current set effect on the virtual router instances in-use priority can be removed. As with lag-port-down events, this may be a decrease in the set effect if the clearing amounts to a lower set threshold.
The hold-set command can be executed at anytime. If the hold-set timer value is configured larger than the new seconds setting, the timer is loaded with the new hold-set value.
The no form of this command reverts the default value.
0
Specifies the number of seconds that the hold-set timer waits after an event enters a set state or enters a higher threshold set state, depending on the event type.
The value of 0 disables the hold-set timer, preventing any delay in processing lower set thresholds or cleared events.
priority priority-level [{delta | explicit}]
no priority
config>vrrp>policy>priority-event>host-unreachable
config>vrrp>policy>priority-event>lag-port-down>number-down
config>vrrp>policy>priority-event>port-down
config>vrrp>policy>priority-event>route-unknown
Supported on all 7210 SAS platforms as described in this document
This command controls the effect the set event has on the virtual router instance in-use priority.
When the event is set, the priority-level is either subtracted from the base priority of each virtual router instance or it defines the explicit in-use priority value of the virtual router instance depending on whether the delta or explicit keywords are specified.
Multiple set events in the same policy have interaction constraints:
If any set events have an explicit priority value, all the delta priority values are ignored.
The set event with the lowest explicit priority value defines the in-use priority that are used by all virtual router instances associated with the policy.
If no set events have an explicit priority value, all the set events delta priority values are added and subtracted from the base priority value defined on each virtual router instance associated with the policy.
If the delta priorities sum exceeds the delta-in-use-limit parameter, then the delta-in-use-limit parameter is used as the value subtracted from the base priority value defined on each virtual router instance associated with the policy.
If the priority command is not configured on the priority event, the priority-value defaults to 0 and the qualifier keyword defaults to delta, therefore, there is no impact on the in-use priority.
The no form of this command reverts to the default values.
0
Specifies the priority level adjustment value, expressed as a decimal integer.
Specifies what effect the priority-level will have on the base priority value.
When delta is specified, the priority-level value is subtracted from the associated virtual router instance base priority when the event is set and no explicit events are set. The sum of the priority event priority-level values on all set delta priority events are subtracted from the virtual router base priority to derive the virtual router instance in-use priority value. If the delta priority event is cleared, the priority-level is no longer used in the in-use priority calculation.
When explicit is specified, the priority-level value is used to override the base priority of the virtual router instance if the priority event is set and no other explicit priority event is set with a lower priority-level. The set explicit priority value with the lowest priority-level determines the actual in-use protocol value for all virtual router instances associated with the policy.