How to Run DR IP Customizer for a VMware Cloud on AWS to VMware Cloud on AWS Pairing

You must use the DR IP Customizer tool from an on-premises Site Recovery Manager instance with a custom configuration file.

The DR IP Customizer tool is shipped within the Site Recovery Manager appliance. The DR IP Customizer requires shell access to the Site Recovery Manager instance. In VMware Cloud on AWS, you do not have shell access and Guest OS credentials for the Site Recovery Manager appliance. To use the tool, you must run it from an on-premises Site Recovery Manager instance with a custom configuration file.

Prerequisites

Verify that the on-premises instance of Site Recovery Manager is the same version as the Site Recovery Manager appliance at VMware Cloud on AWS.

Note: If you attempt to run the DR IP Customizer tool at an on-premises Site Recovery Manager 8.3 against a Site Recovery Manager 8.2 at VMware Cloud on AWS, the tool fails with: ERROR: Unsupported version URI "urn:internaldr0/8.3".

Procedure

1. Prepare a custom configuration file for the DR IP Customizer by using the following template.

   <?xml version="1.0" encoding="UTF-8"?>
   <Config>
      <vmacore>
         <threadPool>
            <initializeCOM>mta</initializeCOM>
            <catchWorkItemExceptions>false</catchWorkItemExceptions>
            <TaskMax>20</TaskMax>
            <IoMax>60</IoMax>
         </threadPool>
      </vmacore>
      <waitForObjectTimeout>300</waitForObjectTimeout>
      <log>
         <directory>/var/log/vmware/srm</directory>
         <!-- log file names will get -#.log appended -->
         <name>dr-ip-customizer</name>
         <level>verbose</level>
         <coreDump>/var/log/vmware/srm/DumpFiles</coreDump>
      </log>
      <level id="SoapAdapter">
         <logName>SoapAdapter</logName>
         <logLevel>info</logLevel>
      </level>
      <level id="Libs">
         <logName>Libs</logName>
         <logLevel>warning</logLevel>
      </level>
      <level id="HttpConnectionPool">
         <logName>HttpConnectionPool</logName>
         <logLevel>info</logLevel>
      </level>
      <workingDir>.</workingDir>
      <extension>
         <key>com.vmware.vcDr-foobar</key>
      </extension>
   </Config>

2. Update the extension key, the log directory, and the log coreDump settings in the custom configuration file.
   If the extension key does not match, the tool reports the following error: ERROR: Failed to locate DR endpoint for VC UUID....
   1. Use the extension key reported by the VMware Cloud on AWS Site Recovery Manager appliance. See the Extension key: value at https://srm.sddc-1-2-3-4.vmwarevmc.com/drserver/.
      For example, use com.vmware.vcDr if you are using default extension key or com.vmware.vcDr-custom_suffix if you are using a custom extension key.
3. Set the firewall rules to allow a TCP connection on port 443 by the on-premises Site Recovery Manager instance to the VMware Cloud on AWS vCenter Server and Site Recovery Manager appliance.
4. Run the DR IP Customizer tool at the on-premises Site Recovery Manager instance with --cfg argument pointing to the custom configuration file and --uri argument pointing to https://vmc_vcenter_fqdn/lookupservice/sdk.
5. Make sure to use log directory and log coreDump folders that are writable by the user running the DR IP Customizer tool.
   For example, if using the log directory /var/log/vmware/srm/ and you are logged in as the admin user to an on-premises Site Recovery Manager appliance, run the tool with sudo.

   sudo /opt/vmware/srm/bin/dr-ip-customizer --verbose --cfg /tmp/dr-ip-customizer-config.xml --cmd generate --out /tmp/ip-customizer-generated.csv --uri https://vcenter.sddc-1-2-3-4.vmwarevmc.com/lookupservice/sdk

   sudo /opt/vmware/srm/bin/dr-ip-customizer --verbose --cfg /tmp/dr-ip-customizer-config.xml --cmd apply --csv /tmp/ip-customizer-edited.csv --uri https://vcenter.sddc-1-2-3-4.vmwarevmc.com/lookupservice/sdk

What to do next

You can use the same procedure for running the DR IP Reporter tool for a VMware Cloud on AWS to VMware Cloud on AWS pairing. You use an identical custom configuration file, but set the log name to dr-ip-reporter instead.