Proactively Identifying Component Details for M2P Promotion Eligibility in NSX Migration
search cancel

Proactively Identifying Component Details for M2P Promotion Eligibility in NSX Migration

book

Article ID: 425274

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • After starting the Migration Coordinator, the M2P step will display a summary that includes the total number of objects that are eligible for promotion as below 
  • The core issue encountered by administrators is that the Migration Coordinator's user interface does not show the specific names or IDs of the components within this eligible list.
  • The below more detailed feedback API does exist, but this crucial endpoint is only populated and functional after an M2P migration attempt has failed. 
     GET https://{{nsx-server}}/api/v1/migration/mp-to-policy/feedback
  • Consequently, administrators are limited to a reactive approach, where they can only obtain the component details after a failure has occurred, rather than proactively identifying and correcting any problematic objects before the promotion process even starts.
  • This document provided the way to Proactively Identifying Component Details for M2P Promotion Eligibility in NSX Migration which can help customer to identify object-level details during the Change Planning stages.

Environment

VMware NSX

Cause

The standard operational feedback loop within the Migration Coordinator is designed to provide a high-level quantitative overview rather than granular, object-level details during the Planning stages.

Resolution

Pre-requisites:

  • Start Migration Coordinator Service: Ensure the migration-coordinator service is running on at least one node in your NSX Manager cluster.

    You must start the migration coordinator service.

    • SSH into any one node of manager cluster nodes(nsx-manager)

    • Run the following command 

      start service migration-coordinator
  • Full NSX Environment Backup: Before proceeding with any promotion, always take a complete backup of your NSX-T environment. This is a critical step to ensure recoverability in case of unexpected issues.

To overcome this visibility limitation and enable a truly proactive migration strategy, administrators can utilize a specific, API endpoint to query the IDs of objects eligible for promotion by resource type. Please find the procedure below:

Procedure - UI

  1. Navigate to System > General Settings > Manager Objects Promotion (Role Needed - Enterprise Admin)
  2. Click Start Objects Promotion.
    1. The system displays summary of manager objects , but does not provides the component details.

 Procedure - API client : 

  1. Please run the below APIs to collect the component level details.This method provides the necessary component details before initiating or failing the M2P process.
  2. The syntax is: 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=RESOURCE_TYPE.

    Resource Type API Method API Endpoint to Fetch Object IDs
    IP Pool 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=IpPool
    Tier-1 Logical Router 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=LogicalRouter
    Certificate 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=Certificate
    NS Service 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=NSService
    NS Group 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=NSGroup
    NS Service Group 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=NSServiceGroup
    Logical Port / Segment Port 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=InternalLogicalPort
    Edge Firewall Section 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=EdgeFirewallSection
    Logical Switch 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=LogicalSwitch
    MAC Set 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=MACSet
    NAT Rule 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=NatRule
    Logical Router Port 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=LrPort
    Firewall Section (DFW/Gateway) 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=FirewallSection
    LB Client SSL Profile 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=LbClientSslProfile
    IP Set 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=IPSet
    LB Server SSL Profile 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=LbServerSslProfile
    DFW Exclude List 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=InternalFirewallExcludeList
    Service Config 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=ServiceConfig
    System Health Agent Profile 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=SystemHealthAgentProfile
    Global Config 
    GET
    		 
    https://(NSX_manager_ip)/api/v1/mppolicy/migration/object-ids?resource_type=GlobalConfig
Powered by Wolken Software