Cannot proceed with NSX V2T host migration with error: Segment path /infra/segments/virtualwire-# is not in the realized map.

Products

• VMware NSX

Issue/Introduction

• NSX 3.2.x - 4.1.x: There are more than 1K segments in the system, but Policy list segment API "/infra/segments" returned the 1000 in the "result_count" in the first response such that the V2T client got only the first 1000 segments and throw the error "Segment path /infra/segments/virtualwire-# is not in the realized map".

• NSX 4.2+: The correct segment count is returned but all next pages will contain the first 1000 segments.

• Relevant logs to look: Compare the API count result with the number of segments found in the database.

  • /var/log/migration-coordinator/v2t/cm.log file show these messages:

    Can not proceed with migration: Segment path /infra/segments/virtualwire-# is not in the realized map
Can not proceed with migration: Segment path /infra/segments/virtualwire-# is not in the realized map
Can not proceed with migration: Segment path /infra/segments/virtualwire-# is not in the realized map
Can not proceed with migration: Segment path /infra/segments/virtualwire-# is not in the realized map
Can not proceed with migration: Segment path /infra/segments/virtualwire-# is not in the realized map

Environment

VMware NSX 3.2.x to 4.2.2.x

Cause

The broken list segments API did not return all segments found in the system when over 1000 segments exists.

Resolution

This issue is resolved in VMware NSX 4.2.3, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.