Service ingress QoS policies define ingress service FC meters and map flows to the meters. When a service ingress QoS policy is created, it has a single meter defined that cannot be deleted and is used for all the traffic (both unicast and multicast traffic). These meters exist within the definition of the policy, but are instantiated in hardware only when the policy is applied to a SAP. In the case where the service does not have multipoint traffic, the multipoint meters are not instantiated.
In the simplest service ingress QoS policy, all traffic is handled as a single flow and mapped to a single meter, including all flooded traffic. The required elements to define a service ingress QoS policy are the following:
unique service ingress QoS policy ID
QoS policy scope of template or exclusive
number of classification and meter resources to allocate for this policy
allocation of resources from the ingress internal CAM resource pool for use with service ingress QoS policies
Additionally, the allocation of resources to the appropriate classification match criteria.
at least one default FC meter
See Meter/policer parameters for information about the parameters that can be configured for a meter.
Optional service ingress QoS policy elements include the following:
additional unicast meters up to a total of 8 (eight)
additional multipoint meters up to 32
QoS policy match criteria to map packets to an FC
option to use dot1p or IP DSCP table-based classification in Layer 2 services (Epipe and VPLS) on 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
option to use IP DSCP table-based classification in Layer 3 services on the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
option to use meters from either CAM-based meter resource pool or table-based service-meter resource pool on 7210 SAS-Mxp
The following options are available when using resources for classification and policing:
CAM-based classification and policing
Resources for both classification and policing are allocated from the CAM-based classification and meter resource pool. Configure resources from the CAM-based pool using the configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command. The user has the flexibility to use IP criteria (both IPv4 and IPv6) and MAC criteria for classification of traffic flows to an FC (FC). Using this option allows each SAP to define its FC-to-meter map, which is the default option that is enabled when the system boots up using the default configuration. This option is supported on the following platforms: 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T (in network and access-uplink mode).
table-based classification and CAM-based policing
Resources for classification are allocated from the table-based classification pool of resources, and policing resources are allocated from the CAM-based meter resource pool. Configure resources for the CAM-based pool using the configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command. See Service ingress QoS policies for examples that show how to configure this option. Using this option, the classification of traffic flows can be done only using IP DSCP and or dot1p bits. (See Service ingress QoS policies for information about classification support details.) The use of IP and MAC criteria are mutually exclusive. Using this option allows each SAP to define its FC-to-meter map. This option is supported only on the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.
table-based classification and service-meter based policing
Resources for classification are allocated from the table-based classification pool of resources, and policing resources are allocated from the table-based service-meter resource pool. See Service ingress QoS policies for examples that show how to configure this option. With this option, the classification of traffic flows can be done only using IP DSCP or dot1p bits (for classification support details, see Service ingress QoS policies). The use of IP and MAC criteria are mutually exclusive. All SAPs in the node must use a single FC-to-meter map (other than the default). This option is supported only on the 7210 SAS-Mxp.
Each meter can have unique meter parameters to allow individual policing of the flow mapped to the FC. The following figure shows service traffic being classified into three different FCs.
Mapping a flow to an FC is controlled by comparing each packet to the match criteria in the QoS policy. The ingress packet classification to FC requires a provisioned classification policy.