Cisco Systems ASR 9000 Manual De Usuario
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
3-32
Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide
OL-17502-01
Chapter 3 Configuring General Router Features
Managing Configuration Sessions
If you end a configuration session without committing the configuration changes, the router prompts you
to save changes, discard changes, or cancel the action, as shown in the following example:
to save changes, discard changes, or cancel the action, as shown in the following example:
RP/0/RSP0/CPU0:router(config-if)# end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:
Respond to the prompt by entering one of the following options:
•
yes—Commit the configuration changes and exit configuration mode.
•
no—Exit configuration mode without committing the configuration changes.
•
cancel—Remain in configuration mode without committing the configuration changes.
Note
In EXEC mode, the exit command logs the user out of the system.
Aborting a Configuration Session
When you abort a configuration session, any changes are discarded and the configuration session ends.
No warning is given before the configuration changes are deleted.
No warning is given before the configuration changes are deleted.
In global configuration mode, the abort command discards configuration changes and returns to EXEC
mode. In administration configuration mode, the abort command discards configuration changes and
returns to administration EXEC mode. To abort a configuration session, type the abort command, as
shown in the following example:
mode. In administration configuration mode, the abort command discards configuration changes and
returns to administration EXEC mode. To abort a configuration session, type the abort command, as
shown in the following example:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# hostname host1
RP/0/RSP0/CPU0:router(config)# interface Gi 0/2/0/2
RP/0/RSP0/CPU0:router(config-if)# description this is my interface
RP/0/RSP0/CPU0:router(config-if)# ipv4 address 10.1.1.1 255.0.0.0
RP/0/RSP0/CPU0:router(config-if)# shutdown
RP/0/RSP0/CPU0:router(config-if)# abort
RP/0/RSP0/CPU0:router#
Configuring the RSP Hostname
The hostname identifies an RSP on the network. Although devices can be uniquely identified by their
Layer 2 and Layer 3 addresses (such as an IP address), it is often simpler to remember network devices
by an alphanumeric “hostname.” This name is used in the CLI prompt and default configuration
filenames and to identify the RSP on the network.
Layer 2 and Layer 3 addresses (such as an IP address), it is often simpler to remember network devices
by an alphanumeric “hostname.” This name is used in the CLI prompt and default configuration
filenames and to identify the RSP on the network.
To configure the hostname, type the hostname command with the RSP name as shown in the following
example:
example:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# hostname SDR_SJ
RP/0/RSP0/CPU0:router(config)# commit
RP/0/RSP0/CPU0:Apr 7 00:07:33.246 : config[65669]: %LIBTARCFG-6-COMMIT : Configuration
committed by user 'user_a'. Use 'show configuration commit changes 1000000067' to view
the changes.
RP/0/RSP0/CPU0:RP_SJ(config)#
The preceding example sets the RSP name to RP_SJ.