Header
Home | Set as homepage | Add to favorites
  Search the Site     » Advanced Search
Sections
Syndication


Blogroll:

||||| ALL Cisco-Network ARTICLES |||||  
CCIE Journey,
The CCIE Journey,


Bridge Protocol Data Unit Format

Jul 08,2008 by admin

image

Bridge Protocol Data Unit Format

graphics/01fig17.gif

Spanning Tree Port Transitions and Timers

Part of the STP algorithm and process of building a loop-free network, as well as reconfiguration on a topology change, is to cycle the bridge ports through several states, as follows:

  • Blocking— A port is placed in blocking mode upon startup and when STP determines it is a suboptimal path to the root bridge. Blocked ports do not forward traffic.

  • Listening— When a port is transitioned from blocking to listening, it starts to listen for other bridges. It does not send out configuration messages, learn MAC addresses, or forward traffic.

  • Learning— The bridge continues to listen for other bridges; however, it can now also learn MAC addresses of network devices.

  • Forwarding— This is normal operation. Data and configuration messages are passed through the port.

STP uses timers to determine how long to transition ports. STP also uses timers to determine the health of neighbor bridges and how long to cache MAC addresses in the bridge table.

The explanation of the timers is as follows:

  • Hello timer— 2 seconds. This timer is used to determine how often root bridge sends configuration BPDUs.

  • Maximum Age (Max Age)— 20 seconds. This timer tells the bridge how long to keep ports in the blocking state before listening.

  • Forward Delay (Fwd Delay)— 15 seconds. This timer determines how long to stay in the listening state before learning, and the learning state before forwarding.

The STP timers can be tuned based on network size. These parameters are designed to give STP ample opportunity to ensure a loop-free topology. Mistuning these parameters can cause serious network instability. Tuning these parameters will be discussed in Chapter 10, "Implementing and Tuning Spanning Tree." When a bridge sees BPDUs with a better path to the root, it recalculates STP. This allows ports to transition when appropriate.

Topology Changes in STP

The other type of STP BPDU that needs to be discussed is Topology Change Notification (TCN). TCNBPDU is generated when a bridge discovers a change in topology, usually because of a link failure, bridge failure, or a port transitioning to forwarding state. The TCN BPDU is set to 0x80 in the Type field and is subsequently forwarded on the root port toward the root bridge. The upstream bridge responds back with acknowledgment of the BPDU in the form of Topology Change Acknowledgment (TCA). The least significant bit is for TCN, and the most significant bit is for TCA in the Flag field.

Figure 1-18 shows the flow of topology change BPDUs. The bridge sends this message to its designated bridge. Remember, the designated bridge is a particular bridge's closest neighbor to the root (or the root, if it is directly connected). The designated bridge acknowledges the topology change back to the sending neighbor and sends the message to its designated bridge. This process repeats until the root bridge gets the message. The root learns about the topology changes in the network in this way.


287 times read

Related news

» Topology Changes in STP
by admin posted on Jul 08,2008
» Spanning Tree Port Transitions and Timers
by admin posted on Jul 08,2008
» Spanning Tree Port States
by alperen posted on Dec 09,2008
» BackboneFast
by alperen posted on Dec 13,2008
» Spanning Tree Operations
by admin posted on Jul 08,2008
Did you enjoy this article?
(total 0 votes)

comment Comments (0 posted) 

More Top News
CCSP-Cisco Certified Security Professional
Most Popular
Most Commented
Featured Author