QinQ SAP configuration restrictions for 7210 SAS in network mode only

The following are the QinQ access SAP configuration guidelines for 7210 SAS in network mode only:

• Tagged packets received on SAPs configured in a service in which a QinQ SAP is also in use are processed (not applicable when a QinQ SAP is not provisioned in a service).

• When a QinQ SAP is configured in a service, the number of VLAN tags in the packets received on null SAP, dot1q SAP, and QinQ SAP configured in the same service should match the number of VLAN tags implied by the port encapsulation mode. Packets that do not match are dropped by the hardware. That is, packets received with more than two VLAN tags on a QinQ SAP are dropped, packets received with more than one VLAN tag on a dot1q SAP are dropped, and packets received with tags (even packets with a priority tag) on a null SAP are dropped. In this document, such packets are referred to as extra-tag packets.

• When a QinQ SAP is configured in a service, the number of VLAN tags in the packets received on the VC/pseudowire of type VC-VLAN should be exactly one and packets received on the VC/pseudowire of type VC-Ether-should contain no tags (not even priority tags). If either case, packets that contain more VLAN tags than the number specified previously are dropped. In this document, such packets are referred to as extra-tag packets.

• The system provides a limited number of counters for the extra-tag packets dropped on SAP ingress. These counters are intended for diagnostic use.

  The following table describes the SAP types allowed in a service when QinQ SAP is in use.

  Table: SAP types in a service when QinQ SAP is in use (network mode operation)

  SAP configured in the service	SAPs not allowed for configuration in same service
  QinQ	Q.* SAP, Dot1q default SAP
  Q.*	Q1.Q2
  Dotq1 default SAP	Q1.Q2

A 0.* QinQ SAP configured in the service only accepts untagged or priority-tagged packets, regardless of whether a QinQ SAP is configured in the service.