No, that's not the problem we're having. (We *did* have that problem,
and just deleting the offending rule file no lnoger works in RHEL 6,
but we fixed it by creating
/etc/udev/rules.d/75-persistent-net-generator.rules as a symlink to
/dev/null). At this point, Linux is doing the right thing
Hello Will,
You will want to disable the auto-assigned mac addresses from ESX/ESXi.
Part of the requirement is to run a dhcp server on the management
node, at a minimum for the private management network.
With that when you add new computers you define your mac addresses
upfront in the add
Hello Mike,
I'm curious if the management node set to statically assign the public address.
Can you double check the settings for your management node? Select
Management node- Edit management Node Information and select Edit.
Near the bottom.
With this feature you can define how VCL handles the
Michael
Could you please check that 'eth0macaddress', 'privateIPAddress' and 'hostname'
(in VCL DB) matches 'hardware ethernet', 'fixed address' and 'host-name'
options in dhcpd.conf for the host? Also, /etc/hosts should have an entry
'privateIPAddress hostname' for captured computer.
Can
Hi Aaron.
Ah, sure enough, it is set to Static. Silly me, when I first set this
up I read that to mean don't try to set the public IP, leave it to us
humans to configure.
...Okay, so how would we get that behvior? We'll want our deployed VM's
to come up with predictable IP addresses so that
Hi Dmitri.
DHCP on the backnet works as expected. eth0 is being configured
correctly (gets the expected MAC address, which matches the one in
dhcpd.conf). /etc/hosts is correct for both the private IP and the
(intended) public-side IP.
The problem is that the config file for eth1 is being
Thanks Aaron.
Maybe this will be obvious when we get further into our testing, but how
do you provide access to deployed hosts where the DHCP-assigned
addresses are random? Are you using DynDNS?
On Tue, Jun 26, 2012 at 09:36:52AM -0400, Aaron Peeler wrote:
Set it to dynamic dhcp, this setting
Yes, in the vcl code during the post_load tasks of the OS modules.
There is a step to collect the network configuration of the loaded
node(vm or bare-metal), figure out the publicly assigned address and
then update the database which is then presented to the end-user.
Aaron
On Tue, Jun 26, 2012
