From what I understand, to participate in RSTP convergence, a switch must determine the status of each of its ports, and if an RSTP-compatible switch is activated, non-Edge ports remain in a defined/blocking or rejected state, right? Imagine we have two SWA and SWB switches, and when those switches are switched on, both switches claim to be the segment root switch, and they will both start replacing the BPDUs. Send SWA A BPDU configuration with BPDU`s proposal set to 1, if SWB receives this BPDU and see that it is a BPDU PRESE, it holds the port that it receives this BPDU to receive a root port, am I correct? “If a designated port is in a state of rejection or learning (and only in this case), it fixes the proposal bit on the bpDUs it sends.” 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. Ранее, для того, чтобы убедиться, что порт может участвовать в передаче данных, требовались таймеры, т.е. свич пассивно ждал в течение означенного времени, слушая BPDU. RSTP – RSTP – Full Duplex – Full Duplex (-.
. Shared-B- BLK — LIS — LRN — FWD.
