My network environment is traditional 3 layers network, which is composed of Core, Aggregation and Edge.
Core router is the place where we set gateway, and I also set Core's spanning tree priority with 8192 to make Core play as a root.
Here is the situation, there was vlan 100 on Core and Aggregation but not on Edge. I was trying to create vlan 100 on Edge. Edge's spanning tree priority was default(32768), so I was sure Edge will not take the root. After I created vlan 100 on Edge, I saw some log like "Topology change.......@#$@#%" showed on Edge.
I looked up some description of topology change as below
Principle of Operation
This section explains how a bridge advertises a topology change at the Bridge Protocol Data Unit (BPDU) level.
It has already been briefly explained when a bridge considers it detected a topology change. The exact definition is:
When a port that was forwarding is going down (blocking for instance).
When a port transitions to forwarding and the bridge has a designated port. (This means that the bridge is not standalone.)
The process to send a notification to all bridges in the network involves two steps:
The bridge notifies the root bridge of the spanning tree.
The root bridge "broadcasts" the information into the whole network.
Here are my questions...
1.) When I saw "topology change....." log on Edge, does this mean Edge receives the topology change BPDU from root?
2.) The one who initializes the TCN should be Aggregation, do I think right? Because Aggregation got a port transitions to forwarding and it also has designated port, whereas Edge only has root port.
3.) In this case, even Edge's priority is too big to take the root, does Aggregation still sends the TCN to root(Core)?
4.) Followed by Q3, when root(Core) receives the TCN, does root also broadcast the information to all members even Edge is not able to be root?
5.) Followed by Q4, in this case, do all other members still flush their MAC table when receive the broadcast from root?
GoalDocumentationDefineAdd Device to Smart AccountSync Smart Account via vManage1.1 VNF package for vBranchDesignDeployOperate
To successfully provision a ENCS device in remote site with internet connection.
Minimum software relea...
はじめに確認方法Version による Application name の変更について備考参考情報 はじめに本ドキュメントでは Cisco SD-WAN における Policy 上で設定可能な Application を確認する方法について記載しています。 確認方法サポートされている Application name についてはご使用されている vManage へ API を呼び出して確認することが可能です。https://<IP or FQDN>/...
DMVPN (Dynamic Multipoint VPN) Introduced by Cisco in late 2000 is a routing technology you can use to build a VPN network with multiple sites (spokes) without having to statically configure all devices. It’s a “hub and spoke” network, where the spok...
On 24th August 2021, Cisco announced the latest IOS XE release - Cisco IOS XE Bengaluru 17.6.1a
IOS XE 17.6.1a unlocks various routing features and enhancements comprehensively covering different technology segments such as voice, security,...
DMVPN (Dynamic Multipoint VPN) Introduced by Cisco in late 2000 is a routing technology you can use to build a VPN network with multiple sites (spokes) without having to statically configure all devices. It’s a “hub and spoke” network, where th...