Configuring default QinQ SAPs for Epipe transit traffic in a ring scenario in access-uplink mode

Note:

Default QinQ SAPs are only supported on 7210 SAS platforms operating in the access-uplink mode.

In the following figure, 7210-1 is used to deliver some services to customers connected to the device, and additionally it needs to pass through transit from other nodes on the ring (for example, traffic from 7210-2 to 7210-3 or from 7210-2 to 7750-SR onto the core network).

Figure: Default QinQ SAP for transit traffic in a ring scenario

Without default QinQ SAPs, the user would need to configure a service on 7210-1, with access-uplink SAPs for each service originating on some other node in the ring. With support for default QinQ SAPs, all traffic that does not need to be delivered to any customer service configured on 7210-1 can be switched using the Epipe service.

The following is a sample configuration output:

ALA-1>config>service# epipe 8 customer 1 svc-sap-type null-star create
            sap 1/1/5:*.* create
                statistics
                    ingress
                    exit
                exit
            exit
            sap 1/1/6:*.* create
                statistics
                    ingress
                    exit
                exit
            exit
            no shutdown
        exit