Updating SRM Server IP Address

I had to update the IP address of a VMware SRM server recently, but after the update, the SRM service wouldn’t start.  Of course…why should that be that simple?!

Symptoms:

SRM IP 01

 

From %AppData%\VMware\VMware Site Recovery Manager\Logs\vmware-dr-x.log:

[2009-03-25 15:50:20.800 ‘MainVcConnection’ 2024 info] VC Connection:
Logging in as user ‘srm.service’

[2009-03-25 15:50:21.050 ‘MainVcConnection’ 2024 info] VC Connection:
Logged in session 90C5B71A-7DB4-4E53-9E1F-22B879DE3722

[2009-03-25 15:50:21.691 ‘App’ 2024 error] The proxy spec for
extension com.vmware.vcDr points to 192.168.254.12,
not to this host

[2009-03-25 15:50:21.691 ‘DrServiceInstance’ 2024 error] Registration
with the local VC server is not valid

[2009-03-25 15:50:21.691 ‘DrServiceInstance’ 2024 warning]
Initializing service content: Unexpected exception ‘class Vmacore::Exception’
Registration with the local VC server is not valid

[2009-03-25 15:50:21.691 ‘App’ 2024 error] Application error:
Registration with the local VC server is not valid. Shutting down …

[2009-03-25 15:50:21.800 ‘App’ 1516 info] [serviceWin32,414]
vmware-dr service stopped

Ah-ha!  vCenter is pointing to the old IP, which clearly isn’t this SRM server.  That’s why the service isn’t starting.

Turns out that when SRM configures vCenter it gives it the SRM server’s IP address instead of it’s hostname/FQDN.  So much for DNS rules all VMware environments.

 So where to change this setting?

Running C:\Program Files\VMware\VMware Site Recovery Manager\bin\srm-config -cmd info -cfg ../config/vmware-dr.xml provides me the following information:

SRM IP 02

So, it’s the SRM extension that’s holding onto the old IP.

The fix:
Update the IP address in C:\Program Files\VMware\VMware Site Recovery Manager\config\extension.xml file in two spots

a.      <server>
<url>http://192.168.254.12:8095</url>

b.     <client>
<url>http://192.168.254.12:8096/VMware-srmplugin.exe</url>

2.
Run C:\Program Files\VMware\VMware Site Recovery Manager\bin\srm-config -cmd updateext -cfg ../config/vmware-dr.xml –extcfg ../config/extension.xml

SRM IP 03

And voila…

SRM IP 04

2 Responses so far.

  1. Ben Conrad says:

    Bingo, nice post.

  2. Dimitri says:
    Worked without issues. Great instructions.

    Still cant believe there are no official instructions from VMware on how to do this.

    Thank you.

Leave a Reply to Dimitri Cancel reply