The access SAPs that specify VLAN range values (using the connection profile) are only allowed in an Epipe service. The system allows only one range SAP in an Epipe service, and fails any attempt to configure more than one. Range SAPs can only be configured on access ports. The other endpoint in the Epipe service has to be a Q.* access SAP or a spoke-SDP (PW) in network mode.
The spoke-SDP processing and forwarding behavior for packets received on range SAPs are as follows:
No VLAN tags are removed/stripped on ingress of the access dot1q SAPs using VLAN range connection profile.
When the other endpoint in the service is configured to be an Q1.* access SAP, 7210 adds another tag to the packet and forwards it out of that SAP.
If the other endpoint in the service is configured to be a spoke-SDP whose vc-type is set to vc-ether, the 7210 SAS adds the appropriate MPLS PW and LSP encapsulations and forwards it out of the SDP.
In the reverse direction, when the other endpoint is a Q1.* SAP and a packet is received on it, the 7210 SAS removes the outermost VLAN tag and forwards the packet out of the access dot1q SAP using VLAN ranges.
When the other endpoint is a spoke-SDP (whose vc-type is set to vc-ether), the 7210 SAS removes the MPLS PW and LSP encapsulation and forwards the packet out of the access dot1q SAP using VLAN ranges.
The system does not check if the VLAN in the packet matches the VLAN IDs of the dot1q access SAPs configured in the service.
ACLs, QoS, hardware, accounting, and mirroring are supported as follows:
For ACLs, filter policies are supported on SAP ingress. In 7210 SAS-T operating in access-uplink mode, IP criteria and MAC criteria-based filter policy is supported with access SAPs.
For more information about ACLs on range SAPs, refer to the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
In 7210 SAS devices operating in network mode, only MAC criteria-based filter policy is supported with access SAPs.
For more information about ACLs on range SAPs, refer to the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
For QoS, ingress classification and hierarchical metering are supported for SAP ingress. On the 7210 SAS-T, egress per port queues and shaping are supported. On the 7210 SAS-Mxp, egress per SAP queues and shaping are supported:
SAP ingress classification criteria that is available for use with VLAN range SAPs is similar to that available for other SAPs supported in an Epipe service. Dot1p-based ingress classification uses the dot1p bits in the outermost VLAN tag for matching. On access egress, dot1p received from the SDP (on a network port) from another access port is preserved.
The amount of hardware resources (such as CAM entries used for matching in QoS classification and ACL matching, meters used in SAP ingress policy, and others), consumed by a single range SAP, are equivalent to the amount of resources consumed by a single SAP that specifies a single VLAN ID for service identification. That is, the hardware has the ability to match a range of VLAN values, and therefore uses X resources for a SAP using a VLAN range, instead of X✕n, where n is the number of VLANs specified in the range and X is the amount of QoS or ACL resources needed.
Ingress accounting support is similar to the support available for other SAPs in an Epipe service. The count of packets or octets received from individual VLANs configured in the connection profile is not available. No support for Egress SAP statistics and accounting is available.
Mirroring is supported. In network mode, the use of service resiliency mechanisms, such as MC-LAG and Epipe PW redundancy, is supported.