NSX VM-tags are not replicated to the DR site after site failover with VMware SRM

Products

• VMware NSX

Issue/Introduction

Disaster recovery test to move a VM with SRM between to sites.

The failover VM are starting up in secondary site without the TAGs

Environment

VMware NSX 4.x.x

Cause

VM tag replication policies are created and defined in GM, they are not being pushed to the LMs.

 

Resolution

Workaround:

Run the following command to push the replication policies:

1. Check for the 'replication policies id'
   curl -k -u admin --request GET 'https://<gm-ip>/global-manager/api/v1/global-infra/vm-tag-replication-policies/
   (This command will require IP address and admin user password of this GM.)
   
   
2. Use the 'replication policies id'
   curl -k -u admin  GET 'https://<gm-ip>/global-manager/api/v1/global-infra/vm-tag-replication-policies/<Replication_policies_id'>'
   (This command will require IP address and admin user password of this GM.)
   
   
3.  Copy the response of step 2.
   
   
4.  Run this command:
   curl -k -u admin --request PATCH 'https://<gm-ip>/global-manager/api/v1/global-infra/vm-tag-replication-policies/<Replication_policies_id'>' --header 'Content-Type: application/json' --data 'paste the response of step 1 here'
   (This command will require IP address, admin user password of this GM, and the response of step 2.)
   
   
5. Verify the LM to see if the policy gets pushed.
   From the LM command line check the Corfu dumps for the VmTagReplicationPolicy table.

   /opt/vmware/bin/corfu_tool_runner.py -o showTable -n ns x -t VmTagReplicationPolicy 

Additional Information

Working with and NSX Federation