Owner's Manual

Bare Metal Provisioning 1.5 | 29
Reload with a DHCP Server offer without an FTOS image
If a switch that is configured to reload in DHCP-Client mode reaches a DHCP server
but does not locate a downloadable FTOS image file on the server, the FTOS image
stored in the local flash is loaded as follows:
1. The system boots up with the BMP application.
Entering Jumpstart app:
Initializing runtime directories
Reading Release Image at 0x40000 Part: A
2. The system receives a DHCP offer from a DHCP server with the following
parameters.
***** DHCP OFFER DETAILS *****
DHCP acquired IP = 20.0.0.77
subnet-mask = 255.255.255.0
DHCP provided Image file = NIL
DHCP provided Config file = customer.conf
DHCP Server IP = 20.0.0.1
TFTP Server IP = 20.0.0.1
DNS IP = 20.0.0.1
**********************************
3. One of the following actions is taken:
a The system does not receive an FTOS image name in the DHCP server
response and no image is downloaded from the file server. The following
message appears:
DHCP offer does not have Image file name
The system boots up with the image stored in the local flash and applies the startup
configuration file in the flash.
b The system receives an FTOS image name in the DHCP server response and
downloads the customer.conf configuration file from the file-server address
if you did not enter the honor startup-config option with the reload
factory-default dhcp-client-mode command:
dhcp.conf
tftping dhcp.conf ...
tftp> Received 119 bytes in 0.0 seconds
tftp success
Re-try count: 1
SUCCEED
customer.conf downloaded
4. If the local startup-configuration was applied, manually configure the
management IP address using the interface managementethernet
command.
Note: The IP address assigned by the DHCP server is released at the end of the
system reload. The switch attempts to reach the file server four times before sending
an error message and proceeding to the next step.