After changing the network parameters, the device attempts to load the device's firmware
file (cmp) and various configuration files from the TFTP server’s IP address received from
the BootP/DHCP server. If a TFTP server’s IP address isn’t received, the device attempts
to load the cmp file and / or configuration files from a preconfigured TFTP server. Thus, the
device can obtain its network parameters from BootP or DHCP servers, and its software
and configuration files from a different TFTP server (preconfigured in the ini configuration
file).
If BootP/DHCP servers are not found or when the device is reset using the Web interface
or SNMP, it retains its network parameters and attempts to load the cmp file and / or
configuration files from a preconfigured TFTP server. If a preconfigured TFTP server
doesn’t exist, the device operates using the existing software and configuration files on its
flash memory.
Figure 32-1: BootP Request and DHCP Discovery upon Startup
Note: By default, the duration between BootP/DHCP requests sent by the device is
one second (configured by the BootPDelay ini file parameter). By default, the