ViPR SRM 4.0.2: How do I deploy a Collector VM in a different datacenter

Use this procedure if your design requires the deployment of remote Collectors in different datacenters.
 
1. Navigate to the Support by Product page for ViPR SRM (https://support.emc.com/products/34247_ViPR-SRM).
2. Click Downloads and search for ViPR SRM
3. Download the ViPR SRM <version number> vApp Deployment zip file.
       The host being connected to the vCenter should be local to the ESX servers for the quickest deployment. Extract the *.zip file and
       locate the 1VM OVF deployment file on the host running the vCenter Client or place the files on the DataStore.
4. Under each download is a checksum link.  Copy off the checksum number and validate the integrity of the *.zip file after downloading.
5. Open vCenter Client and connect to the vCenter Server that manages your VMware environment.
       Do not run vCenter Client over a VPN connection.
       For the fastest deployment time, the host running vCenter Client should be local to the ESX servers.
6. Select File > Deploy OVF Template.
7. In the Source step, locate the 1VM OVF template file.
8. Click Next.
9. In the OVF Template Details step, review the details of the loaded OVF file, and then click Next.
10. In the End User License Agreement step, review the license agreement. Click Accept, and then click Next.
11. In the Name and Location step:
       a. Specify a new name or accept the default name for the appliance.
       b. Specify an inventory location for the appliance in your VMWare environment.
12. In the Deployment Configuration step, select Additional Backend Appliance or Collector Appliance.
13. In the Host/Cluster step, select the ESX server or ESX Cluster, and click Next.
14. In the Resource Pool step select the Resource Pool within the Cluster which you wish to deploy the template.
       This will be deployed outside any existing vApps.
15. In the Storage step, select the destination storage (DataStore) for the virtual machine files, and then click Next.
        The compatibility window will state if there is insufficient disk space on the selected DataStore and a warning will popup
        once the next button is selected if there is insufficient space on the selected DataStore
16. In the Disk Format step, select the storage space provisioning method, and then click Next.
17. In the Network Mapping step, select a destination network for the VM, and then click Next.
18. In the IP Address Allocation step, choose the IP allocation policy and IP protocol to use, and then click Next.
19. In the Properties step, provide the values for each field, and then click Next.
20. In the Ready to Complete step, review the list of properties for the appliance, uncheck Power On after deployment and then click Finish.
         A pop-up menu that shows the deployment progress opens in vCenter Client.
21. After the 1VM deployment finishes, in the Deployment Completed Successfully dialog box, click Close.
22. Repeat this process for each Collector needed.

After all of the Collector VMs have been deployed in different datacenters using the 1 VM OVF install, follow these steps to complete the installation:
 
Note: To make adjustments to memory and CPU and the vApp has to be powered off.
 
1) Adjust the memory and CPU settings for each Collector VM as described in your EMC ViPR SRM design specification for your site.
                1. Right click the VM and select Edit Settings.
                2. Under the Hardware Tab - select Memory - on the right make the appropriate change.
                3. Under the Hardware Tab - select CPU - on the right make the appropriate change.
 
2) Change the Collector VM name in vCenter to conform to naming policies for your site.
                1. Right click the VM and select Edit Settings
                2. Click on the Options tab and the Virtual Machine Name can be changed within the window on the right.
 
3)  All Collector VMs are deployed with 132GB storage. Adjust the disk space for each Collector VM as described in your EMC ViPR SRM
      design specification for your site using the following procedure:
                1. Right click the VM and select Edit Settings
                2. Under the Hardware tab click Add
                3. Select Hard Disk and click Next.
                4. Select Create a new virtual disk and click Next.
                5. Specify the disk size, the provisioning type, the location of the disk and click Next.
                6. Specify the virtual device node (the default value should be OK) and click Next.
                7. Review the options and click Finish.
                8. After ViPR SRM is up and running, putty to the Linux host. You can access a login prompt through the vCenter Client console or
                     using an SSH tool such as PuTTY.
                9. At the root system prompt, type the command expand_disk.pl.
 
                The script will merge the new VMDK with the existing files system while the VM is still running. Use the df -h command when the
                  script is finished to see the new filesystem size.
 
4) Right click on the Collector VM and select Power On.
 
5) Power on the new Collector VM
     From the Frontend server run the following command:
      /usr/APG_Source/conf/frontend-scale-collector.sh  H <COLLECTOR_FQDN> -o linux-x64
     Login to Centralized Management UI and manually configure new collector.
 
6) Once the remote Collector VM(s) are powered on, configure the Load Balancer Connector, generic-snmp and generic-rsc through
     the ViPR SRM UI.
                1. From Centralized Management, expand SolutionPacks and click on Other Components
                2. In the right window, in the upper right use the search feature to search for "load" to list the Load Balancers
                3. Click on the pencil icon to reconfigure the Load Balancer connector component
                4. For the Arbiter Configuration - Select Add a new Arbiter configuration from the drop down to open up the configuration settings
                5. For the Arbiter hostname or IP address - set to the Primary Backend over port 2020
                6. For the Alerting on data collection - Select Add a new alerting on data collection from the drop down to open up the configuration
                      settings.
                7. The Alerting Backend hostname or IP address should be set to the Primary Backend over port 2010
                8. For the Front End Web Service - Select Add a new Front end Web Service from the drop down to open up the configuration
                      settings
                9.  For the Tomcat hostname or IP address - set to the Frontend over port 58080
                10. Click on Reconfigure
                11. Repeat the above process for each remote collector.
                12. Under Other Components search for "generic" to list the generic-snmp and generic-rsc
                13. Click on the pencil icon to reconfigure both the generic-snmp and generic-rsc
                14. Under Data Collection - Hostname or IP address to send data to should be set to localhost over port 2020
                15. Under Front End Web Service - Tomcat hostname or IP address should be set to Frontend over port 58080
                16. Under Topology Service - Topology hostname or IP address should be set to Primary Backend