Multiple Spanning Tree Protocol: Difference between revisions

Content deleted Content added

Revision as of 21:41, 30 May 2025 edit Kvng (talk \| contribs) Extended confirmed users, New page reviewers 116,029 edits acro def in prose. convert EL to ref. no such main article. ← Previous edit		Latest revision as of 21:45, 30 May 2025 edit undo Kvng (talk \| contribs) Extended confirmed users, New page reviewers 116,029 edits m rm already linked
(One intermediate revision by the same user not shown)
Line 182: ==== BPDUs ==== ~~{{Main article\|Bridge Protocol Data Unit}}~~ AMSTP BPDUs use the same local multicast protocol addresses than STP and have a structure that resembles MSTP BPDUs since both are comprised essentially of a basic BPDU and several AM-Records, allowing full-backwards compatibility with RSTP and STP standard protocols. Each of the AM-Records contains the data used to negotiate a specific tree instance (AMSTI). Every ABridge, except for the elected root bridge, creates an AM-Record for its own spanning tree instances. They are used by connected ports of neighboring switches to negotiate the transitions of each tree instance with a proposal/agreement mechanism. Line 216 ⟶ 215: ==See also== * [[Bridge Protocol Data Unit]] * [[Distributed minimum spanning tree]] * [[EtherChannel]]