This applies to bridges that otherwise
would be exchanging BPDUs, such as provider edge bridge C-components and customer
bridges. Bridges such as simple S-components, which pass BPDUs as ordinary
data, need not be specially configured. The server-side bridges do, however, respect the
Multiple VLAN Registration Protocol (MVRP). They register all VIDs with the client
bridge (thus saying, ???I??™ll take anything???). The server-side bridges accept MVRP registrations
from the client bridges as well and filter those VIDs that are not registered by
the client cloud.
On the client side, the bridge or cloud of bridges simply runs a spanning tree algorithm,
presumably MSTP, so that different VLANs can be blocked on different links.
The only oddity is, again, that the bridge ports connecting to the server cloud are
specially configured. This configuration involves a few changes to the normal MSTP
algorithms:
?– BPDUs received from the server cloud are discarded and ignored.
?– No BPDUs are transmitted toward the server cloud.
?– Each of these ports pretends to receive a BPDU from the server cloud that claims
a path to a root bridge that is superior to any potential claim to being a root bridge
for any bridge in the client cloud.
Pages:
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913