When a switch is set as secondary root , the bridge id will come less than root bridge id. How this is notified in the BDPU ? Will it not create a confusion in the root bridge selection. how this is handled in STP ?
In the STP root selection process, less is better. If Switch A advertises a root ID that is a lower number than the root ID that Switch B advertises, the information from Switch A is better. Switch B stops the advertisement of its root ID, and accepts the root ID of Switch A.
All the switches exchange information for use in the root switch selection and for subsequent configuration of the network. Bridge protocol data units (BPDUs) carry this information. Each switch compares the parameters in the BPDU that the switch sends to a neighbor with the parameters in the BPDU that the switch receives from the neighbor.
every switch consider itself as root till the time it doesnt get any bpdu from its neighbour with lower bridge ID.Once it knows the switch with lowest bridge id, it put that bridge id in its own bpdu's root id field and start communicating to others.
When you configure root primary/Secondary, it automatically decrease/adjust the priority value to make the switch root primary/secondary.However,if you manually assign lowest root value to some other switch then "root primary/Secondary" will not self readjust its value which means your root will no longer act as root.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
There's no "reserved" root or secondary root values. Root would be the active bridge with the lowest bridge ID and "secondary root" would be the active bridge with the next lowest bridge ID. As bridge ID also uses device MAC, there shouldn't be any "ties".
As bridge ID also contains a configurable bridge priority, you normally assign a value one or two tiers lower, (or the lowest possible) than the default for your choice of the root bridge and assign a priority between the default and what was set for your choice of root bridge for your secondary root bridge choice.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...