4.11. Configuring boot file options with CLI

This section provides information to configure BOF parameters with CLI.

4.11.1. BOF configuration overview

Nokia routers do not contain a boot EEPROM. The bootstrap image is loaded from the boot.tim file. The BOF performs the following tasks:

  1. sets up the uplink ports or the Ethernet management port (speed, duplex, auto) (only on platforms that support the Ethernet management port)
  2. assigns the IP address (either statically or using DHCP) for the uplink/Ethernet management port
  3. assigns the VLAN to the uplink port
  4. creates static routes to provide network connectivity
  5. sets the console port speed
  6. configures the Domain Name System (DNS) name and DNS servers
  7. configures the primary, secondary, tertiary configuration source
  8. configures the primary, secondary, and tertiary image source
  9. configures operational parameters

4.11.2. Basic BOF configuration

The parameters that specify the location of the image filename that the router will try to boot from and the configuration file are in the BOF.

The most basic BOF configuration should have the following:

  1. uplink port or Ethernet management port parameters
  2. primary image location
  3. primary configuration location

The following output is an example of a basic BOF configuration.

A:7210>show# bof
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xxx.xxx.xx.xx//import/panos_builds/nightly/
2.0                                             /S80/MTU-sultan/
    primary-config     tftp://xx.xxx.xx.xxx/MTU/mtu3DGP.cfg
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    0
    uplinkA-vlan       0
#uplinkB Port Settings:
uplinkB-port       1/1/2
    uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-address    0
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no console-disabled 
===============================================================================
A:7210>show#

The following output is an example of configuration to enable satellite mode in the BOF for the 7210 SAS-Sx/S 1/10GE.

===============================================================================
A:7210SAS-Sx# shell satclicmd 1 "show bof"
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xx.x.x.x/esat-1/primary/
    secondary-image    ftp://*:*@xx.x.x.x/esat-1/secondary/
    tertiary-image     ftp://*:*@xx.x.x.x/esat-1/tertiary/
    primary-config     ftp://*:*@xx.x.x.x/esat-1/config.cfg
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port 1/1/49
    uplinkA-autoneg
    uplinkA-duplex full
    uplinkA-speed 1000
    uplinkA-address xx.xxx.x.x/19 
    uplinkA-vlan 0
    uplinkA-route xx.x.x.x/32 next-hop xx.xxx.x.x
#uplinkB Port Settings:
    uplinkB-port 1/1/50
    uplinkB-autoneg
    uplinkB-duplex full
    uplinkB-speed 1000
    uplinkB-address xx.xxx.x.x/19 
    uplinkB-vlan 0
    uplinkB-route xx.x.x.x/32 next-hop xx.xxx.x.x
#System Settings:
    wait 3
    persist off
    console-speed 115200
    no console-disabled
    host-type satellites
===============================================================================
Result of 'satclicmd' = 0 = 0x0
A:7210SAS-Sx# 

The following output is an example of a basic BOF configuration for the 7210 SAS-R6.

*A:dut-b>show# bof
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xx.xxx.x.xxx/./images/sasr/cpm.tim
    primary-config     cf2:\MasterScaling_18_Aug_B.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.x.xxx/24 active
    eth-mgmt-address   xxxx::xxxx/64 active
    eth-mgmt-address   xx.xxx.x.xxx/24 standby
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.x.x
    eth-mgmt-route     xxx.xxx.x.x/16 next-hop xx.xxx.x.x
    eth-mgmt-route     xxx.xxx.x.x/16 next-hop xx.xxx.x.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
===============================================================================
*A:dut-b>show#

4.11.3. Common configuration tasks

This section describes basic system configuration tasks that must be performed to configure the BOF.

For details about hardware installation and initial router connections, refer to the specific hardware installation guide.

4.11.3.1. Searching for the BOF

The BOF should be on the same drive as the bootstrap image file. If the system cannot load or cannot find the BOF, the system checks whether the boot sequence was manually interrupted or else continues with the auto-init mode. The system prompts for a different image and configuration location.

Note:

Auto-init is not supported on the 7210 SAS-R6 and 7210 SAS-R12; use the starter BOF or create a BOF manually to boot the system.

4.11.3.2. Sample output of BOF configuration on bootup for 7210 SAS platforms

This section provides sample output of a BOF configuration boot sequence for 7210 SAS platforms.

4.11.3.2.1. Sample output: BOF configuration on bootup for 7210 SAS-Mxp and 7210 SAS-T

The following is a sample output of a manually interrupted boot sequence on the 7210 SAS-Mxp and 7210 SAS-T.

Hit a key within 3 seconds to change boot parameters...
 
Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt
 
 
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.
   "reset"   - reset the bof and reboot.
 
Press ENTER to begin, or 'flash' to enter firmware update, or the shell password...
 
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@xxx.xxx.x.xxx/./timos1.0R1
      ftp://user:passwd@[xxxx::x]/./timos1.0R1
      tftp://xxx.xxx.x.xxx/./timos1.0R1
      tftp://xxxx::x/./timos1.0R1
 
The existing Image URL is 'ftp://*:*@xx.xx.xxx.xx//home/***/images/both.tim'
Press ENTER to keep it.
Software Image URL:
Using: 'ftp://*:*@xx.xx.xxx.xx//home/****/images/both.tim'
 
 
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@xxx.xxx.x.xxx/./config.cfg
      ftp://user:passwd@[xxxx::x]/./config.cfg
      tftp://xxx.xxx.x.xxx/./config.cfg
      tftp://xxxx::x/./config.cfg
 
The existing Config URL is 'ftp://*:*@xx.xxx.xx.xxx/tftpboot/STU/config.cfg
Press ENTER to keep it, or the word 'none' for no Config URL.
Config File URL: none
 
 
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 address,
   static routes, and VLAN Id in case of uplink ports.
 
   eth-mgmt Port Setting
   --------------------
Existing eth-mgmt port settings are:
 
   eth-mgmt-port
   eth-mgmt-address    xx.xxx.xx.xx/24
   eth-mgmt-route      xx.xxx.x.x/16 next-hop xx.xxx.xx.x
   eth-mgmt-route      xxx.xxx.x.x/16 next-hop xx.xxx.xx.x
 
   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:
 
   uplinkA Port Setting
   --------------------
Existing uplinkA port settings are:
#uplinkA Port Settings:
uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    0
    uplinkA-vlan       0
#uplinkB Port Settings:
#uplinkB Port Settings:
uplinkB-port       1/1/2
    uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-address    0
    uplinkB-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:
 
   uplinkB Port Setting
   --------------------
Existing uplinkB port settings are:
 
   uplinkB-port       1/1/2
   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:
 
 
New Settings
------------
    primary-image      ftp://*:*@xxx.xxx.xxx.xx//home/****/images/both.tim
    secondary-config   tftp://xx.xxx.xx.xxx/STU/config.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xx/24
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.x
    eth-mgmt-route     xxx.xxx.x.x/16 next-hop xx.xxx.xx.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#uplinkA Port Settings:
uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    0
    uplinkA-vlan       0
#uplinkB Port Settings:
uplinkB-port       1/1/2
    uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-address    0
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    console-disabled 

4.11.3.2.2. Sample output: BOF configuration on bootup for 7210 SAS-R6 and 7210 SAS-R12

The following is a sample output of a manually interrupted boot sequence on the 7210 SAS-R6 and 7210 SAS-R12.

Hit a key within 3 seconds to change boot parameters...   
Enter password to edit the Boot Options File
Or CTRL-D to exit the prompt
Password: 
Incorrect password
Password: 
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.
   "reset"   - reset the bof and reboot.
Press ENTER to begin, or 'flash' to enter firmware update...
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@xxx.xxx.x.xxx/./timos1.0R1
      ftp://user:passwd@[xxxx::x]/./timos1.0R1
      tftp://xxx.xxx.x.xxx/./timos1.0R1
      tftp://[xxxx::x]/./timos1.0R1
The existing Image URL is 'ftp://*:*@xxx.xxx.xx.xxx/tmp/sasr/b/'
Press ENTER to keep it.
Software Image URL: 
Using: 'ftp://*:*@xxx.xxx.xx.xxx/tmp/sasr/b/'
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@xxx.xxx.x.xxx/./config.cfg
      ftp://user:passwd@[xxxx::x]/./config.cfg
      tftp://xxx.xxx.x.xxx/./config.cfg
      tftp://[xxxx::x]/./config.cfg
The existing Config URL is 'uf1:\SASR2553.cfg'
Press ENTER to keep it, or the word 'none' for no Config URL.
Config File URL: 
Using: 'uf1:\SASR2553.cfg'
Network Configuration
---------------------
   You specified a network location for either the
   software or the configuration file.  You need to
   assign an IP(v6) address for this system.
   The IP address should be entered in standard
   dotted decimal form with a network length.
       example:   192.168.1.169/24
Existing eth-mgmt port settings are:
   eth-mgmt-port        
   eth-mgmt-address    xx.xxx.xx.xx/24 active
   eth-mgmt-address    xx.xxx.xx.xx/24 standby
   eth-mgmt-address    0 active
   eth-mgmt-address    0 standby
   eth-mgmt-route      x.x.x.x/24 next-hop xx.xxx.xx.x
   eth-mgmt-route      x.x.x.x/24 next-hop xx.xxx.xx.x
   eth-mgmt-route      xx.xxx.x.x/16 next-hop xx.xxx.xx.x
   eth-mgmt-route      xxx.x.x.x/8 next-hop xx.xxx.xx.x
   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: edit
   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 Active IP address is xx.xxx.xx.xx/24. Press ENTER to keep it.
Enter eth-mgmt Active IP Address : xx.xxx.xx.xx/24
   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): 0
The existing eth-mgmt Standby IP address is xx.xxx.xx.xx/24. Press ENTER to keep it.
Enter eth-mgmt Standby IP Address : xx.xxx.xx.xx/24
   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): 0
   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: xxx.x.x.x/8 next-hop xx.xxx.xx.x
Do you want to keep it? (yes/no) y
Would you like to add a static route? (yes/no) yes
Enter ip route: xx.xxx.x.x/16 next-hop xx.xxx.xx.x
A route to that subnet already exists.
Would you like to add a static route? (yes/no) n
Would you like to add a static IPv6 route? (yes/no) n
Current configuration enables use of console (setting is "no console-disabled")
Press ENTER to proceed with existing setting or 'disable' to disable console access:
New Settings
------------
    primary-image      ftp://*:*@xxx.xxx.xx.xxx/tmp/sasr/b/
    secondary-image    cf1:\
    tertiary-image     uf1:\
    primary-config     uf1:\SASR2553.cfg
    secondary-config   uf1:\SASR2553.cfg
    tertiary-config    cf2:\SASR2553.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xx/24 active
    eth-mgmt-address   xx.xxx.xx.xx/24 standby
    eth-mgmt-route     x.x.x.x/24 next-hop xx.xxx.xx.x
    eth-mgmt-route     x.x.x.x/24 next-hop xx.xxx.xx.x
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.x
    eth-mgmt-route     xxx.x.x.x/8 next-hop xx.xxx.xx.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#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): y
Successfully saved the new settings in cf1:/bof.cfg
Configuring Network with eth-mgmt Port Setting.....
Primary config file present at: uf1:\SASR2553.cfg
Sap Index file present at: uf1:\SASR2553.sdx
Primary image location: ftp://*:*@xxx.xxx.xx.xxx/tmp/sasr/b/
Initial DNS resolving preference is ipv4-only
Loading image ftp://*:*@xxx.xxx.xx.xxx/tmp/sasr/b/cpm.tim
Version C-6.1.R3, Wed Jun  4 10:32:00 IST 2014 by builder in /home/builder/6.1B1/R3/
panos/main
text:(35757600-->121586864)
telnet>  

4.11.3.2.3. Sample output: BOF configuration on bootup for 7210 SAS-Sx/S 1/10GE

The following is a sample output of a manually interrupted boot sequence on the 7210 SAS-Sx/S 1/10GE.

primary-image      cf2:both.tim
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/25
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      10000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/26
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      10000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
    primary-image      ftp://*:*@xxx.xxx.xx.x/./images/SASS-hops-both.tim
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/1
    uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
    uplinkA-address    xxx.xxx.xx.xxx/24 
    uplinkA-vlan       0
    uplinkA-route      xxx.xxx.x.x/16 next-hop xxx.xxx.xx.x
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
   primary-image      ftp://*:*@xx.xxx.xx.xxx/./images/SASS-hops-both.tim
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xxx/24 active
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.xxx
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
  primary-image      uf1:both.tim
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/25
    no  uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      10000
    uplinkA-address    0 
    uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/26
    no  uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      10000
    uplinkB-address    0 
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled

4.11.3.3. Accessing the CLI

To access the CLI to configure the software for the first time, follow these steps:

  1. When the power to the chassis is turned on, the 7210 SAS software automatically begins the boot sequence.
  2. When the boot loader and BOF image and configuration files are successfully located, establish a router connection (console session).

See Console connection for information about establishing a console connection.

4.11.3.4. Configuring BOF Encryption

The BOF contents can be encrypted using AES256 and integrity information maintained using SHA256.

Use the following CLI syntax to configure BOF encryption.

CLI Syntax:
bof
encrypt {on | off}

4.11.3.5. Configuring the BOF Interactive Menu Password

The 7210 SAS supports the configuration of a BOF password to provide specific users with access to the BOF interactive menu. To securely store the BOF password, use the bof secure-bof-password command.

Use the following CLI syntax to configure and securely store a password for the BOF interactive menu.

CLI Syntax:
bof
bof-password password
no bof-password
secure-bof-password {enable | disable}

The password must be a plaintext string, between 8 and 32 characters, and cannot contain embedded nulls.

Caution:

When entering the password in plaintext, ensure that the password is not visible to bystanders.

4.11.3.6. Configuring the Configuration File Encryption

The configuration file contents can be encrypted using AES256 and integrity information maintained using SHA256.

Use the following CLI syntax to configure an encryption key for the configuration file.

CLI Syntax:
bof
encryption-key key
no encryption-key

The configured encryption key must be a plaintext string, between 8 to 32 characters, and cannot contain embedded nulls.

Caution:

When entering the encryption key in plaintext, ensure that the key is not visible to bystanders.

4.11.3.7. Console connection

To establish a console connection, you will need the following:

  1. an ASCII terminal or a PC running terminal emulation software set to the parameters described in Table 23
  2. a standard serial cable connector for connecting to a RS232 port (provides a RJ45 connector)

The following table lists the console configuration parameter values.

Table 23:  Console configuration parameter values 

Parameter

Value

Baud

115,200

Data bits

8

Parity

None

Stop bits

1

Flow control

None

4.11.3.8. Procedure to connect to a console

Perform this procedure to establish a console connection to any platform:

  1. Connect the terminal to the Console port on the front panel using the serial cable. See Location of console ports on 7210 SAS platforms for information about the console port and its placement on the 7210 SAS platforms.
  2. Power on the terminal.
  3. Establish the connection by pressing the <Enter> key a few times on your terminal keyboard.
  4. At the router prompt, enter the login and password.
    The default login is admin. The default password is admin.

4.11.3.9. Location of console ports on 7210 SAS platforms

This section provides console port information, supported variants, and modes of operation for 7210 SAS platforms.

4.11.3.9.1. 7210 SAS-Mxp console port

The 7210 SAS-Mxp is a non-blocking, service-aware IP/MPLS switch that supports the SR OS with 64Gbps (full-duplex) of switching capacity. It is available in two variants: Standard (Standard operating temperature range), and ETR (Extended Temperature Range). The 7210 SAS-Mxp can be operated in standalone or satellite mode.

The 7210 SAS-Mxp ETR CC (Conformal Coating) variant is conformally coated to provide additional protection against environmental contaminants that cause corrosion of the components when the platform is deployed in harsh environments. The 7210 SAS-Mxp ETR CC includes a -48V DC power supply. It supports an extended operating range of –40° to 149°F (–40° to 65°C) and includes two PoE/PoE+ ports.

The following figure shows an example of the console port on a 7210 SAS-Mxp front panel.

Figure 11:  Front panel: 7210 SAS-Mxp console port 

4.11.3.9.2. 7210 SAS-R6 console port

The 7210 SAS-R6 is a service-aware MPLS-capable switch, suitable as an MPLS Ethernet access aggregation platform. The 7210 SAS-R6 can aggregate 1G and 10G rings in access Ethernet networks. The platform supports full line-rate redundant switching capacity, as well as MPLS and MPLS-TP-based service transport. It supports control-plane and switch fabric redundancy.

The following figure shows an example of the console port on a 7210 SAS-R6 front panel.

Figure 12:  Front panel: 7210 SAS-R6 console port 
Note:

Refer to the 7210 SAS-R6 Chassis Installation Guide to know the IMMs supported.

4.11.3.9.3. 7210 SAS-R12 console port

The 7210 SAS-R12 is a service-aware IP MPLS-capable switch, suitable as an IP MPLS and Carrier Ethernet access aggregation platform. The 7210 SAS-R12 can aggregate 1G and 10G rings in access Ethernet networks. The platform supports full line-rate redundant switching capacity, as well as MPLS and MPLS-TP based service transport. It supports control-plane and switch fabric redundancy.

The following figure shows an example of the Console port on a 7210 SAS-R12 front panel.

Figure 13:  Front panel: 7210 SAS-R12 console port 
Note:

Refer to the 7210 SAS-R12 Chassis Installation Guide for more information about the supported IMMs.

4.11.3.9.4. 7210 SAS-Sx 1/10GE console port

The 7210 SAS-Sx 1/10GE is an IP/MPLS Ethernet device for business service applications and Ethernet mobile backhaul applications to be used as an access device or as an access aggregation device. It can also be operated in satellite mode, where it provides port expansion, allowing users to break out the 10GE ports on the 7x50 to 1GE ports.

7210 SAS-Sx 1/10GE is available in six variants:

  1. 7210 SAS-Sx 1/10GE 46F 2C 4SFP+
  2. 7210 SAS-Sx 1/10GE 22F 2C 4SFP+
  3. 7210 SAS-Sx 1/10GE 48T 4SFP+
  4. 7210 SAS-Sx 1/10GE 24T 4SFP+
  5. 7210 SAS-Sx 1/10GE 48Tp 4SFP+ PoE
  6. 7210 SAS-Sx 1/10GE 24Tp 4SFP+ PoE

All variants are 1RU platforms, designed to be NEBS compliant, supporting line-rate switching on all the ports, with the option for a redundant hot-swappable power supply. They also provide a console port and out-of-band Ethernet management interface on the rear of the chassis:

  1. The 7210 SAS-Sx 1/10GE 46F 2C 4SFP+ and 7210 SAS-Sx 1/10GE 22F 2C 4SFP+ allow for 48 SFP ports and 24 SFP ports respectively, along with an option to use copper interfaces on two ports.
  2. The 7210 SAS-Sx 1/10GE 48T 4SFP+ and 7210 SAS-Sx 1/10GE 24T 4SFP+ allow for 48 10/100/1000Mbps copper ports and 24 10/100/1000Mbps copper ports respectively.
  3. The 7210 SAS-Sx 1/10GE 48Tp 4SFP+ PoE and 7210 SAS-Sx 1/10GE 24Tp 4SFP+ POE allow for 48 10/100/1000Mbps copper ports and 24 10/100/1000Mbps copper ports respectively, along with option to use PoE/PoE+, with a maximum of 720W of power being available to PoE devices across all the ports.

In addition, all variants support 4 x 10GE SFP+ ports that can be used as uplinks.

The following variants support the use of a 1GE fiber-optic SFP in a 10GE SFP+ port:

  1. 7210 SAS-Sx 1/10GE 48T 4SFP+
  2. 7210 SAS-Sx 1/10GE 24T 4SFP+
  3. 7210 SAS-Sx 1/10GE 48Tp 4SFP+ PoE
  4. 7210 SAS-Sx 1/10GE 24Tp 4SFP+ PoE

With this functionality, operators can use either 1GE or 10GE fiber uplinks. This enhancement provides the flexibility of using SFP+ ports as 1GE uplinks with the capability to move to 10GE uplinks as bandwidth demands grow. This functionality is supported for standalone mode only.

For a list of SFPs supported for 1GE operation, contact your Nokia representative.

Note:

  1. Before using a 1GE SFP in an SFP+ port, the SFP+ port speed must be set to 1000 Mb/s with the config>port>ethernet>speed command; otherwise, an error message is generated indicating that the SFP is unsupported. For information about setting the port speed, refer to the Ethernet Port Commands section of the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
  2. SFP+ ports that support SFPs do not support speeds of 10 Mb/s or 100 Mb/s.

The 7210 SAS-Sx 1/10GE can be operated in two modes – Standalone mode and Satellite mode:

  1. In satellite mode, the platform is managed by the 7x50 host. It does not need to be assigned an IP address. The user needs to connect the right ports to the 7x50 and power on the node. The node automatically fetches the BOF, the image and the configuration required to operate in satellite mode.
  2. In standalone mode, the platform provides IP/MPLS functionality and needs to be assigned an IP address and managed independently.

The following figure shows an example of the console port on a 7210 SAS-Sx 1/10GE front panel for the 24-port variant.

Figure 14:  Front panel: 7210 SAS-Sx 1/10GE 24-port variant 

The following figure shows an example of the console port on a 7210 SAS-Sx 1/10GE front panel for the 48-port variant.

Figure 15:  Front panel: 7210 SAS-Sx 1/10GE 48-port fiber variant 

The following figure shows an example of the rear panel on a 7210 SAS-Sx 1/10GE port fiber variant.

Figure 16:  Rear Panel: 7210 SAS-Sx 1/10GE fiber variant 

4.11.3.9.5. 7210 SAS-S 1/10GE console port

The 7210 SAS-S 1/10GE is an IP/MPLS Ethernet device for business service applications and Ethernet mobile backhaul applications to be used as an access device or as an access aggregation device. It can also be operated in satellite mode, where it provides port expansion, allowing users to break out the 10GE ports on the 7x50 to 1GE ports.

The 7210 SAS-S 1/10GE is available in the following variants:

  1. 7210 SAS-S 1/10GE 48F 4SFP+ AC
  2. 7210 SAS-S 1/10GE 48F 4SFP+ DC
  3. 7210 SAS-S 1/10GE 24F 4SFP+ AC
  4. 7210 SAS-S 1/10GE 24F 4SFP+ DC
  5. 7210 SAS-S 1/10GE 48T 4SFP+ AC
  6. 7210 SAS-S 1/10GE 48T 4SFP+ DC
  7. 7210 SAS-S 1/10GE 24T 4SFP+ AC
  8. 7210 SAS-S 1/10GE 24T 4SFP+ DC
  9. 7210 SAS-S 1/10GE 48Tp 4SFP+ AC PoE
  10. 7210 SAS-S 1/10GE 24Tp 4SFP+ AC PoE

The variants are 1RU platforms, supporting line-rate switching on all the ports, with a single AC or DC integrated power supply and an option for redundant hot-swappable power supplies. They also provide a console port and OOB Ethernet management interface. The user has the option to use either 48-port or 24-port fiber or copper variants. All the variants support 4 x 10GE SFP+ ports.

The 7210 SAS-S 1/10GE 48Tp 4SFP+ AC PoE and 7210 SAS-S 1/10GE 24Tp 4SFP+ AC POE allow for 48 10/100/1000Mbps copper ports and 24 10/100/1000Mbps copper ports respectively, along with option to use PoE/PoE+, with a maximum of 720W of power being available to PoE devices across all the ports.

The following variants support the use of a 1GE fiber-optic SFP in a 10GE SFP+ port:

  1. 7210 SAS-S 1/10GE 48T 4SFP+ AC
  2. 7210 SAS-S 1/10GE 48T 4SFP+ DC
  3. 7210 SAS-S 1/10GE 24T 4SFP+ AC
  4. 7210 SAS-S 1/10GE 24T 4SFP+ DC

With this functionality, operators can use either 1GE or 10GE fiber uplinks. This enhancement provides the flexibility of using SFP+ ports as 1GE uplinks with the capability to move to 10GE uplinks as bandwidth demands grow. This functionality is supported for standalone mode only.

For a list of SFPs supported for 1GE operation, contact your Nokia representative.

Note:

  1. Before using a 1GE SFP in an SFP+ port, the SFP+ port speed must be set to 1000 Mb/s with the config>port>ethernet>speed command; otherwise, an error message is generated indicating that the SFP is unsupported. For information about setting the port speed, refer to the Ethernet Port Commands section of the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
  2. SFP+ ports that support SFPs do not support speeds of 10 Mb/s or 100 Mb/s.

The 7210 SAS-S 1/10GE can be operated in two modes: standalone mode and satellite mode:

  1. In satellite mode, it provides port expansion function and the platform is managed by the 7x50 host. It does not need to be assigned an IP address. User needs to connect the right ports to the 7x50 and power on the node. The node automatically fetches the BOF, the image and the configuration required to operate in satellite mode.
  2. In standalone mode, the platform provides IP/MPLS functionality and needs to be assigned an IP address and managed independently.

4.11.3.9.6. 7210 SAS-Sx 10/100GE console port

The 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4 and 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variants each provide 64 1GE/10GE SFP+ ports and 4 100GE CFP4 or QSFP28 ports, providing a platform for high-density 10GE Ethernet access and access aggregation with 100GE uplinks.

Both variants are 1.5RU platforms, with front access to all the 10GE and 100GE service interfaces. Both provide redundant hot-swappable power supplies (AC, -48V DC) and a non-removable set of fans on the rear of the chassis for cooling, with detection and notification of single fan failure. Both variants provide a Console port and out-of-band Ethernet management interface on the rear of the chassis.

Both variants support the use of a 1GE fiber-optic SFP in a 10GE SFP+ port. With this functionality, a single platform can be used to deliver both 1GE and 10GE services. This enables operators to continue to provide 1GE service or to build a 1GE access network and simultaneously migrate to deliver 10GE service and build a 10GE access network to address the growing bandwidth needs driven by cloud applications and migration to 4G/5G mobile networks. For a list of SFPs supported for 1GE operation, contact your Nokia representative.

Note:

  1. Before using a 1GE SFP in an SFP+ port, the SFP+ port speed must be set to 1000 Mb/s with the config>port>ethernet>speed command; otherwise, an error message is generated indicating that the SFP is unsupported. For information about setting the port speed, refer to the Ethernet Port Commands section of the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
  2. SFP+ ports that support SFPs do not support speeds of 10 Mb/s or 100 Mb/s.
  3. On the 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4 variant, ports on the front panel are named 1/1/1 to 1/1/64 for the 64 SFP+ ports, and 1/1/65 to 1/1/68 for the four 100GE CFP4 ports.
  4. On the 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant, ports on the front panel are named 1/1/1 to 1/1/64 for the 64 SFP+ ports, and 1/1/c1, 1/1/c2, 1/1/c3, and 1/1/c4 for the four100GE QSFP28 ports.

The platforms can be operated in two modes of operations: satellite mode and standalone mode:

  1. In satellite mode, it provides port expansion function and the platform is managed by the 7x50 host. It does not need to be assigned an IP address. User needs to connect the right ports to the 7x50 and power on the node. The node automatically fetches the BOF, the image and the configuration required to operate in satellite mode.
  2. In standalone mode, the platform provides IP/MPLS functionality and needs to be an IP address and managed independently.

The following figure shows the front panel for the 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4 variant.

Figure 17:  Front panel: 7210 SAS-Sx 10/100GE 64SFP+ 4CFP4  

The following figure shows the front panel for the 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant.

Figure 18:  Front panel: 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 

4.11.3.9.7. 7210 SAS-T console port

The 7210 SAS-T is a service-aware IP/MPLS switch. It supports two modes of operation:

  1. access-uplink mode (only L2 uplinks)
  2. network mode (L2 or MPLS uplinks)

The switch is available in two variants:

  1. 7210 SAS-T (non-ETR variant) with support for up to 12 100/1000 fiber-optic SFP ports, 10 10/100/1000 copper SFP ports and four XFP-based 10 Gig ports (see Figure 19)
  2. 7210 SAS-T (ETR variant) with support for up to 12 100/1000 fiber-optic SFP ports, six 10/100/1000 copper SFP ports, four XFP-based 10 Gig ports and four Power over Ethernet (PoE and PoE+) ports (see Figure 20)

The following figure shows an example of the console port on a 7210 SAS-T non-ETR variant front panel.

Figure 19:  Front panel: 7210 SAS-T (non-ETR variant) 

The following figure shows an example of the console port on a 7210 SAS-T ETR variant front panel.

Figure 20:  Front panel: 7210 SAS-T (ETR variant) 

4.11.3.10. Configuring BOF parameters

This section provides sample output of a BOF configurations on 7210 SAS platforms.

4.11.3.10.1. Sample output: BOF configuration for 7210 SAS-Mxp and 7210 SAS-T

The following is a sample output of a BOF configuration for the 7210 SAS-Mxp and 7210 SAS-T.

A:7210>show# bof
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xxx.xxx.xxx.xx//import/panos_builds/nightly/
2.0                                             /S80/MTU-sultan/
    primary-config     tftp://xx.xxx.xx.xxx/MTU/mtu3DGP.cfg
#eth-mgmt Port Settings:
    eth-mgmt-disabled
#uplinkA Port Settings:
    uplinkA-port       1/1/24
    uplinkA-address    xx.xxx.xx.xx/24
uplinkA-autoneg
    uplinkA-duplex     full
    uplinkA-speed      1000
uplinkA-vlan       0
#uplinkB Port Settings:
    uplinkB-port       1/1/2
    uplinkB-address    0
uplinkB-autoneg
    uplinkB-duplex     full
    uplinkB-speed      1000
    uplinkB-vlan       0
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no console-disabled 
===============================================================================
A:7210>show#

4.11.3.10.2. Sample output: BOF configuration for 7210 SAS-R6

The following is a sample output of a BOF configuration for 7210 SAS-R6.

--------
*7210SAS# show bof 
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xx.xxx.xx.xx/./images/SASR6-KT2/
    primary-config     cf1:\config.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xx/24 active
    eth-mgmt-address   xx.xxx.xx.xx/24 standby
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.x
    eth-mgmt-route     xxx.x.x.x/8 next-hop xx.xxx.xx.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
===============================================================================
7210 SAS#

4.11.3.10.3. Sample output: BOF configuration for 7210 SAS-R12

The following is a sample output of a BOF configuration for 7210 SAS-R12.

--------------
A:7210SAS# show bof 
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xx.xxx.xx.xx/./images/SASR12-KT2
    primary-config     cf1:\sreekak.cfg
    secondary-config   cf2:\sreekak.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xx/24 active
    eth-mgmt-address   xx.xxx.xx.xx/24 standby
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.x
    eth-mgmt-route     xxx.x.x.x/8 next-hop xx.xxx.xx.x
    eth-mgmt-autoneg
    eth-mgmt-duplex    full
    eth-mgmt-speed     100
#System Settings:
    wait               3
    persist            off
    console-speed      115200
    no  console-disabled
===============================================================================
A:7210SAS#

4.11.3.10.4. Sample output: BOF configuration for 7210 SAS-Sx/S 1/10GE

The following is a sample output of a BOF configuration for 7210 SAS-Sx/S 1/10GE.

*A:SAS7210>show# bof
===============================================================================
BOF (Memory)
===============================================================================
    primary-image      ftp://*:*@xx.xxx.x.xx/./images/SASS/hops-both.tim
    primary-config     cf1:\default_config.cfg
#eth-mgmt Port Settings:
    no  eth-mgmt-disabled
    eth-mgmt-address   xx.xxx.xx.xx/24 active
    eth-mgmt-route     xx.xxx.x.x/16 next-hop xx.xxx.xx.x
    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
===============================================================================
*A:SAS7210>show#
 

4.12. Service management tasks

This section describes the service management tasks and system administration commands.

4.12.1. System administration commands

Use the following administrative commands to perform management tasks.

CLI Syntax:
A:ALA-1# admin
auto-init stop
check-golden-bootstrap
debug-save [<file-url>]
disconnect [address <ip-address> | username <user-name> | {console|telnet|ftp|ssh}]
display-config
[no] enable-tech
reboot [upgrade][auto-init][now]
save [file-url] [detail] [index]
set-time <date> <time>
tech-support <file-url>
update-golden-bootstrap [file-url]

4.12.1.1. Viewing the current configuration

Use one of the following CLI commands to display the current configuration. The detail option displays all default values. The index option displays only the persistent indexes. The info command displays context-level information.

CLI Syntax:
admin# display-config [detail|index]
info detail

The following is a sample configuration file.

*A:sim169# admin display-config
# TiMOS-B-0.0.I218 both/i386 NOKIA SAS-Sx 7210 Copyright (c) 2016.
# All rights reserved. All use subject to applicable license agreements.
# Built on Fri Sep 26 20:46:58 IST 2016 by panosbld in /panosbld/ws/panos/main
 
# Generated THU JUN 23 19:19:22 2016 UTC
 
exit all
configure
#--------------------------------------------------
echo "System Configuration"
#--------------------------------------------------
    system
        name "7210-3"
        contact "Fred Information Technology"
        location "Bldg.1-floor 2-Room 201"
        clli-code "abcdefg1234"
        coordinates "N 45 58 23, W 34 56 12"
        ccm 1
        exit
        snmp
        exit
        login-control
            idle-timeout 1440
            motd text "7210-3"
        exit
        time
            sntp
                shutdown
            exit
            zone UTC 
        exit
        thresholds
            rmon
            exit
        exit
    exit...
...
#--------------------------------------------------
 
# Finished FRI Nov 21 15:06:16 2008 UTC
A:*A:sim169## 

4.12.1.2. Modifying and saving a configuration

If you modify a configuration file, the changes remain in effect only during the current power cycle unless a save command is executed. Changes are lost if the system is powered down or the router is rebooted without saving:

  1. Specify the file URL location to save the running configuration. If a destination is not specified, the files are saved to the location where the files were found for that boot sequence. The same configuration can be saved with different filenames to the same location or to different locations.
  2. The detail option adds the default parameters to the saved configuration.
  3. The index option forces a save of the index file.
  4. Changing the active and standby addresses without reboot standby CPM may cause a boot-env synchronization to fail.

Use the following command syntax to save a configuration.

CLI Syntax:
bof# save [cflash-id]
Example:
 A:ALA-1# bof A:ALA-1>bof# save cf1: A:ALA-1>bof#

Use the following command syntax to save the system configuration.

CLI Syntax:
admin# save [file-url] [detail] [index]
Example:
 A:ALA-1# admin save cf1:\test123.cfg Saving config.# Saved to cf1:\test123.cfg ... complete A:ALA-1#
Note:

If the persist option is enabled and the admin save file-url command is executed with an FTP path used as the file-url parameter, two FTP sessions simultaneously open to the FTP server. The FTP server must be configured to allow multiple sessions from the same login; otherwise, the configuration and index files will not be saved correctly.

4.12.1.3. Deleting BOF parameters

You can delete specific BOF parameters. The no form of these commands removes the parameter from configuration. The changes remain in effect only during the current power cycle unless a save command is executed. Changes are lost if the system is powered down or the router is rebooted without saving.

Deleting the BOF and rebooting causes the system to enter the auto mode.

Use the following CLI syntax to save and remove BOF configuration parameters.

CLI Syntax:
bof# save [cflash-id]
Example:
  A:ALA-1# bof A:ALA-1>bof# save cf1: A:ALA-1>bof#
CLI Syntax:
*A:7210>bof#
no console-speed
no dns-domain
no eth-mgmt-address
no eth-mgmt-autoneg
no eth-mgmt-disable
eth-mgmt-duplex
no eth-mgmt-route
eth-mgmt-speed
persist
no ping-address
no primary-config
no primary-dns
no primary-image
save
no secondary-config
no secondary-dns
no secondary-image
no tertiary-config
no tertiary-dns
no tertiary-image
no uplinkA-address
no uplinkA-autoneg
no uplinkA-duplex
no uplinkA-speed
no uplinkA-port
no uplinkA-route
no uplinkA-vlan
no uplinkB-address
no uplinkB-autoneg
no uplinkB-duplex
no uplinkB-speed
no uplinkB-port
no uplinkB-route
no uplinkB-vlan
wait

4.12.1.4. Saving a configuration to a different filename

Save the current configuration with a unique filename to have additional backup copies and to edit parameters with a text editor. You can save your current configuration to an ASCII file.

Use one of the following CLI syntax to save a configuration to a different location.

CLI Syntax:
bof# save [cflash-id]
Example:
  A:ALA-1# bof A:ALA-1>bof# save cf1: A:ALA-1>bof#

or

CLI Syntax:
admin# save [file-url] [detail] [index]
Example:
  A:ALA-1>admin# save cf1:\testABC.cfg Saving config.# Saved to cf1:\testABC.cfg ... complete A:ALA-1#

4.12.1.5. Rebooting

When an admin>reboot command is issued, the system reboots. Changes are lost unless the configuration is saved. Use the admin>save file-url command to save the current configuration. If no command line options are specified with the reboot command, the user is prompted to confirm the reboot operation. However, if the now option is specified, the user is not prompted to confirm the reboot operation.The reboot upgrade command forces an upgrade of the device firmware (CPLD and ROM) and reboots the system.

Note:

The auto-init option is supported on the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone), 7210 SAS-Sx 10/100GE (standalone), and 7210 SAS-T. It is not supported on 7210 SAS-R6, 7210 SAS-R12, and platforms operating in standalone-VC mode.

Use the following CLI syntax to reboot.

CLI Syntax:
admin# reboot [upgrade] [auto-init] [now]
A:DutA>admin# reboot
Are you sure you want to reboot (y/n)? y
Resetting...OK
 
Nokia 7210 Boot ROM. Copyright 2016 Nokia.
All rights reserved. All use is subject to applicable license agreements.
Running POST tests from ROM
Testing ROM load area...done
 
Relocating code...Jumping to RAM
...

When an admin reboot auto-init command is issued, the system resets the existing BOF and reboots. The system startup process after the admin reboot auto-init command is executed is the same as the first time system boot as described in System initialization.

Note:

After the BOF is reset, the system may not boot up with the last saved system configuration unless the new BOF also uses the same configuration file. If booting the system with the last saved system configuration is required, it is recommended to run the admin>save file-url command to save the current system configuration and modify the BOF to use this configuration file.

Use the following syntax to reset the BOF and reboot.

CLI Syntax:
admin# reboot auto-init [now]
Example: *A:ALA-1# admin reboot auto-init 
WARNING: Configuration and/or Boot options may have changed since the last save.
Are you sure you want to reset the bof and reboot (y/n)? Y 
Resetting...OK
 
Nokia 7210 Boot ROM. Copyright 2016 Nokia.
All rights reserved. All use is subject to applicable license agreements.