Feedback
|
Table Of Contents
Prerequisites for Implementing OSPF for IPv6
Restrictions for Implementing OSPF for IPv6
Information About Implementing OSPF for IPv6
Comparison of OSPFv3 and OSPF Version 2
Fast Convergence—LSA and SPF Throttling
Addresses Imported into OSPFv3
Link Quality Metrics Reporting for OSPFv3 with VMI Interfaces
OSPFv3 External Path Preference Option
How to Implement OSPF for IPv6
Configuring the OSPFv3 Router Process
Configuring the IPv6 Address Family in OSPFv3
Configuring the IPv4 Address Family in OSPFv3
Configuring Route Redistribution in OSPFv3
Enabling OSPFv3 on an Interface
Defining an OSPFv3 Area Range for the IPv6 or IPv4 Address Family
Configuring the OSPFv3 Max-Metric Router LSA
Tuning LSA and SPF Transmission for OSPFv3 Fast Convergence
Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
Enabling Event Logging for LSA and SPF Rate Limiting for the IPv6 or IPv4 Address Family
Enabling Event Logging for LSA and SPF Rate Limiting
Clearing the Content of an Event Log
Calculating OSPFv3 External Path Preferences per RFC 5340
Enabling OSPFv3 Graceful Restart
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Capable Router
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Aware Router
Verifying OSPFv3 Configuration and Operation
Verifying OSPFv3 Configuration and Operation
Configuration Examples for Implementing OSPF for IPv6
Example: Enabling OSPFv3 on an Interface Configuration
Example: Defining an OSPFv3 Area Range
Example: Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
Example: Forcing SPF Configuration
Feature Information for Implementing OSPF for IPv6
Implementing OSPF for IPv6
First Published: May 5, 2008Last Updated: July 25, 2011The Implementing OSPF for IPv6 module expands on Open Shortest Path First version 3 (OSPFv3), or OSPF for IPv6, to provide support for IPv6 routing prefixes.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Implementing OSPF for IPv6" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Implementing OSPF for IPv6
•
Restrictions for Implementing OSPF for IPv6
•
Information About Implementing OSPF for IPv6
•
How to Implement OSPF for IPv6
•
Configuration Examples for Implementing OSPF for IPv6
•
Feature Information for Implementing OSPF for IPv6
Prerequisites for Implementing OSPF for IPv6
•
Complete the OSPFv3 network strategy and planning for your IPv6 network. For example, you must decide whether multiple areas are required.
•
Enable IPv6 unicast routing.
•
Enable IPv6 on the interface.
•
Configure the IP Security (IPsec) secure socket application program interface (API) on OSPFv3 in order to enable authentication and encryption.
•
To use the IPv4 unicast address families (AF) in OSPFv3, you must enable IPv6 on a link, although the link may not be participating in IPv6 unicast AF.
•
With the OSPFv3 Address Families feature, users may have two router processes per interface, but only one process per AF. If the AF is IPv4 an IPv4 address must first be configured on the interface, but IPv6 must be enabled on the interface.
This document assumes that you are familiar with IPv4. Refer to the publications referenced in the "Related Documents" section for IPv4 configuration and command reference information.
Restrictions for Implementing OSPF for IPv6
•
When running a dual-stack IP network with OSPF version 2 for IPv4 and OSPFv3, be careful when changing the defaults for commands used to enable OSPFv3. Changing these defaults may affect your OSPFv3 network, possibly adversely.
•
A packet will be rejected on a router if the packet is coming from an IPv6 address that is found on any interface on the same router.
Information About Implementing OSPF for IPv6
•
Comparison of OSPFv3 and OSPF Version 2
•
Fast Convergence—LSA and SPF Throttling
•
Addresses Imported into OSPFv3
•
Link Quality Metrics Reporting for OSPFv3 with VMI Interfaces
•
OSPFv3 External Path Preference Option
How OSPFv3 Works
OSPF is a routing protocol for IP. It is a link-state protocol, as opposed to a distance-vector protocol. Think of a link as being an interface on a networking device. A link-state protocol makes its routing decisions based on the states of the links that connect source and destination machines. The state of a link is a description of that interface and its relationship to its neighboring networking devices. The interface information includes the IPv6 prefix of the interface, the network mask, the type of network it is connected to, the routers connected to that network, and so on. This information is propagated in various type of link-state advertisements (LSAs).
A router's collection of LSA data is stored in a link-state database. The contents of the database, when subjected to the Dijkstra algorithm, result in the creation of the OSPF routing table. The difference between the database and the routing table is that the database contains a complete collection of raw data; the routing table contains a list of shortest paths to known destinations via specific router interface ports.
OSPF version 3, which is described in RFC 5340, supports IPv6.
Comparison of OSPFv3 and OSPF Version 2
Much of the OSPFv3 feature is the same as in OSPF version 2. OSPFv3, which is described in RFC 5340, expands on OSPF version 2 to provide support for IPv6 routing prefixes and the larger size of IPv6 addresses.
In OSPFv3, a routing process does not need to be explicitly created. Enabling OSPFv3 on an interface will cause a routing process, and its associated configuration, to be created.
In OSPFv3, each interface must be enabled using commands in interface configuration mode. This feature is different from OSPF version 2, in which interfaces are indirectly enabled using the router configuration mode.
In IPv6, users can configure many address prefixes on an interface. In OSPFv3, all address prefixes on an interface are included by default. Users cannot select some address prefixes to be imported into OSPFv3; either all address prefixes on an interface are imported, or no address prefixes on an interface are imported.
Unlike OSPF version 2, multiple instances of OSPFv3 can be run on a link.
In OSPFv3, it is possible that no IPv4 addresses will be configured on any interface. In this case, the user must use the router-id command to configure a router ID before the OSPF process will be started. A router ID is a 32-bit opaque number. OSPF version 2 takes advantage of the 32-bit IPv4 address to pick an IPv4 address as the router ID. If an IPv4 address does exist when OSPFv3 is enabled on an interface, then that IPv4 address is used for the router ID. If more than one IPv4 address is available, a router ID is chosen using the same rules as for OSPF version 2.
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.
OSPFv3 Address Families
The OSPFv3 address families feature enables both IPv4 and IPv6 unicast traffic to be supported. With this feature, users may have two router processes per interface, but only one process per AF. If the IPv4 AF is used, an IPv4 address must first be configured on the interface, but IPv6 must be enabled on the interface. A single IPv4 or IPv6 OSPFv3 process running multiple instances on the same interface is not supported.
Users with an IPv6 network that uses OSPFv3 as its IGP may want to use the same IGP to help carry and install IPv4 routes. All routers on this network have an IPv6 forwarding stack. Some (or all) of the links on this network may be allowed to do IPv4 forwarding and be configured with IPv4 addresses. Pockets of IPv4-only routers exist around the edges running an IPv4 static or dynamic routing protocol. In this scenario, users need the ability to forward IPv4 traffic between these pockets without tunneling overhead, which means that any IPv4 transit router has both IPv4 and IPv6 forwarding stacks (e.g., is dual stack).
This feature allows a separate (possibly incongruent) topology to be constructed for the IPv4 AF. It installs Pv4 routes in IPv4 RIB, and then the forwarding occurs natively. The OSPFv3 process fully supports an IPv4 AF topology and can redistribute routes from and into any other IPv4 routing protocol.
An OSPFv3 process can be configured to be either IPv4 or IPv6. The address-family command is used to determine which AF will run in the OSPFv3 process, and only one address family can be configured per instance. Once the AF is selected, users can enable multiple instances on a link and enable address-family-specific commands.
Different instance ID ranges are used for each AF. Each AF establishes different adjacencies, has a different link state database, and computes a different shortest path tree. The AF then installs the routes in AF-specific RIB. LSAs that carry IPv6 unicast prefixes are used without any modification in different instances to carry each AFs' prefixes.
The IPv4 subnets configured on OSPFv3-enabled interfaces are advertised through intra-area prefix LSAs, just as any IPv6 prefixes. External LSAs are used to advertise IPv4 routes redistributed from any IPv4 routing protocol, including connected and static. The IPv4 OSPFv3 process runs the SPF calculations and finds the shortest path to those IPv4 destinations. These computed routes are then inserted in the IPv4 RIB (computed routes are inserted into an IPv6 RIB for an IPv6 AF).
Because the IPv4 OSPFv3 process allocates a unique pdbindex in the IPv4 RIB, all other IPv4 routing protocols can redistribute routes from it. The parse chain for all protocols is same, so the ospfv3 keyword added to the list of IPv4 routing protocols causes OSPFv3 to appear in the redistribute command from any IPv4 routing protocol. With the ospfv3 keyword, IPv4 OSPFv3 routes can be redistributed into any other IPv4 routing protocol as defined in the redistribute ospfv3 command.
The OSPFv3 address families feature is supported as of Cisco IOS Release 15.1(3)S and Cisco IOS Release 15.2(1)T. Cisco routers that run software older than these releases and third-party routers will not neighbor with routers running the AF feature for the IPv4 AF because they do not set the AF bit. Therefore, those routers will not participate in the IPv4 AF SPF calculations and will not install the IPv4 OSPFv3 routes in the IPv6 RIB.
LSA Types for OSPFv3
The following list describes LSA types, each of which has a different purpose:
•
Router LSAs (Type 1)—Describes the link state and costs of a router's links to the area. These LSAs are flooded within an area only. The LSA indicates if the router is an Area Border Router (ABR) or Autonomous System Boundary Router (ASBR), and if it is one end of a virtual link. Type 1 LSAs are also used to advertise stub networks. In OSPFv3, these LSAs have no address information and are network-protocol-independent. In OSPFv3, router interface information may be spread across multiple router LSAs. Receivers must concatenate all router LSAs originated by a given router when running the SPF calculation.
•
Network LSAs (Type 2)—Describes the link-state and cost information for all routers attached to the network. This LSA is an aggregation of all the link-state and cost information in the network. Only a designated router tracks this information and can generate a network LSA. In OSPFv3, network LSAs have no address information and are network-protocol-independent.
•
Interarea-prefix LSAs for ABRs (Type 3)—Advertises internal networks to routers in other areas (interarea routes). Type 3 LSAs may represent a single network or a set of networks summarized into one advertisement. Only ABRs generate summary LSAs. In OSPFv3, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0.
•
Interarea-router LSAs for ASBRs (Type 4)—Advertises the location of an ASBR. Routers that are trying to reach an external network use these advertisements to determine the best path to the next hop. Type 4 LSAs are generated by ABRs on behalf of ASBRs.
•
Autonomous system external LSAs (Type 5)—Redistributes routes from another AS, usually from a different routing protocol into OSPFv3. In OSPFv3, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0.
•
Link LSAs (Type 8)—Have local-link flooding scope and are never flooded beyond the link with which they are associated. Link LSAs provide the link-local address of the router to all other routers attached to the link, inform other routers attached to the link of a list of prefixes to associate with the link, and allow the router to assert a collection of Options bits to associate with the network LSA that will be originated for the link.
•
Intra-Area-Prefix LSAs (Type 9)—A router can originate multiple intra-area-prefix LSAs for each router or transit network, each with a unique link-state ID. The link-state ID for each intra-area-prefix LSA describes its association to either the router LSA or the network LSA and contains prefixes for stub and transit networks.
An address prefix occurs in almost all newly defined LSAs. The prefix is represented by three fields: PrefixLength, PrefixOptions, and Address Prefix. In OSPFv3, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0. Type 3 and Type 9 LSAs carry all prefix (subnet) information that, in OSPFv2, is included in router LSAs and network LSAs. The Options field in certain LSAs (router LSAs, network LSAs, interarea-router LSAs, and link LSAs) has been expanded to 24 bits to provide support for OSPFv3.
In OSPFv3, the sole function of link-state ID in interarea-prefix LSAs, interarea-router LSAs, and autonomous-system external LSAs is to identify individual pieces of the link-state database. All addresses or router IDs that are expressed by the link-state ID in OSPF version 2 are carried in the body of the LSA in OSPFv3.
The link-state ID in network LSAs and link LSAs is always the interface ID of the originating router on the link being described. For this reason, network LSAs and link LSAs are now the only LSAs whose size cannot be limited. A network LSA must list all routers connected to the link, and a link LSA must list all of the address prefixes of a router on the link.
OSPFv3 Max-Metric Router LSA
The OSPFv3 max-metric router LSA feature enables OSPFv3 to advertise its locally generated router LSAs with a maximum metric. The feature allows OSPFv3 processes to converge but not attract transit traffic through the router if there are better alternate paths. After a specified timeout or a notification from BGP, OSPFv3 advertises the LSAs with normal metrics.
The max-metric LSA control places the OSPFv3 router into the stub router role using its LSA advertisement. A stub router only forwards packets destined to go to its directly connected links. In OSPFv3 networks, a router could become a stub router by advertising large metrics for its connected links, so that the cost of a path through this router becomes larger than that of an alternative path. OSPFv3 stub router advertisement allows a router to advertise the infinity metric (0xFFFF) for its connected links in router LSAs and advertise normal interface cost if the link is a stub network.
Fast Convergence—LSA and SPF Throttling
The OSPFv3 LSA and SPF throttling feature provides a dynamic mechanism to slow down link-state advertisement updates in OSPF during times of network instability. It also allows faster OSPF convergence by providing LSA rate limiting in milliseconds.
Previously, OSPFv3 used static timers for rate-limiting SPF calculation and LSA generation. Although these timers are configurable, the values used are specified in seconds, which poses a limitation on OSPFv3 convergence. LSA and SPF throttling achieves subsecond convergence by providing a more sophisticated SPF and LSA rate-limiting mechanism that is able to react quickly to changes and also provide stability and protection during prolonged periods of instability.
Addresses Imported into OSPFv3
When importing the set of addresses specified on an interface on which OSPFv3 is running into OSPFv3, users cannot select specific addresses to be imported. Either all addresses are imported, or no addresses are imported.
OSPFv3 Customization
You can customize OSPFv3 for your network, but you likely will not need to do so. The defaults for OSPFv3 are set to meet the requirements of most customers and features. If you must change the defaults, refer to the IPv6 command reference to find the appropriate syntax.
CautionBe careful when changing the defaults. Changing defaults will affect your OSPFv3 network, possibly adversely.
OSPFv3 Virtual Links
For each virtual link, a master security information datablock is created for the virtual link. Because a secure socket must be opened on each interface, there will be a corresponding security information datablock for each interface in the transit area. The secure socket state is kept in the interface's security information datablock. The state field in the master security information datablock reflects the status of all of the secure sockets opened for the virtual link. If all of the secure sockets are UP, then the security state for the virtual link will be set to UP.
Link Quality Metrics Reporting for OSPFv3 with VMI Interfaces
OSPFv3 is one of the routing protocols that can be used with Virtual Multipoint Interfaces (VMIs) in router-to-radio networks. The quality of a radio link has a direct impact on the throughput that can be achieved by router-router traffic. The PPPoE protocol has been extended to provide a process by which a router can request, or a radio can report, link quality metric information. Cisco's OSFPv3 implementation has been enhanced so that the route cost to a neighbor is dynamically updated based on metrics reported by the radio, thus allowing the best route to be chosen within a given set of radio links.
The routing protocols receive raw radio link data, and compute a composite quality metric for each link. In computing these metrics, the following factors may be considered:
•
Maximum Data Rate—the theoretical maximum data rate of the radio link, in bytes per second
•
Current Data Rate—the current data rate achieved on the link, in bytes per second
•
Latency—the transmission delay packets encounter, in milliseconds
•
Resources—a percentage (0 to 100) that can represent the remaining amount of a resource (such as battery power)
•
Relative Link Quality—a numeric value (0-100) representing relative quality, with 100 being the highest quality
Metrics can be weighted during the configuration process to emphasize or de-emphasize particular characteristics. For example, if throughput is a particular concern, the current data rate metric could be weighted so that it is factored more heavily into the composite metric. Similarly, a metric that is of no concern can be omitted from the composite calculation.
Link metrics can change rapidly, often by very small degrees, which could result in a flood of meaningless routing updates. In a worst case scenario, the network would be churning almost continuously as it struggled to react to minor variations in link quality. To alleviate this concern, Cisco provides a tunable dampening mechanism that allows the user to configure threshold values. Any metric change that falls below the threshold is ignored.The quality of a connection to a neighbor varies, based on various characteristics of the interface when OSPF is used as the routing protocol. The routing protocol receives dynamic raw radio link characteristics and computes a composite metric that is used to reduce the effect of frequent routing changes.
A tunable hysteresis mechanism allows users to adjust the threshold to the routing changes that occur when the router receives a signal that a new peer has been discovered, or that an existing peer is unreachable. The tunable metric is weighted and is adjusted dynamically to account for the following characteristics:
•
Current and maximum bandwidth
•
Latency
•
Resources
•
L2 factor
Individual weights can be deconfigured and all weights can be cleared so that the cost is set back to the default value for the interface type. Based on the routing changes that occur, cost can be determined by the application of these metrics.
OSPFv3 External Path Preference Option
Per RFC 5340, the following rules indicate which paths are preferred when multiple intra-AS paths are available to ASBRs or forwarding addresses:
•
Intra-area paths using non-backbone areas are always the most preferred.
•
The other paths, intra-area backbone paths and inter-area paths, are of equal preference.
These rules apply when the same ASBR is reachable through multiple areas, or when trying to decide which of several AS-external-LSAs should be preferred. In the former case the paths all terminate at the same ASBR, while in the latter the paths terminate at separate ASBRs or forwarding addresses. In either case, each path is represented by a separate routing table entry. This feature only applies when RFC 1583 compatibility is set to disabled using the no compatibility rfc1583 command (RFC 5340 provides an update to RFC 1583).
CautionTo minimize the chance of routing loops, all OSPF routers in an OSPF routing domain should have RFC compatibility set identically.
OSPFv3 Graceful Restart
The graceful restart feature in OSPFv3 allows nonstop data forwarding along routes that are already known while the OSPFv3 routing protocol information is being restored. A router can participate in graceful restart either in restart mode (such as in a graceful-restart-capable router) or in helper mode (such as in a graceful-restart-aware router).
To perform the graceful restart function, a router must be in high availability (HA) stateful switchover (SSO) mode (that is, dual RP). A router capable of graceful restart will perform the graceful restart function when the following failures occur:
•
A Route Processor (RP) failure that results in switchover to standby RP
•
A planned RP switchover to standby RP
The graceful restart feature requires that neighboring routers be graceful-restart aware.
For further information about SSO and nonstop forwarding (NSF), see the Stateful Switchover and Cisco Nonstop Forwarding documents.
How to Implement OSPF for IPv6
•
Configuring the OSPFv3 Router Process
•
Configuring the IPv6 Address Family in OSPFv3
•
Configuring the IPv4 Address Family in OSPFv3
•
Configuring Route Redistribution in OSPFv3
•
Enabling OSPFv3 on an Interface
•
Defining an OSPFv3 Area Range for the IPv6 or IPv4 Address Family
•
Configuring the OSPFv3 Max-Metric Router LSA
•
Tuning LSA and SPF Transmission for OSPFv3 Fast Convergence
•
Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
•
Enabling Event Logging for LSA and SPF Rate Limiting for the IPv6 or IPv4 Address Family
•
Calculating OSPFv3 External Path Preferences per RFC 5340
•
Enabling OSPFv3 Graceful Restart
•
Verifying OSPFv3 Configuration and Operation
Configuring the OSPFv3 Router Process
Once you have completed step 3 and entered OSPFv3 router configuration mode, you can perform any of the subsequent steps in this task as needed to configure OSPFv3 router configuration.
This task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
area area-ID [default-cost | nssa | stub]
5.
auto-cost reference-bandwidth Mbps
6.
bfd all-interfaces
7.
default {area area-ID [range ipv6-prefix | virtual-link router-id]} [default-information originate [always | metric | metric-type | route-map] | distance | distribute-list prefix-list prefix-list-name {in | out} [interface] | maximum-paths paths | redistribute protocol | summary-prefix ipv6-prefix]
8.
ignore lsa mospf
9.
interface-id snmp-if-index
10.
log-adjacency-changes [detail]
11.
passive-interface [default | interface-type interface-number]
12.
queue-depth {hello | update} {queue-size | unlimited}
13.
router-id {router-id}
DETAILED STEPS
Configuring the IPv6 Address Family in OSPFv3
Perform this task to configure the IPv6 address family in OSPFv3. Once you have completed step 4 and entered IPv6 address-family configuration mode, you can perform any of the subsequent steps in this task as needed to configure the IPv6 AF.
The task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
address-family ipv6 unicast
5.
area area-ID range ipv6-prefix/prefix-length
6.
default {area area-ID [range ipv6-prefix | virtual-link router-id]} [default-information originate [always | metric | metric-type | route-map] | distance | distribute-list prefix-list prefix-list-name {in | out} [interface] | maximum-paths paths | redistribute protocol | summary-prefix ipv6-prefix]
7.
default-information originate [always | metric metric-value | metric-type type-value | route-map map-name]
8.
default-metric metric-value
9.
distance distance
10.
distribute-list prefix-list list-name {in [interface-type interface-number] | out routing-process [as-number]}
11.
maximum-paths number-paths
12.
summary-prefix prefix [not-advertise | tag tag-value]
DETAILED STEPS
Configuring the IPv4 Address Family in OSPFv3
Perform this task to configure the IPv4 address family in OSPFv3. Once you have completed step 4 and entered IPv4 address-family configuration mode, you can perform any of the subsequent steps in this task as needed to configure the IPv4 AF.
The task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
address-family ipv4 unicast
5.
area area-id range ip-address ip-address-mask [advertise | not-advertise] [cost cost]
6.
default {area area-ID [range ipv6-prefix | virtual-link router-id]} [default-information originate [always | metric | metric-type | route-map] | distance | distribute-list prefix-list prefix-list-name {in | out} [interface] | maximum-paths paths | redistribute protocol | summary-prefix ipv6-prefix]
7.
default-information originate [always | metric metric-value | metric-type type-value | route-map map-name]
8.
default-metric metric-value
9.
distance distance
10.
distribute-list prefix-list list-name {in [interface-type interface-number] | out routing-process [as-number]}
11.
maximum-paths number-paths
12.
summary-prefix prefix [not-advertise | tag tag-value]
DETAILED STEPS
Configuring Route Redistribution in OSPFv3
The task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
address-family ipv6 unicast
or
address-family ipv4 unicast
5.
redistribute source-protocol [process-id] [options]
DETAILED STEPS
Enabling OSPFv3 on an Interface
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
ospfv3 process-id area area-ID {ipv4 | ipv6} [instance instance-id]
or
ipv6 ospf process-id area area-id [instance instance-id]
DETAILED STEPS
Defining an OSPFv3 Area Range for the IPv6 or IPv4 Address Family
The cost of the summarized routes will be the highest cost of the routes being summarized. For example, if the following routes are summarized:
OI 2001:DB8:0:7::/64 [110/20]via FE80::A8BB:CCFF:FE00:6F00, Ethernet0/0OI 2001:DB8:0:8::/64 [110/100]via FE80::A8BB:CCFF:FE00:6F00, Ethernet0/0OI 2001:DB8:0:9::/64 [110/20]via FE80::A8BB:CCFF:FE00:6F00, Ethernet0/0They become one summarized route, as follows:
OI 2001:DB8::/48 [110/100]via FE80::A8BB:CCFF:FE00:6F00, Ethernet0/0The task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
Prerequisites
OSPFv3 routing must be enabled.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
address-family ipv6 unicast
or
address-family ipv4 unicast
5.
area area-ID range ipv6-prefix
DETAILED STEPS
Defining an OSPFv3 Area Range
The task can be performed in releases prior to Cisco IOS Release 15.1(3)S and 15.2(1)T.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
area area-id range ipv6-prefix/prefix-length [advertise | not-advertise] [cost cost]
DETAILED STEPS
Configuring the OSPFv3 Max-Metric Router LSA
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
max-metric router-lsa [external-lsa [max-metric-value]] [include-stub] [inter-area-lsas [max-metric-value]] [on-startup {seconds | wait-for-bgp}] [prefix-lsa] [stub-prefix-lsa [max-metric-value]] [summary-lsa [max-metric-value]]
5.
exit
6.
show ospfv3 [process-id] [address-family] max-metric
DETAILED STEPS
Tuning LSA and SPF Transmission for OSPFv3 Fast Convergence
The task can be performed in Cisco IOS XE Release 3.4S and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
timers lsa arrival milliseconds
5.
timers pacing flood milliseconds
6.
timers pacing lsa-group seconds
7.
timers pacing retransmission milliseconds
DETAILED STEPS
Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
The task can be performed in releases prior to Cisco IOS XE Release 3.4S.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
timers throttle spf spf-start spf-hold spf-max-wait
5.
timers throttle lsa start-interval hold-interval max-interval
6.
timers lsa arrival milliseconds
7.
timers pacing flood milliseconds
DETAILED STEPS
Enabling Event Logging for LSA and SPF Rate Limiting for the IPv6 or IPv4 Address Family
This task can be performed in Cisco IOS XE Release 3.4S and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
address-family ipv6 unicast
or
address-family ipv4 unicast
5.
event-log [one-shot | pause | size number-of-events]
DETAILED STEPS
Enabling Event Logging for LSA and SPF Rate Limiting
This task can be performed in releases prior to Cisco IOS XE Release 3.4S.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
event-log [size [number of events]] [one-shot] [pause]
DETAILED STEPS
Clearing the Content of an Event Log
SUMMARY STEPS
1.
enable
2.
clear ipv6 ospf [process-id] events
DETAILED STEPS
Calculating OSPFv3 External Path Preferences per RFC 5340
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
no compatible rfc1583
DETAILED STEPS
Enabling OSPFv3 Graceful Restart
•
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Capable Router
•
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Aware Router
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Capable Router
The task can be performed in Cisco IOS XE 3.4S and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
graceful-restart [restart-interval interval]
DETAILED STEPS
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Capable Router
The task can be performed in releases prior to Cisco IOS XE Release 3.4S.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
graceful-restart [restart-interval interval]
DETAILED STEPS
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Aware Router
The task can be performed in Cisco IOS Release 15.1(3)S and 15.2(1)T and later releases.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router ospfv3 [process-id]
4.
graceful-restart helper {disable | strict-lsa-checking}
DETAILED STEPS
Enabling OSPFv3 Graceful Restart on a Graceful-Restart-Aware Router
The task can be performed in releases prior to Cisco IOS Release 15.1(3)S and 15.2(1)T.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ipv6 router ospf process-id
4.
graceful-restart helper {disable | strict-lsa-checking}
DETAILED STEPS
Forcing an SPF Calculation
SUMMARY STEPS
1.
enable
2.
clear ospfv3 [process-id] force-spf
3.
clear ospfv3 [process-id] process
4.
clear ospfv3 [process-id] redistribution
5.
clear ipv6 ospf [process-id] {process | force-spf | redistribution}
DETAILED STEPS
Verifying OSPFv3 Configuration and Operation
This task is optional. The commands in this task are available in Cisco IOS XE Release 3.4S and later releases.
SUMMARY STEPS
1.
enable
2.
show ospfv3 [process-id] border-routers
3.
show ospfv3 [process-id [area-id]] database [database-summary | internal | external [ipv6-prefix] [link-state-id] | grace | inter-area prefix [ipv6-prefix | link-state-id] | inter-area router [destination-router-id | link-state-id] | link [interface interface-name | link-state-id] | network [link-state-id] | nssa-external [ipv6-prefix] [link-state-id] | prefix [ref-lsa {router | network} | link-state-id] | promiscuous | router [link-state-id] | unknown [{area | as | link} [link-state-id]] [adv-router router-id] [self-originate]
4.
show ospfv3 [process-id] events [generic | interface | lsa | neighbor | reverse | rib | spf]
5.
show ospfv3 [process-id] [area-id] flood-list interface-type interface-number
6.
show ospfv3 [process-id] graceful-restart
7.
show ospfv3 [process-id] [area-id] interface [type number] [brief]
8.
show ospfv3 [process-id] [area-id] neighbor [interface-type interface-number] [neighbor-id] [detail]
9.
show ospfv3 [process-id] [area-id] request-list [neighbor] [interface] [interface-neighbor]
10.
show ospfv3 [process-id] [area-id] retransmission-list [neighbor] [interface] [interface-neighbor]
11.
show ospfv3 [process-id] statistic [detail]
12.
show ospfv3 [process-id] summary-prefix
13.
show ospfv3 [process-id] timers rate-limit
14.
show ospfv3 [process-id] traffic [interface-type interface-number]
15.
show ospfv3 [process-id] virtual-links
DETAILED STEPS
Verifying OSPFv3 Configuration and Operation
SUMMARY STEPS
1.
enable
2.
show ipv6 ospf [process-id] [area-id] interface [interface-type interface-number]
3.
show ipv6 ospf [process-id] [area-id]
4.
show ipv6 ospf [process-id] event [generic | interface | lsa | neighbor | reverse | rib | spf]
DETAILED STEPS
Examples
•
Sample Output for the show ipv6 ospf interface Command
•
Sample Output for the show ipv6 ospf Command
•
Sample Output for the show ipv6 ospf graceful-restart Command
Sample Output for the show ipv6 ospf interface Command
The following is sample output from the show ipv6 ospf interface command with regular interfaces and a virtual link that are protected by encryption and authentication:
Router# show ipv6 ospf interfaceOSPFv3_VL1 is up, line protocol is upInterface ID 69Area 0, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type VIRTUAL_LINK, Cost: 64Configured as demand circuit.Run as demand circuit.DoNotAge LSA allowed.NULL encryption SHA-1 auth SPI 3944, secure socket UP (errors: 0)Transmit Delay is 1 sec, State POINT_TO_POINT,Timer intervals configured, Hello 2, Dead 10, Wait 40, Retransmit 5Hello due in 00:00:00Index 1/3/5, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 1, maximum is 1Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 10.2.0.1 (Hello suppressed)Suppress hello for 1 neighbor(s)OSPFv3_VL0 is up, line protocol is upInterface ID 67Area 0, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type VIRTUAL_LINK, Cost: 128Configured as demand circuit.Run as demand circuit.DoNotAge LSA allowed.MD5 authentication SPI 940, secure socket UP (errors: 0)Transmit Delay is 1 sec, State POINT_TO_POINT,Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:09Index 1/2/4, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 1, maximum is 10Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 10.1.0.1 (Hello suppressed)Suppress hello for 1 neighbor(s)Gigabitethernet1/0/0 is up, line protocol is upLink Local Address FE80::A8BB:CCFF:FE00:6601, Interface ID 6Area 0, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type BROADCAST, Cost: 10Transmit Delay is 1 sec, State DR, Priority 1Designated Router (ID) 10.0.0.1, local address FE80::A8BB:CCFF:FE00:6601No backup designated router on this networkTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:09Index 1/1/1, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 0, maximum is 0Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 0, Adjacent neighbor count is 0Suppress hello for 0 neighbor(s)Serial12/0 is up, line protocol is upLink Local Address FE80::A8BB:CCFF:FE00:6600, Interface ID 50Area 1, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type POINT_TO_POINT, Cost: 64AES-CBC encryption SHA-1 auth SPI 2503, secure socket UP (errors: 0)authentication NULLTransmit Delay is 1 sec, State POINT_TO_POINT,Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:09Index 1/2/3, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 1, maximum is 5Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 10.2.0.1Suppress hello for 0 neighbor(s)Serial11/0 is up, line protocol is upLink Local Address FE80::A8BB:CCFF:FE00:6600, Interface ID 46Area 1, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type POINT_TO_POINT, Cost: 64MD5 authentication (Area) SPI 500, secure socket UP (errors: 0)Transmit Delay is 1 sec, State POINT_TO_POINT,Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:09Index 1/1/2, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 1, maximum is 5Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 1.0.0.1Suppress hello for 0 neighbor(s)Sample Output for the show ipv6 ospf Command
The following is sample output from the show ipv6 ospf command:
Router# show ipv6 ospfRouting Process "ospfv3 1" with ID 172.16.3.3It is an autonomous system boundary routerRedistributing External Routes from,staticSPF schedule delay 5 secs, Hold time between two SPFs 10 secsMinimum LSA interval 5 secs. Minimum LSA arrival 1 secsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsNumber of external LSA 1. Checksum Sum 0x218DNumber of areas in this router is 1. 1 normal 0 stub 0 nssaArea 1Number of interfaces in this area is 2SPF algorithm executed 9 timesNumber of LSA 15. Checksum Sum 0x67581Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Sample Output for the show ipv6 ospf graceful-restart Command
The following is sample output from the show ipv6 ospf graceful-restart command:
Router# show ipv6 ospf graceful-restartRouting Process "ospf 1"Graceful Restart enabledrestart-interval limit: 120 sec, last restart 00:00:15 ago (took 36 secs)Graceful Restart helper support enabledRouter status : ActiveRouter is running in SSO modeOSPF restart state : NO_RESTARTRouter ID 10.1.1.1, checkpoint Router ID 10.0.0.0Configuration Examples for Implementing OSPF for IPv6
•
Example: Enabling OSPFv3 on an Interface Configuration
•
Example: Defining an OSPFv3 Area Range
•
Example: Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
•
Example: Forcing SPF Configuration
Example: Enabling OSPFv3 on an Interface Configuration
The following example configures an OSPFv3 routing process 109 to run on the interface and puts it in area 1:
ipv6 ospf 109 area 1Example: Defining an OSPFv3 Area Range
The following example specifies an OSPFv3 area range:
interface gigabitethernet7/0/0ipv6 address 2001:DB8:0:7::/64 eui-64ipv6 enableipv6 ospf 1 area 1!interface gigabitethernet8/0/0ipv6 address 2001:DB8:0:8::/64 eui-64ipv6 enableipv6 ospf 1 area 1!interface gigabitethernet9/0/0ipv6 address 2001:DB8:0:9::/64 eui-64ipv6 enableipv6 ospf 1 area 1!ipv6 router ospf 1router-id 10.11.11.1area 1 range 2001:DB8::/48Example: Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
The following example displays the configuration values for SPF and LSA throttling timers:
Router# show ipv6 ospf
Routing Process "ospfv3 1" with ID 10.9.4.1
Event-log enabled, Maximum number of events: 1000, Mode: cyclic
It is an autonomous system boundary router
Redistributing External Routes from,
ospf 2
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
Example: Forcing SPF Configuration
The following example triggers SPF to redo the SPF and repopulate the routing tables:
clear ipv6 ospf force-spfAdditional References
Related Documents
Related Topic Document TitleConfiguring a router ID in OSPF
•
"Configuring OSPF," Cisco IOS XE IP Routing Protocols Configuration Guide
LSA throttling
"OSPF Link-State Advertisement (LSA) Throttling," Cisco IOS XE IP Routing Protocols Configuration Guide
OSPFv3 commands
IPv6 supported feature list
"Start Here: Cisco IOS XE Software Release Specifics for IPv6 Features," Cisco IOS XE IPv6 Configuration Guide
Implementing basic IPv6 connectivity
"Implementing IPv6 Addressing and Basic Connectivity," Cisco IOS XE IPv6 Configuration Guide
Stateful switchover
"Stateful Switchover," Cisco IOS XE High Availability Configuration Guide
Cisco nonstop forwarding
"Cisco Nonstop Forwarding," Cisco IOS XE High Availability Configuration Guide
OSPF for IPv4 commands
Security configuration tasks (IPv4)
Cisco IOS XE Security Configuration Guide, Release 2
Security commands: complete command syntax, command mode, defaults, usage guidelines, and examples (IPv4)
Cisco IOS master command list, all releases
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
MIBs MIBs LinkNone
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Implementing OSPF for IPv6
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Table 1 Feature Information for Implementing OSPF for IPv6
Feature Name Releases Feature InformationIPv6 Routing—Fast Convergence—LSA and SPF Throttling
Cisco IOS XE Release 2.1
The OSPFv3 LSA and SPF throttling feature provides a dynamic mechanism to slow down link-state advertisement updates in OSPFv3 during times of network instability.
The following sections provide information about this feature:
•
Fast Convergence—LSA and SPF Throttling
•
Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
•
Enabling Event Logging for LSA and SPF Rate Limiting
•
Clearing the Content of an Event Log
•
Example: Configuring LSA and SPF Throttling for OSPFv3 Fast Convergence
The following commands were modified by this feature: clear ipv6 ospf events, event-log, ipv6 router ospf, show ipv6 ospf event, timers lsa arrival, timers pacing flood, timers throttle lsa, timers throttle spf
IPv6 Routing—LSA Types in OSPFv3
Cisco IOS XE Release 2.1
A router's collection of LSA data is stored in a link-state database. The contents of the database, when subjected to the Dijkstra algorithm, result in the creation of the OSPFv3 routing table.
The following sections provide information about this feature:
IPv6 Routing—OSPF for IPv6 (OSPFv3)
Cisco IOS XE Release 2.1
OSPF version 3 for IPv6 expands on OSPF version 2 to provide support for IPv6 routing prefixes and the larger size of IPv6 addresses.
This entire document provides information about this feature.
The following commands were modified by this feature: area range, clear ipv6 ospf, ipv6 ospf area, ipv6 router ospf, show ipv6 ospf, show ipv6 ospf interface
OSPFv3 Address Families
Cisco IOS XE Release 3.4S
The OSPFv3 address families feature enables IPv4 and IPv6 unicast traffic to be supported with a single network topology.
The following sections provide information about this feature:
•
Configuring the OSPFv3 Router Process
•
Configuring the IPv6 Address Family in OSPFv3
OSPFv3 External Path Preference Option
Cisco IOS XE Release 3.4S
This feature is provides a way to calculate external path preferences per RFC 5340.
The following sections provide information about this feature:
•
OSPFv3 External Path Preference Option
OSPFv3 Graceful Restart
Cisco IOS XE Release 2.1
The graceful restart feature in OSPFv3 allows nonstop data forwarding along routes that are already known while the OSPFv3 routing protocol information is being restored.
The following sections provide information about this feature:
•
Enabling OSPFv3 Graceful Restart
The following commands were modified by this feature: graceful-restart, graceful-restart helper, ipv6 router ospf, show ipv6 ospf graceful-restart
OSPFv3 Max-Metric Router LSA
Cisco IOS XE Release 3.4S
The OSPFv3 max-mtric router LSA feature enables OSPF to advertise its locally generated router LSAs with a maximum metric.
The following sections provide information about this feature:
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2003-2011 Cisco Systems, Inc. All rights reserved.
Feedback
