I was following along this blog that showed me step by step how to setup vSphere Replication with SRM - SRM 5 vSphere Replication – how to install and configure. And I got down towards the end where I have to Configure the VRMS Connection. During my setup attempts I kept getting this error: "VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: 'Unexpected status code: 404'."
This led me to this VMware communities post: http://communities.vmware.com/thread/330733
I followed along with the suggested work around to use FQDN vs IP in the configuration setup and that still didn't work for me. I use DNS in my home lab because I'm a good sysadmin. But for some reason I kept on getting this error popping. So I went into the appliance and found out that the two sites couldn't ping each other without the FQDN. If i just used the simple hostname, then it would not be able to ping. If i used FQDN, then I could ping. /etc/hosts to the rescue.
If you are having a problem with getting these two pairing to work, then DO NOT sit there and remove the appliance and rebuild it 4x like i did. simply edit the hosts file of each VM and add the vCenter servers of both sides. To do so
{codecitation}
vi /etc/hosts
i {insert}
IP_OF_VC_1 {tab} FQDN {tab} hostname
IP_OF_VC_2 {tab} FQDN {tab} hostname
{escape button}
:wq
{/codecitation}
This is needed because the appliance is not given a hostname of hostname with a domain during deployment. Don't bother trying to give the appliance a hostname either. As soon as you reboot the appliance, the hostname "record" will re-appear. The /etc/hosts file on the other hand will be persistent across reboots
