5.8. Configuring the BOF with the CLI
This section provides information to configure BOF parameters with the CLI.
Topics in this section include:
5.9. BOF Configuration Overview
The 7705 SAR 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 CSM Management port (speed, duplex, auto)
- Assigns the IP address for the CSM Management port
- Creates static routes for the CSM Management 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
Note: The CSM Management port is referred to as the CPM Management port in the CLI to align with the CLI syntax used with other SR products.
5.10. 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:
- primary address
- primary image location
- primary configuration location
The following displays an example of a basic BOF configuration.
5.11. Configuring BOF Parameters
Use the CLI syntax displayed below to configure BOF parameters:
The following example displays BOF command usage:
5.12. Configuring BOF Encryption
Use the following CLI syntax to enable encryption of the BOF (bof.cfg) using the AES256 cipher algorithm.
After the BOF is encrypted, it can still be modified using the BOF interactive menu. Access to the BOF interactive menu is controlled using a password.
Use the following syntax to set the interactive menu password.
The password can be in one of the following formats:
- a plaintext string between 8 and 32 characters; the plaintext string cannot contain embedded nulls or end with “hash” or “hash2”
- a hashed string between 1 and 64 characters; the selected hashing scheme can be hash or hash2
Note: The hash2 encryption scheme is node-specific and the password cannot be transferred between nodes.
After the password is set, editing of the BOF during a boot process is allowed only if the password is entered correctly (the boot process can be interrupted in order to make BOF changes). If the password is not entered correctly within 30 s, the node reboots whether the BOF is encrypted or not. This adds an additional layer of security that ensures that the BOF is not exposed to any unauthorized user. After the system is booted, changes can be made to the BOF without entering the password.
| Note: After BOF encryption is configured, use the bof save command to save the encrypted file. |
5.13. Configuring Configuration File Encryption
Use the following syntax to set the configuration file encryption key using the AES256 cipher algorithm. This key is used for all configuration files (primary, secondary, and tertiary).
The encryption key can be in one of the following formats:
- a plaintext string between 8 and 32 characters; the plaintext string cannot contain embedded nulls or end with “hash” or “hash2”
- a hashed string between 1 and 64 characters; the selected hashing scheme can be hash or hash2
| Note:
|
5.14. Service Management Tasks
This section describes system administration commands.
5.14.1. System Administration Commands
Use the following administrative commands to perform management tasks.
5.14.1.1. Viewing the Current Configuration
Use the following CLI command to display the current configuration. The detail option displays all default values. The index option displays only the persistent indexes.
The following displays an example of a configuration file:
5.14.1.2. Modifying or Deleting BOF Parameters
You can modify or delete 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.
 | Caution: All BOF parameters can be configured, modified, or deleted locally through a console session or remotely using Telnet or SSH. However, when modifying or deleting the BOF address, the following behaviors must be considered.
|
Use the following CLI syntax to remove BOF configuration parameters:
5.14.1.3. 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 filenames 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.
Use either of the following CLI syntaxes to save a configuration:
| Note:
|
5.14.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 either of the following CLI syntaxes to save a configuration to a different location:
or
5.14.1.5. Rebooting
When an admin>reboot command is issued, routers with redundant CSMs are rebooted. 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: