Member Link With Non-Lag Partner; Ethernet Link Redundancy And Rstp; Table 10: Behavior Of Member Links Using Local And Remote Lacp - Juniper JUNOSE SOFTWARE 11.0.X - LINK LAYER CONFIGURATION GUIDE 4-1-2010 Configuration Manual

JUNOSe 11.0.x Link Layer Configuration Guide
Table 10: Behavior of Member Links Using Local and Remote LACP Modes

Member Link with Non-LAG Partner

When a member link has a non-LAG partner, there are two separate links in a 1:1
configuration. To successfully configure this, you must disable LACP.
When a failover occurs and LACP is active, the partner might receive a new LAG ID
and the LACP PDUs receive a new MAC address; therefore, the member links are
not aggregated or the bundle is disabled, terminating the sessions above it.
The partner that is connected to the redundant link must not be forwarding network
traffic; that is, it is either blocked through a protocol such as RSTP, or MAC address
learning has selected the active port. The redundant link must not transmit over the
redundant link to that MAC. The behavior of the redundant link depends on the
failure detection method that is controlled by the network protocol that is blocking
the port.

Ethernet Link Redundancy and RSTP

In a LAG to non-LAG configuration, you can configure redundancy capabilities when
redundant ports are connected to a bridged network that has RSTP controlling the
topology.
On external devices, we recommend that you configure RSTP-enabled bridged ports
that are connected to the LAG interfaces as edge ports to enable the ports to transition
quickly to forwarding state upon reconfiguration, and to avoid the listening and
learning states required by the spanning tree protocol. The edge port designation
instructs the local bridge that bridge loops do not exist through the interface, enabling
it to skip the listening and learning states.
218
Ethernet Link Redundancy Behavior
Remote LACP Mode
Local LACP Mode Disabled
Passive
Active
Disabled Passive Active
–
–