Error Message

GUI





TEXT
(excerpt)

[07/07/2015 07:51:30] Checking to see if CS is reachable from MH
[07/07/2015 07:52:26] Output: HTTP/1.1 404 Not Found. Could not connect to proxy target

404 Not Found. Could not connect to proxy target
[07/07/2015 07:52:26] Return code: 1024
[07/07/2015 07:52:26] fancy_die
[07/07/2015 07:52:26] ADD_HOST_CS_NOT_REACHABLE
[07/07/2015 07:52:26] fancy_dead

Other issues can cause this symptom however this article is focusing on the typical issue when NAT is enabled for a CS installed on a VM.

The MH does not have network connectivity to the NAT enabled CS installed in a VM.

Create an entry in the hosts file of the MH so that the hostname of the CS resolves to the IP of host server (external IP).

In other words, let's say for discussion purposes that we have a CS as follows:

Guest Server:                192.168.10.12 (ESX for example)
CS hostname:                VOM_CS
​CS IP:                          10.148.105.44 (real IP of CS)

1)  Check nslookup on both the CS and MH to see if it resolves to the IP address of the Guest Server,  If nslookup returns an error or the real IP of the CS, then the hosts file of the MH will need to be modified.

# nslookup VOM_CS
Server:         nnn.nnn.nnn.nnn
Address:        nnn.nnn.nnn.nnn

Non-authoritative answer:
Name:   VOM_CS
Address:  10.148.105.44
======================================
# nslookup VOM_CS
Server:         nnn.nnn.nnn.nnn
Address:        nnn.nnn.nnn.nnn

** server can't find VOM_CS: NXDOMAIN


2)  Configure an entry on the MH so the CS will resolve to the NAT (converted) IP of the Guest Server.

vi /etc/hosts




192.168.10.12        VOM_CS

​
 

Oftentimes, a sites DNS will have an entry where the hostname of the VOM CS (also known as CMS or MS), will resolve to the real IP of the virtual machine (or possibly no entry at all). When NAT is enabled, there is no route from the MH to the CS.  The MH must be able to resolve the hostname of the VOM CS to the guest server's IP and Network Address Translation (NAT) will forward the packet to the VOM CS.

This issue was reported on a Linux VM CS version 6.1 but could apply in similar environments.