• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

vCloud Director Network and Remote Console issues

V

Vader

Supreme [H]ardness
2FA
Joined
Dec 22, 2002
Messages
5,137
I stood up vCloud Director in my lab and after I setup my test organizational vDC, I setup a test vApp.

I have 3 VM's, Web/App/DB set up and I have two problems:

1. I can't start more than 1 server, says there aren't any resources available, when I know that's not true becuase i've allocated enough resources. I have an internal port group setup on a dvSwitch and it states that I only have one connection in the network setup..which is odd or i'm missing something so i'm thinking that's it?

2. I can not connect via the remote console to the VM's themselves to set them up. I'm thinking there is some sort of connectivity issue, but not exactly sure. the management VM's, vCloud Director etc are all in the same subnet as the test vApp VM's.

Any insight would be appreciated. I'll still research it..but nothing glaring coming out of a search at this point.

Here are some screenshots of said issues.





Resource Allocation:



http://imageshack.us/photo/my-images/853/vcloud3.jpg/



Here is the error for starting the other machine..not sure how i'm outside of availability constraints....probably something easy that i'm just not seeing at the moment.




Here is the cluster info:

 
Last edited:
There are multiple places you can restrict the number of running VMs without regard to actually being over resource limits, but will give resource limit errors. In the quotas section of the Org policies, or in the allocations of different types of org vDCs, or in the quotas section of organization user properties.

"2. I can not connect via the remote console to the VM's themselves to set them up. I'm thinking there is some sort of connectivity issue, but not exactly sure. the management VM's, vCloud Director etc are all in the same subnet as the test vApp VM's."

Do you mean you cannot connect to the remote console of the VMs through the vCloud Director interface, through vSphere, or both...
 
I'll need to see all the details on your org/vdc network panes in vcd. it's got a million and one options.
 
The VM's are set to unlimited in the this org/vdc and by the user. I've attached a few more screenshots. Also..I can get to the VM console via my vCenter appliance but not through vCloud Director. I have the Remote Console Plugin installed and it launches but just sits at connecting. That's really not as important as the other issue, obviously....but would like to get that resolved as well. Maybe DNS could be the problem..but i've verified DNS is setup and I manually added all the entries.
 
Last edited:
I'll dig through mine as soon as it's back online (updating array firmware right now).
 
oh, for the can't-start, what's HA set to for "allow availability constraints?"
 
It was set to enable, I disabled it and now the VM's start. I'm not sure where the "constraint" is. There's certainly enough resources to accomodate availability?

Any ideas on the remote console?

Thanks!;)
 
I turned off Iptables firewall on my CentOS install that I have for vCloud Director..still can't connect..very strange. I can see the screen in the vApp screen, just can't connect using the remote console.
 
Actually, yes..it was in my install script...hmmmm
 
Last edited:
Vader said:
It was set to enable, I disabled it and now the VM's start. I'm not sure where the "constraint" is. There's certainly enough resources to accomodate availability?
Click to expand...
Well it might appear that way to you ;). Just keep in mind what your slot sizes are, if applicable. If you have any reservations on any virtual machines, and you're using the the number of host failures the cluster tolerates admission control policy, then you might have a lot fewer slots than you expect.
 
Now this is just getting stranger by the minute. All of a sudden I lost my Proxy eth1 adapater on my vCloud Director Cent OS install. When I do an ifconfig, it only shows the management interface and yesterday it was showing both. Not only that, but I can't get ot the login page of the vCloud Director vm any longer. Sometimes it goes to cannot display page, or it will randomly go to the background of the login page but the login box will not pop up and then error the page out. I'm thinking I may have to start from scratch..beauty of the lab I suppose and i'll get the practice benefit.
 
Hate to raise an old issue but it's rearing it's head again. I never did figure out what caused it the first time and by the time I could look at it again, my vCloud Director demo license expired.

I just stood up the vCloud Director appliance and am having the exact same issue.

I have a very simple network, both the http service IP and Proxy IP are in the same subnet...it just sit's there at connecting when using the vCloud Director Console plugin.

Let me point out, however, I am running nested ESXi5 boxes in the vCloud Cluster, however I do have the networks setup for Promiscuous Mode and everything is working so far with the exception of this.

lopoetve...I need your help...:).
 
Last edited:
Dude, I'll be totally honest - I'm not sure ANYONE actually understands vCloud. I spent 4 months playing with it, licensed, trying to figure out how to make it do cool things, and gave ~up~.

I'll ask one of the Cloud folk today to take a look.
 
Awesome...not really a "show stopper" to continue my testing..but would like to be able to launch the console from the web.....vCloud barks at you when you try to mange the VM's in the vApp using the vSphere client.
 
lopoetve said:
Dude, I'll be totally honest - I'm not sure ANYONE actually understands vCloud. I spent 4 months playing with it, licensed, trying to figure out how to make it do cool things, and gave ~up~.

I'll ask one of the Cloud folk today to take a look.
Click to expand...

Hahaha...I won't lie, he's pretty much right. I'm taking the 3-day vCD bootcamp at PEX and really looking forward to it.
 
lopoetve said:
Dude, I'll be totally honest - I'm not sure ANYONE actually understands vCloud. I spent 4 months playing with it, licensed, trying to figure out how to make it do cool things, and gave ~up~.
Click to expand...

I understand vCloud, but it has enough moving pieces that are early enough in their life cycle that are only 99% or so reliable that you end up with INTERESTING behavior at times.

Proxy console is usually one of the more stable bits. If you are having weirdness with your second eth interface in CentOS, what happens if you assign a second IP to your primary interface and use that IP for the proxy console service.

I'm assuming you are only running one cell.

When you start vmware-vcd on your cell, if you run a "tail -f /$VCLOUD_HOME/logs/cell.log" to watch the startup sequnce, are you seeing any output regarding the proxy after vCD start up has completed?

vCD doesn't bark at using vSphere for console access, but you are WAY better off never touching a VM through vSphere for anything that actually affects the state/configuration of the VM.

Just do a power on or power off and watch the reconfigure commands flow. vCD is very jealous and wants everything to be in a state that it is expecting.
 
Let me rephrase, when you try to manage the VM's in your vApp via the vSphere client, it barks at you..you can still do it..but it warns you that it's managed by vCloud Director.

Not really a big deal..but..essentially not really testing the full capability of vCloud Director. Customers are not going to have access to the vSphere Client when they need to provision VM's..etc...i'm testing this like i'm a customer...so it would be nice to use it on the customer side as well to get the full experience.

I am only running one cell. Here are the results of the "tail" command. Also..both interfaces are up, and can ping both..no issues..no issues on boot up.

 
Last edited:
The tail is a bit late in the startup sequnce to see what I was looking to find. I'm running vCD 1.0.1 but in between the first startup announcement line and 9% started, you can see the vCD portion binding to the IP for the web interface for port 80 and 443.

In the portion betweeen 9% and 18% the proxy interface initializes on port 443, and ports 61613 and 61616 initialize on the vCD IP binding in my config.

When you look at the Cloud Cells option under the "Manage&Monitor>Cloud Resources" tree, you are seeing two green check marks in the line for your cell?
 
I have a status that shows green and vCenter that shows green then the http address for management.
 
FYI..figuired it out..it was IE9..which vCloud Director Console Plugin does not play nicely with. Installed Firefox and the Console Plugin for Firefox and it works fine!

I should've known 99% of the time it's always the easiest answer...lol...
 
Last edited:
You must log in or register to reply here.
Back
Top