3-9
Cisco IOS XR Getting Started Guide
Chapter3 Configuring Additional Router Features
Saving and Loading Target Configuration Files
To load rollback configuration changes from the current configuration to a specific session, enter the
load rollback changes to commitId command:
RP/0/0/CPU0:router(config)# load rollback changes to 1000000068
Building configuration...
Loading.
233 bytes parsed in 1 sec (231)bytes/sec
To load rollback configuration changes from the current configuration to a specified number of previous
sessions, enter the load rollback changes last commit-range command:
RP/0/0/CPU0:router(config)# load rollback changes last 6
Building configuration...
Loading.
221 bytes parsed in 1 sec (220)bytes/sec
In the preceding example, the command loads the rollback configuration changes for the last six
commitIDs.
To load the rollback configuration for a specific commitID, enter the load rollback changes commitId
command:
RP/0/0/CPU0:router(config)# load rollback changes 1000000060
Building configuration...
Loading.
199 bytes parsed in 1 sec (198)bytes/sec

Deleting CommitIDs

You can delete the oldest configuration commitIDs by entering the clear configuration commit
command in EXEC mode. The clear configuration commit command must be followed by either the
amount of disk space you want to reclaim or number of commitIDs you want to delete. To reclaim disk
space from the oldest commitIDs, enter the clear configuration commit command followed by the
keyword diskspace and number of kilobytes to reclaim:
RP/0/0/CPU0:router# clear configuration commit diskspace 50
Deleting 4 rollback points '1000000001' to '1000000004'
64 KB of disk space will be freed. Continue with deletion?[confirm]
To delete a specific number of the oldest commitIDs, enter the clear configuration commit command
followed by the keyword oldest and number of commitIDs to delete:
RP/0/0/CPU0:router# clear configuration commit oldest 5
Deleting 5 rollback points '1000000005' to '1000000009'
80 KB of disk space will be freed. Continue with deletion?[confirm]
Saving and Loading Target Configuration Files
Target configurations can be saved to a separate file without committing them to the running
configuration. Target configuration files can then be loaded at a later time and further modified or
committed. The following sections describe how to save and load target configurations:
Saving the Target Configuration to a File, page 3-10
Loading the Target Configuration from a File, page 3-10