NX-OS and the 7K runs standard MQC QoS architecture. Classification can be done on:
ACL Classification
DSCP Classification
IP Precedence Classification
Protocol Classification
QoS Group Classification
Discard Class Classification
Layer 3 Packet Length Classification
CoS Classification
IP RTP Classification
Class Map Classification
NX-OS also supports marking, policing and queuing and scheduling.
There are two types of class maps, policy maps, and service polices are:
Type queuing: Queuing objects define interface queuing policies (which is what i think you are referring to)
Type qos: QoS objects define forwarding engine policies:
If no type specified, type qos is assumed
Type Queueing class maps are pre-defined based on the physical hardware possibilities (different line cards, different capabilities). The assignment of these pre-defined class maps may be attached to policy maps within each non-default VDC. In order to create customized Type Queueing class maps, the configuration must be completed within the default VDC context.
Note: Type Queueing class maps may only have Class of Service (CoS) assigned to the policy maps.
Class-map configuration for type queuing are as follows:
class-map type queuing match-any (class-queuing-name): Creates or accesses the class map
match parameter: Which parameter the packet needs to match against
HTH
---
Posted by WebUser Adriaan Steyn
