[VMC on AWS] Unable to reach a specific subnet via SDDC Transit Connect
search cancel

[VMC on AWS] Unable to reach a specific subnet via SDDC Transit Connect

book

Article ID: 323266

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

To explain the cause of, and how to remediate, the route issue.

Symptoms:
Users are unable to reach specific subnets via the VMC Transit Connect.
Other networks are reachable via the Transit Connect. This indicates that the network path is healthy.

Cause

This is caused by a lingering route to a network on VMC. This route is present in the NSX configuration for the host running the active edge.
This can occur if there was a route to a similar network in the environment that was since removed.
For example, the problem route may have the same CIDR as a compute segment that was removed.

Resolution

This is resolved in an upcoming release.

Workaround:
Contact VMC on AWS Support for assistance in having the route programming corrected.
There is no impact to workloads during this process.

Additional Information

How to file a Support Request in Customer Connect and via Cloud Services Portal

Impact/Risks:
Users will not be able to reach the remote network via the Transit Connect.