vMotion in vCloud Director 1.5 problem

Similar Questions

• Storage vMotion in vCloud Director

  Hello

  It is already possible to have a vm to a data store to another without interruption in service (storage vmotion ) with vCloud Director. If this isn't yet - it is planned to apply this? This isn't a feature for the Org Admin, but for the vCloud Admin, especially when - storage systems go to replace. And don't tell me to use a storage-virtualization product. Even those who should be replaced one day ;-)

  That would be average cource, Org-Admin would see several data stores during the migration the vapps. One thing to consider is of course how manage fast-provioned vm. Consolidation is no real option, since the virtual machine must be turned off (unless the gui). And of course, it's a unique solution...

  Thank you

  You should be able to use Storage vMotion directly * BUT * there * traps * you need to be aware of:

  (1) you * need * of storage vMotion virtual machine from this data store in your PvDC

  (2) If you use Fast provisioning (Linked Clones) the Storage vMotion, no he will not keep the format of the source, and * WILL * consolidate the virtual machine.

  If you want to keep the disc format, use the vCloud API and the * move * call the API (it will take care of everything you need to keep it as a linked clone).

  Note: I speak on 1.5.x, as you have profile storage & DTS 5.1, you can manage differently with DTS Maintenance mode >

  Hope this helps,

• Management Pack for vCloud Director (vROps) connection problem / authentication adapter?

  Hello

  I'm trying to configure the Management Pack for vCloud Director (Cloud Management Marketplace |) Solution Exchange) and I seem to be having trouble with the simplest thing. I have the Solution installed and configured for most, but for some reason usually reach out and join the vCD server, or have a kind of authentication problems. When I test the map with appropriate powers (local and LDAP in vCD), I get the error:

  Cannot establish a connection on the target system. Logon failed! using Host = < FQDN > User = < adminuser > @System

  The adapter puts the @System after him, or is this something so simple, that I'm more thinking than he. I'd be happy to post any kind of newspapers if needed, let me know what you need.

  Thanks a ton!

  You HAVE to put @system, as it should work with or without. the base public REST API URL is assigned within vCloud Director? See the manual page, installation 28...

  Have you checked for ports Firewall open between the machine virtual analytical and vCloud Director host?

• vCloud Director - SVMOTION ERROR

  When I try to SVMotion a virtual machine. I get the error "this virtual machine is managed by vcloud Director solution.» It is not recommended to edit it directly. Instead, use the management console.

  The virtual machine is turned off in State

  Please suggest how to SVMOTION a virtual computer managed by vCLOUD Director

  Hello

  Even if it's a warning, we can migrate the virtual machine as long as under conditions are checked.

  Note: migrate through Storage vMotion is possible, but there are several caveats.

  • Make sure that the new data stores have the correct storage policy and are assigned to the correct hosts. There is no vCloud check engine steering investment using this method and it can cause serious problems if you do it right.
  • This is not recommended for virtual machines configured quickly as they are inflated to the full clones.
  • It is not possible for VAAI quickly put into service of the virtual machines being unable to Storage vMotion them vSphere.
  • Balancing of virtual machines on data warehouses is entirely manual.

  Follow each step diligently---> http://download3.vmware.com/vcat/documentation-center/index.html#page/Consuming%20a%20vCloud/3c%20Consuming%20a%20VMware%20vCloud.2.083.html

  VMware KB: Best practice for migrating to new storage in vCloud Director vCloud infrastructure

• VCloud Director displays do not Vcenter data.

  Hi guys,.

  I installed VCD 5.5, vsheild Manager and vcenter on a single ESXi 5.5 . I am facing problems with VCloud Director.Although I have attached the Vcenter Sucessfully in VCD, vcenter data not poping upward into Vcd. So the list of hosts is empty. No resouce pool are coming in Vcd.

  Here are my questions coming in my mind... I think I might get hurt

  1 then I installed VCD 5.5, vsheild Manager and vcenter on a single ESXi 5.5 host?

  2. is it a problem with the license... Although all of them are allowed until 2015. ?

  3. do I need to manually install the agent Vcd on ESXi... Although I think that this should be done automatically? If yes how to do this.

  Please tell me where I can be wrong.

  I have attached snapshots of Vcenter and VCD. Please review those and help out me

  All responses will be appreciated.

  Thank you

  Tarun Gupta

  You must create a provider vDC for nothing appear.  This requires some DRS to be on (if you don't have it already done) and requires usually two hosts in a cluster.  This is because you need to spend in maintenance mode to install the agent correctly and can vmotion powerd on the VMS of a host while the other prepares.  It's all part of the installation and Administrator's guide.

• vmotion in vcloud 5.1 configuration

  We are running vcloud Director 5.1. The cluster backend wasn't originally setup with vmotion because we had no dedicated network. We are now successfully vcloud vapps and would add vmotion for the cluster. I read that there may be problems of vcloud after toggle DRS, I wanted to ask if anyone has seen the same thing with vmotion. Thank you

  vMotion is independent of vCloud Director.  You shouldn't do anything in vCloud Director at all.  Simply configure kernel ports as required and out of the race.

  If you have not configured for vMotion, DRS we that will perform the initial placement of the virtual machine... then more nothing else (since there is no mechanism to allow automatic movement of virtual machines).

• Unable to prepare the host to Vcloud Director

  Hi all

  Hope you guys can help me. I try to install the track of vcloud Director version, and I got most of this work. The problem I have now is that I cannot prepare a host. I installing the server in a cluster, I have no shared but only storage using local disks (wondering if this isn't the problem). I added my vcenter server, which is a virtual machine on a host, but I'm still unable to activate the host for its use.

  I read somewhere on the forums that it must be in maintenance mode, but it does not work. In fact if I do this, the host gets a Red Cross in the available column. On the only host I get an error saying connection refused. The other, they say just can't prepare host.

  Any help would be welcome.

  KettieKop

  You need to meet the prerequisites first, specifically to have active DRS.  For the active DRS on the Cluster of hosts in vCenter, for the DRS, you need to have more than one ESX host AND the shared storage.

  Shared storage is a requirement for vMotion (as the DRS is on your virtual machines for load balancing)

  Several hosts is necessary to allow pools of resources (you need a place to load their balance)

  Once you meet the requirements, then you should be able to view the ESX host, when you try to prepare them for vCloud Director.

  Best regards

  Jon Hemming

• MCAK for vCloud Director 5.1

  Hello

  We use the most recent MultiCloud since vCloud Director but now look at upgrading to vCenter vCloud Director 5.1.

  I had seen a mention of help soon with version 5.1 of vCD, but did not see if it is available, or in what version it will be.

  Would you be able to give an indication of support for this version, please?

  Kind regards

  Paul

  You should have no problem with the latest version of MCAK vCloud Director 5.1. All the features of the IAC has been verified. What is not yet supported is 5.1 VCD API, so you would not be able to take advantage of the new features of the product/API with the adapter IN VCD (although you can always write your own custom using HTTP requests process to call the new REST API directly).

• VMware vCloud Director with the NSX Manager installation process.

  Hello world

  I recently planned to deploy VMware vCloud Director (so NSX Manager will be deployed, as part of the process) on an existing environment (existing virtual machines running, virtual switches,...).

  Customers use their virtual machines because they are in production.

  I was wondering if the deployment / installation of NSX Manager would cause no downtime or disturb the workflows running or even break the VM interconnections?

  Thanks in advance,

  Lawrence B.

  I looked at many tutorials, and indeed nothing should happen so that deploy a controller or something else. My concerns were about this "else", as the virtual switches and so on. I guess that the NSX will show existing resources such as the existing virtual switches (and so forth) already configured with vCenter?

  What vCloud Director does is interact with NSX via API.  Calls are exclusive to VXLAN (vdnscope-# resources in the API) and demand to deploy or update an edge.  vCD is not 'show' resources discovered by NSX.  You configure NSX and vCD makes an API call and said ' I want a Board connected to the port groups A and B "or"I want a new vWire of this VXLAN instance.

  Is there a document with the "best practices" for the deployment of vCD?

  Yes: VMware vCloud Architecture Toolkit: Cloud Computing reference Architecture | United States

  The meddle with existing resources, must have dedicated resources for the vCD vendor (aka the cluster in vCenter).  It is better to have that then using a pool of resources to a cluster where neighbour noisy problems can arise.  vCAT above might exceed a lot of that when you read it.

• vRealize device Orchestrator 6.0.3 and vCenter 5.5 5.6 U3/vCloud Director

  Hello world

  I have a few questions on the compatibility between vRO 6.0.3 and vCenter vCloud Director 5.6 and 5.5:

  In vCenter Orchestrator 5.5.2 I plugin to connect the vCO to vCenter (version 5.5.2.1875635):

  

  1. in new vRO 6.0.3 for configuration I can not find this plugin, but when I checked the news of plug-ins I found a plugin vCenter (version vCenter Server 6.0.2.2995112). But how can I connect vRO 6.0.3 vCenter 5.5 (only by the workflow?).

  

  2. a supplementary door on vSphere Web Client integration with vRO. To do this properly first of all I must use SSO authentication mode? It won't work with LDAP authentication?

  3. anyone know if vRO works closely with vCloud Director 5.6? I found 5.5.1.2 plugin, but using this plugin, I can not connect to vCD (in vCO 5.5.2 I have no problem).

  
  

  
  

  
  

  Hello

  (1) Yes, plugin configuration is workflow (this is the approach recommended new plug-ins; the old configuration of Web UI is deprecated and will be removed at some point).

  (2) only the SSO mode is supported; LDAP won't work. Note that the UNIQUE authentication token is acquired in the name of the user logged in vSphere client to Web, so you must make sure that this user has enough permissions to connect to vRO.

  (3) it should be newer versions of this plugin, and compatibility matrix showing which plugin version is compatible with given the vCD. Don't know where it is, however.

• Cannot delete the storage policy to vCloud Director 5.5

  I'm trying to delete the storage policy to vCloud Director 5.5. I did in several vCloud Director organization VDC but stuck with one on the same instance of vCloud Director. I migrated all the VMs, the media and the VAPP model to another storage strategy. I checked in vCenter as there is no VMs who belong to this policy. Always in the vCloud Director, I see 30MB "asked" to this strategy of storage for this VDC.

  Any ideas what I need to check? How can I find what always uses this storage strategy?

  The problem has been resolved. Failed ISO image was only visilble in Administration and media & other only. After it has been removed, we were able to delete the storage policy.

• Cannot access vCloud Director VM console

  Hello

  We´re in the face of a very strange problem when you try to access a console virtual machine via the vCloud Director 5.6 Web Portal.

  Let me describe the environment:

  1 - 2 vCloud Director cells;

  2. load balancer 1;

  3 - 1 VIP for the proxy console; 1 VIP for the web portal;

  4 - certificate of CA-signed 1 with wildcard characters (*. < domain >) instead of certificates 2 ordinary host (http. < domain > and consoleproxy. < domain >).

  5 - the following procedure was used to create the keystore of Java and to be able to import the certificate even twice (each time with a different alias):

  OpenSSL pkcs12 - in /keystore/ < company > .pfx-out /keystore/ < company > .pem

  OpenSSL pkcs12-export - in /keystore/ < company > .pem-inkey /keystore/ < company > .key-out _http.p12 /keystore/ < company > - name "http".

  OpenSSL pkcs12-export - in /keystore/ < company > .pem-inkey /keystore/ < company > .key-out _console.p12 /keystore/ < company > - name 'consoleproxy '.

  keytool - v - importkeystore - srckeystore /keystore/ < company > _console.p12 - srcstoretype PKCS12 - destkeystore /keystore/ < company > .ks - deststoretype JCEKS

  keytool - v - importkeystore - srckeystore /keystore/ < company > _http.p12 - srcstoretype PKCS12 - destkeystore /keystore/ < company > .ks - deststoretype JCEKS

  6 race "keytool-list - keystore /keystore/ < company > .ks - stores JCEKS" shows two aliases in the keystore.

  7 - vCD installer not to complaint about it.

  8 - certificate is loaded correctly when accessing the web portal

  Now the question:

  1 - the gate opens as it should;

  2. each type of action is possible and works very well;

  3. when we open a VM console for the first time, it opens normally;

  4. If we close it and try to reopen, or if we try to open a second console, it won´t open;

  5 - according to the browser:

  5.1 - console remains black. State begins to 'connection '. Changes to "Offline" after a short time;

  5.2 - console remains empty. Status hangs on "Loading"; He sometimes goes to "disconnected";

  6. If restart us the two cells, it begins around (able to open the first console, cannot open the rest);

  7. same behavior if the access using the VIP (with load balancing) or directly (using the internal IP address of cells).

  I ve seen some issues with what seemed like the same problem but no conclusive answer.

  Any help on this would be appreciated.

  Thank you very much.

  The fixed.

  1 - upgrade of vCD 5.6.3 to 5.6.4.

  2 - something with virtual machines, we had deployed for testing. We have erased their and the new have no behavior.

• vCloud Director page does not open.

  Hi all

  Today I faced a strange problem in my vcloud Director. all of a sudden all the URLs for org and admin home page of vcloud stopped.

  I tried to search in google and find a few KB, but they are not useful. As below.

  VMware KB: Access to the URL of the organization fails with the browser error: error 404 not found
  
  I have tried different browsers and restarted my vcloud server but nothing helped. Any help or idea please.

  Thank you

  vCloud newspapers are not specific to the problem. I checked and found the watchdog .log and found that the server is not the storage space. in any case, I'd drive and his works fine and went smoothly. .

  Thanks for your help. Have a nice day everyone.

• vCloud Director 5.5.1 can prepare the host

  Hello!
  My environment: vCloud Director 5.5.1.1654672

  ESXi 5.1.0 1065491

  vCenter 5.5.0 1623101

  
  I want to prepare a new host in our vCloud cluster, but I only had errors:

  "host cannot be prepaired":

  com.vmware.ssdc.util.LMException: com.vmware.ssdc.library.vim.SvcConnectionException:

  com.vmware.ssdc.util.LMException: com.vmware.ssdc.library.vim.SvcConnectionException:

  com.vmware.ssdc.library.vim.SvcConnectionException:

  com.vmware.ssdc.library.vim.SvcConnectionException

  all with the error "unable to connect to vcenter Server.

  org.apache.http.conn.HttpHostConnectException: connection to https://vcloudserver refused

  -Connection to https://vcloudserver refused

  -Connection has expired

  I checked the dns resolution (all directions, network connectivity (ping, telnet,...), vshield status etc...)

  I found the Thread problem preparing hosts , but is not a solution for me.

  Anyone have any idea?

  THX

  BR

  I solved my problem - it was a firewall issue.

  vCloud Director coud not connect to the esxi host because ports were blocked.

• vSphere 5.5 hosts appear under "Hosts" in vCloud Director

  Hi guys.

  I had a problem with my cell of vCloud Director and re-installed completely.

  On the vCD fresh installation I have no problem adding vCenter 5.5 but no host show at all.

  I tried to remove and re - install agents on host computers, vCD reset my vCenter inventory 5.5 database, restart the hosts, but nothing is.

  Any thoughts on this topic?

  Thank you

  Campellos

  Attach a vCenter is not enough, you must create a provider vDC then.  It is the association of a cluster for the vCloud instance.  Once this is done, guests who are part of the cluster should appear in the list of guests to prepare.

  Clusters must be active DRS.  Do not disable DRS on a cluster, it is attached to vCloud Director.