policy class-map—Map forwarding classes to output queues (on vEdge routers only). When you are configuring QoS policy, you refer to the forwarding class mappings when you configure a QoS scheduler.
Class mappings can apply to unicast and multicast traffic.
vManage Feature Template
For vEdge routers:
Configuration ► Policies ► Localized Policy
policy class-map class class-name queue number
- Class Mapping to Output Queue
- class class-name queue number
Map a class name to an interface queue number. The class name can be a text string from 1 to 32 characters long.
On hardware vEdge routers and Cloud vEdge virtualized routers, each interface has eight queues, numbered from 0 through 7. Queues 1 through 7 are available for data traffic, and the default scheduling method for these seven queues is weighted round-robin (WRR). Queue 0 is reserved, and is used for both control traffic and low-latency queuing (LLQ). For LLQ, any class that is mapped to queue 0 must also be configured to use LLQ; 100 percent of control traffic is transmitted.
In Releases 17.2 and earlier, on Cloud vEdge virtualized routers, each interface has four queues, numbered from 0 through 3. Queue 0 is reserved for control traffic, and queues 1, 2, and 3 are available for data traffic. The scheduling method for all four queues is WRR. LLQ is not supported.
Map forwarding classes:
vEdge# show running-config policy class-map policy class-map class be queue 2 class af1 queue 3 class af2 queue 4 class af3 queue 5 ! !
Command introduced in Viptela Software Release 14.1.
In Release 14.2, the LLQ queue changed from queue 1 to queue 0. The software supports only one queue for LLQ, and it must be queue 0.
In Release 16.3, add support for multicast traffic and for vEdge Cloud routers.
In Release 17.2.2, vEdge Cloud routers support eight queues, with queue 0 reserved for LLQ.