Post

2 followers Follow
0
Avatar

Bypass address range requirement

Is it possible to bypass the requirement of having an address range on a virtual network?

I am using VMware OS customizations to configure VMs after deployment by vOneCloud, but VMware tools is identifying the VMware generated MAC address before vOneCloud changes it to the MAC address specified in the virtual network address range. This is causing the customization to fail because the NIC with the VMware tools identified MAC address no longer exists. I am also using an external DHCP server for IP addresses. What I would like to do is use vOneCloud for the interface and provisioning of VMs, but allow vCenter to manage the MAC addresses and the DHCP server to manage the IP addresses. As far as I can tell, there is no way in the UI to disable address ranges completely. I am hoping there is some other way to remove them.

I am using vOneCloud version 3.4.1

Ryan Collins

Please sign in to leave a comment.

2 comments

0
Avatar

but VMware tools is identifying the VMware generated MAC address before vOneCloud changes it to the MAC address specified in the virtual network address range

vOneCloud performs the change of the MAC address before the VM is poweron. Hence, the VMware tools should never see other MAC address other than the one assigned by vOneCloud.

Can you detail the workflow on your VM so we can try and reproduce the problem and evaluate a workaround?

 

vOneCloud Support Team 0 votes
Comment actions Permalink
0
Avatar

I am guessing VMware tools is identifying the originally generated MAC address through a cache in vCenter.

The VMs I have tested with this issue are all Linux VMs (tried with both VMware tools and open-vm-tools) using guest OS customizations through vCenter. The guest customization is used to set the hostname (to match the VM display name), the timezone, and to set the NIC to DHCP. When I deploy them, the VM is cloned from the template successfully and then the MAC address is changed and it is powered on. During the guest customization step, I see an error in the VM event log in vCenter about the customization failing. It references a log file stored in /var/log/vmware-imc/ for more info. In that log, I see references to the original, vCenter supplied MAC address. It appears to be looking for a NIC with that MAC address and when it can't find it, the customization fails.

Ryan Collins 0 votes
Comment actions Permalink