3.4. Configuring Boot Options File with CLI
This section provides information to configure BOF parameters with CLI.
3.4.1. BOF Configuration Overview
Nokia routers do not contain a boot EEPROM. The boot loader code is loaded from the boot.ldr file. The BOF file performs the following tasks:
- Sets up the CPM and CCM Ethernet port (speed, duplex, auto).
- Assigns the IP address for the CPM and CCM Ethernet port.
- Creates static routes for the CPM/CCM Ethernet port.
- Sets the console port speed.
- Configures the Domain Name System (DNS) name and DNS servers.
- Configures the primary, secondary, tertiary configuration source.
- Configures the primary, secondary, and tertiary image source.
- Configures the license source.
- Configures operational parameters.
3.4.2. Basic BOF Configuration
The parameters which specify 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:
- Primary address
- Primary image location
- Primary configuration location
The following is a sample of a basic BOF configuration.
Classic CLI:
MD-CLI:
3.4.3. Common Configuration Tasks
The following sections are basic system tasks that must be performed.
For details about hardware installation and initial router connections, refer to the specific router hardware installation guide.
3.4.3.1. Searching for the BOF
The BOF should be on the same drive as the boot loader file. If the system cannot load or cannot find the BOF then the system checks whether the boot sequence was manually interrupted. The system prompts for a different image and configuration location.
The following example shows an example of the output when the boot sequence is interrupted.
. . .
3.4.3.2. Accessing the CLI
To access the CLI to configure the software for the first time, follow these steps:
- When the CPM/CCM is installed, and power to the chassis is turned on, the SR OS software automatically begins the boot sequence.
- When the boot loader and BOF image and configuration files are successfully located, establish a router connection (console session).
3.4.3.2.1. Console Connection
To establish a console connection, you will need the following:
- An ASCII terminal or a PC running terminal emulation software set to the parameters shown in the table below.
- A standard serial cable with a male DB9.
Table 6 lists the console configuration parameter values.
Table 6: Console Configuration Parameter Values
Parameter | Value |
Baud Rate | 115,200 |
Data Bits | 8 |
Parity | None |
Stop Bits | 1 |
Flow Control | None |
To establish a console connection:
- Connect the terminal to the Console port on the CPM/CCM using the serial cable.
- Power on the terminal.
- Establish the connection by pressing the <Enter> key a few times on your terminal keyboard.
- At the router prompt, enter the login and password.The default login is admin.The default password is admin.
3.4.4. Autoconfigure
When autoconfigure is enabled, the router performs a DHCP discovery or solicit (IPv6) to get the IP address of the out-of-band (OOB) management port.
The OOB management port can support a DHCP client for IPv4, IPv6, or dual stack. For dual stack, both IPv4 and IPv6 DHCP are configured. When the offer for either of the address families arrives, the management port is configured with the IP address in the offer. Eventually, both offers arrive and the management port is configured with both address families.
When a DHCP client is configured using autoconfigure, all image and license files should be placed and loaded from the CF. The configuration file could be loaded from the network, but Nokia recommends that the config file be on the CF as well. The configuration file is not loaded until the DHCP client offer is received and programmed successfully for the management port IP address, or the DHCP client timeout is expired.
3.4.4.1. Autoconfigure Restrictions
When autoconfigure is enabled, a static IP address or static route cannot be configured in the BOF.
Similarly, a DNS server cannot be configured in the BOF, and only the DNS server provided by the DHCP offer can be used to resolve URLs.
The option 15 DNS domain name is not supported. The user can configure the DNS domain in the BOF so that the domain is not blocked when autoconfigure is used. Otherwise, the user must use the absolute URL with the host name and domain included.
3.4.4.2. DHCP Discovery of MAC Addresses
When autoconfigure is used on redundant CPM chassis, the DHCP discovery uses the chassis MAC address. Only the active CPM performs a DHCP discovery and not the inactive CPM. When the offer arrives, the node uses that IP and the chassis MAC as addresses for management. Consequently, the inactive CPM is not reachable by the network, because it has no separate IP address. On activity switch, the inactive CPM inherits the active IP and chassis MAC.
For non-redundant CPMs, the management port MAC is used.
 | Note: The router must be rebooted when enabling autoconfigure for the first time to ensure that the CPM card uses the chassis MAC address. |
3.4.4.3. IPv6 DUID
SR OS supports type 2 DUID (link local), which is set to the chassis serial number. Type 3 (enterprise) is set to the chassis MAC address. Type 1 is not supported.
For type 2 DUID, the SR OS sends the Nokia Enterprise ID as the second byte of the DUID, followed by the chassis serial number. The first byte is the DUID type code. The chassis serial number starts with capital ASCII letters, which ensures that the serial number is unique as an application ID in the SR OS IPv6 DHCP application domain.
DUID type codes are as follows:
- DHCP6C_DUID_ENT_ID__IPSEC_IPV4ADDR - 1
- DHCP6C_DUID_ENT_ID__IPSEC_ASN1DN - 2
- DHCP6C_DUID_ENT_ID__IPSEC_FQDN - 3
- DHCP6C_DUID_ENT_ID__IPSEC_USER_FQDN - 4
- DHCP6C_DUID_ENT_ID__IPSEC_IPV6ADDR - 5
- DHCP6C_DUID_ENT_ID__IPSEC_ASN1GN - 6
- DHCP6C_DUID_ENT_ID__IPSEC_KEYID - 7
- DHCP6C_DUID_ENT_ID__WLAN_GW - 8
- DHCP6C_DUID_ENT_ID__AUTOBOOT - 9
- DHCP6C_DUID_ENT_ID__ZTP_BOF_AUTOP - Capital letters in ASCII
3.4.4.4. IPv6 DHCP RAs
An IPv6 DHCP offer does not have an IP prefix within the offer, unlike an IPv4 DHCP offer. The IPv6 prefix is usually obtained from the IPv6 Route Advertisement (RA) arriving from the upstream router. For ZTP, SR OS is a host and assigns a /128 prefix to the IPv6 address obtained from the DHCP offer.In addition, SR OS supports the installation of IPv6 default and static routes from upstream routers using the IPv6 RA. Multiple upstream routers can respond to a route solicitation with their own RA. SR OS installs all the routes advertised by the RA. If the same route is advertised by multiple upstream routers (next hops), the SR OS installs the route with the highest preference. The SR OS does not support ECMP when the same route is advertised from multiple next hops by multiple RAs.
To ensure that all the RAs are obtained before the auto-provisioning process is started for IPv6, SR OS follows the RFC 4861 recommendation that the host (in this case SR OS) send a minimum of three route solicitations. This is to ensure that if a route solicitation is lost, at least one of the three would reach the upstream routers. Each route solicitation is followed by a 4 s timeout. If the first route solicitation is sent at T0, the second is sent at T0+4 s and the third is sent at T0+8 s. The upstream routers must respond to the route solicitation with in 0.5 s. This means that the SR OS will have all of the RAs and the routes within 8.5 s of the first route solicitation. Therefore, SR OS waits for a maximum of 9 s to receive all RAs.
If the DHCPv6 timeout is less than 9 s, the DHCPv6 timeout is honored even for the RA wait time. If the node has received a single RA and DHCP offer, the process is considered a success. However, it is possible that not all the RAs have arrived on the node because the node has waited less than 9 s.
3.5. System Administration Commands in the Classic CLI
For more information about the supported classic CLI commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide.
Use the following administrative commands to perform management tasks.
3.5.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 indices. The info command displays context-level information.
The following example shows a configuration file for the 7750 SR:
3.5.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.
- 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 file names to the same location or to different locations.
- The detail option adds the default parameters to the saved configuration.
- The index option forces a save of the index file.
- Changing the active and standby addresses without reboot standby CPM may cause a boot-env sync to fail.
The following command saves a configuration:
The following command saves the system configuration:
| 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. |
3.5.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 a BOF address entry is not allowed from a remote session.
Use the following CLI syntax to save and remove BOF configuration parameters:
3.5.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 the following CLI syntax to save a configuration to a different location:
3.5.5. Rebooting
When an admin>reboot command is issued, routers with redundant CPM are rebooted as well as the XMAs, XCMs, and IOMs. 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, the user is prompted to confirm the reboot operation.
Use the following CLI syntax to reboot:
3.5.6. Setting the MTU Value for the Management Port
The ip-mtu command in the bof context configures the MTU for IP packets transmitted out the interface of the management router instance associated to the management port. The command applies to the SR OS but does not necessarily apply during the boot loader processing.
The operational MTU for the port is set to the lesser of the values configured with the ip-mtu command and the management port MTU. For example, with the port MTU fixed at 1514 bytes and an Ethernet header size of 14 bytes, the MTU of the management port is1500 bytes (the default operational IP MTU).
If the interface supports IPv6 packets, the command value must be set to 1280 or higher, in accordance with RFC 2460 Internet Protocol, Version 6 (IPv6) Specification.
3.6. System Administration Commands in the MD-CLI
For more information about the supported MD-CLI commands, refer to the 7450 ESS, 7750 SR, and 7950 XRS MD-CLI Command Reference Guide.
Use the following administrative commands to perform management tasks.
3.6.1. Viewing the Current Configuration
The admin show configuration command displays the current configuration for a specified configuration region (the default region is configure). The booted and cflash-id options are valid only for the bof configuration region.
The following example shows a BOF configuration file with the detail option to display all default and unconfigured values and the units option to show units where applicable:
3.6.2. Modifying BOF Parameters
Changing the active and standby addresses without rebooting the standby CPM may cause synchronization with the boot-env option to fail.
Deleting a BOF address entry is not allowed from a remote session.
BOF parameters can be modified via a BOF session in exclusive configuration mode in the MD-CLI. The same configuration management commands that are available in the configure region are available in the bof region.
Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR MD-CLI Command Reference Guide and Configuring in the MD-CLI in the 7450 ESS, 7750 SR, 7950 XRS, and VSR MD-CLI User Guide for more information.
3.6.3. Saving a Configuration
Configuration changes are lost if the system is powered down or the router is rebooted before the changes are saved. If the URL location to save the running configuration is not specified, the files are saved to the location where the files were found for the boot sequence. The same configuration can be saved with different file names to the same location or to different locations.
Changing the active and standby addresses without rebooting the standby CPM may cause synchronization with the boot-env option to fail.
The following command saves the running configuration for the configure region. If no URL is specified, the configuration is saved to file config.cfg.
The following command saves a BOF configuration:
The BOF configuration is saved to cf3:\bof.cfg with every commit command. The BOF configuration can be manually saved to a backup file on a server or to a different location.
The following command saves the BOF configuration to the file named testbof.cfg on cf3:
| Note: The BOF configuration file is saved in classic format. |
3.6.4. Rebooting
When a reboot command is issued, routers with redundant CPM are rebooted as well as the XMAs, XCMs, and IOMs. If the now option is not specified, the user is prompted to confirm the reboot operation.
Use the following syntax to reboot the router:
3.6.5. Setting the MTU Value for the Management Port
The ip-mtu command in the bof router “managment” interface “management” context configures the MTU for IP packets transmitted out the interface of the management router instance associated to the management port. The command applies to the SR OS but does not necessarily apply during the boot loader processing.
The operational MTU for the port is set to the lesser of the values configured with the ip-mtu command and the management port MTU. For example, with the port MTU fixed at 1514 bytes and an Ethernet header size of 14 bytes, the MTU of the management port is1500 bytes (the default operational IP MTU).
If the interface supports IPv6 packets, the command value must be set to 1280 or higher, in accordance with RFC 2460 Internet Protocol, Version 6 (IPv6) Specification.