License replication issues in vCenter ELM deployments due to VMdir running in "standalone" state

Products

• VMware vCenter Server

Issue/Introduction

Changes to licenses, or added license keys are not properly replicated between to vCenter Server where they were entered and its Enhanced Linked Mode replication partners.

• When logging into each VC individually can see correct new license attached
• However, remaining VCs not showing correct License (May show old license for 7.0 version)

Environment

vCenter Server 8.0 in Enhanced Linked Mode (ELM) deployments

Cause

This issue can occur when the replication between the Enhanced Linked Mode (ELM) partner nodes is not properly functioning, specifically when vmdir is not running in "normal" but in "standalone" mode.

Resolution

To verify that the issue is present in your environment, apply the steps below:

1. Open an SSH connection to the vCenter Server Appliance
2. Enter "shell" to open the BASH shell
3. Check replication agreement using the vdcrepadmin tool: 

   # /usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator

4. verify if the output looks like this:

   Partner: [email protected]
   Host available:   Yes
   Status available: No

5. Check the VMdir state using the vdcadmintool:

   # /usr/lib/vmware-vmdir/bin/vdcadmintool

6. Select option 6 (get vmdir state)
7. Again, verify if the output looks like in the example below: 

   VmDir State is - Standalone

 

To fix this issue, you need to change the vmdir state back to "normal, by following the steps below:

1. Make sure that you have taken fresh offline snapshots (in powered off state) for ALL members in the ELM replication setup. If a restore is needed, all ELM nodes need to be restored.
2. Run the vdcadmintool:

   # /usr/lib/vmware-vmdir/bin/vdcadmintool

3. In vcdadmintool, select Option 5 (set vmdir state)
4. Enter NORMAL and confirm