tsugliani's Accepted Solutions

Did you setup the API URL correctly in your system settings ? https://docs.vmware.com/en/vCloud-Director/9.0/vcd_90_admin_guide.pdf  (page 170)
You should be able to use Storage vMotion directly *BUT* there are some *gotchas* you need to be aware of : 1) You *need* to storage vMotion the VM to a datastore present into your PvDC 2) I... See more...
You should be able to use Storage vMotion directly *BUT* there are some *gotchas* you need to be aware of : 1) You *need* to storage vMotion the VM to a datastore present into your PvDC 2) If you are using Fast Provisionning (Linked Clones) the Storage vMotion, will not keep it as the source format, and *WILL* consolidate the VM. If you want to keep the disk format, use the vCloud API and the *relocate* api call (it will take care of everything needed to keep it as a linked clone). Note : I'm talking about 1.5.x, as you have SDRS & Storage profiles in 5.1, you can manage differently with SDRS Maintenance mode> Hope this helps,
Yes, this is possible and not only related to ESXi. You can add your fenced vApp to the catalog, and take notice of the option "[x] Make identical copy". This will preserve all the VMs setting... See more...
Yes, this is possible and not only related to ESXi. You can add your fenced vApp to the catalog, and take notice of the option "[x] Make identical copy". This will preserve all the VMs settings perfectly. Of course if you try to do this without fencing, the second vApp you will deploy will never start because you will have 2 same mac addr on the same L2 network which would break everything. Hope this helps.
Option 4 It should be URL for "VCD Public": https://10.2.10.166/cloud/ Proxy-Address der VCD-Public-Konsole: 10.2.10.167 Basis-URL for VCD Public REST API: https://10.2.10.166/ ... See more...
Option 4 It should be URL for "VCD Public": https://10.2.10.166/cloud/ Proxy-Address der VCD-Public-Konsole: 10.2.10.167 Basis-URL for VCD Public REST API: https://10.2.10.166/ To explain a bit further, the "HTTP" nic that you probably configured on eth0 will provide the vCloud Director Portal, and will also handle the API traffic. The second nic will be used for the "Console Proxy" which is the remote console (VMRC) Hope it helps. PS: On the other side this is a known bug with every Firefox version > 12 it seems. (You need at the moment to open the remote console in fullscreen to be able to see the console.
It should work, here is an example screenshot that shows sample configurations. I've just tested with range and CIDR notation. What kind of message are you getting ?
Hi, That's why it doesn't work, you need to fill up the API box too (The api will always answer with it's internal http nic setting otherwise, and the upload process goes through the API) ... See more...
Hi, That's why it doesn't work, you need to fill up the API box too (The api will always answer with it's internal http nic setting otherwise, and the upload process goes through the API) Please try and confirm it works. Regards,
Hi, From the error message could you check that all your hosts are correctly enabled in vCD ? vCloud Admin -> Manage & Monitor -> vSphere Resources -> Hosts if not, be sure to enable eac... See more...
Hi, From the error message could you check that all your hosts are correctly enabled in vCD ? vCloud Admin -> Manage & Monitor -> vSphere Resources -> Hosts if not, be sure to enable each host, this permits you to use the "host spanning" capability for your Network Pools. (your underlying vSphere Cluster) Regards,
I think the easiest and proper way would be to leave the "console" alone, and just SSH to the vima appliance You won't have the vga "physical default console" limitation, and it will b... See more...
I think the easiest and proper way would be to leave the "console" alone, and just SSH to the vima appliance You won't have the vga "physical default console" limitation, and it will be much faster.
Did you change your portgroup hosting ESX 4.0 in promiscious mode ? If not, that should be the issue.
Check vimsh configuration guide (it's an unofficial command but available on every ESX server) Xtravirt wrote a nice guide about it, and you will be able to switch active/standby configuration... See more...
Check vimsh configuration guide (it's an unofficial command but available on every ESX server) Xtravirt wrote a nice guide about it, and you will be able to switch active/standby configuration on your vSwitch using it. http://www.xtravirt.com/index.php?option=com_remository&Itemid=75&func=fileinfo&id=6
Use << \EOF1 this will save your $ variables.