Nokia 7210 Sas-sx Manual

[Shawnna Franz]

Whenthe 7210 SAS device is powered on, the system executes the boot.tim file (also known as the boot loader or the bootstrap image) from the file system located on one of the storage media available on the 7210 SAS platform. The boot.tim file is the image that reads and executes the system initialization commands configured in the Boot Option File (BOF).

When the system executes the boot.tim file, the bootstrap image searches for and processes the BOF. The user has the option to modify the BOF manually and save it (see Manual Mode for more information), or to retrieve the BOF from the network (see Auto-init Mode for more information).

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.

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.

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.

The location of the boot.tim bootstrap image varies per 7210 SAS platform and depends on the storage locations supported by the platform. The boot option modes to find and load the boot.tim bootstrap image file also vary per 7210 SAS platform.

The use of a boot.tim file on a USB storage for booting up is not supported on the 7210 SAS-M. The boot.tim is present in cf1:\, or the golden bootstrap image in cf1:\ is used. The 7210 SAS-M supports the use of only a both.tim (TiMOS image) file on the USB storage device.

These platforms support the use of the external SD card slot or external compact flash (cf2:\) to boot the system. Use the storage media supplied with the purchase of a valid satellite mode license. After you insert the storage media in the external storage media slot, ensure that the satellite is connected to the host before you power on the system.

When operating the 7210 SAS platform in satellite mode, Nokia recommends to use only the auto-init procedure to retrieve the BOF and other boot parameters from the host. Other procedures, such as the manual configuration of the BOF, are not allowed. See Auto-init Mode for more information.

The bootstrap image processes the initialization parameters from the BOF and attempts to locate the configuration file configured in the BOF. Up to three locations can be configured for the system to search for the configuration file. The locations can be local or remote. The first location searched is the primary configuration location. If not found, the secondary configuration location is searched, and lastly, the tertiary configuration location is searched.

This section describes the booting sequence of the 7210 SAS platforms when they are powered on, and how they obtain the TiMOS image file, the BOF, the configuration file loads, the image, and the configuration file to bring up the platform.

On the 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE and 7210 SAS-Mxp, the operator can configure the chassis-role and host-type boot parameters to operate the 7210 SAS node in standalone mode or satellite mode. The values configured for these parameters must be consistent for boot up to proceed correctly. Table 22 describes the boot loader action when the chassis-role and host-type parameters are set to one of the allowed values.

Optionally, the BOF persist parameter can specify whether the system should preserve system indexes when a save command is executed. During a subsequent boot, the index file is read along with the configuration file. As a result, a number of system indexes are preserved between reboots, including the interface index. If persistence is not required and the configuration file is successfully processed, the system becomes operational. If persistence is required, a matching x.ndx file must be located and successfully processed before the system can become operational. Matching files (configuration and index files) must have the same filename prefix such as test123.cfg and test123.ndx, and are created at the same time when a save command is executed. The persistence option must be enabled to deploy the Network Management System (NMS). The default is off.

The 7210 SAS platforms support the OOB Ethernet management port for management of the node. An OOB Ethernet port can be used to download the TiMOS image file and the configuration file by creating a BOF manually. The OOB management port allows for use of both IPv4 and IPv6. See IPv6 Configuration Guidelines in OOB Node Management for information about platforms that support IPv6 for the OOB management port.

The 7210 SAS OS supports disabling the console port and OOB Ethernet management port. In remote deployments, operators can choose to disable user access to the node through the console and through the Ethernet management port to prevent unauthorized and malicious access. Use the bof>console-disabled command to disable the console and the bof>eth-mgmt-disabled command to disable the use of the Ethernet management port.

Access to a console is only disabled when the TiMOS image is loaded. Console access remains unchanged during the boot loader stage of the boot up process. That is, the bof command takes effect only when the node is booted with the TiMOS image.

3a8082e126