Secondary Node(s) Fail to Join Oracle Virtual Desktop Infrastructure Center
Last updated on AUGUST 30, 2013
Applies to:Oracle Virtual Desktop Infrastructure - Version 3.3 to 3.5 [Release 3.0]
Information in this document applies to any platform.
While working to configure a secondary node as part of an Oracle Virtual Desktop Infrastructure (VDI) Cluster as outlined in the formal product documentation, the VDI Administrator may receive the following error during the post-installation setup using the vda-config command:
For reference, here is a sample excerpt showing the condition:
pinging cluster agent . - cluster agent is available
Calling /opt/SUNWvda/sbin/vda-center agent-ping -d -f -u root -P vdi1.oracle.com
the time difference in miliseconds: 
+ Joining Oracle VDI center...
Calling /opt/SUNWvda/sbin/vda-center join -h vdi2.oracle.com -l /var/adm/log/vda-config.2011_12_01_17:47:28.log -s -f -u root -P vdi1.oracle.com
Failed to join VDI center at vdi1.oracle.com: New host vdi2.oracle.com refuses to join VDI center: Failed to import VDI Center data. Unresolved host in map.
Failed to join Oracle VDI center at host vdi1.oracle.com.
Common Agent Container (vda) restarted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms