Blowfelt82
asked on
Configure nested ESXi host virtual machines DHCP configuration.
I have a nested ESXi environment which can be illustrated (very roughly) as:
[Server 1 - Remote Workstation]
Physical ESXi Host Server
Nested ESXi Host Server
Virtual Machine
Alongside this I have another virtual machine running a domain controller in VMWare Workstation where I have configured a DHCP server. The virtual Domain Controller can ping all of the addresses of the components listed above as can the development machine itself.
[Server 2 - Development Machine]
Virtual Domain Controller
I have assigned the virtual machine a E1000 network adapter type and configured a fixed MAC address for it. Currently when I start the virtual machine I get the error message 'PXE-E51: No DHCP or proxyDHCP offers were received'. I believe this is because the virtual machine cannot find the domain controllers DHCP server across the network (guess).
Within VMWare Virtual Network editor I have bridged the NICs between the development and remote workstations to enable the required connectivity between the components - but as a result of doing this configuring DHCP becomes disabled so I cannot configure this to use the DHCP server on my virtual domain controller. So what I am wondering is how I can force the virtual machine/esxi host/... to use the DHCP server running on my development machine. Assuming this is the problem...
Has anyone out there done something similar in the past? Any help appreciated as I am out of ideas!
[Server 1 - Remote Workstation]
Physical ESXi Host Server
Nested ESXi Host Server
Virtual Machine
Alongside this I have another virtual machine running a domain controller in VMWare Workstation where I have configured a DHCP server. The virtual Domain Controller can ping all of the addresses of the components listed above as can the development machine itself.
[Server 2 - Development Machine]
Virtual Domain Controller
I have assigned the virtual machine a E1000 network adapter type and configured a fixed MAC address for it. Currently when I start the virtual machine I get the error message 'PXE-E51: No DHCP or proxyDHCP offers were received'. I believe this is because the virtual machine cannot find the domain controllers DHCP server across the network (guess).
Within VMWare Virtual Network editor I have bridged the NICs between the development and remote workstations to enable the required connectivity between the components - but as a result of doing this configuring DHCP becomes disabled so I cannot configure this to use the DHCP server on my virtual domain controller. So what I am wondering is how I can force the virtual machine/esxi host/... to use the DHCP server running on my development machine. Assuming this is the problem...
Has anyone out there done something similar in the past? Any help appreciated as I am out of ideas!
ASKER
Yes the error occurs on startup, I have only only configured one vNIC (E1000) so after that I get an 'operating system not found'. I am trying to install ESXi via a PXEBoot so this wouldnt end up booting Windows but doesnt get this far anyway. As far as initial testing I will be happy if starting the VM takes out a DHCP lease on the domain controller...
The nested setup is a result of not enough physical kit to test on, I am working on the install, configuration and import of multiple ESXi servers into a vCenter inventory. Nested ESXi servers allow me to run multiple servers for initial testing without all the extra kit. This is a design decision above my head though and I am sure there are other reasons.
Is the subnet mask on the NICs what you need to know? They are different: 255.255.255.0/255.255.252.
The nested setup is a result of not enough physical kit to test on, I am working on the install, configuration and import of multiple ESXi servers into a vCenter inventory. Nested ESXi servers allow me to run multiple servers for initial testing without all the extra kit. This is a design decision above my head though and I am sure there are other reasons.
Is the subnet mask on the NICs what you need to know? They are different: 255.255.255.0/255.255.252.
If they are on seperate subnets the DHCP packets will need to be relayed. if your physical switch supports ip-helper that is an option, otherwise i would put a dhcp server nic and the client on the same network subnet.
When nesting ESXi in ESXi, did you make sure that you used
on the HOST networking for the VMs.
1. E1000 interface.
2. also used the VLAN 4095 (ALL)
You may also want to refer to my EE Article and AutoLab.
HOW TO: Set up a lab environment for vSAN using VMware Workstation
(I know it states Workstation, the article contains links to AutoLab for ESXI!)
on the HOST networking for the VMs.
1. E1000 interface.
2. also used the VLAN 4095 (ALL)
You may also want to refer to my EE Article and AutoLab.
HOW TO: Set up a lab environment for vSAN using VMware Workstation
(I know it states Workstation, the article contains links to AutoLab for ESXI!)
ASKER
I have configured the VM with one vNIC which uses the E1000 adapter type, when I start up the VM it does attempt to obtain a DHCP address but fails so I assume the VM is configured as it should be and the problem lies elsewhere - is this what you mean or should something be configured on the physical/nested ESXi servers? AutoLab looks interesting I will have a look tomorrow...
Blowfelt82, are they on the same network?
Like, are they both connected to the same switch, with the server bridged and the workstation bridged to that switch? or are they on the same vswitch?
Like, are they both connected to the same switch, with the server bridged and the workstation bridged to that switch? or are they on the same vswitch?
ASKER
The server and workstation are on a bridged network...
did you check VLAN 4095 (ALL)
ASKER
I have assigned a network connection TEST-LAN to my VM with an adapter type on E1000, then on the host network properties I have edited the TEST-LAN properties to use VLAN ID 4095. I have also enabled promiscuous mode, mac address changes and forged transmits... Unfortunately still no luck...
Sorry for the late reply, my development environment got messed up last night! Any other ideas?
Sorry for the late reply, my development environment got messed up last night! Any other ideas?
ASKER
The error has progressed to 'PXE-E53: No boot filename received'. I have configured a boot filename using the correct MAC address format in the WDS boot images repository - however even though the error message does not refer to DHCP I am not seeing a DHCP lease being made in the DHCP console.
are DHCP params, set correctly.
ASKER
Very new to DHCP but I think so...
I have setup a DHCP scope with a range of addresses on the same subnet as the ESXi host and given the DHCP scope the 060 PXEClient option... is that what you had in mind?
I have setup a DHCP scope with a range of addresses on the same subnet as the ESXi host and given the DHCP scope the 060 PXEClient option... is that what you had in mind?
what are you deploying?
we use 66 and 67.
we use 66 and 67.
Yeah you need option 67 set to a filename.
Are you using wds?http://m.windowsitpro.com/networking/configuring-dhcp-and-wds
Are you using wds?http://m.windowsitpro.com/networking/configuring-dhcp-and-wds
ASKER
Voila, I am getting somewhere a DHCP lease has been registered but now I get the error:
PXE-T04: Illegal operation error
PXE-E36: Error received from TFTP server
PXE-M0F: Exiting Intel PXE ROM
Andrew the points are yours, but if you care to shed any light on this feel free! I seem to be hitting every error possible along the way...
PXE-T04: Illegal operation error
PXE-E36: Error received from TFTP server
PXE-M0F: Exiting Intel PXE ROM
Andrew the points are yours, but if you care to shed any light on this feel free! I seem to be hitting every error possible along the way...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Problem solved, values in the scope options were wrong. Thanks for all your time on this you have been a lifesaver - really appreciate it.
Is Server 2 on the same network subnet as Server 1?
Also, why the nested set up?