Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the abort command to terminate a configuration session and return to EXEC mode from any configuration mode. This command discards all uncommitted configuration changes. You are prompted to commit the changes.

Usage Guidelines

Use the admin command to enter Admin EXEC mode mode. Administration commands are used to execute various administration plane commands.

Note	Administration commands can be run only by entering administration mode and not by prefixing the admin command with the keyword in EXEC mode mode.

Usage Guidelines

This command should not be used unless specifically requested by Cisco TAC or another Cisco support representative.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Cisco IOS XR software supports generic alias definitions for various entities. Any physical or logical entity can have an alias as a reference. For example, an alias can refer to a command, a partial command, a group of commands, a location, or an IP address.

An alias must first be defined. The alias can then be used in command lines in place of the defined entity.

Following is a list of properties for an alias:

• An alias can be used anywhere and in any mode.
• An alias can have zero, one, or many parameters.
• An alias can refer to those parameters with the $ sign.
• If an alias refers to more than one command, the commands must be separated by a semicolon (;).
• The size of the alias command is limited to 1024 characters.

The alias command can be used anywhere. If the content referenced by the alias is invalid or inappropriate in that context or mode, the system issues a warning message containing the substituted content.

An alias name should not be a subset of the keywords that it represents as alias. Substitution is done only when the entered input match fails completely. For instance, the attempt to define an alias with “config? as the alias name fails, as shown in the following example:

RP/0/RSP0/CPU0:router(config)# alias config set_host hostname router
RP/0/RSP0/CPU0:router(config)# show configuration

alias set_host hostname router
  

Use the show aliases command to display all command aliases or the command aliases in a specified mode.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Configuration statements in configuration groups come into effect only when the configuration groups are applied in the system configuration, and the configuration statements have the correct context and inheritance priority in the mode in which the configuration groups are applied. The maximum number of configuration groups that can be specified in a single apply-group command is eight.

To change the composition of an apply-group command, you must specify all desired groups. For example, if you used the command apply-group g10 g20 g30, and now you want to add the group g15, use the command apply-group g10 g15 g20 g30. If you now want to delete group g20, use the command apply-group g10 g15 g30. If you use the no apply-group command, all groups are removed from the configuration.

Note	From the Release 6.3.1 onwards, you are able to enter the Flexible CLI config group definition, apply-group and exclude-group command in any order as long as the entire commit has all the group definitions needed.

Note	Use multi-line configuration style to configure Flexible CLI configuration groups by entering each configuration mode in a separate line, one configuration per line. This is important so that the configuration properties are fully inherited and for better readability during troubleshooting.

Usage Guidelines

Consider, you have configured four groups, g10 g20 g30 g40 using the apply-group command. To remove g20, you can use the apply-group-remove command to edit the apply-group command configuration.

Note	This command is not a configuration command and will not be seen in show configuration or show run commands.

Note	This command has to be executed in the same configuration mode as the apply-group command used to configure the groups.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the apply-template command to apply a template to the target configuration. Templates allow you to create a template name that represents a group of configuration commands.

Use the template command to define a template. Use the end-template command to exit template configuration mode and return to global configuration mode. Use the show-running command with the optional template template-name keyword and argument to display the contents of a template.

Task ID

Usage Guidelines

The clear comment command clears any comments that were added for a specific configuration in the configuration file. After you enter the clear comment command, enter the configuration for which you want to delete the comment on a separate line.

To enter configuration comments, enter ! followed by the comment. The comment you enter is associated with the next configuration entered. For example:

RP/0/RSP0/CPU0:router#!router1 is located in xxx
RP/0/RSP0/CPU0:router# hostname router1
RP/0/RSP0/CPU0:router# commit
  

The comment is displayed in the output of the show running-config command:

RP/0/RSP0/CPU0:router# show running-config
...
!router1 is located in xxx
hostname router1
...
  

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the clear configuration commits command to delete the number of commit IDs available for rollback operations. The most recent 100 commits are retained by the system. As new commit IDs are added, the oldest commit IDs are discarded and are no longer available for rollback operations.

Note	The clear configuration commits command deletes commits from the commit database only. The running configuration, thus, is not changed.

Note	When a commit ID is deleted from the commit database, it is no longer available for rollback and can no longer be used to display commit changes (with the show configuration rollback changes command).

Use the rollback configuration command to roll back the current running configuration to a previous configuration. Use the show configuration rollback changes command to display a list of the commit IDs available for rollback operations or to display the changes that would be made by the rollback configuration command.

Task ID

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

An inconsistency alarm is set when there is a failure to restore the configuration; this can occur during router startup, or when a line card or route switch processor (RSP) card is inserted or removed.

If an inconsistency alarm is set, a message similar to the following example is displayed:

RP/0/0/CPU0:May 26 11:58:40.662 : cfgmgr-rp[130]: %MGBL-CONFIGCLI-3 
   BATCH_CONFIG_FAIL : 28 config(s) failed during startup. To view 
   failed config(s) use the command - "show configuration failed startup"
  
RP/0/0/CPU0:May 26 11:58:41.731 : cfgmgr-rp[130]: 
   %MGBL-CONFIG-3-ADMIN_INCONSISTENCY_ALARM : Admin plane configuration
   inconsistency alarm has been raised. Configuration commits will be
   blocked until an ADMIN plane 'clear configuration inconsistency' command
   has been run to synchronize persisted admin plane configuration with 
   running admin configuration.
    

When the inconsistency alarm is set, all configuration commit operations fail until the alarm is cleared using the clear configuration inconsistency command. This command clears the alarm and removes the failed configuration.

For example, the following configuration commit fails to finish due to an existing inconsistency alarm:

RP/0/RSP0/CPU0:router# configure 
  
ADMIN plane running configuration is inconsistent with persistent 
  configuration.
No configuration commits will be allowed until an admin plane 
'clear configuration inconsistency' command is performed.
RP/0/RSP0/CPU0:router(config)# hostname router2
RP/0/RSP0/CPU0:router(config)#commit
  
ADMIN plane running configuration is inconsistent with persistent 
  configuration.
No configuration commits will be allowed until an admin plane 
'clear configuration inconsistency' command is performed.
    

Enter the clear configuration inconsistency command to clear the alarm and allow commit operations to continue.

Note	To reapply the failed configuration, you must reapply and recommit the configuration. Use the load configuration failed command with the startup keyword to populate the target configuration with the contents of the previous failed configuration from the startup configuration.

Use the show configuration history command with the alarm keyword to view the inconsistency alarm set and alarm clear events in the configuration history log.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

In administration EXEC mode, the replica node for the clear configuration inconsistency replica command is the standby designated system controller (DSC). In EXEC mode, the replica nodes are the route switch processors (RSPs) that can become the designated shelf controller (DSC).

Use the clear configuration inconsistency replica command if there is a configuration inconsistency between the standby DSC and the current active DSC; or alternatively, if the configuration on any nodes that could become the DSC is not the same as the configuration on the current DSC. To determine if you have a configuration inconsistency, use the show configuration inconsistency replica command.

To clear configuration inconsistencies for the admin plane configuration, enter the clear configuration inconsistency replica command in administration EXEC mode.

To clear configuration inconsistencies for an SDR configuration, enter the clear configuration inconsistency replica command in EXEC mode for that SDR.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the clear configuration sessions command to clear a configuration session. This command can be used to end the configuration sessions of another user. Any uncommitted changes to a user’s target configuration are discarded.

Use the show configuration sessions command to identify active configuration sessions.

When a configuration session is cleared, a message is displayed on the terminal of the terminated user. For example:

RP/0/RSP0/CPU0:router(config)# This configuration session was terminated by user 'user_a' from line 'aux0_0_CPU0'

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Changes made during a configuration session are inactive until the commit command is entered. By default, the commit operation is pseudo-atomic, meaning that all changes must succeed for the entire commit operation to succeed. If any errors are found, none of the configuration changes takes effect.

To replace the default numeric ID for the commit, use the optional label keyword. This label is displayed (instead of the autogenerated commit ID) in the output for the show configuration commit list command.

Enter an optional comment with the comment keyword to provide additional information about the commit action. This comment is displayed in the output for the show configuration commit list command with the detail keyword.

Use the optional confirmed minutes keyword and argument to commit a configuration on a trial basis for a minimum of 30 seconds and a maximum of 300 seconds (5 minutes). During the trial configuration period, enter the commit command to confirm the configuration. If the commit command is not entered, then the system reverts to the previous configuration when the trial time period expires. The confirmed option is not available in administration configuration mode.

You can use the commit command in conjunction with the load command. Load a new configuration with the load command, and use the commit command with the replace keyword to have the loaded configuration become the active (running) configuration.

Use the optional save-running filename file_path keywords and argument to save the running configuration to a specified file. To configure automatic saving of the configuration file on every commit, use the configuration commit auto-save command. If automatic saving of the configuration file is already enabled, specifying save-running filename file_path with the commit command has no additional effect.

In pseudo-atomic commit, if an error occurs on one or more of the configurations in a commit, other configurations which are already part of the running configuration in the same commit are reverted.

Caution

Saving the running configuration to a file is CPU intensive.

Note	If you use the commit command without previously loading a target configuration, a blank configuration is committed.

Note

If you use the commit command with the replace keyword, it does not affect the mode of an 8-port E1/T1 SPA. If the mode is E1 before using the commit replace command, it remains E1. However, since the default mode is T1, the router does not recognize that the mode is E1. To change the mode to T1, you must first use the hw-module subslot cardtype e1 command to add the E1 mode into the configuration so that it correlates with the system. Then manually reload the router and it boots in T1 mode. For more information regarding the hw-module subslot cardtype command, refer to Interface and Hardware Component Command Reference for Cisco ASR 9000 Series Routers.

Warning

Performing removal and reconfiguration of services with varying attributes within a single commit may result in unpredictable behavior such as mis-programming and so on. We recommend that you implement service configuration changes incrementally to ensure accurate control and forwarding plane programming.

Usage Guidelines

[ tftp|ftp\rcp\scp\sftp ] ://{username:password@}A.B.C.D{;vrf-name}/folder/file.extension

Caution

Saving the running configuration to a file is CPU intensive.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Configuration modes are used to enter changes to a target configuration session and commit those changes to the running configuration. A router running Cisco IOS XR software contains multiple configurations:

• The configuration for a router. This mode is used to configure router- specific features such as routing protocols.
• The administration configuration for system-wide resources and settings. Some features can be configured only in administration configuration mode.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the description command to add a description to an interface configuration. The maximum number of characters is 1022.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To display the various EXEC mode commands that are available to execute with the do command, use the online help (?) function at the configuration mode prompt.

Note	The configure and describe commands are not supported with the do command.

Usage Guidelines

Use the end command to exit any configuration mode and return directly to EXEC mode Admin EXEC mode. If you enter this command without committing the changes to the target configuration, you are prompted to do so:

Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]: 

• Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode Admin EXEC mode.

  If errors are found in the running configuration, the configuration session does not end. To view the errors, enter the show configuration (config) command with the failed keyword.

• Entering no exits the configuration session and returns the router to EXEC mode Admin EXEC mode without committing the configuration changes.
• Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Note	Entering Ctrl-Z is functionally equivalent to entering the end command.

Use the abort command to exit the configuration session and return to EXEC mode Admin EXEC mode without being prompted to commit changes and without saving changes to the target configuration.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

Use the end-template command to exit template configuration mode after you have completed the template definition.

To define a template, use the template command. To apply a template to the target configuration, use the apply-template command. To view the contents of a template, use the show running-config command with the optional template template-name keyword and argument.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

More than one configuration group can be excluded simultaneously. A maximum of eight groups can be specified at one time.

Note	From Release 6.3.1 onwards, you can enter Flexible CLI config groups, apply-group and exclude-group command in any order as long as the entire commit has all the group definitions needed.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To log off from a terminal session, enter the exit command in EXEC mode Admin EXEC mode.

When exiting from global or administration configuration mode to EXEC mode Admin EXEC mode, you are prompted to commit any uncommitted configuration changes.

Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
  

• Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode Admin EXEC mode.

  If errors are found in the running configuration, the configuration session does not end. To view the errors, enter the show configuration (config) command with the failed keyword.

• Entering no exits the configuration session and returns the router to EXEC mode Admin EXEC mode without committing the configuration changes.
• Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Note	Entering the exit command from global configuration is functionally equivalent to entering the end command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The group command enters group configuration mode where you can list a series of configuration statements that can then be used elsewhere in the router configuration. Most configuration commands can be used in group configuration mode. You must be in a user group associated with a task group that includes the appropriate task IDs for each of the command statements that you list within a configuration group.

The group-name argument is limited to 32 characters and is case-sensitive. It must not contain any of these special characters:

• ` - grave

• ' - single quote

• " - double quote

• < - less than

• > - greater than

• ( - open parenthesis

• ) - close parenthesis

• [ - open bracket

• ] - close bracket

• { - open brace

• } - close brace

• / - slash

• \ - backslash

• & - ampersand

• ^ - caret

• ! - exclamation point

• ? - question mark

• ~ - tilde

• * - asterisk

• % - percent sign

• = - equal sign

• , - comma

• + - plus sign

• | - vertical bar

•   - space

A configuration group can be removed from the running configuration, only if it is not used by a configured apply-group command.

To exit from configuration group submode and return to global configuration mode, use the end-group command.

Regular expressions are used within the configuration statements to make them widely applicable. POSIX 1003.2 regular expressions are supported in the names of configuration statements. Single quotes are used to delimit a regular expression. For example, to specify the regular expression GigabitEthernet.* that matches all GigabitEthernet interfaces, enter the regular expression within single quotes as 'GigabitEthernet.*'.

To display a list of available interface types for your router configuration, enter interface ? at the configuration group prompt:

RP/0/RSP0/CPU0:router(config-GRP)# interface ?

  ATM              'RegExp': ATM Network Interface(s)
  BVI              'RegExp': Bridge-Group Virtual Interface
  Bundle-Ether     'RegExp': Aggregated Ethernet interface(s)
  Bundle-POS       'RegExp': Aggregated POS interface(s)
  GigabitEthernet  'RegExp': GigabitEthernet/IEEE 802.3 interface(s)
  IMA              'RegExp': ATM Network Interface(s)
  Loopback         'RegExp': Loopback interface(s)
  MgmtEth          'RegExp': Ethernet/IEEE 802.3 interface(s)
  Multilink        'RegExp': Multilink network interface(s)
  Null             'RegExp': Null interface
  POS              'RegExp': Packet over SONET/SDH network interface(s)
  PW-Ether         'RegExp': PWHE Ethernet Interface
  PW-IW            'RegExp': PWHE VC11 IP Interworking Interface
  Serial           'RegExp': Serial network interface(s)
  tunnel-ip        'RegExp': GRE/IPinIP Tunnel Interface(s)
  tunnel-mte       'RegExp': MPLS Traffic Engineering P2MP Tunnel interface(s)
  tunnel-te        'RegExp': MPLS Traffic Engineering Tunnel interface(s)
  tunnel-tp        'RegExp': MPLS Transport Protocol Tunnel interface
  

Note	Although you are required to enter only enough characters for the interface type to be unique, it is recommended that you enter the entire phrase. All interface types used in regular expressions are case-sensitive.

For example, you can use the command interface 'GigabitEthernet.*', but not interface 'gigabite.*'. To specify a subinterface, prefix the expression with the characters \. (backslash period), for example: interface 'GigabitEthernet.*\..*'. Refer to the Configuring Flexible Command Line Interface Configuration Groups module in the System Management Configuration Guide for Cisco ASR 9000 Series Routers for more extensive examples.

Usage Guidelines

The hostname is used in prompts and default configuration filenames.

No blank or space characters are permitted as part of a name. Do not expect case to be preserved. Uppercase and lowercase characters look the same to many Internet software applications. It may seem appropriate to capitalize a name the same way you might do in English, but conventions dictate that computer names appear all lowercase. For more information, see RFC 1178, Choosing a Name for Your Computer.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the load command to populate the target configuration with the contents of a previously saved configuration. When loading a file, you must specify the device, directory path, and filename of the configuration file.

Use the commit command in conjunction with the load command. Load a new configuration with the load command, and use the commit command with the replace keyword to have the loaded configuration become the active (running) configuration.

Use the show configuration failed (config) command with the optional load keyword to display syntax errors that occurred during the last load operation.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the load commit changes command to populate the target configuration with changes from previous configuration commits. The changes are not applied until you enter the commit command.

Use the show configuration (config) command to display the target configuration.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the load configuration failed command to populate the target configuration with the contents of the previous failed configuration commit.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the load configuration removed command to populate the target configuration with the contents of the removed configuration during installation operations.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the load rollback changes command to load rollback configuration changes to the target configuration. This command is similar to the rollback configuration command. The difference between the commands is that the load rollback changes command copies the rollback changes to the target configuration and does not commit the changes until the changes are explicitly committed with the commit command.

Use the show configuration rollback changes command to display rollback changes.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

You must have the documentation PIE installed before you can use the man command. If you attempt to run this command without the documentation PIE installed, an error is displayed as shown in the following example:

RP/0/RSP0/CPU0:router# man command show install

Building index table...
Warning. Unable to get directory info for '/pkg/man' :No such file or directory.
 Discarding!
man [5521656]:Building index table failed. No entries found
  

For information about installing optional software PIEs, see the Upgrading and Managing Cisco IOS XR Software module in System Management Configuration Guide for Cisco ASR 9000 Series Routers.

Use the man command to display the manual pages for a specific command on the basis of the command name, a feature, or a keyword. Each man page contains the command name, syntax, command mode, usage, examples, and related commands.

The man command queries and displays command information about the router. A query can be based on keywords or a feature. The feature feature-name keyword and argument display all commands that match the feature. For example, entering man feature asr9k - base-1 displays all commands that match the asr9k-base-1 feature. The keyword keywords keyword and argument display all commands that contain the specified keyword. For example, man keyword ipv4 displays all commands that contain ipv4.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the more command to display any text file, especially an ASCII file stored on the router or accessible through the network. The file can be a configuration file or any other text file.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Each time the commit command is entered, a commit ID is assigned to the new configuration. You can revert the system to the configuration of a previous commit ID with the rollback configuration command:

• Use the to keyword to revert to the configuration that existed before the configuration specified with the commit-id argument.
• Use the last keyword to revert to the configuration that existed before the last number of configuration commits (specified with the number-of-commits argument) were made.
• Use show configuration commit list to display a list of the commit IDs available for rollback operations.

Note	The most recent 100 commits are retained by the system. As new commit IDs are added, the oldest commit IDs are discarded and are no longer available for rollback operations.

Use the force keyword to override commits that would fail otherwise. This is useful in the event of a low-memory condition on the router, to revert to a commit that would remove a configuration that caused the low-memory condition.

Note	The rollback operation may fail if you try to rollback two (or more) commits where the individual commits involve the configuration and removing of the configuration of the same item, and there is a dependency of one item over another in any of the individual commit operations.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To save a configuration to a file, use the save configuration command.

To save a configuration that failed to a file, use the save configuration failed command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To save the configuration changes to be made during a replace operation to a file, use the save configuration changes command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the save configuration commit changes command to save the changes made in a commit operation to a file. You can specify a specific commit ID, all the changes since a specified commit ID, or the changes that occurred during the last n commits.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

To save a configuration to a file, use the save configuration command.

To save a configuration that failed to a file, use thesave configuration failed command.

To save a configuration that failed during startup to a file, use the save configuration failed command with the startup keyword.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

When a package is deactivated, the configuration belonging to that package is removed from the running configuration and saved to a file. To save a copy of the removed configuration file, use the save configuration removed command.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the save rollback changes command to save the changes that would be made in a configuration rollback to a specific commit point or for a series of commits.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the set default-afi command to set the default AFI for the current session. This command acts as a keystroke shortcut for show commands. If the default AFI setting is set to IPv4, then you would not have to specify the ipv4 keyword for show commands that support the ipv4 keyword. For example, if the AFI setting is set to IPv4, you could issue the show route command without specifying the ipv4 keyword to display IPv4 routes in the Routing Information Base (RIB).

Use the show default-afi-safi-vrf command to display the default AFI setting.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the set default-safi command to set the default SAFI setting for the current session. This command acts as a keystroke shortcut for show commands. If the default SAFI setting is set to unicast, you would not have to specify the unicast keyword for show commands that support that keyword. For example, if the default SAFI setting is set to unicast, you could issue the show router command without specifying the unicast keyword to display information about unicast address prefixes in the Routing Information Base (RIB).

Use the show default-afi-safi-vrf command to display the default SAFI setting.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the set default-vrf command to set the default VRF setting for the current session. This command acts as a keystroke shortcut for show commands. For example, if the default VRF is configured, you can issue the show route command without specifying the VRF name.

When the default VRF for the session is set to none , then IPv4 routes for the system default VRF are displayed.

Note	To override the default VRF setting, specify the VRF name in the show command.

Use the show default-afi-safi-vrf command to display the default VRF setting.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The show commands display information about the system and its configuration. To display a list of the available show commands, use the question mark (?) online help function.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the show aliases command to display all aliases currently configured on the system.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

The output of this show command indicates if the group is a part of the global apply-group or is a part of the sub-mode level apply-group.

Usage Guidelines

Task ID

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Use the show configuration command to display details on uncommitted configuration changes.

Use the show configuration command with the running keyword to display the running (active) configuration.

Prior to committing the target configuration, use the show configuration command with the merge keyword from any configuration mode to display the result of merging the target configuration with the running configuration.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes appropriate task IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Usage Guidelines

Each time a configuration is committed with the commit command, the configuration commit operation is assigned a commit ID. The show configuration commit changes command displays the configuration changes made since the specified commit.

To display a list of the available commit IDs, enter the show configuration commit list command. You can also display the commit IDs by entering the show configuration commit changes command with the online help function (? ).

You can’t view commit IDs from a different release if the syntax or semantics of the configuration changed in the current release.

Note	Syntax of a configuration refers to its structure and format, while the semantics of a configuration refers to its backend interpretation.