Highlighted
Timothy4
2 Bronze

successfully deployed vApp but no web console?

So I had our vm admins deploy the vApp in our lab.

All 3 machines come up fine in their vApp container + the Data Collector machine.

Now the Deployment guide says I need to register the collector. I got onto the registration form ok through IE on the collector host but I tried using the default credentials (appadmin\Changeme1!) but it said it couldn't contact the server.

So I skipped that step and went to try and log into the application server directly.

It doesn't give a URL in the deployment guide only saying:

"Open a web browser and browse to the ProSphere Application by specifying the URL address (usinc the IP address or hostname) of the virtual machien where ProSphere Appplication was depoyed."

(by the way... why did I have to type that... your java box here disables paste! ??? )

If I try http://hostname I get a 404

https://hostname I get a security certificate warning then an "Internet Explorer cannot display the webpage"

I checked for TLS 1.0 and it's checked....

what now? The hosts are apparently running SuSE when I know mabye 5 things about.

-- Tim

Tags (2)
0 Kudos
7 Replies
Timothy4
2 Bronze

Re: successfully deployed vApp but no web console?

Sorry, but I don't see an edit button either so you'll have to exuse my type-o's (I hate this keyboard)

0 Kudos
ConorLawlor
3 Argentium

Re: successfully deployed vApp but no web console?

Hi Timothy

Ensure the conf. details input at installation is correct.


Please restart the ProSphere Vapp:The correct procedure is to start the VMs at the vApp level in vSphere Client (right-click the vApp and use the power off/power on options).  This will ensure that the three VMs start up/shutdown in the correct order.  Do not start the VMs individually. All of the VMs should be set to start and stop at the same time.  You can confirm this by right clicking the vApp, selecting Edit Settings, then Start Order.  All ProSphere VMs should be  in Group 1 (recommend you move Collectors into that group if you have any).

After restarting review the  monitor services on the following virtual machines:

◆ProSphere Application
◆Discovery Engine
◆Historical Database

To view all running services, type the following URL in a browser:

https://<host-name|ip-address>/cgi-bin/mon.cgi

From the service monitor page all required Services should be showing as running (green). MSA Configuration Proxy Service is disabled by default in /1.6 and will not be used till later builds of ProSphere to interact with other products.

Putty into each VM as root user and ensure the details within the /etc/ovfEnv.xml file is correct

Open a browser and point it to the hostname of the ProSphere SRM Application VM hostname: https://<host-name|ip-address>/ to see if will open.

********************************************************************************

You could also try addin the Prosphere VMS  IP and FQDN entries to your local host C:\Windows\System32\drivers\etc\hosts file:

            # ProSphere 1.6
10.**.**.***      prosphere16.***.***    prosphere16
10.**.**.***      discovery16.***.***    discovery16
10.**.**.***      database16.e***.***    database16
10.**.**.***      collector16.e***.***   collector16

Open a browser and point it to the hostname of the ProSphere SRM Application VM hostname: https://<host-name|ip-address>/

********************************************************************************

If the issue remains after checking the above open an SR with Support

Regards

Conor

0 Kudos
Timothy4
2 Bronze

Re: successfully deployed vApp but no web console?

1. shut down everything

2. started the vApp from the container (they came up in the correct order)

3. waited 15 minutes

4. still no https access on application server

5. /cgi-bin/mon.cgi => "cannot display"

I can get an SSH connection to the App server but what's the root password supposed to be?

Changeme1! doesn't work as root or appadmin.

0 Kudos
ConorLawlor
3 Argentium

Re: successfully deployed vApp but no web console?

Hi Timothy,

The default root password is documented in Security Configuration Guide page 13

https://support.emc.com/docu40179_ProSphere-1.6.0.2-Security-Configuration-Guide.pdf?language=en_US

May be best if you open an SR so support can review

Regards

Conor

0 Kudos
Timothy4
2 Bronze

Re: successfully deployed vApp but no web console?

Yeah, I just opened one as it seems this isn't a simple problem.

(I thought vApp was supposed to make this easy)

Apparently that document just showed up today.

https://support.emc.com/products/15995_ProSphere/Documentation/

So I can see how I missed it.

0 Kudos
ConorLawlor
3 Argentium

Re: successfully deployed vApp but no web console?

Hi Timothy,

The above issue can occur if there is no DNS service configured or DNS details were missed typed during installation. DNS is a requirement of ProSphere.

From vSphere client ensure the networking information such as DNS Servers and Search Domain for all ProSphere appliances VM is correct.

Regards

Conor

0 Kudos
Timothy4
2 Bronze

Re: successfully deployed vApp but no web console?

I checked that ovfEnv.xml and the DNS servers look ok.

There's some errors in the apache logs though so I'm going to let support handle this over a webex later today.

Thanks for the speedy replys Conor.

-- Tim

0 Kudos