Note! Booting with TFTP should ONLY be used in a development environment.
We strongly discourage use of this boot method in deployment because of the load on the TFTP server.
TFTP, or Trivial File Transfer Protocol, provides a quick alternative to booting your IP-STB from an Infocast Server. A DHCP server is required, which sends our information to the IP-STBs. The IP-STB receives this information, connects to the TFTP server, and downloads the specified file and then boots using it. In contrast to Infocast, which can handle a practically unlimited number of booting STB's, the TFTP server experiences a load for each booting box, and is therefore not suitable outside of a lab environment.
Example: /tftpboot/
To enable IP-STB:s to boot through TFTP you need to send some parameters, namely the TFTP server address, the file to download, and the kernel-protocol which tells the IP-STB to use TFTP boot instead of Infocast or Flash memory. Update the DHCP configuration as follows. See DHCP options for further reference on the settings.
# 19xx series of boxes
group {
next-server 192.168.1.73; # TFTP server
option Kreatel.kernel-protocol "2"; # Use TFTP
option Kreatel.tftp-blocksize 25000; # Improve loading speed
option Kreatel.tftp-kernel-filename "/boot-1900.bin"; # file path and name (relative to TFTP server root)
host 1910 {
hardware ethernet 00:02:9B:42:62:21;
fixed-address 192.168.5.78;
}
}
Remember to restart DHCP server.Example: service dhcpd restart
Copy your bootimage to the TFTP directory. Example: cp bootimage.bin /tftpboot/boot-1900
Power on you IP-STB and you should have it load the bootimage through TFTP.
If your IP-STB is not booting as expected, you can check the following things: