Managing Configuration Sessions
Viewing Configuration Error Messages and Descriptions
Configuration changes are automatically verified during the commit operation, and a message appears
if one or more configuration entries fail. To display an error message and description for a failed
configuration, type the show configuration failed command.
You can view configuration errors only during the current configuration session. If you exit
Note
configuration mode after the commit operation, the configuration error information is lost.
In the following example, an error is introduced in global configuration mode and the error information
appears after the commit operation fails:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# taskgroup alr
RP/0/RSP0/CPU0:router(config-tg)# description this is a test of an invalid taskgroup
RP/0/RSP0/CPU0:router(config-tg)# commit
% Failed to commit one or more configuration items. Please use 'show configuration failed'
to view the errors
RP/0/RSP0/CPU0:router(config-tg)# show configuration failed
!! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS
taskgroup alr
!!% Usergroup/Taskgroup names cannot be taskid names
Viewing Configuration Error Messages Without Descriptions
Configuration changes are automatically verified during the commit operation, and a message appears
if one or more configuration entries fail. To display only the error message (without a description) for a
failed configuration, type the show configuration failed noerror command, as shown in the following
example:
RP/0/RSP0/CPU0:router(config-tg)# show configuration failed noerror
!! CONFIGURATION FAILED DUE TO SEMANTIC ERRORS
taskgroup alr
!
You can view configuration errors only during the current configuration session. If you exit
Note
configuration mode after the commit operation, the configuration error information is lost.
Viewing Configuration Error Messages Produced While Loading a Configuration
To display any syntax errors found in a configuration loaded with the load command, type the show
configuration failed load command.
Saving the Target Configuration to a File
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.
Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide
3-26
F I N A L D R A F T — C i s c o C o n f i d e n t i a l
Chapter 3
Configuring General Router Features
OL-17502-01