Quantcast
Channel: VMware Communities: Message List - VMware vCloud Director
Viewing all 7719 articles
Browse latest View live

Re: vCloud Director lost the connection to the vCenter Server


Re: LDAP Sync Error : vCD 5.5

$
0
0

Bump...

 

Am experiencing this same error now with our vCD infrastructure and corporate Microsoft Active Directory. Any idea what resolved it?

 

javax.naming.CommunicationException: mgsops.net:389 [Root exception is java.net.ConnectException: Connection timed out]

- [mydomainname].net:389

- Connection timed out

 

com.vmware.vcloud.common.threadpool.ThreadContextExecutor.execute(ThreadContextExecutor.java:62)

  at com.vmware.ssdc.backendbase.CAkimbiTask$InvokeChildThread.run(CAkimbiTask.java:153)

Caused by: javax.naming.CommunicationException: mgsops.net:389 [Root exception is java.net.ConnectException: Connection timed out]

 

 

TIA

Darren

standalone vmrc for vcloud director console

Re: standalone vmrc for vcloud director console

$
0
0

VMRC Standalone is not supported with vCloud Director.

 

VMware Remote Console 7.0 Release Notes

  • VMRC does not support vCloud Director, vCloud Air, and vRealize Automation virtual machines.

 

Therefore, you must use the provided console system within vCloud Director.

Re: LDAP Sync Error : vCD 5.5

$
0
0

Two notes to kick off:

 

1. You forgot to redact the hostname.net in two other places.

2. Please start a new thread.  Reusing old threads usually causes confusion as to what the problem is, and there is no way for you to mark something as correct (since you didn't create the thread).

 

This isn't even a vCloud Director error.  This is Java stating there is a timeout when connecting your domain.  Can you try putting a specific domain controller into vCloud Director's configuration?  Hopefully one on the same network as the Cells, to avoid firewalls or WAN latency.

Re: standalone vmrc for vcloud director console

$
0
0

Thanks for the reply. Is it possible to open the console via .net sdk or through creating an url for the vm ?

 

for instance if we open the console manually the plugin uses a link https://vcd.xxxxx.de/cloud/VMRCConsole.html to open the vm console.

So, i guess this html page should accept an input like vm's screen ticket to open the console.

if so, can i create an url in any specific format to open the console ?

 

 

 

 

 

Thanks.

Re: standalone vmrc for vcloud director console

Re: standalone vmrc for vcloud director console

$
0
0

Thanks for the links..i ll look into those.


The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Hello All,

vCD : 5.5.1

Today i am facing an issue with my vcd where i cant deploy the new vapp in our environment.

What i checked and made changes.

First i thought its an storage issue. but i have 18.84 TB storage available already out of 44 TB .

Second i change the threshold to minimum of the datastore.

Third i recreated the storage policy but not helpful.

Fourth i added a new storage policy for a different datastore and the vm deployed on it succesfully.

 

So still i am figuring out what is the correct issue there.

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Is that a storage cluster?  If so, how large are the Datastores inside of it?  Do any have at least 310GB Free? (Red threshold of 250 + 60 GB required based on the error state).

 

I also need to know if Storage DRS is turned on.  If so, vCloud Director doesn't determine initial placement.  we send a definition of the VM to vCenter and get a response for compatible datastores.

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Thanks IamTHEvilONE

I was expecting you for helping me out..

Well situation is I dont have sotrage Cluster enabled. Only datastores are playing around with.


Yeah. one thing i have to share . We assigned a separate datastore to each org vdc in our environment. Now the Datastore already part of the production and having 30 TB full. and now we have to use the same datastore and migrate those vms in to the org vdc created for it.

(e.g. Like we have a Team called "ABCaround 250 vms are for them and hosting on the same 44 TB datastore occupying around 30 TB of datastore. now we created a org vdc in same environment and add that datastore 44 TB datstore in to it. some vms are thin provisioned. now we cant build our first vapp to test the environment.even cant migrate any vms from that team.)

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

The only other limiting factor I can think of is the Organization vDC's Storage Policy doesn't have enough space left in it.

 

Here is at least a starting point, may I have a screen capture of:

 

1. Manage & Monitor > Organization vDCs > Double click the one where deployment fails > Storage Policies tab > I need to see all policies listed here

 

2. Based on the error it seems that we need 60 GB of space to be free, can you just validate that is correct from the source vApp/VMs you are deploying?

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Sure. find the attachment.

The policy client services is the impacted one. SCDemo works fine(Tested that SP for making it sure).

We have enough storage available on our environment in client service datastore .

Pic1.jpg

See the Client services datastore.

01st.jpg

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Yeah one more thing to share. till now i was creating orgvdc with the scratched datastore which was start using by vcloud only.

but this is the org vdc i am using a already being used datastore. Hope this is not causing the issue. (just afraid if it is the reason ?)

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Okay, so it seems fine here from an allocation perspective.

 

Next 2 Screen captures:

 

1. Manage & Monitor > Storage Policies > Screen capture Client Services

 

2. Manage & Monitor > Provider vDCs > Double click the provider vDC backing the Org vDC > Storage Policies > screen capture the storage policies here.


Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

Unless the Datastore is disabled in the Datastore list (managed & monitor), there is no immediate reason for this error state to happen that I can tell.

 

The next test to do, would be to reduce the Red Threshold on this specific Datastore by 70GB and then attempt to provision the vApp again.  If this works, there is something funny with how the threshold is being applied in this situation.

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

I did below now.

1. reduce the red and yellow threshold to 70 and 150 GB.

2. tried to create a small vapp with 30 GIG of space. 

No luck.

Was just suspecting as this is the biggest datastore in our environment 44 TB. Is their any limitation for the max size of datastore support.  Also this datastore extended multiple times till now.

Also i find below URL to run SQL query .Does this will help ?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2062686

Re: The operation failed because no suitable resource was found. Hub "Resources" doesn't have enough "*" storage: required - 60000 MB, available - 0 MB.

$
0
0

yeah, the query could help in case the data is stored incorrectly.

 

I'm not aware of a limit on a given Datastore, which is capped at the database level by the column type (which I think is big int).

Re: standalone vmrc for vcloud director console

$
0
0

HI..i tried the method provided in the links. Unfortunately it is not working in my case.

Meanwhile i found the Open-VMConsoleWindow cmdlet in powercli perfectly opens the vcloud vm console.

It creates a link in the format  " file:///C:/Program%20Files%20(x86)/VMware/Infrastructure/vSphere%20PowerCLI/VMConsoleWindow/VMConsoleWindow.html?host=147.73.89.34&vmid=vm-20&vmName=VM-01&ticket=cst-A5ri4bi43PVmzD46hLwEfjicMXdd567F2PBC4mzsD/R/O9eCBTpLR9PYKWlc6fssEqNFtUDLTn32Ewy7eFBNht7YLlhBT613eXZbbeZdTeWeBWa2NE85xMSgkj7EX51/wkWKDK95DD0mcGI2wgNpodilETJ0ZWtpaG/TxraQlLz8BZkzm8nQBoDbK5TNqCnGMpLYqTUovXM+cIiMztZtkqRQPCAG8dARay0IWaunRIb4cXYU1yo71TSTguUsJQeMi/jqDRBoeq+CgLAdZGqs6D64Vqsw03N2+KMrcyPUwZty6WuRXWtrd32sRAc54BNR0L0Lw4aovBf3/97SlUahAD9UNsqRPTSO6fxUSoOl2Sh7R5QLwLMM5ClyObPXYvFs-nhkzBiJWLJP2GrsFGRDhAjFW6jCFXO2D3poPOw==--tp-D8:C7:F7:3E:5D:14:A2:21:DB:1D:3A:54:3F:2E:8A:F2:EA:A4:65:91--&tunnelConnection=1"



I tried generating a similar url. But i couldnt open the console. I guess the ticket is some form of encoded string.

AcquireTicketMethod() geneartes a screenTicket which starts with "mks:\\".

can u please help me to understand what kind of encoded string is provided as ticket parameter in the url ?



Thanks,

Viewing all 7719 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>