Alcatel-Lucent 7750 SR Manual page 810

PBB Features
right after the CMAC addresses using the configured QTAG. The dot1p, DE bits from the specified
outer/inner customer QTAG will be copied in the newly added tag.
Once the force-qtag-forwarding is enabled in one IVPLS/PBB Epipe instance, it will be enabled in
all of the related instances.
At the remote PBB PE/BEB on the egress SAPs or SDPs, the first QTAG after the CMAC
addresses will be removed and its dot1p, DE bits will be copied in the newly added customer
QTAGs.
Configuration Examples
This section gives usage examples for the new commands under PBB Epipe or IVPLS instances.
PBB IVPLS usage:
configure service vpls 100 ivpls
PBB Epipe Usage:
configure service epipe 200
Details Solution Description
Figure 120
core and an egress PBB PE - let us consider the generic use case where:
1. the packet arrives on the ingress PBB PE on an I-SAP or an I-SDP binding/PW and it is
assigned to a PBB service instance (Epipe/IVPLS)
2. goes next through a PBB core (native Ethernet B-SAPs or PW/MPLS based B-SDP)
3. lastly, egresses at another PBB PE through a PBB service instance on either an I-SAP or I-
SDP binding/PW.
Similar to the Ethernet-VLAN VC Type, the following packet processing steps apply for different
scenarios.
Page 810
sap 1/1/1:101
pbb
backbone-vpls 10 isid 100
force-qtag-forwarding
sap 1/1/1:201
pbb
tunnel 10 backbone-dest-mac ab-bc-cd-ef-01-01 isid 200
force-qtag-forwarding
depicts a specific use case. Keeping the same topology - an ingress PBB PE, a PBB
7750 SR OS Services Guide