PBB Features
Page 774 7750 SR OS Services Guide
SAP and SDP Support
PBB B-VPLS
•SAPs
→ Ethernet DOT1Q is supported — This is applicable to most PBB use cases, for
example, one backbone VLAN ID used for native Ethernet tunneling.
→ Ethernet null is supported — This is supported for a direct connection between PBB
PEs, for example, no BVID is required.
→ Default SAP types are blocked in the CLI for the B-VPLS SAP.
• The following rules apply to the SAP processing of PBB frames:
→ For “transit frames” (not destined to a local BMAC), there is no need to process the
ITAG component of the PBB Frames. Regular Ethernet SAP processing is applied to
the backbone header (BMACs and BVID).
→ If a local I-VPLS instance is associated with the B-VPLS, “local frames” originated/
terminated on local I-VPLS(s) are PBB encapsulated/de-encapsulated using the pbb-
etype provisioned under the related port or SDP component.
•SDPs
→ For MPLS, both mesh and spoke-SDPs with split horizon groups are supported.
→ Similar to regular pseudowire, the outgoing PBB frame on an SDP (for example, B-
pseudowire) contains a BVID qtag only if the pseudowire type is Ethernet VLAN. If
the pseudowire type is ‘Ethernet’, the BVID qtag is stripped before the frame goes
out.
PBB I-VPLS
• Port Level
→ All existing Ethernet encapsulation types are supported (for example, null, dot1q,
qinq).
•SAPs
→ The I-VPLS SAPs can co-exist on the same port with SAPs for other business
services, for example, VLL, VPLS SAPs.
→ All existing Ethernet encapsulation are supported: null, dot1q, qinq.
•SDPs
→ GRE and MPLS SDP are spoke-sdp only. Mesh SDPs can just be emulated by using
the same split horizon group everywhere.
To Next Page
Loading...
