Cisco 2950 Software Configuration Guide - Page 340
Specifying the Link Type to Ensure Rapid Transitions, Restarting the Protocol Migration Process
UPC - 746320454504
View all Cisco 2950 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 340 highlights
Configuring MSTP Features Chapter 15 Configuring MSTP Specifying the Link Type to Ensure Rapid Transitions If you connect a port to another port through a point-to-point link and the local port becomes a designated port, the RSTP negotiates a rapid transition with the other port by using the proposal-agreement handshake to ensure a loop-free topology as described in the "Rapid Convergence" section on page 15-7. By default, the link type is determined from the duplex mode of the interface: a full-duplex port is considered to have a point-to-point connection; a half-duplex port is considered to have a shared connection. If you have a half-duplex link physically connected point-to-point to a single port on a remote switch running MSTP, you can override the default setting of the link type and enable rapid transitions to the forwarding state. Beginning in privileged EXEC mode, follow these steps to override the default link-type setting. This procedure is optional. Step 1 Step 2 Command configure terminal interface interface-id Step 3 Step 4 Step 5 Step 6 spanning-tree link-type point-to-point end show spanning-tree mst interface interface-id copy running-config startup-config Purpose Enter global configuration mode. Specify the interface to configure, and enter interface configuration mode. Valid interfaces include physical ports, VLANs, and port channels. Valid VLAN IDs are 1 to 1005 when the SI is installed and 1 to 4094 when the EI is installed. Valid port-channel numbers are 1 to 6. Specify that the link type of a port is point-to-point. Return to privileged EXEC mode. Verify your entries. (Optional) Save your entries in the configuration file. To return the switch to its default setting, use the no spanning-tree link-type interface configuration command. Restarting the Protocol Migration Process A switch running MSTP supports a built-in protocol migration mechanism that enables it to interoperate with legacy 802.1D switches. If this switch receives a legacy 802.1D configuration BPDU (a BPDU with the protocol version set to 0), it sends only 802.1D BPDUs on that port. An MSTP switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a different region, or an RST BPDU (version 2). However, the switch does not automatically revert to the MSTP mode if it no longer receives 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. A switch also might continue to assign a boundary role to a port when the switch to which it is connected has joined the region. To restart the protocol migration process (force the renegotiation with neighboring switches) on the switch, use the clear spanning-tree detected-protocols privileged EXEC command. To restart the protocol migration process on a specific interface, use the clear spanning-tree detected-protocols interface interface-id privileged EXEC command. 15-22 Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide 78-11380-10