[no] sap-ingress policy-id [create]
config>qos
Supported on all 7210 SAS platforms as described in this document
This command is used to create or edit the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement service packets receive when they ingress a SAP. SLA enforcement requires the definition of meters/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/meter that all ingress traffic flows through. Complex policies have multiple meters/queues combined with classification entries that indicate which meter/queue a packet flows though.
Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. Meters/ queues defined in the policy are not instantiated until a policy is applied to a service SAP.
Depending on the support available on different 7210 SAS platforms, SAP ingress policies can be defined with either dot1p, IP DSCP, IP headers, MAC headers, or all as the match criteria.
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. The work area 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 a SAP ingress policy can be associated with a SAP, resources must be allocated using the config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command. See Resource allocation for service ingress QoS policy classification rules for information about resource allocation. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about system resource allocation and examples for this CLI command.
On the 7210 SAS-D and 7210 SAS-Dxp, only meters are supported on service ingress for rate enforcement. These platforms do not support service ingress queues.
On the 7210 SAS-D and 7210 SAS-Dxp, the user has the option to use dot1p, IP DSCP, IPv4 and IPv6 criteria, and MAC criteria.
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 restores the factory defaults to policy ID1.
policy-id 1
Specifies a policy ID that uniquely identifies the policy.
Specifies to create a SAP ingress policy.
scope {exclusive | template}
no scope
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command configures the service ingress QoS policy scope.
The no form of this command reverts the scope of the policy to the default.
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 will become available for assignment to another exclusive SAP.
Specifies that the policy can be applied to multiple SAPs on the router. An error is generated when scope template is changed to scope exclusive for default policies.
default-fc fc
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command configures the default FC for the policy. If an ingress packet does not match a higher priority (more explicit) classification command, the default FC is associated with the packet. Unless overridden by an explicit FC classification rule, all packets received on an ingress SAP using this ingress QoS policy is classified to the default FC.
The default FC is best effort (be). The default-fc settings are displayed in the show configuration and save output, regardless of whether the detail keyword is included in the show command.
The in and out parameters are mutually exclusive following the profile classification keyword. Either in or out must be specified when the profile keyword is present.
be
Specifies the FC name for the queue/meter. The value specified for fc must be one of the predefined FCs in the system.
[no] fc fc-name [create]
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
The fc command creates a class instance of the FC fc-name. After the fc-name is created, classification actions can be applied and then used in match classification criteria.
The no form of this command removes all explicit queue mappings for fc-name forwarding types. The queue mappings revert to the default meters for fc-name.
Specifies the FC name for the queue. The value specified for the fc-name must be one of the predefined FCs for the system.
Keyword to create a class instance of the FC.
[no] ip-mac-match {ip-first | mac-first}
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command enables the user to match on both IP and MAC criteria in a SAP ingress policy. If this command is not executed, the software does not allow for configuration of both IP and MAC criteria in a SAP ingress policy. In other words, 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 the other way around. For example, if ip-first is configured, all the IP criteria entries are compared for matches first; if there are no matches, then MAC criteria entries are compared for matches.If a match is found, no further matches are performed and the actions associated with the matched entry are taken.
The no form of the command reverts to the default value.
no ip-mac-match
Specifies to match all the IP criteria entries first before matching any of the MAC entries.
Specifies to match all the MAC criteria entries first before matching any of the IP entries.
[no] ip-criteria [any | dscp-only] policy id
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command selects the ingress meter and corresponding FC 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 Resource allocation for service ingress QoS policy classification rules for more information.
This command is used to enter the context to create or edit policy entries that specify IP criteria DiffServ code point.
The 7210 SAS 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.
The no form of this command deletes all the entries specified under this node. After an IP criteria entry is 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 (Example - IP source, IP destination, IP protocol fields can be used) for matching
Specifies that entries can use the IP DSCP field or IP precedence field.
Specifies the policy ID.
[no] ipv6-criteria [any | dscp-only] policy-id
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command selects the appropriate ingress meters and corresponding FC 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 DSCP.
The 7210 SAS 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-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C 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. After an IPv6 criteria entry is removed from a SAP ingress policy, the IPv6 criteria is removed from all services where that policy is applied.
Specifies that entries can use any of the fields available under ipv6-criteria (Example - IPv6 source, IPv6 destination, IPv6 protocol fields can be used) for matching
Specifies that entries can use the IP DSCP field or IPv6 precedence field.
Specifies the policy ID.
[no] mac-criteria [any | dot1p-only] policy id
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command selects the appropriate ingress meters and corresponding FC for matched traffic.
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 Resource allocation for service ingress QoS policy classification rules for more information about SAP ingress resource allocation.
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.
The no form of this command deletes all the entries specified under this node. After a MAC criteria entry is removed from a SAP ingress policy, the MAC criteria is removed from all services where that policy is applied.
dot1p-only
Specifies that entries can use the other MAC header fields for matching.
Specifies that entries can use only the dot1p field.
Specifies the policy ID.
num-qos-classifiers [num-resources] [ipv6 | no-ipv6]
config>qos>sap-ingress>num-qos-classifiers
Supported on all 7210 SAS platforms as described in this document
This command configures the number of classifiers the SAP ingress Qos policy can use. This parameter cannot be modified when it is associated with a SAP.
The num-resources parameter also determines the maximum number of meters that are available to this policy. The maximum number of meters available for use by the FCs (FC) defined under this policy is equal to half the value specified in num-resources parameter (maximum of 32). Any of these meters are 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 ipv6 keyword indicates a plan to use ipv6-criteria, and the resources needed for this SAP ingress QoS policy must be allocated to the slice assigned to IPv6 criteria.
num-qos-classifiers 2 no-ipv6
Specifies the number of resources planned for use by this policy. The value must be a multiple of two.
Specifies to use ipv6-criteria. The software must allocate resources from the chunks alloted to IPv6 criteria.
Specifies to not use ipv6-criteria. Resources are then allocated from the chunk alloted to either IPv4 criteria or MAC criteria, depending on what criteria the user uses.