The segment list REST API /infra/segments does not return all segments leading to NSX-V to NSX-T migration failure
searchcancel
The segment list REST API /infra/segments does not return all segments leading to NSX-V to NSX-T migration failure
book
Article ID: 397799
calendar_today
Updated On: 05-16-2025
Products
VMware NSX
Issue/Introduction
NSX version is between 3.2.x to 4.1.x and the segment list REST API /infra/segments does not return all segments in the system when there are over 1000 segments.
NSX version is 4.2.x and the segment list REST API /infra/segments returns the correct segment count, but only the first 1000 segments will always be returned at all the pages.
If a user is performing NSX-V to NSX-T migration, migration of ESXi hosts to NSX-T may fail with the following error in the UI:
Can not proceed with migration: Segment path /infra/segments/virtualwire-#### is not in the realized map. cm.log file may show these messages during V2T migration: Can not proceed with migration: Segment path /infra/segments/virtualwire-#### is not in the realized map Above error is shown in spite of NSX-V virtual wire table showing all the virtual wires.
Environment
VMware NSX-T Data Center 3.2.x
VMware NSX 4.1.x
VMware NSX 4.2.0.x
VMware NSX 4.2.1.x
VMware NSX 4.2.2
Resolution
This is a known issue impacting VMware NSX.
Workaround:
Using segment_type=ALL while calling the segment list API is the workaround. Instead of calling <mgr_ip>/policy/api/v1/infra/segments?segment_type=DVPortgroup or calling <mgr_ip>/policy/api/v1/infra/segments, use the below API call: