This is a known issue.
VMware NSX-T Data Center
DrVmTagMsg cannot be published to recovery sites due to the IllegalArgumentException, which interrupts the Falcon transaction in Federation-SRM app.
This is fixed with VMware NSX-T 3.2.3 and in upcoming versions.
GET https://<global-manager-ip>/global-manager/api/v1/global-infra/vm-tag-replication-policies/ { "result_count": 1, "results": [ { "protected_site": "/global-infra/sites/XXXX", "recovery_sites": [ "/global-infra/sites/XXXX" ], "vm_match_criteria": "MATCH_BIOS_UUID_NAME", "groups": [ "/global-infra/domains/default/groups/test1" ], "resource_type": "VMTagReplicationPolicy", "id": "policy1", <<<<< this is the policy-id >>>>> "display_name": "vm tag replication policy test", "description": "vm tag replication policy1", "path": "/global-infra/vm-tag-replication-policies/policy1", "relative_path": "policy1", "parent_path": "/global-infra", "unique_id": "XXX-eada-4849-a77c-XXX", "marked_for_delete": false, "overridden": false, "_create_time": 1670581076492, "_create_user": "admin", "_last_modified_time": 1670581076492, "_last_modified_user": "admin", "_system_owned": false, "_protection": "NOT_PROTECTED", "_revision": 0 } ], "sort_by": "display_name", "sort_ascending": true }
2.Move the interface of VMs identified in step 1 to Virtual Standard Switch or NSX backed Logical Switch.
You may observe that DrVmTagMsg is missing in recovery sites and thus the disaster-recovery policy applied on the VM does not work.