ページ1に含まれる内容の要旨
CHAPTER 3
Configuring Additional Router Features
This chapter contains instructions and information for entering basic configurations using the
command-line interface (CLI).
Contents
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 Logg
ページ2に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features 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)# do
ページ3に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Managing Configuration History and Rollback 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
ページ4に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features 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 comm
ページ5に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Managing Configuration History and Rollback 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
ページ6に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features 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_a vty0 CLI 00:16:51 UTC Thu May 11 2004 2 1000000143 user_a vty0 CLI 00:04:32 UTC Thu May 11 2004 3 1000000142 user_a 0.0.0.0 XMLAgent 21:58:36 UTC Wed M
ページ7に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Managing Configuration History and Rollback 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 ch
ページ8に含まれる内容の要旨
Chapter 3 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 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
ページ9に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Saving and Loading Target Configuration Files 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 sessio
ページ10に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Saving and Loading Target Configuration Files Saving the Target Configuration to a File To save the configuration changes in the target configuration to a file, enter the show configuration | file filename command. � If the full path of the file is not specified, the default directory for your account is used. You should always save your target configuration files to this location. � The filename should end with the .cfg suffix for easy
ページ11に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuring Logging and Logging Correlation Configuring Logging and Logging Correlation System messages generated by the Cisco IOS XR software can be logged to a variety of locations based on the severity level of the messages. For example, you could direct information messages to the system console and also log debugging messages to a network server. In addition, you can define correlation rules that group and summarize related events, g
ページ12に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuring Logging and Logging Correlation For example, the original message describing a card online insertion and removal (OIR) and system state being up or down can be reported, and all subsequent messages reiterating the same event can be correlated. When you create correlation rules, a common root event that is generating larger volumes of follow-on error messages can be isolated and sent to the correlation buffer. An operator can
ページ13に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuring Logging and Logging Correlation Command or Action Purpose Step 4 logging console [severity] Logs messages on the console. � When a severity level is specified, only messages at that severity level are logged on Example: the console. RP/0/RP0/CPU0:router(config)# logging console emergencies � See Table 3-2 for a summary of the logging severity levels. Step 5 logging buffered [severity | buffer-size] Copies logging messages to
ページ14に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups RP/0/RP0/CPU0:Apr 6 21:30:59.515 : alphadisplay[103][317]: alpha_display_drain_ queue: Draining 1 message from the queue of size = 1 RP/0/RP0/CPU0:Apr 6 21:31:03.099 : ingressq[227]: %INGRESSQ_DLL-3-HALF_DEPTH_PA RT_DISCOVERED : ingressq dll: half depth memory detected, memory: DQ External QE Memory --More-- Related Documents For more information on message logging and configuration of
ページ15に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups Displaying Details About User Accounts, User Groups, and Task IDs Table 3-3 summarizes the EXEC mode commands used to display details about user accounts, user groups, and task IDs. Table 3-3 Commands to Display Details About Users and User Groups Command Description show aaa userdb username Displays the task IDs and privileges assigned to a specific username. To display all users on t
ページ16に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Creating and Modifying User Accounts and User Groups Creating Users and Assigning Groups To create a user, assign a password, and assign the user to a group, perform the following procedure: SUMMARY STEPS 1. configure 2. username user-name 3. password {0 | 7} password or secret {0 | 5} password 4. group group-name 5. Repeat Step 4 for each user group to be associated with the user specified in Step 2. 6. end or commit DETAILED STEPS Comma
ページ17に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuration Limiting Command or Action Purpose Step 4 group group-name Assigns the user named in Step 2 to a user group. � The user takes on all attributes of the user group, as defined by the user group association to various task Example: groups. RP/0/RP0/CPU0:router(config-un)# group sysadmin � Each user must be assigned to at least one user group. A user may belong to multiple user groups. Step 5 Repeat Step 4 for each user group
ページ18に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuration Limiting The following sections describe the limits you can configure, default and maximum values, and commands for configuring and displaying the configuration limits: � Static Route Configuration Limits, page 3-18 � IS-IS Configuration Limits, page 3-19 � OSPFv2 and v3 Configuration Limits, page 3-19 � BGP Configuration Limits, page 3-22 � Routing Policy Language Line and Policy Limits, page 3-24 � Multicast Configuration L
ページ19に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuration Limiting IS-IS Configuration Limits Table 3-5 summarizes the maximum limits for IS-IS, including the commands used to display and change the limits. Table 3-5 IS-IS Configuration Limits and Commands Default Absolute Configuration Command Show Current Settings Maximum Maximum (Address Family Configuration Command Feature Limit Description Limit Limit Mode) (EXEC Mode) Maximum number of 10,000 28,000 maximum-redistributed-pref
ページ20に含まれる内容の要旨
Chapter 3 Configuring Additional Router Features Configuration Limiting Table 3-6 OSPFv2 and OSPFv3 Configuration Limits and Commands Default Absolute Feature Limit Maximum Maximum Configuration Command Show Current Settings Command Description Limit Limit (Router Configuration Mode) (EXEC Mode) Maximum number of 255 1024 maximum interfaces n show ospf interfaces that can be configured for an OSPF instance Maximum routes 10,000 28,672 maximum redistributed-prefix n show ospf redistribu
