Overview of QoS policies on 7210 SAS-T in network mode

QoS policies are applied on service ingress, access port egress, network port ingress and egress, and on network IP interface ingress when configured to operate in network mode.

These policies allow user to configure the following:

classification rules to map traffic to FCs
FC association with meters and meter parameters used for policing (rate-limiting)
queuing parameters for shaping
QoS marking and interpretation

Several types of QoS policies exist:

service ingress policies for access SAP ingress

Service ingress QoS policies are applied to customer-facing SAPs. Traffic that enters through the SAP is classified to map it to an FC. FCs are associated with meters or policers on ingress. The mapping of traffic to meters can be based on combinations of customer QoS marking (IEEE 802.1p bits), IP criteria, and MAC criteria. The characteristics of the FC meters are defined in the policy as to the number of FC meters for unicast traffic and the meter characteristics (such as CIR, PIR, and so on). Each of the FCs can be associated with different unicast parameters. A service ingress QoS policy also defines up to three (3) meters per FC to be used for multipoint traffic for multipoint services. There can be up to 32 meters in total per service ingress QoS policy. In the case of VPLS, four forwarding types (which are not to be confused with FCs) are supported: unicast, multicast, broadcast, and unknown. Multicast, broadcast, and unknown types are flooded to all destinations within the service, while the unicast forwarding type is handled in a point-to-point manner within the service.
access egress policies for access port egress

An access egress policy is analogous to a SAP-egress policy, as defined in the 7x50 SR series of products. The difference is the point of attachment. An access egress policy is applied on the physical port as opposed to the logical port (SAP) for SAP egress policies. It applies to all the SAPs on the port. An access egress QoS policy maps the traffic egressing on the customer-facing ports into various queues and marks the traffic. The FCs are mapped to the queues. There are 8 (eight) queues at the port level. FC-to-queue mapping is static and not configurable. The number of queues is not user-configurable and the software allocates 8 (eight) queues at the port level. An access egress policy also defines how to remark the FC-to-packet header bits (for example, IEEE 802.1p bits in the Layer 2 VLAN header).
network policies for network and hybrid port, ingress and egress

For devices configured to operate in network mode, there are two types of network QoS policies, one applied to a network IP interface and the other is applied to a network port. Network QoS policies are applied to IP interfaces. On ingress, the policy applied to an IP interface maps incoming MPLS LSP EXP values to FC and profile state for the traffic received from the core network. On egress, the policy maps FC and profile state to MPLS LSP EXP values for traffic to be transmitted into the core network. The network policy applied to a network port maps incoming IP packets, DSCP or dot1p values, to the FC and the profile state for the traffic received from the core network. On egress, the policy maps FC and profile state to DSCP and/or dot1p values for IP traffic to be transmitted into the core network.
network-queue policies for network and hybrid port egress

Network queue policies are applied on egress to network ports when operating in network mode. The policies define the FC queue characteristics for these entities. The FCs are mapped to the queues. There are 8 (eight) queues at the port level. FC-to-queue mapping is static and not configurable. The number of queues is not user-configurable and the software allocates 8 (eight) queues at the port level.
port-scheduler policies for access port, network port and hybrid port egress

Port scheduler policies are applied on egress for access, network, and hybrid ports. These policies allow the user to define queue scheduling attributes, such as strict-priority queuing and weighted queuing.
slope policies

Slope policies are applied to the egress queues on the access, network, and hybrid ports. These policies define the WRED congestion management attributes, such as drop probability and thresholds for high-profile and low-profile traffic.
remark policies for access port, network port, and hybrid port egress marking

Remark policies are applied to access ports/SAPs, network ports/IP interfaces, and hybrid ports/SAPs/IP interfaces to configure the marking values for different forwarding classes and profiles.These policies enable marking of packet header QoS fields for packets that are forwarded out of the port, SAP, or IP interface. See Remark policies for more information.

Service ingress, access egress, and network QoS policies are defined with a scope of either template or exclusive. Template policies can be applied to multiple entities (such as SAPs and ports) whereas exclusive policies can only be applied to a single entity.

One service ingress QoS policy can be applied to a specific SAP access egress policy. One access egress QoS policy can be applied to the access port. One network QoS policy can be applied to a specific IP interface or network port, based on the type of network QoS policy, when operating in network mode. One network QoS policy can be applied to an access-uplink port when operating in access-uplink mode. A network QoS policy defines both ingress and egress behavior. One network queue policy can be applied to the network port or a access-uplink port.

If no QoS policy is explicitly applied to a SAP, port, or interface, a default QoS policy is applied.

The following table describes the major functions performed by QoS policies.

Note:

Not all policies are supported on all platforms. See the following sections and chapters for more information.

Table: QoS policy types and descriptions for 7210 SAS-T devices in network mode
Policy type	Applied at…	Description	Section
Service Ingress	SAP ingress	defines up to 16 FC meters and meter parameters for traffic classification defines match criteria to map flows to the meters based on any one of the criteria	Service ingress QoS policies
Access Egress	Access port	defines up to 8 FC queues and queue parameters for traffic classification maps FCs to the queues defines FC-to-remarking values defines CIR levels and PIR weights, which determine how the scheduler prioritizes the queue	Service egress QoS policies on 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
Network (of type ‟ip-interface”)	IP interface	used for classification or marking of MPLS packets at ingress, defines MPLS LSP-EXP-to-FC mapping and 12 meters used by FCs at egress, defines FC-to-MPLS LSP-EXP marking	Network QoS policies in network mode
Network (of type ‟port”)	Network and hybrid ports	used for classification or marking of IP packets at ingress, defines DSCP or dot1p to FC mapping and 8 meters at egress, defines FC-to-DSCP or dot1p marking or both	Network QoS policies in network mode
Network Queue	Network ports and hybrid ports	defines FC mappings to network queues, and queue characteristics for the queues	Network queue policies in network mode
Slope	Access ports, network ports and hybrid ports	enables or disables the high-slope, low-slope, and non-TCP parameters within the egress pool	Slope policy parameters
Port scheduler	Access ports, Network ports and Hybrid ports	defines the parameters for the port scheduler	Port scheduler policies for 7210 SAS-T
Remark (Only on 7210 SAS-T)	Network ports, access ports, and hybrid ports	applied at egress, defines the FC-to-priority bits (DSCP or dot1p or EXP) marking	Remark policies on 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T (network mode)