Processing Behavior For Saps Using Vlan Ranges In Network Mode - Alcatel-Lucent 7210 SAS M Service Manual

Processing behavior for SAPs using VLAN ranges in network
mode
•
•
•
•
•
7210 SAS M Services Guide
The access SAPs that specifies VLAN range values (using connection-profile) is allowed
only in an E-Pipe service. The system allows only one range SAP in an Epipe service. It
will fail any attempt to configure more than one range SAP in an Epipe service. Range
SAP can be configured only 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 listed below: 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, 7210 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, 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), 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.
Filter policies are supported on SAP ingress. In 7210 SAS-M access-uplink mode, IP
criteria and MAC criteria based filter policy is available for use with access SAPs. In
7210 SAS-M network mode, only MAC criteria based filter policy is available for use
with access SAPs.
QoS – Ingress classification, metering with hierarchical metering, marking, queuing and
shaping for SAP ingress and SAP egress. On egress per port queues and shaping is
available on 7210 SAS-M.
→ SAP ingress classification criteria 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 match, meters used in SAP ingress policy, and others.) consumed
by a single range SAP is equivalent to the amount of resources consumed by a single SAP
that specifies a single VLAN ID for service identification. In other words, the hardware
has the ability to match a range of VLAN values and hence 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. Count of packets or octets received from individual VLANs configured in the
Virtual Leased Line Services
Page 165