|
802.1D Port Role
|
RSTP Port Role
|
802.1D Port State
|
RSTP Port State
|
|
Root port
|
Root port
|
Forwarding
|
Forwarding
|
|
Designated port
|
Designated port
|
Forwarding
|
Forwarding
|
|
Nondesignated port
|
Alternative or backup port
|
Blocking
|
Discarding
|
|
Disabled
|
Disabled
|
---
|
Discarding
|
|
Transition
|
Transition
|
Listening Learning
|
Learning
|
●
To achieve fast convergence on a port with RSTP without
relying on a timer configuration, the protocol relies on two variables: Link
type and edge port
●
Link type provides a categorization for each port
participating in RSTP. Automatically derived from the duplex mode of a port.
Port in full duplex assumed to be point-to-point where half-duplex is
considered shared port. Configuration can be overridden by configuration.
●
Ports directly connected to end stations are
transitioned directly to forwarding. If it receives a BPDU, it loses it’s edge
port status and becomes normal spanning-tree port. Equivalent of PortFast
enabled ports.
●
Point-to-point links are candidates for rapid
transition to forwarding state
●
Root ports - Do not use the link type parameter. Can
make a rapid transition to the forwarding state as soon as the port receives
the BPDU of the root and it puts the nondesignated ports in blocking state.
Operation is called sync
●
Alternative and backup ports - Do not use link type
parameter in most cases because these ports need to arrive at the states based
on the operation of the RSTP. Only configure link type parameter explicitly
when you understand the final state for these ports.
●
Designated ports - Makes most use of link type
parameter. Rapid transition occurs only if the link type parameter indicates a
point-to-point link
●
When an edge port receives a BPDU, it generates a
topology change notification (TCN). RSTP maintains the PortFast keyword for the
edge port configuration making an overall network transition to RSTP more
seamless but configuring an edge port where the port will be attached to
another switch can have negative implications for RSTP when it is in the “sync”
state
●
When a port is selected by spanning tree to become a
designated port, 802.1D waits two times the forward delay seconds (2 x 15 by
default) before it transitions it to the forwarding state. In RSTP, this
condition corresponds to a port with a designated role but a blocking state.
●
802-1D - When the root bridge is aware of a topology
change, it sets a TC flag on the BPDUs that get relayed to all the bridges.
When a bridge receives a BPDU with the TC flag bit set, it reduces it’s
bridging-table aging time to forward-delay seconds ensuring a relatively quick
flushing of stale information.
●
In RSTP, only non-edge ports that are moving to the
forwarding state cause a topology change. Loss of connectivity does not
generate a topology change. A port that is moving to blocking does not cause
the respective bridge to generate a TC BPDU
●
With RSTP, the switch can send its on it’s new root
port to authorize immediate transition to the forwarding state and bypass
twice-the-forward-delay long listening and learning states
●
In 802.1D standard, the BID was composed of the bridge
priority and MAC address of the switch and all the VLANs were represented by a
CST. PVST+, MST, and PVRSTP+ requires a separate instance of spanning tree run
for each VLAN, the BID field is required to carry VLAN ID (VID) information by
reusing a porition of the Priority field as the extended ID to carry a VID.
●
2 Byte header:
○
Bridge Priority - 4-bit field used to carry bridge
priority. Priority conveyed in increments of 4096. Default priority in 802.1D
is 32,768
○
Extended System ID - 12-bit field carrying the VID for
PVST+
○
MAC address - 6-byte field with the MAC address of a
single switch
●
In RSTP, if a port consistently receives BPDUs that do
not correspond to it’s current operating mode for two times the hello time, it
switches to the other STP mode
●
Catalyst supports PVST+, PVRST+, and MST. Default is
PVST+.
●
PortFast - Causes interface to enter forwarding state
immediately. Use for access ports
●
Portfast is configured using the following interface
command: [no] spanning-tree portfast
●
Verify portfast using the following command syntax: show spanning-tree interface fastethernet
3/27 portfast
●
On building access switches, you can enable PortFast
globally so there is no need to enable PortFast on each port individually.
You’ll need to explicitly disable it on uplink ports to other distribution
layer switches though. Doesn’t affect trunk ports.
●
To enable portfast on a trunk port, use the following
interface level command: spanning-tree
portfast trunk
●
Enable portfast globally using the following command: spanning-tree portfast default
●
The following interface command issues a macro for both
portfast and to disable negotiation of channeling and trunking: switchport mode host
●
To enable PVRST+ globally:
○
spanning-tree
mode rapid-pvst
○
spanning-tree
vlan [number] root primary
○
spanning-tree
vlan [number] root secondary
●
Steps to implement PVRST+
○
Enable it globally on all switches in broadcast domain
○
Designate and configure a switch to be the root bridge
○
Designate and configure a switch to be the secondary
(backup) root bridge
○
Enable load sharing on uplinks using priority and cost
parameters
○
Verify the config
●
To verify PVRST+ config: show spanning-tree vlan [number]
●
Multiple Spanning Tree (MST) extends 802.1w RST
algorithm to multiple spanning trees. Purpose is to reduce the total number of
spanning-tree instances to match the physical topology of the network and
reduce the CPU cycles of the switch
●
MST uses the minimum number of STP instances to match
the physical topologies present
●
MST converges faster than PVRST+ and backwards compatible
with STP, RSTP, and PVRST+
●
Allows for building of multiple spanning trees over
trunks by grouping and associating VLANs to spanning-tree instances
●
The term MST region refers to the set of interconnected
bridges that have the same MST configuration
●
MST is more complex and requires additional training of
the operation staff
●
Interaction with legacy bridges is sometimes
challenging
●
MST can provide multiple active forwarding paths for
data traffic and enables load balancing. Failure in one instance or forwarding
path does not necessarily affect other instances
●
Each switch that runs MST in the network has a single
MST configuration that consists of three attributes: An alphanumeric
configuration name (32 bytes), a configuration revision number (2 bytes), and a
4096-element table that associates each of the potential 4096 VLANs supported
on the chassis to a given instance
●
The 12-bit Extended System ID field is used in MST. 4
bits for for bridge priority, 12 bites for Extended System ID (MST instance
number carried here)
●
Enabling MST is a multistep process that involves
mapping ranges of VLANs to a single MSTI
●
Enable MST with the following command: spanning-tree mode mst but you must
configure additional information and instances
|
Step
|
Description
|
Notes and Comments
|
|
1
|
Enters MST configuration
submode. #spanning-tree mst
configuration
|
You can use the no keyword to
clear the MST configuration
|
|
2
|
Displays the current MST
configuration. #show current
|
This command can be used in
configuration mode to display the current configuration before making changes
|
|
3
|
#name name
|
|
|
4
|
Sets the MST configuration
revision number. #revision revision_number
|
The revision number can be any
unassigned 16-bit integer. It is not incremented automatically when you
commit a new MST config
|
|
5
|
Maps the VLANs to an MST
instance. #instance instance_number vlan vlan_range
|
If you do not specify the vlan
keyword, you can use the no keyword to unmap all the VLANs that were mapped
to an MST instance. If you specify the vlan keyword, you can use the no
keyword to unmap a specified VLAN from an MST instance
|
|
6
|
#show pending
|
Displays the new MST config to
be applied
|
|
7
|
#end
|
Applies the configuration and
exit MST config submode
|
|
8
|
#spanning-tree mst instance_number
root primary | secondary
|
Assigns root bridge for MST
instance. This syntax makes the switch primary or secondary (only active if
primary fails). It sets primary priority to 24576 and secondary to 28672
|
|
9
|
#spanning-tree extended system-id
|
This enables MAC address
reduction, also knows as system ID in Cisco IOS software
|
|
19
|
#spanning-tree mst pre-standard
|
This command is required if the
neighboring switch is using a prestandard version of MST
|
●
show
spanning-tree mst [number] [detail]
●
show
spanning-tree mst interface fa0/1
●
Cisco Unidirectional Link Detection (UDLD) and Loop
Guard features prevent network device failures that are due to faulty hardware
or software errors
●
BPDU Guard - Prevents accidental connection of
switching devices to PortFast-enabled ports. Puts port into err-disabled if
BPDU is received.To enable BPD guard or disable it globally: [no] spanning-tree portfast edge bpduguard
default or you can enable it at the interface level: spanning-tree bpduguard enable without even enabing PortFast
●
BPDU Filtering - Restricts a switch from sending
unnecessary BPDUs out access ports/PortFast interfaces. When enabled globally,
BPDU filtering affects all operational PortFast ports on switches that do not
have BPDU filtering configured on the individual ports, if BPDUs are seen the
port loses it’s PortFast status and BPDU filtering is disabled turning it into
a STP port, and upon started, the port transmits ten BPDUs and if it receives
any back during that time, it turns into an STP port. When enabled on an
individual port, it ignores all BPDUs received and sends no BPDUs. BPDU
filtering takes precedence over BPDU guard on an interface rendering BPDU guard
unusable. To enable BPDU filtering globally on portfast ports: spanning-tree portfast bpdufilter default.
To enable it on a specific switchport: spanning-tree
bpdufilter enable. To verify the configuration: show spanning-tree summary
No comments:
Post a Comment