How to use Site Recovery Manager DR IP Customizer

As one of the tasks given to me include protecting critical virtual machines via Site Recovery Manager (SRM) I ran into an environment that needed to be protected and have static IP’s assigned to them. The environment consists of about 15 VM’s, all of the VM’s each have 5 NIC’s with two of the VM’s having 9 NIC’s – that’s a lot of NIC’s to manually configure on both the Protected and Recovery side in SRM.

Looking through the SRM Documentation I was able to see that VMware has graced us with a wonderful tool to greatly speed up this process, dr-ip-customizer.exe!

How to use VMware DR-IP-Customizer

  1. Log into the server you installed SRM onto and open a command prompt and navigate to:
    C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin

    Note: drive letter and/or path may differ from your install.

  2. Then type the command:
    dr-ip-customizer.exe --cfg ..\config\vmware-dr --out C:\sample.csv --cmd generate --vc FQDN_OF_VCENTER

    generate csv file

  3. You will then be asked if you trust the server, type Y and press enter then you are prompted to enter your username and password. Enter your credentials and press enter. Note: This will create a .CSV file listing every virtual machine in all Recovery Plans within SRM.
    dr-ip-customizer credentials
  4. You can now open the “sample.csv” file within Notepad, but using Microsoft Excel will make edits much easier, here is what the output will look like within Excel (I’ve already expanded the columns so they are easier to read)
    cvs file dr-ip-customizer

The dr ip customizer will create two entries for each VM that’s in a Recovery Plan in SRM. One entry for the Protected site and another for the Recovery site. Each will have an Adapter ID of 0. The only only thing you can configure for Adapter ID 0 is a DNS Server and suffix.

That said you will have to create two new lines for each NIC a virtual machine will have and give them an ID higher than 0, you’ll see the example below. From there you’ll be able to set things like IP address, subnet mask, gateway, additional DNS, WINS, etc. In my case the IP for each NIC needed to remain the same on the Recovery site as it is in the Protected site thus why the settings look the same. You can also set the VM to DHCP by typing “dhcp” in the IP address field if needed.

dr-ip-customizer csv file completed

  1. Save the CSV file. Now it’s time to apply the settings from the CSV to SRM.
  2. Go back to the command prompt and now type this command:
    dr-ip-customizer.exe --cfg ..\config\vmware-dr.xml --cmd apply --csv C:\sample.csv --vc FQDN_OF_VCENTER

    Again you’ll be asked if you trust the server. Confirm and then enter your credentials.
    import csv dr ip customizer

  3. Done! Now open up SRM in vSphere and confirm your changes have indeed applied.
    srm dr-ip-customizer applied

There is still a bit of a process typing all the IP’s, etc in the CSV file it certainly is much faster than doing so directly in SRM, NIC by NIC, tab by tab, protected site and recovery site when you have to make bulk IP changes for VM’s in SRM.

Also thanks to Stuart Yerdon for his assistance gathering IP’s and testing.

Similar Posts

  • Shrink a thin provisioned VMDK disk

    When maintaining a Horizon View environment I like to keep my parent images as small as possible and over time a thin provision disk can start to grow on you if you don’t watch it – be it from downloading installers, updates, or even running disk defrag. While there isn’t a simple, one click button in the View Administrator Console there is a fairly easy manual method using vmfkstools.

    Before we can use “vmkfstools” to shrink the VMDK file we must zero out any unused space on the thin provisioned disk. A simple way of doing this is by using a free utility called SDelete from Sysinternals.

    Read More “Shrink a thin provisioned VMDK disk”

  • vSphere 5.1 Release Date leaked, maybe?

    Looks like Sammy Bogaert over at Boerlowie’s Blog has possibly found the release date of vSphere 5.1… maybe?

    I was about to download vSphere Update Manager PowerCLI 5.0.

    I followed the main site and wanted to check the documentation first. So I clicked the Documentation button.

    vmware update manager

    This lead me to the Docs of Update Manager PowerCLI 5.1! That’s right, 5.1! With a release date of 10 September 2012.

    vsphere5.1 release date

    None of the links for 5.1 work, so no news on any new features…

    Guess somebody at VMware was a bit too fast to update the website

    Nice find Sammy, guess time will tell if the Sept. 10th date is the actual release date or not.

  • How to add Realtek R8168 to ESXi 5.5 Update 2 ISO

    Realtek

    Over the past weekend I was working on a whitebox ESXi host and wanted to upgrade it to ESXi 5.5 Update 2 from an older version of ESXi 5.1 using a realtek R8168 network card. While I could have performed an in place upgrade, such as via command line, a clean install was preferred. However, VMware has removed a number of NIC drivers from ESXi 5.x and trying to install with the base ESXi image would result in a “No Network Adapters” error during install.

    In order to do a clean install you have to re-add the Realtek R8168 NIC drivers back into the ESXi 5.5 image, otherwise a NIC will not be found and thus ESXi will not install. These are the steps to easily re-add the Realtek R8168 drivers into ESXi 5.5 ISO by making a custom ESXi 5.5 image.

    Read More “How to add Realtek R8168 to ESXi 5.5 Update 2 ISO”

  • Edit Virtual Hardware 10 VM’s with vSphere 5.5 U2 client

    When ESXi 5.5 came out so did a new virtual hardware version, 10, as well. However the ability to edit virtual machines have have been upgraded to virtual hardware 10 was restricted to only the vSphere web client. In some cases people have put off upgrading to virtual hardware 10 either for dislike of the web client or knowing you cannot edit the VM in the event of the web client being down.

    That all changes today, VMware has just released vCenter 5.5 Update 2 today and one of the “resolved issues” in today’s release notes is the ability to now edit virtual machines with Virtual Hardware 10 using the vSphere thick (C#) client.

    edit virtual hardware 10

    Read More “Edit Virtual Hardware 10 VM’s with vSphere 5.5 U2 client”

  • Easy ESXi 5.5 upgrade via command line

    ESXi 5.5 was just released general availability (GA) on Sunday (9/22) and I’m itching to upgrade the home lab to run the latest version with all it’s goodies. I wanted to try upgrading my hosts without having to go through the same process that I followed setting up ESXi on the NUC in the first place, injecting custom NIC drivers, etc.

    Enter the command line…

    1. Move all VM’s from the host and then put the host into Maintenance Mode.
    2. Go to the Configuration tab > Security Profile and Enable SSH under Services.
      ssh enabled
    3. Under Firewall, enable httpClient (outbound http).
      httpClient enable
    4. Open PuTTY (or other SSH client) and SSH into your host.
    5. Read More “Easy ESXi 5.5 upgrade via command line”

  • VMware vCenter Server 5.5.0a update released

    VMware has released an update to vCenter 5.5 Server. The new updated, numbered 5.5.0a doesn’t appear to add any new features but instead focus on squishing a number of bugs in the 5.5 version – mostly around vCenter Single-Sign-On and the vSphere web client.

    Issues resolved with this release are as follows:

    1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
    2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
    3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
    4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables

    Read More “VMware vCenter Server 5.5.0a update released”

Leave a Reply

Your email address will not be published. Required fields are marked *

One Comment

  1. Mike – Great article! Do you know the exact process SRM goes through to change the ip and hostname on a Linux host? I’m assuming it is uses the vmware tools installed on the Linux host?