Cisco IOS XE IP Routing Protocols Configuration Guide, Release 2 - OSPF Limit on Number of Redistributed Routes [Cisco IOS XE Software]

Table Of Contents

OSPF Limit on Number of Redistributed Routes

Finding Feature Information

Contents

Prerequisites for OSPF Limit on Number of Redistributed Routes

Information About OSPF Limit on Number of Redistributed Routes

Benefits of OSPF Limit on Number of Redistributed Routes

How to Limit the Number of OSPF Redistributed Routes or Receive a Warning About the Number of OSPF Redistributed Routes

Limiting the Number of Redistributed Routes

Requesting a Warning About the Number of Routes Redistributed into OSPF

Configuration Examples for OSPF Limit on Number of Redistributed Routes

OSPF Limit the Number of Redistributed Routes: Example

Requesting a Warning About the Number of Redistributed Routes: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for OSPF Limit on Number of Redistributed Routes

OSPF Limit on Number of Redistributed Routes

Last Updated: May 4, 2009

Open Shortest Path First (OSPF) supports a user-defined maximum number of prefixes (routes) that are allowed to be redistributed into OSPF from other protocols or other OSPF processes. Such a limit could help prevent the router from being flooded by too many redistributed routes.

Finding Feature Information

For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for OSPF Limit on Number of Redistributed Routes" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for OSPF Limit on Number of Redistributed Routes

•Information About OSPF Limit on Number of Redistributed Routes

•How to Limit the Number of OSPF Redistributed Routes or Receive a Warning About the Number of OSPF Redistributed Routes

•Configuration Examples for OSPF Limit on Number of Redistributed Routes

•Additional References

•Feature Information for OSPF Limit on Number of Redistributed Routes

Prerequisites for OSPF Limit on Number of Redistributed Routes

It is presumed that you have OSPF configured in your network, along with another protocol or another OSPF process you are redistributing.

Information About OSPF Limit on Number of Redistributed Routes

Before you limit the number of OSPF redistributed routes, you should understand the concept described in this section.

•Benefits of OSPF Limit on Number of Redistributed Routes

Benefits of OSPF Limit on Number of Redistributed Routes

If someone mistakenly injects a large number of IP routes into OSPF, perhaps by redistributing Border Gateway Protocol (BGP) into OSPF, the network can be severely flooded. Limiting the number of redistributed routes prevents this potential problem.

How to Limit the Number of OSPF Redistributed Routes or Receive a Warning About the Number of OSPF Redistributed Routes

This section contains the following procedures, which are mutually exclusive. That is, you cannot both limit redistributed prefixes and also choose to be warned.

•Limiting the Number of Redistributed Routes

•Requesting a Warning About the Number of Routes Redistributed into OSPF

Limiting the Number of Redistributed Routes

This task describes how to limit the number of routes redistributed into OSPF. If the number of redistributed routes reaches the maximum value configured, no more routes will be redistributed.

The redistribution limit applies to all IP redistributed prefixes, including summarized ones. The redistribution limit does not apply to default routes or prefixes that are generated as a result of Type-7 to Type-5 translation.

SUMMARY STEPS

1. enable

2. configure terminal

3. router ospf process-id

4. redistribute protocol [process-id] [as-number] [metric metric-value] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [subnets]

5. redistribute maximum-prefix maximum [threshold]

6. end

7. show ip ospf [process-id]

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

router ospf process-id
Example:

Router(config)# router ospf 1

Configures an OSPF routing process.

Step 4

redistribute protocol [process-id] [as-number] [metric metric-value] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [subnets]
Example:

Router(config-router)# redistribute eigrp 10

Redistributes routes from one routing domain into another routing domain.

Step 5

redistribute maximum-prefix maximum [threshold]
Example:

Router(config-router)# redistribute maximum-prefix 100 80

Sets a maximum number of IP prefixes that are allowed to be redistributed into OSPF.

•There is no default value for the maximum argument.

•The threshold value defaults to 75 percent.

Note If the warning-only keyword had been configured in this command, no limit would be enforced; a warning message is simply logged.

Step 6

end
Example:

Router(config-router)# end

Exits router configuration mode.

Step 7

show ip ospf [process-id]
Example:

Router# show ip ospf 1

(Optional) Displays general information about OSPF routing processes.

•If a redistribution limit was configured, the output will include the maximum limit of redistributed prefixes and the threshold for warning messages.

Requesting a Warning About the Number of Routes Redistributed into OSPF

This task describes how to cause the system to generate a warning message when the number of redistributed prefixes reaches a maximum value. However, additional redistribution is not prevented.

The redistribution count applies to external IP prefixes, including summarized routes. Default routes and prefixes that are generated as a result of Type-7 to Type-5 translation are not considered.

SUMMARY STEPS

1. enable

2. configure terminal

3. router ospf process-id

4. redistribute protocol [process-id] [as-number] [metric metric-value] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [subnets]

5. redistribute maximum-prefix maximum [threshold] warning-only

6. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

router ospf process-id
Example:

Router(config)# router ospf 1

Configures an OSPF routing process.

Step 4

redistribute protocol [process-id] [as-number] [metric metric-value] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [subnets]
Example:

Router(config-router)# redistribute eigrp 10

Redistributes routes from one routing domain into another routing domain.

Step 5

redistribute maximum-prefix maximum [threshold] warning-only
Example:

Router(config-router)# redistribute maximum-prefix 1000 80 warning-only

Causes a warning message to be logged when the maximum number of IP prefixes has been redistributed into OSPF.

•Because the warning-only keyword is included, no limit is imposed on the number of redistributed prefixes into OSPF.

•There is no default value for the maximum argument.

•The threshold value defaults to 75 percent.

•This example causes two warnings: one at 80 percent of 1000 (800 routes redistributed) and another at 1000 routes redistributed.

Step 6

end
Example:

Router(config-router)# end

Exits router configuration mode.

Configuration Examples for OSPF Limit on Number of Redistributed Routes

This section contains the following examples:

•OSPF Limit the Number of Redistributed Routes: Example

•Requesting a Warning About the Number of Redistributed Routes: Example

OSPF Limit the Number of Redistributed Routes: Example

This example sets a maximum of 1200 prefixes that can be redistributed into OSPF process 1. Prior to reaching the limit, when the number of prefixes redistributed reaches 80 percent of 1200 (960 prefixes), a warning message is logged. Another warning is logged when the limit is reached and no more routes are redistributed.
router ospf 1 
 router-id 10.0.0.1 
 domain-id 5.6.7.8 
 log-adjacency-changes 
 timers lsa-interval 2 
 network 10.0.0.1 0.0.0.0 area 0 
 network 10.1.5.1 0.0.0.0 area 0 
 network 10.2.2.1 0.0.0.0 area 0 
 redistribute static subnets
 redistribute maximum-prefix 1200 80
Requesting a Warning About the Number of Redistributed Routes: Example

This example allows two warning messages to be logged, the first if the number of prefixes redistributed reaches 85 percent of 600 (510 prefixes), and the second if the number of redistributed routes reaches 600. However, the number of redistributed routes is not limited.
router ospf 1
 network 10.0.0.0 0.0.0.255 area 0 
 redistribute eigrp 10 subnets
 redistribute maximum-prefix 600 85 warning-only
Additional References

The following sections provide references related to OSPF Limit on Number of Redistributed Routes.

Related Documents

Related Topic

Document Title

OSPF commands

Cisco IOS IP Routing Protocols Command Reference

Configuring OSPF

"Configuring OSPF" chapter in the Cisco IOS XE IP Routing Protocols Configuration Guide, Release 2

Cisco IOS master command list, all releases

Cisco IOS Master Command List, All Releases

Standards

Standard

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

—

MIBs

MIB

MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFC

Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/public/support/tac/home.shtml

Feature Information for OSPF Limit on Number of Redistributed Routes

Table 1 lists the release history for this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

Table 1 Feature Information for OSPF Limit on Number of Redistributed Routes

Feature Name

Releases

Feature Information

OSPF Limit on Number of Redistributed Routes

Cisco IOS XE
Release 2.1

OSPF supports a user-defined maximum number of prefixes (routes) that are allowed to be redistributed into OSPF from other protocols or other OSPF processes. Such a limit could help prevent the router from being flooded by too many redistributed routes.

The following commands are introduced or modified in the feature documented in this module:

•redistribute maximum-prefix

•show ip ospf

•show ip ospf database

CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2008-2009 Cisco Systems, Inc. All rights reserved.