Skip to main content

RSTP - Proposal Agreement Process Simplified

 In RSTP (Rapid Spanning Tree Protocol), the Proposal and Agreement process is key to optimizing convergence times when a topology change occurs. Here’s how it works:

  1. Proposal Stage:

    • When a switch detects a link coming up (such as when a new switch is connected or a port goes from blocking to forwarding), it assumes it could become the designated bridge on that port.
    • The switch sends a Proposal BPDU on that port, which signals to the downstream switch that it intends to make the port a designated port and immediately start forwarding traffic.

  2. Agreement Stage:

    • The downstream switch (receiving the Proposal BPDU) checks whether the port on its side should be in blocking or forwarding state.
    • If the downstream switch agrees with the proposal and can allow the new topology without creating loops, it sends an Agreement BPDU back to the original switch.
    • Upon receiving the Agreement, the original switch places the port into the Forwarding state immediately without waiting for the long transition times used by legacy STP (802.1D).

  3. Synchronization:

    • The downstream switch will block its non-edge ports until it ensures that they will not form loops, i.e., until it completes its own Proposal and Agreement process with other switches further downstream.

Key Advantages:

  • Rapid Convergence: The Proposal and Agreement mechanism allows rapid transitions to the forwarding state without the long delays experienced in legacy STP.
  • Loop-Free Topology: This process ensures that no loops are formed during topology changes because switches only allow forwarding when they agree on the new topology.

In essence, RSTP achieves much faster convergence compared to legacy STP by utilizing this Proposal and Agreement mechanism, which replaces the slow transitional states of Listening and Learning.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...
Post a Comment
Read more