Was this a fresh deployment of 188.8.131.52 or an upgrade from a previous version?
If this was a fresh deployment the above issue can occur if information was missed typed during installation or if there is no DNS service configured. DNS is a requirement of ProSphere.
From vSphere client verified and confirm that all FQDNs & IP addresses of the ProSphere Vms etc.. are correct, ensure the networking information such as DNS Servers and Search Domain for all ProSphere appliances VM is correct.
Putty into each VM as root user and ensure the details within the /etc/ovfEnv.xml file is correct for FQDN names of the VMs.
Please open an SR with Support for this issue as it may need to be looked at in more detail.