/common/logs/admin/app.log:<timestamp> UTC [NetworkStretchService_SvcThread-458, j: 9ea10d55, s: d33d37ab, , TxId: #########-####-####-####-#########] WARN c.v.v.h.networkstretch.AbstractJob- Fa
iled to resolve vc opaque network moref for logical switch #########-####-####-####-#########: Failed to get opaque network moref with logical switch id #########-####-####-####-#########
<timestamp> UTC [NetworkStretchService_SvcThread-458, j: 9ea10d55, s: d33d37ab, , TxId: #########-####-####-####-#########] WARN c.v.v.h.n.i.AbstractJobInt- Exception
in NetworkStretchJobs:ExtendNetworkWorkflowInt. Reason : Unable to find Layer2 Id for segment /infra/segments/<segment-name>
Unable to find Layer2 Id for segment /infra/segments/<segment-name>VMware HCX 4.x
VMware NSX 3.2 or later
The policy API /policy/api/v1/infra/segments/<segment-id> creates a Segment along with a Logical Switch and populates the VNI in the realized entity. If the policy API is used to create a Segment for an already available overlay-backed Logical Switch, the Segment creation succeeds, but the VNI information is not populated in the realized logical switch.
This is a condition that may occur in a VMware HCX / NSX environment.
If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.
HCX - Segments Created with NSX-T Manager UI/API not Visible in NE wizard
Note: If you face this issue on NSX 3.1.x or lower, please use the article HCX - "Unable to find Layer2 id for segment“ error during Network Extension of an NSX-T Overlay Segment