4. Boot options

This chapter provides information about configuring boot option parameters.

4.1. System initialization

When the 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).

Note:

Some 7210 SAS platforms (including 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE) do not ship with the bootstrap image. For these platforms, you must use one of the following devices to access the boot.tim file to boot the system. Insert the device containing the bootstrap image in the specified storage media location before powering on the system, as follows:

  1. external flash
    Insert the compact flash into the external compact flash slot.
  2. SD card
    Insert the SD card into the SD card slot.
  3. USB device
    Insert the USB storage device into the USB port.

Refer to the appropriate chassis installation guide for more information about the prerequisites for the specific 7210 SAS platform. See Contents of factory-shipped 7210 SAS systems for a list of contents shipped with the system on each 7210 SAS platform.

If the system cannot find the bootstrap image (boot.tim) in the default location (cf:\boot.tim), the system searches other storage locations (such as uf1:\) for the file and uses the boot.tim file in these locations to boot the system.

The following figure shows the typical flash directory structure and file names for a node shipped from the factory.

Figure 3:  Flash drive directory structure 

Files on the compact flash are:

  1. bof.cfg - boot option file
  2. boot.tim - bootstrap image
  3. config.cfg - default configuration file
  4. TIMOS-m.n.Yz:
    1. m - major release number
    2. n - minor release number
    3. Y - type of release
      1. A - alpha release
      2. B - beta release
      3. M - maintenance release
      4. R - released software
    4. z - version number
    5. both.tim - CPM and IOM image file

4.1.1. Contents of factory-shipped 7210 SAS systems

The following table lists the contents that are shipped with the system on each 7210 SAS platform.

Table 20:  Contents shipped with the system on 7210 SAS  

7210 SAS platforms

System contents

boot.tim File

Golden bootstrap image

BOF

TiMOS Image

cf1:\

cf2:\

7210 SAS-Mxp 1

✓

✓

✓

7210 SAS-R6 1

✓

✓

✓

7210 SAS-R12 1

✓

✓

✓

7210 SAS-S 1/10GE 2

✓

✓

✓

7210 SAS-Sx 1/10GE 2

✓

✓

✓

7210 SAS-Sx 10/100GE 2

✓

✓

✓

7210 SAS-T 1

✓

✓

✓

    Notes:

  1. No images are shipped on cf1:\. The user can purchase the software that is shipped with the boot.tim, starter BOF, and TiMOS image on cf2:\.
  2. No images are shipped on cf1:\. The user must purchase a software license to obtain an image on the SD card. The SD card can be inserted into the SD card slot on the chassis to boot up the node. The software is shipped with the boot.tim, starter BOF, and TiMOS image.

4.1.2. System boot option modes

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).

Depending on whether the node is factory-shipped with the BOF, the user can obtain and use the BOF as follows. See Table 20 for information about which platforms are factory-shipped with the BOF:

  1. On 7210 SAS nodes that are factory-shipped with the BOF, use one of the following manual mode options:
    1. boot the system in manual mode by using the starter BOF; the system uses the default both.tim, as configured in the default BOF
    2. boot the system by interrupting the default boot process and manually edit the contents of the BOF to create a new BOF
    Refer to the appropriate 7210 SAS chassis installation guide for more information about editing and creating a new BOF for the specific 7210 SAS platform.
  2. On 7210 SAS nodes that are factory-shipped without a BOF, the file is not present when the system is powered on for the first time. Use one of the following options to obtain a BOF for the system:
    1. boot the system by manually creating a BOF (manual mode)
    2. boot the system by retrieving the BOF from the network, using DHCP to retrieve the network location of the BOF (auto-init mode); auto-init mode is the default boot procedure if there is no manual intervention during the first boot of the node
    Refer to the appropriate chassis installation guide for more information about using the available system boot options for the specific 7210 SAS platform.
Note:

  1. If the operator executes the reset command in the boot loader prompt or the admin>reboot auto-init command in the TiMOS CLI, 7210 SAS resets the current BOF, reboots, and initiates auto-init mode after the reboot.
  2. 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.

4.1.2.1. Auto-init mode

Note:

Auto-init is supported on all 7210 SAS platforms as described in this document, except the 7210 SAS-R6, 7210 SAS-R12, and platforms operating in standalone-VC mode.

During the first boot or a reboot after the execution of the admin>reboot auto-init command, if the user does not intervene to create the BOF in the manual mode, the system, by default, runs the auto-init procedure after a wait time. The default wait time is 3 seconds. Two designated ports are used for auto-init: front panel port 1 and 2. Auto-init requires a DHCP server to be configured in the network and reachable by the system. DHCP requests are directed out of one uplink port at a time because all other ports in the system are down.

Note:

Some systems use other ports in addition to front panel port 1 and 2. See Configuration notes for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp for information about specific ports used to send DHCP request for 7210 SAS platforms.

If a DHCP server is present in the network, the system expects to receive an IP address, default gateway information, and a BOF location in the response returned by the DHCP server. Upon receiving these parameters from the DHCP server, the system applies the IP configuration and downloads the BOF from the location specified by the DHCP server. The BOF is saved in the flash drive and used for subsequent reboots. The bootstrap image processes the BOF parameters to boot the system. See Configuration file and TiMOS image loading for information about the BOF processing.

Before the node attempts to use DHCP to obtain the BOF and image files, you can configure the following link parameters in the BOF to suit your deployment needs:

  1. the uplink ports to use
  2. VLAN ID used
  3. link speed
  4. duplex setting for the link
  5. auto-negotiation capability for the link
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 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.

4.1.2.2. Manual mode

Manual mode has two options:

  1. Either use the starter BOF or configure the BOF to point to a local image to use the image files on the flash that are shipped with the node.
  2. Configure the BOF to retrieve the image files from the network.

If the user opts for the manual mode boot procedure using the network to retrieve the images and configuration for the first-time boot, the required parameters must be specified for a successful system boot. Manual mode configurations require authentication. The default password is password. BOF parameters that should be configured include the following:

  1. image path
  2. configuration file path
  3. uplinkA parameters (port number, VLAN ID, IP/mask, static route)
  4. uplinkB parameters (port number, VLAN ID, IP/mask, static route)
  5. eth-mgmt-disable
Note:

The following caveats apply for manual mode on 7210 SAS platforms.

  1. UplinkA and uplinkB parameters are only supported on the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE operating in standalone mode, 7210 SAS-Sx 10/100GE, and 7210 SAS-T.
  2. On the 7210 SAS-R6 and 7210 SAS-R12, the out-of-band (OOB) Ethernet management port can be used to retrieve the image and configuration file from the network.
  3. The auto-init mode is not supported on 7210 7210 SAS-Sx/S 1/10GE (standalone-VC), 7210 SAS-R6, and 7210 SAS-R12.

Provisions to configure two uplinks is supported in the BOF for port redundancy. If the image path and configuration file path are local, the IP address and routing information for uplinkA and uplinkB is not required. Optionally, the user can obtain IP parameters through DHCP by configuring 0 (zero) for the IP address of the uplink port. In this case, the DHCP server should be configured to grant the IP address and the default gateway information used to reach the server where the image and configuration files are located. After the BOF configuration is complete, a BOF with configured parameters is created in the flash that can be used for subsequent reboots. The bootstrap image then processes the BOF parameters to boot the system. See Configuration file and TiMOS image loading for information about BOF processing.

The eth-mgmt-disable parameter indicates whether the out-of-band Ethernet management port is enabled during the boot process. On a 7210 SAS node where a previous version of the BOF exists, the boot process uses the existing parameter values for uplinkA and uplinkB ports to boot the TIMOS image. The OOB port is disabled by default. The user has the option to enable the Ethernet management port and use it to boot the system.

4.1.3. BOF and configuration file encryption

In cases where the 7210 SAS platform is not installed in a physically secure location, the user can encrypt the BOF and the configuration file to halt or hinder interpretation of the contents of the file.

By default, the BOF and configuration file are not encrypted. When encryption is enabled for either file and a change is saved (using the admin save command), the original file is moved to filename.1 and the encrypted file becomes the new filename.cfg.

Caution:

When the original file is moved to filename.1, this file is unencrypted. To maintain node security, delete the unencrypted filename.1 file.

When the BOF is encrypted on the compact flash, the BOF parameters can be modified using the BOF interactive menu during node startup, and fields can be modified using this menu.

See Configuring BOF Encryption for information about configuring BOF encryption. See Configuring the BOF Interactive Menu Password for information about configuring the BOF interactive menu password. See Configuring the Configuration File Encryption for information about configuring configuration file encryption.

4.1.4. Bootstrap load process

The following figure shows the bootstrap load process.

See 7210 SAS boot options and procedures for more information about platform-specific supported boot options, and how the specific system processes these options and loads the bootstrap image file (boot.tim), the TiMOS image (both.tim) and the configuration file to make the system operational and ready for use.

Figure 4:  System initialization: bootstrap load process 

The following is a sample of console display when the boot.tim file is located on cf1:/ and the system boots successfully.

Nokia 7210 Boot ROM. Copyright 2016 Nokia.
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
 
?Attempting to load from file cf1:/boot.tim
Version L-0.0.I312, Fri Jan  2 04:26:32 IST 2009 by panosbld in /panosbld/ws/panos/
main
text:(3002475-->12623392) + data:(550940-->2414128)
Starting at 0xb000000...
 
 
Total Memory: 512MB  Chassis Type: sas  Card Type: badami_7210
TiMOS-L-0.0.I312 boot/mpc NOKIA SAS-Sx 7210 Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Fri Jan 2 04:26:32 IST 2016 by panosbld in /panosbld/ws/panos/main
 
TiMOS BOOT LOADER
 
...

4.1.5. 7210 SAS boot options and procedures

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.

This section provides information about the supported boot option modes and storage locations for 7210 SAS platforms.

4.1.5.1. System boot options on 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T

These 7210 SAS platforms support the following options to retrieve the boot.tim and TiMOS/SROS images (both.tim) required to boot the system:

  1. internal flash (cf1:\)
  2. external flash (cf2:\)
  3. external USB flash (uf1:\)
  4. network (with auto-init)
    This option is supported only on the 7210 SAS-T.
  5. network (without auto-init)

Because multiple storage locations are available for the bootstrap image boot.tim file on the 7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12, these platforms do not support the golden bootstrap image.

During bootup, the bootrom searches for the boot.tim in the following locations in the specified order and uses the image obtained from the first location where boot.tim is found to load the bootstrap image:

  1. cf1:\ (internal USB)
  2. cf2:\ (external flash)
  3. uf1:\ (external USB)

If the boot.tim is not found in any of these locations, the boot procedure fails. If the boot.tim image is found, the system searches for bof.cfg (the boot options file) on the same storage device in the root directory. For example, if boot.tim is found on cf2:\, the system also looks for bof.cfg in cf2:\bof.cfg.

If bof.cfg is found, the system uses the BOF to locate the TiMOS software (both.tim file), configuration file, and other boot parameters, and processes them to boot the system. If the BOF is not found, the system attempts to retrieve the BOF from the network using the auto-init mode and create a new BOF as part of the auto-init process.

In some cases, the BOF may specify different storage device locations for the TiMOS image (both.tim) and the configuration file. For example, the bootstrap image boot.tim file may be located on cf1:\, but both.tim and the configuration file may not be located on this device. You can use the show>system>information command to identify the location of the BOF and the boot.tim image used to boot the system.

The following is a sample output of system information for the 7210 SAS-T.

*...........
Boot-loader Source     : cf1:
BOF Source             : cf1:
Image Source           : primary
Config Source          : N/A
Last Booted Config File: N/A
Last Boot Cfg Version  : N/A
Last Boot Config Header: N/A
Last Boot Index Version: N/A
Last Boot Index Header : N/A
Last Saved Config      : N/A
Time Last Saved        : N/A
Changes Since Last Save: Yes
User Last Modified     : admin
Time Last Modified     : 2000/06/01 20:03:28
Max Cfg/BOF Backup Rev : 5
Cfg-OK Script          : N/A
Cfg-OK Script Status   : not used
Cfg-Fail Script        : N/A
Cfg-Fail Script Status : not used
*A:SAST>show>system#

See System boot option modes for more information about the auto-init and manual boot option modes, and how the system processes these options and loads the boot loader (boot.tim), the TiMOS image (both.tim), and the configuration file to make the system operational and ready for use.

4.1.5.2. System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE

Note:

See the Virtual chassis chapter for information about boot up and configuration of the 7210 SAS-Sx/S 1/10GE operating in standalone-VC mode.

These platforms can operate in the satellite mode or standalone mode, according to the following considerations:

  1. In the satellite mode of operation, these 7210 SAS platforms do not need an assigned IP address because they are managed by the 7750 SR host. The user must connect the correct ports to the 7750 SR host and power on the node. The node automatically fetches the BOF, the image, and the configuration required to operate in satellite mode.
    See System boot options for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE in satellite mode for a detailed procedure used to boot these 7210 SAS platforms.
  2. In the standalone mode of operation, these 7210 SAS platforms provide IP/MPLS functionality. The platforms need an assigned IP address and can be managed independently. See System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in standalone mode for procedures to boot these 7210 SAS platforms.

The operating mode that the 7210 SAS platform or node uses to boot up is determined by the chassis-role and host-type BOF parameters. Nokia recommends configuring similar values for both parameters to ensure that the node boots up in the correct mode. Failure to do so will result in an error and the node will not boot up. See BOF chassis-role and host-type parameters for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE for more information about BOF parameter settings to boot up the nodes in standalone mode and satellite mode.

Note:

  1. Nokia recommends using the external SD card slot (cf2:\) on the 7210 SAS-Sx/S 1/10GE and 7210 SAS-Sx 10/100GE or the external compact flash (cf2:\) on the 7210 SAS-Mxp to boot up the node the first time.
  2. To change the chassis role and the mode in which the platform will boot up, manually interrupt the boot process and use the BOF menu option to configure the chassis-role parameter value. You can also revert the parameter value to the factory default setting of factory-default.
  3. To boot up in standalone mode, it is not required to update the BOF to include the host-type parameter. To maintain backward compatibility, the node boots up in standalone mode if the chassis-role parameter is set to factory-default (the value set when it is shipped from the factory), and the host-type parameter is set to none.

The following sections describe the system initialization process for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in both standalone mode and satellite mode, and the role of the chassis-role and host-type BOF parameters:

  1. System boot options for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE in satellite mode
  2. System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in standalone mode
  3. Configuration notes for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp

4.1.5.3. System boot options for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE in satellite mode

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.

Table 21 lists the uplink ports used for 7210 SAS platforms and their variants. To boot up in satellite mode, the uplinks must be connected to the host ports, as described in Table 21.

Note:

The following notes apply to the host port information listed in Table 21:

  1. In satellite mode, you cannot configure the BOF parameters uplinkA and uplinkB ports for use with auto-init. For successful boot up in satellite mode, only use ports specified in Table 21 as uplinks to the 7750 SR host; use of other uplink ports is not supported. See Configuration notes for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp for information about ports used for first-time boot up with the chassis-role set to factory-default.
  2. On the 7210 SAS-Sx 10/100GE operating in satellite mode, you can establish a connection to the host with one 100 GE or 10 GE uplink. However, Nokia recommends that you use more than one uplink based on capacity requirements and to provide redundancy.
  3. On the 7210 SAS-Sx 10/100GE, by default, the DHCP requests are sent through ports 1/1/65 and 1/1/66, followed by 10GE ports 1/1/1 and 1/1/2. However, to use ports 1/1/1 and 1/1/2 as uplink ports in satellite mode, you must first appropriately configure the ports in the 7750 SR host machine.
  4. Refer to the 7210 SAS Software Release Notes 22.x.Rx, part number 3HE 18217 000x TQZZA, for information about the 7750 SR platforms and releases that support Ethernet satellites, and the version of 7210 SAS satellite mode software that is compatible with a specific version of SR OS software.
Table 21:  Uplink ports used for 7210 SAS platforms and variants in satellite mode 

Uplink ports used to connect to the host

7210 SAS platforms and variants

7210 SAS-Mxp

7210 SAS-Sx/S 1/10GE

7210 SAS-Sx 10/100GE

ETR

Non-ETR

22F 2C 4SFP+

24T 4SFP+

24Tp 4SFP+ PoE

46F 2C 4SFP+

48T 4SFP+

48Tp 4SFP+ PoE

64SFP+ 4CFP4

64SFP+ 4QSFP28

1/1/25 1

✓

✓

✓

✓

✓

1/1/26 1

✓

✓

✓

✓

✓

1/1/49 1

✓

✓

✓

1/1/50 1

✓

✓

✓

1/1/65 2

✓

1/1/66 2

✓

1/1/c1/1 2

✓

1/1/c2/1 2

✓

    Notes:

  1. 10GE uplink port
  2. 100GE uplink port

After the uplinks are connected and the node is powered up, the satellite node sends out DHCP packets. The host matches the MAC address in the DHCP packet against the host configuration to identify the satellite and provides the correct BOF to the satellite node for booting up. The BOF sets the host-type command to satellites and also provides the location of the TiMOS (SR OS) image and configuration file. The boot loader fetches the TiMOS image and configuration file and boots up in satellite mode.

Note:

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.

4.1.5.4. System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in standalone mode

Note:

See the Virtual chassis chapter for information about boot up and configuration of the 7210 SAS-Sx/S 1/10GE operating in standalone-VC mode.

When operating in standalone mode, these 7210 SAS platforms support the following options to boot the system:

  1. internal flash (cf1:\)
  2. external SD card slot (cf2:\)
  3. external USB flash (uf1:\) (not available for 7210 SAS-S 1/10GE)
  4. network (with auto-init; auto-init is not supported on platforms operating in standalone-VC mode)
  5. network (without auto-init)

Because multiple storage locations are available for the boot loader (boot.tim) on the 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE, these platforms do not support the golden bootstrap image.

During bootup, the bootrom searches for the boot.tim in the following locations in the specified order and uses the image obtained from the first location where boot.tim is found to load the bootstrap image:

  1. cf1:\ (internal USB)
  2. cf2:\ (external SD card slot)
  3. uf1:\ (external USB) (if available)

If the boot.tim is not found in any of the locations, the boot procedure fails. If the boot.tim is found in one of these locations, the system searches for bof.cfg (the boot option file) on the same storage device in the root directory. For example, if boot.tim is found on cf2:\, the system also looks for bof.cfg in cf2:\bof.cfg.

If the BOF is found, the system uses the BOF to locate the TiMOS software (both.tim file), configuration file and other boot parameters and processes them to boot the system. If the BOF is not found, the system attempts auto-init to retrieve the BOF from the network and create a new BOF as part of the auto-init process.

Note:

The following notes apply to 7210 SAS platforms configured in standalone mode:

  1. To perform a first-time bootup on a factory-shipped node, you are required to buy the software license and use the storage media (for example, SD card of compact flash) obtained to boot up the system. To boot up in standalone mode, it is not required to modify the BOF received during auto-init mode process to include the host-type parameter. To maintain backward compatibility, the node will boot up in standalone mode if the chassis-role parameter is set to factory-default (the value set when it is shipped from factory) and the host-type parameter is not set to any value (none).
  2. The auto-init procedure for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-1/10GE, and 7210 SAS-Sx 10/100GE remains unchanged and is the same as the other 7210 SAS platforms. Operators can continue to use the auto-init procedure that was used in previous releases. The ports used for first-time boot up when chassis-role is set to factory-default is described in section Configuration notes for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp.
  3. When operating in standalone mode, 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE support the option of either configuring the BOF manually (see section Manual mode for more information about the procedure used) or retrieving the BOF using autoinit (see section Auto-init mode for more information about the procedure used).

In some cases, the BOF may specify different storage device locations for the TiMOS image (both.tim) and the configuration file. For example, the boot.tim file may be located on cf1:\, but both.tim and the configuration file may be located on cf2:\. Use the show>system>information command to identify the location of the BOF and the boot.tim image used to boot the system.

The following is a sample output of system information for the 7210 SAS-Sx/S 1/10GE.

A:7210SAS>show>system# information
 
===============================================================================
System Information
===============================================================================
System Name            : hw_sass_duth
System Type            : 7210 SAS-Sx/S 1/10GE 48Tp4SFP+ (PoE)-1
System Version         : B-8.0.B1-238
System Contact         :
System Location        :
System Coordinates     :
System Up Time         : 0 days, 00:03:52.99 (hr:min:sec)
 
SNMP Port              : 161
SNMP Engine ID         : 0000197f0000a47b2cc669d3
SNMP Engine Boots      : 42
SNMP Max Message Size  : 1500
SNMP Admin State       : Enabled
SNMP Oper State        : Enabled
SNMP Index Boot Status : Not Persistent
SNMP Sync State        : N/A
 
Tel/Tel6/SSH/FTP Admin : Enabled/Disabled/Enabled/Disabled
Tel/Tel6/SSH/FTP Oper  : Up/Down/Up/Down
 
Boot-loader Source     : cf1:
BOF Source             : cf1:
Image Source           : primary
Config Source          : primary
Last Booted Config File: cf1:\bala_default_config.cfg
Last Boot Cfg Version  : THU JAN 13 01:53:35 2000 UTC
Last Boot Config Header: # TiMOS-B-8.0.B1-225 both/hops NOKIA SAS-Sx
                         48T4SFP+ 7210 Copyright (c) 2016 Nokia.
                          # All rights reserved. All use subject to
                         applicable license agreements. # Built on Thu Apr 14
                         21:25:57 IST 2016 by builder in /home/builder/8.0B1/
                         panos/main # Generated THU JAN 13 01:53:35 2016 UTC
Last Boot Index Version: N/A
Last Boot Index Header : # TiMOS-B-8.0.B1-225 both/hops NOKIA SAS-Sx
                         48T4SFP+ 7210 Copyright (c) 2016 Nokia.
                          # All rights reserved. All use subject to
                         applicable license agreements. # Built on Thu Apr 14
                         21:25:57 IST 2016 by builder in /home/builder/8.0B1/
                         panos/main # Generated THU JAN 13 01:53:35 2016 UTC
Last Saved Config      : N/A
Time Last Saved        : N/A
Changes Since Last Save: No
Max Cfg/BOF Backup Rev : 5
Cfg-OK Script          : N/A
Cfg-OK Script Status   : not used
Cfg-Fail Script        : N/A
Cfg-Fail Script Status : not used
 
Management IP Addr     : xx.xxx.xx.xx/24
Primary DNS Server     : N/A
Secondary DNS Server   : N/A
Tertiary DNS Server    : N/A
DNS Domain             : (Not Specified)
DNS Resolve Preference : ipv4-only
BOF Static Routes      :
  To                   Next Hop
  xx.xxx.x.x/16        xx.xxx.xx.x
 
  xxx.x.x.x/8          xx.xxx.xx.x
 
 
ICMP Vendor Enhancement: Disabled
===============================================================================
 
===============================================================================
System Oper Group Information
===============================================================================
Name                             Oper   Creation Hold   Hold   Members Monitor
                                 Status Origin   UpTime DnTime
                                                 (secs) (secs)
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
A:7210SAS-Sx>show>system#

The following is a sample output of system information for the 7210 SAS-Sx 10/100GE.

*A:7210SAS>show>system# information
 
===============================================================================
System Information
===============================================================================
System Name               : NS1633T0067
System Type               : 7210 SAS-Sx 64SFP+4CFP4-1
Chassis-role Config value : standalone
Host-type Config value    : standalone
Chassis Operating Mode    : standalone
System Version            : B-9.0.B1-246
System Contact         :
System Location        :
System Coordinates     :
System Up Time            : 16 days, 19:05:26.61 (hr:min:sec)
 
SNMP Port                 : 161
SNMP Engine ID            : 0000197f0000d099d58f5e41
SNMP Engine Boots         : 44
SNMP Max Message Size     : 1500
SNMP Admin State          : Disabled
SNMP Oper State           : Disabled
SNMP Index Boot Status    : Not Persistent
SNMP Sync State           : N/A
 
Tel/Tel6/SSH/FTP Admin    : Disabled/Disabled/Enabled/Disabled
Tel/Tel6/SSH/FTP Oper     : Down/Down/Up/Down
 
Boot-loader Source        : cf2:
BOF Source                : cf2:
Image Source              : primary
Config Source             : N/A
Last Booted Config File   : N/A
Last Boot Cfg Version     : N/A
Last Boot Config Header: N/A
Last Boot Index Version   : N/A
Last Boot Index Header : N/A
Last Saved Config         : N/A
Time Last Saved           : N/A
Changes Since Last Save   : Yes
User Last Modified        : admin
Time Last Modified        : 2000/01/13 22:19:03
Max Cfg/BOF Backup Rev    : 5
Cfg-OK Script             : N/A
Cfg-OK Script Status      : not used
Cfg-Fail Script           : N/A
Cfg-Fail Script Status    : not used
 
Management IP Addr        : xx.xxx.xx.xx/24
Primary DNS Server        : N/A
Secondary DNS Server      : N/A
Tertiary DNS Server       : N/A
DNS Domain                : (Not Specified)
DNS Resolve Preference    : ipv4-only
DNSSEC AD Validation      : False
DNSSEC Response Control   : drop
BOF Static Routes         :
  To                   Next Hop
  xx.xxx.x.x/16        xx.xxx.xx.x
 
  xxx.x.x.x/8          xx.xxx.xx.x
 
 
ICMP Vendor Enhancement   : Disabled
EFM OAM Grace Tx Enable   : False
===============================================================================
 
===============================================================================
System Oper Group Information
===============================================================================
Name                             Oper   Creation Hold   Hold   Members Monitor
                                 Status Origin   UpTime DnTime
                                                 (secs) (secs)
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:7210SAS>show>system#

The following is a sample output of system information for the 7210 SAS-Mxp.

*A:7210SAS>show>system# information
 
===============================================================================
System Information
===============================================================================
System Name            : SAS-M2
System Type            : 7210 SAS-Mxp 22F2C 4SFP+ ETR-1
System Version         : B-8.0.F40(16)
System Contact         :
System Location        :
System Coordinates     :
System Up Time         : 3 days, 13:26:45.91 (hr:min:sec)
 
SNMP Port              : 161
SNMP Engine ID         : 0000197f0000c4084a7ab86d
SNMP Engine Boots      : 11
SNMP Max Message Size  : 1500
SNMP Admin State       : Enabled
SNMP Oper State        : Enabled
SNMP Index Boot Status : Not Persistent
SNMP Sync State        : N/A
 
Tel/Tel6/SSH/FTP Admin : Enabled/Disabled/Enabled/Enabled
Tel/Tel6/SSH/FTP Oper  : Up/Down/Up/Up
 
BOF Source             : cf1:
Image Source           : primary
Config Source          : primary
Last Booted Config File: cf1:/default.cfg
Last Boot Cfg Version  : THU SEP 10 08:12:31 2015 UTC
Last Boot Config Header: N/A
Last Boot Index Version: N/A
Last Boot Index Header : N/A
Last Saved Config      : N/A
Time Last Saved        : N/A
Changes Since Last Save: Yes
User Last Modified     : admin
Time Last Modified     : 2015/09/19 01:37:49
Max Cfg/BOF Backup Rev : 5
Cfg-OK Script          : cf1:/env.cfg
Cfg-OK Script Status   : success
Cfg-Fail Script        : N/A
Cfg-Fail Script Status : not used
 
Management IP Addr     : 10.135.5.168/24
Primary DNS Server     : N/A
Secondary DNS Server   : N/A
Tertiary DNS Server    : N/A
DNS Domain             : (Not Specified)
DNS Resolve Preference : ipv4-only
BOF Static Routes      :
  To                   Next Hop
  135.0.0.0/8          10.135.5.1
 
 
ICMP Vendor Enhancement: Disabled
===============================================================================
 
===============================================================================
System Oper Group Information
===============================================================================
Name                             Oper   Creation Hold   Hold   Members Monitor
                                 Status Origin   UpTime DnTime
                                                 (secs) (secs)
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:7210SAS>show>system#

4.2. Configuration file and TiMOS image loading

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.

If the configuration file is in a remote location, the bootstrap process saves it on the flash as cf1:/default.cfg. Users must not delete this file or create a file with this name. The configuration file includes chassis, IOM, MDA, and port configurations, as well as system, routing, and service configurations.

Like the configuration file, three locations can be configured for the system to search for the files that contain the both.tim (SR OS/TiMOS) image. The locations can be local or remote. The first location searched is the primary image location. If not found, the secondary image location is searched, and lastly, the tertiary image location is searched.

Note:

The configuration and image loading information described in this section applies to all the 7210 SAS platforms with the following exceptions:

  1. On 7210 SAS-R6 and 7210 SAS-R12, the following caveats apply:
    1. only manual mode using OOB port or Ethernet management port is supported
    2. obtaining an IP address and other parameters using DHCP with the OOB port is not supported
    3. auto-init is not supported
  2. On 7210 SAS-Mxp and 7210 SAS-T, both manual mode and auto-init mode are supported.
  3. On 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE, the manual mode is used only to boot the platform in standalone mode.

4.2.1. Boot sequence and image loading

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.

  1. Figure 4 shows the bootstrap load process.
  2. Figure 5 shows an overview of the system initialization process and the multiple options available to initialize the system.
  3. Figure 6 shows the system initialization process in manual mode to create a new BOF or edit an existing BOF.
  4. Figure 7 shows the system initialization process in auto-init mode using partially configured BOF parameters.
  5. Figure 8 shows the system initialization process using auto-init mode to retrieve the BOF from the network.
  6. Figure 9 shows the process for booting up the TiMOS (both.tim) image.
Figure 5:  System initialization: bootstrap process overview 

See Persistence for more information on persistence of the index files.

Figure 6:  System initialization: bootstrap process for manual mode 

See Manual mode for more information about the manual mode process.

Figure 7:  System initialization: bootstrap process for auto-init mode with partial BOF 

See Auto-init mode for more information on operating in the auto-init mode with a partial BOF.

Figure 8:  System initialization: bootstrap process for auto-init mode 

When the both.tim file is successfully downloaded, control is passed from the bootstrap image to the TiMOS image. The TiMOS image attempts to load the configurations from the downloaded configuration file. If no configuration file location is present in the BOF, the system is loaded with the default configuration.

Note:

During the auto-init procedure, if the configuration file or image file download fails from the network, the system reinitiates the auto-init process.

See Auto-init mode for more information about the auto-init mode process.

Figure 9:  System initialization: TiMOS boot 

4.2.2. BOF chassis-role and host-type parameters for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE

On the 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE, 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.

The bof>host-type command can be set to one of the following values:

  1. none (factory default setting)
  2. standalone
  3. satellites

The chassis-role boot parameter (not available in the BOF) can be set to one of the following values:

  1. factory-default
    By default, the chassis-role boot parameter value is set to factory-default when the 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE and 7210 SAS-Mxp are shipped from the factory. In the factory-default setting, the user can use auto-init to retrieve the BOF and boot the node in either standalone or satellite mode by setting the host-type parameter in the BOF.
    By default, the boot loader assigns a value of none to the host-type parameter and uses this value if the host-type parameter is not explicitly received in the BOF. As a result, in the factory-default setting, the user can boot the node in standalone mode without setting the host-type parameter to an explicit value (which maintains backward compatibility).
  2. standalone
    This parameter setting forces the node to operate in standalone mode. In the standalone setting, the host-type parameter value in the BOF (retrieved through auto-init, present locally, or configured manually) must be set to either standalone or none. If host-type is set to satellites, the boot loader detects a mismatch and does not boot up.
  3. satellite
    This parameter setting forces the node to operate only in satellite mode. In the satellite setting, the host-type parameter value in the BOF (retrieved through autoinit, present locally, or configured manually) must be set to satellites. If host-type is set to standalone, the boot loader detects a mismatch and does not boot up.

The following table describes the boot loader action when the chassis-role and host-type parameters are set to one of the allowed values.

Table 22:  7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE boot loader actions for chassis-role and host-type parameters  

Boot parameter: chassis-role

BOF parameter: host-type

Boot loader action

factory-default

satellites

  1. The user sets chassis-role to satellite.
  2. The system boots up successfully in satellite mode.
  3. On subsequent reboots, the system will continue to boot up in satellite mode.

standalone

  1. The user sets chassis-role to standalone.
  2. The system boots up successfully in standalone mode.
  3. On subsequent reboots, the system will continue to boot up in standalone mode.

none

(host-type is not set to any value explicitly)

  1. The chassis-role value is unchanged from factory-default.
  2. The system boots up successfully in standalone mode.
  3. On subsequent reboots, the system will continue to boot up in standalone mode, if the value of host-type is not set explicitly (that is, it is set to none).

standalone

standalone

  1. The chassis-role value is unchanged from standalone.
  2. The system boots up successfully in standalone mode.
  3. On subsequent reboots, the system will continue to boot up in standalone mode.

satellites

The boot loader detects a mismatch and returns an error. Depending on the context of the boot loader, it will take one of the following actions:

  1. If the boot loader is in auto-init, it will retry auto-init to fetch a new BOF with the correct value for host-type.
  2. If the boot loader was interrupted to configure the BOF parameters manually, it will go back to provide an option for the user to change the value of host-type to the correct value.

none

  1. The value of chassis-role is unchanged from standalone.
  2. The system boots up successfully in standalone mode.
  3. On subsequent reboots, the system will continue to boot up in standalone mode if the host-type value is not set explicitly (that is, the value is set to none).

satellite

satellites

  1. The chassis-role value is unchanged from satellite.
  2. The system boots up successfully in satellite mode.
  3. On subsequent reboots, the system will continue to boot up in satellite mode.

standalone

The boot loader detects a mismatch and returns an error. Depending on the context of the boot loader, it will take one of the following actions:

  1. If the boot loader is in auto-init, it will retry auto-init to fetch a new BOF with the correct value for host-type.
  2. If the boot loader was interrupted to configure the BOF parameters manually, it will go back to provide an option for the user to change host-type to the correct value.

none

(host-type is not set to any value explicitly)

Not recommended

4.2.3. Configuration notes for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp

The following BOF configuration guidelines apply to these platforms:

  1. When the chassis-role parameter for the node is set to satellite, DHCP requests are sent out of the following ports:
    1. ports 1/1/25, 1/1/26 (10GE ports) on the 24-port 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Mxp variants
    2. ports 1/1/49, 1/1/50 (10GE ports) on the 48-port 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE variants
    3. ports 1/1/65, 1/1/66 (100GE ports), and ports 1/1/1, 1/1/2 (which are 10GE ports) on the 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4 variant
    4. ports 1/1/c1/1 and 1/1/c2/1, and 10 GE ports 1/1/1 and 1/1/2 on the 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant
    The boot loader continuously iterates over the previously mentioned ports, sending out DHCP requests until the boot loader receives a response from the host.
  2. When the chassis-role parameter for the node is set to standalone, DHCP requests are sent out of the following ports:
    1. ports 1/1/27, 1/1/28 (10GE ports) and ports 1/1/1, 1/1/2 (1GE ports) on the 24-port 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Mxp variants
    2. ports 1/1/51, 1/1/52 (10GE ports) and ports 1/1/1, 1/1/2 (1GE ports) on the 48-port 7210 SAS-Sx/S 1/10GE, and 7210 SAS-S 1/10GE variants
    3. ports 1/1/67, 1/1/68 (100GE ports) and ports 1/1/1, 1/1/2 (10GE ports) on the 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4 variant
    4. ports 1/1/c3/1 and 1/1/c4/1, and 10 GE ports 1/1/1 and 1/1/2 on the 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant
    In addition, the boot loader will attempt to load the TiMOS image (both.tim) from the local flash if autoinit fails (that is, no responses were received from the DHCP server).
  3. When the node is shipped from the factory (with the chassis-role set to factory-default) and powered up for the first time, the node sends out DHCP requests on the following ports:
    1. 10GE ports 1/1/25, 1/1/26, 1/1/27, and 1/1/28 on the 24-port 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Mxp
    2. 10GE ports 1/1/49, 1/1/50, 1/1/51 and 1/1/52 on the 48-port 7210 SAS-Sx 1/10GE and 7210 SAS-S 1/10GE
    3. the first two 1GE ports, 1/1/1 and 1/1/2, on all 7210 SAS-Sx/S 1/10GE and 7210 SAS-Mxp variants
    On a 7210 SAS-Sx 10/100GE CFP4 platform shipped from the factory, the DHCP requests are sent out of the first two 10GE ports (1/1/1 and 1/1/2) and all 100GE ports (1/1/65, 1/1/66, 1/1/67, and 1/1/68).
    On a 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant, the DHCP requests are sent out of ports 1/1/c1/1, 1/1/c2/1, 1/1/c3/1, and 1/1/c4/1, and the first two 10 GE ports (1/1/1 and 1/1/2). To change this, connect to the console and modify the chassis-role parameter value to either satellite or standalone, as required. After the chassis-role parameter is updated, the node attempts autoinit to retrieve the BOF.

4.3. Persistence

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.

Traps, logs, and console messages are generated if problems occur and SNMP shuts down for all SNMP gets and sets; however, traps are issued.

4.4. Configuration guidelines for auto-init and manual mode

This section describes the configuration guidelines for the auto-init and manual modes:

  1. The Ethernet management port does not support auto-init mode. The use of DHCP to obtain the BOF from the network and other system parameters is currently not supported on Ethernet management ports.
  2. In auto-init mode, DHCP requests sent out by the node are in two formats. The system attempts to communicate with the DHCP server in these two formats, one after another (if necessary).
    1. Initially, the DHCP requests are sent out with a priority VLAN tag (VLAN ID = 0, dot1p PCP bits set to 7).
    2. If no response is received from the DHCP server after the DHCP request is sent, DHCP requests are sent without VLAN tags (that is, null-tagged packets).
  3. In auto-init mode, the BOF can be downloaded through FTP or TFTP based on the information a client receives from the DHCP server. The DHCP client tries the following options to obtain the BOF name and the server IP address:
    1. using the vendor-specific option
      The client searches for option 43 in the DHCP reply. This provides the URL, which has to be accessed through FTP. For example: ftp://abcd:xyz@10.0.0.2/test/bof.cfg. If this file is found the client retrieves this file.
    2. collating server-name and file-name
      If option 43 is not found in the DHCP reply, a URL is formed by using the tftp-server name and the boot-file retrieved via TFTP. The IP address of the TFTP server is obtained from DHCP option 66 or the "sname" field of a DHCP message, and the filename on the TFTP server is obtained from DHCP option 67 or the "file" field of a DHCP message.
  4. In manual mode, if the OOB port is enabled (that is, if no eth-mgmt-disable is configured), the OOB port is used to download the TIMOS image file and configuration file specified in the BOF, and the system boot is successfully completed. If a system boot fails, the uplinkA and uplinkB parameters are used to retrieve the TIMOS image and configuration files.
  5. On a factory-shipped 7210 SAS-T device, the system attempts the auto-init process (that is, sends DHCP requests) using the first two 1GE ports (1/1/1 and 1/1/2 on 7210 SAS-T) and the last two 10GE ports (1/1/25 and 1/1/26 on 7210 SAS-T). See System boot options for 7210 SAS-Mxp, 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE in satellite mode and System boot options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in standalone mode for information about ports used for bootup on these platforms.
  6. The system sends out the DHCP request on a single port at a time and waits for the DHCP server to respond. If a successful server response is received, the auto-init process uses the information to boot up the system. If no response is received from the server within a stipulated time, the system sends out DHCP requests on the next port in the list based on a specific order, looping through all the ports until a successful response is received from the server, or the user interrupts the boot process.
  7. When using auto-init with partial BOF configuration, the user has the option to either stop auto-init by logging in to the node and using the console to run the admin>auto-init stop command or let auto-init continue.
  8. The user can intervene to stop auto-init at any time when auto-init is in progress. The system logs the progress of auto-init. The system emits the LED light until auto-init is complete or when the user stops the auto-init process.

4.5. Resetting the node to the factory default setting

From release 4.0 onward, you can use the bof>bof-password command to modify the factory default BOF password password.

The user must enter the correct BOF password to edit the BOF parameters. If the incorrect password is entered three times consecutively, the system prompts the user, after the third attempt, to reset the BOF password to the factory default.

If the user chooses not to reset the BOF password, the system prompts the user to enter the password again. If the user chooses to reset the password to factory default, the system also resets the flash to factory defaults (removes all files from the flash drive, except the boot image file (cf1:\boot.tim) and TiMOS image file (cf1:\both.tim)) as a security measure to prevent malicious access to the configuration file.

After password reset, the node is rebooted with the factory default settings; the BOF parameters are also set to default values. The user must now setup the box using the same steps that were used during first-time boot up of the factory-shipped box. After the system boots up with this setup, use the factory default password password to edit the BOF parameters, and use the bof>bof-password command to change the password again.

Note:

  1. The BOF password can be changed from the default value to any other user-defined value only at the TiMOS level.
  2. Nokia strongly recommends that the user should not rename cf1:\boot.tim and cf1:\both.tim if the system needs to retain them during the password recovery procedure.
  3. Nokia strongly recommends that the user should retain a backup copy of all the image files, configuration files, and other data.

The following sample logs show the system console prompts that are displayed when the user forgets the password and chooses to reset the password to the factory default setting. The BOF contents before and after the reset are also displayed.

Note:

The BOF parameters are set to default values after a password reset.

 
TiMOS BOOT LOADER
 
CPLD Version: 2.1
Time from clock is FRI AUG 19 09:22:46 2016 UTC
USB:   USB EHCI 1.00
scanning bus for devices...
1 USB Device(s) found
Number of blocks in device 0 is 0
Number of bytes per block in device 0 is 0
Switching serial output to sync mode...   done
 
Looking for cf1:/bof.cfg ... OK, reading
 
Contents of Boot Options File on cf1:
    primary-image      ftp://*:*@xxx.xxx.xx.xx/xxx/xx/xxx/xx/xxx/both.tim
    primary-config     cf1:\sasm.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xxx/24 active
    eth-mgmt-route     x.x.x.x/0 next-hop xx.xxx.xx.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#uplinkA Port Settings:
uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    0
    uplinkA-vlan       0
#uplinkB Port Settings:
uplinkB-port       1/1/2
    uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-address    0
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    uplink-mode        network
    acl-mode           IPv6-None
    use-expansion-card-type   m4-ds1-ces
    no  console-disabled
 
Hit a key within 3 seconds to change boot parameters...
 
Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt
 
Password:
Incorrect password
 
Password:
Incorrect password
 
Password:
Incorrect password
 
 Authentication failed, Do you want to reset password?(yes/no)
 
*******************************************************************
  On reset,the node's flash contents will be set to factory defaults.
  All files on the flash will be removed. If present, files
  cf1:/boot.tim and cf1:/both.tim are not removed.
  Please ensure that you have a backup of the required
  files before you proceed.
*******************************************************************
 
'yes' or 'no' ?
'yes' or 'no' ? yes      
 
********************************************
*** Chassis must not be powered off nor  ***
*** cards removed while password reset   ***
*** is in progress                       ***
********************************************
Password reset complete. Restarting...
 

At this point, the password reset is complete and the node restarts to boot up with factory default settings.

Resetting...OK
ø
Nokia 7210 Boot ROM. Copyright 2016 Nokia.
 
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 'NS1023C1436'
Bootlog started for Version 9-V-0.0.I1111
Build V-0.0.I1111 bootrom/mpc 7xxx
Built on Wed Jun 29 21:55:30 IST 2016 by builder in /builder/0.0/panos/main
 
?Attempting to load from file cf1:/boot.tim
Version L-4.0.beta-private, Sat Aug 20 12:59:26 IST 2016 by abc /abc/ws-40b/panos/
main
text:(3706043-->13139264) + data:(528557-->2068192)
Starting at 0xb000000...
 
 
Total Memory: 1GB  Chassis Type: sas  Card Type: badami_7210
TiMOS-L-4.0.beta-private boot/mpc NOKIA SAS 7210 Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Sat Aug 20 12:59:26 IST 2016 by abc in /abc/ws-40b/panos/main
 
TiMOS BOOT LOADER
 
CPLD Version: 2.1
Time from clock is FRI AUG 19 09:24:05 2016 UTC
USB:   USB EHCI 1.00
scanning bus for devices...
1 USB Device(s) found
Number of blocks in device 0 is 0
Number of bytes per block in device 0 is 0
Switching serial output to sync mode...   done
 
Looking for cf1:/bof.cfg ... not found
Could not find bof.cfg on any of the local drives.
 
Default Settings
----------------
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    0
    uplinkA-vlan       0
#uplinkB Port Settings:
uplinkB-port       1/1/2
    uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-address    0
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    uplink-mode        network
    acl-mode           IPv6-None
    use-expansion-card-type   m4-ds1-ces
    no  console-disabled
Hit a key within 1 second to change boot parameters...
Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt
Password:
Note:

At this password prompt, you are required to enter the default password password .

4.6. BOF password

7210 SAS devices require a BOF password for the user to change the contents of the BOF using the BOF interactive menu. Additionally, the 7210 SAS supports an option to securely store the BOF password using the bof secure-bof-password command, as shown in the following sample logs.

------------
primary-image ftp://*:*@135.254.173.17//usr/global/images/21.9/B1-8/7xxx/
bcmiproc-both.tim
primary-config ftp://*:*@135.254.173.3/tmp/dxp/dxp2537.cfg
secondary-config ftp://*:*@135.254.173.3/tmp/dxp/dxp2537bkup.cfg
password *
ping-address 1.1.1.1
#uplinkA Port Settings:
uplinkA-port 1/1/1
uplinkA-autoneg
uplinkA-duplex full
uplinkA-speed 1000
uplinkA-address 10.135.25.37/24
uplinkA-vlan null
uplinkA-route 135.0.0.0/8 next-hop 10.135.25.1
#uplinkB Port Settings:
uplinkB-port 1/1/11
no uplinkB-autoneg
uplinkB-duplex full
uplinkB-speed 10000
uplinkB-address 0
uplinkB-vlan 0
#System Settings:
wait 3
persist off
console-speed 115200
uplink-mode access-uplink
no console-disabled
secure-bof-password enable
Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no): y
Successfully saved the new settings in cf1:/bof.cfg
----------------------------

4.7. OOB Ethernet management port

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.

Refer to the 7210 SAS OS Software Release Notes 11.0Rx for information about the specific software release that supports OOB management port and IPv6.

4.7.1. IPv6 configuration guidelines in OOB node management

The following are the configuration guidelines for IPv6 on an OOB management port of the node:

  1. The management port on the management router instance only supports host functionality.
  2. It is required that an IPv4 address is configured in the BOF. A BOF that contains only IPv6 addresses is not supported.
  3. IPv6 duplicate address detection is not supported.
  4. IPv6 auto-configuration is not supported.
  5. IPv6 over IPv4 tunneling is not supported.
  6. IPv6 path MTU discovery is not supported.
  7. The router discovery option is not supported on the management port.

4.8. Security for console port and Ethernet 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.

Note:

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.

4.9. Initial system startup process flow

The following figure shows the process to start your system. This example assumes that the boot loader and BOF image and configuration files are successfully located.

Figure 10:  System startup process flow 

4.10. Configuration notes

This section describes BOF configuration guidelines:

  1. The loading sequence is based on the order in which the sequence is placed in the configuration file. It is loaded as it is read during bootup.