BGP neighborship towards PE remains down on PG handoff using C_tag and S_tag

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

If a partner configures BGP on a Partner Gateway towards an Enterprise using handoff config with C-Tag (Customer tag) and S-Tag (Service tag), the neighborship to the Provider Edge router may fail to come up.

This is triggered by either of these 3 conditions

• Partner enabled PG handoff for a new Enterprise with multiple segments and enabling BGP for any one of the segments
• Partner created the PG handoff settings using Classic UI and modifying the config using Angular UI (New UI)
• Partner is trying to reuse the C-Tag (Customer tag) and S-Tag (Service tag) previously used for a different Enterprise

VCG <---- Handoff interface running BGP ---> Provider Edge Router

Environment

VCG with Partner Handoff enabled and running multiple BGP neighborship for different Enterprises

Cause

The BGP config is getting pushed from the Orchestrator. But gateway is not able to apply the config correctly for the Enterprise.

This is caused by combination of two bugs 91920 and 143374

Resolution

As a workaround Partner can trigger a configuration change by saving the handoff configuration for the affected Enterprise.

The issue will be fixed in part of 5.2.4.x, 6.0.1.x and 6.1.x.x