If you have a resilient network design with dual core and multiple paths around the network it is possible to share the traffic through the network by specifying that one core is root bridge for certain VLANs and the other core is root bridge for the remaining VLANs.
If multiple paths exist and you specify that a single core will be root for all VLANs then all traffic will take the same route through the network and the same ports will be placed in blocking state. This means that certain links will be operating purely as redundant links and will not be utilised unless a failure occurs on the primary links. If you split the roots for your VLANs accross say two devices then the best paths to these devices will be different for each VLAN, and different ports will be in blocking states for different VLANs. This means that the traffic through the network will be more evenly spread, and the resilient links will also be utilised instead of just sitting there incase there is a failure.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...