Reverting After A Failover; Lacp Configuration And Member Link Behavior - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

JunosE 11.2.x Link Layer Configuration Guide

LACP Configuration and Member Link Behavior

214

Reverting After a Failover

When you specify the auto-revert keyword with the redundant-port command, the
redundant link reverts back to redundant mode when the failed link becomes active
again.
The system uses the following processes when the auto-revert feature is enabled (by
specifying the auto-revert keyword) or disabled.
When auto-revert is enabled:
An active link fails and a redundant link becomes active.
1.
The original active link becomes active.
2.
The original redundant link fails over to the original active link.
3.
The redundant link can fail over to any other active link again.
4.
When auto-revert is disabled:
An active link fails and a redundant link becomes active.
1.
The original active link becomes active.
2.
The original redundant link remains the active link.
3.
You can force the link to fail over by issuing the redundant-port force-failover
4.
command.
By default, when a redundant member link is configured, the system disables LACP and
the transmitter on that link.
When a member link is administratively down, the link state is operationally down at the
local and remote ends, which means it does not transmit or receive PDUs.
The active link does not fail over when:
An active link goes down and you set the redundant member link to administratively
down.
An active link is set to administratively down.
LACP configurations affect member link behavior based on the local or remote endpoint.
For a remote end to include a member link in link aggregation, the two member links that
are connected must have LACP configured.
Table 10 on page 215 lists the acceptable configurations that enable redundant behavior
for LACP modes at local and remote endpoints.
Copyright © 2010, Juniper Networks, Inc.