MP2P Migration INITIATE Call Duration Expected Behavior

Products

• VMware NSX

Issue/Introduction

• The MP2P (Migration Coordinator) Migration INITIATE call takes an excessively long time (8 minutes or more) to complete.
• The issue is observed consistently across different deployments within the migration workflow.
• API calls to /api/v1/migration/mp-to-policy/workflow?action=INITIATE return successfully but with high latency.

Environment

• VMware NSX
• Migration Coordinator (MP2P)

Cause

This behavior occurs because the migration initiation triggers backend operations, including:

1. Object Promotion: The time required scales proportionally with the number of objects being promoted.
2. Resource Allocation: Significant consolidation of resources is required for larger environments.
3. Snapshot Data: The presence of large VMs or significant snapshot data significantly increases the processing time for backend operations.

The initiate API time is not currently configurable.

Resolution

This is considered expected behavior based on the complexity and volume of the objects being migrated. No configuration changes are available to shorten this duration.

Recommendation: It is recommended to subscribe to this article to be updated on any changes to the fix status. For details on how to subscribe, see Knowledge Article Subscriptions.

Additional Information

• For sequential steps on retrieving logs to verify migration progress, please refer to the NSX Administration Guide.
• To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.