Table Of Contents
Boot Commands on Cisco IOS XR Software
config-register
reload
reload location
show system backup
show variables boot
show variables system
system backup
system boot-sequence
Boot Commands on Cisco IOS XR Software
This chapter describes the commands used to boot or reset the Cisco IOS XR software.
For more information about ROM Monitor (ROMMON) and boot tasks, see Cisco IOS XR Getting Started Guide.
config-register
To define the configuration register boot value, use the config-register command in administration EXEC mode.
config-register value [location all]
Syntax Description
value
|
Hexadecimal or decimal value that represents the 16-bit configuration register value to be used the next time the router is reloaded. Range is from 0x0 to 0xFFFF (0 to 65535 in decimal).
For information about common configuration register settings, see Table 1.
|
location all
|
Specifies all RP nodes in a multishelf system.
|
Defaults
Enter the command config-register value to set the configuration register setting for the DSC (DSDRSC of the owner SDR).
By default, the configuration register value is 0x102 after a TURBOBOOT.
Command Modes
Administration EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was first supported on the Cisco XR 12000 Series Router. This command was moved from global configuration mode to Administration configuration mode.
|
Release 3.3.0
|
Support was added for the location all keywords.
|
Release 3.4.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The configuration register setting is a 16-bit, user-configurable value that determines how the primary route processor (RP) functions during initialization. The configuration register can cause the RP to boot normally from the default configuration, or to enter ROMMON mode during a reload. Configuration register settings can also be used to perform tasks such as password recovery.
The config-register command is entered in administration EXEC mode, on the designated system controller (DSC) of the system. The DSC is the primary RP of the owner secure domain router (owner SDR). When setting the configuration register value for the config-register command, note the following conditions:
•
If both the primary and standby DSC are up and running when the configuration register value is set, the configuration register value applies to both the primary and standby DSC.
•
By contrast, if only the primary DSC is up and running when the configuration register value is set and the standby DSC is introduced into the router at a later time, the router does not attempt to synchronize the configuration register value for the standby RP to that of the active RP; in this situation, the configuration register setting applied to the standby DSC is determined by the configuration register value set in ROMMON mode.
•
To set the configuration register value for all RPs in a multishelf system, enter the command config-register value location all.
Note
To display the current configuration settings, use the command show variables boot.
The most commonly used configuration register settings are described in Table 1.
Table 1 Common Configuration Register Settings
Value
|
Description
|
0x0
|
RP enters ROMMON mode (rommon B1>) on the next system boot.
|
0x2
|
RP loads the Cisco IOS XR software software and default configuration on the next system boot. After logging in, the user can access EXEC mode.
|
0x102
|
Router disables the break key.
|
0x40
|
Router enters the password recovery mode on the next system boot.
|
Task ID
Task ID
|
Operations
|
root-lr
|
read, write
|
Examples
The following example shows how to set the configuration register on the DSC to 0x2. Setting the configuration registration to 0x2 causes the router to boot the Cisco IOS XR software and enter EXEC mode during a router reload.
RP/0/RP0/CPU0:router(admin)# config-register 0x2
Successfully set config-register to 0x2 on node 0/RP0/CPU0
Successfully set config-register to 0x2 on node 0/RP1/CPU0
Related Commands
Command
|
Description
|
reload
|
Defines how the node functions during a reset operation in ROMMON mode.
|
show variables boot
|
Displays the RP configuration register setting.
|
show version
|
Displays information on the Cisco IOS XR software.
|
reload
To reload the designated secure domain router system controller (DSDRSC), use the reload command in EXEC mode.
reload [force]
Syntax Description
force
|
(Optional) Forces the reload without performing any cleanup.
|
Defaults
The reload process performs cleanup.
Command Modes
EXEC
Command History
Releases
|
Modifications
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the reload command to cause the DSDRSC to reload the Cisco IOS XR software according to the configuration register setting (for example, 0x0 to enter ROMMON mode and 0x2 to reload the RP to EXEC mode). If a standby DSDRSC is in the ready redundancy state, the reload command also causes the router to failover to the standby DSDRSC. Use the show redundancy command in EXEC mode to display the status of the standby RP.
When the reload command is used and a failover occurs, the running (active) software configuration is automatically maintained during failover.
Caution 
If a standby RP is not installed or is not in the ready state, then the router experiences a loss of service while the active RP is reloading the Cisco IOS XR software. To view the status of the standby RP, issue the
show redundancy command in EXEC mode.
Task ID
Task ID
|
Operations
|
root-lr
|
execute
|
Examples
The following example shows how to reload the active RP. If a standby RP is in Ready state, then the router fails over to the standby RP. If the standby RP is not installed or not in Ready state, then the router enters ROMMON mode and routing operations stop.
RP/0/RP0/CPU0:router# reload
Updating Commit Database. Please wait...[OK]
Proceed with reload? [confirm] y
PCI0 device[7]: Vendor ID 0x10ee
PCI0 device[7]: Device ID 0x300e
PCI1 device[7]: Device ID 0x1100
PCI1 device[7]: Vendor ID 0x1013
PCI1 device[8]: Device ID 0x649
PCI1 device[8]: Vendor ID 0x1095
PCI1 device[9]: Device ID 0x5618
PCI1 device[9]: Vendor ID 0x14e4
PCI1 device[10]: Device ID 0x5618
PCI1 device[10]: Vendor ID 0x14e4
System Bootstrap, Version 1.15(20040120:002852) ,
Copyright (c) 1994-2004 by cisco Systems, Inc.
Board type is 0x100000 (1048576)
Broadcom 5618 #0 Found on PCI
Broadcom 5618 #1 Found on PCI
No. of BCM 56xx switches found 2 .
BCM Switch #0 initialisation complete.
BCM Switch #1 initialisation complete
G4(7450-SMP-GT64260_A) platform with 2048 Mb of main memory
Related Commands
Command
|
Description
|
config-register
|
Defines the configuration register setting in administration EXEC mode.
|
reload
|
Defines how the node functions during a reset operation in ROMMON mode.
|
reload location
|
Performs a reload of a single node or all nodes in the system.
|
show redundancy
|
Displays the redundancy status of the RPs.
|
reload location
To reload a node or all nodes on a single chassis or multishelf system, use the reload location command in the administration EXEC mode.
reload location [node-id | all] [rack rack-number] [force]
Syntax Description
node-id
|
The node-id argument is expressed in rack/slot/module notation.
|
all
|
Reloads all the nodes in the system.
|
force
|
Forces a node reload without cleaning up the data.
|
rack
|
Reloads all the nodes on a specified chassis.
|
rack-number
|
The rack number of the line card chassis or fabric chassis.
|
Defaults
The default behavior for reload is the force option.
Command Modes
Administration EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Before reloading nodes on a Cisco CRS-1, we recommend using the cfs check command to check the sanity of the configuration file system and attempt to recover from internal inconsistencies.
Enter the cfs check command on each SDR that has nodes impacted by the reload. If you enter the reload location all command, run the cfs check command on every SDR in the system before reloading the router.
•
To reload all the nodes in all chassis in a multishelf system, use the reload location all command.
•
To reload all the nodes in a specific chassis, use the reload location rack rack-number command. This command cannot be used to reload the DSC line card chassis in Release 3.3.0 (rack 0). DSC failover between racks is not supported in this release.
•
To reload a specific node on the router specify the reload location node-id command. The node-id is expressed rack/slot/module.
•
To ensure a graceful reload and ensure the sanity of the configuration file system, enter the cfs check command on each SDR that has nodes impacted by the reload.
Task ID
Task ID
|
Operations
|
root-system
|
execute
|
Examples
The following example shows how to reload all the nodes on the router:
RP/0/RP0/CPU0:router(admin)# reload location all
Graceful reload of all nodes not supported
Operation may result in file corruptions or loss of config. Proceed [Y/N]? Y
Note
To ensure the sanity of the configuration file system, enter the cfs check command on each SDR impacted by the reload operation. If you enter the reload location all command, run the cfs check command on every SDR in the system before reloading the router.
The following example shows how to reload all the nodes in a single chassis:
RP/0/RP0/CPU0:router(admin)# reload rack 1
Graceful reload of a rack in admin mode is not supported
Operation may result in file corruption or loss of config. Proceed? [confirm]
In Release 3.3.0, you cannot reload the chassis containing the DSC. The following example shows the message displayed if an attempt is made to reload rack 0 (line card chassis 0) in a multishelf system:
RP/0/RP0/CPU0:router(admin)# reload rack 0
Reload of rack 0 is not supported in 3.3 release.
Related Commands
Command
|
Description
|
cfs check
|
Verifies the Configuration File System (CFS).
|
config-register
|
Defines the configuration register setting in administration EXEC mode.
|
reload
|
Defines how the node functions during a reset operation in ROMMON mode.
|
reload
|
Performs a reload of the route processor.
|
show redundancy
|
Displays the redundancy status of the RPs.
|
show system backup
To display the system backup details and history, use the show system backup command in EXEC and administration EXEC mode.
show system backup [target-dev] [details | diff] [verify] [location {all | node-id}]
Syntax Description
target-dev
|
(Optional) Displays the backup details and history for the specified device.
|
details
|
(Optional) Lists the software packages and configurations stored on the specified backup device.
|
diff
|
(Optional) Displays the differences between the software packages and configuration files on the backup device, with the packages and configuration files on the current boot device.
|
verify
|
(Optional) Verifies the software packages and configuration files stored on the specified backup device.
|
location node-id
|
(Optional) Displays information for a designated RP node.
|
location all
|
(Optional) Displays information for all RP nodes.
|
Defaults
Enter the show system backup command without keywords or arguments to display the date, time and status of the last backup for the current DSDRSC. This command also displays the configured primary and secondary boot devices.
Command Modes
EXEC
Administration EXEC
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show system backup command to display details of the current system backup on a local storage device.
•
Enter the show system backup command to display information on the backup performed for the active RP where you are logged in, including the date, time and status of the last backup.
•
Enter the show system backup target-dev command to display backup information for a specified device on a RP node.
•
Enter the show system backup details command to list information about the software packages and configuration files stored on the backup device.
•
Enter the show system backup diff command to display the differences between the software and configurations on the backup device and the software and configurations on the currently active boot disk.
•
Enter the show system backup location command with the location node-id keyword and argument to display information for a backup on a specific node. Use the location all keywords to display information for backups on all nodes in the system.
Command Modes
•
To display information for the current SDR, enter the show system backup command in the EXEC mode of that SDR.
•
When the command is entered in administration EXEC mode, the backup information for the owner SDR is displayed.
Task ID
Task ID
|
Operations
|
root-lr
|
execute
|
Examples
In the following example, the show system backup command displays the status of the last system backup:
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# show system backup
System Backup information for node0_0_CPU0 on disk1:
=======================================================
Backup started at Sat Jun 24 12:22:10 2006
ended at Sat Jun 24 12:42:11 2006
Verify started at Sat Jun 24 12:42:12 2006
ended at Sat Jun 24 12:48:47 2006
BOOT_DEV_SEQ_CONF=disk0:;disk1:
BOOT_DEV_SEQ_OPER=disk0:;disk1:
In the following example, the show system backup command is entered with the details keyword to display additional information on the configuration and software package files stored on the backup device. Because this command is entered in administration EXEC mode, the backup information for both the administration and SDR configurations is displayed.
RP/0/0/CPU0:router(admin)# show system backup details
System Backup information for node0_0_CPU0 on disk1:
=======================================================
Backup started at Sat Jun 24 12:22:10 2006
ended at Sat Jun 24 12:42:11 2006
Verify started at Sat Jun 24 12:42:12 2006
ended at Sat Jun 24 12:48:47 2006
BOOT_DEV_SEQ_CONF=disk0:;disk1:
BOOT_DEV_SEQ_OPER=disk0:;disk1:
Admin configuration last commit record on disk1:
Device Commitid Time Stamp
disk1: 2000000010 23:07:59 UTC Fri Jun 09 2006
SDR configuration last commit record on disk1:
Device Commitid Time Stamp
disk1: 1000000030 11:56:43 UTC Thu Jun 22 2006
Active software packages on disk1:
No Inactive software packages on disk1:
In the following example, backup information is displayed for backups located on disk1 in all RPs in the system. In this example, a separate backup was created on disk1 of node 0/3/CPU0 for a non-owner SDR.
RP/0/0/CPU0:router(admin)# show system backup disk1: location all
System Backup information for node0_0_CPU0 on disk1:
=======================================================
Backup started at Sat Jun 24 12:22:10 2006
ended at Sat Jun 24 12:42:11 2006
Verify started at Sat Jun 24 12:42:12 2006
ended at Sat Jun 24 12:48:47 2006
BOOT_DEV_SEQ_CONF=disk0:;disk1:
BOOT_DEV_SEQ_OPER=disk0:;disk1:
System Backup information for node0_3_CPU0 on disk1:
=======================================================
Backup started at Sat Jun 24 13:02:23 2006
ended at Sat Jun 24 13:21:30 2006
Verify started at Sat Jun 24 13:21:30 2006
ended at Sat Jun 24 13:27:55 2006
BOOT_DEV_SEQ_CONF=disk0:;disk1:
BOOT_DEV_SEQ_OPER=disk0:;disk1:
Table 2 describes the significant fields shown in the display.
Table 2 show system backup Field Descriptions
Field
|
Description
|
BOOT_DEV_SEQ_CONF=
|
ROM Monitor environmental variable for the boot disk sequence. This variable is defined by the system boot-sequence command. The first disk is the primary device; the second disk is the backup (secondary) device. The value listed in the secondary device is also used as the default backup target device for the system backup command.
|
BOOT_DEV_SEQ_OPER=
|
ROM Monitor environmental variable for the boot disks currently in use by the system.
|
Related Commands
Command
|
Description
|
system boot-sequence
|
Defines the order of boot devices used to bring up a router. The secondary device argument also defines the default backup target device used by the system backup command.
|
system backup
|
Performs a backup of software and configuration files.
|
show variables boot
To display the configuration register setting and boot file setting for the RPs in the system, use the show variables boot command in administration EXEC mode.
show variables boot
Syntax Description
This command has no arguments or keywords.
Defaults
No defaults behavior or values
Command Modes
Administration EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show variables boot command to display system boot variables for the router. This command displays the configuration register setting and boot file setting for the RPs in the system.
The configuration register setting is set with the command config-register. The boot variable is set in ROM Monitor mode. For more information on ROM Monitor mode, see Cisco IOS XR ROM Monitor Guide.
Task ID
Task ID
|
Operations
|
root-lr
|
read
|
Examples
The following is sample output from the show variables boot command:
RP/0/RP0/CPU0:router# show variables boot
BOOT variable = disk0:hfr-os-mbi-3.3.30/mbihfr-rp.vm,1;
BOOT variable = disk0:hfr-os-mbi-3.3.30/mbihfr-rp.vm,1;
Related Commands
Command
|
Description
|
config-register
|
Defines the configuration register setting in administration EXEC mode.
|
show variables system
|
Displays internal system environmental variables set on the router.
|
show version
|
Displays information on the Cisco IOS XR software.
|
show variables system
To display internal system environmental variables set on the router, use the show variables system command in EXEC mode.
show variables system
Syntax Description
This command has no arguments or keywords.
Defaults
No defaults behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was first supported on the Cisco XR 12000 Series Router. Removed the boot keyword.
|
Release 3.3.0
|
No modification.
|
Release 3.4.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show variables system command to display system environmental variables for the router.
The boot keyword was removed from the show variables system command in Cisco IOS XR Software Release 3.2. To display the configuration register setting, use the show variables boot command in administration EXEC mode.
Task ID
Task ID
|
Operations
|
basic-services
|
read
|
Examples
The following is sample output from the show variables system command. The output is meant to be interpreted by Cisco personnel.
RP/0/RP0/CPU0:router# show variables system
BFM_CONFIG_PATH=/pkg/bfm/config
CONFIGS_PATH=/pkg/configs
DM_RULES_PATH=/pkg/dm/rules
INIT_STARTUP_PATH=/pkg/init.d
INSTHELPER_PATH=/pkg/other
MIB_LIBRARY_PATH=/pkg/lib/mib
NETIO_SCRIPT_PATH=/pkg/script
PARTITIONS_PATH=/pkg/partitions
STARTUP_PATH=/pkg/startup
UCODE_PATH=/pkg/gsr/ucode
UCODE_ROOT_PATH=/pkg/ucode
VCM_RULES_PATH=/pkg/vcmrules
SYSMGR_NODE=node0_RP0_CPU0
Related Commands
Command
|
Description
|
config-register
|
Defines the configuration register setting in administration EXEC mode.
|
show variables boot
|
Displays the configuration register setting and boot file setting for the RPs in the system.
|
show version
|
Displays information on the Cisco IOS XR software.
|
system backup
To back up the system software and configurations to a backup disk, use the system backup command in EXEC or administration EXEC mode.
system backup [target-dev] [format] [location {all | node-id}] [synchronous | asynchronous]
Syntax Description
target-dev
|
(Optional) Specifies the storage device used for the system backup. If a target device is not specified, then the secondary device defined with the system boot-sequence command is used. If a target device is not specified with either command, then the system backup command will return an error.
• The target device cannot be the current boot device.
• The target device must be large enough to store the current software set and configuration.
• On the Cisco XR 12000 Series Router, the supported storage devices are disk0, disk1, and compactflash (if installed).
• On the Cisco CRS-1, the supported storage devices are disk0 and disk1 (if installed).
|
format
|
(Optional) Formats a target disk that already contains a system backup.
By default, the system backup command formats the target disk if that target disk does not contain a previous system backup. If the target disk already contains a backup, then the disk is not formatted again. The format keyword forces a format of the target device even if it contains a previous system backup.
|
location node-id
|
(Optional) Specifies an alternative node location for the backup target disk, such as the standby DSDRSC.
By default, the backup files are copied to the target device in the current DSDRSC. Use the location node-id keyword and argument to specify an alternative node for the backup files, such as the standby DSDRSC.
The node-id argument is expressed in rack/slot/module notation.
|
location all
|
(Optional) Backs up the software and configuration files to all RPs in the system or SDR. Each RP must contain a disk in the specified target device location, such as disk1.
|
asynchronous
|
(Optional) Performs the command in asynchronous mode. In asynchronous mode, the command runs in the background, and the EXEC prompt is returned as soon as possible.
|
synchronous
|
(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned. This is the default mode.
|
Defaults
The operation is performed in synchronous mode.
The backup files are copied to the secondary device defined with the system boot-sequence command.
The backup files are copied to the target device on the current DSDRSC.
Command Modes
EXEC
Administration EXEC
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Target Device for the Backup
Use the system backup command with the target-dev argument to specify the local storage device for backup software and configuration files. The target-dev argument is optional and applies only to the current backup operation.
•
If a target storage device is not specified, then the files are backed up to the defined by the secondary storage device defined with the system boot-sequence command.
•
If a target device is not specified with either the system backup target-dev command or the system boot-sequence command, then the backup operation is not allowed.
The target-dev can be any local storage device except the current boot device, and must be large enough to store the current software set and configuration. On the Cisco XR 12000 Series Router, the supported storage devices are disk0, disk1, and compactflash (if installed). On the Cisco CRS-1, the supported storage devices are disk0 and disk1 (if installed).
Location Node of the Target Device
By default, the backup is created on the specified target device of the active DSDRSC where the command is executed.
•
To specify an alternate node for the system backup, such as the standby DSDRSC, use the system backup command with the location node-id keyword and argument.
•
To perform the backup on all RPs installed in a specified SDR, use the system backup command with the location all keywords in EXEC mode.
•
To perform the backup on all RPs in all SDRs installed in the system, use the system backup command with the location all keywords in administration EXEC mode.
Note
Each RP or DRP impacted by the system backup command must contain the specified target device. For example, if the system backup command is executed for disk1 on all RPs in the system, then a flash disk must be installed in disk1 of each RP.
Command Modes
•
Use the system backup command in administration EXEC mode to back up the administration plane configuration, including software and configurations for all SDRs in the system.
•
Use the system backup command in the EXEC mode of an SDR to back up the software and configurations for a specific SDR.
Commit and Install Operations Not Allowed During Backup
•
Configuration changes are not allowed during the backup process. Any attempts to commit configuration changes are rejected until the backup operation is complete.
•
The backup process cannot be performed during an install operation. If an install operation is performed while a backup is in process, the backup operation terminates.
Displaying the Current Backup Information
Enter the show system backup command to display information about the current backup files. If no backup exists, an error message is displayed.
Task ID
Task ID
|
Operations
|
root-lr
|
read, write
|
Examples
The following example shows how To back up the software and configuration files for a Cisco XR 12000 Series Router.
•
The command is run in administration EXEC mode, which backs up both the administration and SDR configurations.
•
The target device is defined as disk1.
•
Because this is the first backup on the device, the disk is formatted.
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# system backup disk1:
Info: node0_0_CPU0: formatting target device
Info: node0_0_CPU0: copying admin configuration
Info: node0_0_CPU0: copying SDR configuration
Info: node0_0_CPU0: copying installed software
Info: node0_0_CPU0: backup complete.
Info: node0_0_CPU0: verifying admin configuration
Info: node0_0_CPU0: verifying installed software
Info: node0_0_CPU0: verify complete.
Info: node0_0_CPU0: command succeeded.
Related Commands
Command
|
Description
|
show system backup
|
Displays the system backup settings and history.
|
system boot-sequence
|
Defines the order of boot devices used to bring up a router. The secondary device argument also defines the default backup target device used by the system backup command.
|
system backup
|
Performs a backup of software and configuration files.
|
system boot-sequence
To define the order of local storage devices used to boot a router, use the system boot-sequence command in EXEC or administration EXEC mode.
system boot-sequence {primary-device [secondary-device] | disable} [location {all | node-id}]
Syntax Description
primary-device
|
Defines the default device where software packages are installed and run. This device is also the default location for router configurations. The value of the primary-device argument is normally disk0.
|
secondary-device
|
Defines the secondary (backup) boot device, used by the system backup command To back up system software and configurations.
• On the Cisco XR 12000 Series Router, the supported storage devices are disk0, disk1, and compactflash (if installed).
• On the Cisco CRS-1, the supported storage devices are disk0 and disk1 (if installed).
Note The value of the secondary-device argument must be different from the value of the primary-device argument.
|
disable
|
Temporarily disables the automatic recovery mechanism (not supported in Release 3.4.0).
|
location node-id
|
Defines the boot sequence on any RP in the current SDR. The node-id argument is expressed in rack/slot/module notation.
|
location all
|
Defines the boot sequence on all RPs in all SDRs.
|
Defaults
The primary device is disk0. The (optional) secondary boot device is not defined.
Command Modes
EXEC
Administration EXEC
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the system boot-sequence command to define the local storage devices used to boot a router. You can define two devices with this command:
•
The value of the primary-device argument defines the default device where software packages are installed and run. This device is also the default location for router configurations.
•
The value of the secondary-device argument defines the device used by the system backup command To back up system software and configurations. This field is optional.
•
The secondary device can also be temporarily defined when the system backup command is executed with the target-device argument. Use the system boot-sequence command with the secondary-device argument to permanently define the secondary (backup) device.
Note
The primary and secondary device definitions remain in effect until the system boot-sequence command is entered again.
General Usage Guidelines
•
The value of the secondary-device argument must be different from the value of the primary-device argument.
•
We recommend disk0 as the primary boot device in the boot sequence, and disk1 as the secondary boot device.
•
The boot device specified with the system boot-sequence command must be installed in the card, or the command is rejected.
Command Modes
•
Use the system boot-sequence command in administration EXEC mode to define the boot sequence for all SDRs in the system.
•
Use the system boot-sequence command in EXEC mode to define the boot sequence for a specific SDR.
Location Node
•
Use the location node-id keyword and argument to define the boot sequence for a specific RP.
•
Use the location all keywords to define the boot sequence for all RPs in the SDR. Use this command in administration EXEC mode to define the boot sequence for all RPs in all SDRs.
Disabling Automatic Recovery
Use the system boot-sequence command with the disable keyword to disable the automatic recovery.
Note
Automatic recovery is not supported in Release 3.4.0.
Displaying the Current Boot Sequence Settings
Enter the show system backup command to display the currently configured boot sequence devices.
Task ID
Task ID
|
Operations
|
root-lr
|
read, write
|
Examples
The following example show how to define the primary and secondary boot device for the active RP (DSC). In this example, the default location for software and configurations is disk0. The location for backups of software and configurations is disk1.
RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# system boot-sequence disk0: disk1:
Info: node0_0_CPU0: command succeeded.
Related Commands
Command
|
Description
|
system backup
|
Performs a backup of software and configuration files.
|
show system backup
|
Displays the system backup settings and history.
|