Rstp Proposal And Agreement Process

At the same time, Sw1 transferred its port to the intended role in the transmitting state. This virtually completes the RSTP synchronization process between Sw1 and Sw2. Switch A responds to the root switch with a redirect agreement. Both switch ports quickly switch to the transmission state with the certainty that there are no Layer 2 loops. I will use the following topology to go through the synchronization process. And that`s it! Sw1 and Sw2 are synchronized and have also notified all ports that have switched to the redirect state. The same process goes from Sw2 down to Sw3 and then they will converge. Once all the unspecified links on the Edge have gone through this process, the network is considered synchronized. SWB will put all its ports in a state of disruption and send its own BPDU proposal to its downstream neighbors, if it receives a response from its downstream neighbors, it will pass its root port to the transmission state and send a BPDU agreement to SWA, set at 1 and the proposal rate at 0. SWA ports are transferred in the transmission. Thank you very much. I understand at least the operation and intent of the proposal agreement mechanism As a result, all designated non-edge ports have been put into a rejection state, at this point they all start sending BPDUs with the proposal bit and start the downstream proposal/agreement process to the other switches…