This information is propagated through the client
network in the normal way.
?– If a server-facing port in the client cloud is ever chosen as a designated port, then
the port is placed in the blocked state, instead of the forwarding state.
Each server-facing port in the client cloud is configured with different root bridge
information. Presumably, with two links available, you would configure one such
port with a very high priority root for one spanning tree and a not-quite-so-high priority
root for the other VLANs, and the other server-facing port would be configured
in an opposite manner. As the spanning tree operates normally in the client cloud,
the port that has the best claim becomes a root port and goes into the forwarding
state. When that information propagates to any other server-facing port, one that
has a second- or third-best claim, that port becomes a designated port and is blocked.
Thus, exactly one of the server-facing ports is in the forwarding state for any given
spanning tree.
In the event of the failure of either one of the links or bridges, one of the secondary
ports becomes the root port. This happens almost instantaneously if the client cloud is
a single bridge, and it happens through the normal spanning tree operations if it is a
cloud of bridges.
Pages:
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914