/common/logs/admin/app.log
:<timestamps> UTC [NetworkStretchService_SvcThread-968, j: ########, s: ########, , TxId: ########-####-####-####-###########] ERROR c.v.v.h.n.i.AbstractJobInt- NetworkStretchJobs workflow prepareCloudNetwork failed. Error: Error creating NSX-T Segment. Address ###.###.###.##/## overlaps with Segment path=[/infra/segments/<segment-name>] that has subnet ###.###.###.###/##.
System
→ Administration
→ Activity Logs
, similar to the screenshot below:HCX
VMware Cloud on AWS
The issue occurs due to the difference in segment creation paths between VMC and Non-VMC deployments:
1. In VMC deployments, the expected segment path is:
infra/tier-1s/<tier-1_id>/segments/<segment_id>
2. In Non-VMC deployments, the segment path used is:
infra/segments/<segment_id>
Because of this distinction, deployments using the non-VMC path format in a VMC environment fail. Specifically, in VMC, when a new Tier-1 (other than CGW or MGW) is created followed by addition of segment, the UI/API defaults to using the path /infra/segments/
. However, per VMC architecture guidelines, segments must be created under: infra/tier-1s/<tier-1_id>/segments/
.
This is a condition that may occur in a VMware HCX environment on VMware Cloud on AWS.
Workaround:
Option 1: If you need to use a pre-created segment in NSX, you can use the default Tier-1 (CGW - Compute Gateway).
Option 2: If you need to extend to a dedicated Tier-1, pre-created segments are currently not supported. However, you can still extend the network if the segment is not pre-created.
Note that this specific issue only affects VMC environments using a new Tier-1 and pre-created networks. If you are experiencing a similar error message, refer to the KB: HCX - Error while extending pre-created segments "Error creating NSX-T Segment. Address, overlaps with Segment path"