I have an Auto Deploy server with two network adapters and had the problem that the configured ePXE Boot URL on the auto deploy server was different to the one that the ePXE boot server received.
Nic1 has the IP X.X.237.9 and communicates to the ESX hosts
Nic2 has the IP X.X.133.112 and communicates to the vCenter server only
ePXE boot server should receive files from Nic1 but for some reason it has the ip from Nic2
Well after some investigation I found the problem but not the root cause.
If you download and unzip the tftp packet from the auto deploy page in vshpere client you’ll find also a file called tramp. Open it with an editor of your choice
Its content should look like this 😉 Yep the IP of Nic2 was written in the tramp file.
#!gpxe set filename https://xxx.xxx.133.112:6501/vmw/rbd/tramp chain https://xxx.xxx.133.112:6501/vmw/rbd/tramp
Well, I have no idea why and honestly I don’t care but what I know is since I corrected the IP the ePXE boot server received the correct IP and could continue with auto deployment.
#!gpxe set filename https://xxx.xxx.237.9:6501/vmw/rbd/tramp chain https://xxx.xxx.237.9:6501/vmw/rbd/tramp
I’m using vSphere 5.0
Rafael Camison's Notes 