PBB Features
Page 442 7210 SAS M Services Guide
PBB Mapping to Existing VPLS Configurations
The IEEE model for PBB is organized around a B-component handling the provider backbone
layer and an I-component concerned with the mapping of the customer/provider bridge (QinQ)
domain (MACs, VLANs) to the provider backbone (B-MACs, B-VLANs). For example, the I-
component contains the boundary between the customer and backbone MAC domains.
Alcatel-Lucent’s implementation is extending the IEEE model for PBB to allow support for MPLS
pseudowires using a chain of two VPLS context linked together as depicted in Figure 61.
7210 does not support MPLS pseudowires in a PBB B-component and PBB I-component.
Figure 61: PBB Mapping to VPLS Constructs
Note: I-PW and B-PW are not supported on 7210 SAS devices.
A VPLS context is used to provide the backbone switching component. The white circle marked
B, referred to as backbone-VPLS (B-VPLS) operates on backbone MAC addresses providing a
core multipoint infrastructure that may be used for one or multiple customer VPNs. Alcatel-
Lucent’s B-VPLS implementation allows the use of native PBB infrastructures.
Note: 7210 implementation allows the use of only native PBB over Ethernet infrastructures.
Another VPLS context (I-VPLS) can be used to provide the multipoint I-component functionality
emulating the ELAN service (refer to the triangle marked “I” in Figure 61). Similar to B-VPLS, I-
VPLS inherits from the regular VPLS and native Ethernet (SAPs) handoffs accommodating this
way different types of access: for example, direct customer link, QinQ or HVPLS.
Payload
Ethertype
Ethertype
Ethertype
802.1ad
22B
(No FCS/Preamble)
Ethertype
2-4
1
8 654 32 1
1
2-4 5-10 11-16
I-SID
I-PCP Res2
I-DEI
Res1
NCA
C-DA C-SA
2+2
Octets
Bits
6+6
Ethertype
C-VID
S-VID
I-TAG
C-SA
C-DA
B-SA
B-VID
B-DA
OSSG192
To Next Page
Loading...
