PBB Features
Page 444 7210 SAS M Services Guide
SAP 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 = 0x88e7.
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.
Existing SAP processing rules still apply for the I-VPLS case; the SAP encapsulation definition on
Ethernet ingress ports defines which VLAN tags are used to determine the service that the packet
belongs to:
• Null encap defined on ingress — Any VLAN tags are ignored and the packet goes to a
default service for the SAP.
• Dot1q encap defined on ingress — only first VLAN tag is considered;
• Qinq encap defined on ingress — both VLAN tags are considered; wildcard support for
the inner VLAN tag
To Next Page
Loading...
