BGP peering lost on non-Global segments in a SD-WAN Edge

Products

• VMware
• VMware SD-WAN by VeloCloud

Issue/Introduction

Symptoms:

In a VMware SD-WAN Edge:

• BGP does not come up.
• Edge fails to establish a BGP session with devices connected to non-global segment
• The following conditions are true:
  • BGP is configured in both the global segment and a non-global segment.
  • In the non-global segment, BGP is configured on a subinterface.
  • The same IP address is configured in different segments (for example, the same IP is used in a WAN overlay interface on the global segment, and in a subinterface of the non-global segment). 

The issue can happen after a reboot of software upgrade.
 

 

Environment

VMware SD-WAN
VMware SD-WAN by VeloCloud

Cause

The issue is documented in bug #102655.

The issue happens because the Edge sends the BGP packets on the non-global segment without a VLAN tag, eventually causing the BGP peer to send a reset on the TCP connection.

Resolution

This issue is resolved in SD-WAN Edge versions 4.5.2 and 5.2.0

For information on how to upgrade please check the following article: VMware SD-WAN Software Upgrade FAQs

Workaround:
To work around this issue if you do not want to upgrade, change the IP address of the subinterface to a unique address instead of a duplicate of the Global segment.

Additional Information

To be alerted when this article is updated, click Subscribe to Article in the Actions box