Workload domain for cluster under Network tab show :"Portgroups [Virtual SAN-vlan11_100.x.x.x/26] not found in vCenter associated with the hosts of the cluster"
search cancel

Workload domain for cluster under Network tab show :"Portgroups [Virtual SAN-vlan11_100.x.x.x/26] not found in vCenter associated with the hosts of the cluster"

book

Article ID: 375503

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The customer has standardized the use of /26 in their port group names across various workloads. However, warnings are being generated in all clusters except the management cluster, which does not include the / character in its port group names

Environment

VCF 5.x

 

Cause

SDDC Database:

public.vds (id, creation_time, modification_time, mtu, name, niocs, port_groups, status, version, is_used_by_nsxt, source_id, nsxt_switch_config) FROM stdin;
f1d67a6778ad","transportType":"VLAN"}],"hostSwitchOperationalMode":"STANDARD"}
0fdb589a-a8cc-4b7f-8f38-7da13658fd40 1711965201324 1711965201324 0 wld1-cmd-vds1-vsan \N [{"name":"Virtual SAN-vlan11_100.x.x.x/26","transportType":"VSAN","type":"EARLY_BINDING","vlanId":11,"activeUplinks":

We can see that the "/" present in  portgroup names is getting url encoded to "%2f" when fetched from vc. As a result the portgroup name Virtual SAN-vlan11_100.x.x.x/26 is fetched as Virtual SAN-vlan11_100.x.x.x%2f26 from vc but the input param continues to contain the correct name Virtual SAN-vlan11_100.x.x.x/26. Due to the mismatch between Virtual SAN-vlan11_100.x.x.x%2f26 and Virtual SAN-vlan11_100.x.x.x/26 in  ReconfigurePortGroupsAction.java are hitting this failure.

Resolution

Step 1: Update the Inventory

  1. Snapshot the SDDC Manager:

    • Before proceeding, take a snapshot of the SDDC Manager to ensure you can revert any changes if necessary.
  2. Retrieve Domain Inventory Data:

    • From the SDDC Manager as the root user, run the following command to obtain all domain inventory data:

 curl localhost/inventory/extensions/vi/domainInventory > di.json

     3. List Domain Names:

    • Extract and display all domain names by executing

          cat di.json | jq '.[].domain.name'

      4. Identify and Prepare the Payload for the Target Domain:

    • Determine the index of the domain you need to modify (indexing starts at 0). Here DOMAIN-NAME-INDEX starts from 0.
    • Use the following command to extract the domain inventory information for the specific domain:

cat di.json | jq '.[<DOMAIN-NAME-INDEX>]' > payload.json
 

    • For example If: 

cat di.json | jq '.[].domain.name'

"domain1"
"domain2"

                 To modify the hosts in domain1, run

          cat di.json | jq '.[0]' > payload.json

                  For domain2, run:

          cat di.json | jq '.[1]' > payload.json

5. Edit the Port Group Name:

    • Open payload.json in a JSON editor, update the port group name as needed, and save the changes to modified_payload.json

                   vim modified_payload.json

Step 2: Copy the text to the JSON editor and change the name of the port-group name

Step 3: Update the Inventory

  • Use the modified payload to update the inventory by executing

          curl -s localhost/inventory/extensions/vi/clusters -XPOST -H "Content-type: application/json" -d @modified_payload.json

Step 4: Update the Port Group Name in vCenter

  • Change the port group name directly in vCenter to match the updated name in the inventory.

Step 5: Refresh the SDDC UI Networks Tab

  • Reload the Networks tab in the SDDC UI to ensure the changes are reflected.