Default SAPs on a QinQ port (supported only on 7210 SAS devices configured in access-uplink mode)

Default QinQ SAPs (notation *.*) are used in ring ports to avoid the need to configure services on all the intermediate nodes in the ring that are transiting the service. Default QinQ SAPs match all VLAN-tagged traffic that is not classified into any other SAP configured on the same port. Only one Epipe service with default QinQ SAPs is needed for transit service traffic on access-uplink ports.

Default QinQ SAPs are only allowed on access-uplink ports and access ports. A default QinQ SAP can coexist with a 0.* SAP on an access-uplink or access port. A default QinQ SAP accepts only tagged packets. Untagged packets or priority-tagged packets are not accepted on default QinQ SAPs.

When an Epipe service with default QinQ SAPs on the ring ports is used for transit traffic in a ring deployment, no protection mechanism (for example, STP or G.8032) is supported for default QinQ SAPs. The upstream or head-end node on which the service originates must ensure that the correct path on the ring is selected using either G.8032 or STP.

When a VPLS service with default QinQ SAPs on the ring ports is used for transit traffic in a ring deployment, users can use either G.8032 or M-VPLS with xSTP for ring protection. When using G.8032, the state of the default QinQ SAPs in the VPLS service can be managed using a separate G.8032 control instance.

Note:

A G.8032 control instance cannot use default QinQ SAPs.

A default QinQ SAP is available for use only in an Epipe and a VPLS service created with the svc-sap-type parameter set to null-star. A default QinQ SAP can be configured along with other SAPs allowed in the same service (that is, service with the svc-sap-type parameter set to null-star).

The following features are available for use with default QinQ SAPs configured in Epipe and VPLS service (unless explicitly specified, the following features are applicable for both Epipe and VPLS service).

The following features are available for default QinQ SAPs on either access ports or access-uplink ports:

The following features are available for default QinQ SAPs created on access-uplink port:

The following features are available for default QinQ SAPs created on access ports: