-
Cisco IOS XR Getting Started Guide, Release 3.3
-
Preface
-
Chapter 1 - Introduction to Cisco IOS XR Software
-
Chapter 2 - Bringing Up the Cisco IOS XR Software on a Standalone Router
-
Chapter 3 - Bringing Up the Cisco IOS XR Software on a Multishelf System
-
Chapter 4 - Configuring General Router Features
-
Chapter 5 - Configuring Additional Router Features
-
Chapter 6 - CLI Tips, Techniques and Shortcuts
-
Chapter 7 - Upgrading and Managing Cisco IOS XR Software
-
Chapter 8 - Managing the Router Hardware
-
Chapter 9 - Troubleshooting the Cisco IOS XR Software
-
Appendix A - Understanding Regular Expressions, Special Characters, and Patterns
-
Glossary
-
Index
-
Table Of Contents
Configuring Additional Router Features
Configuring the Domain Name and Domain Name Server
Configuring Telnet, HTTP, and XML Host Services
Managing Configuration History and Rollback
Displaying the Configuration History Log
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
Loading Rollback Configuration Changes to the Target Configuration
Configuring Logging and Logging Correlation
Logging Locations and Severity Levels
Configuring Basic Message Logging
Creating and Modifying User Accounts and User Groups
Displaying Details About User Accounts, User Groups, and Task IDs
Creating Users and Assigning Groups
Static Route Configuration Limits
OSPFv2 and v3 Configuration Limits
Routing Policy Language Line and Policy Limits
Multicast Configuration Limits
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
•
•
•
•
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 configure the DNS and DNS server, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
Examples
In the following example, the domain name and DNS are configured:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# domain name cisco.comRP/0/RP0/CPU0:router(config)# domain name-server 10.1.1.1RP/0/RP0/CPU0:router(config)# commitRP/0/RP0/CPU0:router(config)# endRP/0/RP0/CPU0:router# show hostsDefault domain is cisco.comName/address lookup uses domain serviceName servers: 10.1.1.1Related Documents
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:
•
•
•
Prerequisites
The following prerequisites must be met before configuring the Telnet, HTTP, and XML host services:
•
•
See "Upgrading and Managing Cisco IOS XR Software," for information on installing and activating packages.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
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
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.
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:
•
•
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
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 listSNo. Label/ID User Line Client Time Stamp~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~1 1000000219 cisco vty0 CLI 12:27:50 UTC Wed Mar 22 20062 1000000218 cisco vty1 CLI 11:43:31 UTC Mon Mar 20 20063 1000000217 cisco con0_RP0_C CLI 17:44:29 UTC Wed Mar 15 2006RP/0/RP1/CPU0:router# adminRP/0/RP1/CPU0:router(admin)# show configuration commit listSNo. Label/ID User Line Client Time Stamp~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~1 2000000022 cisco vty1 CLI 15:03:59 UTC Fri Mar 17 20062 2000000021 cisco con0_RP0_C CLI 17:42:55 UTC Wed Mar 15 20063 2000000020 SYSTEM con0_RP0_C Setup Dial 17:07:39 UTC Wed Mar 15 2006Displaying the Configuration History Log
To display the header records for up to 1000 commit events, enter the show configuration commit history command in EXEC or administration 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.
RP/0/RP0/CPU0:router# show configuration commit historySNo. Label/ID User Line Client Time Stamp~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~1 1000000144 user_a vty0 CLI 00:16:51 UTC Thu May 11 20042 1000000143 user_a vty0 CLI 00:04:32 UTC Thu May 11 20043 1000000142 user_a 0.0.0.0 XMLAgent 21:58:36 UTC Wed May 11 20044 1000000141 user_a 0.0.0.0 XMLAgent 21:46:07 UTC Wed May 11 20045 1000000140 user_b con0_RP1_C CLI 21:43:30 UTC Wed May 11 20046 1000000139 user_a 0.0.0.0 XMLAgent 21:40:13 UTC Wed May 11 20047 1000000138 user_a 0.0.0.0 XMLAgent 21:34:48 UTC Wed May 11 20048 1000000137 user_b con0_RP1_C CLI 21:32:10 UTC Wed May 11 20049 1000000136 user_a 0.0.0.0 XMLAgent 21:30:13 UTC Wed May 11 200410 1000000135 user_b con0_RP1_C CLI 19:45:04 UTC Wed May 11 200411 1000000134 user_b con0_RP1_C CLI 19:37:26 UTC Wed May 11 200412 1000000133 user_b con0_RP1_C CLI 19:36:27 UTC Wed May 11 200413 1000000132 user_b con0_33_1 Rollback 18:34:45 UTC Wed May 11 200414 1000000131 user_b con0_33_1 Rollback 18:32:37 UTC Wed May 11 200415 1000000130 user_b con0_33_1 Rollback 18:31:09 UTC Wed May 11 200416 1000000129 user_b con0_33_1 CLI 18:28:12 UTC Wed May 11 200417 1000000128 user_b con0_33_1 CLI 18:27:22 UTC Wed May 11 200418 1000000127 user_b con0_33_1 CLI 18:27:19 UTC Wed May 11 200419 1000000126 user_b con0_33_1 Rollback 18:25:55 UTC Wed May 11 200420 1000000125 user_b con0_33_1 Rollback 18:24:25 UTC Wed May 11 2004Displaying 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> commitssince Changes made since (and including) a specific commit2000000020 Commit ID2000000021 Commit ID2000000022 Commit IDRP/0/RP1/CPU0:router(admin)# show configuration commit changes 2000000020Building configuration...username ciscosecret 5 $1$MgUH$xzUEW6jLfyAYLKJE.3p440group root-system!endPreviewing 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 ID1000000218 Commit ID1000000219 Commit IDRP/0/RP1/CPU0:router# show configuration rollback changes to 1000000218Building configuration...no interface Loopback100interface POS0/1/0/0no ipv6 nd dad attempts!!no route-policy xxendTo 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 2Building configuration...interface Loopback3no descriptionno ipv4 address 10.0.1.1 255.0.0.0exitinterface Loopback4no descriptionno ipv4 address 10.0.0.1 255.0.0.0endIn 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.
Tip
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 1000000220Loading Rollback Changes.Loaded Rollback Changes in 1 secCommitting.2 items committed in 1 sec (1)items/secUpdating.Updated Commit database in 1 secConfiguration 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 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 2Loading Rollback Changes.Loaded Rollback Changes in 1 secCommitting.1 items committed in 1 sec (0)items/secUpdating.Updated Commit database in 1 secConfiguration 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.
Note
To load commitID changes in the target configuration, go to global configuration or administration configuration mode and enter the load commit changes command with the commitID number. In the following example, show commands are used to display the changes for a commitID, the commitID configuration is loaded into the target configuration, and the target configuration is displayed:
RP/0/RP1/CPU0:router# show configuration commit changes ?last Changes made in the most recent <n> commitssince Changes made since (and including) a specific commit1000000217 Commit ID1000000218 Commit ID1000000219 Commit ID1000000220 Commit ID1000000221 Commit IDRP/0/RP1/CPU0:router# show configuration commit changes 1000000219Building configuration...interface Loopback100!interface POS0/1/0/0ipv6 nd dad attempts 50!endRP/0/RP1/CPU0:router# configRP/0/RP1/CPU0:router(config)# load commit changes 1000000219Building configuration...Loading.77 bytes parsed in 1 sec (76)bytes/secRP/0/RP1/CPU0:router(config)# show configurationBuilding configuration...interface Loopback100!interface POS0/1/0/0ipv6 nd dad attempts 50!endLoading Rollback Configuration Changes to the Target Configuration
If the changes for a specific rollback point are close to what you want, but a rollback is not appropriate, you can load the rollback configuration changes 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.
Tip
To load rollback configuration changes from the current configuration to a specific session, go to global configuration or administration configuration mode and enter the load rollback changes to commitId command:
RP/0/0/CPU0:router(config)# load rollback changes to 1000000068Building configuration...Loading.233 bytes parsed in 1 sec (231)bytes/secTo load rollback configuration changes from the current configuration to a specified number of previous sessions, go to global configuration or administration configuration mode and enter the load rollback changes last commit-range command:
RP/0/0/CPU0:router(config)# load rollback changes last 6Building configuration...Loading.221 bytes parsed in 1 sec (220)bytes/secIn the preceding example, the command loads the rollback configuration changes for the last six commitIDs.
To load the rollback configuration for a specific commitID, go to global configuration or administration configuration mode and enter the load rollback changes commitId command:
RP/0/0/CPU0:router(config)# load rollback changes 1000000060Building configuration...Loading.199 bytes parsed in 1 sec (198)bytes/secDeleting CommitIDs
You can delete the oldest configuration commitIDs by entering the clear configuration commit command in EXEC or administration 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 50Deleting 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 5Deleting 5 rollback points '1000000005' to '1000000009'80 KB of disk space will be freed. Continue with deletion?[confirm]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, generate complex queries for the list of logged events, and retrieve logging events through an XML interface.
The following sections describe logging and the basic commands used to log messages in Cisco IOS XR software:
•
•
Logging Locations and Severity Levels
Error messages can be logged to a variety of locations, as shown in Table 5-1.
You can log messages based on the severity level of the messages, as shown in Table 5-2.
Alarm Logging Correlation
Alarm logging correlation is used to group and filter similar messages to reduce the amount of redundant logs and isolate the root causes of the messages.
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 extract all correlated messages for display later, should the need arise. See the Cisco IOS XR System Management Configuration Guide for more information.
Configuring Basic Message Logging
Numerous options for logging system messages in Cisco IOS XR software are available. This section provides a basic example.
To configure basic message logging, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Step 1
configure
Example:RP/0/RP0/CPU0:router# configureEnters global configuration mode.
Step 2
logging {ip-address | hostname}
Example:RP/0/RP0/CPU0:router(config)# logging 10.1.1.1
Specifies a syslog server host to use for system logging.
Step 3
logging trap severity
Example:RP/0/RP0/CPU0:router(config)# logging trap debugging
Limits the logging of messages sent to syslog servers to only those messages at the specified level.
•
Step 4
logging console [severity]
Example:RP/0/RP0/CPU0:router(config)# logging console emergencies
Logs messages on the console.
•
•
Step 5
logging buffered [severity | buffer-size]
Example:RP/0/RP0/CPU0:router(config)# logging buffered 1000000
Copies logging messages to an internal buffer.
•
•
•
Step 6
commit
Example:RP/0/RP0/CPU0:router(config)# commit
Commits the target configuration to the router running configuration.
Step 7
end
Example:RP/0/RP0/CPU0:router(config)# end
Ends the configuration session and returns to EXEC mode.
Step 8
show logging
Example:RP/0/RP0/CPU0:router# show logging
Displays the messages that are logged in the buffer.
Examples
In the following example, basic message logging is configured:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# logging 10.1.1.1RP/0/RP0/CPU0:router(config)# logging trap debuggingRP/0/RP0/CPU0:router(config)# logging console emergenciesRP/0/RP0/CPU0:router(config)# logging buffered 1000000RP/0/RP0/CPU0:router(config)# commitRP/0/RP0/CPU0:router(config)# endRP/0/RP0/CPU0:router# show loggingSyslog logging: enabled (162 messages dropped, 0 flushes, 0 overruns)Console logging: level emergencies, 593 messages loggedMonitor logging: level debugging, 0 messages loggedTrap logging: level debugging, 2 messages loggedLogging to 10.1.1.1, 2 message lines loggedBuffer logging: level debugging, 722 messages loggedLog Buffer (1000000 bytes):RP/0/RP0/CPU0:Apr 8 19:18:58.679 : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OPRP/0/RP0/CPU0:Apr 8 19:19:01.287 : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OPRP/0/RP0/CPU0:Apr 8 19:22:15.658 : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OPLC/0/1/CPU0:Apr 8 19:22:30.122 : sysmgr[74]: %OS-SYSMGR-7-INSTALL_NOTIFICATIONLC/0/6/CPU0:Apr 8 19:22:30.160 : sysmgr[74]: %OS-SYSMGR-7-INSTALL_NOTIFICATIONRP/0/RP0/CPU0:Apr 8 19:22:30.745 : sysmgr[79]: %OS-SYSMGR-7-INSTALL_NOTIFICATIRP/0/RP1/CPU0:Apr 8 19:22:32.596 : sysmgr[79]: %OS-SYSMGR-7-INSTALL_NOTIFICATILC/0/1/CPU0:Apr 8 19:22:35.181 : sysmgr[74]: %OS-SYSMGR-7-INSTALL_FINISHED : sLC/0/6/CPU0:Apr 8 19:22:35.223 : sysmgr[74]: %OS-SYSMGR-7-INSTALL_FINISHED : sRP/0/RP0/CPU0:Apr 8 19:22:36.122 : sysmgr[79]: %OS-SYSMGR-7-INSTALL_FINISHED :RP/0/RP1/CPU0:Apr 8 19:22:37.790 : sysmgr[79]: %OS-SYSMGR-7-INSTALL_FINISHED :RP/0/RP0/CPU0:Apr 8 19:22:41.015 : schema_server[332]: %MGBL-SCHEMA-6-VERSIONCRP/0/RP0/CPU0:Apr 8 19:22:59.844 : instdir[203]: %INSTALL-INSTMGR-4-ACTIVE_SOFRP/0/RP0/CPU0:Apr 8 19:22:59.851 : instdir[203]: %INSTALL-INSTMGR-6-INSTALL_OP--More--Related Documents
For more information on message logging and configuration of alarm correlation, see the following Cisco documents:
Disabling Console Logging
To disable console logging, enter the logging console disable command in global configuration mode.
Creating and Modifying User Accounts and User Groups
In the Cisco IOS XR software, users are assigned individual usernames and passwords. Each username is assigned to one or more user groups, each of which defines display and configuration commands the user is authorized to execute. This authorization is enabled by default in the Cisco IOS XR software, and each user must log in to the system using a unique username and password.
The following sections describe the basic commands used to configure users and user groups. For a summary of user accounts, user groups, and task IDs, see the "User Access Privileges" section.
•
Note
Displaying Details About User Accounts, User Groups, and Task IDs
Table 5-3 summarizes the EXEC mode commands used to display details about user accounts, user groups, and task IDs.
Table 5-3 Commands to Display Details About Users and User Groups
Configuring User Accounts
User accounts, user groups, and task groups are created by entering the appropriate commands in one of the "AAA" configuration submodes, as shown in Figure 5-1.
This section describes the process to configure usernames. For instructions to configure user groups, task groups, and other AAA security features, see the Cisco IOS XR System Security Configuration Guide.
Figure 5-1 AAA Configuration Submodes
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.
2.
3.
or
secret {0 | 5} password4.
5.
6.
DETAILED STEPS
Related Documents
For more information on configuration and management of users and user access privileges, see the following Cisco documents:
Create users, assign users to user groups, create and modify user groups, and configure remote AAA access
Cisco IOS XR System Security Configuration Guide
Configuration Limiting
The Cisco IOS XR software places preset limits on the configurations you can apply to the running configuration of a router. These limits ensure that the router has sufficient system resources (such as RAM) for normal operations. Under most conditions, these preset limits are sufficient.
In some cases, for which a large number of configurations is required for a particular feature, it may be necessary to override the preset configuration limits. This override can be done only if configurations for another feature are low or unused. For example, if a router requires a large number of BGP configurations and Multiprotocol Label Switching (MPLS) is not being used at all, then the BGP limits can be increased to use the unused memory assigned to MPLS.
Caution
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
Table 5-4 summarizes the maximum limits for static routes, including the commands used to display and change the limits.
Table 5-4 Static Route Configuration Limits and Commands
Examples
In the following example, the maximum number of static IPv4 routes is changed to 5000 and the new configuration is displayed.
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router staticRP/0/RP1/CPU0:router(config-static)# maximum path ipv4 5000RP/0/RP1/CPU0:router(config-static)# commitRP/0/RP1/CPU0:router(config-static)# show running-config router staticrouter staticmaximum path ipv4 5000address-family ipv4 unicast0.0.0.0/0 172.29.52.1!!IS-IS Configuration Limits
Table 5-5 summarizes the maximum limits for IS-IS, including the commands used to display and change the limits.
Table 5-5 IS-IS Configuration Limits and Commands
Examples
In the following example, the maximum number of active parallel paths for each route is increased to 10, and the maximum number of prefixes redistributed into IS-IS is increased to 12,000:
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router isis 100 address-family ipv4RP/0/RP1/CPU0:router(config-isis-af)# maximum-paths 10RP/0/RP1/CPU0:router(config-isis-af)# maximum-redistributed-prefixes 12000RP/0/RP1/CPU0:router(config-isis-af)# commitRP/0/RP1/CPU0:Mar 30 14:11:07 : config[65739]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000535' to view the changes.RP/0/RP1/CPU0:router(config-isis-af)#OSPFv2 and v3 Configuration Limits
Table 5-6 summarizes the maximum limits for OSPF, including the commands used to display and change the limits.
Table 5-6 OSPFv2 and OSPFv3 Configuration Limits and Commands
Examples
The following subsections provide the following examples:
•
•
•
Maximum Interfaces for Each OSPF Instance
In the following example, the show ospf command is used to display the maximum number of OSPF interfaces:
RP/0/RP1/CPU0:router# show ospfRouting Process "ospf 100" with ID 0.0.0.0Supports only single TOS(TOS0) routesSupports opaque LSAIt is an area border routerInitial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsInitial LSA throttle delay 500 msecsMinimum hold time for LSA throttle 5000 msecsMaximum wait time for LSA throttle 5000 msecsMinimum LSA interval 5 secs. Minimum LSA arrival 1 secsMaximum number of configured interfaces 255--More--The following example configures the maximum interface limit on a router:
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router ospf 100RP/0/RP1/CPU0:router(config-router)# maximum interfaces 600RP/0/RP1/CPU0:router(config-router)# endUncommitted changes found, commit them? [yes]: yRP/0/RP1/CPU0:Mar 30 16:12:39 : config[65740]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000540' to view the changes.RP/0/RP1/CPU0:Mar 30 16:12:39 : config[65740]: %SYS-5-CONFIG_I : Configured fromconsole by ciscoRP/0/RP1/CPU0:router# show ospfRouting Process "ospf 100" with ID 0.0.0.0Supports only single TOS(TOS0) routesSupports opaque LSAIt is an area border routerInitial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsInitial LSA throttle delay 500 msecsMinimum hold time for LSA throttle 5000 msecsMaximum wait time for LSA throttle 5000 msecsMinimum LSA interval 5 secs. Minimum LSA arrival 1 secsMaximum number of configured interfaces 600--More--Maximum Routes Redistributed into OSPF
In the following example, the maximum redistributed-prefixes command is used to set the maximum routes redistributed into OSPF:
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router ospf 100RP/0/RP1/CPU0:router(config-router)# maximum redistributed-prefixes 12000RP/0/RP1/CPU0:router(config-router)# endUncommitted changes found, commit them? [yes]: yRP/0/RP1/CPU0:Mar 30 16:26:52 : config[65740]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000541' to viewthe changes.RP/0/RP1/CPU0:Mar 30 16:26:52 : config[65740]: %SYS-5-CONFIG_I : Configured fromconsole by ciscoRP/0/RP1/CPU0:router#Number of Parallel Links (max-paths)
In the following example, the maximum paths command is used to set the maximum number of parallel routes:
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router ospf 100RP/0/RP1/CPU0:router(config-router)# maximum paths 10
