Tags created from one ELM vCenter to VM in another vCenter cannot be assigned.
It fails with below error:
Operation failed:
(vmodl.fault.ManagedObjectNotFound) {
faultCause = null,
faultMessage = null,
obj = ManagedObjectReference: type = InventoryServiceTag, value = d27b6041-f828-4e2b-adbf-f203b1e1ee2d, serverGuid = GLOBAL
}
However, error is not visible under monitor>tasks
for the VM.
When you create a new tag from VC1 , it is not visible in VC2.
vCenter servers with Enhanced linked mode
In ELM , if there is an issue with replication, we will have issues assigning tags from one VC ui to VM in another VC
Check the replication status of vCenter VMs using below command:
/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator
Partner: vc1
Host available: Yes
Status available: No
Partner: vc3
Host available: Yes
Status available: No
Whereas on other vCenters it shows changes behind for vc2
Note: Before making any changes it is recommended to take offline snapshot of all 3 vCenter servers in ELM and while restoring, restore snapshot of all 3 vCenter servers.
Troubleshoot the issue with PSC replication in ELM:
/usr/lib/vmware-vmdir/bin/vdcadmintool
==================
Please select:
0. exit
1. Test LDAP connectivity
2. Force start replication cycle
3. Reset account password
4. Set log level and mask
5. Set vmdir state
6. Get vmdir state
7. Get vmdir log level and mask
==================
Select option: 6
VmDir State is - Standalone
/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator
If you have logged in to vc1 in ELM and trying to assign tag to VM in VC2 , logs for vSphere-ui will be recorded in VC1 vsphere-ui.