Configuring VLAN Shaping
The following section explains the configuration of basic infrastructure to provide the functionality of queuing per services on an interface. These queues will support all the possible QoS treatment via egress queuing policy-map configurations. Services can be mapped using service-template or via match vlan. Whenever we will be matching a service in a class inside a policy and attach it on interface, 4 new queues will be created for these services. User can create max 3-level scheduling hierarchy for each of the services using these policy-maps.
Policy-map attached to interface will be referred as "L0" level policy-map. Each child policy-map that will be added, will be at one incremented level i.e. L0-level's child policy-map will be L1 level policy-map and L1-level's child will be L2 policy-map. This is the max 3-level hierarchy supported in user defined policy-map.
Class-default-q is a self-created class map as part a policy map. There are two types of class-default-q CMAPs:
• When a policy is applied on an interface, the class-default-q represents the port default queues. If the operator wants to shape or apply certain TailDrop/WRED properties on the port queues, it has to be applied on the class-default-q cmap at Level 0.
• When a child policy is attached to a cmap with some service match criteria (match service-template/vlan), the class-default-q cmap in the child policy represents the queues which are left unmatched in rest of the cmaps of the child policy.
Last modified date: 10/20/2023