Migrate core VM Management port group to another distributed switch in VCF 9.0.1
search cancel

Migrate core VM Management port group to another distributed switch in VCF 9.0.1

book

Article ID: 442542

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

We may need to move the core "VM Management" distributed port group from its original vSphere Distributed Switch (vDS) to a different vDS within a VMware Cloud Foundation (VCF) 9.0.1 Management Domain. 

Environment

VCF 9.0.1 

Cause

Manual migration of core management port groups in vCenter Server creates configuration drift. SDDC Manager’s internal PostgreSQL database remains bound to the original vDS mapping defined during initial bring-up. If the database is not synchronized, future lifecycle management (LCM) operations, such as host expansions or upgrades, will fail as they attempt to query non-existent network mappings.

Resolution

Before you begin 
1. Take a non-memory snapshot of the SDDC Manager and vCenter Server VMs.
2. Ensure no active LCM tasks are running in the SDDC Manager.

To migrate the VM Management port group while maintaining synchronization with SDDC Manager, follow these steps:

  1. Create Replica Port Group : In vCenter, create an exact replica of the existing VM Management port group on the target vDS.
  2. Migrate Virtual Machines : Manually migrate all VMs from the old port group to the newly created replica on the new vDS.
  3. Decommission Old Port Group : Once all VMs are successfully migrated and the old port group is no longer in use, delete the old port group from the original vDS.
  4. Synchronize Inventory
    A. Using VCF Operations : Perform the "Sync Inventory" task from the UI. This triggers a reconciliation process that parses the vCenter inventory and updates the SDDC Manager database. Refer following kb Synchronizing vCenter Manual Changes with SDDC Manager via VCF Operations 9.0
    B. Using API : If VCF Operations is unavailable, use the SDDC Manager Developer Center to invoke the synchronization API:
         `/v1/domains/{domainId}/synchronizations`