7.1. 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:

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.

7.2. 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:

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:

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

The 7210 SAS-M and 7210 SAS-D are factory-shipped with a TiMOS image (both.tim) on the internal flash.

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: Refer to 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.

1. Connect the 7210 SAS console port to the serial port of the PC, and power up 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+4CFP4 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+4CFP4 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
2. 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...
3. 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:
4. 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...
5. 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) :
6. 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:
7. 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:
8. 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:
9. 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):
10. 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
11. 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:
12. 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.

7.2.2. 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: Refer to 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.

1. Power on the 7210 SAS device.
2. 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
3. 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...
4. 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:
5. 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...
6. 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:
7. 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:
8. 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:
9. 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:
10. 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:
11. 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:
12. At the prompt, perform one of the following.
    1. Enter null to send out packets without VLAN tags.
    2. 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):
13. At the prompt, enter the port IP address and mask that the device should use (for example, 10.135.4.172/10).
14. 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)
15. At the prompt, type yes and press Enter to add a static route.
    Enter route:
16. 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:
17. 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:
18. 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):
19. 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
20. 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:
21. 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.

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

1. Power on the 7210 SAS device.
2. 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+4CFP4 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+4CFP4 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
3. 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... 
4. 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:
5. 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...
6. 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) :
7. 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:
8. 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:
9. 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:
10. 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):
11. 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):
12. 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)
13. At the prompt, enter no. The following console output is displayed.
    Enter route to Primary Image at 192.254.173.3:
14. 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)
15. 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
16. 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)
17. At the prompt, enter yes. The following console output is displayed.
    Enter ip route:
18. 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)
19. At the prompt, enter no. The following console output is displayed.
    Would you like to add another static IPv6 route?
20. 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:
21. 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:
22. 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:
23. 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):
24. 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

    ==================================================
25. 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:
26. 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.

7.3. 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 Table 20 for a list of factory-shipped contents for each 7210 SAS device.

7.4. Procedure to Boot in the Satellite Mode

Note: See Table 1 for the list of 7210 SAS platforms that support the satellite mode of operation. See System Boot Options for 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp in Satellite Mode for information about the satellite mode on 7210 SAS devices.

Refer to 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.