[no] sap-ingress policy-id [create] [use-svc-meter-pool]
config>qos
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command creates or edits the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement service packets receive as they ingress a SAP. SLA enforcement is accomplished through the definition of meters and queues (depends on the support available on a platform) that have Forwarding Class (FC), Committed Information Rate (CIR), Peak Information Rate (PIR), Committed Burst Size (CBS), and Maximum Burst Size (MBS) characteristics. The simplest policy defines a single queue or meter that all ingress traffic flows through. Complex policies have multiple meters/queues combined with classification entries that indicate which meter or queue a packet will flow though.
Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. Meters defined in the policy are not instantiated until a policy is applied to a service SAP.
Only one service ingress policy can be provisioned. The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other policy is explicitly specified. The system SAP ingress policy can be modified but not deleted. The no sap-ingress command restores the factory default settings when used on policy-id 1. See Default SAP ingress policy for more information.
Any changes made to the existing policy, using any of the sub-commands are applied immediately to all services where this policy is applied. For this reason, when many changes are required on a policy, it is recommended that the policy be copied to a work area policy ID. That work-in-progress policy can be modified until complete and then written over the original policy ID. Use the config qos copy command to maintain policies in this manner.
Before associating a SAP ingress policy with a SAP, resources must be allocated using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command. For more information about this CLI command and resource allocation, see Service ingress QoS policies and the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.
Only meters with the SAP ingress policy are supported on 7210 SAS-T (access-uplink and network mode), 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE; ingress queues are not supported.
The no form of this command deletes the SAP ingress policy. A policy cannot be deleted until it is removed from all services where it is applied. The system default SAP ingress policy is a special case; the no command reverts the factory defaults to policy ID 1.
Default SAP ingress policy ID 1 is used in low-sap-scale mode. See the 7210 SAS-Mxp, S, Sx, T Services Guide for more information about low-sap-scale mode and high-sap-scale mode.
Specifies the policy.
Keyword to create a SAP ingress policy.
Specifies that the SAP ingress policy uses policers or meters from the service-meter pool. When this parameter is specified, an FC meter map is attached to the policy by default. Only table-based classification policies are used for classification; the CAM-based classification entries are ignored. If this parameter is not specified, the meter resources for the SAP ingress policy are allocated from the CAM-based meter resource pool. This parameter is only supported on 7210 SAS-Mxp.
scope {exclusive | template}
no scope
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures the Service Ingress QoS policy scope as exclusive or template.
The no form of this command sets the scope of the policy to the default of template.
template
Specifies that the policy can only be applied to one SAP. If a policy with an exclusive scope is assigned to a second SAP an error message is generated. If the policy is removed from the exclusive SAP, it becomes available for assignment to another exclusive SAP.
Specifies that the policy can be applied to multiple SAPs on the router.
Default QoS policies are configured with template scopes. An error is generated when the template scope parameter to exclusive scope on default policies is modified.
table-classification-criteria table-classification-criteria
config>qos>sap-ingress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command allows the user to choose the dot1p or DSCP classification policies to classify the traffic to an FC. The option to select either dot1p, DSCP, or both, applies only to SAPs configured in Layer 2 services (Epipe and VPLS). It is not applicable to SAPs configured in Layer 3 services (IES, VPRN and RVPLS). See Table-based IP DSCP and dot1p classification policy commands for SAP ingress (7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12) for more information.
The following options can be used to configure the classification policy.
If none is configured, use default-fc fc-name profile out (from the SAP ingress policy).
If use-dscp is configured, use the following policies:
DSCP classification policy for IP packets
default-fc fc-name profile out (from the SAP ingress policy) for non-IP packets
If use-dot1p is configured, use the following policies:
dot1p classification policy for all tagged packets (IP and non-IP)
default-fc fc-name profile out (from the SAP ingress policy) for untagged packets
If both-dscp-dot1p is configured, use the following policies:
DSCP classification policy for IP packets
dot1p classification policy for non-IP tagged packets
default-fc fc-name profile out (from the SAP ingress policy) for non-IP untagged traffic
table-classification-criteria both-dscp-dot1p
Specifies the table classification criteria to use.
default-fc fc
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures the default forwarding class for the policy. If an ingress packet does not match a higher priority (more explicit) classification command, the default forwarding class will be associated with the packet. Unless overridden by an explicit forwarding class classification rule, all packets received on an ingress SAP using this ingress QoS policy will be classified to the default forwarding class.
The default forwarding class is best effort (be). The default-fc settings are displayed in the show configuration and save output regardless of inclusion of the detail keyword.
be
Specifies the forwarding class name for the queue or meter. The value given for fc must be one of the predefined forwarding classes in the system.
dscp-classification policy-id
no dscp-classification
config>qos>sap-ingress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command associates a DSCP classification policy with a SAP ingress QoS policy.
The no form of this command removes the DSCP classification policy from its association with the SAP ingress QoS policy.
no dscp-classification
Specifies the policy ID that uniquely identifies the DSCP classification policy.
[no] fc fc-name [create]
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command creates a class instance of the forwarding class fc-name. Once the fc-name is created, classification actions can be applied and can be used in match classification criteria.
The no form of this command removes all the explicit queue mappings for fc-name forwarding types. The queue mappings revert to the default meters for fc-name.
Specifies the forwarding class name for the queue. The value given for the fc-name must be one of the predefined forwarding classes for the system.
Keyword to create a forwarding class.
[no] ip-mac-match {ip-first | mac-first}
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command must be executed if user intends to match on both IP and MAC criteria in a SAP ingress policy. If this command is not executed software does not allow for configuration of both IP and MAC criteria in a SAP ingress policy. That is, without this command in a SAP ingress policy IP and MAC criteria are mutually exclusive.
The user also has the option to specify if all the IP criteria entries configured in the policy need to be matched first followed by all the MAC criteria entries or vice-versa. That is, if ip-first is configured all the IP criteria entries are matched and only if there are no matches in the MAC criteria entries are matched. If a match is found no further matches are done and the actions associated with the matched entry are taken.
no ip-mac-match
Keyword to match all the IP criteria entries first before matching any of the MAC entries.
Keyword to match all the MAC criteria entries first before matching any of the IP entries.
[no] ip-criteria policy id [any | dscp-only]
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command creates or edits policy entries that specify IP criteria DiffServ code point. IP criteria-based SAP ingress policies are used to select the appropriate ingress meter and corresponding forwarding class for matched traffic.
The user can specify either any or dscp-only as the sub-criteria. The sub-criteria determines what fields can be used to match traffic. The resource allocation for classification is affected by the sub-criteria in use. See Table: SAP ingress resource allocation and match criteria types for more information.
The 7210 SAS OS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.
When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.
The no form of this command deletes all the entries specified under this node. Once IP criteria entries are removed from a SAP ingress policy, the IP criteria is removed from all services where that policy is applied.
dscp-only
Specifies that entries can use any of the fields available under ip-criteria for matching; for example, IP source, IP destination, IP protocol fields can be used.
Specifies that entries can use the IP DSCP field or IP precedence field.
Specifies the policy.
[no] ipv6-criteria policy-id [any | dscp-only]
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command selects the appropriate ingress meters and corresponding forwarding class for matched traffic.
This command is used to enter the node to create or edit policy entries that specify IPv6 criteria such as IP quintuple lookup or DiffServ code point.
The 7210 SAS OS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason entries must be sequenced correctly from most to least explicit.
Before associating a SAP ingress policy configured to use IPv6 criteria with a SAP, resources must be allocated using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv6-ipv4-match-enable command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information about this CLI command and resource allocation.
The no form of this command deletes all the entries specified under this node. Once ipv6-criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.
When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.
Specifies that entries can use any of the fields available under ipv6-criteria for matching; for example, IPv6 source, IPv6 destination, IPv6 protocol fields can be used.
Specifies that entries can use the IP DSCP field or IPv6 precedence field.
Specifies the policy.
[no] mac-criteria policy id [any | dot1p-only]
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command selects the appropriate ingress meters and corresponding forwarding class for matched traffic.
The user can specify either any or dot1p-only as the sub-criteria. The sub-criteria determines what fields can be used to match traffic. The resource allocation for classification is affected by the sub-criteria in use. See Table: SAP ingress resource allocation and match criteria types for more information.
This command is used to enter the node to create or edit policy entries that specify MAC criteria.
The 7210 SAS OS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit.
When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.
The no form of this command deletes all the entries specified under this node. Once mac-criteria entries are removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is applied.
any
Specifies that entries can use any of the fields available under mac-criteria; for example, MAC source, MAC destination, and MAC Ethertype fields can be used)
Specifies that entries can use only the dot1p field.
Specifies the policy.
num-qos-classifiers [num-resources] [ipv6 | no-ipv6]
no num-qos-classifiers
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures the number of classifiers the SAP ingress Qos policy can use. A user cannot modify this parameter when it is in use (that is, applied to a SAP).
The num-resources parameter determines the maximum number of meters that are available to this policy. The maximum number of meters available for use by the forwarding classes (FC) defined under this policy is equal to half the value specified in the parameter num-resources. Any of these meters is available for use to police unicast or multipoint traffic. Any of these meters is available for use by more than one FC (or a single meter is available for use by all the FCs).
The keyword ipv6 allows users to indicate that they plan to use the ipv6-criteria and the resources needed for this SAP ingress QoS policy must be allocated for the chunk allocated to IPv6 criteria.
On the 7210 SAS-Mxp, this parameter is ignored if the use-svc-meter-pool parameter is set.
num-qos-classifiers 2 no-ipv6
Specifies the number of resources planned for use by this policy, expressed as multiple of 2.
Specifies that the user intends to use the ipv6-criteria and software must allocate resources from the chunks alloted to IPv6 criteria.
Specifies that the user intends to use the ipv6-criteria. Resources are then allocated from the chunk alloted to either IPv4 criteria or MAC criteria, depending on what criteria the user uses.