Technical data

BLADE OS 5.1 Application Guide
194
 Chapter 14: High Availability BMD00136, November 2009
Monitor Port State
A monitor port is considered operation as long as the following conditions are true:
 The port must be in the Link Up state.
 If STP is enabled, the port must be in the Forwarding state.
 If the port is part of an LACP trunk, the port must be in the Aggregated state.
If any of the above conditions is false, the monitor port is considered to have failed.
Control Port State
A control port is considered Operational if the monitor trigger is up. As long as the trigger is up, the
port is considered operational from a teaming perspective, even if the port itself is actually in the
Down state, Blocking state (if STP is enabled on the port), or Not Aggregated state (if part of
an LACP trunk).
A control port is considered to have failed on if the monitor trigger is in the Down state.
To view the state of any port, use one of the following commands:
L2 Failover with Other Features
L2 Failover works together with Link Aggregation Control Protocol (LACP) and with Spanning
Tree Protocol (STP), as described below.
LACP
Link Aggregation Control Protocol allows the switch to form dynamic trunks. You can use the
admin key to add up to two LACP trunks to a failover trigger using automatic monitoring. When
you add an admin key to a trigger, any LACP trunk with that admin key becomes a member of the
trigger.
Spanning Tree Protocol
If Spanning Tree Protocol (STP) is enabled on the ports in a failover trigger, the switch monitors the
port STP state rather than the link state. A port failure results when STP is not in a Forwarding state
(that is, Listening, Learning, Blocking, or No Link). The switch automatically disables the
appropriate control ports.
>> # show interface link (View port link status)
>> # show interface port <x> spanning-tree stp <x> (View port STP status)
>> # show lacp information (View port LACP status)