MSTP(Multiple Spanning Tree Protocol)
2002 \u5e74 IEEE 802.1s mstp\u6a19\u6e96\u88ab\u63d0\u51fa<\/p>\n\n\n\n
\u6982\u5ff5<\/strong> \u512a\u9ede<\/strong> MST\u505a\u6cd5<\/strong> MST\u76f8\u5bb9\u6027<\/strong> …<\/p>\n\n\n\n MST region<\/strong> MST region attribution<\/strong> MST configuration revision number<\/strong> MST region attribution relation<\/strong> …<\/p>\n\n\n\n MSTI(MST Instances)<\/strong> MSTI 0(IST)<\/strong> IST(Internal Spanning Tree) Instances<\/strong> ps: MSTP(Multiple Spanning Tree Pr …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"","fifu_image_alt":"","_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[26],"tags":[],"class_list":["post-815","post","type-post","status-publish","format-standard","hentry","category-osi-layer2"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts\/815","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/comments?post=815"}],"version-history":[{"count":0,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts\/815\/revisions"}],"wp:attachment":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/media?parent=815"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/categories?post=815"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/tags?post=815"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Multiple instances of STP can be used, with each instance supporting a different group of VLANs(mapping one or more VLANs to a single STP instance)<\/p>\n\n\n\n
The MSTP was developed to address the lack of and surplus of STP instances.
ps:
the network administrator can configure exactly the number of STP instances that makes sense for the enterprise network, no matter how many VLANs are in use.
ps:
\u63d0\u4f9bmulti-forward path\u53caload balance\u7684\u6a5f\u5236\uff0c\u800c\u4e14\u4e5f\u8207STP\u53caRSTP\u76f8\u5bb9<\/p>\n\n\n\n
\u5c07\u9700\u8981\u9032\u884c\u76f8\u540cSTP path\u8a08\u7b97\u7684VLAN mapping\u5230\u540c1\u500bSTP instance\u4e2d
\u7121\u8ad6\u6709\u591a\u5c11vlan,\u53ea\u8981\u5be6\u969b\u7522\u751fn\u500bpath,\u5c31\u7dad\u8b77n\u500bstp instance,\u53ef\u7bc0\u7701\u7cfb\u7d71\u8cc7\u6e90
ex:switch\u4e0a\u670920\u500bVLAN\uff0c\u901920\u500bVLAN\u7684\u6d41\u91cf\u53ea\u9700\u89813\u689d\u4e0d\u540cpath\uff0c\u5247\u53ea\u9700\u7ef4\u8b773\u500bSTP instance\u5373\u53ef
ps
CST:\u6240\u6709\u6d41\u91cf\u653e\u5728\u55ae\u4e00\u8def\u5f91\u4e2d\u50b3\u8f38
ex:switch\u4e0a\u670920\u500bVLAN\uff0c\u800cCST\u53ea\u7dad\u8b771\u500bSTP instance
PVST+:\u6bcf\u500bVLAN\u904b\u4f5c\u4e00\u500bSTP instance,\u5c07\u4e0d\u540cVLAN\u7684\u6d41\u91cf\u653e\u5728\u4e0d\u540cpath\u4e0a\u50b3\u8f38,\u4f46\u6bcf\u500bVLAN\u90fd\u904b\u4f5c\u4e00\u500bSTP instance,\u6240\u4ee5\u6703\u5f88\u6d88\u8017\u7cfb\u7d71\u8cc7\u6e90
ex:switch\u4e0a\u670920\u500bVLAN\uff0c\u800cPVST+\u7dad\u8b7720\u4e2aSTP instance<\/p>\n\n\n\n
\u5be6\u4f5cMST\u9700\u6c7a\u5b9a\u7684\u4e8b<\/strong>
1. The number of STP instances needed to support the desired topologies
2. Whether to map a set of VLANs to each instance<\/p>\n\n\n\n
MST is different from 802.1Q and PVST+, although it can interoperate with them
1
if an MST region connects with a switch running traditional PVST+
MST can detect this situation by listening to the received BPDUs.
2
If BPDUs are heard from more than one VLAN (the CST), PVST+ must be in use.
When the MST region sends a BPDU toward the PVST+ switch, the IST BPDUs are replicated into all the VLANs on the PVST+ switch trunk.<\/p>\n\n\n\n
In most networks, a single MST region is sufficient, although you can configure more than one region
ps:
If a switch is configured to use MST, it somehow must figure out which of its neighbors are using which type of STP.This is done by configuring switches into common MST regions,where every switch in a region runs MST with compatible parameters.<\/p>\n\n\n\n
all switches must run the instance of MST that is defined by the following attributes:
MST configuration name (32 characters)
MST configuration revision number (0 to 65535)
MST instance-to-VLAN mapping table (4096 entries)<\/p>\n\n\n\n
1.for tracking changes to the MST region configuration
2.Each time you make changes to the configuration, you should increase the number by one
3.the region configuration (including the revision number) must match on all switches in the region. Therefore, you also need to update the revision numbers on the other switches to match.<\/p>\n\n\n\n
if two switches region 3 attributes
same:
\u3000they belong to the same MST region.
\u3000the STP instances within MST can be shared as part of the same region.
not same:
\u3000 they belong to two independent regions
\u3000a switch is seen to be at the MST region boundary,
ps:
MST region boundary where one region meets another or one region meets traditional 802.1D STP.
ps:
MST BPDUs contain configuration attributes so that switches receiving BPDUs can compare them against their local MST configurations.<\/p>\n\n\n\n
entire MST instance-to-VLAN mapping table<\/strong>
1 The table contents:
\u3000is not sent in the BPDUs ,
\u3000because the instance mappings must be configured on each switch.
2 a digest\/hash code computed from the table contents:
\u3000is sent in the BPDUs
\u3000As the contents of the table change, the digest value will be different.
ps:
a switch quickly can compare a received digest to its own to see if the advertised table is the same<\/p>\n\n\n\n
1.different MSTIs can exist within a single MST region
2.Each of the MSTIs is significant only within a region, even if an adjacent region has the same MSTIs in use.
ex:
MST region “compnayregion” include MSTI1=vlan2-3 stp ,MSTI2=vlan4-5 stp
ps:
In other words, the MSTIs combine with the IST only at the region boundary to form a subtree of the CST. That means only IST BPDUs are sent into and out of a region.
ps:
MSTI number\u70babridge id\u4e2d\u7684extend system id<\/p>\n\n\n\n
only the MSTI is allowed to send and receive MST BPDUs.
Information about each of the other MSTIs is appended to the MST BPDU as an M-record.
By default, all VLANs will belong to MSTI 0
ps:
if a region has all 16 instances active, only 1 BPDU is needed to convey STP information about them all.<\/p>\n\n\n\n
1. Something other than CST must work out a loop-free topology inside each MST region.
2. Within a single MST region,
an IST instance runs to work out a loop-free topology
between “the links where CST meets the region boundary” and “all switches inside the region”.
ps:
the IST instance as a locally significant CST, bounded by the edges of the region.
The IST presents the entire region as a single virtual bridge to the CST outside.
ps:
BPDUs are exchanged at the region boundary only over the native VLAN of trunks, as if a single CST were in operation<\/p>\n\n\n\n
the IST instance is active on every port on a switch. Even if a port does not carry VLANs that have been mapped to the IST, IST must be running on the port.<\/p>\n","protected":false},"excerpt":{"rendered":"