Cisco Systems OL-14361-01 User Manual

CHAP T E R

Configuring Additional Router Features

This chapter contains instructions and information for entering basic configurations using the command-line interface (CLI).

• Configuring the Domain Name and Domain Name Server, page 5-103

• Configuring Telnet, HTTP, and XML Host Services, page 5-106

• Managing Configuration History and Rollback, page 5-108

• Configuring Logging and Logging Correlation, page 5-114

• Creating and Modifying User Accounts and User Groups, page 5-117

• Configuring Software Entitlement, page 5-121

• Configuration Limiting, page 5-121

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

OL-14361-01

5-103

Configuring the Domain Name and Domain Name Server

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

end

5. show hosts

DETAILED STEPS

Command or Action Purpose

Step 1

configure

Chapter 5 Configuring Additional Router Features

Enters global configuration mode.

Step 2

Step 3

Example:

RP/0/RP0/CPU0:router# configure

domain name domain-name-of-organization

Example:

RP/0/RP0/CPU0:router(config)# domain name cisco.com

domain name-server ipv4-address

Example:

RP/0/RP0/CPU0:router(config)# domain name-server 192.168.1.111

Defines a default domain name used to complete unqualified hostnames.

Specifies the address of a name server to use for name and address resolution (hosts that supply name information).

Note You can enter up to six addresses, but only one for

each command.

5-104

Cisco IOS XR Getting Started Guide

OL-14361-01

Chapter 5 Configuring Additional Router Features

Command or Action Purpose

Step 4

end

commit

Example:

RP/0/RP0/CPU0:router(config)# end or RP/0/RP0/CPU0:router(config)# commit

Step 5

show hosts

Configuring the Domain Name and Domain Name Server

Saves configuration changes.

• When you issue the end command, the system prompts

you to commit 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.

–

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

–

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

• Use the commit command to save the configuration

changes to the running configuration file and remain within the configuration session.

Displays all configured name servers.

Example:

RP/0/RP0/CPU0:router(config)# 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

Default domain is cisco.com Name/address lookup uses domain service Name servers: 10.1.1.1

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.

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.

Note This process enables the Telnet, HTTP and XML host services on the Management Ethernet interfaces.

SUMMARY STEPS

See Cisco IOS XR System Management Configuration Guide for information on installing and activating packages.

For more information on how to enable these services on other inband interfaces, refer to the

Implementing Management Plane Protection on Cisco IOS XR Software module in Cisco IOS XR System Security Configuration Guide.

1. configure

2. telnet {ipv4 | ipv6} server max-servers limit

3. http server

4. xml agent corba

5. commit

5-106

Cisco IOS XR Getting Started Guide

OL-14361-01

Chapter 5 Configuring Additional Router Features

DETAILED STEPS

Command or Action Purpose

Step 1

configure

Example:

RP/0/RP0/CPU0:router# configure

Step 2

telnet ipv4 server max-servers limit

telnet ipv6 server max-servers limit

Example:

RP/0/RP0/CPU0:router(config)# telnet ipv4 server max-servers 5

Step 3

http server

Configuring Telnet, HTTP, and XML Host Services

Enters global configuration mode.

Enables Telnet services on the router and specifies the maximum number of allowable Telnet servers.

Enables HTTP server on the router.

Step 4

Step 5

Example:

RP/0/RP0/CPU0:router(config)# http server

xml agent corba

Example:

RP/0/RP0/CPU0:router(config)# xml agent corba

end

commit

Example:

RP/0/RP0/CPU0:router(config)# end or RP/0/RP0/CPU0:router(config)# commit

Enables XML CORBA agent services on the router.

Saves configuration changes.

• When you issue the end command, the system prompts

you to commit 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.

–

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

–

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

OL-14361-01

• Use the commit command to save the configuration

changes to the running configuration file and remain within the configuration session.

Cisco IOS XR Getting Started Guide

5-107

Chapter 5 Configuring Additional Router Features

Managing Configuration History and Rollback

Examples

In the following example, the host services are enabled:

RP/0/RP0/CPU0:router# configure 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

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 or administration 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.

The commitIDs are shown in the “Label/ID” column. The following example shows the show configuration commit list command display in EXEC and administration EXEC modes:

RP/0/RP1/CPU0:router# show configuration commit list

SNo. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 1000000219 cisco vty0 CLI 12:27:50 UTC Wed Mar 22 2006 2 1000000218 cisco vty1 CLI 11:43:31 UTC Mon Mar 20 2006 3 1000000217 cisco con0_RP0_C CLI 17:44:29 UTC Wed Mar 15 2006

Managing Configuration History and Rollback

RP/0/RP1/CPU0:router# admin RP/0/RP1/CPU0:router(admin)# show configuration commit list

SNo. Label/ID User Line Client Time Stamp ~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~ 1 2000000022 cisco vty1 CLI 15:03:59 UTC Fri Mar 17 2006 2 2000000021 cisco con0_RP0_C CLI 17:42:55 UTC Wed Mar 15 2006 3 2000000020 SYSTEM con0_RP0_C Setup Dial 17:07:39 UTC Wed Mar 15 2006

Displaying the Configuration Changes Recorded in a CommitID

To display the configuration changes made during a specific commit session (commitID), go to EXEC or administration EXEC mode and enter the show configuration commit changes command followed by a commitID number. The easiest way to determine the commitID is to enter the show configuration commit changes ? command first. In the following example, the command help is used to display the available commitIDs, and then the changes for a specific commitID are displayed:

RP/0/RP1/CPU0:router(admin)# show configuration commit changes ?

last Changes made in the most recent <n> commits since Changes made since (and including) a specific commit 2000000020 Commit ID 2000000021 Commit ID 2000000022 Commit ID

RP/0/RP1/CPU0:router(admin)# show configuration commit changes 2000000020

OL-14361-01

Building configuration... username cisco secret 5 $1$MgUH$xzUEW6jLfyAYLKJE.3p440 group root-system ! end

Cisco IOS XR Getting Started Guide

5-109

Managing Configuration History and Rollback

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.

To display the prospective rollback configuration changes from the current configuration to a specific commitID, go to EXEC or administration EXEC mode and enter the show configuration rollback changes to commitId command. In the following example, the command help displays the available commitIDs, and then the rollback changes are displayed.

RP/0/RP1/CPU0:router# show configuration rollback changes to ?

1000000217 Commit ID 1000000218 Commit ID 1000000219 Commit ID

RP/0/RP1/CPU0:router# show configuration rollback changes to 1000000218

Building configuration... no interface Loopback100 interface POS0/1/0/0 no ipv6 nd dad attempts ! ! no route-policy xx end

Chapter 5 Configuring Additional Router Features

To display the prospective rollback configuration changes from the current configuration to a specified number of previous sessions, go to EXEC or administration EXEC mode and 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

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. The rollback process also creates a new rollback point so that you can roll back the configuration to the previous configuration.

5-110

Cisco IOS XR Getting Started Guide

OL-14361-01

Chapter 5 Configuring Additional Router Features

Managing Configuration History and Rollback

Tip To 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, go to EXEC or administration EXEC mode and enter the rollback configuration to commitId command:

RP/0/RP1/CPU0:router# rollback configuration to 1000000220 Loading Rollback Changes. Loaded Rollback Changes in 1 sec Committing. 2 items committed in 1 sec (1)items/sec Updating. Updated Commit database in 1 sec Configuration successfully rolled back to '1000000220'.

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, commits the rolled-back configuration, and creates a new commitID for the previous configuration.

Tip To 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, go to EXEC or administration EXEC mode and 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.

Loading CommitID Configuration Changes to the Target Configuration

If the changes saved for a specific commitID are close to what you want, but a rollback is not appropriate, you can load the configuration changes for a commitID into the target configuration, modify the target configuration, and then commit the new configuration. Unlike the rollback process, the loaded changes are not applied until you commit them.

OL-14361-01

Cisco IOS XR Getting Started Guide

5-111

+ 19 hidden pages

Cisco Systems OL-14361-01 User Manual

Contents

Configuring the Domain Name and Domain Name Server

Examples

Related Documents

Configuring Telnet, HTTP, and XML Host Services

Prerequisites

Managing Configuration History and Rollback

Examples

Displaying the CommitIDs

Displaying the Configuration Changes Recorded in a CommitID

Previewing Rollback Configuration Changes

Rolling Back the Configuration to a Specific Rollback Point

Rolling Back the Configuration over a Specified Number of Commits

Loading CommitID Configuration Changes to the Target Configuration