7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Boot options
Note:
DHCP uses the values specified in the partial BOF to retrieve the complete BOF from the
network. If you configure the preceding parameters in the partial BOF, Nokia recommends using
the same values for the locally modified BOF as in the BOF downloaded from the network.
To update the preceding BOF parameters, use console access and break the boot sequence. Then, enter
the auto keyword and follow the prompts to update the BOF parameters. Enter exit when you are done.
The boot loader software uses these parameters to configure the link appropriately and sends out the
DHCP requests to obtain the BOF. The BOF obtained through DHCP must contain the location of the
image file and configuration file (and values for other BOF parameters). If the DHCP process is successful,
the BOF obtained from the network is copied to the local flash.
Caution:
The parameter values in the BOF downloaded from the network must match those configured
in the partial BOF. If there is a mismatch between the values retrieved from the network (that is,
the network BOF is not configured to match the new values) and the user-configured values in
the partial BOF, the next reboot of the system will fail. For example, specifying different auto-
negotiate values in the two BOFs may cause the system to fail to bring up the link, which will
cause the auto-init procedure and subsequent reboots to fail.
A mismatch may also cause the system to require twice the number of network resources. For
example, the use of different VLAN ID values causes the system to require twice the number of
resources for two services (one for each VLAN ID).
See Figure 5: System initialization: bootstrap process overview for more information about the
bootstrap process and system initialization.
The system first attempts to use uplinkA and then uplinkB parameters to receive a successful response
from the DHCP server. If there is no response on both uplink ports, the boot procedure is restarted,
during which the user can choose to enter the manual mode or allow the system to default to the auto-init
procedure again.
If the image fails to download through the auto-init process, the system loads the TiMOS image by using
the both.tim file located on the local flash (that is, cf1:\both.tim and cf1:\*TIMOS*\both.tim).
After the TiMOS image is loaded and bootup is successful, the user can choose to continue using the
same image by entering the admin>auto-init stop command within a fixed amount of time, as prompted.
Running the admin>auto-init stop command creates a BOF and saves it on the local flash, with the image
location pointing to the image on the flash. If the user does not run this command when prompted, the
system reboots again and attempts to find an image through the auto-init process (that is, by sending
DHCP requests).
4.1.2.1.1 Ping check in auto-init mode
After successful bootup using the Auto-init mode procedure, the software initiates a ping check to ensure
that the system has IP connectivity. The software loads the configuration file and attempts to ping the
destination node three times using the IP address specified in the ping-address BOF parameter. If the
ping check does not succeed, the system is rebooted with the BOF reset after 1 minute and the boot
process is repeated. If the address in the BOF is zero or the ping address is not specified, the ping check is
not performed.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
124
SPACER TEXT
To Next Page
Loading...