vSphere Replication appliance does not integrate with vCenter

[automatyka]

vSphere Replication appliance does not integrate with vCenter (I cannot see vSphere Replication Tab, not even vSphere Replication configuration when right-clicking a particular VM.

Only warning i have received during deployment process was the warning that it will bind with vCenter Extension vService.

I have relogged to vCenter, even rebooted vCenter, still nothing...

Another weird symptom is that when i browse web clients vCenter Server Extensions - it can't load it at all (circle spins round and round with no effect what so ever) - same thing when i try to browse vApps...

I have tried unregister vRA from vCenter from the vRA configuration site, but it has told me "Extension management error: org.apache.http.NoHttpResponseException: The target server failed to respond".

Also the "VRM service is stopped", as i can read on the bottom of configuration page (starting it only result in temporary "started" status, and "stopped" again).

vSphere Client shows that vSphere Replication appliance is present (with dependency: vCenter Extension Installation) in vService Manager in vCenter Solutions Manager tab.

[mvalkanov]

Hi,

Please check /var/log/boot.msg inside the VR appliance and also /opt/vmware/hms/logs/hms.log.

Looks like either registering VRMS as extension of vCenter has failed or VRMS process failed to start.

Perhaps you can also take a look if anything seems to be broken at the VRMS extension data in vCenter - https://vcenter_address/mob/?moid=ExtensionManager&doPath=extensionList["com.vmware.vcHms"]

Regards,

Martin

[automatyka]

ending of boot.msg looks like this:

<notice -- Jan 23 13:09:55.882115000> 'hms start' exits with status 0

Master Resource Control: runlevel 3 has been reached

Failed services in runlevel 3: network

Skipped services in runlevel 3: splash

<notice -- Jan 23 13:09:55.883850000> killproc: kill(2025,3)

entire /opt/vmware/hms/logs/hms.log:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vmomiListener' defined in class path resource [META-INF/vlsi.xml]: Cannot resolve reference to bean 'correlationStep' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'correlationStep' defined in class path resource [META-INF/vlsi.xml]: Cannot resolve reference to bean 'dispatcherStep' while setting bean property 'nextStep'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dispatcherStep' defined in class path resource [META-INF/vlsi.xml]: Cannot resolve reference to bean 'validationStartStep' while setting bean property 'nextStep'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validationStartStep' defined in class path resource [META-INF/vlsi.xml]: Cannot resolve reference to bean 'adapterServer' while setting bean property 'adapterServer'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'adapterServer' defined in class path resource [META-INF/vlsi.xml]: Cannot resolve reference to bean 'hmsManagedObjectFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'siteManager' defined in class path resource [META-INF/hmsmo.xml]: Cannot resolve reference to bean 'moContext' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'moContext' defined in class path resource [META-INF/hms.xml]: Cannot resolve reference to bean 'serverRegistry' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vcExtensionChecker' defined in class path resource [META-INF/vlsi.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.TransportProtocolException: org.apache.http.NoHttpResponseException: The target server failed to respond

        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)

        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)

        at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)

        at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)

        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)

after followin Your link ( https://vcenter_address/mob/?moid=ExtensionManager&doPath=extensionList[%22com.vmware.vcHms%22]https://vcenter_address/mob/?moid=ExtensionManager&doPath=extensionList[%22com.vmware.vcHms%22]https://vcenter_address/mob/?moid=ExtensionManager&doPath=extensionList["com.vmware.vcHms"]) i have received:

client	ExtensionClientInfo[]	Unset
company	string	""
description	Description	description
dynamicProperty	DynamicProperty[]	Unset
dynamicType	string	Unset
eventList	ExtensionEventTypeInfo[]	Unset
extendedProductInfo	ExtExtendedProductInfo	extendedProductInfo
faultList	ExtensionFaultTypeInfo[]	Unset
healthInfo	ExtensionHealthInfo	Unset
key	string	"com.vmware.vcHms"
lastHeartbeatTime	dateTime	"2014-01-23T10:36:28.486999Z"
managedEntityInfo	ExtManagedEntityInfo[]	Unset
ovfConsumerInfo	ExtensionOvfConsumerInfo	Unset
privilegeList	ExtensionPrivilegeInfo[]	Unset
resourceList	ExtensionResourceInfo[]	Unset
server	ExtensionServerInfo[]	Unset
shownInSolutionManager	boolean	false
solutionManagerInfo	ExtSolutionManagerInfo	solutionManagerInfo
subjectName	string	""
taskList	ExtensionTaskTypeInfo[]	Unset
type	string	""
version	string	"0.0.1"

Looks either default, or not installed/unconfigured to me. I can see the output of the logs and it clearly indicates network connectivity problem.

Could You help me fix this?

EDIT: i have checked firewall settings (VR is in different subnet than vCS) and it allows all connectivity.

[mvalkanov]

Hi,

VRMS failed to populate the extension information in vCenter, because it couldn't talk to it.

Please check the values of hms-localvc-address and hms-localvc-port in /opt/vmware/hms/conf/hms-configuration.xml and also the evs:Address, evs:HttpPort and evs:HttpsPort in /opt/vmwate/etc/vami/ovfEnv.xml.

If the port values do not match the current settings in vCenter - power off and power on (restart won't work) the VR appliance and the /opt/vmware/etc/vami/ovfEnv.xml and hms-configuration.xml should be automatically updated.

If the evs:Address is not a FQDN (not and IP address and does not contain the domain suffix path), please fix VirtualCenter.FQDN advanced setting in vCenter to include the domain part and do the power-off and power-on of the VR appliance to pick up the updated environment settings.

Regards,

Martin

[automatyka]

/opt/vmware/hms/conf/hms-configuration.xml:    

hms-localvc-address points to vcenter server address, and port is configured to 80, so i presume that it's correct.

Values from /opt/vmwate/etc/vami/ovfEnv.xml are also correct.

evs:Address is not an FQDN, it's static IP, just as every adress i have configured in my vmware network (vcenter FQDN in advanced settings also is put as static ip).

[rjahuja]

did someone figure out a fix for this?

[john23]

Try to give the FQDN name in C:\Windows\System32\drivers\etc\hosts file

<ip> <hostname> <full host name>

on both the sites. and try to deploy.

-A

[automatyka · Accepted solution]

It works when having vcenter and vRM on the same subnet. Maybe my router/firewall is buggy, nevermind. Dropping the case.

[GoggiP365]

Different subnet in my case today also meant different domain.  Resolved the issue for me when VR and VC were put on the same domain address.   For some reason VR had been working with old fqdn untill upgrade happened.  Hope this helps somebody as it did me today.