[VMC on AWS] After Cutover of L2E Segment to the SDDC the CIDR is not Advertised out the DX/Transit Connect
search cancel

[VMC on AWS] After Cutover of L2E Segment to the SDDC the CIDR is not Advertised out the DX/Transit Connect

book

Article ID: 331532

calendar_today

Updated On:

Products

VMware HCX VMware Cloud on AWS

Issue/Introduction

To detail the workaround and fix to this known problem.

Symptoms:
Customer is cutting over previous Layer-2 extensions from HCX to be native VMC SDDC segments. After unextending the segment successfully via HCX, the Segment on the SDDC is switched to be of type ROUTED.
The segment CIDR fails to advertise out the Direct Connect or Transit Connect (SDDC Group) interfaces.
Customer is running a 1.20v1/v2/v3/v4 SDDC version.

Cause

A problem in handling the segment properties change within NSX leads to the route not being advertised out the correct interfaces.

Resolution

A future SDDC version will include a fix to this problem.

Workaround:
Engage VMware Support (Creating and managing Broadcom support cases) and request the workaround be applied on your behalf.

Additional Information

Impact/Risks:
The customer will be unable to complete the full cutover of the L2E segment to the SDDC until the workaround is applied.