action [fc fc-name]
no action
config>qos>sap-ingress>ip-criteria>entry
config>qos>sap-ingress>mac-criteria>entry
Supported on all 7210 SAS platforms as described in this document
This mandatory command associates the FC with specific IP or MAC criteria entry ID. The action command supports setting the FC parameter. Packets that meet all match criteria within the entry have their FC overridden based on the parameters included in the action parameters.
The action command must be executed for the match criteria to be added to the active list of entries.
Each time action is executed on a specific entry ID, the previously entered values for fc fc-name are overridden with the newly defined parameters.
The no form of this command removes the entry from the active entry list. Removing an entry on a policy immediately removes the entry from all SAPs using the policy. All previous parameters for the action are lost.
action specified by the default-fc command
Specifies the FC name for the queue. When a packet matches the rule, the FC is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the FC is not explicitly defined in the rule, the FC is inherited based on previous rule matches.The value specified for fc fc-name must be one of the predefined FCs in the system.
[no] entry entry-id [create]
config>qos>sap-ingress>ip-criteria
config>qos>sap-ingress>mac-criteria
Supported on all 7210 SAS platforms as described in this document
This command creates or edits an IP or MAC criteria entry for the policy. Multiple entries can be created using unique entry-id numbers.
The list of flow criteria is evaluated in a top-down fashion with the lowest entry ID at the top and the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches the information in the egress packet, the system stops matching the packet against the list and performs the matching reclassification actions specified by the entries. If none of the entries match the packet, the IP flow reclassification list has no effect on the packet.
An entry is not populated in the list unless the action command is executed for the entry. An entry that is not populated in the list has no effect on egress packets. If the action command is executed without any explicit reclassification actions specified, the entry is populated in the list allowing packets matching the entry to exit the list, preventing them from matching entries lower in the list. Because this is the only flow reclassification entry that the packet matched and this entry explicitly states that no reclassification action is to be performed, the matching packet is not reclassified.
The no form of this command removes the specified entry from the policy. Entries removed from the policy are immediately removed from all services where that policy is applied.
Specifies a match criterion and the corresponding action. It is recommended that multiple entries be assigned entry IDs in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.
An entry may not have any match criteria defined (in which case, everything matches) but it must have at least the command action fc for it to be considered complete. Entries without the action command are considered incomplete and are rendered inactive.
This keyword is required when creating a flow entry if the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object. This keyword is not required when the protection is disabled. The keyword is ignored when the flow entry already exists.
[no] match [protocol protocol-id]
config>qos>sap-ingress>ip-criteria>entry
Supported on all 7210 SAS platforms as described in this document
This command configures match criteria for SAP QoS policy matches. When the match criteria are satisfied, the action associated with the match criteria is executed.
If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied (and function) before the action associated with the match will be executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry.
Specifies an IP protocol to be used as an ingress or egress network QoS policy match criterion.
The protocol type is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), and UDP(17).
match
no match
config>qos>sap-ingress>mac-criteria>entry
Supported on all 7210 SAS platforms as described in this document
This command creates or edits the match MAC criteria for ingress SAP QoS policy match criteria. When the match criteria are satisfied the action associated with the match criteria is executed.
If more than one match criterion (within one match statement) is configured, all criteria must be satisfied (and function) before the action associated with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
The no form of this command removes the match criteria for the entry-id.
match [next-header next-header]
no match
config>qos>sap-ingress>ipv6-criteria>entry
Supported on all 7210 SAS platforms as described in this document
This command configures match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria are satisfied, the action associated with the match criteria is executed.
If more than one match criterion (within one match statement) is configured, all criteria must be satisfied (and function) before the action associated with the match is executed.
A match context can consist of multiple match criteria, but multiple match statements cannot be specified per entry.
The no form of this command removes the match criteria for the entry-id.
Specifies the next header to match.
The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17).