Transport Group is not working

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

If a customer sets the Transport Group on business policies , customers may encounter what the Transport Group may not work as customer set.
In most cases, these behaviours are expected.This article describes the causes and resolution for cases where the Transport Group does not work as set.

 

Resolution

Pattern 1 - In a hub-and-spoke configuration, if the peer device does not have a same Type WAN link, Link Steering->Transport Group setting is not working.

In a hub-and-spoke configuration, If the peer device does not have a same Type (WAN Overlay Settings->Advanced Settings for Public Overlay->Type), the Link Steering->Transport Group setting is not working.

For example, if the Spoke Edge has a Public Wireless WAN link and the Hub Edge does not have a Public Wireless WAN link as shown below, Business policy, which set Mandatory and Transport Group: Public Wireless, is not working.

Workaround

The above behavior is expected. This is because the Spoke Edge and Hub Edge perform QoS synchronization for the flow. When set the Transport group, both the Spoke Edge and Hub Edge need to have a same Type WAN link.

The workaround is to specify Link Steering as the Interface and Public Wireless WAN Link (GE4 in this case) as the Select Interface in the Business Policy. Or add a public wireless WAN link on the Hub Edge.

 

Pattern 2 - Edge sends traffic via Hot standby link when set Link Steering->Transport Group

Edge sends traffic via Hot standby link when set Link Steering->Transport Group.

For example, in the below case, if the link steering is Transport Group 'Public Wired', hot standby link is included in the Transport Group. At that time, Edge is sending traffic via hot standby link.

Workaround

The above behavior is expected when set Link Steering to anything other than "Auto". If you do not want to send traffic to the hot standby link, please set link steering to "Auto".