Procedure to boot using auto-init mode

About this task

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:

Procedure

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

    Example
    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+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 WED MAR 04 09:23:22 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.
    Example
    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...
    
  3. 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.

    Example
    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
    
  4. 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
    
  5. 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.

    Example
    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)
    
  6. After the 7210 SAS device boots up, the following login prompt is displayed.
    Example
    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:
    
  7. At the prompt, enter admin for the default username and password, and log in to the 7210 SAS device.