Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Americas Headquarters
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED
WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version
of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL
FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR
ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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,
network topology diagrams, and other 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.
2011 Cisco Systems, Inc. All rights reserved.
CONTENTS
Configuring OSPF 1
Finding Feature Information 1
Information About OSPF 1
Cisco OSPF Implementation 2
Router Coordination for OSPF 2
Route Distribution for OSPF 2
OSPF Network Types 3
Original LSA Behavior 7
LSA Group Pacing with Multiple Timers 7
How to Configure OSPF 9
Enabling OSPF 10
Configuring OSPF Interface Parameters 11
Configuring OSPF over Different Physical Networks 13
Configuring Point-to-Multipoint Broadcast Networks 13
Configuring OSPF for Nonbroadcast Networks 13
Configuring OSPF Area Parameters 14
Configuring OSPF Area Parameters 14
Configuring OSPF NSSA 16
Configuring an OSPF NSSA Area and Its Parameters 16
Configuring an NSSA ABR as a Forced NSSA LSA Translator 17
Disabling RFC 3101 Compatibility and Enabling RFC 1587 Compatibility 19
Configuring OSPF NSSA Parameters 20
Prerequisites 20
Configuring OSPF NSSA Area Parameters 20
Configuring Route Summarization Between OSPF Areas 21
Configuring Route Summarization Between OSPF Areas Configuring Route
Summarization Between OSPF Areas Configuring Route Summarization Between OSPF
Areas 22
Configuring Route Summarization When Redistributing Routes into OSPF 22
Contents
Contents
Contents
Contents
Additional References 82
Feature Information for OSPF Update Packet-Pacing Configurable Timers 84
OSPF Sham-Link Support for MPLS VPN 85
Finding Feature Information 85
Feature Overview 85
Using OSPF in PE-CE Router Connections 86
Using a Sham-Link to Correct OSPF Backdoor Routing 86
Sham-Link Configuration Example 89
Benefits 91
Restrictions 91
Related Features and Technologies 91
Related Documents 91
Supported Platforms 91
Supported Standards MIBs and RFCs 92
Prerequisites 93
Configuration Tasks 93
Creating a Sham-Link 93
Verifying Sham-Link Creation 95
Monitoring and Maintaining a Sham-Link 95
Configuration Examples 95
Glossary 96
OSPF Retransmissions Limit 99
Finding Feature Information 99
Feature Overview 99
Benefits 100
Restrictions 100
Related Features and Technologies 100
Supported Platforms 100
Configuration Tasks 101
Setting OSPF Retransmission Limits 101
OSPF Support for Multi-VRF on CE Routers 103
Finding Feature Information 103
Information About OSPF Support for Multi-VRF on CE Routers 103
How to Configure OSPF Support for Multi-VRF on CE Routers 104
Configuring the Multi-VRF Capability for OSPF Routing 104
Contents
Contents
Contents
Contents
Contents
Contents
Contents
Configuring OSPF
This module describes how to configure Open Shortest Path First (OSPF). OSPF is an Interior Gateway
Protocol (IGP) developed by the OSPF working group of the Internet Engineering Task Force (IETF).
OSPF was designed expressly for IP networks and it supports IP subnetting and tagging of externally
derived routing information. OSPF also allows packet authentication and uses IP multicast when sending
and receiving packets.
Cisco supports RFC 1253, OSPF Version 2 Management Information Base, August 1991. The OSPF MIB
defines an IP routing protocol that provides management information related to OSPF and is supported by
Cisco routers.
For protocol-independent features that work with OSPF, see the "Configuring IP Routing ProtocolIndependent Features" module.
Configuring OSPF
OSPF Network Types
X.25 and Frame Relay provide an optional broadcast capability that can be configured in the map to allow
OSPF to run as a broadcast network. Refer to the x25 map and frame-relay map command descriptions in
the Cisco IOS Wide-Area Networking Command Reference publication for more detail.
On point-to-multipoint, broadcast networks, there is no need to specify neighbors. However, you can
specify neighbors with the neighbor router configuration command, in which case you should specify a
cost to that neighbor.
Before the point-to-multipoint keyword was added to the ip ospf network interface configuration
command, some OSPF point-to-multipoint protocol traffic was treated as multicast traffic. Therefore, the
neighbor router configuration command was not needed for point-to-multipoint interfaces because
multicast took care of the traffic. Hello, update, and acknowledgment messages were sent using multicast.
In particular, multicast hello messages discovered all neighbors dynamically.
On any point-to-multipoint interface (broadcast or not), the Cisco IOS software assumed that the cost to
each neighbor was equal. The cost was configured with the ip ospf cost interface confutation command. In
reality, the bandwidth to each neighbor is different, so the cost should differ. With this feature, you can
configure a separate cost to each neighbor. This feature applies to point-to-multipoint interfaces only.
Because many routers might be attached to an OSPF network, a designated router is selected for the
network. Special configuration parameters are needed in the designated router selection if broadcast
capability is not configured.
These parameters need only be configured in those devices that are themselves eligible to become the
designated router or backup designated router (in other words, routers with a nonzero router priority value).
You can specify the following neighbor parameters, as required:
Configuring OSPF
OSPF Network Types
On point-to-multipoint, nonbroadcast networks, use the neighbor router configuration command to identify
neighbors. Assigning a cost to a neighbor is optional.
Prior to Cisco IOS Release 12.0, some customers were using point-to-multipoint on nonbroadcast media
(such as classic IP over ATM), so their routers could not dynamically discover their neighbors. This feature
allows the neighbor router configuration command to be used on point-to-multipoint interfaces.
On any point-to-multipoint interface (broadcast or not), the Cisco IOS software assumed the cost to each
neighbor was equal. The cost was configured with the ip ospf cost interface configuration command. In
reality, the bandwidth to each neighbor is different, so the cost should differ. With this feature, you can
configure a separate cost to each neighbor. This feature applies to point-to-multipoint interfaces only.
Our OSPF software allows you to configure several area parameters. These area parameters, shown in the
following task table, include authentication, defining stub areas, and assigning specific costs to the default
summary route. Authentication allows password-based protection against unauthorized access to an area.
Stub areas are areas into which information on external routes is not sent. Instead, there is a default external
route generated by the ABR, into the stub area for destinations outside the autonomous system. To take
advantage of the OSPF stub area support, default routing must be used in the stub area. To further reduce
the number of LSAs sent into a stub area, you can configure the no-summary keyword of the area stub
router configuration command on the ABR to prevent it from sending summary link advertisement (LSAs
Type 3) into the stub area.
The OSPF NSSA feature is described by RFC 3101. In Cisco IOS Release 15.1(2)S and later releases, RFC
3101 replaces RFC 1587. RFC 3101 is backward compatible with RFC 1587. For a detailed list of
differences between them, see Appendix F of RFC 3101. NSSA support was first integrated into Cisco IOS
Release 11.2. OSPF NSSA is a nonproprietary extension of the existing OSPF stub area feature.
RFC 3101 support enhances both the Type 7 autonomous-system external routing calculation and the
translation of Type 7 LSAs into Type 5 LSAs. For more information, see RFC 3101.
Use NSSA to simplify administration if you are an Internet service provider (ISP) or a network
administrator that must connect a central site that is using OSPF to a remote site that is using a different
routing protocol.
Prior to NSSA, the connection between the corporate site border router and the remote router could not be
run as an OSPF stub area because routes for the remote site could not be redistributed into the stub area,
and two routing protocols needed to be maintained. A simple protocol such as RIP was usually run and
handled the redistribution. With NSSA, you can extend OSPF to cover the remote connection by defining
the area between the corporate router and the remote router as an NSSA.
As with OSPF stub areas, NSSA areas cannot be injected with distributed routes via Type 5 LSAs. Route
redistribution into an NSSA area is possible only with a special type of LSA that is known as Type 7 that
can exist only in an NSSA area. An NSSA ASBR generates the Type 7 LSA so that the routes can be
redistributed, and an NSSA ABR translates the Type 7 LSA into a Type 5 LSA, which can be flooded
throughout the whole OSPF routing domain. Summarization and filtering are supported during the
translation.
Cisco IOS Release 15.1(2)S and later releases support RFC 3101, which allows you to configure an NSSA
ABR router as a forced NSSA LSA translator. This means that the NSSA ABR router will unconditionally
assume the role of LSA translator, preempting the default behavior, which would only include it among the
candidates to be elected as translator.
Configuring OSPF
OSPF Network Types
Note
Even a forced translator might not translate all LSAs; translation depends on the contents of each LSA.
The figure below shows a network diagram in which OSPF Area 1 is defined as the stub area. The
Enhanced Interior Gateway Routing Protocol (EIGRP) routes cannot be propagated into the OSPF domain
because routing redistribution is not allowed in the stub area. However, once OSPF Area 1 is defined as an
NSSA, an NSSA ASBR can inject the EIGRP routes into the OSPF NSSA by creating Type 7 LSAs.
Figure 1
OSPF NSSA
The redistributed routes from the RIP router will not be allowed into OSPF Area 1 because NSSA is an
extension to the stub area. The stub area characteristics will still exist, including the exclusion of Type 5
LSAs.
Route summarization is the consolidation of advertised addresses. This feature causes a single summary
route to be advertised to other areas by an ABR. In OSPF, an ABR will advertise networks in one area into
another area. If the network numbers in an area are assigned in a way such that they are contiguous, you
can configure the ABR to advertise a summary route that covers all the individual networks within the area
that fall into the specified range.
When routes from other protocols are redistributed into OSPF (as described in the module "Configuring IP
Routing Protocol-Independent Features"), each route is advertised individually in an external LSA.
However, you can configure the Cisco IOS software to advertise a single route for all the redistributed
routes that are covered by a specified network address and mask. Doing so helps decrease the size of the
OSPF link-state database.
In OSPF, all areas must be connected to a backbone area. If there is a break in backbone continuity, or the
backbone is purposefully partitioned, you can establish a virtual link. The two endpoints of a virtual link
are ABRs. The virtual link must be configured in both routers. The configuration information in each router
consists of the other virtual endpoint (the other ABR) and the nonbackbone area that the two routers have
in common (called the transit area). Note that virtual links cannot be configured through stub areas.
You can force an ASBR to generate a default route into an OSPF routing domain. Whenever you
specifically configure redistribution of routes into an OSPF routing domain, the router automatically
Configuring OSPF
OSPF Network Types
becomes an ASBR. However, an ASBR does not, by default, generate a default route into the OSPF routing
domain.
You can configure OSPF to look up Domain Naming System (DNS) names for use in all OSPF show
EXEC command displays. You can use this feature to more easily identify a router, because the router is
displayed by name rather than by its router ID or neighbor ID.
OSPF uses the largest IP address configured on the interfaces as its router ID. If the interface associated
with this IP address is ever brought down, or if the address is removed, the OSPF process must recalculate
a new router ID and resend all its routing information out its interfaces.
If a loopback interface is configured with an IP address, the Cisco IOS software will use this IP address as
its router ID, even if other interfaces have larger IP addresses. Because loopback interfaces never go down,
greater stability in the routing table is achieved.
OSPF automatically prefers a loopback interface over any other kind, and it chooses the highest IP address
among all loopback interfaces. If no loopback interfaces are present, the highest IP address in the router is
chosen. You cannot tell OSPF to use any particular interface.
In Cisco IOS Release 10.3 and later releases, by default OSPF calculates the OSPF metric for an interface
according to the bandwidth of the interface. For example, a 64-kbps link gets a metric of 1562, and a T1
link gets a metric of 64.
The OSPF metric is calculated as the ref-bw value divided by the bandwidth value, with the ref-bw value
equal to 108 by default, and the bandwidth value determined by the bandwidth interface configuration
command. The calculation gives FDDI a metric of 1. If you have multiple links with high bandwidth, you
might want to specify a larger number to differentiate the cost on those links.
An administrative distance is a rating of the trustworthiness of a routing information source, such as an
individual router or a group of routers. Numerically, an administrative distance is an integer from 0 to 255.
In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the
routing information source cannot be trusted at all and should be ignored.
OSPF uses three different administrative distances: intra-area, interarea, and external. Routes within an area
are intra-area; routes to another area are interarea; and routes from another routing domain learned via
redistribution are external. The default distance for each type of route is 110.
Because simplex interfaces between two devices on an Ethernet represent only one network segment, for
OSPF you must configure the sending interface to be a passive interface. This configuration prevents OSPF
from sending hello packets for the sending interface. Both devices are able to see each other via the hello
packet generated for the receiving interface.
You can configure the delay time between when OSPF receives a topology change and when it starts a
shortest path first (SPF) calculation. You can also configure the hold time between two consecutive SPF
calculations.
The OSPF on-demand circuit is an enhancement to the OSPF protocol that allows efficient operation over
on-demand circuits such as ISDN, X.25 switched virtual circuits (SVCs), and dialup lines. This feature
supports RFC 1793, Extending OSPF to Support Demand Circuits.
Prior to this feature, OSPF periodic hello and LSA updates would be exchanged between routers that
connected the on-demand link, even when no changes occurred in the hello or LSA information.
With this feature, periodic hellos are suppressed and the periodic refreshes of LSAs are not flooded over
the demand circuit. These packets bring up the link only when they are exchanged for the first time, or
when a change occurs in the information they contain. This operation allows the underlying data link layer
to be closed when the network topology is stable.
This feature is useful when you want to connect telecommuters or branch offices to an OSPF backbone at a
central site. In this case, OSPF for on-demand circuits allows the benefits of OSPF over the entire domain,
Configuring OSPF
Original LSA Behavior
without excess connection costs. Periodic refreshes of hello updates, LSA updates, and other protocol
overhead are prevented from enabling the on-demand circuit when there is no "real" data to send.
Overhead protocols such as hellos and LSAs are transferred over the on-demand circuit only upon initial
setup and when they reflect a change in the topology. This means that critical changes to the topology that
require new SPF calculations are sent in order to maintain network topology integrity. Periodic refreshes
that do not include changes, however, are not sent across the link.
The OSPF LSA group pacing feature allows the router to group OSPF LSAs and pace the refreshing,
checksumming, and aging functions. The group pacing results in more efficient use of the router.
The router groups OSPF LSAs and paces the refreshing, checksumming, and aging functions so that sudden
increases in CPU usage and network resources are avoided. This feature is most beneficial to large OSPF
networks.
OSPF LSA group pacing is enabled by default. For typical customers, the default group pacing interval for
refreshing, checksumming, and aging is appropriate and you need not configure this feature.
Configuring OSPF
LSA Group Pacing with Multiple Timers
sent out in one packet or more. Thus, the refresh packets are paced, as are the checksumming and aging.
The pacing interval is configurable; it defaults to 4 minutes, which is randomized to further avoid
synchronization.
The figure below illustrates the case of refresh packets. The first timeline illustrates individual LSA timers;
the second timeline illustrates individual LSA timers with group pacing.
Figure 3
The group pacing interval is inversely proportional to the number of LSAs the router is refreshing,
checksumming, and aging. For example, if you have approximately 10,000 LSAs, decreasing the pacing
interval would benefit you. If you have a very small database (40 to 100 LSAs), increasing the pacing
interval to 10 to 20 minutes might benefit you slightly.
The default value of pacing between LSA groups is 240 seconds (4 minutes). The range is from 10 seconds
to 1800 seconds (30 minutes).
By default, OSPF floods new LSAs over all interfaces in the same area, except the interface on which the
LSA arrives. Some redundancy is desirable, because it ensures robust flooding. However, too much
redundancy can waste bandwidth and might destabilize the network due to excessive link and CPU usage in
certain topologies. An example would be a fully meshed topology.
You can block OSPF flooding of LSAs two ways, depending on the type of networks:
On broadcast, nonbroadcast, and point-to-point networks, you can block flooding over specified OSPF
interfaces.
On point-to-multipoint networks, you can block flooding to a specified neighbor.
The growth of the Internet has increased the importance of scalability in IGPs such as OSPF. By design,
OSPF requires LSAs to be refreshed as they expire after 3600 seconds. Some implementations have tried to
improve the flooding by reducing the frequency to refresh from 30 minutes to about 50 minutes. This
solution reduces the amount of refresh traffic but requires at least one refresh before the LSA expires. The
OSPF flooding reduction solution works by reducing unnecessary refreshing and flooding of already
known and unchanged information. To achieve this reduction, the LSAs are now flooded with the higher
bit set. The LSAs are now set as "do not age."
Cisco routers do not support LSA Type 6 Multicast OSPF (MOSPF), and they generate syslog messages if
they receive such packets. If the router is receiving many MOSPF packets, you might want to configure the
router to ignore the packets and thus prevent a large number of syslog messages.
Configuring OSPF
How to Configure OSPF
The former OSPF implementation for sending update packets needed to be more efficient. Some update
packets were getting lost in cases where the link was slow, a neighbor could not receive the updates quickly
enough, or the router was out of buffer space. For example, packets might be dropped if either of the
following topologies existed:
OSPF update packets are now automatically paced so they are not sent less than 33 milliseconds apart.
Pacing is also added between resends to increase efficiency and minimize lost retransmissions. Also, you
can display the LSAs waiting to be sent out an interface. The benefit of the pacing is that OSPF update and
retransmission packets are sent more efficiently. There are no configuration tasks for this feature; it occurs
automatically.
You can display specific statistics such as the contents of IP routing tables, caches, and databases.
Information provided can be used to determine resource utilization and solve network problems. You can
also display information about node reachability and discover the routing path that your device packets are
taking through the network
Enabling OSPF
How to Configure OSPF
Enabling OSPF
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. network ip-address wildcard-mask area area-id
5. end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router> router ospf 109
Example:
Router> network 192.168.129.16 0.0.0.3 area 20
Step 5 end
Example:
Router(config-router)# end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router> router ospf 109
Example:
Router(config-if)# ip ospf cost 65
Configuring OSPF
How to Configure OSPF
Command or Action
Step 5 ip ospf retransmit-interval seconds
Purpose
Specifies the number of seconds between link-state
advertisement (LSA) retransmissions for adjacencies
belonging to an OSPF interface.
Example:
Router(config-if)# ip ospf retransmit-interval 1
Sets the estimated number of seconds required to send a linkstate update packet on an OSPF interface.
Example:
Router(config-if)# ip ospf transmit delay 1
Example:
Router(config-if)# ip ospf priority 1
Specifies the length of time between the hello packets that the
Cisco IOS software sends on an OSPF interface.
Example:
Router(config-if)# ip ospf hello-interval 1
Example:
Router(config-if)# ip ospf dead-interval 1
Example:
Router(config-if)# ip ospf authentication-key 1
Example:
Router(config-if)# ip ospf message-digest-key 1
md5 23456789
Command or Action
Purpose
Example:
Router(config-if)# ip ospf authentication
message-digest
Step 13 end
Example:
Router(config-router)# end
DETAILED STEPS
Command or Action
Purpose
Step 2 exit
neighbors will assume the cost of the interface, based on the ip ospf cost
interface configuration command.
SUMMARY STEPS
1. ip ospf network point-to-multipoint non-broadcast
2. exit
3. router ospf process-id
4. neighbor ip-address [cost number]
DETAILED STEPS
Command or Action
Purpose
Step 1 ip ospf network point-to-multipoint Configures an interface as point-to-multipoint for nonbroadcast media.
non-broadcast
Step 2 exit
neighbors will assume the cost of the interface, based on the ip ospf cost
interface configuration command.
Purpose
Enables authentication for an OSPF area.
Configuring OSPF
Configuring OSPF Area Parameters
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. area area-id authentication
5. area area-id stub [ no summary ]
6. area area-id stub default-cost cost
7. end
DETAILED STEPS
Command or Action
Purpose
Step 1 enable
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 10
Example:
Router(config-router)# area 10.0.0.0 authentication
Example:
Router(config-router)# area 10.0.0.0 stub no-summary
Command or Action
Purpose
Example:
Router(config-router)# area 10.0.0.0 default-cost 1
Step 7 end
Example:
Router(config-router)# end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Configuring OSPF
Configuring an NSSA ABR as a Forced NSSA LSA Translator
Command or Action
Step 2 configure terminal
Purpose
Enters global configuration mode.
Example:
Router# configure terminal
Example:
Step 4 redistribute protocol [process-id] {level-1 | level-1-2 | Redistributes routes from one routing domain into another
level-2} [autonomous-system-number] [metric {metric- routing domain.
value | transparent}] [metric-type type-value] [match
The example causes RIP subnets to be redistributed into
{internal | external 1 | external 2}] [tag tag-value]
the OSPF domain.
[route-map map-tag] [subnets] [nssa-only]
Example:
Router(config-router)# redistribute rip subnets
Example:
Defines the interfaces on which OSPF runs and defines the area
ID for those interfaces.
Step 6 area area-id nssa [no-redistribution] [defaultinformation-originate [metric] [metric-type]] [nosummary] [nssa-only]
Example:
Router(config-router)# area 1 nssa
Step 7 end
Example:
Router(config-router)# end
Configuring OSPF
Configuring an NSSA ABR as a Forced NSSA LSA Translator
Note
In Cisco IOS Release 15.1(2)S and later releases, the output of the show ip ospf command shows whether
the NSSA ABR is configured as a forced translator, and whether the router is running as RFC 3101 or RFC
1587 compatible.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. area area-id nssa translate type7 always
5. end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1
replaces RFC 1587, and you can use the always keyword in the
area nssa translate command to configure an NSSA ABR
router as a forced NSSA LSA translator. This command will
work if RFC 3101 is disabled and RFC 1587 is being used.
Example:
Router(config-router)# area 10 nssa
translate type7 always
Step 5 end
Example:
Router(config-router)# end
Configuring OSPF
Disabling RFC 3101 Compatibility and Enabling RFC 1587 Compatibility
In Cisco IOS Release 15.1(2)S and later releases, the output of the show ip ospf command will indicate if
the NSSA ABR is configured as RFC 3101 or RFC 1587 compatible.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. compatible rfc1587
5. end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# compatible rfc1587
Command or Action
Purpose
Step 5 end
Example:
Router(config-router)# end
Prerequisites, page 20
Prerequisites
Evaluate the following considerations before you implement this feature:
You can set a Type 7 default route that can be used to reach external destinations. When configured,
the router generates a Type 7 default into the NSSA or the NSSA ABR.
Every router within the same area must agree that the area is NSSA; otherwise, the routers will not be
able to communicate.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Command or Action
Purpose
Example:
Router# configure terminal
Example:
Router> router ospf 109
Example:
Router(config-router)# area 10 nssa no-redistribution
Example:
Router(config-router)# summary-address 10.1.0.0
255.255.0.0 not-advertise
Step 6 end
Example:
Router(config-router)# end
Purpose
Specifies an address range for which a single route
will be advertised.
Configuring Route Summarization Between OSPF Areas Configuring Route Summarization Between
OSPF Areas Configuring Route Summarization Between OSPF Areas, page 22
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Forces the ASBR to generate a default route into
the OSPF routing domain.
Note The always keyword includes the following
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Configures DNS name lookup.
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
DETAILED STEPS
Purpose
Command or Action
Step 1 interface loopback 0
Creates a loopback interface, which places the router in interface configuration mode.
Purpose
Differentiates high -bandwidth links.
ref-bw
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Command
distance ospf
external} dist
{intra-area |
inter-area
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Step 1
Example:
Purpose
Example:
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Configures route calculation timers.
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
DETAILED STEPS
Command or Action
Purpose
Step 1
Step 2
Step 3
ip ospf demand-circuit
Note
You can prevent an interface from accepting demand-circuit requests from other routers to by specifying
the ignore keyword in the ip ospf demand-circuit command.
Prerequisites, page 28
Prerequisites
Evaluate the following considerations before implementing the On-Demand Circuits feature:
Because LSAs that include topology changes are flooded over an on-demand circuit, we recommend
that you put demand circuits within OSPF stub areas or within NSSAs to isolate the demand circuits
from as many topology changes as possible.
Every router within a stub area or NSSA must have this feature loaded in order to take advantage of
the on-demand circuit functionality. If this feature is deployed within a regular area, all other regular
areas must also support this feature before the demand circuit functionality can take effect because
Type 5 external LSAs are flooded throughout all areas.
Hub-and-spoke network topologies that have a point-to-multipoint (P2MP) OSPF interface type on a
hub might not revert to nondemand circuit mode when needed. You must simultaneously reconfigure
OSPF on all interfaces on the P2MPsegment when reverting them from demand circuit mode to
nondemand circuit mode.
Do not implement this feature on a broadcast-based network topology because the overhead protocols
(such as hello and LSA packets) cannot be successfully suppressed, which means the link will remain
up.
Configuring the router for an OSPF on-demand circuit with an asynchronous interface is not a
supported configuration. The supported configuration is to use dialer interfaces on both ends of the
circuit. For more information, refer to Why OSPF Demand Circuit Keeps Bringing Up the Link .
Purpose
log-adjacency-changes [detail]
Note
SUMMARY STEPS
1.
Configuring OSPF
Changing the LSA Group Pacing Interval
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Changes the group pacing of LSAs.
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Step 1
Example:
Example:
Purpose
Purpose
On point-to-multipoint networks, to block flooding of OSPF LSAs, use the following command in router
configuration mode:
Command
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
ip ospf flood-reduction
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Note
SUMMARY STEPS
1.
DETAILED STEPS
Command or Action
Purpose
Step 1
Example:
Example:
Purpose
Configuring OSPF
Displaying OSPF Update Packet Pacing
Command
Purpose
Displays lists of information related
to the OSPF database.
[area-id]]
[area-id]]
[Router#
[area-id]]
Configuring OSPF
Monitoring and Maintaining OSPF
Command
Purpose
Purpose
[neighbor-id]]}
Restrictions
Configuration Examples for OSPF
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Example:
Router> enable
Step 2
show ipospf[process-id]
Enables OSPF routing, which places the router in router configuration mode.
Example:
Router> show ip ospf 1
Restrictions
On systems with a large number of interfaces, it may be possible to configure OSPF such that the number
of links advertised in the router LSA causes the link state update packet to exceed the size of a "huge"
Cisco IOS buffer. To resolve this problem, reduce the number of OSPF links or increase the huge buffer
size by entering the buffers huge size size command.
A link state update packet containing a router LSA typically has a fixed overhead of 196 bytes, and an
additional 12 bytes are required for each link description. With a huge buffer size of 18024 bytes there can
be a maximum of 1485 link descriptions.
Because the maximum size of an IP packet is 65,535 bytes, there is still an upper bound on the number of
links possible on a router.
Router 1 Configuration
hostname Router 1
!
interface serial 1
ip address 10.0.0.2 255.0.0.0
ip ospf network point-to-multipoint
encapsulation frame-relay
frame-relay map ip 10.0.0.1 201 broadcast
frame-relay map ip 10.0.0.3 202 broadcast
frame-relay map ip 10.0.0.4 203 broadcast
!
router ospf 1
network 10.0.0.0 0.0.0.255 area 0
Router 2 Configuration
hostname Router 2
!
interface serial 0
ip address 10.0.0.1 255.0.0.0
ip ospf network point-to-multipoint
encapsulation frame-relay
frame-relay map ip 10.0.0.2 101 broadcast
frame-relay map ip 10.0.0.4 102 broadcast
!
router ospf 1
network 10.0.0.0 0.0.0.255 area 0
Router 3 Configuration
hostname Router 3
!
interface serial 3
ip address 10.0.0.4 255.0.0.0
ip ospf network point-to-multipoint
encapsulation frame-relay
clock rate 1000000
Router 4 Configuration
hostname Router 4
!
interface serial 2
ip address 10.0.0.3 255.0.0.0
ip ospf network point-to-multipoint
encapsulation frame-relay
clock rate 2000000
frame-relay map ip 10.0.0.2 301 broadcast
!
router ospf 1
network 10.0.0.0 0.0.0.255 area 0
neighbor
State
1
FULL/
1
FULL/
1
FULL/
Dead Time
Address
00:01:50
10.0.1.5
00:01:47
10.0.1.4
00:01:45
10.0.1.3
Interface
Serial0
Serial0
Serial0
The following example is the configuration for the router on the other side:
interface Serial9/2
ip address 10.0.1.3 255.255.255.0
encapsulation frame-relay
ip ospf network point-to-multipoint non-broadcast
no ip mroute-cache
no keepalive
no fair-queue
frame-relay local-dlci 301
frame-relay map ip 10.0.1.1 300
no shutdown
!
router ospf 1
network 10.0.1.0 0.0.0.255 area 0
neighbor
State
1
FULL/
1
FULL/
1
FULL/
Dead Time
Address
00:01:52
10.0.1.5
00:01:52
10.0.1.4
00:01:52
10.0.1.3
Interface
Serial0
Serial0
Serial0
Router 2
hostname Router2
!
!
interface Loopback1
ip address 10.1.0.2 255.255.255.255
!
interface Serial10/0
description Router1 interface s11/0
no ip address
shutdown
serial restart-delay 0
no cdp enable
!
interface Serial11/0
description Router1 interface s10/0
ip address 192.168.10.2 255.255.255.0
ip ospf 1 area 1
serial restart-delay 0
no cdp enable
!
interface Serial14/0
description Router3 interface s13/0
ip address 192.168.14.2 255.255.255.0
ip ospf 1 area 1
serial restart-delay 0
Configuring OSPF
Configuration Examples for OSPF
no cdp enable
!
router ospf 1
area 1 nssa
!
end
Router 3
hostname Router3
!
interface Loopback1
ip address 10.1.0.3 255.255.255.255
!
interface Ethernet3/0
ip address 192.168.3.3 255.255.255.0
no cdp enable
!
interface Serial13/0
description Router2 interface s14/0
ip address 192.168.14.3 255.255.255.0
ip ospf 1 area 1
serial restart-delay 0
no cdp enable
!
router ospf 1
log-adjacency-changes
area 1 nssa
redistribute rip subnets
!
router rip
version 2
redistribute ospf 1 metric 15
network 192.168.3.0
end
Router 4
hostname Router4
!
interface Loopback1
ip address 10.1.0.4 255.255.255.255
!
interface Ethernet3/0
ip address 192.168.3.4 255.255.255.0
no cdp enable
!
interface Ethernet4/1
ip address 192.168.41.4 255.255.255.0
!
router rip
version 2
network 192.168.3.0
network 192.168.41.0
!
end
Router 5
hostname Router5
!
interface Loopback1
ip address 10.1.0.5 255.255.255.255
!
interface Ethernet0/0
ip address 192.168.0.10 255.255.255.0
ip ospf 1 area 0
no cdp enable
!
Configuring OSPF
Configuration Examples for OSPF
interface Ethernet1/1
ip address 192.168.11.10 255.255.255.0
ip ospf 1 area 0
!
router ospf 1
!
end
The figure below shows the OSPF stub network with NSSA Area 1. The redistributed routes that Router 4
is propagating from the two RIP networks will be translated into Type 7 LSAs by NSSA ASBR Router 3.
Router 2, which is configured to be the NSSA ABR, will translate the Type 7 LSAs back to Type 5 so that
they can be flooded through the rest of the OSPF stub network within OSPF Area 0.
Figure 5
When the show ip ospf command is entered on Router 2, the output confirms that OSFP Area 1 is an
NSSA area:
Router2# show ip ospf
Routing Process "ospf 1" with ID 10.1.0.2
Start time: 00:00:01.392, Time elapsed: 12:03:09.480
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 0 normal 0 stub 1 nssa
Number of areas transit capable is 0
Configuring OSPF
Configuration Examples for OSPF
1)
Checksum
0x00CBCB
0x009371
0x004149
Link count
2
4
2
Checksum
0x00A605
0x009503
Checksum Tag
0x00484F 0
0x00A4CC 0
Entering the show ip ospf database data command displays additional information about redistribution
between Type 5 and Type 7 LSAs for routes that have been injected into the NSSA area and then flooded
through the OSPF network.
Router2# show ip ospf database data
OSPF Router with ID (10.1.0.2) (Process ID 1)
Area 1 database summary
LSA Type
Count
Delete
Maxage
Router
3
0
0
Network
0
0
0
Summary Net
2
0
0
Summary ASBR 0
0
0
Type-7 Ext
2
0
0
Prefixes redistributed in Type-7 0
Opaque Link
0
0
0
Opaque Area
0
0
0
Subtotal
7
0
0
Process 1 database summary
LSA Type
Count
Delete
Maxage
Router
3
0
0
Network
0
0
0
Summary Net
2
0
0
Summary ASBR 0
0
0
Type-7 Ext
2
0
0
Opaque Link
0
0
0
Opaque Area
0
0
0
Type-5 Ext
0
0
0
Prefixes redistributed in Type-5 0
Opaque AS
0
0
0
Total
7
0
0
Entering the show ip ospf database nssa command also displays detailed information for Type 7 to Type 5
translations:
Router2# show ip ospf database nssa
OSPF Router with ID (10.1.0.2) (Process ID 1)
Type-7 AS External Link States (Area 1)
Routing Bit Set on this LSA
LS age: 1903
Options: (No TOS-capability, Type 7/5 translation, DC)
Configuring OSPF
Configuration Examples for OSPF
Router 3
Entering the show ip ospf command on Router 3 displays the information to confirm that Router 3 is acting
as an ASBR and that OSPF Area 1 has been configured to be an NSSA area:
Router3# show ip ospf
Routing Process "ospf 1" with ID 10.1.0.3
Start time: 00:00:01.392, Time elapsed: 12:02:34.572
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
!It is an autonomous system boundary router
Redistributing External Routes from,
rip, includes subnets in redistribution
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 0 normal 0 stub 1 nssa
Number of areas transit capable is 0
External flood list length 0
Area 1
Number of interfaces in this area is 1
! It is a NSSA area
Area has no authentication
SPF algorithm last executed 11:38:13.368 ago
SPF algorithm executed 3 times
Area ranges are
Number of LSA 7. Checksum Sum 0x050CF7
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 0
Number of indication LSA 0
Example: OSPF NSSA Area with RFC 3101 Disabled and RFC 1587 Active
Configuration Examples for OSPF
Example: OSPF NSSA Area with RFC 3101 Disabled and RFC 1587 Active
In the following example, the output for the show ip ospf and show ip ospf database nssa commands is
for an OSPF NSSA area where RFC 3101 is disabled, RFC 1587 is active, and an NSSA ABR router is
configured as a forced NSSA LSA translator. As described in the "Configuring OSPF NSSA", if RFC 3101
is disabled, the forced NSSA LSA translator remains inactive. The command output demonstrates this.
Router# show ip ospf
Routing Process "ospf 1" with ID 10.0.2.1
Start time: 00:00:25.512, Time elapsed: 00:01:02.200
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Supports NSSA (compatible with RFC 1587)
Event-log enabled, Maximum number of events: 1000, Mode: cyclic
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 0 normal 0 stub 1 nssa
Number of areas transit capable is 0
External flood list length 0
IETF NSF helper support enabled
Cisco NSF helper support enabled
Reference bandwidth unit is 100 mbps
Area 1
Number of interfaces in this area is 1
It is a NSSA area
Configured to translate Type-7 LSAs, inactive (RFC3101 support
disabled)
Area has no authentication
SPF algorithm last executed 00:00:07.160 ago
SPF algorithm executed 3 times
Area ranges are
Number of LSA 3. Checksum Sum 0x0245F0
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
The "Supports NSSA (compatible with RFC 1587)" line in the output indicates that RFC 1587 is active or
that the OSPF NSSA area is RFC 1587 compatible.
The "Configured to translate Type-7 LSAs, inactive (RFC3101 support disabled)" line indicates that the
OSPF NSSA area has an ABR router configured to act as a forced translator of Type 7 LSAs, but it is
inactive because RFC 3101 is disabled.
Router2# show ip ospf database nssa
Router Link States (Area 1)
LS age: 28
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 10.0.2.1
The "Unconditional NSSA translator" line indicates that the status of the NSSA ASBR router is as a forced
NSSA LSA translator.
Example: Basic OSPF Configuration for Internal Router ABR and ASBRs
Configuring OSPF
Example: Complex Internal Router with ABR and ASBR
The following example illustrates the assignment of four area IDs to four IP address ranges. In the example,
OSPF routing process 109 is initialized, and four OSPF areas are defined: 10.9.50.0, 2, 3, and 0. Areas
10.9.50.0, 2, and 3 mask specific address ranges, and area 0 enables OSPF for all other networks.
router ospf 109
network 192.168.10.0 0.0.0.255 area 10.9.50.0
network 192.168.20.0 0.0.255.255 area 2
network 192.168.30.0 0.0.0.255 area 3
network 192.168.40.0 255.255.255.255 area 0
!
! Interface Ethernet0 is in area 10.9.50.0:
interface ethernet 0
ip address 192.168.10.5 255.255.255.0
!
! Interface Ethernet1 is in area 2:
interface ethernet 1
ip address 192.168.20.5 255.255.255.0
!
! Interface Ethernet2 is in area 2:
interface ethernet 2
ip address 192.168.20.7 255.255.255.0
!
! Interface Ethernet3 is in area 3:
interface ethernet 3
ip address 192.169.30.5 255.255.255.0
!
! Interface Ethernet4 is in area 0:
interface ethernet 4
ip address 192.168.40.1 255.255.255.0
!
! Interface Ethernet5 is in area 0:
interface ethernet 5
ip address 192.168.40.12 255.255.0.0
Each network area router configuration command is evaluated sequentially, so the order of these
commands in the configuration is important. The Cisco IOS software sequentially evaluates the address/
wildcard-mask pair for each interface. See the network area command in the Cisco IOS IP Routing: OSPF
Command Reference for more information.
Consider the first network area command. Area ID 10.9.50.0 is configured for the interface on which
subnet 192.168.10.0 is located. Assume that a match is determined for Ethernet interface 0. Ethernet
interface 0 is attached to area 10.9.50.0 only.
The second network area command is evaluated next. For area 2, the same process is then applied to all
interfaces (except Ethernet interface 0). Assume that a match is determined for interface Ethernet 1. OSPF
is then enabled for that interface and Ethernet interface 1 is attached to area 2.
This process of attaching interfaces to OSPF areas continues for all network area commands. Note that the
last network area command in this example is a special case. With this command, all available interfaces
(not explicitly attached to another area) are attached to area 0.
Configuring OSPF
Example: Complex Internal Router with ABR and ASBR
The following example outlines a configuration for several routers within a single OSPF autonomous
system. The figure below provides a general network map that illustrates this example configuration.
Figure 6
Configuring OSPF
Example: Complex Internal Router with ABR and ASBR
Note
You do not need to include definitions of all areas in an OSPF autonomous system in the configuration of
all routers in the autonomous system. Only the directly connected areas must be defined. In the example
that follows, routes in area 0 are learned by the routers in area 1 (Router A and Router B) when the ABR
(Router C) injects summary LSAs into area 1.
The OSPF domain in BGP autonomous system 109 is connected to the outside world via the BGP link to
the external peer at IP address 10.0.0.6. Example configurations follow.
Following is the sample configuration for the general network map shown in the figure above.
Router A Configuration--Internal Router
interface ethernet 1
ip address 192.168.1.1 255.255.255.0
router ospf 1
network 192.168.0.0 0.0.255.255 area 1
Router C Configuration--ABR
interface ethernet 3
ip address 192.168.1.3 255.255.255.0
interface serial 0
ip address 192.168.2.3 255.255.255.0
router ospf 999
network 192.168.1.0 0.0.0.255 area 1
network 192.168.2.0 0.0.0.255 area 0
Router E Configuration--ASBR
interface ethernet 5
ip address 10.0.0.5 255.0.0.0
interface serial 2
ip address 172.16.1.5 255.255.255.0
router ospf 65001
network 10.0.0.0 0.255.255.255 area 0
redistribute bgp 109 metric 1 metric-type 1
router bgp 109
network 192.168.0.0
network 10.0.0.0
neighbor 172.16.1.6 remote-as 110
Configuring OSPF
Example: Complex OSPF Configuration for ABR
The specific tasks outlined in this configuration are detailed briefly in the following descriptions. The
figure below illustrates the network address ranges and area assignments for the interfaces.
Figure 7
Redistribute IGRP and RIP into OSPF with various options set (including including metric-type,
metric, tag, and subnet).
Redistribute IGRP and OSPF into RIP.
interface ethernet 1
ip address 172.19.251.202 255.255.255.0
ip ospf authentication-key ijklmnop
ip ospf cost 20
ip ospf retransmit-interval 10
ip ospf transmit-delay 2
ip ospf priority 4
!
interface ethernet 2
ip address 172.19.254.2 255.255.255.0
ip ospf authentication-key abcdefgh
ip ospf cost 10
!
interface ethernet 3
ip address 10.56.0.0 255.255.0.0
ip ospf authentication-key ijklmnop
ip ospf cost 20
ip ospf dead-interval 80
The following example redistributes RIP routes with a hop count equal to 1 into OSPF. These routes will be
redistributed into OSPF as external LSAs with a metric of 5, a metric type of Type 1, and a tag equal to 1.
router ospf 109
redistribute rip route-map rip-to-ospf
!
route-map rip-to-ospf permit
match metric 1
set metric 5
Configuring OSPF
Example: Complex OSPF Configuration for ABR
The following example redistributes OSPF learned routes with tag 7 as a RIP metric of 15:
router rip
redistribute ospf 109 route-map 5
!
route-map 5 permit
match tag 7
set metric 15
The following example redistributes OSPF intra-area and interarea routes with next hop routers on serial
interface 0 into BGP with an INTER_AS metric of 5:
router bgp 109
redistribute ospf 109 route-map 10
!
route-map 10 permit
match route-type internal
match interface serial 0
set metric 5
The following example redistributes two types of routes into the integrated IS-IS routing table (supporting
both IP and CLNS). The first type is OSPF external IP routes with tag 5; these routes are inserted into
Level 2 IS-IS link state packets (LSPs) with a metric of 5. The second type is ISO-IGRP derived CLNS
prefix routes that match CLNS access list 2000; these routes will be redistributed into IS-IS as Level 2
LSPs with a metric of 30.
router isis
redistribute ospf 109 route-map 2
redistribute iso-igrp nsfnet route-map 3
!
route-map 2 permit
match route-type external
match tag 5
set metric 5
set level level-2
!
route-map 3 permit
match address 2000
set metric 30
With the following configuration, OSPF external routes with tags 1, 2, 3, and 5 are redistributed into RIP
with metrics of 1, 1, 5, and 5, respectively. The OSPF routes with a tag of 4 are not redistributed.
router rip
redistribute ospf 109 route-map 1
!
route-map 1 permit
match tag 1 2
set metric 1
!
route-map 1 permit
match tag 3
set metric 5
!
route-map 1 deny
match tag 4
!
route map 1 permit
match tag 5
set metric 5
In the following configuration, a RIP learned route for network 160.89.0.0 and an ISO-IGRP learned route
with prefix 49.0001.0002 will be redistributed into an IS-IS Level 2 LSP with a metric of 5:
router isis
The following configuration example illustrates how a route map is referenced by the default-information
router configuration command. This type of reference is called conditional default origination. OSPF will
originate the default route (network 0.0.0.0) with a Type 2 metric of 5 if 140.222.0.0 is in the routing table.
Note
Only routes external to the OSPF process can be used for tracking, such as non-OSPF routes or OSPF
routes from a separate OSPF process.
route-map ospf-default permit
match ip address 1
set metric 5
set metric-type type-2
!
access-list 1 permit 172.16.0.0 0.0.255.255
!
router ospf 109
default-information originate route-map ospf-default
Router A Configuration
router ospf 1
redistribute ospf 2 subnet
distance ospf external 200
!
router ospf 2
redistribute ospf 1 subnet
distance ospf external 200
Router B Configuration
router ospf 1
redistribute ospf 2 subnet
distance ospf external 200
!
router ospf 2
redistribute ospf 1 subnet
distance ospf external 200
Router A Configuration
username RouterB password 7 060C1A2F47
isdn switch-type basic-5ess
ip routing
!
interface TokenRing0
ip address 192.168.50.5 255.255.255.0
no shutdown
!
interface BRI0
no cdp enable
description connected PBX 1485
ip address 192.168.45.30 255.255.255.0
encapsulation ppp
ip ospf demand-circuit
dialer map ip 140.10.10.6 name RouterB broadcast 61484
dialer-group 1
ppp authentication chap
no shutdown
!
router ospf 100
network 192.168.45.0 0.0.0.255 area 0
network 192.168.45.50 0.0.0.255 area 0
!
dialer-list 1 protocol ip permit
Router B Configuration
username RouterA password 7 04511E0804
isdn switch-type basic-5ess
ip routing
!
interface Ethernet0
ip address 192.168.50.16 255.255.255.0
no shutdown
!
interface BRI0
no cdp enable
description connected PBX 1484
ip address 192.168.45.17 255.255.255.0
encapsulation ppp
dialer map ip 192.168.45.19 name RouterA broadcast 61485
dialer-group 1
ppp authentication chap
no shutdown
!
router ospf 100
network 192.168.45.0 0.0.0.255 area 0
network 192.168.45.50 0.0.0.255 area 0
!
dialer-list 1 protocol ip permit
The following example prevents flooding of OSPF LSAs to point-to-multipoint networks to the neighbor at
IP address 10.10.10.45:
router ospf 109
neighbor 10.10.10.45 database-filter all out
Additional References
Configuring OSPF
Additional References
Related Documents
Related Topic
Document Title
OSPF commands
Title
--
MIBs
MIB
MIBs Link
RFCs
RFC
Title
RFC 1253
RFC 1587
RFC 1793
RFC 2328
RFC 3101
Configuring OSPF
Feature Information for Configuring OSPF
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Releases
Feature Information
OSPF
11.2.1
12.1(2)T
Configuring OSPF
Feature Name
Releases
Feature Information
11.2.1
12.0(1)T
15.1(2)S
15.0(1)SY
15.2(2)T
15.0(1)SY
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
12.0(15)S
12.2(4)T
12.2(4)T3
12.2(8)T
12.2(11)T
12.2(28)SB
Release
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Benefits
The OSPF ABR Type 3 LSA Filtering feature gives the administrator improved control of route
distribution between OSPF areas.
Restrictions
Only type 3 LSAs that originate from an ABR are filtered.
Configuration Tasks
See the following sections for configuration tasks for the OSPF ABR Type 3 LSA Filtering feature. Each
task in the list is identified as either required or optional:
DETAILED STEPS
Command or Action
Purpose
Step 2 Router(config-router)# area area-id filter-list prefix prefix- Configures the router to filter interarea routes into the
specified area.
list-name in
Step 3 Router(config-router)# exit
Step 4 Router(config)# ip prefix-list list-name [seq seq-value] deny Creates a prefix list with the name specified for the listname argument.
| permit network/len [ge ge-value] [le le-value]
SUMMARY STEPS
1. Router(config)# router ospf process-id
2. Router(config-router)# area area-id filter-list prefix prefix-list-name out
3. Router(config-router)# exit
4. Router(config)# ip prefix-list list-name [seq seq-value] deny | permit network/len [ge ge-value] [le levalue]
DETAILED STEPS
Command or Action
Purpose
Step 2 Router(config-router)# area area-id filter-list prefix prefix- Configures the router to filter interarea routes out of the
specified area.
list-name out
Step 3 Router(config-router)# exit
Creates a prefix list with the name specified for the listname argument.
show ip prefix-list
Purpose
Displays information about a prefix list or prefix
list entries.
Configuration Examples
The following configuration example output shows interarea filtering that is applied to both incoming and
outgoing routes:
Router(config)# router ospf 1
log-adjacency-changes
area 1 filter-list prefix AREA_1_OUT out
area 3 filter-list prefix AREA_3_IN in
network 10.0.0.0 0.255.255.255 area 3
network 172.16.1.0 0.0.0.255 area 0
network 192.168.0.0 0.255.255.255 area 1
!
ip prefix-list AREA_1_OUT seq 10 permit 10.25.0.0/8 ge 16
ip prefix-list AREA_1_OUT seq 20 permit 172.20.20.0/24
!
ip prefix-list AREA_3_IN seq 10 permit 172.31.0.0/16
!
Additional References
The following sections provide references related to OSPF ABR Type 3 LSA Filtering.
Related Documents
Related Topic
Document Title
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
None
RFCs
RFC
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
configuration options that allow you to configure a router that is running the Open Shortest Path First
(OSPF) protocol to advertise a maximum or infinite metric to all neighbors.
When any of these three configuration options are enabled on a router, the router will originate link-state
advertisements (LSAs) with a maximum metric (LSInfinity: 0xFFFF) through all nonstub links. The
advertisement of a maximum metric causes other routers to assign a cost to the new router that is higher
than the cost of using an alternate path. Because of the high cost assigned to paths that pass through the
new router, other routers will not use a path through the new router as a transit path to forward traffic that is
destined for other networks, which allows switching and routing functions to be up and running and routing
tables to converge before transit traffic is routed through this router.
Note
Directly connected links in a stub network are not affected by the configuration of a maximum or infinite
metric because the cost of a stub link is always set to the output interface cost.
You can configure a timer to advertise a maximum metric when the router is started or reloaded. When
this option is configured, the router will advertise a maximum metric, which forces neighbor routers to
select alternate paths until the timer expires. When the timer expires, the router will advertise accurate
(normal) metrics, and other routers will send traffic to this router depending on the cost. The
configurable range of the timer is from 5 to 86,400 seconds.
You can configure a router to advertise a maximum metric at startup until BGP routing tables
converge or until the default timer expires (600 seconds). Once BGP routing tables converge or the
default timer expires, the router will advertise accurate (normal) metrics and other routers will send
traffic to this router, depending on the cost.
Note
You should not save the running configuration of a router when it is configured for a graceful shutdown
because the router will continue to advertise a maximum metric after it is reloaded.
Supported Platforms
The OSPF Stub Router Advertisement feature is supported by the following platforms in Cisco IOS
Release 12.2(14)S that support OSPF:
DETAILED STEPS
Command or Action
Purpose
Places the router in router configuration mode and enables an OSPF routing
process.
DETAILED STEPS
Command or Action
Purpose
Step 1 Router(config)# router ospf process-id Places the router in router configuration mode and enables an OSPF routing
process.
Step 2 Router(config-router)# max-metric
router-lsa on-startup wait-for-bgp
Configures OSPF to advertise a maximum metric until BGP routing tables have
converged or until the default timer has expired. The wait-for-bgp keyword
must follow the on-startup keyword to be configured. The default timer value is
600 seconds.
DETAILED STEPS
Command or Action
Purpose
Step 1 Router(config)# router ospf process- Places the router in router configuration mode and enables an OSPF routing
process.
id
Step 2 Router(config-router)# max-metric
router-lsa
Configures OSPF to advertise a maximum metric until the router is shut down.
Exits configuration mode and places the router in privileged EXEC mode.
Displays general information about OSPF routing processes. The show ip ospf
command is entered in order to verify that the max-metric router-lsa command
has been enabled before the router is shut down or reloaded.
Note
You should not save the running configuration of a router when it is configured for a graceful shutdown
because the router will continue to advertise a maximum metric after it is reloaded.
The output of the show ip ospfcommand will display the condition, state, and remaining time delay of the
advertisement of a maximum metric, depending on which options were configured with the max-metric
router-lsa command.
The following sample output is similar to the output that will be displayed when the on-startupkeyword
and announce-time argument are configured with the max-metric router-lsa command:
Router# show ip ospf
Routing Process "ospf 1998" with ID 10.18.134.155
Supports only single TOS(TOS0) routes
Supports opaque LSA
It is an area border and autonomous system boundary router
Redistributing External Routes from,
static, includes subnets in redistribution
Originating router-LSAs with maximum metric, Time remaining: 00:01:18
Condition: on startup for 300 seconds, State: active
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
Number of external LSA 7. Checksum Sum 0x47261
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 2. 1 normal 0 stub 1 nssa
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm executed 3 times
Area ranges are
Number of LSA 8. Checksum Sum 0x474AE
Number of opaque link LSA 0. Checksum Sum 0x0
The following sample output is similar to the output that will be displayed when the on-startupand waitfor-bgp keywords are configured with the max-metric router-lsa command:
Router# show ip ospf
Routing Process "ospf 1998" with ID 10.18.134.155
Supports only single TOS(TOS0) routes
Supports opaque LSA
It is an area border and autonomous system boundary router
Redistributing External Routes from,
static, includes subnets in redistribution
Originating router-LSAs with maximum metric, Time remaining: 00:01:18
Condition: on startup while BGP is converging, State: active
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
Number of external LSA 7. Checksum Sum 0x47261
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 2. 1 normal 0 stub 1 nssa
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm executed 3 times
Area ranges are
Number of LSA 8. Checksum Sum 0x474AE
Number of opaque link LSA 0. Checksum Sum 0x0
The following sample output is similar to the output that will be displayed when the max-metric routerlsa command is configured without any keywords or arguments:
Router# show ip ospf
Routing Process "ospf 1998" with ID 10.18.134.155
Supports only single TOS(TOS0) routes
Supports opaque LSA
It is an area border and autonomous system boundary router
Redistributing External Routes from,
The output of the show ip ospf databasecommand will display information about OSPF LSAs and indicate
if the router is announcing maximum cost links. The following sample output is similar to the output that
will be displayed when any form of the max-metric router-lsa command is configured:
Router# show ip ospf database
Exception Flag: Announcing maximum link costs
LS age: 68
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 172.18.134.155
Advertising Router: 172.18.134.155
LS Seq Number: 80000002
Checksum: 0x175D
Length: 60
Area Border Router
AS Boundary Router
Number of Links: 3
Link connected to: a Transit Network
(Link ID) Designated Router address: 192.168.1.11
(Link Data) Router Interface address: 192.168.1.14
Number of TOS metrics: 0
TOS 0 Metrics: 65535 (metric used for local calculation: 10)
Link connected to: a Transit Network
(Link ID) Designated Router address: 10.1.145.11
(Link Data) Router Interface address: 10.1.145.14
Number of TOS metrics: 0
TOS 0 Metrics: 65535 (metric used for local calculation: 10)
Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.11.12.0
(Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
TOS 0 Metrics: 1
show ip ospf
Purpose
Displays general information about OSPF routing
processes and provides information about the
configuration settings and status of the OSPF Stub
Router Advertisement feature.
Command
Router#
Purpose
Displays information about router LSAs, and
indicates if a router is announcing maximum link
costs.
Additional References
Related Documents
Related Topic
Document Title
Configuring OSPF
"Configuring OSPF"
Related Topic
Document Title
OSPF commands
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
RFCs
RFC
Title
RFC 3137
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 2
Feature Name
Releases
Feature Information
The OSPF Stub Router
Advertisement feature allows you
to bring a new router into a
network without immediately
routing traffic through the new
router and allows you to
gracefully shut down or reload a
router without dropping packets
that are destined for other
networks.
The following commands are
introduced or modified in the
feature documented in this
module:
max-metric router-lsa
show ip ospf
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Note
The default settings for OSPF packet pacing timers are suitable for the majority of OSPF deployments. You
should change the default timers only as a last resort.
Supported Platforms
The OSPF Update Packet-Pacing Configurable Timers feature is supported by the following platforms in
Cisco IOS Release 12.2(14)S that support OSPF:
DETAILED STEPS
Command or Action
Step 1 Router(config)# router ospf process-id
Purpose
Places the router in router configuration mode and enables an OSPF
routing process.
Command or Action
Step 2 Router(config-router)# timers pacing flood
milliseconds
Purpose
Configures a flood packet pacing timer delay (in milliseconds).
SUMMARY STEPS
1. Router(config)# router ospf process-id
2. Router(config-router)# timers pacing lsa-group seconds
DETAILED STEPS
Command or Action
Purpose
SUMMARY STEPS
1. Router(config)# router ospf process-id
2. Router(config-router)# timers pacing lsa-group seconds
DETAILED STEPS
Command or Action
Purpose
Troubleshooting Tips
If the number of OSPF packet retransmissions rapidly increases, increase the value of the packet pacing
timers. The number of OSPF packet retransmissions is displayed in the output of the show ip ospf
neighbor command.
show ip ospf
Purpose
Displays general information about OSPF routing
processes.
Command
Purpose
router#
Router#
Additional References
Related Documents
Related Topic
Document Title
Configuring OSPF
Configuring OSPF"
Related Topic
Document Title
OSPF commands
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
RFCs
RFC
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Releases
Feature Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.2(8)T
This module describes how to configure and use a sham-link to connect Virtual Private Network (VPN)
client sites that run the Open Shortest Path First (OSPF) protocol and share backdoor OSPF links in a
Multiprotocol Label Switching (MPLS) VPN configuration.
Feature Overview
When OSPF is used to connect PE and CE routers, all routing information learned from a VPN site is
placed in the VPN routing and forwarding (VRF) instance associated with the incoming interface. The PE
routers that attach to the VPN use the Border Gateway Protocol (BGP) to distribute VPN routes to each
other. A CE router can then learn the routes to other sites in the VPN by peering with its attached PE router.
The MPLS VPN superbackbone provides an additional level of routing hierarchy to interconnect the VPN
sites running OSPF.
When OSPF routes are propagated over the MPLS VPN backbone, additional information about the prefix
in the form of BGP extended communities (route type, domain ID extended communities) is appended to
the BGP update. This community information is used by the receiving PE router to decide the type of linkstate advertisement (LSA) to be generated when the BGP route is redistributed to the OSPF PE-CE process.
In this way, internal OSPF routes that belong to the same VPN and are advertised over the VPN backbone
are seen as interarea routes on the remote sites.
For basic information about how to configure an MPLS VPN, refer to the "MPLS Virtual Private Networks
Configuration" module.
sites belong to the same OSPF area, the path over a backdoor link will always be selected because OSPF
prefers intraarea paths to interarea paths. (PE routers advertise OSPF routes learned over the VPN
backbone as interarea paths.) For this reason, OSPF backdoor links between VPN sites must be taken into
account so that routing is performed based on policy.
For example, the figure above shows three client sites, each with backdoor links. Because each site runs
OSPF within the same Area 1 configuration, all routing between the three sites follows the intraarea path
across the backdoor links, rather than over the MPLS VPN backbone.
The following example shows BGP routing table entries for the prefix 10.3.1.7/32 in the PE-1 router in the
figure above. This prefix is the loopback interface of the Winchester CE router. As shown in bold in this
example, the loopback interface is learned via BGP from PE-2 and PE-3. It is also generated through
redistribution into BGP on PE-1.
PE-1# show ip bgp vpnv4 all 10.3.1.7
BGP routing table entry for 100:251:10.3.1.7/32, version 58
Paths: (3 available, best #2)
Advertised to non peer-group peers:
10.3.1.2 10.3.1.5
Local
10.3.1.5 (metric 30) from 10.3.1.5 (10.3.1.5)
Origin incomplete, metric 22, localpref 100, valid, internal
Extended Community: RT:1:793 OSPF DOMAIN ID:0.0.0.100 OSPF
RT:1:2:0 OSPF 2
Local
10.2.1.38 from 0.0.0.0 (10.3.1.6)
Origin incomplete, metric 86, localpref 100, weight 32768,
valid, sourced, best
Extended Community: RT:1:793 OSPF DOMAIN ID:0.0.0.100 OSPF
RT:1:2:0 OSPF 2
Local
10.3.1.2 (metric 30) from 10.3.1.2 (10.3.1.2)
Origin incomplete, metric 11, localpref 100, valid, internal
Extended Community: RT:1:793 OSPF DOMAIN ID:0.0.0.100 OSPF
RT:1:2:0 OSPF 2
Within BGP, the locally generated route (10.2.1.38) is considered to be the best route. However, as shown
in bold in the next example, the VRF routing table shows that the selected path is learned via OSPF with a
next hop of 10.2.1.38, which is the Vienna CE router.
PE-1# show ip route vrf ospf 10.3.1.7
Routing entry for 10.3.1.7/32
Known via "ospf 100", distance 110, metric 86, type intra area
Redistributing via bgp 215
Advertised by bgp 215
Last update from 10.2.1.38 on Serial0/0/0, 00:00:17 ago
Routing Descriptor Blocks:
* 10.2.1.38
, from 10.3.1.7, 00:00:17 ago, via Serial0/0/0
Route metric is 86, traffic share count is 1
The OSPF intra-area path is preferred over the interarea path (over the MPLS VPN backbone)
generated by the PE-1 router.
OSPF has a lower administrative distance (AD) than internal BGP (BGP running between routers in
the same autonomous system).
If the backdoor links between sites are used only for backup purposes and do not participate in the VPN
service, then the default route selection shown in the preceding example is not acceptable. To reestablish
the desired path selection over the MPLS VPN backbone, you must create an additional OSPF intra-area
(logical) link between ingress and egress VRFs on the relevant PE routers. This link is called a sham-link.
A sham-link is required between any two VPN sites that belong to the same OSPF area and share an OSPF
backdoor link. If no backdoor link exists between the sites, no sham-link is required.
The figure below shows a sample sham-link between PE-1 and PE-2. A cost is configured with each shamlink and is used to decide whether traffic will be sent over the backdoor path or the sham-link path. When a
sham-link is configured between PE routers, the PEs can populate the VRF routing table with the OSPF
routes learned over the sham-link.
Because the sham-link is seen as an intra-area link between PE routers, an OSPF adjacency is created and
database exchange (for the particular OSPF process) occurs across the link. The PE router can then flood
LSAs between sites from across the MPLS VPN backbone. As a result, the desired intra-area connectivity
is created.
The section, "Creating a Sham-Link, page 93", describes how to configure a sham-link between two PE
routers. For more information about how to configure OSPF, refer to the "Configuring OSPF" module.
The following example shows the forwarding that occurs between sites from the standpoint of how PE-1
views the 10.3.1.7/32 prefix, the loopback1 interface of the Winchester CE router in the figure above.
PE-1# show ip bgp vpnv4 all 10.3.1.7
BGP routing table entry for 100:251:10.3.1.7/32, version 124
Paths: (1 available, best #1)
Local
10.3.1.2 (metric 30) from 10.3.1.2
(10.3.1.2)
Origin incomplete, metric 11, localpref 100, valid, internal,
best
Extended Community: RT:1:793 OSPF DOMAIN ID:0.0.0.100 OSPF
RT:1:2:0 OSPF 2
The next example shows forwarding information in which the next hop for the route, 10.3.1.2, is the PE-3
router rather than the PE-2 router (which is the best path according to OSPF). The reason the OSPF route is
not redistributed to BGP on the PE is because the other end of the sham-link already redistributed the route
to BGP and there is no need for duplication. The OSPF sham-link is used only to influence intra-area path
selection. When sending traffic to a particular destination, the PE router uses the MP-BGP forwarding
information.
PE-1# show ip bgp vpnv4 all tag | begin 10.3.1.7
10.3.1.7/32
10.3.1.2
notag/38
PE-1# show tag-switching forwarding 10.3.1.2
Local Outgoing
Prefix
Bytes tag Outgoing
Next Hop
tag
tag or VC or Tunnel Id
switched
interface
31
42
10.3.1.2/32
0
PO3/0/0
point2point
PE-1# show ip cef vrf ospf 10.3.1.7
10.3.1.7/32, version 73, epoch 0, cached adjacency to POS3/0/0
0 packets, 0 bytes
tag information set
local tag: VPN-route-head
fast tag rewrite with PO3/0/0, point2point, tags imposed: {42 38
}
via 10.3.1.2
, 0 dependencies, recursive
next hop 10.1.1.17, POS3/0/0 via 10.3.1.2/32
valid cached adjacency
tag rewrite with PO3/0/0, point2point, tags imposed: {42 38}
If a prefix is learned across the sham-link and the path via the sham-link is selected as the best, the PE
router does not generate an MP-BGP update for the prefix. It is not possible to route traffic from one shamlink over another sham-link.
In the following example, PE-2 shows how an MP-BGP update for the prefix is not generated. Although
10.3.1.7/32 has been learned via OSPF across the sham-link as shown in bold, no local generation of a
route into BGP is performed. The only entry within the BGP table is the MP-BGP update received from
PE-3 (the egress PE router for the 10.3.1.7/32 prefix).
PE-2# show ip route vrf ospf 10.3.1.7
Routing entry for 10.3.1.7/32
Known via "ospf 100
", distance 110, metric 12, type intra area
Redistributing via bgp 215
Last update from 10.3.1.2 00:00:10 ago
Routing Descriptor Blocks:
* 10.3.1.2 (Default-IP-Routing-Table), from 10.3.1.7, 00:00:10 ago
Route metric is 12, traffic share count is 1
PE-2# show ip bgp vpnv4 all 10.3.1.7
BGP routing table entry for 100:251:10.3.1.7/32, version 166
Paths: (1 available, best #1)
Not advertised to any peer
Local
10.3.1.2 (metric 30) from 10.3.1.2 (10.3.1.2)
Origin incomplete, metric 11, localpref 100, valid, internal,
best
Extended Community: RT:1:793 OSPF DOMAIN ID:0.0.0.100 OSPF
RT:1:2:0 OSPF 2
Benefits
Supported Platforms
The PE router uses the information received from MP-BGP to set the ongoing label stack of incoming
packets, and to decide to which egress PE router to label switch the packets.
Benefits
Client Site Connection Across the MPLS VPN Backbone
A sham-link overcomes the OSPF default behavior for selecting an intra-area backdoor route between VPN
sites instead of an interarea (PE-to-PE) route. A sham-link ensures that OSPF client sites that share a
backdoor link can communicate over the MPLS VPN backbone and participate in VPN services.
Flexible Routing in an MPLS VPN Configuration
In an MPLS VPN configuration, the OSPF cost configured with a sham-link allows you to decide if OSPF
client site traffic will be routed over a backdoor link or through the VPN backbone.
Restrictions
When OSPF is used as a protocol between PE and CE routers, the OSPF metric is preserved when routes
are advertised over the VPN backbone. The metric is used on the remote PE routers to select the correct
route. For this reason, you should not modify the metric value when OSPF is redistributed to BGP, and
when BGP is redistributed to OSPF. If you modify the metric value, routing loops may occur.
MPLS
OSPF
BGP
Related Documents
Supported Platforms
Cisco 1600
Cisco 1600R
Cisco 1710
Cisco 1720
Cisco 1721
Cisco 1750
Cisco 1751
Cisco 2420
Cisco 2600
Cisco 2691
Cisco 3620
Cisco 3631
Cisco 3640
Cisco 3660
Cisco 3725
Cisco 3745
Cisco 7100
Cisco 7200
Cisco 7500
Cisco 7700
URM
Cisco uBR7200
Creating a Sham-Link
Prerequisites
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to
the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
Before you can configure a sham-link in an MPLS VPN, you must first enable OSPF as follows:
Configuration Tasks
See the following sections for configuration tasks for the sham-link feature. Each task in the list is
identified as either required or optional.
Creating a Sham-Link
Before you create a sham-link between PE routers in an MPLS VPN, you must:
Configure a separate /32 address on the remote PE so that OSPF packets can be sent over the VPN
backbone to the remote end of the sham-link. The /32 address must meet the following criteria:
Belong to a VRF.
Not be advertised by OSPF.
Be advertised by BGP.
SUMMARY STEPS
1. Router1# configure terminal
2. Router1(config)# interface loopback interface-number
3. Router1(config-if)# ip vrf forwarding vrf-name
4. Router1(config-if)# ip address ip-address mask
5. Router1(config)# end
6. Router2# configure terminal
7. Router2(config)# interface loopback interface-number
8. Router2(config-if)# ip vrf forwarding vrf-name
9. Router2(config-if)# ip address ip-address mask
10. Router1(config)# end
11. Router1(config)# router ospf process-id vrf vrf-name
12. Router1(config-if)# areaarea-id sham-linksource-address destination-address cost number
13. Router2(config)# router ospf process-id vrf vrf-name
14. Router2(config-if)# area area-id sham-link source-address destination-address cost number
DETAILED STEPS
Command or Action
Purpose
Step 3 Router1(config-if)# ip vrf forwarding vrf- Associates the loopback interface with a VRF. Removes the IP address.
name
Step 4 Router1(config-if)# ip address ip-address
mask
Step 8 Router2(config-if)# ip vrf forwarding vrf- Associates the second loopback interface with a VRF. Removes the IP
address.
name
Step 9 Router2(config-if)# ip address ip-address
mask
Configures the specified OSPF process with the VRF associated with the
sham-link interface on PE-1 and enters interface configuration mode.
Command or Action
Purpose
Configures the specified OSPF process with the VRF associated with the
sham-link interface on PE-2 and enters interface configuration mode.
Command
Router#
Router#
Configuration Examples
The following example shows how to configure a sham-link between two PE routers:
Router1(config)
# interface loopback 1
Router1(config-if)# ip vrf forwarding ospf
Router1(config-if)# ip address 10.2.1.1 255.255.255.255
!
Router2(config)# interface loopback 1
Router2(config-if)# ip vrf forwarding ospf
Router2(config-if)# ip address 10.2.1.2 255.255.255.255
!
Router1(config)# router ospf 100 vrf ospf
Router1(config-if)# area 1 sham-link 10.2.1.1 10.2.1.2 cost 40
!
Router2(config)# router ospf 100 vrf ospf
Router2(config-if)# area 1 sham-link 10.2.1.2 10.2.1.1 cost 40
Glossary
BGP --Border Gateway Protocol. Interdomain routing protocol that exchanges reachability information
with other BGP systems. It is defined in RFC 1163.
CE router --customer edge router. A router that is part of a customer network and that interfaces to a
provider edge (PE) router. CE routers are not aware of associated VPNs.
CEF -- Cisco Express Forwarding. An advanced Layer 3 IP switching technology. CEF optimizes network
performance and scalability for networks with large and dynamic traffic patterns.
OSPF --Open Shortest Path First protocol.
IGP --Interior Gateway Protocol. An Internet protocol used to exchange routing information within an
autonomous system. Examples of common IGPs include IGRP, OSPF, and RIP.
LSA --link-state advertisement. A broadcast packet used by link-state protocols. The LSA contains
information about neighbors and path costs and is used by the receiving router to maintain a routing table.
MPLS --Multiprotocol Label Switching. Emerging industry standard upon which tag switching is based.
PE router --provider edge router. A router that is part of a service provider network connected to a
customer edge (CE) router. All VPN processing occurs in the PE router.
SPF --shortest path first calculation.
VPN --Virtual Private Network. A secure IP-based network that shares resources on one or more physical
networks. A VPN contains geographically dispersed sites that can communicate securely over a shared
backbone.
VRF --VPN routing and forwarding instance. A VRF consists of an IP routing table, a derived forwarding
table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that
determine what goes into the forwarding table. In general, a VRF includes the routing information that
defines a customer VPN site that is attached to a PE router.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.2(11)T
This feature module describes the change in how the Open Shortest Path First (OSPF) protocol handles
retransmissions.
Feature Overview
Cisco IOS Release 12.2(4)T added a limit to the number of retransmissions of database exchange and
update packets for both demand and non-demand circuits. The retransmission of these packets stops once
this retry limit is reached, thus preventing unnecessary use of the link in continual retransmission of the
packets if, for some reason, a neighbor is not responding during adjacency forming.
The limit for both demand circuit and non-demand circuit retransmissions is 24.
The limit-retransmissions command allows you to either remove (disable) the limit or change the maximum
number of retransmissions to be a number from 1 to 255.
Benefits
Supported Platforms
Benefits
The limit-retransmissions command provides for backward compatibility for previous or other releases of
Cisco IOS or other routers that do not have this feature.
Restrictions
The limit to the number of retransmissions does not apply for update packets on nonbroadcast multiaccess
(NBMA) point-to-multipoint direct circuits. In this situation, the dead timer is used to end communication
with non-responding neighbors and thus stop the retransmissions.
Supported Platforms
The limit-retransmissions command is supported for the following platforms in Cisco IOS Release
12.2(11)T:
Cisco AS5300
Cisco AS5400
Cisco AS5800
Cisco 1400 series
Cisco 1600 series
Cisco 1600R series
Cisco 1710
Cisco 1720
Cisco 1721
Cisco 1750
Cisco 1751
Cisco 2500 series
Cisco 2600 series
Cisco 3620
Cisco 3631
Cisco 3640
Cisco 3725
Cisco 3745
Cisco 3660
Cisco IGX 8400 Series URM
Cisco MC3810
Cisco 7100 series
Cisco 7200 series
Cisco 7500 series
Cisco uBR7200 series
Configuration Tasks
DETAILED STEPS
Command or Action
Purpose
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
SUMMARY STEPS
1. enable
2. show ip ospf [process-id]
3. configure terminal
4. router ospf process-id [vrf vpn-name]
5. capability vrf-lite
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables higher privilege levels, such as privileged EXEC mode.
Example:
Router> enable
Displays the status of the router. If the display indicates that the router is
connected to the VPN backbone, you can use the capability vrf-lite
command to decouple the PE router from the VPN backbone.
Example:
Router> show ip ospf 1
Example:
Router# configure terminal
Example:
Command or Action
Purpose
Example:
Router(config)# capability vrf-lite
When the OSPF VRF process is configured with the capability vrf-lite command under the router ospf
command, the "Connected to MPLS VPN Superbackbone" line will not be present in the display.
interface Serial3/0
ip vrf forwarding grc
ip address 192.168.2.1 255.255.255.252
...
!
router ospf 9000 vrf grc
log-adjacency-changes
capability vrf-lite
redistribute rip metric 1 subnets
network 192.168.1.0 0.0.0.255 area 0
!
router rip
address-family ipv4 vrf grc
redistribute ospf 9000 vrf grc
network network 192.168.2.0
no auto-summary
end
Router# show ip route vrf grc
Routing Table: grc
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
O IA 192.168.192.0/24 [110/138] via 192.168.1.13, 00:06:08, Serial2/0
[110/138] via 192.168.1.9, 00:06:08, Serial3/0
O IA 192.168.242.0/24 [110/74] via 192.168.1.13, 00:06:08, Serial2/0
O IA 192.168.193.0/24 [110/148] via 192.168.1.13, 00:06:08, Serial2/0
[110/148] via 192.168.1.9, 00:06:08, Serial3/0
O IA 192.168.128.0/24 [110/74] via 192.168.1.9, 00:06:08, Serial3/0
O IA 192.168.129.0/24 [110/84] via 192.168.1.9, 00:06:08, Serial3/0
O IA 192.168.130.0/24 [110/84] via 192.168.1.9, 00:06:08, Serial3/0
172.16.0.0/24 is subnetted, 2 subnets
O E2
172.16.9.0 [110/5] via 192.168.1.13, 00:06:08, Serial2/0
O E2
172.16.10.0 [110/5] via 192.168.1.13, 00:06:08, Serial2/0
O IA 192.168.131.0/24 [110/94] via 192.168.1.9, 00:06:20, Serial3/0
192.168.1.0/30 is subnetted, 4 subnets
C
192.168.1.8 is directly connected, Serial3/0
C
192.168.1.12 is directly connected, Serial2/0
O
192.168.1.0 [110/128] via 192.168.1.9, 00:06:20, Serial3/0
O
192.168.1.4 [110/128] via 192.168.1.13, 00:06:20, Serial2/0
Additional References
Related Documents
Related Topic
Document Title
Configuring OSPF
Configuring OSPF
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
RFCs
RFCs
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Releases
Feature Information
capability vrf-lite
Glossary
CE Router --Customer Edge router, an edge router in the C network, defined as a C router which attaches
directly to a P router.
C Network --Customer (enterprise or service provider) network.
C Router --Customer router, a router in the C network.
LSA --link-state advertisement . Broadcast packet used by link-state protocols that contains information
about neighbors and path costs. LSAs are used by the receiving routers to maintain their routing tables.
PE Router --Provider Edge router, an edge router in the P network, defined as a P router which attaches
directly to a C router.
P Network --MPLS-capable service provider core network. P routers perform MPLS.
P Router --Provider router, a router in the P network.
SPF --shortest path first. A routing algorithm that iterates on length of path to determine a shortest-path
spanning tree.
VPN --Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by
encrypting all traffic from one network to another.
VRF --VPN Routing and Forwarding.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Benefits of OSPF Forwarding Address Suppression in Translated Type-5 LSAs, page 112
When to Suppress OSPF Forwarding Address in Translated Type-5 LSAs, page 112
This problem is solved by suppressing the forwarding address on the ABR so that the forwarding address is
set to 0.0.0.0 in the Type-5 LSAs that were translated from Type-7 LSAs. A forwarding address set to
0.0.0.0 indicates that packets for the external destination should be forwarded to the advertising OSPF
router, in this case, the translating NSSA ABR.
Before configuring this feature, consider the following caution.
Caution
Configuring this feature causes the router to be noncompliant with RFC 1587. Also, suboptimal routing
might result because there might be better paths to reach the destinations forwarding address. This feature
should not be configured without careful consideration and not until the network topology is understood.
Configuring this feature causes the router to be noncompliant with RFC 1587. Also, suboptimal routing
might result because there might be better paths to reach the destinations forwarding address. This feature
should not be configured without careful consideration and not until the network topology is understood.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. area area-id nssa translate type7 suppress-fa
5. end
DETAILED STEPS
Command or Action
Step 1 enable
Example:
Purpose
Enables higher privilege levels, such as privileged EXEC
mode.
Router> enable
Command or Action
Purpose
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# area 10 nssa translate
type7 suppress-fa
Step 5 end
Example:
Router(config-router)# end
Example Suppressing OSPF Forwarding Address in Translated Type-5 LSAs, page 114
Additional References
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
RFCs
RFCs
Title
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Feature Information for OSPF Forwarding Address Suppression in Translated Type-5 LSAs
Releases
Feature Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
link-state advertisement (LSA) flooding. In the route map, the user can match on any attribute of the OSPF
route. That is, the route map could be based on the following match options:
match interface
match ip address
match ip next-hop
match ip route-source
match metric
match route-type
match tag
This feature can be useful during redistribution if the user tags prefixes when they get redistributed on
Autonomous System Boundary Routers (ASBRs) and later uses the tag to filter the prefixes from being
installed in the routing table on other routers.
Filtering Based on Route Tag
Users can assign tags to external routes when they are redistributed to OSPF. Then the user can deny or
permit those routes in the OSPF domain by identifying that tag in the route-map and distribute-list in
commands.
Filtering Based on Route Type
In OSPF, the external routes could be Type 1 or Type 2. Users can create route maps to match either Type
1 or Type 2 and then use the distribute-list in command to filter certain prefixes. Also, route maps can
identify internal routes (interarea and intra-area) and then those routes can be filtered.
Filtering Based on Route Source
When a match is done on the route source, the route source represents the OSPF Router ID of the LSA
originator of the LSA in which the prefix is advertised.
Filtering Based on Interface
When a match is done on the interface, the interface represents the outgoing interface for the route that
OSPF is trying to install in the routing table.
Filtering Based on Next Hop
When a match is done on the next hop, the next hop represents the next hop for the route that OSPF is
trying to install in the routing table.
Note
The distribute-list in command can be configured to prevent routes from being installed in the global
Routing Information Base (RIB). Prior to the implementation of OSPF local RIB (for feature information
on OSPF local RIB, see OSPFv2 Local RIB), OSPF would attempt to install a less preferred route (e.g. an
inter-area route when the intra-area path is filtered). With OSPF local RIB, only the best route is considered
(because this is the only route the local RIB maintains). There is no concept of a "second-best" OSPF route.
For more information on the routing algorithm used by Cisco OSPF routers, please refer to RFC 2328.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Step 3 route-map map-tag [permit | deny] [sequence-number] Defines a route map to control filtering.
Example:
Router(config)# route-map tag-filter deny 10
Command or Action
Purpose
Example:
Optional.
Step 6 exit
Example:
Router(config-router)# exit
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# distribute-list routemap tag-filter in
Step 9 end
Example:
Router(config-router)# end
Additional References
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Feature Information for OSPF Inbound Filtering Using Route Maps with a Distribute List
Releases
Feature Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.2(14)S
12.0(23)S
12.2(15)T
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn . You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
The figure below shows the intervals at which the SPF calculations occur so long as at least one topology
change event is received in a given wait interval.
Figure 11
Notice that the wait interval between SPF calculations doubles when at least one topology change event is
received during the previous wait interval. Once the maximum wait time is reached, the wait interval
remains the same until the topology stabilizes and no event is received in that interval.
If the first topology change event is received after the current wait interval, the SPF calculation is delayed
by the amount of time specified as the start interval. The subsequent wait intervals continue to follow the
dynamic pattern.
If the first topology change event occurs after the maximum wait interval begins, the SPF calculation is
again scheduled at the start interval and subsequent wait intervals are reset according the parameters
specified in the timers throttle spfcommand. Notice in the figure below that a topology change event was
received after the start of the maximum wait time interval and that the SPF intervals have been reset.
Figure 12
DETAILED STEPS
Command or Action
Step 1 enable
Example:
Purpose
Enables higher privilege levels, such as privileged
EXEC mode.
Enter your password if prompted.
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# interface ethernet 1/1/1
Command or Action
Step 4 ip address ip-address mask [secondary]
Purpose
Sets a primary or secondary IP address for an
interface.
Example:
Router(config-if)# ip address 192.168.0.2 255.255.255.0
Step 5 exit
Example:
router# exit
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# network 192.168.0.0 0.0.255.255
area 0
Example:
Router(config-router)# timers throttle spf 10 4800 90000
Step 9 end
Example:
Router(config-router)# end
The table below describes the show ip ospf display fields and their descriptions.
Table 7
Field
Description
Routing process "ospf 201" with ID 192.42.110.200 Process ID and OSPF router ID.
Supports ...
It is ...
SPF calculations
Number of areas
Field
Description
Additional References
For additional information related to OSPF, refer to the following references:
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
No new or modified RFCs are supported by this
feature, and support for existing RFCs has not been
modified by this feature.
Title
MIBs
MIBs
MIBs Link
RFCs
RFCs
Title
Link
http://www.cisco.com/cisco/web/support/
index.html
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables higher privilege levels, such as privileged EXEC mode.
Enter your password if prompted.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# interface ethernet 0
Sets the interval during which at least one hello packet must be received,
or else the neighbor is considered down.
Example:
Router(config-if)# ip ospf deadinterval minimal hello-multiplier 5
Step 5 end
Example:
Use this command when you are ready to exit configuration mode
and save the configuration to the running configuration file.
Router(config-if)# end
Command or Action
Purpose
The relevant fields that verify OSPF fast hello packets are indicated
in the sample output following this table.
Example:
Router# show ip ospf interface
ethernet 1/3
Examples
The following example output verifies that OSPF Support for Fast Hello Packets is configured. In the line
that begins with "Timer intervals configured," the hello interval is 200 milliseconds, the dead interval is 1
second, and the next hello packet is due in 76 milliseconds.
Router# show ip ospf interface ethernet 1/3
Ethernet1/3 is up, line protocol is up
Internet Address 172.16.1.2/24, Area 0
Process ID 1, Router ID 172.17.0.2, Network Type BROADCAST, Cost:1
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 172.17.0.2, Interface address 172.16.1.2
Backup Designated router (ID) 172.16.0.1, Interface address 172.16.1.1
Timer intervals configured, Hello 200 msec, Dead 1, Wait 1, Retransmit 5
Hello due in 76 msec
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 3
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 172.16.0.1 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
Additional References
The following sections provide references related to OSPF Support for Fast Hello Packets.
Related Documents
Related Topic
Document Title
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 8
Feature Name
Releases
Feature Information
12.0(23)S 12.2(18)S
12.2(27)SBC 12.2(15)T
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
OSPF uses Dijkstras SPF algorithm to compute the shortest path tree (SPT). During the computation of the
SPT, the shortest path to each node is discovered. The topology tree is used to populate the routing table
with routes to IP networks. When changes to a Type-1 or Type-2 link-state advertisement (LSA) occur in
an area, the entire SPT is recomputed. In many cases, the entire SPT need not be recomputed because most
of the tree remains unchanged. Incremental SPF allows the system to recompute only the affected part of
the tree. Recomputing only a portion of the tree rather than the entire tree results in faster OSPF
convergence and saves CPU resources. Note that if the change to a Type-1 or Type-2 LSA occurs in the
calculating router itself, then the full SPT is performed.
Incremental SPF is scheduled in the same way as the full SPF. Routers enabled with incremental SPF and
routers not enabled with incremental SPF can function in the same internetwork.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id
4. ispf
5. end
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Example:
Router> enable
Step 2
configure terminal
Example:
Router# configure terminal
Step 3
Command or Action
Purpose
Example:
Router(config)# router ospf 1
Step 4
ispf
Example:
Router(config-router)# ispf
Step 5
end
Example:
Router(config-router)# end
Additional References
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Table 9
Feature Name
Releases
Feature Information
ispf
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
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
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Command or Action
Step 3 router ospf process-id
Purpose
Configures an OSPF routing process.
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# redistribute eigrp 10
Example:
Router(config-router)# redistribute maximumprefix 100 80
Example:
Router(config-router)# end
Example:
Router# show ip ospf 1
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# redistribute eigrp 10
Command or Action
Purpose
Example:
Router(config-router)# redistribute maximumprefix 1000 80 warning-only
Step 6 end
Example:
Router(config-router)# end
Additional References
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Releases
Feature Information
redistribute maximumprefix
show ip ospf
show ip ospf database
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.0(25)S
12.3(2)T
12.2(18)S
12.2(27)SBC
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn . You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1
Example:
Router(config-router)# timers throttle lsa all
100 10000 45000
start-intervalis 0 milliseconds
hold-intervalis 5000 milliseconds
max-intervalis 5000 milliseconds
Command or Action
Purpose
Example:
Router(config-router)# timers lsa arrival 2000
Step 6 end
Example:
Router(config-router)# end
Example:
Router# show ip ospf timers rate-limit
Example:
LSAID: 10.1.1.1
Type: 1
Due in: 00:00:00.028
Example:
LSAID: 192.168.4.1
Type: 3
Adv Rtr:
172.17.2.2 Due in: 00:00:00.028
Command or Action
Step 8 show ip ospf
Purpose
(Optional) Displays information about OSPF.
Example:
Router#
show ip ospf
Example:
Routing Process "ospf 4" with ID 10.10.24.4
Example:
Supports only single TOS(TOS0) routes
Example:
Supports opaque LSA
Example:
Supports Link-local Signaling (LLS)
Example:
Initial SPF schedule delay 5000 msecs
Example:
Minimum hold time between two consecutive SPFs
10000 msecs
Example:
Maximum wait time between two consecutive SPFs
10000 msecs
Example:
Incremental-SPF disabled
Command or Action
Example:
Example:
Example:
Minimum LSA arrival 1000 msecs
Example:
LSA group pacing timer 240 secs
Example:
Interface flood pacing timer 33 msecs
Example:
Retransmission pacing timer 66 msecs
Example:
Number of external LSA 0. Checksum Sum 0x0
Example:
Number of opaque AS LSA 0. Checksum Sum 0x0
Purpose
Command or Action
Purpose
Example:
Number of DCbitless external and opaque AS LSA 0
Example:
Number of DoNotAge external and opaque AS LSA 0
Example:
Number of areas in this router is 1. 1 normal 0
stub 0 nssa
Example:
External flood list length 0
Example:
Area 24
Example:
Number of interfaces in this area is 2
Example:
Area has no authentication
Example:
SPF algorithm last executed 04:28:18.396
ago
Example:
SPF algorithm executed 8 times
Example:
Area ranges are
Command or Action
Purpose
Example:
Number of LSA 4. Checksum Sum 0x23EB9
Example:
Number of opaque link LSA 0. Checksum
Sum 0x0
Example:
Number of DCbitless LSA 0
Example:
Number of indication LSA 0
Example:
Number of DoNotAge LSA 0
Example:
Flood list length 0
Additional References
The following sections provide references related to OSPF LSA throttling.
Related Documents
Related Topic
Document Title
OSPF commands
Standards
Standards
Title
No new or modified standards are supported by this -feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.3(4)T
12.0(27)S
12.2(25)S
12.2(18)SXE
12.2(27)SBC
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn . You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
Configuring and Verifying Unlimited Software VRFs per Provider Edge Router, page 165
Configuring and Verifying Unlimited Software VRFs per Provider Edge Router
How to Configure OSPF Support for Unlimited Software VRFs per PE Router
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 1 vrf crf-1
Step 4 end
Note You now can configure as many OSPF VRF processes as needed.
Example:
Router(config-router)# end
Example:
Router# show ip ospf 1
Example Configuring OSPF Support for Unlimited Software VRFs per PE Router
Configuration Examples for OSPF Support for Unlimited Software VRFs per PE Router
Example Configuring OSPF Support for Unlimited Software VRFs per PE Router, page 166
Example Verifying OSPF Support for Unlimited Software VRFs per PE Router, page 166
Example Verifying OSPF Support for Unlimited Software VRFs per PE Router
This example illustrates the output display from the show ip ospf command to verify that the OSPF VRF
process 12 has been created for the VRF named first. The output that relates to the VRF first appears in
bold.
Router# show ip ospf 12
main ID type 0x0005, value 0.0.0.100
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Connected to MPLS VPN Superbackbone, VRF first
It is an area border router
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Number of areas transit capable is 0
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm last executed 00:00:15.204 ago
SPF algorithm executed 2 times
Area ranges are
Number of LSA 1. Checksum Sum 0xD9F3
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Additional References
The following sections provide references related to the OSPF Support for Unlimited Software VRFs per
Provider Edge Router feature.
Related Documents
Related Topic
Document Title
Configuring OSPF
Standards
Standards
Title
None
--
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Glossary
multiprotocol BGP --Border Gateway Protocol (BGP) can be used as an interdomain routing protocol in
networks that use Connectionless Network Service (CLNS) as the network-layer protocol.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Disabling OSPF Area Transit Capability on an Area Border Router, page 170
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id [vrf vpn-name]
4. no capability transit
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 100
Example:
Router(config-router)# no capability transit
Additional References
Related Documents
Related Topic
Document Title
Configuring OSPF
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
None
RFCs
RFC
Title
RFC 2328
OSPF Version 2
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Table 11
Feature Name
Releases
Feature Information
capability transit
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
with RFC 2328 can prevent problems with the forming of Open Shortest Path First (OSPF) neighbors in the
network.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# interface Ethernet 1/0
Example:
Command or Action
Purpose
Example:
Router(config-if)# ip address 10.2.145.20 255.255.255.0
Example:
Router(config-if)# no ip directed-broadcast
Example:
Router(config-if)# ip ospf message-digest-key 100 md5
testing
Example:
Router(config-if)# ip ospf lls disable
What to Do Next
To verify that LLS has been enabled or disabled for a specific interface, use the show ip ospf interface
command. See the "Example: Configuring and Verifying the OSPF Per-Interface Link-Local Signaling
Feature" section for an example of the information displayed.
In the following example, the show ip ospf interface command has been entered to verify that LLS has
been enabled for Ethernet interface 1/0 and disabled for interface Ethernet 2/0:
Router# show ip ospf interface
Ethernet1/0 is up, line protocol is up
Internet Address 10.2.145.2/24, Area 1
Process ID 1, Router ID 10.22.222.2, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 10.2.2.3, Interface address 10.2.145.1
Backup Designated router (ID) 10.22.222.2, Interface address 10.2.145.2
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:00
!
Supports Link-local Signaling (LLS)
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 8
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.2.2.3 (Designated Router)
Suppress hello for 0 neighbor(s)
Ethernet2/0 is up, line protocol is up
Internet Address 10.1.145.2/16, Area 1
Process ID 1, Router ID 10.22.222.2, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 10.2.2.3, Interface address 10.1.145.1
Backup Designated router (ID) 10.22.222.2, Interface address 10.1.145.2
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:04
!
Does not support Link-local Signaling (LLS)
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 11
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 45.2.2.3 (Designated Router)
Suppress hello for 0 neighbor(s)
Ethernet3/0 is up, line protocol is up
Internet Address 10.3.145.2/24, Area 1
Process ID 1, Router ID 10.22.222.2, Network Type BROADCAST, Cost: 10
Additional References
The following sections provide references related to the OSPF Per-Interface Link-Local Signaling feature.
Related Documents
Related Topic
Document Title
Configuring OSPF
"Configuring OSPF"
"NSF-OSPF"
OSPF commands
Standards
Standards
Title
None
--
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
RFC 2328
OSPF Version 2
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Name
Releases
Feature Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Modification
12.0(27)S
12.3(7)T
12.2(25)S
12.2(18)SXE
12.2(27)SBC
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn . You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
If the warning-only keyword of the max-lsa command has been configured, the OSPF process will send
only a warning that the LSA maximum has been exceeded.
Limiting the Number of NonSelf-Generating LSAs for an OSPF Process, page 183
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Command or Action
Purpose
Example:
Router(config-router)# router-id 10.0.0.1
Example:
Router(config-router)# log-adjacency-changes
Example:
Router(config-router)# max-lsa 12000
Example:
Router(config-router)# network 209.165.201.1
255.255.255.255 area 0
Network
2
0
0
Summary Net
8
2
2
Summary ASBR 0
0
0
Type-7 Ext
0
0
0
Opaque Link
0
0
0
Opaque Area
0
0
0
Type-5 Ext
4
0
0
Prefixes redistributed in Type-5
Opaque AS
0
0
0
Non-self
16
Total
19
2
2
ospf 1
router-id 192.168.0.1
log-adjacency-changes
max-lsa 14000
area 33 nssa
network 192.168.0.1 0.0.0.0 area 1
network 192.168.5.1 0.0.0.0 area 1
network 192.168.2.1 0.0.0.0 area 0
In the following example, the show ip ospf command has been entered to confirm the configuration:
Router# show ip ospf 1
Routing Process "ospf 1" with ID 192.168.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Maximum number of non self-generated LSA allowed 14000
Threshold for warning message 75%
Ignore-time 5 minutes, reset-time 10 minutes
Ignore-count allowed 5, current ignore-count 0
It is an area border and autonomous system boundary router
In the following example, the following output appears when the show ip ospf command has been entered
during the time when the router is in the ignore state:
Router# show ip ospf 1
Routing Process "ospf 1" with ID 192.168.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Maximum number of non self-generated LSA allowed 14000
Threshold for warning message 75%
Ignore-time 5 minutes, reset-time 10 minutes
Ignore-count allowed 5, current ignore-count 1
Ignoring all neighbors due to max-lsa limit, time remaining: 00:04:52
It is an area border and autonomous system boundary router
The following output appears when the show ip ospf command has been entered after the router left the
ignore state:
Router# show ip ospf 1
Routing Process "ospf 1" with ID 192.168.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Maximum number of non self-generated LSA allowed 14000
Threshold for warning message 75%
Ignore-time 5 minutes, reset-time 10 minutes
Ignore-count allowed 5, current ignore-count 1 - time remaining: 00:09:51
It is an area border and autonomous system boundary router
The following output appears when the show ip ospf command has been entered for a router that is
permanently in the ignore state:
Router# show ip ospf 1
Routing Process "ospf 1" with ID 192.168.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Maximum number of non self-generated LSA allowed 14000
Threshold for warning message 75%
Ignore-time 5 minutes, reset-time 10 minutes
Ignore-count allowed 5, current ignore-count 6
Permanently ignoring all neighbors due to max-lsa limit
It is an area border and autonomous system boundary router
Additional References
The following sections provide references related to the OSPF Link-State Database Overload Protection
feature.
Related Documents
Related Topic
Configuring OSPF
Document Title
Standards
Standards
Title
None
--
MIBs
MIBs
MIBs Link
None
RFCs
RFCs
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Glossary
LSDB --link-state database.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
OSPF Hello input queue and OSPF process queue status and statistics.
Global OSPF traffic statistics.
Per OSPF interface traffic statistics.
Per OSPF process traffic statistics.
Finding Feature Information, page 189
Prerequisites for OSPF Enhanced Traffic Statistics, page 189
Information About OSPF Enhanced Traffic Statistics, page 190
How to Display and Clear OSPF Enhanced Traffic Statistics, page 190
Configuration Examples for OSPF Enhanced Traffic Commands, page 191
Additional References, page 195
Feature Information for OSPF Enhanced Traffic Statistics, page 196
OSPF process queue status and statistical information can help the network administrator determine if
an OSPF process can handle the amount of traffic sent to OSPF.
OSPF packet header errors and LSA errors statistics keep a record of different errors found in received
OSPF packets.
OSPF enhanced traffic control statistics also monitor the amount of traffic control exchanged between
OSPF processes--an important consideration in network environments with slow links and frequent
topology changes.
Displaying and Clearing OSPF Traffic Statistics for OSPFv2, page 190
Displaying and Clearing OSPF Traffic Statistics for OSPFv3, page 191
SUMMARY STEPS
1. enable
2. show ip ospf [process-id] traffic[interface-type interface-number]
3. clear ip ospf traffic
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# show ip ospf traffic statistics
Command or Action
Purpose
Example:
Router# clear ip ospf traffic
SUMMARY STEPS
1. enable
2. show ipv6 ospf [process-id] traffic[interface-type interface-number]
3. clear ipv6 ospf traffic
DETAILED STEPS
Purpose
Command or Action
Step 1 enable
Example:
Router> enable
Example:
Router# show ipv6 ospf traffic statistics
Example:
Router# clear ipv6 ospf traffic
Displaying and Clearing Enhanced Traffic Statistics for OSPFv2 Example, page 192
Displaying and Clearing Enhanced Traffic Statistics for OSPFv3 Example, page 194
TX Total
54
4392
OSPF header errors
Length 0, Checksum 0, Version 0, Bad Source 13,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, Hello 0,
MTU Mismatch 0, Nbr Ignored 0, LLS 0,
Authentication 0,
OSPF LSA errors
Type 0, Length 0, Data 0, Checksum 0,
The network administrator can issue the clear ip ospf traffic command to reset all counters and restart all
statistics collections:
Router# clear ip ospf traffic
TX DB des
9
312
TX LS req
1
52
TX LS upd
5
376
TX LS ack
3
148
TX Total
29
1308
OSPFv3 header errors
Length 0, Checksum 0, Version 0, No Virtual Link
Area Mismatch 0, Self Originated 0, Duplicate ID
Instance ID 0, Hello 0, MTU Mismatch 0,
Nbr Ignored 0, Authentication 0,
OSPFv3 LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Summary traffic statistics for process ID 6:
OSPFv3 packets received/sent
Type
Packets
Bytes
RX Invalid
0
0
RX Hello
11
436
RX DB des
7
316
RX LS req
2
104
RX LS upd
9
692
RX LS ack
4
264
RX Total
33
1812
TX Failed
0
0
TX Hello
19
724
TX DB des
12
456
TX LS req
2
104
TX LS upd
8
628
TX LS ack
6
296
TX Total
47
2208
OSPFv3 header errors
Length 0, Checksum 0, Version 0, No Virtual Link
Area Mismatch 0, Self Originated 0, Duplicate ID
Instance ID 0, Hello 0, MTU Mismatch 0,
Nbr Ignored 0, Authentication 0,
OSPFv3 LSA errors
Type 0, Length 0, Data 0, Checksum 0,
0,
0,
0,
0,
The network administrator can issue the clear ipv6 ospf traffic command to reset all counters and restart
all statistics collections:
Router# clear ipv6 ospf traffic
Additional References
The following sections provide references related to the OSPF Enhanced Traffic Statistics for OSPFv2 and
OSPFv3 feature.
Related Documents
Related Topic
Document Title
OSPF commands
OSPF configuration
Configuring OSPF
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
None
RFCs
RFC
Title
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Table 13
Feature Name
Feature Information for OSPF Enhanced Traffic Statistics for OSPFv2 and OSPFv3
Releases
Feature Information
This document describes the
detailed OSPF traffic statistics
that are provided when the user
enters the new and modified
commands show commands for
OSPFv2 and OSPFv3.
The following commands were
introduced or modified: clear
ipv6 ospf traffic, show ip ospf
traffic, show ipv6 ospf traffic.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Simple Network Management Protocol (SNMP) must be enabled on the router before notifications
(traps) can be configured or before SNMP GET operations can be performed.
OSPF MIB
This section describes the new MIB objects that are provided by RFC 1850 definitions. These OSPF MIB
definitions provide additional capacity that is not provided by the standard OSPF MIB that supported the
previous RFC 1253. To see a complete set of OSPF MIB objects, see the OSPF-MIB file.
The table below shows the new OSPF-MIB objects that are provided by RFC 1850 definitions. The objects
are listed in the order in which they appear within the OSPF-MIB file, per the tables that describe them.
Table 14
OSPF-MIB Table
OspfAreaEntry table
OspfAreaSummary
OspfAreaStatus
OSPF-MIB Table
OspfStubAreaEntry
OspfStubMetricType
OspfAreaRangeEntry
OspfAreaRangeEffect
OspfHostEntry
OspfHostAreaID
OspfIfEntry
OspfIfStatus
OspfIfMulticastForwarding
OspfIfDemand
OspfIfAuthType
OspfVirtIfEntry
OspfVirtIfAuthType
OspfNbrEntry
OspfNbmaNbrPermanence
OspfNbrHelloSuppressed
OspfVirtNbrEntry
OspfVirtNbrHelloSuppressed
OspfExtLsdbEntry
OspfExtLsdbType
OspfExtLsdbLsid
OspfExtLsdbRouterId
OspfExtLsdbSequence
OspfExtLsdbAge
OspfExtLsdbChecksum
OspfExtLsdbAdvertisement
OspfAreaAggregateEntry
OspfAreaAggregateAreaID
OspfAreaAggregateLsdbType
OspfAreaAggregateNet
OspfAreaAggregateMask
OspfAreaAggregateStatusospfSetTrap
OspfAreaAggregateEffect
OspfExtLsdbLimit
OspfMulticastExtensions
OspfExitOverflowInterval
OspfDemandExtensions
The ospfSetTrap control MIB object contains the OSPF trap MIB objects that enable and disable OSPF
traps in the IOS CLI. These OSPF trap MIB objects are provided by the RFC 1850 standard OSPF MIB. To
learn how to enable and disable the OSPF traps, see the How to Enable OSPF MIB Support of RFC 1850
and Latest Extensions, page 205.
The table below shows the OSPF trap MIB objects, listed in the order in which they appear within the
OSPF-TRAP-MIB file.
Table 15
ospfIfStateChange
ospfVirtIfStateChange
ospfNbrStateChange
ospfVirtNbrState
ospfIfConfigError
ospfVirtIfConfigError
ospfIfAuthFailure
ospfVirtIfAuthFailure
ospfIfRxBadPacket
ospfVirtIfRxBadPacket
ospfTxRetransmit
ospfVirtIfTxRetransmit
ospfOriginateLsa
ospfMaxAgeLsa
cospfRFC1583Compatibility
cospfOpaqueLsaSupport
cospfOpaqueASLsaCount
cospfOpaqueASLsaCksumSum
For each of the following table entries, the new Cisco-specific MIB objects that are provided as extensions
to support the RFC 1850 OSPF MIB definitions are listed. To see the complete set of objects for the Ciscospecific OSPF MIB, refer to the CISCO-OSPF-MIB file.
The table below shows the new CISCO-OSPF-MIB objects that are provided by RFC 1850 definitions. The
objects are listed in the order in which they appear within the CISCO-OSPF-MIB file, per the tables that
describe them.
Table 16
CISCO-OSPF-MIB Table
cospfAreaEntry
cospfOpaqueAreaLsaCount
cospfOpaqueAreaLsaCksumSum
cospfAreaNssaTranslatorRole
cospfAreaNssaTranslatorState
cospfAreaNssaTranslatorEvents
cospfLsdbEntry
cospfLsdbType
cospfLsdbSequence
cospfLsdbAge
cospfLsdbChecksum
cospfLsdbAdvertisement
cospfIfEntry
cospfIfLsaCount
cospfIfLsaCksumSum
cospfVirtIfEntry
cospfVirtIfLsaCount
cospfVirtIfLsaCksumSum
cospfLocalLsdbEntry
cospfLocalLsdbIpAddress
cospfLocalLsdbAddressLessIf
cospfLocalLsdbType
cospfLocalLsdbLsid
cospfLocalLsdbRouterId
cospfLocalLsdbSequence
cospfLocalLsdbAge
cospfLocalLsdbChecksum
cospfLocalLsdbAdvertisement
cospfVirtLocalLsdbEntry
cospfVirtLocalLsdbTransitArea
cospfVirtLocalLsdbNeighbor
cospfVirtLocalLsdbType
cospfVirtLocalLsdbLsid
cospfVirtLocalLsdbRouterId
cospfVirtLocalLsdbSequence
cospfVirtLocalLsdbAge
cospfVirtLocalLsdbChecksum
cospfVirtLocalLsdbAdvertisement
support RFC 1850. To see a complete set of Cisco OSPF Trap MIB objects, see the CISCO-OSPF-TRAPMIB file.
The table below shows the trap events described within the cospfSetTrap MIB object in the CISCO-OSPFTRAP-MIB:
Table 17
cospfIfConfigError
cospfVirtIfConfigError
cospfTxRetransmit
cospfVirtIfTxRetransmit
cospfOriginateLsa
cospfMaxAgeLsa
cospfNssaTranslatorStatusChange
For information about how to enable OSPF MIB traps, see the How to Enable OSPF MIB Support of RFC
1850 and Latest Extensions, page 205.
New CLI commands have been added to enable SNMP notifications for OSPF MIB support objects, Ciscospecific errors, retransmission and state-change traps. The SNMP notifications are provided for errors and
other significant event information for the OSPF network.
SUMMARY STEPS
1. enable
2. configure terminal
3. snmp-server community string1 ro
4. snmp-server community string2 rw
5. snmp-server host {hostname | ip-address} [vrf vrf-name] [traps | informs] [version {1 | 2c | 3 [auth |
noauth | priv]}] community-string [udp-port port] [notification-type]
6. snmp-server enable traps ospf
7. end
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Command or Action
Purpose
Enables read access to all objects in the MIB, but does not allow
access to the community strings.
Example:
Router(config)# snmp-server community
public ro
Enables read and write access to all objects in the MIB, but does
not allow access to the community strings.
Example:
Router(config)# snmp-server community
private rw
Step 5 snmp-server host {hostname | ip-address} [vrf vrfname] [traps | informs] [version {1 | 2c | 3 [auth |
noauth | priv]}] community-string [udp-port port]
[notification-type]
Example:
Router(config)# snmp-server host
172.20.2.162 version 2c public ospf
Example:
Router(config)# snmp-server enable traps
ospf
Step 7 end
Example:
Router(config)# end
What to Do Next
If you did not want to enable all OSPF traps, follow the steps in the following section to selectively enable
one or more type of OSPF trap:
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# snmp-server enable traps ospf
cisco-specific errors config-error
Entering the snmp-server enable traps ospf ciscospecific errors command with the optional virtconfig-error keyword enables only the SNMP
notifications for configuration mismatch errors on
virtual interfaces.
Command or Action
Step 4 snmp-server enable traps ospf cisco-specific retransmit
[packets] [virt-packets]
Purpose
Enables error traps for Cisco-specific OSPF errors that
involve re-sent packets.
Example:
Router(config)# snmp-server enable traps ospf
cisco-specific retransmit packets virt-packets
Entering the snmp-server enable traps ospf ciscospecific retransmit command with the optional
virt-packetskeyword enables only the SNMP
notifications for packets that are re-sent on virtual
interfaces.
Example:
Router(config)# snmp-server enable traps ospf
cisco-specific state-change
Example:
Router(config)# snmp-server enable traps ospf
cisco-specific lsa
Step 7 snmp-server enable traps ospf errors [authenticationfailure] [bad-packet] [config-error] [virt-authenticationfailure] [virt-config-error]
Example:
Example:
Router(config)# snmp-server enable traps ospf lsa
Example:
Router(config)# snmp-server enable traps ospf ratelimit 20 20
Command or Action
Purpose
Example:
Router(config)# snmp-server enable traps ospf
retransmit
Example:
Router(config)# snmp-server enable traps ospf
state-change
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Example Enabling and Verifying OSPF MIB Support Traps, page 210
The show running-config command is entered to verify that the traps are enabled:
Router# show running-config | include traps
snmp-server enable traps ospf
Where to Go Next
For more information about SNMP and SNMP operations, see the "Configuring SNMP Support" chapter of
the Cisco IOS Configuration Fundamentals and Network Management Configuration Guide, Release 12.2.
Additional References
The following sections provide references related to the OSPF MIB Support of RFC 1850 and Latest
Extensions feature.
Related Documents
Related Topic
Document Title
SNMP commands
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.
MIB
MIB
MIBs Link
To locate and download MIBs for selected
platforms, Cisco IOS releases, and feature sets, use
Cisco MIB Locator found at the following URL:
CISCO-OSPF-MIB
CISCO-OSPF-TRAP-MIB
OSPF-MIB
OSPF-TRAP-MIB
http://www.cisco.com/go/mibs
RFC
RFC
Title
RFC 1850
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Table 18
Feature Name
Feature Information for OSPF MIB Support of RFC 1850 and Latest Extensions
Releases
Feature Information
OSPF MIB Support of RFC 1850
and Latest Extensions feature
introduces the capability for
Simple Network Management
Protocol (SNMP) monitoring on
the Open Shortest Path First
(OSPF) routing protocol. Users
have an improved ability to
constantly monitor the changing
state of an OSPF network by use
of MIB objects to gather
information relating to protocol
parameters and trap notification
objects that can signal the
occurrence of significant network
events such as transition state
changes. The protocol
information collected by the
OSPF MIB objects and trap
objects can be used to derive
statistics that will help monitor
and improve overall network
performance.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Benefits of Choosing to Identify Interfaces by the SNMP MIB-II ifIndex Value, page 214
How OSPFv2 and OSPFv3 Use the SNMP MIB-II ifIndex Value, page 214
Using the SNMP MIB-II ifIndex (interface index) identification numbers to identify OSPF interfaces
makes it easier for network administrators to identify interfaces because the numbers will correspond
to the numbers that they will see reported by SNMP.
When examining link-state advertisements (LSAs), the value used in fields that have the interface ID
will be the same as the value that is reported by SNMP.
When looking at the output of the show ipv6 ospf interface command, the interface ID number will
have the same value that is reported by SNMP.
Using the SNMP MIB-II IfIndex is also suggested, but not required, by the OSPF RFC 2328 for
OSPFv2 and the RFC 2740 for OSPFv3.
How OSPFv2 and OSPFv3 Use the SNMP MIB-II ifIndex Value
The user chooses for OSPF interfaces to use the SNMP MIB-II ifIndex number by entering the interface-id
snmp-if-index command for a specific OSPF process. If an interface under the specific OSPF process does
not have an SNMP ifIndex number, OSPF will not be enabled on that interface.
For OSPFv2, the ifIndex number is used for the Link Data field in the Router LSA for unnumbered pointto-point interfaces and sham links. When the interface-id snmp-if-index command is entered, the affected
LSAs will immediately be reoriginated.
For OSPFv3, the ifIndex number is used for the interface ID in router LSAs, as the LSID in Network and
Link LSAs, and also as the interface ID in Hello packets. Intra-Area-Prefix LSAs that reference Network
LSAs have the network LSAs LSID in the Referenced LSID field, so they will also be updated when the
interface-id snmp-if-index command is entered. The old Network, Link and Intra-Area-Prefix LSAs that
are associated with a Network LSA will be flushed.
For both OSPFv2 and OSPFv3, adjacencies are not flapped, except for affected OSPFv3 demand circuits
(including virtual links) with full adjacencies.
For both OSPFv2 and OSPFv3, if an interface does not have an SNMP ifIndex number and an interface ID
is needed (for OSPFv2 this applies only to unnumbered interfaces and sham links), an error message will
be generated and the interface will be disabled. The interface will be reenabled if the no interface-id
snmp-if-index command is entered.
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
How to Configure the Interface ID in Data Fields
numbers or the interfaces will not be enabled for OSPF. Therefore, repeat the steps within this task for each
OSPF process for which you want the interfaces to use the SNMP MIB-II ifIndex numbers.
SUMMARY STEPS
1. enable
2. configure terminal
3. Do one of the following:
4. interface-id snmp-if-index
5. end
6. show snmp mib ifmib ifindex [interface-type] [slot /][port-adapter /][port]
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 4
Example:
Example:
Router(config)# ipv6 router ospf 4
Configuring the SNMP ifIndex Value for Interface ID for OSPFv2 Example
Configuration Examples for the Interface ID in Data Fields
Command or Action
Purpose
Example:
Router(config-router)# interface-id snmp-if-index
Step 5 end
Example:
Router(config-router)# end
Step 6 show snmp mib ifmib ifindex [interface-type] [slot /][portadapter /][port]
Example:
Router# show snmp mib ifmib ifindex Ethernet 0/1
Configuring the SNMP ifIndex Value for Interface ID for OSPFv2 Example, page 216
Configuring the SNMP ifIndex Value for Interface ID for OSPFv3 Example, page 217
Configuring the SNMP ifIndex Value for Interface ID for OSPFv2 Example
The following example configures the OSPF interfaces to use the SNMP ifIndex values for the interfaces
IDs. The show snmp mib ifmib ifindex command confirms that the SNMP MIB-II ifIndex values are used
for the Interface ID values in the OSPFv2 data fields.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# router ospf 1
Router(config-router)# interface-id snmp-if-index
Router(config-router)# ^Z
Router# show ip ospf 1 1 data router self
OSPF Router with ID (172.16.0.1) (Process ID 1)
Router Link States (Area 1)
LS age: 6
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 172.16.0.1
Advertising Router: 172.16.0.1
LS Seq Number: 80000007
Checksum: 0x63AF
Length: 48
Area Border Router
Number of Links: 2
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 172.17.0.1
Configuring the SNMP ifIndex Value for Interface ID for OSPFv3 Example
Configuration Examples for the Interface ID in Data Fields
Configuring the SNMP ifIndex Value for Interface ID for OSPFv3 Example
The following example configures the OSPFv3 interfaces to use the SNMP ifIndex values for the interface
IDs.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# ipv6 router ospf 1
Router(config-router)# interface-id snmp-if-index
The output from the show snmp mib ifmib ifindex command confirms that the SNMP MIB-II ifIndex
values are being used for the Interface ID values in the OSPFv3 data fields.
Router# show snmp mib ifmib ifindex Ethernet1/0
Ethernet1/0: Ifindex = 5
Router#
Router# show ipv6 ospf int
OSPF_VL0 is up, line protocol is up
Interface ID 71
Area 0, Process ID 1, Instance ID 0, Router ID 172.16.0.1
Network Type VIRTUAL_LINK, Cost: 10
Configured as demand circuit.
Run as demand circuit.
DoNotAge LSA allowed.
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:02
Index 1/2/3, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.1 (Hello suppressed)
Suppress hello for 1 neighbor(s)
Ethernet2/0 is up, line protocol is up
Link Local Address FE80::A8BB:CCFF:FE00:6F02, Interface ID 10
Area 0, Process ID 1, Instance ID 0, Router ID 172.16.0.1
Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 172.16.0.1, local address FE80::A8BB:CCFF:FE00:6F02
No backup designated router on this network
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:06
Index 1/1/2, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)
Ethernet1/0 is up, line protocol is up
Link Local Address FE80::A8BB:CCFF:FE00:6F01, Interface ID 6
Area 1, Process ID 1, Instance ID 2, Router ID 172.16.0.1
Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 172.16.0.1, local address FE80::A8BB:CCFF:FE00:6F01
Backup Designated router (ID) 10.0.0.1, local address FE80::A8BB:CCFF:FE00:6E01
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:06
Index 1/1/1, flood queue length 0
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
Configuration Examples for the Interface ID in Data Fields
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.1 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
Router#
Router# show ipv6 ospf data net adv 172.16.0.1
OSPFv3 Router with ID (172.16.0.1) (Process ID 1)
Net Link States (Area 1)
LS age: 144
Options: (V6-Bit E-Bit R-bit DC-Bit)
LS Type: Network Links
Link State ID: 6 (Interface ID of Designated Router)
Advertising Router: 172.16.0.1
LS Seq Number: 80000001
Checksum: 0x1FC0
Length: 32
Attached Router: 172.16.0.1
Attached Router: 10.0.0.1
Router# show ipv6 ospf data prefix adv 172.16.0.1
OSPFv3 Router with ID (172.16.0.1) (Process ID 1)
Intra Area Prefix Link States (Area 0)
Routing Bit Set on this LSA
LS age: 196
LS Type: Intra-Area-Prefix-LSA
Link State ID: 0
Advertising Router: 172.16.0.1
LS Seq Number: 80000001
Checksum: 0x6F11
Length: 44
Referenced LSA Type: 2001
Referenced Link State ID: 0
Referenced Advertising Router: 172.16.0.1
Number of Prefixes: 1
Prefix Address: 2002:0:2::
Prefix Length: 64, Options: None, Metric: 10
Intra Area Prefix Link States (Area 1)
Routing Bit Set on this LSA
LS age: 161
LS Type: Intra-Area-Prefix-LSA
Link State ID: 0
Advertising Router: 172.16.0.1
LS Seq Number: 80000001
Checksum: 0xB6E7
Length: 52
Referenced LSA Type: 2001
Referenced Link State ID: 0
Referenced Advertising Router: 172.16.0.1
Number of Prefixes: 1
Prefix Address: 2002:0:2:0:A8BB:CCFF:FE00:6F02
Prefix Length: 128, Options: LA , Metric: 0
Routing Bit Set on this LSA
LS age: 151
LS Type: Intra-Area-Prefix-LSA
Link State ID: 1006
Advertising Router: 172.16.0.1
LS Seq Number: 80000001
Checksum: 0x6E24
Length: 44
Referenced LSA Type: 2002
Referenced Link State ID: 6
Referenced Advertising Router: 172.16.0.1
Number of Prefixes: 1
Prefix Address: 2002:0:1::
Prefix Length: 64, Options: None, Metric: 0
Router#
Router# show ipv6 ospf data router
OSPFv3 Router with ID (10.0.0.1) (Process ID 1)
Router Link States (Area 0)
Routing Bit Set on this LSA
LS age: 5 (DoNotAge)
Options: (V6-Bit E-Bit R-bit DC-Bit)
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
Configuration Examples for the Interface ID in Data Fields
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
Additional References
Additional References
The following sections provide references related to the OSPF: SNMP ifIndex Value for Interface ID in
OSPFv2 and OSPFv3 Data Fields feature.
Related Documents
Related Topic
Document Title
OSPF commands
OSPF configuration
"Configuring OSPF"
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
None
RFCs
RFC
Title
RFC 2328
OSPF Version 2
RFC 2740
OSPF Version 3
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
Feature Information for SNMP ifIndex Value for Interface ID in Data Fields
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Feature Information for OSPF: SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data
Fields
Feature Name
Releases
Feature Information
12.4(6)T 12.2(31)SB2
12.2(33)SRB
Glossary
SNMP --Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the
exchange of management information between network devices. It is part of the Transmission Control
Protocol/Internet Protocol (TCP/IP) protocol suite.
SNMP ifIndex Value for Interface ID in OSPFv2 and OSPFv3 Data Fields
Note
See Internetworking Terms and Acronyms for terms not included in this glossary.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Restarting Mode--Also known as IETF NSF-restarting mode or graceful-restarting mode. In this mode,
the OSPF router process is performing non-stop forwarding recovery because of an RP switchover;
this may result from an RP crash or a software upgrade on the active RP.
Helper Mode--Also known as IETF NSF-awareness. In this mode, the neighboring router is restarting
and helping in the NSF recovery.
For more information about OSPF RFC 3623 Graceful Restart, see http://www.ietf.org/rfc/rfc3623.txt .
As the OSPF routing protocol starts to repopulate the RIB on a prefix-by-prefix basis, the updates in turn
cause prefix-by-prefix updates that CEF uses to update the FIB and adjacency databases. Existing and new
entries receive the new version number, indicating that they have been refreshed. The forwarding
information is updated on the line cards or forwarding engines during convergence. The RP signals when
the RIB has converged. The software removes all FIB and adjacency entries that have an epoch older than
the current switchover epoch. The FIB now represents the newest routing protocol forwarding information.
The OSPF routing protocol runs on only the active RP, and OSPF receives routing updates from OSPF
neighbor routers. The OSPF routing protocol does not run on the standby RP. Following a switchover,
OSPF requests that the NSF-aware neighbor devices send state information to help rebuild the routing
tables.
Note
For NSF operation, OSPF depends on CEF to continue forwarding packets while OSPF rebuilds the routing
information.
The neighbor must have a full adjacency with the restarting router over the associated network
segment.
There have been no changes to the link-state database since the restarting router began restarting.
The grace period has not yet expired.
Local policy allows the neighbor router to act as a helper router.
The neighbor router must not be in its own graceful restart process.
Helper mode for this router has not been disabled by the network administrator.
The grace-LSA that was originated by the restarting router is flushed, to signify that the restarting
router has exited the graceful restart process successfully.
The grace period of the grace-LSA expires.
A change in link-state database contents indicates a network topology change, forcing the termination
of the graceful restart process.
For complete information about graceful restart functionality, see RFC 3623 at http://www.ietf.org/rfc/
rfc3623.txt .
The OSPF RFC 3623 Graceful Restart Helper Mode feature is enabled by default. Disabling this feature is
not recommended because the disabled neighbor will detect the lost adjacency and the graceful restart
process will be terminated on the restarting neighbor router.
The strict LSA checking feature allows a helper router to terminate the graceful restart process if it detects
a changed LSA that would cause flooding during the graceful restart process. Strict LSA checking is
disabled by default. You can enable strict LSA checking when there is a change to an LSA that would be
flooded to the restarting router. You can configure strict LSA checking on both NSF-aware and NSFcapable routers; however, it becomes effective only when the router is in helper mode.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 454
Example:
Router(config-router)# nsf ietf helper disable
Command or Action
Purpose
Example:
Router(config-router)# nsf ietf strict-lsa-checking
Step 6 end
Example:
Router(config-router)# end
Example:
Router# show ip ospf 454
Additional References
The following sections provide references related to the OSPF RFC 3623 Graceful Restart Helper Mode
feature.
Related Documents
Related Topic
Document Title
OSPF commands
OSPF configuration
"Configuring OSPF"
Related Topic
Document Title
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
None
RFCs
RFC
Title
RFC 2328
OSPF Version 2
RFC 3623
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 20
Feature Name
Feature Information for OSPF RFC 3623 Graceful Restart Helper Mode
Releases
Feature Information
This document focuses on NSF
for OSPFv2 in Cisco IOS
software, using IETF
standardized graceful restart
functionality as described in RFC
3623.
The following commands were
introduced or modified: nsf cisco
helper disable, nsf ietf helper
disable, nsf ietf helper strict-lsachecking.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
Previous Methods to Limit the Number of IP Prefixes Carried in LSAs, page 232
Feature Overview, page 232
Feature Overview
The OSPF mechanism to exclude connected IP prefixes from LSAs allows network administrators to
control what IP prefixes are installed into LSAs. This functionality is implemented for router and network
LSAs in the following manner:
Note
For the router LSA, to exclude prefixes, the feature excludes link type 3 (stub link).
For the network LSA, the OSPF Designated Router (DR) generates LSAs with a special /32 network
mask (0xFFFFFFFF).
Previous versions of Cisco IOS software that do not have this feature will install the /32 prefix into the
routing table.
Note
Prefixes that are associated with loopbacks, secondary IP addresses, and passive interfaces are excluded
because typical network designs require those to remain reachable.
Note
If you have globally suppressed IP prefixes from connected IP networks by configuring the prefixsuppression router configuration command, the interface configuration command takes precedence over
the router configuration mode command.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 23
Step 4 prefix-suppression
Prevents OSPF from advertising all IP prefixes except prefixes that are
associated with loopbacks, secondary IP addresses, and passive
interfaces.
Example:
Router(config-router)# prefix-suppression
Command or Action
Step 5 end
Purpose
Returns to privileged EXEC mode.
Example:
Router(config-router)# end
enabled.
Example:
Router# show ip ospf
Examples
In the following example, output from the show ip ospf command shows that IP prefix advertisement has
been suppressed for OSPF process 1.
Router# show ip ospf
Routing Process "ospf 1" with ID 10.0.0.6
Start time: 00:00:04.912, Time elapsed: 00:02:35.184
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
It is an area border router
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 2. Checksum Sum 0x0132C8
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 3. 3 normal 0 stub 0 nssa
Number of areas transit capable is 1
External flood list length 0
IETF NSF helper support enabled
Cisco NSF helper support enabled
Prefix-suppression is enabled
.
.
.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# interface serial 0/0
Example:
Router(config-if)# ip ospf prefixsuppression
Step 5 end
Example:
Router(config-if)# end
Command or Action
Step 6 show ip ospf interface
Purpose
Displays OSPF-related interface information.
Note Use this command to verify that IP prefix suppression has been
Example:
Router# show ip ospf interface
Examples
In the following example, the output from the show ip ospf interface command verifies that prefix
suppression has been enabled for Ethernet interface 0/0.
Router# show ip ospf interface
Ethernet0/0 is up, line protocol is up
Internet Address 192.168.130.2/24, Area 2
Process ID 1, Router ID 10.0.0.6, Network Type BROADCAST, Cost: 10
Prefix-suppression is enabled
.
.
.
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# debug ip ospf lsa-generation
Command or Action
Purpose
Example:
Router# debug interface serial 0/0
Example:
Router# show debugging
Example:
Router# show logging
Examples
The following sample output from the debug ip ospf lsa-generation command verifies that for the
Ethernet interface 0/0, IP prefixes from the connected network 192.168.131.0 are excluded.
Router# debug ip ospf lsa-generation
OSPF summary lsa generation debugging is on
Router# debug condition interface e0/0
Condition 1 set
Router# show debugging
IP routing:
OSPF summary lsa generation debugging is on
Condition 1: interface Et0/0 (1 flags triggered)
Flags: Et0/0
Router# show logging
*Jun 5 21:54:47.295: OSPF: Suppressing 192.168.131.0/24 on Ethernet1/0 from router LSA
*Jun 5 21:54:52.355: OSPF: Suppressing 192.168.131.0/24 on Ethernet1/0 from router LSA
.
.
.
Excluding IP Prefixes from LSAs for an OSPF Process Example, page 238
Excluding IP Prefixes from LSAs for a Specified Interface Example, page 238
When the show ip ospf command is entered, the displayed output verifies that IP prefix suppression has
been enabled for OSPF process 23.
Router# show ip ospf
outing Process "ospf 23" with ID 10.0.0.6
Start time: 00:00:04.912, Time elapsed: 00:02:35.184
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
It is an area border router
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 2. Checksum Sum 0x0132C8
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 3. 3 normal 0 stub 0 nssa
Number of areas transit capable is 1
External flood list length 0
IETF NSF helper support enabled
Cisco NSF helper support enabled
Prefix-suppression is enabled
.
.
.
When the show ip ospf interface command is entered, the displayed output verifies that IP prefix
suppression is enabled for Ethernet interface 0/0.
Router# show ip ospf interface
Ethernet0/0 is up, line protocol is up
Internet Address 192.168.130.2/24, Area 2
Process ID 1, Router ID 10.0.0.6, Network Type BROADCAST, Cost: 10
Prefix-suppression is enabled
.
.
.
Additional References
The following sections provide references related to the OSPF Mechanism to Exclude Connected IP
Prefixes from LSA Advertisements feature.
Related Documents
Related Topic
Document Title
Standards
Standard
Title
None
--
MIBs
MIB
MIBs Link
There are no new MIBs that are associated with this To locate and download MIBs for selected
feature.
platforms, Cisco IOS releases, and feature sets, use
Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
Glossary
network LSA --The link-state advertisement created by the designated router (DR) or pseudonode that
represents a group of routers on the same interface. The network LSA advertises summary information to
represent the group of routers on the network.
router LSA --The link-state advertisement that is generated by a router. The router LSA advertises routing
information (connected routes) for the router.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.
It is recommended that you not change the default values because they are conservative and preserve the
current global RIB behavior.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id [vrf vpn-name]
4. local-rib-criteria [forwarding-address] [inter-area-summary] [nssa-translation]
5. end
6. show ip ospf process-id rib [redistribution] [network-prefix] [network-mask] [detail]
DETAILED STEPS
Command or Action
Purpose
Step 1 enable
Example:
Router> enable
Example:
Router# configure terminal
Example:
Router(config)# router ospf 23
Example:
Router(config-router)# local-rib-criteria forwardingaddress
Step 5 end
Example:
Router(config-router)# end
Command or Action
Purpose
Example:
Router# show ip ospf 23 rib
It is recommended to keep the default settings, but you can follow the steps in this section to change the
administrative distance for discard routes.
SUMMARY STEPS
1. enable
2. configure terminal
3. router ospf process-id [vrf vpn-name]
4. discard-route [external [distance]] [internal [distance]]
5. end
6. show ip route [ip-address [mask] [longer-prefixes] | protocol [process-id] | list [access-list-number |
access-list-name] | static download]
DETAILED STEPS
Command or Action
Step 1 enable
Purpose
Enables privileged EXEC mode.
Example:
Router> enable
Example:
Router# configure terminal
Command or Action
Purpose
Example:
Router(config)# router ospf 23
Example:
Step 5 end
Example:
Router(config-router)# end
Step 6 show ip route [ip-address [mask] [longer-prefixes] | protocol Displays the current state of the routing table.
[process-id] | list [access-list-number | access-list-name] |
Note Entering the show ip route command will verify
static download]
the changed administrative distance values for
external and internal discard routes.
Example:
Router# show ip route ospf 23
Examples
The sample output displayed for the show ip route command confirms that the administrative distance for
the IP route 192.168.0.0 255.255.255.0 is 110.
Router#
Troubleshooting Tips
You can research the output from the debug ip ospf rib command to learn about the function of the local
RIB and the interaction between the route redistribution process and the global RIB. For example, you can
learn why the routes that OSPF placed in the global RIB are not the same ones that you anticipated.
The output from the show ip route command verifies that the administrative distance for the internal route
10.2.0.0/16 is set to 30.
Router# show ip route 10.2.0.0 255.255.0.0
Routing entry for 10.2.0.0/16
Known via "ospf 1", distance 30, metric 1, type intra area
Routing Descriptor Blocks:
* directly connected, via Null0
Route metric is 1, traffic share count is 1
The output from the show ip route command verifies that the administrative distance for the external route
192.168.130.2/24 is set to 25.
Router# show ip route 192.168.130.2 255.255.255.0
Routing entry for 192.168.130.2/24
Known via "ospf 1", distance 25, metric 20, type intra area
Routing Descriptor Blocks:
* directly connected, via Null0
Route metric is 20, traffic share count is 1
Additional References
The following sections provide references related to the OSPFv2 Local RIB feature.
Related Documents
Related Topic
Document Title
OSPF commands
"Configuring OSPF"
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
RFCs
RFC
Title
None
--
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/
index.html
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 21
Feature Name
Releases
Feature Information
12.4(15)T
12.2(33)SRC
12.2(33)SB
15.0(1)SY
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned 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. (1110R)
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, network topology diagrams,
and other 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.