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

SSL VPN vs IPSec VPN: Understanding the Key Differences

When it comes to securing communication over the internet, Virtual Private Networks (VPNs) are a cornerstone of modern networking. Two popular types of VPNs are SSL VPN and IPSec VPN . While both serve to encrypt and secure data, they differ significantly in terms of technology, use cases, and implementation. This blog post will help you understand these differences and choose the right solution for your needs. What is SSL VPN? An SSL VPN uses the Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS) , to create a secure connection. It operates at the Application Layer (Layer 7) of the OSI model and is designed to provide secure access to specific resources over the internet. Key Features of SSL VPN: Ease of Use: Accessible via a standard web browser without the need for dedicated client software. Granular Access Control: Allows users to access specific applications or resources rather than the entire network. Port Usage: Uses TCP port 443, which is rarely...
Post a Comment
Read more

Understanding PKI The Complete Process Explained

The Complete Public Key Infrastructure (PKI) Process: From Key Generation to Certificate Verification Public Key Infrastructure (PKI) is the backbone of secure communication on the internet. It ensures that sensitive data exchanged between clients and servers remains private and authentic. This blog post will guide you through the entire PKI process, from generating keys to verifying certificates and ensuring they haven't been revoked. 1. Key Pair Generation The first step in PKI is generating a public-private key pair using an asymmetric cryptographic algorithm, such as RSA or ECDSA: The private key is securely stored on the server and never shared. The public key is included in the certificate and shared with the Certificate Authority (CA) during the certificate request process. This key pair enables encryption and decryption, which are essential for secure communication. 2. Creating a Certificate Signing Request (CSR) The server creates a Certificate Signing Request (CSR) to...
Post a Comment
Read more