Proposal Agreement Rstp

15 12 2020

If an alternative P2 port, a specific P3 redirect port and an Edgeport P4 are present on Switch 1, P2 and P4 already meet one of the criteria. To be synchronized, Switch 1 must block the P3 port and give it the pier`s attribution status. When all ports are synced, Switch 1 can remove the blocking from the newly selected P1 port and respond to the strain by sending a message of agreement. This post is a copy of the BPDU proposal with the bit of agreement instead of the proposal bit. This copy ensures that Port P0 knows exactly which proposal corresponds to the agreement to which it corresponds. 1.) The proposal/agreement process between S4 and S2 should be in the opposite direction. At present, it has been shown that S2 sends a proposal to S4 and S4 to respond with an agreement. It`s not true. A proposal can only be sent from a designated port in a reject or learning state, as in the Cisco “Understanding Rapid Spanning Tree Protocol” document under If a new connection between Root and Switch 1 is created, both ports go into a certain blocking state until they receive a BPDU of their equivalent. The proposal bit on BPDUs is only fixed and sent if a designated port is in a state of rejection or learning.

This process occurs for port P0 of the main deck. As Switch 1 receives superior information, Switch 1 immediately knows that Port P1 is the new root port. Switch 1 then ensures that all ports are synchronized with this new information. The SWB will restore all of its ports and send its own BPDU proposal to its neighbours downstream, if it receives a response from its neighbours downstream, it will redirect its base port and send a BPDU agreement to SWA, set at 1, and the notice of the proposal will be set at 0. SWA ports will switch to redirection. The port of SWB to SWA is the base port and refers an agreement to SWA. This initiates the synchronization process in which a switch agrees with a proposal, in this case Sw2, putting all other non-noble ports in the rejection state (if they were present in our topology – which they do not do at the moment because fa0/1 is stopped). Note here that if Sw2 already had a root port elsewhere, the root port roller would be immediately removed and placed on the port that received the best information from BPDU, and the old root port would be rejected. It is only when all non-edge ports are in a release state with the exception of the Connection to Sw1 that the switch expects the ports to be synchronized. Keep in mind that alternative ports and backup sports are already ejected, so all ports, with the exception of the port, are in a state of rejection in the synchronization process. At this point, Sw2 can then put the port in the transmission state and send the BPDU with the defined agreement file. Learning and transmission flags are also defined because the port moves quickly from the return to the redirect state.

The crucial point here is that all ports, with the exception of the port that must send an agreement, must be discarded before the switch can send it. On the connection between S4 and S2, the F0/2 of the S4 is the designated port, while the Fa0/2 of the S2 is the root port, so the S2 should not send suggestions for this link.