420 V7122 GatewayUser GuideAPPENDIX D: T HE BOOT P/TFTPCONFIGURATION UTILITYThe BootP/TFTP utility enables you to easily configure and provision our boards and mediagateways. Similar to third-party BootP/TFTP utilities (which are also supported) but withadded functionality; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™NT/2000/XP. The BootP/TFTP utility enables remote reset of the device to trigger theinitialization procedure (BootP and TFTP). It contains BootP and TFTP utilities with specificadaptations to our requirements.When to Use the BootP/TFTPThe BootP/TFTP utility can be used with the device as an alternative means of initializing thegateways. Initialization provides a gateway with an IP address, subnet mask, and the defaultgateway IP address. The tool also loads default software, ini and other configuration files.BootP Tool can also be used to restore a gateway to its initial configuration, such as in thefollowing instances: The IP address of the gateway is not known. The Web browser has been inadvertently turned off. The Web browser password has been forgotten. The gateway has encountered a fault that cannot be recovered using the Web browser.The BootP is normally used to configure the device’s initial parameters. Once thisinformation has been provided, the BootP is no longer needed. All parameters arestored in non-volatile memory and used when the BootP is not accessible.An Overview of BootPBootP is a protocol defined in RFC 951 and RFC 1542 that enables an internet device todiscover its own IP address and the IP address of a BootP on the network, and to obtain thefiles from that utility that need to be loaded into the device to function.A device that uses BootP when it powers up broadcasts a BootRequest message on thenetwork. A BootP on the network receives this message and generates a BootReply. TheBootReply indicates the IP address that should be used by the device and specifies an IPaddress from which the unit may load configuration files using Trivial File Transfer Protocol(TFTP) described in RFC 906 and RFC 1350.
