Please perform Manager to Policy promotion error during upgrade to VCF 9
search cancel

Please perform Manager to Policy promotion error during upgrade to VCF 9

book

Article ID: 385606

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • During upgrade to VCF / NSX 9 prechecks will fail with errors similar to the below observed in NSX or SDDC:

    UC MP - Check for data inconsistencies in DB 

Found data inconsistencies: MP Objects found in DB before promotion for tables : #######, please perform Manager to Policy promotion or delete the MP objects and retry the prechecks. Delete any Bridge firewall section/rule if they exist and then retry the prechecks. For more details, please refer to - https://knowledge.broadcom.com/external/article/385606

  • Customers trying to upgrade to VCF 9.0 with MP logical objects will be blocked by the NSX upgrade pre-check to ensure manager objects are removed as no promotion tool exists once upgraded.

 

Environment

 VMware NSX  4.x

Cause

MP Logical APIs and MP2Policy promotion tool have been removed in VCF 9.0 and hence customers are advised to perform manager to policy promotion of such MP logical objects before upgrading to VCF 9.0. 

Resolution

Prerequisites

You must start the migration coordinator service by running the following command on any one node of manager cluster nodes.

> start service migration-coordinator

Procedure - UI

  1. Navigate to System > General Settings > Manager Objects Promotion
  2. Click Start Objects Promotion.
    The system displays summary of manager objects.
  3. Click Continue.
    The system starts the promotion and displays the progress and status of promotion. If any object fails to get promoted, the system displays an error. You can click Skip and Continue to continue the promotion, or you can click Cancel to stop the promotion.
  4. Once the promotion is completed successfully, the system displays the Manager to Policy Objects Promotion page.

 

Procedure - API

  1. Get the total count of pure MP objects and different types of pure MP objects that are eligible for promotion.

    Request
    GET https://<nsx-manager-ip>/api/v1/migration/mp-to-policy/stats?pre_promotion=true
    Response Collapse source
    {
        "current_resource_type_in_promotion""NONE",
        "migration_stats": [
            {
                "resource_type""LOGICAL_SWITCH",
                "promotion_status""NOT_STARTED",
                "total_count""2",
                "promoted_objects_count""0",
                "failed_objects_count""0"
            }
        ],
        "total_count"2
    }
  2. Start Objects Promotion 

    Request
    POST https://<nsx-manager-ip>/api/v1/migration/mp-to-policy/     
     
    {
        "skip_failed_resources"false,
        "mode""GENERIC"
    }

       

  3. Check the status summary of the migration

    Request
    GET https://<nsx-manager-ip>/api/v1/migration/status-summary
    Response Collapse source
    {
        "overall_migration_status""IN_PROGRESS",
        "component_status": [
            {
                "status""SUCCESS",
                "percent_complete"100.0,
                "details""Config translation completed",
                "component_type""MP_TO_POLICY_PRECHECK",
                "can_skip"true
            },
            {
                "status""NOT_STARTED",
                "percent_complete"0.0,
                "component_type""MP_TO_POLICY_MIGRATION",
                "can_skip"false
            }
        ]
    }
  4. Check the migration stats of each object

    Request
    GET https://<nsx-manager-ip>/api/v1/migration/mp-to-policy/stats
    Response Collapse source
    {
        "current_resource_type_in_promotion""NONE",
        "migration_stats": [
            {
                "resource_type""LOGICAL_SWITCH",
                "promotion_status""DONE",
                "total_count""2",
                "promoted_objects_count""2",
                "failed_objects_count""0"
            }
        ],
        "total_count"2
    }
  5. History of the successful completed promotion can be checked using history

    Request
    GET https://<nsx-manager-ip>/api/v1/migration/mp-policy-promotion/history
    Response Collapse source
    {
        "results": [
            {
                "date_time""1736405353487",
                "status""SUCCESS"
            },
            {
                "date_time""1736405347924",
                "status""INITIATED"
            },
            {
                "date_time""1736326570440",
                "status""SUCCESS"
            },
            {
                "date_time""1736326565370",
                "status""INITIATED"
            },
            {
                "date_time""1736322105827",
                "status""SUCCESS"
            },
            {
                "date_time""1736322098588",
                "status""INITIATED"
            }
        ]
    }

Additional Information