5.15. BOF Command Reference

5.15.1. Command Hierarchies

5.15.1.1. Configuration Commands

[no] address ip-prefix/ip-prefix-length [active | standby]
auto-discover [id client-identifier] [vlan vlan-id]
[no] autonegotiate
console-speed baud-rate
dns-domain dns-name
— no dns-domain
duplex {full | half}
encrypt {on | off}
encryption-key key [hash | hash2]
[no] fips-140-2
password password [hash | hash2]
— no password
persist {on | off}
primary-config file-url
primary-dns ip-address
primary-image file-url
save [cflash-id]
secondary-config file-url
secondary-dns ip-address
secondary-image file-url
speed speed
[no] static-route ip-prefix/prefix-length next-hop ip-address
tertiary-config file-url
tertiary-dns ip-address
tertiary-image file-url
wait seconds

5.15.1.2. Show Commands

show
bof [cflash-id | booted]

5.15.2. Command Descriptions

5.15.2.1. Configuration Commands

5.15.2.1.1. File Management Commands

bof

Syntax 
bof
Context 
<root>
Description 

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

A BOF 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 CSM 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.

The pound (#) sign is used at the beginning of the File syntax. Using the command file type bof.cfg displays the # character as a comment delimiter at the top of the raw file. No default BOF exists. The router boots with the factory default boot sequence and options.

Default 

n/a

encrypt

Syntax 
encrypt {on | off}
Context 
bof
Description 

This command enables or disables 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 by a password set with the password command.

After BOF encryption is configured, use the bof save command to save the encrypted file.

Default 

encrypt off

Parameters 
on—
enables BOF encryption
off—
disables BOF encryption

password

Syntax 
password password [hash | hash2]
no password
Context 
bof
Description 

This command configures a password to access the BOF interactive menu at startup.

After the password is configured, the BOF interactive menu is accessible only when the correct password is entered. If the correct password is not entered within 30 s, the node reboots.

The no form of this command removes the configured password.

Default 

no password

Parameters 
password—
specifies the password

If the hash or hash2 parameter is not configured, the password is entered in plaintext and the password length must be between 8 and 32 characters. A plaintext password cannot contain embedded nulls or end with “hash” or “hash2”.

If the hash or hash2 parameter is configured, the password is hashed and the password length must be between 1 and 64 characters.

hash—
specifies that the password is entered in an encrypted form
hash2—
specifies that the password is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the password cannot be transferred between nodes.

save

Syntax 
save [cflash-id]
Context 
bof
Description 

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

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

The BOF is saved to the compact flash drive associated with the active CSM. The slot name is not case-sensitive. You can use uppercase or lowercase “A” or “B”.

Command usage:

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

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

Command usage:

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

The slot name is not case-sensitive. You can use uppercase 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 CSM. Use the show card command to determine the active and standby CSM (A or B).

Default 

saves must be explicitly executed; the BOF is saved to cf3: if a location is not specified

Parameters 
cflash-id—
the compact flash ID where the bof.cfg is to be saved (see Table 16 for parameter descriptions and values)

5.15.2.1.2. BOF Processing Control Commands

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 BOF.

Only one wait command can be defined in the BOF.

Default 

3

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

 

5.15.2.1.3. Console Port Configuration Commands

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 

115200 — console configured for 115 200 b/s operation

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

 

5.15.2.1.4. Image and Configuration Management Commands

encryption-key

Syntax 
encryption-key key [hash | hash2]
no encryption-key
Context 
bof
Description 

This command creates a key for configuration file encryption and hashing using the AES256 cipher algorithm. This key is used for all configuration files (primary, secondary, and tertiary).

After creating the encryption key, use the admin save command to save the encrypted file.

Note:

If the admin rollback save command is used, the rollback files are also encrypted.

The no form of this command deletes the configured encryption key.

Default 

no encryption-key

Parameters 
key—
specifies the encryption key

If the hash or hash2 parameter is not configured, the key is entered in plaintext and the key length must be between 8 and 32 characters. A plaintext key cannot contain embedded nulls or end with “hash” or “hash2”.

If the hash or hash2 parameter is configured, the key is hashed and the key length must be between 1 and 64 characters.

hash—
specifies that the key is entered in an encrypted form
hash2—
specifies that the key is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the key cannot be transferred between nodes.

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, and path IDs. This reduces resynchronizations of the Network Management System (NMS) with the affected network element.

If 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 (.pst) should not be 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 checks to ensure that the disk has enough free space. If there is not enough free space, the persistency will not become active and a trap is generated. The operator must free up adequate disk space before persistency will become active. The system performs a space availability check every 30 seconds. As soon as the space is available the persistency becomes active on the next 30-second check.
Default 

off

Parameters 
on—
preserves the system index when saving the configuration
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 in 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.

Default 

n/a

Parameters 
file-url—
the primary configuration file location (see Table 16 for parameter descriptions)

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.

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

Default 

n/a

Parameters 
file-url—
the location-url can either be local (this CSM) or a remote FTP server (see Table 16 for parameter descriptions)

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.

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

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

Default 

n/a

Parameters 
file-url—
the secondary configuration file location (see Table 16 for parameter descriptions)

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.

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

Default 

n/a

Parameters 
file-url—
the file-url can either be local (this CSM) or a remote FTP server (see Table 16 for parameter descriptions)

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.

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

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

Default 

n/a

Parameters 
file-url—
the tertiary configuration file location (see Table 16 for parameter descriptions)

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 (both.tim) must be located in the same directory.

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

Default 

n/a

Parameters 
file-url—
the file-url can either be local (this CSM) or a remote FTP server (see Table 16 for parameter descriptions)

5.15.2.1.5. CSM Management Configuration Commands

address

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

This command assigns an IP address to the CSM Management port in the running configuration and the BOF on the active CSM, or the CSM Management port on the standby CSM for systems using redundant CSMs.

Either an IPv4 or IPv6 address can be assigned to the CSM Management port. If an address already exists, it will be overwritten with the new address. If no address exists, a new one will be created.

Before changing an active IPv4 or IPv6 address, you must ensure that:

  1. all static routes are removed
  2. the standby address is removed; address changes are not allowed unless both addresses are on the same subnet

In previous releases, if an IPv6 address was assigned to the CSM Management port, an IPv4 address was also required on the port. This setup is no longer required; therefore, for configurations with both IPv4 and IPv6 addresses, the IPv4 address can be deleted from the BOF.

The no form of the command deletes the IP address from the CSM Management port.

If you delete an active IPv4 address from the BOF, or you replace an IPv4 address with an IPv6 address, the following must be considered.

  1. IPv4 static routes must be removed before the IPv4 active address can be deleted.
  2. If remote directory locations are used for the primary image file (primary-image) and primary configuration file (primary-config), you must also change the primary image and primary configuration paths (as well as the secondary and tertiary image and configuration files) to use IPv6 addresses. Otherwise, when the 7705 SAR reboots, it will try to load the image using IPv4, which will cause continuous reboots.
  3. If a primary DNS server is configured (primary-dns), the server address must be changed to an IPv6 address in order for it to be reachable.

If the IPv4 address is removed before any Telnet sessions can be established, Telnet IPv6 servers must be enabled using the config>system>security>telnet6-server command. Refer to the 7705 SAR System Management Guide for the command description.

Caution:

  1. If you have a dual IPv4/IPv6 BOF address configuration and you are running a Telnet IPv6 session or an SSH session, changing or deleting the active IPv4 address will not affect the session.
  2. If you have a dual IPv4/IPv6 BOF address configuration and you are running a Telnet IPv4 session or an SSH session, changing or deleting the active IPv6 address will not affect the session.
  3. If you have a dual IPv4/IPv6 BOF address configuration and you change or delete the active IP address that is the same version as the session (for example, you delete the active IPv4 address while running a Telnet IPv4 session), the session will hang once the change executes, and CLI access will be lost. You can either close the session (if possible) or wait until it times out. You must start a new session, using the new or existing active BOF address, to regain CLI access.
  4. If there is only one active BOF address on the port (that is, not the dual IPv4/IPv6 configuration), and it is deleted through a Telnet or SSH session, the session will hang and CLI access will be lost. You must use a directly connected console session to create a new BOF address. It is strongly recommended that you do not delete a single active BOF address through Telnet or SSH.
Default 

no address — there are no IP addresses assigned to CSM Management ports

Parameters 
ip-prefix/ip-prefix-length—
the IP address for the CSM Management port
Values—

ipv4-prefix

a.b.c.d

ipv4-prefix-length

0 to 30

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 to 126

 

active | standby—
specifies which CSM Management port address is being configured: the active CSM Management port or the standby CSM Management port
Default—
active

auto-discover

Syntax 
auto-discover [id client-identifier] [vlan vlan-id]
no auto-discover
Context 
bof
Description 

This command enables ADP as part of the boot-up sequence by adding an ADP keyword to the BOF file. ADP will run the next time the chassis is rebooted. You can also use this command to specify an optional unique identifier to use in the automatic discovery broadcast. You can use any unique identifier of up to 16 characters. If you specify mac, the chassis MAC address is used. If you run ADP with 802.1q encapsulation, you can specify the VLAN ID.

Parameters 
client-identifier —
 indicates the unique system identifier to use in the auto-discovery broadcast. If you use mac as the client identifier, the chassis MAC address is used.
Values—
any combination of up to 16 alphanumeric characters with no spaces

 

vlan-id—
indicates the VLAN ID for ADP with 802.1q encapsulation
Values—
0 to 4094

 

autonegotiate

Syntax 
[no] autonegotiate
Context 
bof
Description 

This command enables speed and duplex autonegotiation on the CSM Management port in the running configuration and the 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.

Default 

autonegotiate

duplex

Syntax 
duplex {full | half}
Context 
bof
Description 

This command configures the duplex mode of the CSM Management port when autonegotiation is disabled in the running configuration and the BOF.

This configuration command allows for the configuration of the duplex mode of the CSM Management port. If the port is configured to autonegotiate, this parameter will be ignored.

Default 

duplex full — full duplex operation

Parameters 
full—
sets the link to full duplex mode
half—
sets the link to half duplex mode

fips-140-2

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

This command is used to enable the node to support security level 1 of Federal Information Processing Standards 140 series, version 2 (FIPS-140-2). This mode limits the use of cryptographic algorithms on both the CSM and data plane to only those that are in accordance with FIPS-140-2. The node must be rebooted after executing this command in order for the node to begin operating in FIPS-140-2 mode.

Caution:

Before using this command, the operator must ensure that no current configuration exists in the configuration file that is not supported in FIPS-140-2 mode. Failing to remove unsupported configurations will result in the node being unable to boot up.

The no form of the command disables support for security level 1 of FIPS-140-2 on the node.

Default 

no fips-140-2

speed

Syntax 
speed speed
Context 
bof
Description 

This command configures the speed for the CSM Management port when autonegotiation is disabled in the running configuration and the BOF.

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

Default 

100 — 100 Mb/s operation

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

 

static-route

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

This command creates a static route entry for the CSM Management port in the running configuration and the BOF.

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

A static default route (0.0.0.0/0) cannot be configured on the CSM Management port. A maximum of 10 IPv4 and 10 IPv6 static routes can be configured on the CSM Management port.

Each unique next hop of active static routes configured on both the active and standby CSM Management ports are tested every 60 seconds. If the next hop is unreachable, an alarm is raised. The alarm condition is cleared when the preferred static route becomes reachable.

The no form of the command deletes the static route.

Default 

n/a

Parameters 
ip-prefix/prefix-length—
the destination address requiring the static route
Values—
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 to 128

 

next-hop ip-address
the next hop IP address used to reach the destination
Values—
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

 

5.15.2.1.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 — no DNS domain name is configured

Parameters 
dns-name—
the DNS domain name

primary-dns

Syntax 
primary-dns ip-address
no primary-dns
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 — no primary DNS server is configured

Parameters 
ip-address—
the IP address of the primary DNS server
Values—
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

 

secondary-dns

Syntax 
secondary-dns ip-address
no secondary-dns
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 — no secondary DNS server is configured

Parameters 
ip-address—
the IP address of the secondary DNS server
Values—
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

 

tertiary-dns

Syntax 
tertiary-dns ip-address
no tertiary-dns
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 — no tertiary DNS server is configured

Parameters 
ip-address—
the IP address of the tertiary DNS server
Values—
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

 

5.15.2.2. Show Commands

Note:

The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.

bof

Syntax 
bof [cflash-id | booted]
Context 
show
Description 

This command displays the BOF executed on the last system boot or on the specified device.

If no device is specified, the BOF used in the last system boot displays. If the BOF has been modified since the system boot, a message displays.

Parameters 
cflash-id—
the cflash directory name. The slot name is not case-sensitive. Use uppercase or lowercase “A” or “B” for the slot name.
Values—
see Table 16 for parameter descriptions and values

 

booted—
displays the BOF used to boot the system
Output 

The following outputs are examples of BOF information, and Table 24 describes the fields.

Output Example
A:ALU-1# show bof cf3:
===============================================================================
BOF on CF3:
===============================================================================
    primary-image    ftp://*:*@192.168.192.64/cephwreg10/images/both.tim
    primary-config   ftp://*:*@192.168.192.64/cephwreg10/images/dut-a.cfg
    encryption-key   *
    password         *
    address          xxx.xxx.xxx.xx /24 active
    primary-dns      138.120.252.55
    secondary-dns    138.120.252.48
    tertiary-dns     138.120.252.49
    dns-domain       labs.ca.alcatel-lucent.com
    static-route     135.121.0.0/16 next-hop 192.168.192.63
    static-route     138.120.0.0/16 next-hop 192.168.192.63
    static-route     152.148.0.0/16 next-hop 192.168.192.63
    autonegotiate
    duplex           full
    speed            100
    wait             4
    persist          off  
    no fips-140-2         
    console-speed    115200
    encrypt          on
===============================================================================
A:ALU-1#
A:ALU-1# show bof booted
===============================================================================
System booted with BOF
===============================================================================
    primary-image    ftp://*:*@192.168.192.64/cephwreg10/images/both.tim
    primary-config   ftp://*:*@192.168.192.64/cephwreg10/images/dut-a.cfg
    encryption-key   *
    password         *
    address          xxx.xxx.xxx.xx /24 active
    primary-dns      138.120.252.55
    secondary-dns    138.120.252.48
    tertiary-dns     138.120.252.49
    dns-domain       labs.ca.alcatel-lucent.com
    static-route     135.121.0.0/16 next-hop 192.168.192.63
    static-route     138.120.0.0/16 next-hop 192.168.192.63
    static-route     152.148.0.0/16 next-hop 192.168.192.63
    autonegotiate
    duplex           full
    speed            100
    wait             4
    persist          off  
    no fips-140-2         
    console-speed    115200
    encrypt          on
===============================================================================
A:ALU-1#
Table 24:  BOF Field Descriptions 

Label

Description

primary-image

The primary location of the directory that contains the runtime images of the CSM

primary-config

The primary location of the file that contains the configuration

encryption-key

The encrypted encryption key

password

The encrypted password

address

The IP address and mask associated with the CSM Management port or the secondary CSM Management port

primary-dns

The primary DNS server for resolution of host names to IP addresses

secondary-dns

The secondary DNS server for resolution of host names to IP addresses

tertiary-dns

The tertiary DNS server for resolution of host names to IP addresses

dns-domain

The domain name used when performing DNS address resolution

static-route

The static route entry for the CSM Management port in the running configuration and the BOF

autonegotiate

no autonegotiate — autonegotiate is not enabled

autonegotiate — autonegotiate is enabled

duplex

half — specifies that the system uses half duplex

full — specifies that the system uses full duplex

speed

The speed of the CSM Ethernet interface

wait

The time configured for the boot to pause while waiting for console input

persist

Indicates whether the system will preserve system indexes when a save command is executed

fips-140-2

Indicates whether FIPS-140-2 is enabled on the node

console speed

The console port baud rate

encrypt

on — BOF encryption is enabled

off — BOF encryption is not enabled

boot-messages

Syntax 
boot-messages
Context 
show
Description 

This command displays boot messages generated during the last system boot.

Output 

The following output is an example of boot messages.

Output Example
A:ALU-1# show boot-messages 
===============================================================================
cf3:/bootlog.txt
===============================================================================
Boot log started on CPU#0
  Build: X-2.1.R1 on Tue Apr 1 16:25:56 EDT 2016 by csabuild
 
Total Memory: 992MB  Chassis Type: sar8  Card Type: corona_r1
TiMOS-L-2.1.R1 boot/hops NOKIA SAR 7705
Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 9 09:36:02 EDT 2016 by csabuild in /rel2.0/b1/R1/panos/main
 
TiMOS BOOT LOADER
Time from clock is FRI APR 11 13:31:16 2016 UTC
Switching serial output to sync mode...
Total Memory: 992MB  Chassis Type: sar8  Card Type: corona_r1
 
TiMOS-B-2.1.R1 both/hops NOKIA SAR 7705
Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 9 09:53:01 EDT 2016 by csabuild in /rel2.0/b1/R1/panos/main
 
   ___                    ___           ___           ___
  /\  \                  /\__\         /\  \         /\  \
  \:\  \        ___     /::|  |       /::\  \       /::\  \
   \:\  \      /\__\   /:|:|  |      /:/\:\  \     /:/\ \  \
   /::\  \    _\/__/  /:/|:|__|__   /:/  \:\  \   _\:\~\ \  \
  /:/\:\__\  /\__\   /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \ \__\
 /:/  \/__/ /:/  /   \/__/~~/:/  / \:\  \ /:/  / \:\ \:\ \/__/
/:/  /     /:/  /          /:/  /   \:\  /:/  /   \:\ \:\__\
\/__/      \/__/          /:/  /     \:\/:/  /     \:\/:/  /
                         /:/  /       \::/  /       \::/  /
                         \/__/         \/__/         \/__/
 
Time from clock is FRI APR 11 13:31:57 2016 UTC
Initial DNS resolving preference is ipv4-only
 
CRITICAL: CLI #1001 Cannot locate the configuration file -
Using default configuration values.
 
MAJOR: CLI #1008 The SNMP daemon is disabled.  To enable SNMP, execute the comma
nd 'config>system>snmp no shutdown'.
TiMOS-B-2.1.R1 both/hops NOKIA SAR 7705
Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 9 09:53:01 EDT 2016 by csabuild in /rel2.0/b1/R1/panos/main
 
 
Login: 
===============================================================================
cf3:/bootlog_prev.txt
===============================================================================
Boot log started on CPU#0
  Build: X-2.1.R1 on Tue Apr 1 16:25:56 EDT 2016 by csabuild
 
Total Memory: 992MB  Chassis Type: sar8  Card Type: corona_r1
TiMOS-L-2.1.R1 boot/hops NOKIA SAR 7705
Copyright (c) 2016 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Apr 9 09:36:02 EDT 2016 by csabuild in /rel2.0/b1/R1/panos/main
 
TiMOS BOOT LOADER
Time from clock is FRI APR 11 13:30:38 2016 UTC
Switching serial output to sync mode...
 
reboot
===============================================================================