设为首页 收藏本站
查看: 815|回复: 0

[经验分享] cisco(STP)生成树协议

[复制链接]

尚未签到

发表于 2018-7-15 15:52:17 | 显示全部楼层 |阅读模式
看了以后我觉得我对STP有了一个很进步的了解 (双语对照)  1.Consider the example in winch there are bridges:
  Bridge A
  Bridge B
  Bridge C
  3个网桥作为范例:
  网桥A 网桥B 网桥C
  2.Each bridge has a connection with the other bridges.
  每个网桥与其他网桥有一个连接线路。
  3.At the bootup,all of the bridges think of themselves as the Root Bridge.
  在引导启动阶段,所有的网桥把自己看作根网桥(Root Bridge)。

  4.Assume that the first step is that Bridge C sends the BPDU to Bridges A and B,announcing that Bridge C is the Root,with the Root>
  Note that Bridge B\'\'\'\'s Root>
  设想第一步网桥C发送BPDU到网桥A和B,宣布网桥C是根Root,Root>
  网桥B的Root>
  5.Considering that Bridge B\'\'\'\'s Bridge>
  Bridge A still considers itself as the Root as its Bridge>  鉴于网桥B的网桥ID比在BPDU中的网桥ID高,网桥B认为网桥C作为root。

  网桥A一直认为它自己是Root,因为它的网桥ID比BPDU中的Root>  6.Assume that the next step is for Bridge A to send BPDUs towards Bridge B and C announcing itself as the Root.

  Note the change in B and C\'\'\'\'s Root>  下一步网桥A向网桥B和C发送BPDU,宣布自己是Root.

  改变网桥B和C的Root>  7.All bridges are now is agreement that Bridge A is the Root Bridge.
  所有的网桥现在一致认为网桥A为 Root Bridge。
  8.Every non-root bridge must select one Root port.A bridge\'\'\'\'s root port is the port closest to the Root bridge.
  Non-root Bridges elect their respective root port based on the Root path Cose,which is the cumulative cost of all links to the root bridge.
  每个非根网桥(non-root bridge)必须选择一个根端口。A网桥的根端口( root port)离根网桥最近。
  非根网桥基于根路径代价( Root path Cose)选择它们各自的根端口,即到根网桥的所有连接的累积代价(cost)。
  9.Assuming that all links between the bridges have the same speed(say 100 Mbps with a cost of 19,according to the IEEE),Bridge B and Bridge C elect their Root ports.
  假设所有网桥间的链路有相同的速度(依照IEEE100 Mbps代价为19),网桥B和C选择他们的根端口。
  10.Election of Designated ports
  Ports providing the least path cost from the segment to the root are elected as designated ports.
  选举制定的端口
  选择从网段到根有最少路径代价的端口作为制定端口。
  11.The bridge containing the designated port for a given segment is referred to as the designated bridge for that segment.
  在特定网段含有指定端口的网桥被认为是该网段segment的指定网桥。
  12.there are three segments:
  segment 1
  segment 2
  segment 3
  Since the ports on Bridge A are directly connected to the Root Bridge,these ports become the designated ports for Segment 1 and Sement 2.
  这里有三个网段:网段1 网段2 网段3
  网桥A上的端口直接连接根网桥,这些端口成为了网段1和2的指定端口。
  13.Sement3

  The path cost to the root bridge is the same for Bridge B and Bridge C.The tie breaker is the lower bridge>  网段3
  网桥A和网桥C到根网桥的路径代价相同。 平局决胜制tie breaker降低了网桥C的网桥ID。

  14.Since the bridge>  网桥C的网桥ID小于网桥B的,6W@v专4-提无供H业cR教网段B的指定端口变为网桥C的1/2端口。
  15.Root port and the designated ports go into the forwarding states.
  根端口和制定端口进入转发状态(Forwarding state)
  16.Ports that are neither the root ports nor the designated ports,in other words ports that are non-designated ports,go to the blocking state.
  既不是根端口也不是标记端口,
  而是未指定端口进入阻塞状态(Blocking state)。
  17.At this point Spanning tree has fully converged.
  这时生成树成功聚合。
  18.Bridge C has a better BPDU than Bridge B.Bridge C continues to send BPDUs advertising its superiority  over Bridge B.
  As long as Bridge B continues to receive these Superior BPDUs on port 1/2,the port remains in the Blocking mode.
  网桥C比网桥B有较好的BPDU 。 网桥C继续发送BPDU广告它的优越性超过网桥B。
  在网桥B继续在端口1/2接收这些上级BPDU时,端口保持阻塞模式。
  19.For any reason if Bridge B fails to receive these BPDUs for max age time,which is 20 seconds by default,it would start to transition to the forwarding mode.
  Most of the Spanning Tree Algorithm(STA) failures occur due to the excessive loss of BPDUs causing the blocked ports to transition to forwarding mode.
  由于一些原因,如果网桥B失败的在最大老化时间Max Age Time (默认20秒)接收到这些BPDU。它将开始改变转发模式。
  大多的生成树算法(STA)失败发生由于过多的丢失BPDU导致阻塞端口转换为转发模式。
  20.Spanning Tree  Failure
  The blocked port has gone into fowarding mode and the Spanning Tree Failure occurred.
  生成树失败
  阻塞端口进入转发模式,生成树失败发生。
  21.一些由于丢失BPDU引起阻塞端口进入转发模式的情形:
  双方配合不当Duplex Mismatch
  单项链路Unidirectional Link
  包破坏Packet Corruption
  资源错误Resource Errors
  速端口(Portfast)配置错误Portfast Configuration Error
  难使用的生成树协议STP参数调整和直径(网络拓扑中末端站点任意2个连接之间网桥最大数量2-7)流出Awkward STP Parameter Tuning and Diameter Issues
  软件错误Software Errors
  关于上述情形详细资料请继续阅读相关文档

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-537456-1-1.html 上篇帖子: Cisco IOS的故障恢复方法 下篇帖子: Cisco ASA 5505 NAT+DHCP
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表