VMware Cloud Community
DarrenMacK
Contributor
Contributor

network issue with eval of vCloud Director 5.1

I've just installed the eval for 5.1, and am having a lot of problems connecting to the UI.  It seems during install (and in the network configuration) it only allows for a single gateway, which suggests that BOTH interfaces have to be on the same subnet.  This seems unusual, but I can't see any other way it works.  I have now tried installing it at least four times, with various IPs, and even attempting using different subnets even without the gateway (and hitting it from an IP within the vlan on the second interface)....still no dice.  I am able to login to what appears to be the admin console (port 5480), but when I launch the application or try to connect to the IP by itself or through the UI directory, nothing happens.

Here's the current setup I'm using:

IP1 - 172.16.210.162 / 255.255.255.0

IP2 - 172.16.210.161 / 255.255.255.0

Gateway: 172.16.210.1

I am able to hit:  https://172.16.210.162:5480

but nothing else.  When I try to launch the "application" through that console on port 5480, I get a blank screen and then it times out.

If I try to go to:  https://172.16.210.162/cloud

nothing happens.  Going to just the IP itself (no directory) does nothing.  Trying to go to the other IP (172.16.210.161) does nothing.

What's wrong?

Reply
0 Kudos
10 Replies
DarrenMacK
Contributor
Contributor

(bump)

Reply
0 Kudos
DarrenMacK
Contributor
Contributor

(bump)

Nobody?   VMware doesn't appear to offer support for their eval products, which just seems bizarre to me. If I can't install something to evaluate it, why would I want to purchase it?

Reply
0 Kudos
patrickschindle
Contributor
Contributor

Which Browser are you using? I had similar errors with IE 10.

This is only working if you set Browsermode downwards...use F12 in IE to change it to IE 10 Compatibilty, this

one is working for me.

Regards,

Patrick

Reply
0 Kudos
DarrenMacK
Contributor
Contributor

Thanks, that doesn't appear to work, either.  I have also tried Firefox and IE.

I was able to login as "root" on the system and get an actual Linux CLI prompt this time (last time it put into some kind of Cisco-like CLI?).  There appears to be no firewall installed, but it is only listening on the following ports:

0.0.0.0:111

127.0.0.1:1521

0.0.0.0:22

127.0.0.1:25

:::5480 <-- console works, I am able to get in to this

:::111

:::8080

:::5488

:::5489

:::22

:::40023

I notice that when I click "Application Home" to go to the homepage (which I assume is the main UI), it tries to open the vCloud IP address at port 80, but it's not listening on port 80.  If I try to go to:  http://172.16.210.162:8080 though, I get prompted for authentication.  The currently set root / vmware (default credentials) don't work, however.  I also tried the Oracle DB password it asked for during installation (this is the only password it requested when installing the OVA).  But this also didn't work.

Any idea what that password is?  And/or is this the main UI?  Odd that it would try to open it on port 80 if it installs be default for port 8080.

Reply
0 Kudos
JonathanG
Enthusiast
Enthusiast

yes, this is a pain, been there done that a few times

1. When you deploy the OVF, vCloud creates SSL certs using the IP and hostname you designate at deployment, If you change this IP afterwards it is some command line level of effort to modify vcloud; so don't change the IP after you deploy.

Best way to set the IP, netmask etc is when you deploy the OVF in the vsphere client.

You also define the login and password here for "B" below

A. The OVF configuration URL is https://10.202.183.100:5480/#core.Login- this you use infrequently to perhaps change the database, timeone. Login is root/vmware.

B. The vCloud admin URL is https://10.202.183.100/cloud/ -this you use to create organizations, providers etc. the login is defined in the when you deploy the OVF. You will login here frequently

this is useful: http://www.vmware.com/files/pdf/products/vCloud/VMware-vCloud-Director-51-Evaluation-Guide.pdf

Reply
0 Kudos
DMKIBM
Contributor
Contributor

Unfortunately, there is no listener on port 443 at all, so I can't access either of the URLs listed...which is the whole problem.  Is there a log that shows me why I can't get a listener up on port 443?  I can't access the /cloud directory without it.  I am able to login to port 5480 as root/vmware, but that's all I can do with it without it listening on 443.  I haven't changed the IP from what I selected when deploying the OVA file.

Reply
0 Kudos
JonathanG
Enthusiast
Enthusiast

look for errors in the logs in /opt/vmware/vcloud-director/logs

cell.log

vcloud-container-debug.log

attached is a netstat from my vcloud director

Screen Shot 2013-02-20 at 3.17.38 PM.pngScreen Shot 2013-02-20 at 3.17.52 PM.png

Reply
0 Kudos
DMKIBM
Contributor
Contributor

This issue is finally solved.  I thought it would be worth posting an update, in case anyone else ends up with a similar issue and finds this in a web search.  The problem appears to be with the OVA installation (at least the current 5.1.1 one).  If you manually select the IP for either interface, the installation bombs.  Keep both interfaces (on different subnets/VLANs) as DHCP, and the installation runs fine, and the /cloud directory is available on port 443.  Hopefully VMware will look into this and fix it for their next release.

Reply
0 Kudos
JonathanG
Enthusiast
Enthusiast

Reply
0 Kudos
ealaqqad
Enthusiast
Enthusiast

Actually I have a high doubt that your problem is caused by the Linux reverse path filtering which is enabled by default. If you are putting both IPs for the console & HTTP in the same subnet then you might want to look at the following post:

How to get Redhat 6.2 Linux Second NIC to Ping - Virtualization Team

Hope this help Smiley Happy.

Regards,

Eiad Al-Aqqad

B: http://www.Virtualizationteam.com

B: http://www.TSMGuru.com

Regards, Eiad Al-Aqqad Technology Consultant @ VMware b: http://www.VirtualizationTeam.com b: http://www.TSMGuru.com
Reply
0 Kudos