PBB Features
Page 792 7750 SR OS Services Guide
Support Service and Solution Combinations
The following considerations apply when Ethernet tunnels are configured under a VPLS
service:
• Only ports in access or hybrid mode can be configured as eth-tunnel path members. The
member ports can be located on the same or different IOMs or MDAs.
• Dot1q and QinQ ports are supported as eth-tunnel path members.
• The same port cannot be used as member in both a LAG and an Ethernet-tunnel.
• A mix of regular and multiple eth-tunnel SAPs and PWs can be configured in the same
BVPLS.
• Split horizon groups in BVPLS are supported on eth-tunnel SAPs. The use of split horizon
groups allows the emulation of a VPLS model over the native Ethernet core, eliminating
the need for P-MSTP.
• STP and MMRP are not supported in a BVPLS using eth-tunnel SAPs.
• Both PBB ELINE (Epipe) and ELAN (IVPLS) services can be transported over a BVPLS
using Ethernet-tunnel SAPs.
• MC-LAG access multi-homing into PBB services is supported in combination with
Ethernet tunnels:
→ MC-LAG SAPs can be configured in IVPLS or Epipe instances mapped to a BVPLS
that uses eth-tunnel SAPs
→ Blackhole Avoidance using native PBB MAC flush/MAC move solution is also
supported
• Support is also provided for BVPLS with P-MSTP and MMRP control plane running as
ships-in-the-night on the same links with the Ethernet tunneling which is mapped by a
SAP to a different BVPLS.
→ Epipes must be used in the BCBs to support scalable point-to-point tunneling between
the eth-tunnel endpoints when management VPLS is used.
• The following solutions or features are not supported in the current implementation and
are blocked:
→ Capture SAP
→ Subscriber management
→ BSX
→ Eth-tunnels usage as a logical port in the config>redundancy>multi-
chassis>peer>sync>port context
For further information, see G.8031 Protected Ethernet Tunnels on page 54.
To Next Page
Loading...
