System Intialization
Page 92 7210 SAS M, X Basic System Configuration Guide
 System Intialization
When the system is powered ON it executes the bootstrap image, for example, the boot.tim file, 
from the file system which is located on a non-removable flash device (cf1:) that is built in to the 
7210 SAS-Series router. The boot.tim file is the image that reads and executes the system 
initialization commands configured in the Boot Option File (BOF). The default behavior is to 
initially search for the boot.tim file on cf1:. This behavior cannot be modified. If the boot.tim file 
is not present, or is not a valid loadable file, the Golden bootstrap image is loaded by the bootrom. 
This image is equivalent to a boot.tim file except that it is present outside the file system and can 
be updated and checked by means of special CLI commands.
When the system executes boot.tim, provision is given to the user to modify the BOF 
manually and save it or to boot using existing BOF. The bootstrap image then processes the BOF 
file present in the flash as explained in Configuration and Image Loading on page 97. The system 
is shipped to the customer site with a boot.tim file and a Golden bootstrap image, but without a 
BOF file. When the system is powered ON for the first time, there will be no BOF in the system. 
Hence, provisions are given to create a new BOF file or alternatively get the BOF file from the 
network. There are two options:
• Boot by manually creating a BOF file (manual boot).
• Boot by retrieving the BOF file from the network, using DHCP to get the network location 
of the BOF file (auto init). Auto-init is the default boot procedure if there is no manual-
intervention during the first boot. 
Note: When the operator executes the reset command in the boot loader prompt or admin 
reboot auto-init
 in the TiMos CLI, 7210 SAS resets the current BOF and reboots.
Note: The operator can manage a 7210 SAS node through an external physical network. 
Managing a node through an external physical network secures the management network 
by restricting access to service customers and service data. The 7210 SAS node can be 
managed through the Out-of-band (OOB) Ethernet management port. 
The following is an example of console display output when the 
boot.tim file is located on cf1 and 
the system boots successfully.
Alcatel-Lucent 7210 Boot ROM. Copyright 2000-2009 Alcatel-Lucent.
All rights reserved. All use is subject to applicable license agreements.
Running POST tests from ROM
Testing ROM load area...done
Relocating code...Jumping to RAM
Performing second stage RAM test....passed
Board Serial Number is 'SN123456789'
Bootlog started for Version V-0.0.I317
Build V-0.0.I317 bootrom/mpc 7xxx
Built on Tue Jan 6 02:23:14 IST 2009 by panosbld in /panosbld/ws/panos/main