This article is to update the TRAMP file generated by vSphere Auto Deploy 5.x when use with vCenter Server Heartbeat in a WAN deployment.
The TRAMP file, by default, is generated from the IP address of the Auto Deploy server when it is installed. When using vCenter Server Heartbeat in a WAN deployment to protect your Auto Deploy Server, this will not function correctly as they will not have a Public IP that can be utilized.
To work around this issue, perform the following:
- Connect to the vCenter Server via its Public IP address using the vSphere Client.
- Click on Home .
- Under Administration , select Auto Deploy .
- Under the Actions section, click Download TFTP Boot Zip . Save this to your local system.
- Extract the files contained in the deploy-tftp.zip that was downloaded in Step 4. This will contain eight (8) files.
- Open the tramp file in a plain text editor.
Change the following:
set filename https://<IP Address of Auto Deploy Server Node>:6501/vmw/rbd/tramp
chain https://<IP Address of Auto Deploy Server Node>:6501/vmw/rbd/tramp
set filename https://<Public Name of Auto Deploy>:6501/vmw/rbd/tramp
chain https://<Public Name of Auto Deploy Server Node>:6501/vmw/rbd/tramp
- Save this file and close.
- Log into the TFTP server configured for use with the Auto Deploy setup.
Open the directory which TFTP stores the Auto Deploy files
If using SolarWinds, this is by default: c:\TFTP-Root
If using TFTP-Server on Linux, this is by default: var/lib/tftpboot
- Back up the current Auto Deploy files. Do not skip this step.
- Replace the existing files with the new bundle including the modified tramp file.
- Restart the TFTP service.
After these modification, the PXE booting hosts should now be directed to the Public Name of the Auto Deploy protected by vCenter Server Heartbeat during the boot and should be success."
VMware vCenter Server Heartbeat, all versions