This section describes the commands you use to configure QOS Differentiated Services (DiffServ).
You configure DiffServ in several stages by specifying three DiffServ components:
1. Class
2. Policy
3. Service-policy
The DiffServ class defines the packet filtering criteria. The attributes of a DiffServ policy define the way the switch processes packets. You can define policy attributes on a per-class basis. The switch applies these attributes when a match occurs.
The following rules apply when you create a DiffServ class:
The following rules apply when you create a DiffServ policy:
A given class definition can contain a maximum of one reference to another class. You can combine the reference with other match criteria. The referenced class is truly a reference and not a copy since additions to a referenced class affect all classes that reference it. Changes to any class definition currently referenced by any other class must result in valid class definitions for all derived classes, otherwise the switch rejects the change. You can remove a class reference from a class definition.
The only way to remove an individual match criterion from an existing class definition is to delete the class and re-create it.
NOTE 1: The mark possibilities for policing include CoS, IP DSCP, and IP Precedence. While the latter two are only meaningful for IP packet types, CoS marking is allowed for both IP and non-IP packets, since it updates the 802.1p user priority field contained in the VLAN tag of the layer 2 packet header.
NOTE 2: Traffic to be processed by the DiffServ feature requires an IP header.
This command sets the DiffServ operational mode to active. While disabled, the DiffServ configuration is retained and can be changed, but it is not activated. When enabled, Diffserv services are activated.
This command sets the DiffServ operational mode to inactive. While disabled, the DiffServ configuration is retained and can be changed, but it is not activated. When enabled, Diffserv services are activated.