This example enables 802.1X-based port security on M6100/M7100/M5300 and prompts the
hosts connected on ports g5-g8 for an 802.1X-based authentication. The switch passes the
authentication information to the configured RADIUS server.

MSTP

Spanning Tree Protocol (STP) runs on bridged networks to help eliminate loops. If a bridge
loop occurs, the network can become flooded with traffic. IEEE 802.1s Multiple Spanning
Tree Protocol (MSTP) supports multiple instances of Spanning Tree to efficiently channel
VLAN traffic over different interfaces. Each instance of the Spanning Tree behaves in the
manner specified in IEEE 802.1w, Rapid Spanning Tree, with slight modifications in the
working but not the end effect (chief among the effects is the rapid transitioning of the port to
the Forwarding state).

The difference between the RSTP and the traditional STP (IEEE 802.1D) is the ability to
configure and recognize full duplex connectivity and ports that are connected to end stations,
resulting in rapid transitioning of the port to the Forwarding state and the suppression of
Topology Change Notification. These features are represented by the parameters
pointtopoint

and edgeport. MSTP is compatible to both RSTP and STP. It behaves

appropriately to STP and RSTP bridges.

A MSTP bridge can be configured to behave entirely as a RSTP bridge or a STP bridge. So,

an IEEE 802.1s bridge inherently also supports IEEE 802.1w and IEEE 802.1D.

The MSTP algorithm and protocol provides simple and full connectivity for frames assigned
to any given VLAN throughout a Bridged LAN comprising arbitrarily interconnected
networking devices, each operating MSTP, STP or RSTP. MSTP allows frames assigned to
different VLANs to follow separate paths, each based on an independent Multiple Spanning
Tree Instance (MSTI), within Multiple Spanning Tree (MST) Regions composed of LANs and
or MSTP Bridges. These Regions and the other Bridges and LANs are connected into a
single Common Spanning Tree (CST). [IEEE DRAFT P802.1s/D13]