Appendix: 7210 SAS boot procedures

This chapter describes the booting procedures for 7210 SAS devices.

This chapter provides information about booting a factory-shipped 7210 SAS device for the first time. It also includes information to boot the 7210 SAS device after subsequent reboots that are initiated by issuing the admin reboot command. For subsequent reboots, the BOF and the TiMOS image are stored on the local flash.

The 7210 SAS supports two modes for a first-time boot of a factory-shipped node or to boot the node after the admin>reboot auto-init command is executed. The supported boot modes are:

auto-init mode

In this mode, the boot procedure uses an external DHCP server to provide the IP address and other IP parameters, and the BOF configuration, which contains the image location and the configuration file location. This mode does not require user intervention and provides an option for zero-touch provisioning of the node.

This method also provides an option to modify the default values of the BOF parameters used for auto-init and customize a specific set of BOF parameters so that auto-init is supported in the customer network environment. See Auto-init mode for a list of BOF parameters that the user can modify.

The user requires console access to modify BOF parameters. After the partial BOF is saved, the system continues using the auto-init mode procedure to boot, with auto-init using the modified values of the BOF parameters that the user has provided.
manual mode

In this mode, the boot procedure requires user intervention to complete the process. During the boot process, the user must log in to the console on the node and configure the IP address, other IP parameters, and the location of the image file and configuration file. The following options are supported to boot the 7210 SAS device in manual mode:
- boot from the image on flash
- boot from the network using uplink ports
- boot from the network using the OOB Ethernet management port

The following table lists the supported boot procedures for 7210 SAS devices.

Table 1. 7210 SAS boot procedure overview
Section	Description
Procedure to boot using auto-init mode	This procedure uses the auto-init mode to boot the 7210 SAS device.
Procedures to boot using manual mode	This procedure uses the manual mode to boot the 7210 SAS device. In manual mode, the device can be booted from the local flash or it can be booted from the network using an uplink port or the OOB Ethernet management port. The following procedures apply: Procedure to boot from the image on flash in manual mode This procedure uses the manual mode to boot the 7210 SAS device from the local flash. Procedure to boot from the network in manual mode using uplink ports This procedure uses the manual mode to boot the 7210 SAS device from the network using an uplink port. Procedure to boot from the network in manual mode using the OOB Ethernet management port This procedure uses the manual mode to boot from the 7210 SAS device from the network using the OOB Ethernet management port.
Procedure to boot when the BOF is present locally	This procedure uses the BOF that is present locally to boot the 7210 SAS device.
Procedure to boot in the satellite mode	This procedure boots the 7210 SAS device in the satellite mode.
Procedure to boot in the standalone-VC mode	This procedure boots the 7210 SAS device in the standalone-VC mode.
Procedure to boot in standalone-VC mode for factory-default units using an SD card	This procedure boots the 7210 SAS factory-default units in the standalone-VC mode of operation using an SD card.

Note:

Console outputs shown in this chapter are examples only; actual displays may differ depending on the 7210 SAS platform, supported functionality, and user configuration.

Procedure to boot using auto-init mode

Note:

The auto-init mode is supported on all 7210 SAS platforms, except the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS platforms that are configured in the standalone-VC or satellite modes of operation.

This section describes the procedure to boot the 7210 SAS using the auto-init mode.

The auto-init mode is used to boot the 7210 SAS device in the following scenarios:

user boots the device for the first time
user boots the device after a reset to the factory default settings
user boots the device after the execution of the admin>reboot auto-init command

To boot using the auto-init mode requires a DHCP server to be configured in the network and reachable by the system. The 7210 SAS device uses the auto-init mode to obtain the BOF from the network using the IP address and file location provided by the DHCP server, and uses the parameters specified in the BOF to download the TiMOS image file and configuration file required to boot the node. See Auto-init mode for more information about the auto-init procedure and the DHCP parameters used.

Perform the following steps to boot the 7210 SAS device using the auto-init mode:

Optional: Connect the console port to the serial port of the PC and power on the 7210 SAS device to display log messages generated on the screen.

Note:

This is an optional step. Perform this step only if you need to diagnose issues with the auto-init procedure, if any.

The system starts booting and the following console output is displayed.

Nokia 7xxx Boot ROM. Copyright 2000-2020 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-20.3.B1-1 on Wed Feb 12 15:29:52 IST 2020 by sasbuild
Version: 0x38
Processor core is CN66xx
COLD boot on processor #1
?Preparing for jump to RAM...
Starting bootrom RAM code...
Boot rom version is v56
CPU #1 booted from working sector
CPU Control FPGA version is 0x3D
FPGA A version is 0x3D. FPGA B version is 0x3D. FPGA C version is 0x3D.
Restart type = 0x01
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000
Power on Diagnostics passed
Board Serial Number is 'NS1715T0019'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-V-20.3.B1-1 bootrom/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:28:49 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/m
Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Version L-20.3.B1-1, Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(13818400-->40990080) + data:(3162656-->19580220)
Starting at 0x18000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-L-20.3.B1-1 boot/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/
main

TiMOS BOOT LOADER
Time from clock is WED MAR 04 09:23:22 2020 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : factory-default

The system lists the default settings and the following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading

Contents of Boot Options File on cf1:
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/65
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/66
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled

Hit a key within 1 second to change boot parameters...

At the prompt, wait until the specified wait time has elapsed. The system will direct DHCP requests from the uplink ports to reach a DHCP server.

The following console output is displayed.

Trying DHCP on Port 1/1/65 (Priority tagged) 
Chassis MAC Address: D0:99:D5:97:02:41
DHCP failed on Port 1/1/65
Failure reason: SFP not present on port

Trying DHCP on Port 1/1/65 (Untagged) 
Chassis MAC Address: D0:99:D5:97:02:41
DHCP failed on Port 1/1/65
Failure reason: SFP not present on port

Trying DHCP on Port 1/1/66 (Priority tagged) 
Chassis MAC Address: D0:99:D5:97:02:41
DHCP failed on Port 1/1/66
Failure reason: SFP not present on port

Trying DHCP on Port 1/1/66 (Untagged) 
Chassis MAC Address: D0:99:D5:97:02:41
DHCP failed on Port 1/1/66
Failure reason: SFP not present on port

Trying DHCP on Port 1/1/67 (Priority tagged) 
Chassis MAC Address: D0:99:D5:97:02:41
Port 1/1/67, Speed:100000, Duplex:Full, Link:Up.
DHCP failed on Port 1/1/67

Trying DHCP on Port 1/1/67 (Untagged) 
Chassis MAC Address: D0:99:D5:97:02:41
Port 1/1/67, Speed:100000, Duplex:Full, Link:Up.

DHCP Server:192.168.2.8
    Boot device addr: 192.168.2.9
    Subnet mask: 24
    Boot host: 192.168.2.8
    Url from Boot file: tftp://192.168.2.8/images-pf/SASS/voy/bof.cfg
Initial DNS resolving preference is ipv4-only

The DHCP server responds to the system request and supplies an IP address, default gateway information, and a BOF location.
The following console output is displayed.
```
Looking for tftp://192.168.2.8/images-pf/SASS/voy/bof.cfg ... OK, reading
Successfully saved the new settings in cf1:/bof.cfg
```

The system applies the IP configuration and downloads the BOF from the location specified by the DHCP server. The BOF is saved on the flash drive.

The 7210 SAS device initiates the boot using the BOF, and the following console output is displayed.

My New Settings
------------
    primary-image      ftp://*:*@192.168.2.8/./images-pf/SASS/voy/hops-both.tim
    primary-config     ftp://*:*@192.168.2.8/./images-pf/SASS/voy/dut-h.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   192.168.2.9/24 active
    eth-mgmt-route     192.250.0.0/16 next-hop 192.168.2.8
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    host-type        standalone
Setting the chassis role to standalone.

Configuring Network with eth-mgmt Port Setting.....
Primary config file location: ftp://*:*@192.168.2.8/./images-pf/SASS/voy/dut-h.cfg
Initial DNS resolving preference is ipv4-only
Downloading 'ftp://*:*@192.168.2.8/./images-pf/SASS/voy/dut-h.cfg'...OK

Sap Index file location: ftp://*:*@192.168.2.8/./images-pf/SASS/voy/dut-h.sdx
Downloading 'ftp://*:*@192.168.2.8/./images-pf/SASS/voy/dut-h.sdx'...OK

Primary image location: ftp://*:*@192.168.2.8/./images-pf/SASS/voy/hops-both.tim
Initial DNS resolving preference is ipv4-only
Loading image ftp://*:*@192.168.2.8/./images-pf/SASS/voy/hops-both.tim
Version B-20.3.B1-1, Wed Feb 12 15:33:08 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(41664192-->183719312)

After the 7210 SAS device boots up, the following login prompt is displayed.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 14:32:04 IST 2011 by builder in /builder/3.0B5/panos/main
Login:

At the prompt, enter admin for the default username and password, and log in to the 7210 SAS device.

Procedures to boot using manual mode

Note:

The manual mode is supported on all 7210 SAS platforms, except those operating in satellite mode.

This section describes the procedures to boot the 7210 SAS from the network or flash using the manual mode.

The manual mode can be used to boot the 7210 SAS device in the following scenarios:

user boots the device for the first time
user boots the device after a reset to the factory default settings, or after executing the admin>reboot auto-init command (this command is not supported on the 7210 SAS-R6 and 7210 SAS-R12, and 7210 SAS platforms configured in the standalone-VC mode of operation)

In all scenarios, the user must create a local BOF by connecting a console to the node and interrupting the boot process to configure the BOF parameters. The following sections provide the details for configuring the BOF parameters under different scenarios.

The manual mode has two options:

7210 SAS device is booted from the local image on flash; see section Procedure to boot from the image on flash in manual mode (supported on all 7210 SAS platforms, except those operating in the satellite mode)
7210 SAS device is booted from the network using an uplink port (section Procedure to boot from the network in manual mode using uplink ports; supported on all 7210 SAS platforms, except the 7210 SAS-R6 and 7210 SAS-R12) or the Ethernet management port (section Procedure to boot from the network in manual mode using the OOB Ethernet management port; supported on all 7210 SAS platforms when the Ethernet management port is available)

Procedure to boot from the image on flash in manual mode

Note:

This procedure is not supported for 7210 SAS platforms configured in the satellite mode of operation.

7210 SAS platforms that are factory-shipped with the boot.tim and both.tim (TiMOS image) on the internal flash attempt to boot using the auto-init mode when they are booted for the first time from factory. If the auto-init mode fails, the node loads with the image on the flash. If the user wants to continue using this image, they must connect to a console and execute the admin auto-init stop command in the TiMOS prompt. If the user does not execute this command, the device reboots and attempts the auto-init mode procedure again.

For the 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C, 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T, the user must buy a software license that is factory-shipped with the TiMOS image on a flash or SD card device. The user must plug the flash or SD card device in the designated slot for the external flash or SD card device and power on the unit.

Note:

See the corresponding 7210 SAS chassis installation guide for information about equipment required to setup the device.

Perform the following steps to boot the system in the manual mode from the local image on the flash:

Connect the 7210 SAS console port to the serial port of the PC, and power on the 7210 SAS device. The system starts booting and the following console output is displayed.

Nokia 7xxx Boot ROM. Copyright 2000-2020 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-20.3.B1-1 on Wed Feb 12 15:29:52 IST 2020 by sasbuild
Version: 0x38
Processor core is CN66xx
COLD boot on processor #1
?Preparing for jump to RAM...
Starting bootrom RAM code...
Boot rom version is v56
CPU #1 booted from working sector
CPU Control FPGA version is 0x3D
FPGA A version is 0x3D. FPGA B version is 0x3D. FPGA C version is 0x3D.
Restart type = 0x01
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000
Power on Diagnostics passed
Board Serial Number is 'NS1720T0009'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-V-20.3.B1-1 bootrom/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:28:49 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/m

Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Version L-20.3.B1-1, Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(13818400-->40990080) + data:(3162656-->19580220)
Starting at 0x18000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-L-20.3.B1-1 boot/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/
main

TiMOS BOOT LOADER
Time from clock is SUN MAR 15 15:19:08 2020 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : factory-default

The system lists the default settings and the following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading
Contents of Boot Options File on cf1:
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/65
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/66
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
Hit a key within 3 seconds to change boot parameters...

At the prompt, press any key to initiate boot parameter updates. The following console output is displayed.

Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt

Waiting for 30 seconds to enter password
Password:

At the prompt, enter the default password password, and initiate the BOF edit.

The system accepts the password and the following console output is displayed.

You must supply some required Boot Options. At any prompt, you can type:
"restart" - restart the query mode.
"reboot" - reboot.
"exit" - boot with with existing values.
"diag" - enter the diag shell.
"reset" - reset the bof and reboot.

Press ENTER to begin, or 'flash' to enter firmware update...

At the prompt, press Enter to edit the BOF. The following console output is displayed.

Chassis-Role
-------------
Current chassis-role is : factory-default
You can change it to { satellite | standalone }.
Press ENTER to continue OR "edit" to change the chassis-role : 
Chassis-role is set to factory-default, Do you wish to continue with this (yes/no) :

At the prompt, enter yes. The following console output is displayed.

Software Location
-----------------
   You must enter the URL of the TiMOS software.
   The location can be on a Compact Flash device,
   a USB flash drive, or on the network.

   Here are some examples
      cf1:/timos1.0R1
      uf1:/timos1.0R1
      ftp://user:passwd@192.168.1.150/./timos1.0R1
      ftp://user:passwd@[3FFE::1]/./timos1.0R1

or Type 'auto' to retrieve BOF configuration through DHCP.

Software Image URL:

At the prompt, enter the location of the image.

In factory-shipped 7210 SAS devices, the image is typically available at cf1:\both.tim or cf2:\both.tim.

The following console output is displayed.

Configuration File Location
---------------------------
   You must enter the location of configuration
   file to be used by TiMOS.  The file can be on
   a Compact Flash device, a USB flash drive, or
   on the network.

   Here are some examples
      uf1:/config.cfg
      cf1:/config.cfg
      ftp://user:passwd@192.168.1.150/./config.cfg
      ftp://user:passwd@[3FFE::1]/./config.cfg
      tftp://192.168.1.150/./config.cfg
      tftp://[3FFE::1]/./config.cfg

Config File URL:

Enter the location of the configuration file, or press Enter to skip this step.

The following console output is displayed.

Current configuration enables use of console (setting is "no console-disabled")
Press ENTER to proceed with existing setting  or 'disable' to disable console access
:

At the prompt, press Enter. The following console output is displayed.

New Settings
------------
    primary-image      cf2:/both.tim
    primary-config     uf1:/sassx64.cfg
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/65
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/66
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no):

At the prompt, enter yes. The 7210 SAS device begins to boot with the new settings. The following console output is displayed.

Successfully saved the new settings in cf1:/bof.cfg

Configuring Network with uplinkA Port Setting.....
Primary config file present at: uf1:/sassx64.cfg

Skipping missing or bad Sap index file 'uf1:/sassx64.sdx'

Primary image location: cf2:/both.tim
Loading image cf2:\both.tim
Version B-20.3.B1-1, Wed Feb 12 15:33:08 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(41664192-->183719312) + data:(7133216-->49945144)
Executing TiMOS image at 0x2800000

After the 7210 SAS device boots up, the following login prompt is displayed.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 14:32:04 IST 2011 by builder in /builder/3.0B5/panos/main
Login:

At the prompt, enter admin for the default username and password, and log into the 7210 SAS device.

Note:
The SYS LED is green after the device has successfully completed the boot process and is running normally.

Procedure to boot from the network in manual mode using uplink ports

Note:

This procedure is supported on all 7210 SAS platforms, except the 7210 SAS-R6 and 7210 SAS-R12, and all platforms configured in the satellite mode of operation.

Perform this procedure to boot a 7210 SAS device from the network without using the auto-init mode.

Note:

See the corresponding 7210 SAS chassis installation guide for information about equipment required to setup the device.

The front panel ports (referred to as uplinkA and uplinkB in the sample output used in this procedure) are used to boot the device from the network.

Note:

Nokia recommends that the TiMOS image should be stored on the internal flash so that it is available for use in the case where booting the system from the flash is required later on subsequent reboot.

Perform the following steps to boot from the network in the manual mode using uplink ports.

Power on the 7210 SAS device.

Use the uplink ports to boot from the network.

Nokia SASDxp 7210 Boot ROM. Copyright 2000-2020 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-20.3.B1-1 on Wed Feb 12 15:29:18 IST 2020 by sasbuild
Version: 0x8
SASDxp-DC Board
Shmoo tuning data in flash is valid, load it
DDR Tuning Complete.
Passed!
Copying code from FLASH to RAM....
Done
Board CPLD Version: 0x0e
Reboot Reason: 0x05
Boot rom version is v8
>>> RAM: Testing DDR Passed!
Board Serial Number is 'NS1917T0023'
DDR Tuning Complete.

Tuning values already saved. Skip saving to flash.
Memory Test Passed!
Jumping to vxrom at 0x61400000 now..................

^[[6~^[[6~
Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Version L-20.3.B1-1, Wed Feb 12 15:30:14 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(12972416-->39659312) + data:(4504352-->20039220)
Starting at 0x6f000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x4e
TiMOS-L-20.3.B1-1 boot/ARMiproc Nokia SAS-Dxp 6T4F2SFP+ 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:30:14 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/m

TiMOS BOOT LOADER
Time from clock is SUN MAR 15 05:09:48 2020 UTC
Switching serial output to sync mode...   done

The system lists the default settings and the following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading
Contents of Boot Options File on cf1:
#uplinkA Port Settings:
    uplinkA-port       1/1/11
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      10000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/12
    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
Hit a key within 1 second to change boot parameters...

At the prompt, press any key to initiate boot parameter updates. The following console output is displayed.

Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt

Waiting for 30 seconds to enter password
Password:

At the prompt, enter the default password password. The system accepts the password and the following console output is displayed.

You must supply some required Boot Options. At any prompt, you can type:
"restart" - restart the query mode.
"reboot"  - reboot.
"exit"    - boot with with existing values.
"diag"    - enter the diag shell.
"reset"   - reset the bof and reboot.

Press ENTER to begin, or 'flash' to enter firmware update...

At the prompt, press Enter to initiate the update. The following console output is displayed.

Software Location
-----------------
   You must enter the URL of the TiMOS software.
   The location can be on a Compact Flash device,
 or on the network.

   Here are some examples
      cf1:/timos1.0R1
      ftp://user:passwd@192.168.1.150/./timos1.0R1
      ftp://user:passwd@[3FFE::1]/./timos1.0R1

or Type 'auto' to retrieve BOF configuration through DHCP.

Software Image URL:

At the prompt, enter the URL location of the software; for example, ftp://<user>:<password>@10.10.170.22/./images/both.tim. The following console output is displayed.

Configuration File Location
---------------------------
   You must enter the location of configuration
   file to be used by TiMOS.  The file can be on
   a Compact Flash device, or on the network.

   Here are some examples
      cf1:/config.cfg
      ftp://user:passwd@192.168.1.150/./config.cfg
      ftp://user:passwd@[3FFE::1]/./config.cfg
      tftp://192.168.1.150/./config.cfg
      tftp://[3FFE::1]/./config.cfg

Config File URL:

At the prompt, enter the URL location of the configuration file. The following console output is displayed.

Boot Interface Management
-------------------------
   You specified a network location for either the 
   software or the configuration file. You need to 
   configure either eth-mgmt or uplinkA or uplinkB ports.
   You will be asked to configure the port number, IP(v6) address,
   static routes, and VLAN Id in case of uplink ports.

Existing uplinkA port settings are:

   uplinkA-port       1/1/11
   no uplinkA-autoneg
   uplinkA-duplex     full
   uplinkA-speed      10000
   uplinkA-address    0 
   uplinkA-address    0 
   uplinkA-vlan       0

   uplinkA port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, enter edit to change the port settings. The following console output is displayed.

Existing uplinkA port for Boot Interface Management is port 1/1/11.
Press ENTER to keep it.
Enter the new uplinkA port number for Boot Interface Management:

At the prompt, enter the front-panel port that is connected to the network (for example, 1/1/10). The following console output is displayed.
```
Enter uplinkA speed and duplex settings:
```

At the prompt, enter uplink port speed and duplex settings The following console output is displayed.

Auto-Negotiation is currently disabled.
Press ENTER to proceed with existing setting or 'auto' to enable auto-negotiation.
auto
Auto-negotiation will be enabled on uplinkA port.

   You need to configure the VLAN Id for this port 
   VLAN Id can be between 0 to 4094. To send out
   packets with out any VLAN tags, type "null".

Existing VLAN Id for uplinkA port is VLAN Id 0.
Press ENTER to keep it.
Enter the new VLAN Id for uplinkA port:

At the prompt, perform one of the following.

Enter null to send out packets without VLAN tags.
Enter the a VLAN tag ID for the uplink port.

The following console output is displayed.

Using port 1/1/1 as uplinkA port for Boot Interface Management

   You need to assign an IP address for this port.
   The IP address should be entered in standard
   dotted-decimal form with a network length.
   example:   192.168.1.169/24
   Or type "0" to obtain IP address and static route
   through DHCP. Existing IP address and static routes
   will be deleted.

Enter uplinkA  IP Address (Type 0 if none desired):

At the prompt, enter the port IP address and mask that the device should use (for example, 10.135.4.172/10).

Because the FTP server is on a different subnet, enter the IP routing information. The following console output is displayed.

You specified network locations which might require
static routes to reach. You will be asked to
enter static routes until all the locations become
reachable.
Static routes should be entered in the following format:
prefix/mask next-hop ip-address
example:     192.168.0.0/16 next-hop 192.168.1.254

Would you like to add a static route? (yes/no)

At the prompt, type yes and press Enter to add a static route.
```
Enter route:
```

Enter a static route to the FTP server subnet (for example, 10.10.170.0/10 next-hop 10.135.4.1). The following console output is displayed.

Existing uplinkB port settings are:

   uplinkB-port       1/1/12
   no uplinkB-autoneg
   uplinkB-duplex     full
   uplinkB-speed      10000
   uplinkB-address    0 
   uplinkB-address    0 
   uplinkB-vlan       0

   uplinkB port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, press Enter to proceed existing port settings. The following console output is displayed.

Current configuration enables use of console (setting is "no console-disabled")
Press ENTER to proceed with existing setting  or 'disable' to disable console access
:

At the prompt, press Enter to proceed with the existing settings. The following console output is displayed.

New Settings
------------
    primary-image      ftp://*:*@192.254.173.17/usr/global/images/20.3/B1-1/7xxx/
bcmiproc-both.tim
    primary-config     ftp://*:*@192.254.173.5/tmp/dxp/dxp2537.cfg
#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      192.0.0.0/8 next-hop 10.135.25.1
#uplinkB Port Settings:
    uplinkB-port       1/1/12
    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

Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no):

Enter yes to overwrite the bof.cfg file. The 7210 SAS device starts booting. The following console output is displayed.

Successfully saved the new settings in cf1:/bof.cfg

Configuring Network with uplinkA Port Setting.....
Primary config file location: ftp://*:*@192.254.173.5/tmp/dxp/dxp2537.cfg
Initializing uplinkA port using IP addr 10.135.25.37.
Port 1/1/1-->Mode:Fix-Cu, Speed:100, Duplex:Full Autoneg: On, Link:Up.
Initial DNS resolving preference is ipv4-only
Downloading 'ftp://*:*@192.254.173.5/tmp/dxp/dxp2537.cfg'...OK

Sap Index file location: ftp://*:*@192.254.173.5/tmp/dxp/dxp2537.sdx
Downloading 'ftp://*:*@192.254.173.5/tmp/dxp/dxp2537.sdx'...OK

Primary image location: ftp://*:*@192.254.173.17/usr/global/images/20.3/B1-1/7xxx/
bcmiproc-both.tim
Port 1/1/1-->Mode:Fix-Cu, Speed:100, Duplex:Full Autoneg: On, Link:Up.
Initial DNS resolving preference is ipv4-only
Loading image ftp://*:*@192.254.173.17/usr/global/images/20.3/B1-1/7xxx/bcmiproc-
both.tim
Version B-20.3.B1-1, Wed Feb 12 15:32:56 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(41388544-->175510640) + data:(6606080-->43372008)
Executing TiMOS image at 0x60100000

After the 7210 SAS device boots up, the following login prompt is displayed.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 22:44:35 IST 2011 by builder in /builder/3.0B5/R4/panos/main
Login:

At the prompt, enter admin for the default username and password, and log into the 7210 SAS device.

Note:
The Sys LED is green when the device has successfully completed the boot process and is running normally.

Procedure to boot from the network in manual mode using the OOB Ethernet management port

Note:

This procedure is not supported for 7210 SAS platforms configured in the satellite mode of operation. This procedure is supported on all 7210 SAS platforms that are equipped with an OOB Ethernet management port.

Perform the following steps to boot from the network using the OOB Ethernet management port without using the auto-init mode.

Power on the 7210 SAS device.

Use the OOB Ethernet Management port to boot from the network.

Nokia 7xxx Boot ROM. Copyright 2000-2020 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-20.3.B1-1 on Wed Feb 12 15:29:52 IST 2020 by sasbuild
Version: 0x38
Processor core is CN66xx
COLD boot on processor #1
?Preparing for jump to RAM...
Starting bootrom RAM code...
Boot rom version is v56
CPU #1 booted from working sector
CPU Control FPGA version is 0x3D
FPGA A version is 0x3D. FPGA B version is 0x3D. FPGA C version is 0x3D.
Restart type = 0x01
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000
Power on Diagnostics passed
Board Serial Number is 'NS1720T0009'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-V-20.3.B1-1 bootrom/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:28:49 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/m

Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Version L-20.3.B1-1, Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(13818400-->40990080) + data:(3162656-->19580220)
Starting at 0x18000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-L-20.3.B1-1 boot/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/
main

TiMOS BOOT LOADER
Time from clock is THU MAR 12 17:12:50 2020 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : factory-default

The system lists the default settings and the following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading
Contents of Boot Options File on cf1:
    primary-image      ftp://*:*@192.254.173.3/tmp/sass/b/both.tim
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   10.135.25.36/24 active
    eth-mgmt-route     192.0.0.0/8 next-hop 10.135.25.1
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#uplinkA Port Settings:
    uplinkA-port       1/1/65
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/66
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
Hit a key within 3 seconds to change boot parameters...

At the prompt, press any key to initiate boot parameter updates.

The following console output is displayed.

Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt

Waiting for 30 seconds to enter password
Password:

At the prompt, enter the default password password.

The system accepts the password and the following console output is displayed.

You must supply some required Boot Options. At any prompt, you can type:
"restart" - restart the query mode.
"reboot"  - reboot.
"exit"    - boot with with existing values.
"diag"    - enter the diag shell.
"reset"   - reset the bof and reboot.

Press ENTER to begin, or 'flash' to enter firmware update...

At the prompt, press Enter to initiate the update. The following console output is displayed.

Chassis-Role
-------------
Current chassis-role is : factory-default
You can change it to { satellite | standalone }.
Press ENTER to continue OR "edit" to change the chassis-role : 
Chassis-role is set to factory-default, Do you wish to continue with this (yes/no) :

At the prompt, enter yes. The following console output is displayed.

Software Location
-----------------
You must enter the URL of the TiMOS software.
The location can be on a Compact Flash device,
or on the network.

Here are some examples
cf1:/timos1.0R1
ftp://user:passwd@192.168.1.150/./timos1.0R1
tftp://192.168.1.150/./timos1.0R1

Software Image URL:

At the prompt, enter the URL location of the software; for example, ftp://<user>:<password>@10.10.170.22/./images/both.tim.

The following console output is displayed.

Configuration File Location
---------------------------
You must enter the location of configuration
file to be used by TiMOS.  The file can be on
a Compact Flash device, or on the network.

Here are some examples
cf1:/config.cfg
ftp://user:passwd@192.168.1.150/./config.cfg
tftp://192.168.1.150/./config.cfg

No existing Config URL
Press ENTER, or type 'none' for no Config URL.
Config File URL:

At the prompt, enter none. The following console output is displayed.

Boot Interface Management
-------------------------
   You specified a network location for either the 
   software or the configuration file. You need to 
   configure either eth-mgmt or uplinkA or uplinkB ports.
   You will be asked to configure the port number, IP(v6) address,
   static routes, and VLAN Id in case of uplink ports.

Existing eth-mgmt port settings are:
   eth-mgmt-port        
   eth-mgmt-address    10.135.25.36/24 
   eth-mgmt-address    0 
   eth-mgmt-route      192.0.0.0/8 next-hop 10.135.25.1

   eth-mgmt port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, enter edit to change the port settings. The following console output is displayed.

You need to assign an IP address for this port.
   The IP address should be entered in standard
   dotted-decimal form with a network length.
   example:   192.168.1.169/24
The existing eth-mgmt  IP address is 10.135.25.36/24. Press ENTER to keep it.
Enter eth-mgmt  IP Address (Type 0 if none desired):

At the prompt, enter the port IP address and mask that the device should use (for example, 10.135.4.172/10). The following console output is displayed.

In case of an IPv6, the IPv6 address should be
   entered in standard colon hexadecimal notation
   with a prefix length.
       example:   3FFE::1/112

Enter eth-mgmt  IPv6 Address (Type 0 if none desired):

At the prompt, enter 0. The following console output is displayed.

No eth-mgmt IPv6 Address configured

   You specified network locations which might require
   static routes to reach. You will be asked to
   enter static routes until all the locations become
   reachable.
   Static routes should be entered in the following format:
   prefix/mask next-hop ip-address
   example:     192.168.0.0/16 next-hop 192.168.1.254

A static route to the Primary Image exists: 192.0.0.0/8 next-hop 10.135.25.1
Do you want to keep it? (yes/no)

At the prompt, enter no. The following console output is displayed.
```
Enter route to Primary Image at 192.254.173.3:
```
At the prompt, enter the static route for the specified primary image location. The following console output is displayed.
```
A static route to the Primary Config exists: 192.0.0.0/8 next-hop 10.135.25.1
Do you want to keep it? (yes/no)
```

At the prompt, enter yes. The following console output is displayed.

Enter route to Primary Config at 192.254.173.3 192.0.0.0/8 next-hop 10.135.25.1

At the prompt, enter a static route for the specified primary configuration location. The following console output is displayed.
```
Would you like to add a static route? (yes/no)
```
At the prompt, enter yes. The following console output is displayed.
```
Enter ip route:
```
At the prompt, enter a static route to the FTP server subnet (for example, 10.10.170.0/10 next-hop 10.135.4.1). The following console output is displayed.
```
Would you like to add another static route? (yes/no)
```
At the prompt, enter no. The following console output is displayed.
```
Would you like to add another static IPv6 route?
```

At the prompt, enter no. The following console output is displayed.

Existing uplinkA port settings are:

   uplinkA-port       1/1/65
   no uplinkA-autoneg
   uplinkA-duplex     full
   uplinkA-speed      100000
   uplinkA-address    0 
   uplinkA-address    0 
   uplinkA-vlan       0

   uplinkA port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, enter disable to proceed with no backup link. The following console output is displayed.

Existing uplinkB port settings are:

   uplinkB-port       1/1/66
   no uplinkB-autoneg
   uplinkB-duplex     full
   uplinkB-speed      100000
   uplinkB-address    0 
   uplinkB-address    0 
   uplinkB-vlan       0

   uplinkB port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, enter disable to proceed with no backup link. The following console output is displayed.

Current configuration enables use of console (setting is "no console-disabled")
Press ENTER to proceed with existing setting  or 'disable' to disable console access
:

At the prompt, press Enter. The following console output is displayed.

New Settings
------------
    primary-image      ftp://*:*@192.254.173.3/tmp/sass/b/both.tim
    primary-config     ftp://*:*@192.254.173.3/tmp/sass/sassx64.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   10.135.25.36/24 active
    eth-mgmt-route     10.135.0.0/16 next-hop 10.135.25.1
    eth-mgmt-route     192.0.0.0/8 next-hop 10.135.25.1
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#uplinkA Port Settings:
    uplinkA-port       1/1/65
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/66
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled

Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no):

At the prompt, enter yes. The following console output is displayed.

Successfully saved the new settings in cf1:/bof.cfg

Configuring Network with eth-mgmt Port Setting.....
Primary config file location: ftp://*:*@192.254.173.3/tmp/sass/sassx64.cfg
Initial DNS resolving preference is ipv4-only
Downloading 'ftp://*:*@192.254.173.3/tmp/sass/sassx64.cfg'...OK

Sap Index file location: ftp://*:*@192.254.173.3/tmp/sass/sassx64.sdx
Downloading 'ftp://*:*@192.254.173.3/tmp/sass/
sassx64.sdx'...Cannot open input file ftp://*:*@192.254.173.3/tmp/sass/sassx64.sdx
0 files copied
Failed

Primary image location: ftp://*:*@192.254.173.3/tmp/sass/b/both.tim
Initial DNS resolving preference is ipv4-only
Loading image ftp://*:*@192.254.173.3/tmp/sass/b/both.tim
Version B-20.3.B1-1, Wed Feb 12 15:33:08 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(41664192-->183719312) + data:(7133216-->49945144)
Executing TiMOS image at 0x2800000
==================================================

After the 7210 SAS device boots up, the following login prompt is displayed.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 22:44:35 IST 2011 by builder in /builder/3.0B5/R4/panos/main
Login:

At the prompt, enter admin for the default username and password, and log into the 7210 SAS device.

Note:
The Sys LED is green when the device has successfully completed the boot process and is running normally.

Procedure to boot when the BOF is present locally

This section describes the procedure to boot the 7210 SAS after a reboot, when the BOF and image files are present locally, or when the node is shipped from factory with a BOF and an image on the flash.

See Contents shipped with the system on 7210 SAS for a list of factory-shipped contents for each 7210 SAS device.

Execute a reboot of the 7210 SAS device. The system starts booting and the following console output is displayed.

Resetting...OK

Nokia 7xxx Boot ROM. Copyright 2000-2020 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-20.3.B1-1 on Wed Feb 12 15:29:52 IST 2020 by sasbuild
Version: 0x38
Processor core is CN66xx
COLD boot on processor #1
?Preparing for jump to RAM...
Starting bootrom RAM code...
Boot rom version is v56
CPU #1 booted from working sector
CPU Control FPGA version is 0x3D
FPGA A version is 0x3D. FPGA B version is 0x3D. FPGA C version is 0x3D.
Restart type = 0x01
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000
Power on Diagnostics passed
Board Serial Number is 'NS1715T0019'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-V-20.3.B1-1 bootrom/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:28:49 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/m

Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Cannot open "cf1:/boot.tim".
Attempting to load file cf2:/boot.tim
Cannot open "cf2:/boot.tim".
Attempting to load file uf1:/boot.tim
Version L-20.3.B1-1, Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(13818400-->40990080) + data:(3162656-->19580220)
Starting at 0x18000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-L-20.3.B1-1 boot/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:31:09 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/
main

TiMOS BOOT LOADER
Time from clock is WED MAR 04 11:18:16 2020 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : standalone

Looking for uf1:/bof.cfg ... OK, reading

The system locates the BOF on a local drive. The system reads the contents of the BOF and displays it on the console.

The following console output is displayed.

Contents of Boot Options File on uf1:
    primary-image      uf1:\both.tim
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/67
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      100000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/68
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      100000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled

Hit a key within 1 second to change boot parameters...

At the prompt, wait until the specified wait time has elapsed. The boot process can be interrupted at the prompt if necessary to change the boot parameters (for example, the image location). In this example, it is assumed that changes to the BOF are not required.

The following console output is displayed.

Configuring Network with uplinkA Port Setting.....
No existing config file URL

Primary image location: uf1:\both.tim
Loading image uf1:\both.tim
Version B-20.3.B1-1, Wed Feb 12 15:33:08 IST 2020 by sasbuild in /home/sasbuild/
20.3B1/panos/main
text:(41664192-->183719312) + data:(7133216-->49945144)
Executing TiMOS image at 0x2800000

The system loads the TiMOS image and the 7210 SAS device boots up. The following console output is displayed.

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x43
TiMOS-B-20.3.B1-1 both/hops Nokia SAS-Sx 64SFP+4QSFP28 7210 Copyright (c) 2000-
2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 12 15:33:08 IST 2020 by sasbuild in /home/sasbuild/20.3B1/panos/
main
Running 32 bit architecture
Time from clock is WED MAR 04 11:19:24 2020 UTC
Login:

At the prompt, enter admin for the default username and password, and log in to the 7210 SAS device.

Procedure to boot in the satellite mode

Note:

See Supported modes of operation and configuration methods for the list of 7210 SAS platforms that support the satellite mode of operation.

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 information about the satellite mode on 7210 SAS devices.

See the specific 7210 SAS chassis installation guide for more information about prerequisites to boot the system in the satellite mode of operation.

Perform the following steps to boot the 7210 SAS device in the satellite mode of operation.

Configure the 7750 SR host with the 7210 SAS both.tim image location (the software repository).
1. Create the software repository to store the images by using the software-repository command:
```
*A:dut-h# configure system software-repository ‟7210-SAS-Sx-9.0R7-Images” create
```
2. Provide a description for the software repository by using the description command:
```
*A:dut-h>config>system>sw-repos# description "7210-SAS-Sx-Release-9.0R7-Images"
```
3. Manually copy the boot.tim and both.tim files to the repository created in step 1.a.
  
  Do not copy the files to a sub-folder in the repository.
4. Configure the location of the 7210 SAS both.tim and boot.tim by using the primary-location command:
```
*A:dut-h>config>system>sw-repos# primary-location "cf1:/7210-SAS-Sx-9.0R7/images/"
```
5. From the config>system>software-repository context, issue the info command to verify the configuration of the image location. The following output is displayed.
```
*A:dut-h>config>system>sw-repos# info   
---------------------------------------------------------------
            description "7210-SAS-Sx-Release-9.0R7-Images"
            primary-location "cf1:/7210-SAS-Sx-9.0R7/images/"
---------------------------------------------------------------
*A:dut-h>config>system>sw-repos#
```
Configure the Ethernet satellite on the 7750 SR host.
See Uplink ports used for 7210 SAS platforms and variants in satellite mode for information about uplink ports used on 7210 SAS platforms operating in the satellite mode.
Note:
In this example, the 7210 SAS device is identified by satellite ID 1 and its type is set to es64-10gb-sfpp+4-100gb-qsfp28. The satellite identifier (that is, esat-1, in this example) is used to refer to the entire satellite node when configuring services on the 7750 SR host.
1. Configure the Ethernet satellite with ID 1 by using the eth-sat command:
```
*A:dut-h#configure system satellite eth-sat 1 create
```
2. Configure the Ethernet satellite description by using the description command:
```
A:dut-h>config>system>eth-sat# description ‟Ethernet Satellite 1”
```
3. Configure the 7210 SAS device MAC address connected to the 7750 SR host by using the mac-address command:
```
A:dut-h>config>system>eth-sat#mac-address a4:7b:2c:13:bc:48
```
  The MAC address is used by the 7750 SR host to provide the correct configuration to the system. If the MAC address is not configured, the 7750 SR host will not respond to DHCP requests from the system.
4. Configure the software repository by using the software-repository command:
```
*A:dut-h>config>system>eth-sat# software-repository ‟7210-SAS-Sx-9.0R7-Images”
```
  The software repository provides the system with the correct image (both.tim). The software repository name must match the software repository created in step 1.
5. Configure the satellite type by using the sat-type command:
```
*A:dut-h>config>system>eth-sat# sat-type es64-10gb-sfpp+4-100gb-qsfp28
```
  The satellite type allows the 7750 SR host to correctly initialize the satellite and set up the appropriate resources on the 7750 SR host to manage the satellite.
6. From the config>system>eth-sat context, issue the info CLI command to verify the configuration of the Ethernet satellite. The following output is displayed.
```
*A:dut-h>config>system>eth-sat# info 
----------------------------------------------
                shutdown
                description ‟ESat1OnPort1/1/1"
                mac-address a4:7b:2c:13:bc:48
                software-repository "7210-SAS-Sx-9.0R7-Images"
----------------------------------------------
*A:dut-h>config>system>eth-sat#
```
7. From the config>system>eth-sat context, issue the no shutdown command:
```
*A:dut-h>config>system>eth-sat# no shutdown
```
8. On the 7750 host, for a 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant, configure the breakout connection on esat-1/1/c65 (and any other uplink ports) by using the config>port>esat-1/1/c65/1>connector>breakout c1-100g command.
9. Power on the satellite.

On the 7750 SR host, configure the port connected to the 7210 SAS device:

Note: 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 more information about port numbers for the 7210 SAS-Sx 10/100GE operating in satellite mode.

On the 7750 SR host, configure the port to which the satellite is connected by using the port command:
```
*A:dut-h# configure system port-topology port 1/1/1 to esat-1/1/c65/u1 create
```

Issue the show system port-topology command to display the 7750 SR host ports associated with the Ethernet satellite ports. The following output is displayed.

*A:dut-h# show system port-topology 
===============================================================================
Port Topology
===============================================================================
Port              Far-end
Id                Port Id
-------------------------------------------------------------------------------
esat-1/1/c65/u1   1/1/1
-------------------------------------------------------------------------------
No. of Number of port-topology associations: 1
===============================================================================

Issue the show system satellite command to display the status of the satellite. The following output is displayed.

*A:dut-h# show system satellite 
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-1    es64-10gb-sfpp+4-100gb-qsfp28            up            provisioned
              (not equipped)                       
-------------------------------------------------------------------------------
No. of Satellites: 1
===============================================================================
*A:dut-h#

Power on the Ethernet satellite:

Power on the 7210 SAS device.

The satellite will use the bootloader on the SD card inserted in cf2:\ (SD card slot on the rear of the chassis) and initiate the boot procedure.

The 7210 SAS device sends DHCP requests out of its uplink ports.

The 7750 SR host uses the MAC address in the received packets and matches it against MAC addresses provided in the Ethernet satellite configuration on the 7750 SR host.

After finding a match, the 7750 SR host uses the configured image and an appropriate configuration file, generates a BOF, and sends it to the system (the host-type parameter in the BOF generated by the 7750 SR host is set to satellite).

The 7210 SAS boot loader uses the BOF to retrieve the images and the configuration file, and uses them to boot the platform in the satellite mode (because the host-type is set to satellite).

The satellite transitions through the following states: provisioned, booting, and up.

Issue the show system satellite command to determine the boot status of the satellite. The following output is displayed.

*A:dut-h# show system satellite 
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-1    es64-10gb-sfpp+4-100gb-qsfp28            up            provisioned
              (not equipped)                       
-------------------------------------------------------------------------------
No. of Satellites: 1
===============================================================================
*A:dut-h#
*A:dut-h# show system satellite       
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-1    es64-10gb-sfpp+4-100gb-qsfp28            up            booting
-------------------------------------------------------------------------------
No. of Satellites: 1
===============================================================================
*A:dut-h# show system satellite 
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-1    es64-10gb-sfpp+4-100gb-qsfp28            up            booting
-------------------------------------------------------------------------------
No. of Satellites: 1
===============================================================================
*A:dut-h# show system satellite 
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-1    es64-10gb-sfpp+4-100gb-qsfp28            up            up
-------------------------------------------------------------------------------
No. of Satellites: 1
===============================================================================

After the device has booted successfully, issue the show system satellite eth-sat command on the 7750 SR host to display detailed information about the 7210 SAS device connected in satellite mode.

The following output is displayed.

*A:SR7# show system satellite eth-sat 15 
===============================================================================
Satellite Information
===============================================================================
SatID     Provisioned Type                         Admin         Oper
              Equipped Type (if different)         State         State
-------------------------------------------------------------------------------
esat-15   es64-10gb-sfpp+4-100gb-qsfp28            up            up
Description         : SASSx Mariner 100G QSFP28
MAC Address         : d0:99:d5:a6:34:41
Software Repository : SASS-HW64
SyncE               : Enabled
PTP-TC              : Disabled
Client-Down-Delay   : Disabled
Console Access      : Enabled
Hardware Data
    Platform type                 : N/A
    Part number                   : 3HE11597AARA01
    CLEI code                     : INM3110ARA
    Serial number                 : NS1734T0028
    Manufacture date              : 09182017
    Manufacturing deviations      : (Not Specified)
    Manufacturing assembly number : 
    Administrative state          : up
    Operational state             : up
    Temperature                   : 48C
    Temperature threshold         : 85C
    Software boot (rom) version   : X-11.0.R4 on Wed Jul 10 13:44:15 IST 2019
                                    by sasbuild
    Software version              : TiMOS-B-20.3.B1-3 both/hops Nokia SAS-Sx
                                    64SFP+4QSFP28 7210 Copyright (c) 2000-2020
                                    Nokia.
                                    All rights reserved. All use subject to
                                    applicable license agreements.
                                    Built on Fri Mar 20 16:50:24 IST 2020 by
                                    sasbuild in /home/sasbuild/20.3B1/panos/ma
    Time of last boot             : 2019/11/14 13:16:39
    Current alarm state           : alarm cleared
    Base MAC address              : d0:99:d5:a6:34:41

Procedure to boot in the standalone-VC mode

Note:

This procedure is only supported on the 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and their variants.
See Provisioning and booting up the VC in standalone mode for more information.

Perform the following steps to boot the 7210 SAS device in the standalone-VC mode of operation:

Power on the 7210 SAS device.

Use the OOB Ethernet management port to boot form the network.

A:NS1722T0086# admin reboot now 

Resetting...OK

Nokia SAS-S 7210 Boot ROM. Copyright 2000-2018 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-11.0.B1-6 on Thu Dec 6 15:22:31 IST 2018 by sasbuild
Version: 0x1F

DRAM test first stage
?Boot rom version is v31
CPLD Version: 0x0C
Board Serial Number is 'NS1722T0086'
DRAM test second stage
>>>Testing  SDRAM from 0x0000000002200000 to 0x0000000080000000
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000

Loading VxRom image .......

Board Serial Number is 'NS1722T0086'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x14
TiMOS-V-11.0.B1-6 bootrom/hops Nokia SAS-S 24T4SFP+ 7210 Copyright (c) 2000-
2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Dec 6 15:21:48 IST 2018 by sasbuild in /home/sasbuild/11.0B1/panos/main

Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Version L-11.0.B1-21, Wed Feb 27 12:30:02 IST 2019 by sasbuild in /home/sasbuild/
11.0B1/panos/main
text:(13790784-->40910320) + data:(3160736-->19576100)
Starting at 0x18000000...

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x14
TiMOS-L-11.0.B1-21 boot/hops Nokia SAS-S 24T4SFP+ 7210 Copyright (c) 2000-
2019 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Feb 27 12:30:02 IST 2019 by sasbuild in /home/sasbuild/11.0B1/panos/
main

TiMOS BOOT LOADER
Time from clock is SAT JAN 01 00:15:24 2000 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : standalone

The system lists the default settings and the following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading

Contents of Boot Options File on cf1:
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/27
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      10000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled

Hit a key within 3 seconds to change boot parameters...

At the prompt, press any key to initiate boot parameter updates.

The following console output is displayed.

Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt

Waiting for 30 seconds to enter password
Password:

At the prompt, enter the default password password, and initiate the BOF edit.

The system accepts the password and the following console output is displayed.

You must supply some required Boot Options. At any prompt, you can type:
"restart" - restart the query mode.
"reboot" - reboot.
"exit" - boot with with existing values.
"diag" - enter the diag shell.
"reset" - reset the bof and reboot.

Press ENTER to begin, or 'flash' to enter firmware update...

At the prompt, press Enter to edit the BOF. The following console output is displayed.

Chassis-Role
-------------
Current chassis-role is : standalone
You can change it to { satellite | standalone-vc | factory-default }.
Press ENTER to continue OR "edit" to change the chassis-role : standalone-vc
Press "edit" to change OR ENTER to continue :

At the prompt, enter edit. The following console output is displayed.

Enter the new chassis-role { satellite | standalone-vc | factory-
default } :

At the prompt, enter standalone-vc for the chassis-role. The following output is displayed.
```
Are you sure you want to set the chassis-role as standalone-vc? (yes/no) :
```

At the prompt, enter yes. The following console output is displayed.

Looking for cf1:/bof.cfg ... OK, reading
Contents of Boot Options File on cf1:
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    vc-stack-node-type imm-only

Hit a key within 2 seconds to change boot parameters...

At the prompt, press any key to initiate boot parameter updates.

The following console output is displayed.

Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt

Waiting for 30 seconds to enter password
Password:

At the prompt, enter the default password password, and initiate the BOF edit.

The system accepts the password and the following console output is displayed.

You must supply some required Boot Options. At any prompt, you can type:
"restart" - restart the query mode.
"reboot" - reboot.
"exit" - boot with with existing values.
"diag" - enter the diag shell.
"reset" - reset the bof and reboot.

Press ENTER to begin, or 'flash' to enter firmware update...

At the prompt, press Enter to edit the BOF. The following console output is displayed.

Chassis-Role
-------------
Current chassis-role is : standalone-vc
you can change it to { satellite | standalone | factory-default }.
Press ENTER to continue OR "edit" to change the chassis-role : standalone
Press "edit" to change OR ENTER to continue :

At the prompt, press Enter. The following output is displayed.

Chassis-role is set to standalone-vc, Do you wish to continue with this (yes/
no) :

At the prompt, enter yes. The following console output is displayed.

VC Stack Node Type
--------------------
Current Vc Stack Node type of this card is : imm-only
Press ENTER to retain this,
 or { cpm-imm } to change it to cpm-imm :

At the prompt, enter cpm-imm. The following output is displayed.

Setting the Card role to 'cpm-imm'.

VC Stack Name
-------------
Current VC Stack Name in Bof is : 
Enter the VC Stack name (max 32 characters) you wish to use : VC123

At the prompt, enter the name of the VC stack. The following output is displayed.

Changing the VC Stack Name to VC123
Setting the VC name to 'VC123'.
Mac Address of this node is d0:99:d5:9a:6a:41

vc-stack-node field of First cpm-imm Node (cpmA)
------------------------------------------------
   You must enter the VC Stack Slot Num that you intend to use 
   and the node's mac address seperated by a space.

Example, to use slot-num '1' and mac address 'aa:bb:cc:dd:ee:ff'
Type - '1 aa:bb:cc:dd:ee:ff'

Accepted VC Stack Slot Num values are - [1 to 8]
The existing vc-stack-node and mac field in bof is 'none'

vc-stack-node entry of cpmA [1 to 8] [mac address] : 1 d0:99:d5:9a:6a:41

At the prompt, enter the VC stack slot number and MAC address for CPM-A. The following output is displayed.

Using 1 as Vc Stack Slot Id of Node with mac d0:99:d5:9a:6a:41

VC Stack Slot Num of Second cpm-imm Node (cpmB)
-----------------------------------------------
   You must enter the VC Stack Slot Num that you intend to use.
   type 'none' if you do not have the details of second cpm-imm node.

Accepted VC Stack Slot num values are - [1 to 8]
The existing vc-stack-node and mac field in bof is 'none'

vc-stack-node entry of cpmB [1 to 8] [mac address] :

At the prompt, enter the VC stack slot number and MAC address for CPM-B. The following output is displayed.

Using 2 as Vc Stack Slot Id of Node with mac d0:99:d5:94:de:41

Software Location
-----------------
   You must enter the URL of the TiMOS software.
   The location can be on a Compact Flash device,
   a USB flash drive, or on the network.

   Here are some examples
      cf1:/timos1.0R1
      uf1:/timos1.0R1
      ftp://user:passwd@192.168.1.150/./timos1.0R1
      ftp://user:passwd@[3FFE::1]/./timos1.0R1

or Type 'auto' to retrieve BOF configuration through DHCP.

Software Image URL:

At the prompt, enter the URL location of the software image; for example, ftp://<user>:<password>@10.10.170.22/./images/both.tim.

The following console output is displayed.

Configuration File Location
---------------------------
   You must enter the location of configuration
   file to be used by TiMOS.  The file can be on
   a Compact Flash device, a USB flash drive, or
   on the network.

   Here are some examples
      uf1:/config.cfg
      cf1:/config.cfg
      ftp://user:passwd@192.168.1.150/./config.cfg
      ftp://user:passwd@[3FFE::1]/./config.cfg
      tftp://192.168.1.150/./config.cfg
      tftp://[3FFE::1]/./config.cfg

Config File URL:

At the prompt, enter the URL location of the configuration file. The following console output is displayed.

Network Configuration
---------------------

Boot Interface Management
-------------------------
   You specified a network location for either the 
   software or the configuration file. You need to 
   configure either eth-mgmt or uplinkA or uplinkB ports.
   You will be asked to configure the port number, IP(v6) address,
   static routes, and VLAN Id in case of uplink ports.

Existing eth-mgmt port settings are:

   eth-mgmt-port        
   eth-mgmt-address    0 active
   eth-mgmt-address    0 standby
   eth-mgmt-address    0 active
   eth-mgmt-address    0 standby

   eth-mgmt port is configured for Boot Interface Management,
   Press ENTER to proceed with existing port settings
   Or "disable" to disable the port for Boot Interface Management
   Or "edit" to change the port settings:

At the prompt, enter edit. The following output is displayed.

   You need to assign an IP address for this port.
   The IP address should be entered in standard
   dotted-decimal form with a network length.
   example:   192.168.1.169/24

Enter eth-mgmt Active IP Address :

At the prompt, enter the active port IP address and mask that the device should use (for example, 10.135.4.172/10). The following console output is displayed.

   In case of an IPv6, the IPv6 address should be
   entered in standard colon hexadecimal notation
   with a prefix length.
       example:   3FFE::1/112

Enter eth-mgmt Active IPv6 Address (Type 0 if none desired):

At the prompt, enter 0. The following console output is displayed.
```
Enter eth-mgmt Standby IP Address (Type 0 if none desired):
```

At the prompt, enter the standby port IP address and mask that the device should use. The following output is displayed.

   In case of an IPv6, the IPv6 address should be
   entered in standard colon hexadecimal notation
   with a prefix length.
       example:   3FFE::1/112

Enter eth-mgmt Standby IPv6 Address (Type 0 if none desired):

At the prompt, enter 0. The following output is displayed.

   You specified network locations which might require
   static routes to reach. You will be asked to
   enter static routes until all the locations become
   reachable.
   Static routes should be entered in the following format:
   prefix/mask next-hop ip-address
   example:     192.168.0.0/16 next-hop 192.168.1.254

Would you like to add a static route? (yes/no)

At the prompt, enter yes. The following output is displayed.
```
Enter ip route:
```
At the prompt, enter the static IP route. The following output is displayed.
```
OK

Would you like to add another static route? (yes/no)
```
At the prompt, enter no. The following output is displayed.
```
Would you like to add another static IPv6 route? (yes/no)
```

At the prompt, enter no. The following console output is displayed.

Current configuration enables use of console (setting is "no console-disabled")
Press ENTER to proceed with existing setting  or 'disable' to disable console access
:

At the prompt, press Enter. The following console output is displayed.

New Settings
------------
    primary-image      ftp://*:*@10.135.24.85/./img/sass/both.tim
    primary-config     ftp://*:*@10.135.24.85/./cfg/sass/dutE_vcCfg.txt
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   10.135.24.94/24 active
    eth-mgmt-address   10.135.24.95/24 standby
    eth-mgmt-route     135.0.0.0/8 next-hop 10.135.24.1
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    vc-stack-name      VC123
    vc-stack-node-type cpm-imm
    vc-stack-node cpmA slot-num 1 mac-addr d0:99:d5:9a:6a:41
    vc-stack-node cpmB slot-num 2 mac-addr d0:99:d5:94:de:41

Do you want to overwrite cf1:/bof.cfg with the new settings? (yes/no):

At the prompt, enter yes. The 7210 SAS device begins to boot with the new settings. The following console output is displayed.

Successfully saved the new settings in cf1:/bof.cfg

******************* VC Mode ********************
Configuring Network with eth-mgmt Port Setting.....
Primary config file location: ftp://*:*@10.135.24.85/./cfg/sass/dutE_vcCfg.txt
Initial DNS resolving preference is ipv4-only
Downloading 'ftp://*:*@10.135.24.85/./cfg/sass/dutE_vcCfg.txt'...OK

Sap Index file location: ftp://*:*@10.135.24.85/./cfg/sass/dutE_vcCfg.sdx
Downloading 'ftp://*:*@10.135.24.85/./cfg/sass/dutE_vcCfg.sdx'...OK

Primary image location: ftp://*:*@10.135.24.85/./img/sass/both.tim
Initial DNS resolving preference is ipv4-only
Loading image ftp://*:*@10.135.24.85/./img/sass/both.tim
Version B-11.0.S127b, Tue May  7 04:46:24 IST 2019 by sasbuild in /home/sasbuild/
11.0S/panos/main
text:(41482848-->183530192) + data:(7134144-->49884044)
Executing TiMOS image at 0x2800000

After the 7210 SAS device boots up, the following login prompt is displayed.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 14:32:04 IST 2011 by builder in /builder/3.0B5/panos/main
Login:

At the prompt, enter admin for the default username and password, and log into the 7210 SAS device.

Procedure to boot in standalone-VC mode for factory-default units using an SD card

Note:

This procedure is only supported on the 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and their variants.
See Provisioning and booting up the VC in standalone mode for more information.

Perform the following steps to boot the 7210 SAS factory-default units in the standalone-VC mode of operation using an SD card:

Prepare the SD card for the CPM-IMM and IMM-only nodes. The bof.cfg file must be edited offline and stored on the SD card. The following output provides the minimum configuration for CPM-IMM and IMM-only nodes. A separate SD card must be used for each node in the VC, with each card containing an appropriate bof.cfg file based on the role of the node (CPM-IMM or IMM-only) in the VC.
1. Prepare the SD card for the CPM-A node.
  The following sample displays the minimum bof.cfg file configuration required for the CPM-IMM CPM-A node (whose chassis MAC address matches the value specified for CPM-A below).
```
-------------------------------------------------------------
   primary-image      cf2:/both.tim
    primary-config     cf2:/dut-a.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   192.168.7.1/24 active
    eth-mgmt-address   192.168.7.2/24 standby
    eth-mgmt-route     192.168.0.0/16 next-hop 192.168.7.8
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    host-type          standalone-vc
    vc-stack-name      rev3hcs
    vc-stack-node-type cpm-imm
    vc-stack-node cpmA slot-num 1 mac-addr 8c:f7:73:89:4a:b5
    vc-stack-node cpmB slot-num 2 mac-addr 8c:f7:73:fb:cd:a2
------------------------------------------------------------------------------
```
2. Prepare the SD card for the CPM-B node. The following output displays the minimum configuration required for bof.cfg for the CPM-IMM CPM-B node (whose chassis MAC address matches the value specified for CPM-B below).
```
---------------------------------------------------------------------------
    primary-image      cf2:/both.tim
    primary-config     cf2:/dut-a.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   192.168.7.1/24 active
    eth-mgmt-address   192.168.7.2/24 standby
    eth-mgmt-route     192.168.0.0/16 next-hop 192.168.7.8
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    host-type          standalone-vc
    vc-stack-name      rev3hcs
    vc-stack-node-type cpm-imm
    vc-stack-node cpmA slot-num 1 mac-addr 8c:f7:73:fb:cd:a2
    vc-stack-node cpmB slot-num 2 mac-addr 8c:f7:73:89:4a:b5
------------------------------------------------------------------------------
```
  Note:
  Change the OOB management IP address and IP route values appropriately to match their network addressing scheme. Additionally, change the MAC address of the CPM-A and CPM-B nodes to match the chassis MAC address of the nodes used (the chassis MAC address can be obtained from the node and is typically available on the label pasted on the back plate of the node).
  
  Label the SD card for quick identification of the SD card with the CPM-IMM and IMM-only node BOF file. The BOF cannot be interchanged. For example, the CPM-IMM BOf file configured with a specific MAC address must be used on the platform whose MAC address matches the configured MAC address in the BOF. Additionally, the CPM-IMM BOF file cannot be used to boot an IMM-only node, or an IMM-only node be used to boot a CPM-IMM node. The node does not boot up in standalone-VC mode correctly if the SD cards are interchanged.
3. Prepare the SD card for the IMM-only node.
  
  Note:
  The IMM-only node gathers image files and configurations from the CPM-IMM CPM-A node of the VC. Therefore, users do not need to provide the image location and management IP configuration in the bof.cfg file for an IMM-only node.
  
  The following output displays the minimum configuration required for bof.cfg file for an IMM-only node.
```
-------------------------------------------------------------
#eth-mgmt Port Settings:
no  eth-mgmt-disabled
eth-mgmt-autoneg
eth-mgmt-duplex    full
eth-mgmt-speed     100
#System Settings:
wait               3
persist            off
console-speed      115200
no  console-disabled
host-type          standalone-vc
vc-stack-node-type imm-only
-------------------------------------------------------------
```
Insert the SD card into the SD card slot of the chassis. Ensure the SD cards are used with the correct nodes based on the role of the node.
Power on the 7210 SAS system.

Note:
It is recommended to start with the CPM-IMM CPM-A node first, and then power on all other 7210 SAS nodes in the VC.

If a console is attached, the following boot logs are displayed for the CPM-IMM nodes. Further user input is not required during the boot process and users can ignore the displayed prompts.

--------------------------------------------------------------------------------------

Boot log started on CPU#0
  Build: X-23.9.S76b on Wed Sep 11 23:01:33 IST 2024 by sasbuild
Boot rom version is v32
CPLD Version: 0x07
Board Serial Number is 'NS1823C2814'
DRAM test second stage
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000

Loading VxRom image .......

Board Serial Number is 'NS1823C2814'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x51
TiMOS-V-23.9.S76b bootrom/hops Nokia SAS-Sx 46F2C4SFP+ 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 11 23:00:43 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/mai



Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Cannot open "cf1:/boot.tim".
Attempting to load file cf2:/boot.tim
Version L-24.9.S10b, Sat Aug 24 01:04:23 IST 2024 by sasbuild in /home/sasbuild/24.9S/panos/main
text:(16745312-->53543216) + data:(4041600-->25378272)
Starting at 0x18000000...




Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x51
TiMOS-L-24.9.S10b boot/hops Nokia SAS-Sx 46F2C4SFP+ 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Sat Aug 24 01:04:23 IST 2024 by sasbuild in /home/sasbuild/24.9S/panos/main

TiMOS BOOT LOADER
Time from clock is MON SEP 16 10:22:36 2024 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : factory-default

Looking for cf2:/bof.cfg ... OK, reading
Setting the chassis role to standalone-vc.

Contents of Boot Options File on cf2:
    primary-image      cf2:/both.tim
    primary-config     cf2:/dut-a.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   192.168.7.1/24 active
    eth-mgmt-address   192.168.7.2/24 standby
    eth-mgmt-route     135.250.0.0/16 next-hop 192.168.7.8
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    host-type          standalone-vc
    vc-stack-name      rev3hcs
    vc-stack-node-type cpm-imm
    vc-stack-node cpmA slot-num 1 mac-addr 8c:f7:73:89:4a:b5
    vc-stack-node cpmB slot-num 2 mac-addr 8c:f7:73:fb:cd:a2

Hit a key within 3 seconds to change boot parameters...   Hit a key within 2 seconds 
to change boot parameters...   Hit a key within 1 second to change boot parameters...   

******************* VC Mode ********************
CPM-IMM Vc Node, Stack name - rev3hcs, VC Slot - 1, Mate VC Slot - 2



Configuring Network with eth-mgmt Port Setting.....
Primary config file present at: cf2:/dut-a.cfg
Sap Index file present at: cf2:/dut-a.sdx

Primary image location: cf2:/both.tim
Loading image cf2:\both.tim
Version B-23.9.S76b, Wed Sep 11 23:15:10 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/main
text:(43035584-->195820304) + data:(7693280-->56580708)
Executing TiMOS image at 0x2800000



Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x51
TiMOS-B-23.9.S76b both/hops Nokia SAS-Sx 46F2C4SFP+ 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 11 23:15:10 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/main


   ___                    ___           ___           ___
  /\  \                  /\__\         /\  \         /\  \
  \:\  \        ___     /::|  |       /::\  \       /::\  \
   \:\  \      /\__\   /:|:|  |      /:/\:\  \     /:/\:\  \
   /::\  \    _\/__/  /:/|:|__|__   /:/  \:\  \   _\:\~\:\  \
  /:/\:\__\  /\__\   /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \:\__\
/:/  \/__/ /:/  /   \/__/~~/:/  / \:\  \ /:/  / \:\ \:\ \/__/
/:/  /     /:/  /          /:/  /   \:\  /:/  /   \:\ \:\__\
\/__/      \/__/          /:/  /     \:\/:/  /     \:\/:/  /
                         /:/  /       \::/  /       \::/  /
                         \/__/         \/__/         \/__/

Running 32 bit architecture
hwDetectVCSlot: Setting STARTUP-->hwChassisType to SAS_VC
Time from clock is MON SEP 16 10:24:18 2024 UTC
******************* VC Mode ********************
CPM-IMM Vc Node, Stack name - rev3hcs, VC Slot - 1, Mate VC Slot - 2
Initial DNS resolving preference is ipv4-only
lldpInit done
opensslInit usrSsecureInit done

Attempting to exec primary configuration file:
   'cf2:\dut-a.cfg' ...
System Configuration
System Security Configuration

--------------------------------------------------------------------------------------

The following login prompt is displayed after the 7210 SAS device boots up.

All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 20 14:32:04 IST 2011 by builder in /builder/3.0B5/panos/main
Login:

At the prompt, enter admin for the default username and password, and log into the 7210 SAS device.

The following boot logs are displayed for the IMM-only nodes if a console is attached. Further user input is not required during the boot process and users can ignore the displayed prompts. Users are not required to log into IMM-only nodes.

----------------------------------------------------------------------------

Nokia SAS-S 7210 Boot ROM. Copyright 2000-2024 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Build: X-23.9.S76b on Wed Sep 11 23:01:33 IST 2024 by sasbuild
Version: 0x20

DRAM test first stage
?Boot rom version is v32
CPLD Version: 0x0C
Board Serial Number is 'NS1815T0033'
DRAM test second stage
>>>Validate SDRAM from 0x000000007fdfff80 to 0x0000000080000000 (decrementing)
>>>Testing  SDRAM from 0x0000000002200000 to 0x000000007fdfff80
>>>Testing  SDRAM from 0xffffffffe0000000 to 0xffffffffe2000000

Loading VxRom image .......

Board Serial Number is 'NS1815T0033'

Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x14
TiMOS-V-23.9.S76b bootrom/hops Nokia SAS-S 48Tp4SFP+ (PoE) 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 11 23:00:43 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos



Searching for boot.tim on local drives:
Attempting to load file cf1:/boot.tim
Cannot open "cf1:/boot.tim".
Attempting to load file cf2:/boot.tim
Version L-23.9.S76b, Wed Sep 11 23:04:29 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/main
text:(16716608-->53455904) + data:(4039648-->25376640)
Starting at 0x18000000...




Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x14
TiMOS-L-23.9.S76b boot/hops Nokia SAS-S 48Tp4SFP+ (PoE) 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 11 23:04:29 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/ma

TiMOS BOOT LOADER
Time from clock is MON SEP 16 10:22:33 2024 UTC
Switching serial output to sync mode...   done
Chassis-role is set to : factory-default

Looking for cf2:/bof.cfg ... OK, reading
Setting the chassis role to standalone-vc.

Contents of Boot Options File on cf2:
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    host-type          standalone-vc
    vc-stack-node-type imm-only

Hit a key within 3 seconds to change boot parameters...   Hit a key 
within 2 seconds to change boot parameters...   Hit a key within 1 second to change boot parameters...   

******************* VC Mode ********************
Proceeding as IMM Only VC Node.

Setting vc Slot id to 3. 
vchmSetVCSlot/596: MY_VCINFO_SLOT=31->3

Waiting for card to be provisioned...
Active 31 is Unreachable. Waiting...
Active CPM 9 is *NOT* reachable...

Primary image location: ftp://*:*@127.1.0.9/VC:rev3hcs/p/
Loading image ftp://*:*@127.1.0.9/VC:rev3hcs/p/both.tim/both.tim
Version B-23.9.S76b, Wed Sep 11 23:15:10 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/main
text:(43035584-->195820304) + data:(7693280-->56580708)
Executing TiMOS image at 0x2800000



Total Memory: 2GB  Chassis Type: 0xa  Card Type: 0x14
TiMOS-B-23.9.S76b both/hops Nokia SAS-S 48Tp4SFP+ (PoE) 7210 Copyright (c) 2000-2024 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 11 23:15:10 IST 2024 by sasbuild in /home/sasbuild/23.9S/panos/ma


   ___                    ___           ___           ___
  /\  \                  /\__\         /\  \         /\  \
  \:\  \        ___     /::|  |       /::\  \       /::\  \
   \:\  \      /\__\   /:|:|  |      /:/\:\  \     /:/\:\  \
   /::\  \    _\/__/  /:/|:|__|__   /:/  \:\  \   _\:\~\:\  \
  /:/\:\__\  /\__\   /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \:\__\
/:/  \/__/ /:/  /   \/__/~~/:/  / \:\  \ /:/  / \:\ \:\ \/__/
/:/  /     /:/  /          /:/  /   \:\  /:/  /   \:\ \:\__\
\/__/      \/__/          /:/  /     \:\/:/  /     \:\/:/  /
                         /:/  /       \::/  /       \::/  /
                         \/__/         \/__/         \/__/


Running 32 bit architecture
hwDetectVCSlot: Setting STARTUP-->hwChassisType to SAS_VC
Time from clock is MON SEP 16 10:27:35 2024 UTC
******************* VC Mode ********************
Proceeding as IMM Only VC Node.
lldpInit done



------------------------------------------------------------------------------