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

Re: Locate VM

$
0
0

Hi,

 

So I've managed to find an entry in the SQL DB for the VM in question, but still unable to locate it within vCloud.  The scanrio is I have 2 VMs with the same name,  one is present within vCloud but not in use and powered off.  The other is meant to be in vCloud but I cannot find it within the vApp where it's meant to be located, the query I ran was:

 

select ID, DATACENTER_ID, FILE_NAME, LOCAL_FILE_NAME, POWER_STATE, UUID_BIOS, RESOURCE_GROUP_ID from dbo.VPX_VM where LOCAL_FILE_NAME like '%obfuscated-vm-name%'

 

 

Which returned the two following VMs:

 

ID    DATACENTER_ID    FILE_NAME    LOCAL_FILE_NAME    POWER_STATE    UUID_BIOS    RESOURCE_GROUP_ID

16046    2    ds:///vmfs/volumes/50d85ade-24897e14-513f-3440b5bec418/obfuscated-vm-name (86ebb346-2295-440b-b670-541f8b1ed3c0)/obfuscated-vm-name (86ebb346-2295-440b-b670-541f8b1ed3c0).vmx    /vmfs/volumes/50d85ade-24897e14-513f-3440b5bec418/obfuscated-vm-name (86ebb346-2295-440b-b670-541f8b1ed3c0)/obfuscated-vm-name (86ebb346-2295-440b-b670-541f8b1ed3c0).vmx    1    001539cf-eb5b-4652-ae52-e5be386a1aea    117

25003    2    ds:///vmfs/volumes/50d85ade-24897e14-513f-3440b5bec418/obfuscated-vm-name - CLONE 29%2f08%2f2013 16_21/obfuscated-vm-name - CLONE 29%2f08%2f2013 16:21.vmx    /vmfs/volumes/50d85ade-24897e14-513f-3440b5bec418/obfuscated-vm-name - CLONE 29%2f08%2f2013 16_21/obfuscated-vm-name - CLONE 29%2f08%2f2013 16:21.vmx    0    42152789-12d9-4a24-3a5b-374525cb34a4    117

 

As far as I can tell, they both appear to be within the same resource group, any way I can narrow this down to locate the vApp which they should reside in?

 

Many thanks,

 

James


Re: vCloud Director 5.6 + vSphere Replication 5.8

$
0
0

The support informed me that this problem seems to be a bug. My ticket was escalated to the development team.

Re: vCloud Director 5.6 + vSphere Replication 5.8

$
0
0

That's interesting.  I've had the following reply...

 

vmware support wrote:

 

So I've looked into this a bit further and can confirm that you cannot connect vSphere Replication to vCloud Director. You can only connect to vCloud Air.


I can also tell you that vCloud Director for Service Providers is not the same as vCloud Air

Re: vCloud Director 5.6 + vSphere Replication 5.8

$
0
0

Support reply me with this...

 

Replication and disaster recovery  are not features listed for vCloud Director SP

Re: vCloud Director 5.6 + vSphere Replication 5.8

$
0
0

And seems that the documentation was modified to include this information:

 

001502-01

Updated topic About Disaster Recovery to Cloud to clarify that vSphere Replication for Disaster Recovery works with vCloud Air.

Re: Unable to access vCloud Director VM console

$
0
0

Fixed it.

 

1 - Upgrade from vCD 5.6.3 to 5.6.4.

2 - Something with the VMs we had deployed for testing. We erased them and the new ones did not have the behavior.

Re: vCloud Connector - Unable to copy vApp from vCloud Director to vSphere

$
0
0

Solved.

 

Created a new catalog and DID NOT publish it. Used it for copying. Went smoothly.

Re: Network Adapter Issue - Using the PHP SDK

$
0
0

Hi,

 

The approach used to update the network adapter is to first  remove the NIC  currently in the virtual machine.

As the available adapter cannot be updated, it can only be replaced with the new configuration required once the NIC type is created.

 

Please let me know if you have any concern on this.

 

Regards,

Kapil


Re: vCloud Media Upload Error: Thumbprint Mismatch

$
0
0

Did this fix made it into the 5.6.3 vcloud for service providers?

Re: vCloud Media Upload Error: Thumbprint Mismatch

$
0
0

vCD 5.6.x does fix this via new code.

 

We offer the ability to put the Front End SSL Cert into the Public Addresses section, so that is where the thumbprint is gathered from (not the local cell).

Re: vCloud Media Upload Error: Thumbprint Mismatch

$
0
0

Thanks for you prompt answer.

 

The text in the Public Address page is:

 

"If you specify an address in vCloud Director secure public URL, you must place the certificate chain for that address here.

The certificate chain must consist of zero or more PEM-encoded X.509 certificates."

 

However VCD expects the Certificate itself here and not the intermediate certificates. The word "chain" is confusing here.

 

At first I entered our intermediate certificates from Comodo here. And then the thumb-print mismatch error occurred.

Re: vCloud Media Upload Error: Thumbprint Mismatch

$
0
0

the answer to this is dependent on your configuration.

 

Typically, there are around 3 certificates to a "chain"

 

There is the leaf certificate, which is signed to the actual FQDN of the website you are visiting.  This is what you would have purchased from Comodo.

 

This leaf says my parent (authority) is Comodo's Intermediate.  So that'd be the second.

 

Comodo's Intermediate certificate says that it needs to be validated by its parent (root).


I've seen multiple intermediate certificates, so there could be 4 or even more.


all you should have to do is paste in all 3 parts as x509 plain text ... kb.vmware.com/kb/2070908 can help validate if the thumbprints do actually mismatch.

Re: VMRC black screen & disconnected

$
0
0

PercaFluviatilis wrote:

 

I am getting this error to, when open a console in vCloud Director.

 

I dont have this issue in vCloud 5.5 but it come in vCloud 5.6 Using self signed certificates.

 

Can someone please elaborate how to fix this?

 

This is an old post so you probably fixed it by now - but I just noticed the same. Always used 5.5 in my lab with self-signed certificates and never had the issues. Now installed 5.6.4 and got the disconnected console and I too needed to browse manually to the consoleproxy IP and trust the certificate. Once that was done, the console popped up in an instant.

Re: VMRC black screen & disconnected

$
0
0

Follow this if you aren't using IE on Windows (chrome or Firefox):


kb.vmware.com/kb/2058496

Re: vCloud Director 5.6 + vSphere Replication 5.8


vCloud to vRealize Upgrade Options

$
0
0

We have a number of vCloud 5.1 and 5.5 instances and we need to upgrade to vRealize 6.x.

 

Can someone point me in the right direction of upgrade paths and options ?

 

Thanks

Re: vCloud to vRealize Upgrade Options

$
0
0

vRA and vCloud Director are two separate products ... there is no "upgrade" from one to the other, it's more of a migration.

 

I would suggest talking to someone from VMware sales/services, as there are some differences in how they work and are setup to ensure they cover you business needs.

Re: Locate VM

$
0
0

VMWare support have directed me to this blog which looks to be able to remedy my issue, in that I can reassociate the VM within vCloud with the correct and original VM within vCenter:

 

http://chrisbrothers.me/vcloud-error-could-not-find-object-with-moref-vm-xxx-and-vc-id-xxx-xxx-xxx-xxx-xxx-in-inventory-…

 

However since the original VM is powered-on, and VM which vCloud is pointing to is powered-off can anyone advise will the vCloud VM reflect the correct power state once it is associated with the original VM?  Will doing this affect the power state of the original VM?

 

Of course I've gone back to support to raise these questions, but he decided to close the case as soon as he linked me to that third party article, so hoping communities might be able to offer some advice?

Re: Exporting a catalog using OVFTOOL - syntax issue

$
0
0

Thread necromancy!

 

I just ran into the same "Unknown locator query key" error trying to upload an OVF into a vCloud Director catalog.  The problem is the special characters in the name, in my case the VM's name contained a '&', in the dialog box that auto populates the vApp name I just removed it and the upload proceeded just fine.

Re: Exporting a catalog using OVFTOOL - syntax issue

$
0
0

yeah, it happens that the API call uses the & symbol as a delineation marker and it incorrectly breaks on the one from the catalog name and fails to find it.  I think it cannot be in the name of the catalog and or the name of the VM and or name of vApp at the time of upload.

Viewing all 7719 articles
Browse latest View live


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