VMware Velocloud SDWAN: Class of Service (CoS)

Today I am going to talk about the Class of service in the VMware Velocloud SDWAN solution. COS is one of the major part in the network where  certain types of traffic are prioritize in the network during periods of congestion. 

As we have multiple kind of traffic in our network like data, voice, video and so on. You can manage traffic by defining Class of Service (CoS) in a private WAN link.

As we discuss earlier in the VMware Velocloud SDWAN solution, DMPO (Dynamic Multipath Optimization) can take CoS into account for both monitoring and application aware routing decisions. DMPO can treat each CoS as a different link and can take granular application-aware decisions for private link with CoS agreements.

Let us suppose we have multiple WAN links on our VeloCloud Edge (VCE) like MPLS and Internet. we can define various COS values, e.g. Cos 1 (CS5, EF Traffic), Cos 2 (AF41, CS4 Traffic), Cos 3(AF21, CS2 traffic)  and internet, So the specific traffic decision can be made to use CoS1,CoS2, CoS3 or Internet.

Fig 1.1- COS operation in Velocloud SDWAN

Configuring COS on VeloCloud Edge

Step 1: When you login to the orchestration, go to the Enterprise Portal, Once you see the enterprise portal, navigate to configure--> Edges and click on the device tab.

Step 2: Here you see WAN Settings section, click Add User Defined WAN Overlay and choose the Link Type as you required and see there are COS values. 

Just see the WAN Overlay settings, click Advanced and select the Configure Class of Service checkbox. When you enable this option, the following settings appear and configure them appropriately. 

Fig 1.2- COS settings on Edge (VCE)

Note: Always map DSCP tags of same IP precedence to the same class of service. A CoS queue can be an aggregate of many classes but DSCP values of same class cannot be part of multiple class queues.