This chapter contains instructions and information for entering basic configurations using the
command-line interface (CLI).
This chapter contains the following sections:
• Configuring the Domain Name and Domain Name Server, page 3-1
• Configuring Telnet, HTTP, and XML Host Services, page 3-2
• Managing Configuration History and Rollback, page 3-3
• Saving and Loading Target Configuration Files, page 3-9
• Configuring Logging and Logging Correlation, page 3-11
• Creating and Modifying User Accounts and User Groups, page 3-14
3
• Configuration Limiting, page 3-17
Configuring the Domain Name and Domain Name Server
Configure a domain name and domain name server (DNS) for your router to make contacting other
devices on your network more efficient. Use the following guidelines:
• To define a default domain name that the Cisco IOS XR software uses to complete unqualified
hostnames (names without a dotted-decimal domain name), use the domain-name command in
global configuration mode.
• To specify the address of one or more name servers to use for name and address resolution, use the
domain name-server command in global configuration mode. If no name server address is
specified, the default name server is 255.255.255.255 so the DNS lookup can be broadcast to the
local network segment. If a DNS server is in the local network, it replies. If not, there might be a
server that knows how to forward the DNS request to the correct DNS server.
• Use the show hosts command in EXEC mode to display the default domain name, the style of name
lookup service, a list of name server hosts, and the cached list of hostnames and addresses.
Cisco IOS XR Getting Started Guide
3-1
Configuring Telnet, HTTP, and XML Host Services
To configure the DNS and DNS server, complete the following steps:
SUMMARY STEPS
1. configure
2. domain name domain-name-of-organization
3. domain name-server ipv4-address
4. commit
5. end
6. show hosts
Examples
In the following example, the domain name and DNS are configured:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# domain name cisco.com
RP/0/RP0/CPU0:router(config)# domain name-server 10.1.1.1
RP/0/RP0/CPU0:router(config)# commit
RP/0/RP0/CPU0:router(config)# end
RP/0/RP0/CPU0:router# show hosts
Chapter 3 Configuring Additional Router Features
Default domain is cisco.com
Name/address lookup uses domain service
Name servers: 10.1.1.1
Related Documents
Related TopicDocument Title
Complete descriptions of the domain services
commands
Implementing Host Services and Applications on Cisco IOS XR
Software in the Cisco IOS XR IP Addresses and Services
Configuration Guide
Configuring Telnet, HTTP, and XML Host Services
For security, some host services are disabled by default. Host services, such as Telnet, Extensible
Markup Language (XML), and HTTP, can be optionally enabled using the commands described in this
section. Host services provide the following features:
• Enabling the Telnet server allows users to log in to the router using IPv4 or IPv6 Telnet clients.
• Enabling the HTTP server allows users to log in to the router using the CWI.
• Enabling the XML agent enables XML Common Object Request Broker Architecture (CORBA)
agent services so that you can manage and configure the router using an XML interface.
3-2
NoteIPv6 is not supported on the Cisco XR 12000 Series Router.
Cisco IOS XR Getting Started Guide
Chapter 3 Configuring Additional Router Features
Prerequisites
The following prerequisites must be met before configuring the Telnet, HTTP, and XML host services:
• For the XML and HTTP host services, the Manageability package must be installed and activated
on the router.
• To enable the Secure Socket Layer (SSL) of the HTTP and XML services, the Security package must
be installed and activated on the router.
See Chapter 5, “Managing Cisco IOS XR Software Packages,” for information on installing and
activating packages.
SUMMARY STEPS
1. configure
2. telnet ipv4 server max-servers 5
3. telnet ipv6 server max-servers 5
4. http server
5. xml agent corba
Managing Configuration History and Rollback
6. commit
Examples
In the following example, the host services are enabled:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# telnet ipv4 server max-servers 5
RP/0/RP0/CPU0:router(config)# telnet ipv6 server max-servers 5
RP/0/RP0/CPU0:router(config)# http server
RP/0/RP0/CPU0:router(config)# xml agent corba
RP/0/RP0/CPU0:router(config)# commit
Related Documents
Related TopicDocument Title
Installation and activation of the Manageability and
Descriptions of the HTTP and XML server commands Cisco IOS XR System Management Command Reference
Descriptions of the Telnet commandsCisco IOS XR IP Addresses and Services Command Reference
Managing Configuration History and Rollback
After each commit operation, a record of the committed configuration changes is saved. This record
contains only the changes made during the configuration session; it does not contain the complete
configuration. Each record is assigned a unique ID, known as a commitID.
Cisco IOS XR Getting Started Guide
3-3
Managing Configuration History and Rollback
When multiple commitIDs are present, you can use a commitID to identify a previous configuration to
which you want to return, or you can use the commitID to load the configuration changes made during
that configuration session. You can also load configuration changes from multiple commitIDs, and you
can clear commitIDs. If you are thinking about rolling back the configuration to a specific commitID,
consider the following guidelines:
• You cannot roll back to a configuration that was removed because of package incompatibility.
Configuration rollbacks can succeed only when the configuration passes all compatibility checks
with the currently active Cisco IOS XR software.
• If an incompatible configuration is found during the rollback operation, the operation fails and an
error is displayed.
The Cisco IOS XR software automatically saves up to 100 of the most recent commitIDs. The following
sections describe how to manage configuration changes and roll back to a previously committed
configuration:
• Displaying the CommitIDs, page 3-4
• Displaying the Configuration History Log, page 3-5
• Displaying the Configuration Changes Recorded in a CommitID, page 3-6
• Rolling Back the Configuration to a Specific Rollback Point, page 3-7
• Rolling Back the Configuration over a Specified Number of Commits, page 3-7
• Loading the Configuration Changes for a Specific CommitID, page 3-8
• Loading Rollback Configuration Changes to the Target Configuration, page 3-8
• Deleting CommitIDs, page 3-9
Displaying the CommitIDs
To display a history of up to 100 of the most recent commitIDs, enter the show configuration commit
list command in EXEC mode. Up to 100 of the most recent commitIDs are saved by the system. Each
commitID entry shows the user who committed configuration changes, the connection used to execute
the commit, and commitID time stamp.
3-4
Cisco IOS XR Getting Started Guide
Chapter 3 Configuring Additional Router Features
The commitIDs are shown in the “Label/ID” column. The following example shows the
show configuration commit list command display:
RP/0/RP0/CPU0:router# show configuration commit list
SNo. Label/ID User Line Client Time Stamp
~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~
1 1000000391 user_a con0_33_1 CLI 19:29:18 UTC Wed Jan 10 2004
2 1000000390 user_a con0_33_1 CLI 19:29:16 UTC Wed Jan 10 2004
3 1000000389 user_a con0_33_1 CLI 19:29:15 UTC Wed Jan 10 2004
4 1000000388 user_a con0_33_1 CLI 19:29:12 UTC Wed Jan 10 2004
5 1000000387 user_a con0_33_1 CLI 19:26:16 UTC Wed Jan 10 2004
6 1000000386 user_a con0_32_1 CLI 19:18:38 UTC Wed Jan 10 2004
7 1000000385 user_a con0_33_1 CLI 19:14:09 UTC Wed Jan 10 2004
8 1000000384 user_a con0_33_1 CLI 19:13:58 UTC Wed Jan 10 2004
9 1000000383 user_a con0_33_1 CLI 19:13:33 UTC Wed Jan 10 2004
10 1000000382 user_a con0_33_1 CLI 19:12:50 UTC Wed Jan 10 2004
11 1000000381 user_a con0_33_1 CLI 19:12:48 UTC Wed Jan 10 2004
12 1000000380 user_a con0_33_1 CLI 19:12:46 UTC Wed Jan 10 2004
13 1000000379 user_a con0_33_1 CLI 19:12:43 UTC Wed Jan 10 2004
14 1000000378 user_a con0_33_1 CLI 19:12:14 UTC Wed Jan 10 2004
15 1000000377 user_a con0_33_1 CLI 19:10:47 UTC Wed Jan 10 2004
Managing Configuration History and Rollback
Displaying the Configuration History Log
To display the header records for up to 1000 commit events, enter the show configuration commit
history command in EXEC mode, as shown in the following example.
The output from this command does not show the details of the entries, but allows you to display a larger
list of the commit events that occurred. To display the commitIDs to which you can roll back, use the
show configuration commit list command.
Cisco IOS XR Getting Started Guide
3-5
Managing Configuration History and Rollback
RP/0/RP0/CPU0:router# show configuration commit history
SNo. Label/ID User Line Client Time Stamp
~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~
1 1000000144 user_avty0 CLI 00:16:51 UTC Thu May 11 2004
2 1000000143 user_avty0 CLI 00:04:32 UTC Thu May 11 2004
3 1000000142 user_a0.0.0.0 XMLAgent 21:58:36 UTC Wed May 11 2004
4 1000000141 user_a0.0.0.0 XMLAgent 21:46:07 UTC Wed May 11 2004
5 1000000140 user_bcon0_RP1_C CLI 21:43:30 UTC Wed May 11 2004
6 1000000139 user_a0.0.0.0 XMLAgent 21:40:13 UTC Wed May 11 2004
7 1000000138 user_a0.0.0.0 XMLAgent 21:34:48 UTC Wed May 11 2004
8 1000000137 user_bcon0_RP1_C CLI 21:32:10 UTC Wed May 11 2004
9 1000000136 user_a0.0.0.0 XMLAgent 21:30:13 UTC Wed May 11 2004
10 1000000135 user_b con0_RP1_C CLI 19:45:04 UTC Wed May 11 2004
11 1000000134 user_b con0_RP1_C CLI 19:37:26 UTC Wed May 11 2004
12 1000000133 user_b con0_RP1_C CLI 19:36:27 UTC Wed May 11 2004
13 1000000132 user_b con0_33_1 Rollback 18:34:45 UTC Wed May 11 2004
14 1000000131 user_b con0_33_1 Rollback 18:32:37 UTC Wed May 11 2004
15 1000000130 user_b con0_33_1 Rollback 18:31:09 UTC Wed May 11 2004
16 1000000129 user_b con0_33_1 CLI 18:28:12 UTC Wed May 11 2004
17 1000000128 user_b con0_33_1 CLI 18:27:22 UTC Wed May 11 2004
18 1000000127 user_b con0_33_1 CLI 18:27:19 UTC Wed May 11 2004
19 1000000126 user_b con0_33_1 Rollback 18:25:55 UTC Wed May 11 2004
20 1000000125 user_b con0_33_1 Rollback 18:24:25 UTC Wed May 11 2004
Chapter 3 Configuring Additional Router Features
Displaying the Configuration Changes Recorded in a CommitID
To display the configuration changes made during a specific commit session (commitID), enter the show
configuration commit changes command followed by a commitID number, as shown in the following
example:
RP/0/0/CPU0:router# show configuration commit changes 1000000071
Building configuration...
hostname router2
end
Previewing Rollback Configuration Changes
The show configuration rollback changes command allows you to preview the configuration changes
that take place if you roll back the configuration to a specific commitID. For example, if you want to roll
back the configuration to a specific point, all configuration changes made after that point must be
undone. This rollback process is often accomplished by executing the “no” version of commands that
must be undone.
3-6
Cisco IOS XR Getting Started Guide
Chapter 3 Configuring Additional Router Features
To display the prospective rollback configuration changes from the current configuration to a specific
session, enter the show configuration rollback changes to commitId command:
RP/0/RP0/CPU0:router# show configuration rollback changes to 1000000373
Building configuration...
interface Loopback2
no description
no ipv4 address 10.0.0.1 255.0.0.0
To display the prospective rollback configuration changes from the current configuration to a specified
number of previous sessions, enter the show configuration rollback changes last commit-range
command:
RP/0/RP0/CPU0:router# show configuration rollback changes last 2
Building configuration...
interface Loopback3
no description
no ipv4 address 10.0.1.1 255.0.0.0
exit
interface Loopback4
no description
no ipv4 address 10.0.0.1 255.0.0.0
end
Managing Configuration History and Rollback
In the preceding example, the command display shows the proposed rollback configuration changes for
the last two commit IDs.
Rolling Back the Configuration to a Specific Rollback Point
When you roll back the configuration to a specific rollback point, you undo all configuration changes
made during the session identified by the commit ID for that rollback point, and you undo all
configuration changes made after that point. The rollback process rolls back the configuration and
commits the rolled-back configuration.
TipTo preview the commands that undo the configuration during a rollback, use the show configuration
rollback changes command.
To roll back the router configuration to a previously committed configuration, enter the rollback
configuration to commitId command:
RP/0/RP0/CPU0:router# rollback configuration to 1000000325
Configuration successfully rolled back to ’1000000325’.
Rolling Back the Configuration over a Specified Number of Commits
When you roll back the configuration over a specific number of commits, you do not have to enter a
specific commit ID. Instead, you specify a number x, and the software undoes all configuration changes
made in the last x committed configuration sessions. The rollback process rolls back the configuration
and commits the rolled-back configuration.
Cisco IOS XR Getting Started Guide
3-7
Managing Configuration History and Rollback
TipTo preview the commands that undo the configuration during a rollback, use the show configuration
rollback changes command.
To roll back to the last x commits made, enter the rollback configuration last x command; x is a number
ranging from 1 to the number of saved commits in the commit database.
In the following example, a request is made to roll back the configuration changes made during the
previous two commits:
RP/0/RP0/CPU0:router# rollback configuration last 2
Loading Rollback Changes.
Loaded Rollback Changes in 1 sec
Committing.
1 items committed in 1 sec (0)items/sec
Updating.
Updated Commit database in 1 sec
Configuration successfully rolled back 2 commits.
Chapter 3 Configuring Additional Router Features
Loading the Configuration Changes for a Specific CommitID
You can load the configuration changes recorded by any commitID by entering the load commit changes
command in global configuration mode. The load commit changes command must be followed by a
commitID number, as shown in the following example:
RP/0/0/CPU0:router(config)# load commit changes 1000000066
Building configuration...
Loading.
21 bytes parsed in 1 sec (20)bytes/sec
The configuration changes are added to the target configuration and are not applied until you enter the
commit command.
TipTo display the target configuration, enter the show configuration command.
Loading Rollback Configuration Changes to the Target Configuration
You can load rollback configuration changes to the target configuration by entering the load rollback
changes command in global configuration mode. 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.
3-8
TipTo display the rollback changes, enter the show configurationrollback changes command.
Cisco IOS XR Getting Started Guide
Chapter 3 Configuring Additional Router Features
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
Saving and Loading Target Configuration Files
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
Cisco IOS XR Getting Started Guide
3-9
Loading...
+ 19 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.