Sequencing Of Ingress Traffic Actions - Cisco Nexus 7000 Series Configuration Manual

Sequencing of Ingress Traffic Actions

Note You can apply only ingress traffic actions for type QoS policies on Layer 2 interfaces. You can apply both
ingress and egress traffic actions for type QoS policies on Layer 3 interfaces
Sequencing of Ingress Traffic Actions
The sequence of QoS actions on ingress traffic is as follows:
1. Queuing and scheduling
2. Mutation
3. Classification
4. Marking
5. Policing
Sequencing of Egress Traffic Actions
The sequencing of QoS actions on egress traffic is as follows:
1. Classification
2. Marking
3. Policing
4. Mutation
5. Queuing and scheduling
Note
Mutation occurs much closer to the beginning of the traffic actions on the ingress packets, and any further
classification and policing is based on the changed QoS values. Mutation occurs at the end of the traffic actions
on the egress packets, right before queuing and scheduling.
High Availability Requirements for QoS Features
The Cisco NX-OS QoS software recovers its previous state after a software restart, and it is capable of a
switchover from the active supervisor to the standby supervisor without a loss of state.
Note
For complete information on high availability, see the Cisco Nexus 7000 Series NX-OS High Availability and
Redundancy Guide.
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
6
Overview