Virtual Private LAN Services
7750 SR OS Services Guide Page 811
• Ingress PE, ingress I-SAP case with force-qtag-forwarding enabled under PBB Epipe or
IVPLS
The QTAG is inserted automatically right after CMAC addresses; an ethertype value of
8100 is used.
→ Case 1: SAP type = null/dot1q default (1/1/1 or 1/1/1.*) so there is no service
delimiting tag used and stripped on the ingress side.
− VLAN and Dot1p+DE bits on the inserted QTAG are set to zero regardless of
ingress QoS policy
→ Case 2: SAP type = dot1q or qinq default (1/1/1.100 or 1/1/1.100.*) so there is a
service delimiting tag used and stripped.
− The service delimiting QTAG (dot1p + DE bits and VLAN) is copied as is in the
inserted QTAG.
→ Case 3: SAP type = qinq (1/1/1.100.10) so there are two service delimiting tags used
and stripped.
− The service delimiting QTAG (VLAN and dot1p + DE bits) is copied as is from
the inner tag in the inserted QTAG.
• Ingress PE, ingress I-SDP/PW case with force-qtag-forwarding enabled under PBB
Epipe or IVPLS
The QTAG is inserted automatically right after CMAC addresses; an ethertype value of
8100 is used.
→ Case 1: SDP vc-type = Ethernet (force-vlan-vc-forwarding= not supported for I-PW)
so there is no service delimiting tag stripped on the ingress side.
− VLAN and Dot1p+DE bits on the inserted QTAG are set to zero regardless of
ingress QoS policy
→ Case 2: SDP vc-type = Ethernet VLAN so there is a service delimiting tag stripped.
− VLAN and Dot1p + DE bits on the inserted QTAG are preserved from the service
delimiting tag.
PBB packets are tunneled through the core the same way for native ETH/MPLS cases.
To Next Page
Loading...
