Configuring Boot Options File with CLI
This section provides information to configure BOF parameters with CLI.
Topics in this section include:
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/CCM Ethernet port (speed, duplex, auto).
- Assigns the IP address for the CPM/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 operational parameters.
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.
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.
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.
. . .
Accessing the CLI
To access the CLI to configure the software for the first time, follow these steps:
- When the CPM/CFM/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).
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 28: 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/CFM/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.
Configuring BOF Parameters
The following example shows a BOF configuration on a 7750 SR:
Service Management Tasks
This section discusses the following service management tasks:
System Administration Commands
Use the following administrative commands to perform management tasks.
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:
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. |
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 Telnet session.
Use the following CLI syntax to save and remove BOF configuration parameters:
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:
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: