VRRP
Router Configuration Guide 433
Multiple unique lag-port-down event nodes can be configured within the priority-event node up to
the maximum of 32 events.
The lag-port-down command can reference an arbitrary LAG. The lag-id does have to already exist
within the system. The operational state of the lag-port-down event will indicate:
• Set – non-existent
• Set – one port down
• Set – two ports down
• Set – three ports down
• Set – four ports down
• Set – five ports down
• Set – six ports down
• Set – seven ports down
• Set – eight ports down
• Cleared – all ports up
When the lag-id is created, or a port in lag-id becomes operationally up or down, the event operational
state must be updated appropriately.
When one or more of the LAG composite ports enters the operationally down state or the lag-id is
deleted or does not exist, the event is considered to be set. When an event transitions from clear to set,
the set is processed immediately and must be reflected in the associated virtual router instances in-use
priority value. As the event transitions from clear to set, a hold set timer is loaded with the value
configured by the events hold-set command. This timer prevents the event from clearing until it
expires, damping the effect of event flapping. If the event clears and becomes set again before the hold
set timer expires, the timer is reset to the hold-set value, extending the time before another clear can
take effect.
The lag-port-down event is considered to have a tiered event set state. While the priority impact per
number of ports down is totally configurable, as more ports go down, the effect on the associated
virtual router instances in-use priority is expected to increase (lowering the priority). When each
configured threshold is crossed, any higher thresholds are considered further event sets and are
processed immediately with the hold set timer reset to the configured value of the hold-set command.
As the thresholds are crossed in the opposite direction (fewer ports down then previously), the priority
effect of the event is not processed until the hold set timer expires. If the number of ports down
threshold again increases before the hold set timer expires, the timer is only reset to the hold-set value
if the number of ports down is equal to or greater than the threshold that set the timer.
The event contains number-down nodes that define the priority delta or explicit value to be used based
on the number of LAG composite ports that are in the operationally down state. These nodes represent
the event set thresholds. Not all port down thresholds must be configured. As the number of down ports
increase, the number-down ports-down node that expresses a value equal to or less than the number
of down ports describes the delta or explicit priority value to be applied.
The no form of the command deletes the specific LAG monitoring event. The event can be removed
at anytime. When the event is removed, the in-use priority of all associated virtual router instances
must be reevaluated. The events hold-set timer has no effect on the removal procedure.
To Next Page
Loading...
