How to Boot Tabernus LAN/WAN in existing PXE Environment
Firstly, if the Tabernus LAN solution is being used in an existing PXE environment, you must disable the DHCP server, this will prevent the EELAN server from taking over all DHCP requests on the network.
To stop the server:
sudo service isc-dhcp-server stop
To disable the server from starting on boot:
echo manual | sudo tee -a /etc/init/isc-dhcp-server.override
Next, when starting the software for the first time, set the IP address to a static IP outside the range of your DHCP scope on your DHCP server. Set the netmask accordingly.
Once the DHCP server is stopped, we can now boot the client on the client machine, and point this towards the static IP of the server.
The client can be booted from a CD at this point, and should connect to your Tabernus server when you click Try to Connect on the client, and type in the static IP address.
Setting up 3rd Party PXE Booting
It is then possible, once you have tested the above on your network, to set up your existing PXE server/boot environment to boot the Tabernus Enterprise Erase LAN client
Since there are many different options for PXE network booting, we cannot offer full instructions for setting this up, but the broad concept is outlined below.
The pxeboot process that the Tabernus LAN client uses is the following:
TFTP boot lpxelinux.0 -> Load linux kernel and core.gz (via anonymous FTP) with specific kernel parameters -> Linux kernel boots, and Tabernus software starts.
The second step of this is what you must create an analog of in your current setup.
Assuming that your current PXE environment is entirely TFTP based it is possible to boot the kernel and core.gz via TFTP.
Open /var/lib/tftpboot/pxelinux.cfg:
DEFAULT core
TIMEOUT 3000
LABEL core
KERNEL ftp://192.168.0.1/vmlinuz
APPEND initrd=ftp://192.168.0.1/core.gz maxcpus=1 quiet waitusb=15 DELAY=10 IP=192.168.0.1
You will have to configure your PXE server to serve the same files (vmlinuz, core.gz can be found in /var/lib/ftpboot), and load the Linux Kernel and Initrd with the same kernel parameters (from the APPEND line)
If you have further questions, please do not hesitate to contact Tabernus support.