-
Cisco IOS XR Getting Started Guide, Release 3.2
-
Preface
-
Chapter 1 - Getting Started with Cisco IOS XR Software
-
Chapter 2 - Configuring General Router Features
-
Chapter 3 - Configuring Additional Router Features
-
Chapter 4 - CLI Tips, Techniques and Shortcuts
-
Chapter 5 - Managing Cisco IOS XR Software Packages
-
Chapter 6 - Managing the Router Hardware
-
Chapter 7 - Troubleshooting the Cisco IOS XR Software
-
Appendix A - Router Recovery and Management with ROM Monitor
-
Appendix B - Upgrading and Downgrading ROM Monitor Software on Cisco CRS-1 Routers
-
Appendix C - Upgrading and Downgrading Boothelper and ROM Monitor on Cisco XR 12000 Routers
-
Appendix D - 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 the Configuration Changes for a Specific CommitID
Loading Rollback Configuration Changes to the Target Configuration
Saving and Loading Target Configuration Files
Saving the Target Configuration to a File
Loading the Target Configuration from a File
Loading an Alternative Configuration at System Startup
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:
•
•
•
Note
Prerequisites
The following prerequisites must be met before configuring the Telnet, HTTP, and XML host services:
•
•
See Chapter 5, "Managing Cisco IOS XR Software Packages," 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 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:
RP/0/RP0/CPU0:router# show configuration commit listSNo. Label/ID User Line Client Time Stamp~~~~ ~~~~~~~~ ~~~~ ~~~~ ~~~~~~ ~~~~~~~~~~1 1000000391 user_a con0_33_1 CLI 19:29:18 UTC Wed Jan 10 20042 1000000390 user_a con0_33_1 CLI 19:29:16 UTC Wed Jan 10 20043 1000000389 user_a con0_33_1 CLI 19:29:15 UTC Wed Jan 10 20044 1000000388 user_a con0_33_1 CLI 19:29:12 UTC Wed Jan 10 20045 1000000387 user_a con0_33_1 CLI 19:26:16 UTC Wed Jan 10 20046 1000000386 user_a con0_32_1 CLI 19:18:38 UTC Wed Jan 10 20047 1000000385 user_a con0_33_1 CLI 19:14:09 UTC Wed Jan 10 20048 1000000384 user_a con0_33_1 CLI 19:13:58 UTC Wed Jan 10 20049 1000000383 user_a con0_33_1 CLI 19:13:33 UTC Wed Jan 10 200410 1000000382 user_a con0_33_1 CLI 19:12:50 UTC Wed Jan 10 200411 1000000381 user_a con0_33_1 CLI 19:12:48 UTC Wed Jan 10 200412 1000000380 user_a con0_33_1 CLI 19:12:46 UTC Wed Jan 10 200413 1000000379 user_a con0_33_1 CLI 19:12:43 UTC Wed Jan 10 200414 1000000378 user_a con0_33_1 CLI 19:12:14 UTC Wed Jan 10 200415 1000000377 user_a con0_33_1 CLI 19:10:47 UTC Wed Jan 10 2004Displaying 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.
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), 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 1000000071Building configuration...hostname router2endPreviewing 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 session, enter the show configuration rollback changes to commitId command:
RP/0/RP0/CPU0:router# show configuration rollback changes to 1000000373Building configuration...interface Loopback2no descriptionno ipv4 address 10.0.0.1 255.0.0.0To 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 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.
Tip
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 1000000325Configuration 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.
Tip
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 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 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 1000000066Building configuration...Loading.21 bytes parsed in 1 sec (20)bytes/secThe configuration changes are added to the target configuration and are not applied until you enter the commit command.
Tip
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.
Tip
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 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, 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, 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 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]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
To save the configuration changes in the target configuration to a file, enter the show configuration | file filename command.
•
•
Tip
In the following example, a target configuration file is saved to the root of disk0:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# show configuration | file disk0:myconfig.cfgRP/0/RP0/CPU0:router(config)# abortRP/0/RP0/CPU0:router#Loading the Target Configuration from a File
Enter the load filename command to populate the target configuration with the contents of a previously saved configuration file. Consider the following when entering the filename argument:
•
•
In the following example, a target configuration file is loaded into the current configuration session. The current configuration session is therefore populated with the contents of the file:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# load disk0:myconfig.cfgRP/0/RP0/CPU0:router(config)# show configurationBuilding configuration... interface POS 0/3/0/0 description My Pos Interface ipv4 address 10.10.11.20 255.0.0.0 !endLoading an Alternative Configuration at System Startup
When a router is reset or powered on, the last running configuration is loaded and used to operate the router.
You can also load an alternative configuration during system boot. See "Router Recovery and Management with ROM Monitor," for information and instructions on this process.
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 3-1.
You can log messages based on the severity level of the messages, as shown in Table 3-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# configRP/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 (10 messages dropped, 0 flushes, 0 overruns)Console logging: level debugging, 103 messages loggedMonitor logging: level debugging, 0 messages loggedTrap logging: level informational, 0 messages loggedBuffer logging: level debugging, 107 messages loggedLog Buffer (16384 bytes):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 = 1RP/0/RP0/CPU0:Apr 6 21:31:03.099 : ingressq[227]: %INGRESSQ_DLL-3-HALF_DEPTH_PART_DISCOVERED : ingressq dll: half depth memory detected, memory: DQ External QEMemory--More--Related Documents
For more information on message logging and configuration of alarm correlation, see the following Cisco documents:
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 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
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 3-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 3-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.
or
commitDETAILED 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 3-4 summarizes the maximum limits for static routes, including the commands used to display and change the limits.
Table 3-4 Static Route Configuration Limits and Commands
Maximum static IPv4 routes
4000
128,000
route maximum ipv4 n
show running-config route maximum
Maximum static IPv61 routes
4000
128,000
route maximum ipv6 n
show running-config route maximum
1 IPv6 is not supported on the Cisco XR 12000 Series Router.
Examples
In the following example, the maximum number of static IPv4 routes is changed to 5000. The new setting is then displayed with the show running-config route maximum command.
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# route maximum ipv4 5000RP/0/RP1/CPU0:router(config)# commitRP/0/RP1/CPU0:Mar 30 15:50:38 : ipv4_static[214]: %IP_STATIC-6-CONFIG_MAXIMUM_CHANGE : The maximum number of configurations for static routes has been changed from 4000 to 5000RP/0/RP1/CPU0:Mar 30 15:50:39 : config[65740]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000538' to view the changes.RP/0/RP1/CPU0:router(config)# endRP/0/RP1/CPU0:Mar 30 15:50:46 : config[65740]: %SYS-5-CONFIG_I : Configured fromconsole by labRP/0/RP1/CPU0:router# show running-config route maximumroute maximum ipv4 5000RP/0/RP1/CPU0:router#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
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 'lab'. Use 'show configuration commit changes 1000000535' to view the changes.RP/0/RP1/CPU0:router(config-isis-af)#OSPFv2 and v3 Configuration Limits
Table 3-6 summarizes the maximum limits for OSPF, including the commands used to display and change the limits.
Table 3-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 'lab'. 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 labRP/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 'lab'. 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 labRP/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 10RP/0/RP1/CPU0:router(config-router)# endUncommitted changes found, commit them? [yes]: yRP/0/RP1/CPU0:Mar 30 18:05:13 : config[65740]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000542' to view the changes.RP/0/RP1/CPU0:Mar 30 18:05:13 : config[65740]: %SYS-5-CONFIG_I : Configured fromconsole by labRP/0/RP1/CPU0:router#BGP Configuration Limits
The maximum number of BGP neighbors (peers) that can be configured is 1024. This number cannot be changed through configuration. Any attempt to configure additional neighbors beyond the limit fails.
To prevent neighbors (peers) from flooding BGP with advertisements, a limit is placed on the number of prefixes that can be accepted from a peer for each supported address family.
You can override the default limits for an address family with the maximum-prefix command. Table 3-7 summarizes the maximum configuration limits for BGP.
Table 3-7 BGP Configuration Limits and Commands
Maximum number of neighbors (peers).
1024
1024
None. This limit cannot be changed or exceeded.
None
IPv4 unicast maximum prefixes that can be received from a neighbor
524,288
4,294,967,295
maximum-prefix n
show bgp neighbor IP_address
IPv4 multicast maximum prefixes that can be received from a neighbor
131,072
4,294,967,295
maximum-prefix n
show bgp neighbor IP_address
IPv61 unicast maximum prefixes that can be received from a neighbor
131,072
4,294,967,295
maximum-prefix n
show bgp neighbor IP_address
Maximum equal-cost parallel routes to external peers
1
8
maximum-paths n
show running-config
Note
1 IPv6 is not supported on the Cisco XR 12000 Series Router.
A cease-notification message is sent to the neighbor and the peering with the neighbor is terminated when the number of prefixes received from the peer for a given address family exceeds the maximum limit (either set by default or configured by the user) for that address family.
However, if the warning-only keyword (for the maximum-prefix command) is configured, the Cisco IOS XR software sends only a log message, but continues peering with the sender. If the peer is terminated, the peer stays down until the clear bgp command is issued.
The same set of actions (sending cease notification followed by the termination of the peering) is taken for a neighbor with which peering has already been established if you decide to configure a maximum that is less than the number of prefixes that have already been received from the neighbor.
Examples
The following example shows how to set the maximum number of IPv4 unicast prefixes allowed from the neighbor at 10.1.1.1 to 100,000:
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# router bgp 100RP/0/RP1/CPU0:router(config-bgp)# neighbor 10.1.1.1RP/0/RP1/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP1/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP1/CPU0:router(config-bgp-nbr-af)# maximum-prefix 100000RP/0/RP1/CPU0:router(config-bgp-nbr-af)# commitRP/0/RP1/CPU0:Mar 30 19:13:16 : config[65740]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000544' to view the changes.RP/0/RP1/CPU0:Mar 30 19:13:17 : config[65740]: %SYS-5-CONFIG_I : Configured fromconsole by labRP/0/RP1/CPU0:router(config-bgp-nbr-af)#Routing Policy Language Line and Policy Limits
Two limits for Routing Policy Language (RPL) configurations exist:
1.
2.
The limits for RPL lines and policies are summarized in Table 3-8. You can change the default values up to the absolute maximum, but you cannot change the value to a number less than the number of items that are currently configured.
Table 3-8 Maximum Lines of RPL: Configuration Limits and Commands
Examples
In the following example, the show rpl maximum command is used in EXEC mode to display the current setting for RPL limits and number of each limit currently in use. A summary of the memory used by all of the defined policies is also shown below the limit settings.
RP/0/RP1/CPU0:router# show rpl maximumCurrent Current MaxTotal Limit Limit------------------------------------------------------------Lines of configuration 0 65536 131072Policies 0 3500 5000Compiled policies size (kB) 0RP/0/RP1/CPU0:router#In the next example, the rpl maximum command changes the currently configured line and policy limits. The show rpl maximum command displays the new settings.
RP/0/RP1/CPU0:router# configureRP/0/RP1/CPU0:router(config)# rpl maximum policies 4000RP/0/RP1/CPU0:router(config)# rpl maximum lines 80000RP/0/RP1/CPU0:router(config)# commitRP/0/RP1/CPU0:Apr 1 00:23:44.062 : config[65709]: %LIBTARCFG-6-COMMIT : Configuration committed by user 'UNKNOWN'. Use 'show configuration commit changes 1000000010' to view the changes.RP/0/RP1/CPU0:router(config)# exitRP/0/RP1/CPU0:Apr 1 00:23:47.781 : config[65709]: %SYS-5-CONFIG_I : Configuredfrom console by consoleRP/0/RP1/CPU0:router# show rpl maximumCurrent Current MaxTotal Limit Limit------------------------------------------------------------Lines of configuration 0 80000 131072Policies 0 4000 5000Compiled policies size (kB) 0RP/0/RP1/CPU0:router#Multicast Configuration Limits
Table 3-9 summarizes the maximum limits for multicast configuration, including the commands used to display and change the limits.
MPLS Configuration Limits
Table 3-10 summarizes the maximum limits for MPLS configuration, including the commands used to display and change the limits.
Table 3-10 MPLS Configuration Limits and Commands
Other Configuration Limits
Table 3-11 summarizes the maximum limits for additional configuration limits, including the commands used to display and change the limits.
Table 3-11 Additional Configuration Limits and Commands
IPv4 ACL
(access list and prefix list)
5000
9000
ipv4 access-list oor acl threshold n
show ipv4 access-lists
IPv4 ACE
(access list and prefix list)
200,000
350,000
ipv4 access-list oor ace threshold n
show ipv4 access-lists
IPv61 ACL
(access list and prefix list)
1000
2000
ipv6 access-list oor acl threshold n
show ipv4 access-lists
IPv61 ACE
(access list and prefix list)
50,000
100,000
ipv6 access-list oor ace threshold n
show ipv4 access-lists
1 IPv6 is not supported on the Cisco XR 12000 Series Router.
