Hi,
Please try it buy removing the nic from template/catalog VM. I tried this way and it worked.
Vivek
Hi,
Please try it buy removing the nic from template/catalog VM. I tried this way and it worked.
Vivek
Muhammad,
Any kind of changes made in your environment recently? Any upgrade on vCD etc from v 5.x/6/x to 8.X?
Or better disable this alarm
We used to get this alert all the time, but we always ignored this. This issues started with vCD v6 and when we enquired from Engineering team about this, they told this is not vCD issue. vSphere is detecting the cloned VM mac address as duplicate.
As far as I know there's no way to change this default behaviour in VCD. For very large VMs, you could delete the vApp managing to keep the VM and import it back from vSphere, but it would be a procedure somewhat risky and prone to errors.
Double check that Catalog items (Template VMs, ISOs, FLP files) were moved on the new storage.
Hello,
I will have to update to 9.0.0.2 to solve a NOB (New Old Bug, bugs from elder versions of VCD that VMware's engineering magically manage to revive...), anybody here who already did the update and ahve encountered particular problems?
Thanks in advance, e.
Thank you. VMware support also confirmed that as long as everything was migrated and the old storage profile was disabled and later removed that the next steps were continue in vCenter Server. I was really just looking for clarification since the admin guide for older versions of vCloud had additional steps for removing the storage, that those steps were no longer needed. I was able to proceed with the removal without any issues.
Yeah catalog migration did not work as the documentation said that it should. I worked around the issue by creating a new catalog on the new storage and migrating the items from the old catalog to the new one.
This is normal if you are not doing full customization ... e.g. capture to Catalog and make an identical copy.
If you use any method of network isolation (any network from a network pool), then the MACs are isolated from one another (hopefully) and that should keep them from conflicting.
I would think about this from the inside via outside the VM package.
vCloud Director copies VMs using clones from the VMs in the catalog. So long as the VMs have the NICs at provisioning, there isn't much more that vCD does unless you go in and add/remove NICs.
vCenter > Edit Settings of the VM > Should show a consistent number of NICs to vCloud Director with corresponding MAC addresses. If this is correct, then vCenter and vCloud Director have done their job (for the most part).
Inside the Guest ... windows or linux ... the rest of the config happens.
With Linux, there is a lot of issues around persistence rules where NIC cards re-enumerate through templates ... Windows detects NICs as new and names them like network adapter 5/6/7.
I would start by breaking up the issue as much as possible.
Based on what you said ... it sounds like someone removed NICs in vCenter if they are absent there but present in vCloud Director.
Is it possible to deploy Advanced Gateway of the start (without going through Basic and the conversion to Advanced Gateway)? I've looked through API and couldn't find correct option:
Guys,
I create three Independent Disks and attach them to one VM in vCloud Director 8.2 like following:
Disk1 attach to VM with BusNumber=0 and UnitNumber=1
Disk2 attach to VM with BusNumber=0 and UnitNumber=2
Disk3 attach to VM with BusNumber=1 and UnitNumber=0
In VM (Redhat R7.4), there are 3 disks /dev/sdb, /dev/sdc and /dev/sdd for these Independent Disks,
How can I identify which disk (/dev/sd?) in VM mapping to which Independent Disks ?
e.g., how can I know what disk device (/dev/sd?) in VM is Independent Disk 2?
Thanks,
Rena
Hi Manish,
What you posted above is a Storage Profile(Policy) list of an org vdc which is no problem to get. But how does it help to find a href of an ISO mounted to the VM?
Hello
If you have several instances of vDirector in your cell is possible that one of them was not update correctly.
You may review using "cat /opt/vmware/vcloud-director/etc/global.properties | grep -i product.version"
Compare with other vCloud Director instances if all have the same version.
There is other possibility, your vcloud director has not updated correctly your schema. You could to restore the database and recover the snaphost.
Regards, Iván
I hope to help you
Hello all members,
I heard in VMWorld 2018 that vCloud Director team will not continue giving support to Oracle or MSSQL over vCloud Director.
I ask myself two question and I would like to share with your.
Thanks in advance
Regards, Iván
Hi,
Can I deploy vCells in different networks? Until now I've always deployed all vCells in the same network, so nic1 and 2 for web/proxy are in the public facing network, nic3 facing our internal networks. But now I would like to deploy one cell in public network A for nic1&2 and nic3 facing internal and a second cell in public network B for nic1&2 and then nic3 facing the same internal network as the other cell? Is this possible?
The database and vCenter will be accessible by both on the internal facing nic.
Gabrie
Afternoon all.
Can anyone provide any insight as to when we can expect to see VM console support in the new HTML5 Tenant UI?
Thanks
I do it the old VM way on my cloud.
$vms = Get-DatastoreCluster -Name superCluster | get-vm
foreach ($vm in $vms)
{
$vm.ExtensionData.ConsolidateVMDisks()
}