Introduction SuperLoop Configuration Requirements
Software Reference for SwitchBlade x3100 Series Switches (Layer Two Switching)
4-134
4.6.10.2 Feature Interaction
The following features support SuperLoop prevention
• In the output, the Data Vlan Count column shows how many protected VLANs are included in the EPSR
domain.
• For the SHOW EPSR command, the user can easily determine Non-peer SuperLoop and Peer SuperLoop
configurations.
• The parameter PRIORITY is available in the ADD EPSR INTERFACEand SET EPSR commands.
4.6.11 SuperLoop Configuration Requirements
4.6.11.1 Interoperability (General)
1. The SuperLoop feature will interoperate with any third party switches that have implemented RFC 3619 as
part of the network, provided that those third-party switches are not:
• Configured as a Master node for a domain with a common link
• Located on either end of a common link within the SuperLoop topology.
2. Any Network Access product which is running software that includes the SuperLoop feature can be placed
anywhere in the SuperLoop ring topology (i.e., regardless of whether it is adjacent to a common link or
not).
3. Any Network Access product which does not have the SuperLoop feature included in the software it is
running cannot act as a Master node for a domain with a common link or as a transit node on either end of
a common link when placed within a SuperLoop ring topology.
4. A traditional (non-SuperLoop) EPSR ring network (made up of Network Access products and/or third
party switches) can subtend from any node that is part of an EPSR SuperLoop network topology and is not
required to have the SuperLoop feature running in any of the nodes in that subtended ring.
4.6.11.2 Interoperability (Extreme Products)
The SBx3112 contains processing to allow for increased interoperability with Extreme Networks products that
are running Extreme Networks proprietary “EAPS Shared-Ports protocol” in a network topology similar to the
SuperLoop topologies discussed in this Section.
In this scenario, an Extreme Networks product is located on each end of the common link, with one configured
as “Controller” and the other as “Partner”. Processing is provided by the Network Access products to be
compatible with the Extreme Networks products in this configuration provided the following restrictions are
applied:
• The SBx3112 can only operate as a Transit node anywhere within any of the rings sharing a common link
that are running Extreme Networks proprietary “EAPS Shared-Ports protocol”.