Allied Telesis SwitchBlade x3100 Series Manual page 457

Configuring SuperLoop
The network should be configured such that domain instances sharing a common link should have their
Note:
data VLANs segregated; domains should either have a unique set of data VLANs (so no data VLANs
are shared with other domains) or have domains that share data VLANs should have only those shared
data VLANs in them. This is enforced through the CLI, and is explained in more detail in the subsection
on the example configuration.
No two domain instances with a common ring port with shared data VLANs can have the same priority
2.
value on the common interface.
If the user tries to do this, the CLI will fail the command, and the domain(s) cannot be enabled.
Note:
It is possible for a ring segment to have common links with the same priority, but only if these common links
3.
are dis-jointed and are for different ring segments.
4.6.13 Configuration Procedure
Figure 4-16 shows a network consisting of two protected ring segments that share a common link. The two
ring segments (ring segments 1 and 2) make up two EPSR domains that share the same set of data VLANs.
There are two SBx3112 systems (System A and System F). System A is a Transit Node shared by both ring seg-
ments 1 and 2. System F is a Master Node on ring segment 1. This network represents a Peer SuperLoop EPSR
logical domain (as described in section 4.6.11.3) because both ring segments share a common link as well as the
same set of protected VLANs.
Each interface on the common link must have the same VLAN configuration. So, the VLAN
Note:
configuration on interface 3.2 (on System A) must match the configuration on interface 11.4 (on
System E).
Software Reference for SwitchBlade x3100 Series Switches (Layer Two Switching)
Introduction
4-137