Control Port State
L2 Failover with Other Features
LACP
Spanning Tree Protocol
468
CN4093 Application Guide for N/OS 8.2
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 only if the monitor trigger is in the Down
state.
To view the state of any port, use one of the following commands:
CN4093# show interface link
CN4093# show interface port <x> spanningtree stp <x>
CN4093# show lacp information
L2 Failover works together with Link Aggregation Control Protocol (LACP) and
with Spanning Tree Protocol (STP), as described in the next sections.
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.
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 (such as Learning, Discarding, or No Link).
The switch automatically disables the appropriate internal ports, based on the
VLAN monitor.
When the switch determines that ports in the trigger are in STP Forwarding state,
then it automatically enables the appropriate internal ports, based on the VLAN
monitor. The switch fails back to normal operation.
(View port link status)
(View port STP status)
(View port LACP status)