4.6. BOF Configuration Command Reference

4.6.1. Command Hierarchies

4.6.1.1. Configuration Commands

[no] address ip-prefix/ip-prefix-length [active | standby]
[no] autonegotiate
console-speed baud-rate
dns-domain dns-name
— no dns-domain
duplex {full | half}
[no] fips-140-2
[no] li-local-save
[no] li-separate
persist {on | off}
primary-config file-url
primary-dns ip-address
— no primary-dns [ip-address]
primary-image file-url
save [cflash-id ]
secondary-config file-url
secondary-dns ip-address
— no secondary-dns [ip-address]
secondary-image file-url
speed speed
[no] static-route ip-prefix/ip-prefix-length next-hop ip-address
system-base-mac mac-address
system-profile {profile-a | profile-b}
tertiary-config file-url
tertiary-dns ip-address
— no tertiary-dns [ip-address]
tertiary-image file-url
wait seconds

4.6.2. Command Descriptions

4.6.2.1. File Management Commands

bof

Syntax 
bof
Context 
<root>
Description 

This command creates or edits the boot option file (BOF) for the specified local storage device.

A BOF file specifies where the system searches for runtime images, configuration files, and other operational parameters during system initialization.

BOF parameters can be modified. Changes can be saved to a specified compact flash. The BOF must be located in the root directory of either an internal or external compact flash local to the system and have the mandatory filename of bof.cfg.

When modifications are made to in-memory parameters that are currently in use or operating, the changes are effective immediately. For example, if the IP address of the management port is changed, the change takes place immediately.

Only one entry of the BOF configuration command statement can be saved once the statement has been found to be syntactically correct.

When opening an existing BOF that is not the BOF used in the most recent boot, a message is issued notifying the user that the parameters will not affect the operation of the node.

No default boot option file exists. The router boots with the factory default boot sequence and options.

save

Syntax 
save [cflash-id]
Context 
bof
Description 

This command uses the boot option parameters currently in memory and writes them from the boot option file to the specified compact flash.

The BOF must be located in the root directory of the internal or external compact flash drives local to the system and have the mandatory filename of bof.cfg.

If a location is not specified, the BOF is saved to the default compact flash drive (cf3:) on the active CPM (typically the CPM in slot A, but the CPM in slot B could also be acting as the active CPM). The slot name is not case-sensitive. You can use upper or lowercase “A” or “B”.

Command usage:

  1. bof save — saves the BOF to the default drive (cf3:) on the active CPM (either in slot A or B)
  2. bof save cf3: — saves the BOF to cf3: on the active CPM (either in slot A or B)

To save the BOF to a compact flash drive on the standby CPM (for example, the redundant (standby) CPM is installed in slot B), specify -A or -B option.

Command usage:

  1. bof save cf3-A: — saves the BOF to cf3: on CPM in slot A whether it is active or standby
  2. bof save cf3-B: — saves the BOF to cf3: on CPM in slot B whether it is active or standby

The slot name is not case-sensitive. You can use upper or lowercase “A” or “B”.

The bof save and show bof commands allow you to save to or read from the compact flash of the standby CPM. Use the show card command to determine the active and standby CPM (A or B).

Default 

Saves must be explicitly executed. The BOF is saved to cf3: if a location is not specified.

Parameters 
flash-id—
Specifies the compact flash ID where the bof.cfg is to be saved.
Values—
cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

Default—
cf3:

4.6.2.2. BOF Processing Control

wait

Syntax 
wait seconds
Context 
bof
Description 

This command configures a pause, in seconds, at the start of the boot process which allows system initialization to be interrupted at the console.

When system initialization is interrupted the operator is allowed to manually override the parameters defined in the boot option file (BOF).

Only one wait command can be defined in the BOF.

Default 

wait 3

Parameters 
seconds—
Specifies the time to pause at the start of the boot process, in seconds.
Values—
1 to10

 

4.6.2.3. Console Port Configuration

console-speed

Syntax 
console-speed baud-rate
no console-speed
Context 
bof
Description 

This command configures the console port baud rate.

When this command is issued while editing the BOF file used for the most recent boot, both the BOF file and the active configuration are changed immediately.

The no form of the command reverts to the default value.

Default 

console-speed 115200

Parameters 
baud-rate—
Specifies the console port baud rate, expressed as a decimal integer.
Values—
9600, 19200, 38400, 57600, 115200

 

4.6.2.4. Image and Configuration Management

persist

Syntax 
persist {on | off}
Context 
bof
Description 

This command specifies whether the system will preserve system indexes when a save command is executed. During a subsequent boot, the index file is read along with the configuration file. As a result, a number of system indexes are preserved between reboots, including the interface index, LSP IDs, path IDs, etc. This reduces resynchronizations of the Network Management System (NMS) with the affected network element.

In the event that persist is on and the reboot with the appropriate index file fails, SNMP is operationally shut down to prevent the management system from accessing and possibly synchronizing with a partially booted or incomplete network element. To enable SNMP access, enter the config>system>snmp>no shutdown command.

If persist is enabled and the admin save url command is executed with an FTP path used as the 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.

Note:

  1. Persistency files (.ndx) are saved on the same disk as the configuration files and the image files.
  2. When an operator sets the location for the persistency file, the system will check to ensure that the disk has enough free space. If this there is not enough free space, the persistency will not become active and a trap will be generated. Then, it is up to the operator to free adequate disk space. In the meantime, the system will perform a space availability check every 30 seconds. As soon as the space is available the persistency will become active on the next (30 second) check.
Default 

persist off

Parameters 
on—
Enables the system index saves between reboots.
off—
Disables the system index saves between reboots.

primary-config

Syntax 
primary-config file-url
no primary-config
Context 
bof
Description 

This command specifies the name and location of the primary configuration file.

The system attempts to use the configuration specified in primary-config. If the specified file cannot be located, the system automatically attempts to obtain the configuration from the location specified in secondary-config and then the tertiary-config.

If an error in the configuration file is encountered, the boot process aborts.

The no form of the command removes the primary-config configuration.

Parameters 
file-url—
Specifies the primary configuration file location, expressed as a file URL.
Values—

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

primary-image

Syntax 
primary-image file-url
no primary image
Context 
bof
Description 

This command specifies the primary directory location for runtime image file loading.

The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.

All runtime image files (*.tim files) must be located in the same directory.

The no form of the command removes the primary-image configuration.

Parameters 
file-url—
Specifies the file-url can be either local (this CPM) or a remote FTP server.
Values—

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

system-base-mac

Syntax 
system-base-mac mac-address
no system-base-mac
Context 
bob
Description 

This command is used to specify the base MAC address for a VSR-based system. The specified MAC address is used as the first MAC address by the system to assign MAC addresses to individual interfaces.

It is strongly recommended that a unique base MAC address is assigned to each VSR instance with a minimum gap of 1024 between base addresses to avoid a MAC address overlap.

The no form of this command removes the configured system base MAC address.

Default 

no system-base-mac

Parameters 
mac-address—
Specifies the MAC address.
Values—
xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx

 

system-profile

Syntax 
system-profile {profile-a | profile-b}
no system-profile
Context 
bof
Description 

This command configures the system profile in the BOF.

System profile none represents the existing system capabilities and allows FP3- and FP4-based hardware to co-exist within a system. This is indicated by the omission of the system-profile parameter in the BOF, except on 7750 SR-1 systems.

System profile profile-a is primarily targeted at subscriber services and layer 2 and 3 VPN business services.

System profile profile-b is primarily targeted at infrastructure routing, core, peering, and DC-GW applications.

System profile profile-a and profile-b are supported on 7950 XRS-20/20e, 7750 SR-1 and 7750 SR-12e systems, and support only FP4-based line cards.

The system profile on 7750 SR-1 systems should be set to profile-a. It is set by default to profile-a when the system-profile parameter is omitted from the BOF, or configured to an invalid value.

On 7950 XRS-20/20e and 7750 SR-12e systems, default system profile is none.

On all other systems, the system-profile parameter must not be configured in the BOF which sets the system profile to none.

The no version of this command removes the system-profile parameter from the BOF.

Default 

none

Parameters 
profile-a—
This system profile is for subscriber services and Layer 2 and 3 VPN business services.
profile-b—
This system profile is primarily targeted at infrastructure routing, core, peering, and DC-GW applications.

secondary-config

Syntax 
secondary-config file-url
no secondary-config
Context 
bof
Description 

This command specifies the name and location of the secondary configuration file.

The system attempts to use the configuration as specified in secondary-config if the primary config cannot be located. If the secondary-config file cannot be located, the system attempts to obtain the configuration from the location specified in the tertiary-config.

Note that if an error in the configuration file is encountered, the boot process aborts.

The no form of the command removes the secondary-config configuration.

Parameters 
file-url—
Specifies the secondary configuration file location, expressed as a file URL.
Values—

file-url

[local-url | remote-url] (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

secondary-image

Syntax 
secondary-image file-url
no secondary-image
Context 
bof
Description 

This command specifies the secondary directory location for runtime image file loading.

The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.

All runtime image files (*.tim files) must be located in the same directory.

The no form of the command removes the secondary-image configuration.

Parameters 
file-url—
Specifies the file URL; can be either local (this CPM) or a remote FTP server.
Values—

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

tertiary-config

Syntax 
tertiary-config file-url
no tertiary-config
Context 
bof
Description 

This command specifies the name and location of the tertiary configuration file.

The system attempts to use the configuration specified in tertiary-config if both the primary and secondary config files cannot be located. If this file cannot be located, the system boots with the factory default configuration.

Note that if an error in the configuration file is encountered, the boot process aborts.

The no form of the command removes the tertiary-config configuration.

Parameters 
file-url—
Specifies the tertiary configuration file location, expressed as a file URL.
Values—

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

tertiary-image

Syntax 
tertiary-image file-url
no tertiary-image
Context 
bof
Description 

This command specifies the tertiary directory location for runtime image file loading.

The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.

All runtime image files (*.tim files) must be located in the same directory.

The no form of the command removes the tertiary-image configuration.

Parameters 
file-url—
Specifies the file URL; can be either local (this CPM) or a remote FTP server.
Values—

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://|tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

 

4.6.2.5. Management Ethernet Configuration

address

Syntax 
[no] address ip-prefix/ip-prefix-length [active | standby]
Context 
bof
Description 

This command assigns an IP address to the management Ethernet port on the active CPM in the running configuration and the Boot Option File (BOF) or the standby CPM for systems using redundant CPMs. Deleting a BOF address entry is not allowed from a remote session.

Note that changing the active and standby addresses without reboot standby CPM may cause a boot-env sync to fail.

The no form of the command deletes the IP address from the CPM Ethernet port.

Parameters 
ip-prefix/ip-prefix-length—
Specifies the destination address of the aggregate route in dotted decimal notation.
Values—

ipv4-prefix

a.b.c.d (host bits must be 0)

ipv4-prefix-length

0 to 32

ipv6-prefix

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x:

[0 to FFFF]H

d:

[0 to 255]D

ipv6-prefix-length

0 to128

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

 

active | standby—
specifies which CPM Ethernet address is being configured: the active CPM Ethernet or the standby CPM Ethernet.
Default—
active

autonegotiate

Syntax 
[no] autonegotiate
Context 
bof
Description 

This command enables speed and duplex autonegotiation on the management Ethernet port in the running configuration and the Boot Option File (BOF).

When autonegotiation is enabled, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, then the configured duplex and speed parameters are ignored.

The no form of the command disables the autonegotiate feature on this port.

duplex

Syntax 
duplex {full | half}
Context 
bof
Description 

This command configures the duplex mode of the CPM management Ethernet port when autonegotiation is disabled in the running configuration and the Boot Option File (BOF). If the port is configured to autonegotiate this parameter will be ignored.

Parameters 
full—
Sets the link to full duplex mode.
half—
Sets the link to half duplex mode.

ess-system-type

Syntax 
[no] ess-system-type
Context 
bof
Description 

This command allows a new RoHS compliant 7750 SR-12 or 7750 SR-7 chassis to operate as an 7450 ESS-12 or 7450 ESS-7 system.

After entering this command, the system must be rebooted for the change to take effect.

If the RoHS compliant 7750 SR-12 or 7750 SR-7 chassis is operating as an 7450 ESS system, it can operate with either the 7750 SR or 7450 ESS CPM (subject to SR OS support) but both should always be the same type.

In addition, the system can operate with supported 7450 ESS IOMs, MDAs, and IMMs with Layer 2 VPN service licenses. In this mode only 7450 ESS functionality is supported.

The system can also operate in mixed-mode, in which case a mixture of 7750 SR and 7450 ESS IOMs, MDAs, and IMMs are supported, as well as 7450 ESS and 7750 SR functionality. This is subject to all existing requirements and limitations for the mixed-mode feature.

The no version of this command disables this mode of operation and returns the system to a 7750 SR chassis type operation on the next reboot.

Default 

no ess-system-type

fips-140-2

Syntax 
[no] fips-140-2
Context 
bof
Description 

This command is used to configure the node in FIPS-140-2 mode. Before using this command, the operator must ensure that no current configuration exists in the config file that is not supported in FIPS-140-2 mode. Failing to remove unsupported configuration will result in the node being unable to boot up. The node must be rebooted after executing this command in order for the node to begin operating in FIPS-140-2 mode.

li-local-save

Syntax 
[no] li-local-save
Context 
bof
Description 

This command enables the lawful intercept (LI) configuration to be saved locally.

li-separate

Syntax 
[no] li-separate
Context 
bof
Description 

This command enables separate access to lawful intercept (LI) information.

speed

Syntax 
speed speed
Context 
bof
Description 

This command configures the speed for the CPM management Ethernet port when autonegotiation is disabled in the running configuration and the Boot Option File (BOF).

If the port is configured to autonegotiate, this parameter is ignored.

Default 

speed 100

Parameters 
speed—
Sets the link speed, in Mb/s.
Values—
10, 100

 

static-route

Syntax 
[no] static-route ip-prefix/ip-prefix-length next-hop ip-address
Context 
bof
Description 

This command creates a static route entry for the CPM management Ethernet port in the running configuration and the Boot Option File (BOF).

This command allows manual configuration of static routing table entries. These static routes are only used by traffic generated by the CPM Ethernet port. To reduce configuration, manual address aggregation should be applied where possible.

A static default (0.0.0.0/0 or ::/0) route cannot be configured on the CPM Ethernet port. A maximum of 10 static routes can be configured on the CPM port.

The no form of the command deletes the static route.

Default 

no static-route

Parameters 
ip-prefix/ip-prefix-length—
Specifies the destination address of the static route in dotted decimal notation.
Values—

ip-prefix/ip-prefix-length

ipv4-prefix

a.b.c.d (host bits must be 0)

ipv4-prefix-le

0 to32

ipv6-prefix

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x: [0 to FFFF]H

d: [0to 255]D

ipv6-prefix-le

0 to128

ip-address

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x (eight 16-bit pieces)

x:x:x:x:x:x:d.d.d.d

x: [0 to FFFF]H

d: [0 to 255]D

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

 

mask—
Specifies the subnet mask, expressed as an integer or in dotted decimal notation.
Values—
1 to32 (mask length), 128.0.0.0 to255.255.255.255 (dotted decimal)

 

ip-address
Specifies the next hop IP address used to reach the destination.

4.6.2.6. DNS Configuration Commands

dns-domain

Syntax 
dns-domain dns-name
no dns-domain
Context 
bof
Description 

This command configures the domain name used when performing DNS address resolution. This is a required parameter if DNS address resolution is required. Only a single domain name can be configured. If multiple domain statements are configured, the last one encountered is used.

The no form of the command removes the domain name from the configuration.

Default 

no dns-domain

Parameters 
dns-name—
Specifies the DNS domain name up to 178 characters.

primary-dns

Syntax 
primary-dns ip-address
no primary-dns [ip-address]
Context 
bof
Description 

This command configures the primary DNS server used for DNS name resolution. DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.

The no form of the command removes the primary DNS server from the configuration.

Default 

no primary-dns

Parameters 
ip-address—
Specifies the IP or IPv6 address of the primary DNS server.
Values—

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface

32 chars max, for link local addresses

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

 

secondary-dns

Syntax 
secondary-dns ip-address
no secondary-dns [ip-address]
Context 
bof
Description 

This command configures the secondary DNS server for DNS name resolution. The secondary DNS server is used only if the primary DNS server does not respond.

DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.

The no form of the command removes the secondary DNS server from the configuration.

Default 

no secondary-dns

Parameters 
ip-address—
Specifies the IP or IPv6 address of the secondary DNS server.
Values—

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface

32 chars max, for link local addresses

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

 

tertiary-dns

Syntax 
tertiary-dns ip-address
no tertiary-dns [ip-address]
Context 
bof
Description 

This command configures the tertiary DNS server for DNS name resolution. The tertiary DNS server is used only if the primary DNS server and the secondary DNS server do not respond.

DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.

The no form of the command removes the tertiary DNS server from the configuration.

Default 

no tertiary-dns

Parameters 
ip-address—
Specifies the IP or IPv6 address of the tertiary DNS server.
Values—

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface

32 chars max, for link local addresses

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.