OSPFv3 Commands on Cisco IOS XR Software
Available Languages
Table Of Contents
OSPFv3 Commands on Cisco IOS XR Software
database-filter all out (OSPFv3)
default-information originate (OSPFv3)
distribute-list prefix-list in
distribute-list prefix-list out
log adjacency changes (OSPFv3)
maximum redistributed-prefixes (OSPFv3)
show ospfv3 retransmission-list
timers throttle lsa all (OSPFv3)
OSPFv3 Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor the IP Version 6 (IPv6) Open Shortest Path First Version 3 (OSPFv3) routing protocol.
For detailed information about OSPFv3 concepts, configuration tasks, and examples, refer to the Implementing OSPF on Cisco IOS XR Software configuration guide.
address-family (OSPFv3)
To enter address family configuration mode for Open Shortest Path First Version 3 (OSPFv3), use the address-family command in the router ospv3 configuration mode. To disable address family configuration mode, use the no form of this command.
address-family ipv6 [unicast]
no address-family ipv6 [unicast]
Syntax Description
ipv6
Specifies IP Version 6 (IPv6) address prefixes.
unicast
(Optional) Specifies unicast address prefixes.
Defaults
An address family is not specified.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure the OSPFv3 router process with IPv6 unicast address prefixes:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# address-family ipv6 unicastarea (OSPFv3)
To configure an Open Shortest Path First Version 3 (OSPFv3) area, use the area command in router ospfv3 configuration mode. To remove an OSPFv3 area, use the no form of this command.
area area-id
no area area-id
Syntax Description
area-id
Identifier of an OSPFv3 area. The area-id argument can be specified as either a decimal value or as an IPv4 address.
Defaults
No OSPFv3 areas are defined.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
An area must be explicitly configured with the area command.
Use the area command to place the router in area configuration mode (prompt: config-router-ar), from which you can configure area-specific settings. Commands configured under this mode (such as the interface command) are automatically bound to that area.
Note
To remove the specified OSPFv3 area from the router ospfv3 configuration, use the no area area-id command. The no area area-id command removes the OSPFv3 area including all OSPFv3 area options, and all the OSPFv3 interfaces and interface options that are configured under the area.
Task ID
Examples
The following example shows how to configure area 0 for OSPFv3 process 1. The Packet-over-SONET/SDH (POS) 0/1/0/1 interface also is configured:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/1/0/1authentication (OSPFv3)
To enable plain text, Message Digest 5 (MD5) authentication, or null authentication for an Open Shortest Path First Version 3 (OSPFv3) interface, use the authentication command in the appropriate mode. To remove such authentication, use the no form of this command.
authentication {ipsec spi spi-value {md5 | sha1} [clear | password] password | disable}
no authentication
Syntax Description
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the authentication parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the authentication parameter specified for the process.
If this command is not specified at any level, then the interface does not use authentication.Command Modes
Interface configuration
Area configuration
Router configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the authentication command to specify an authentication type for the interface, which overrides the authentication specified for the area to which this interface belongs. If this command is not included in the configuration file, the authentication configured in the area to which the interface belongs is assumed (as specified by the area authentication command).
The authentication type and password must be the same for all OSPFv3 interfaces that are to communicate with each other through OSPFv3.
Task ID
Examples
The following example shows how to enable MD5 authentication:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# router-id 10.1.1.1RP/0/RP0/CPU0:router(config-ospfv3)# authentication ipsec spi 500 md5 1234567890abcdef1234567890abcdefauto-cost (OSPFv3)
To control how the Open Shortest Path First Version 3 (OSPFv3) protocol calculates default metrics for an interface, use the auto-cost command in router ospfv3 configuration mode. To set link cost based only on the interface type, use the disable form of this command. To re-enable OSPFv3 metric calculation for an interface according to the bandwidth of the interface, use the no form of this command.
auto-cost [reference-bandwidth mbps | disable]
no auto-cost [reference-bandwidth mbps | disable]
Syntax Description
reference-bandwidth mbps
(Optional) Sets the rate in Mbps (bandwidth). Range is 1 to 4294967.
disable
(Optional) Sets the link cost based only on the interface type.
Defaults
mbps: 100 Mbps
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs.. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
By default OSPFv3 calculates the OSPFv3 metric for an interface according to the bandwidth of the interface.
The no auto-cost disable form of this command reenables OSPFv3 metric calculation for an interface according to the bandwidth of the interface.
To set link cost based only on the interface type, use the disable keyword.
If you have multiple links with high bandwidth, you might want to use a larger number to differentiate the cost on those links.
Recommended usage of cost configuration for all OSPFv3 configured interfaces is to be consistent: Either explicitly configure link costs (by using the cost command) or choose an appropriate default (by using the auto-cost command).
The value set by the cost command overrides the cost resulting from the auto-cost command.
Task ID
Examples
The following example shows how to set the reference value for the auto cost to 64:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# auto-cost reference-bandwidth 64Related Commands
Explicitly specifies the cost of the interface (network) for OSPF path calculation.
clear ospfv3 process
To reset an Open Shortest Path First Version 3 (OSPFv3) router process without removing and reconfiguring it, use the clear ospfv3 process command in EXEC mode.
clear ospfv3 [process-name] process
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When the OSPFv3 router process is reset, OSPFv3 releases all resources allocated, cleans up the internal database, uninstalls routes, and resets all OSPFv3 adjacencies.
Note
Task ID
Examples
The following example shows how to reset all OSPFv3 processes:
RP/0/RP0/CPU0:router# clear ospfv3 processThe following example shows how to reset the OSPFv3 process 1:
RP/0/RP0/CPU0:router# clear ospfv3 1 processRelated Commands
clear ospfv3 redistribution
To flush all the Type 5 and Type 7 link-state advertisements (LSAs) originated by an Open Shortest Path First Version 3 (OSPFv3) process, use the clear ospfv3 redistribution command in EXEC mode.
clear ospfv3 [process-name] redistribution
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear ospfv3 redistribution command to cause the routing table to be read again. OSPFv3 regenerates and sends Type 5 and Type 7 link-state advertisements (LSAs) to its neighbors. If an unexpected route has appeared in the OSPFv3 redistribution, using this command corrects the issue.
Note
Task ID
Examples
The following example shows how to clear all OSPFv3 redistributed routes from other protocols:
RP/0/RP0/CPU0:router# clear ospfv3 redistributionclear ospfv3 routes
To clear the Open Shortest Path First Version 3 (OSPFv3) internal route table, use the clear ospfv3 routes command in EXEC mode.
clear ospfv3 [process-name] routes
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear ospfv3 routes command to force the internal route table to be repopulated by causing recalculation of the shortest path first (SPF) routing table. When the OSPFv3 routing table is cleared, OSPFv3 routes in the global routing table are also recalculated.
Task ID
Examples
The following example shows how to clear all OSPFv3 routes from the OSPFv3 routing table and recomputes valid routes:
RP/0/RP0/CPU0:router# clear ospfv3 routesclear ospfv3 statistics
To clear the Open Shortest Path First Version 3 (OSPFv3) statistical counters, use the clear ospfv3 statistics command in EXEC mode.
clear ospfv3 [process-name] statistics [neighbor [interface-type interface-instance] [router-id]]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear ospfv3 statistics command to reset statistics so that subsequent changes are easily observed.
Task ID
Examples
The following example shows how to clear the OSPFv3 statistical counters of all neighbors on Packet-over-SONET/SDH (POS) interface 0/2/0/0:
RP/0/RP0/CPU0:router# clear ospfv3 statistics neighbor POS 0/2/0/0cost (OSPFv3)
To explicitly specify the cost of the interface (network) for OSPF path calculations, use the cost command in the appropriate mode. To remove the cost, use the no form of this command.
cost cost
no cost
Syntax Description
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the cost parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the cost parameter specified for the process.
If this command is not specified at any level, then the cost is based on the interface bandwidth, as specified by the auto-cost command.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The link-state metric is advertised as the link cost in the router link advertisement.
In general, the path cost is calculated using the following formula:
10^8 / bandwidth
Using this formula, the default path cost is 1 for OC-3 Packet-over-SONET/SDH (POS). If this value does not suit your network, you can use your own method of calculating path costs.
The value set by the cost command overrides the cost resulting from the auto-cost command.
Task ID
Examples
The following example shows how to set the cost value to 65 for Packet-over-SONET/SDH (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/1/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# cost 65Related Commands
database-filter all out (OSPFv3)
To filter outgoing link-state advertisements (LSAs) to an Open Shortest Path First Version 3 (OSPFv3) interface, use the database-filter command in the appropriate mode. To restore the forwarding of LSAs to the interface, use the no form of this command.
database-filter all out
no database-filter all out
Syntax Description
This command has no arguments or keywords.
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the database filter parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the database filter parameter specified for the process.
If this command is not specified in router ospfv3 configuration mode, then the database filter is disabled and all outgoing LSAs are flooded to the interface.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the database-filter all out command to perform the same function that the neighbor command (with the database-filter keyword) performs on a neighbor basis.
Task ID
Examples
The following example shows how to prevent flooding of OSPFv3 LSAs to neighbors reachable through Packet-over-SONET/SDH (POS) interface 0/2/0/3:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/3RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# database-filter all outRelated Commands
dead-interval (OSPFv3)
To set the interval after which a neighbor is declared dead when no hello packets are observed, use the dead-interval command in the appropriate mode. To return to the default time, use the no form of this command.
dead-interval seconds
no dead-interval
Syntax Description
seconds
Unsigned integer that specifies the interval (in seconds). The value must be the same for all nodes on the same network link. Range is 1 to 65535.
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the dead interval parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the dead interval parameter specified for the process.
If this command is not specified in router ospfv3 configuration mode, then the dead interval is four times the interval set by the hello-interval (OSPFv3) command.Command Modes
Interface configuration
Area configuration
Router ospfv3 configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Two Open Shortest Path First Version 3 (OSPFv3) routers do not become adjacent if their dead interval values differ.
If the hello interval is configured, the dead interval value must be larger than the hello interval value. The dead interval value is usually configured four times larger than the hello interval value.
Task ID
Examples
The following example shows how to set the OSPFv3 dead interval on Packet-over-SONET/SDH (POS) interface 0/2/0/3 to 40 seconds:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/3RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# dead-interval 40Related Commands
Specifies the interval between hello packets that the Cisco IOS XR software sends on the interface.
default-cost (OSPFv3)
To specify a cost for the default summary route sent into a stub area or not-so-stubby area (NSSA) for Open Shortest Path First Version 3 (OSPFv3) packets, use the default-cost command in area configuration mode. To remove the assigned default route cost, use the no form of this command.
default-cost cost
no default-cost cost
Syntax Description
cost
Cost for the default summary route used for a stub or NSSA area. The acceptable value is a 24-bit number.
Defaults
cost: 1
Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the default-cost command only on an Area Border Router (ABR) attached to a stub or an NSSA area.
In all routers and access servers attached to the stub area, the area should be configured as a stub area using the stub (OSPFv3) command in the area configuration submode. Use the default-cost command only on an ABR attached to the stub area. The default-cost command provides the metric for the summary default route generated by the ABR into the stub area.
Task ID
Examples
The following example shows how to assign a cost of 20 to the default route sent into area 10.15.0.0:
RP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# area 10.15.0.0RP/0/RP0/CPU0:router(config-ospfv3-ar)# stubRP/0/RP0/CPU0:router(config-ospfv3-ar)# default-cost 20RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface pos0/3/0/1Related Commands
default-information originate (OSPFv3)
To generate a default external route into an Open Shortest Path First Version 3 (OSPFv3) routing domain, use the default-information originate command in router ospfv3 configuration mode. To disable this feature, use the no form of this command.
default-information originate [route-policy policy-name] [always] [metric metric-value] [metric-type type-value] [tag tag-value]
no default-information originate [route-policy policy-name] [always] [metric metric-value] [metric-type type-value] [tag tag-value]
Syntax Description
Defaults
A default external route into an OSPFv3 routing domain is not generated.
metric-value: 10
type-value: Type 2Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Whenever you use the redistribute or default-information command to redistribute routes into an OSPFv3 routing domain, the software automatically becomes an ASBR. However, an ASBR does not, by default, generate a default route into the OSPFv3 routing domain. The software still must have a default route for itself before it generates one, except when you have specified the always keyword.
When you use the default-information originate command for the OSPFv3 process, the default network must reside in the routing table.
Task ID
Examples
The following example shows how to specify a metric of 100 for the default route redistributed into the OSPFv3 routing domain and an external metric type of Type 1:
RP/0/RP0/CPU0:router(config)# router ospfv3 109RP/0/RP0/CPU0:router(config-ospfv3)# default-information originate metric 100 metric-type 1Related Commands
default-metric (OSPFv3)
To set default metric values for routes redistributed from another protocol into Open Shortest Path First Version 3 (OSPFv3), use the default-metric command in router ospfv3 configuration mode. To return to the default state, use the no form of this command.
default-metric value
no default-metric value
Syntax Description
Defaults
Built-in, automatic metric translations, as appropriate for each routing protocol
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the default-metric command with the redistribute command to cause the current routing protocol to use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, use a default metric to provide a reasonable substitute and enable the redistribution to proceed.
Task ID
Examples
The following example shows how to configure a router with both the Intermediate System-to-Intermediate System (IS-IS) and the OSPFv3 routing protocols. The OSPFv3 routing protocol advertises IS-IS derived routes and assigns the routes a metric of 10:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# default-metric 10RP/0/RP0/CPU0:router(config-ospfv3)# redistribute isis 109Related Commands
demand-circuit (OSPFv3)
To configure the Open Shortest Path First Version 3 (OSPFv3) router process to treat the interface as an OSPFv3 demand circuit, use the demand-circuit command in the appropriate mode. To remove the demand circuit designation from the interface, use the no form of this command.
demand-circuit [disable]
no demand-circuit
Syntax Description
disable
(Optional) Disables the demand circuit configuration that may have been specified at a higher level in the configuration.
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the demand circuit parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the demand circuit parameter specified for the process.
If this command is not specified at any level, then the interface is not a demand circuit.Command Modes
Interface configuration
Area configuration
Router ospfv3 configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
On point-to-point interfaces, only one end of the demand circuit must be configured with the demand-circuit command. Periodic hello messages are suppressed and periodic refreshes of link-state advertisements (LSAs) do not flood the demand circuit. This command allows the underlying data link layer to be closed when the topology is stable. In point-to-multipoint topology, only the multipoint end must be configured with this command.
Task ID
Examples
The following example shows how to configure Packet-over-SONET/SDH (POS) interface 0/3/0/1 as an on-demand circuit:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3)# interface POS 0/3/0/1RP/0/RP0/CPU0:router(config-ospfv3-if)# demand-circuitdistance ospfv3
To define the Open Shortest Path First Version 3 (OSPFv3) route administrative distances based on route type, use the distance ospfv3 command in router ospfv3 configuration mode. To restore the default value, use the no form of this command.
distance ospfv3 {[intra-area] [inter-area] [external]} distance
no distance ospfv3
Syntax Description
Defaults
distance: 110
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You must specify one of the keywords.
Use the distance ospfv3 command to perform the same function as the distance command used with an access list. However, the distance ospfv3 command sets a distance for an entire group of routes, rather than a specific route that passes an access list.
A common reason to use the distance ospfv3 command is when you have multiple OSPFv3 processes with mutual redistribution, and you want to prefer internal routes from one over external routes from the other.
Task ID
Examples
The following example shows how to change the external distance to 200, making it less reliable:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# redistribute ospfv3 2RP/0/RP0/CPU0:router(config-ospfv3)# distance ospfv3 external 200RP/0/RP0/CPU0:router(config-ospfv3)# exitRP/0/RP0/CPU0:router(config)# router ospfv3 2RP/0/RP0/CPU0:router(config-ospfv3)# redistribute ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# distance ospfv3 external 200Related Commands
distribute-list prefix-list in
To filter the routes that Open Shortest Path First Version 3 (OSPFv3) installs in the Routing Information Base (RIB), use the distribute-list prefix-list in command in the appropriate mode. To remove the filter, use the no form of this command.
distribute-list prefix-list prefix-list-name in
no distribute-list prefix-list prefix-list-name in
Syntax Description
prefix-list-name
IP Version 6 (IPv6) prefix list name. The list defines which IPv6 prefixes are installed in the RIB.
Defaults
All routes learned by OSPFv3 are installed in the RIB.
Command Modes
Interface configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the distribute-list prefix-list command to limit the routes that OSPFv3 installs in the RIB of your router. This command does not affect the information sent to other OSPFv3 routers or the routes that these routers compute and install.
Note
When this command is specified in router ospfv3 configuration mode, the filter applies to all routes computed by OSPFv3.
When this command is specified in interface configuration mode, the filter applies only to routes that forward outgoing traffic over that interface.
Task ID
Examples
The following example shows how to prevent OSPFv3 from installing any routes that have 2001:e624 as the first 32 bits of the address. OSPFv3 is also prevented from installing routes to 2002::/16 that use Packet-over-SONET/SDH (POS) interface 0/2/0/0 as the next-hop interface:
RP/0/RP0/CPU0:router(config)# ipv6 prefix-list preflist1RP/0/RP0/CPU0:router(config-ipv6-pfx)# deny 2001:e624::/32 le 128RP/0/RP0/CPU0:router(config-ipv6-pfx)# permit ::/0 le 128!RP/0/RP0/CPU0:router(config)# ipv6 prefix-list preflist2RP/0/RP0/CPU0:router(config-ipv6-pfx)# deny 2002::/16RP/0/RP0/CPU0:router(config-ipv6-pfx)# permit ::/0 le 128!RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# distribute-list prefix-list preflist1 inRP/0/RP0/CPU0:router(config-ospfv3)# area 1RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# distribute-list prefix-list preflist2 in!distribute-list prefix-list out
To filter the routes redistributed into Open Shortest Path First Version 3 (OSPFv3) from other routing protocols, use the distribute-list prefix-list out command in router ospfv3 configuration mode. To remove the filter, use the no form of this command.
distribute-list prefix-list prefix-list-name out [protocol [process-id]]
no distribute-list prefix-list prefix-list-name out [protocol [process-id]]
Syntax Description
Defaults
All routes from protocols specified in the redistribute (OSPFv3) command are redistributed into OSPFv3.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Routes may be redistributed into OSPFv3 from several other routing protocols or from other OSPFv3 processes. These routes are then communicated to other OSPFv3 routes through Type 5 (External) or Type 7 not-so-stubby area (NSSA) link-state advertisements (LSAs). Use the distribute-list prefix-list out command to control redistribution by matching redistributed routes against an IPv6 prefix list. Only routes permitted by the prefix list are redistributed into OSPFv3.
Each protocol being redistributed into OSPFv3 may have a separate prefix list. In addition, a prefix list can be defined that applies to all protocols.
Task ID
Examples
The following example shows how to prevent OSPFv3 from redistributing routes that have 2001:e624 as the first 32 bits of the address. In addition, routes with a prefix beginning with 2064 are not redistributed from Border Gateway Protocol (BGP) autonomous system 1, and only those routes are redistributed from BGP autonomous system 5.
RP/0/RP0/CPU0:router(config)# ipv6 prefix-list p1RP/0/RP0/CPU0:router(config-ipv6-pfx)# deny 2001:e624::/32 le 128RP/0/RP0/CPU0:router(config-ipv6-pfx)# permit ::/0 le 128!RP/0/RP0/CPU0:router(config)# ipv6 prefix-list p2RP/0/RP0/CPU0:router(config-ipv6-pfx)# deny 2064::/16 le 128RP/0/RP0/CPU0:router(config-ipv6-pfx)# permit ::/0 le 128!RP/0/RP0/CPU0:router(config)# ipv6 prefix-list p3RP/0/RP0/CPU0:router(config-ipv6-pfx)# permit 2064::/16 le 128!RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# redistribute bgp 1RP/0/RP0/CPU0:router(config-ospfv3)# redistribute bgp 5RP/0/RP0/CPU0:router(config-ospfv3)# distribute-list prefix-list p1 outRP/0/RP0/CPU0:router(config-ospfv3)# distribute-list prefix-list p2 out bgp 1RP/0/RP0/CPU0:router(config-ospfv3)# distribute-list prefix-list p3 out bgp 5!!Related Commands
Redistributes routes from one routing domain into another routing domain for OSPFv3.
encryption
To encrypt and authenticate Open Shortest Path First Version 3 (OSPFv3) packets, use the encryption command in the appropriate mode. To remove the encryption, use the no form of this command.
encryption {disable | ipsec spi security-parameter esp {3des | aes [192 | 256] | des | null authentication {md5 | sha1}} {clear | password} password
no encryption
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Router ospfv3 configurationCommand History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the encryption command to encrypt and authenticate OSPFv3 packets.
Task ID
Examples
The following example shows how to encrypt and authenticate OSPFv3 packets:
RP/0/0/CPU0:router(config)#router ospfv3 1RP/0/0/CPU0:ospf-3-1(config-ospfv3)#encryption ipsec spi 256 esp 3des clear CAFECAFECAFECAFECAFECAFECAFECAFECAFECAFECAFECAFEflood-reduction (OSPFv3)
To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the flood-reduction command in the appropriate mode. To disable this feature, use the no form of this command.
flood-reduction [disable]
no flood-reduction
Syntax Description
disable
(Optional) Turns off this functionality at a specific level.
Note
Command Default
If this command is not specified in interface configuration mode, then the interface adopts the flood reduction parameter specified by area.
If this command is not specified in area configuration mode, then the interface adopts the flood reduction parameter specified for the process.
If this command is not specified at any level, then flood reduction is disabled.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
All routers that support Open Shortest Path First Version 3 (OSPFv3) demand circuits are compatible with routers supporting flooding reduction.
Task ID
Examples
The following example shows how to reduce the flooding of unnecessary LSAs for area 0:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/1/0/3RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# flood-reductionRelated Commands
Displays OSPFv3-related interface information.
Displays OSPFv3 neighbor information on an individual interface basis.
graceful-restart (OSPFv3)
To enable graceful restart, use the graceful-restart command in router ospfv3 configuration mode. To disable this feature, use the no form of this command.
graceful-restart [helper disable | interval interval | lifetime lifetime]
no graceful-restart [helper disable | interval interval | lifetime lifetime]
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to enable the Graceful Restart feature with a minimum interval between restarts of 300 seconds:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# graceful-restart interval 300Related Commands
Displays OSPFv3-related interface information.
Displays OSPFv3 neighbor information on an individual interface basis.
hello-interval (OSPFv3)
To specify the interval between hello packets that Open Shortest Path First Version 3 (OSPFv3) sends on an interface, use the hello-interval command in the appropriate mode. To return to the default time, use the no form of this command.
hello-interval seconds
no hello-interval
Syntax Description
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the hello interval parameter specified by area.
If this command is not specified in area configuration mode, then the interface adopts the hello interval parameter specified for the process.
If this command is not specified at any level, then the hello interval is 10 seconds (broadcast) or 30 seconds (nonbroadcast).Command Modes
Interface configuration
Area configuration
Router ospfv3 configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The hello interval value is advertised in the hello packets. The shorter the hello interval, the faster topological changes are detected, but more routing traffic ensues. This value must be the same for all routers and access servers on a specific network.
Task ID
Examples
The following example shows how to set the interval between hello packets to 15 seconds on Packet-over-SONET/SDH (POS) interface 0/3/0/2:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/2RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# hello-interval 15Related Commands
Sets the interval after which a neighbor is declared dead when no hello packets are observed
instance
To set the 8-bit instance ID used in Open Shortest Path First Version 3 (OSPFv3) packets sent on an interface, use the instance command in the appropriate mode. To remove the instance ID, use the no form of this command.
instance instance-id
no instance instance-id
Syntax Description
instance-id
Instance identifier sent in OSPFv3 packets. Range is 0 to 255. The same value must be used by all the communicating OSPFv3 routers on a link.
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the instance parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the instance parameter specified for the process.
If this command is not specified at any level, then the instance is 0.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The OSPFv3 routing protocol allows multiple unrelated OSPFv3 processes to share a link by using an 8-bit "instance" value to demultiplex the protocol packets. Each OSPFv3 process sets its configured instance value in the OSPFv3 packets that it sends, and ignores received packets with instance values from other OSPFv3 processes.
Note
Task ID
Examples
The following example shows how to set the instance value for Packet-over-SONET/SDH (POS) interface 0/3/0/1 to 42:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# instance 42Related Commands
Configures an OSPFv3 routing process.
Configures a router ID for the OSPFv3 routing process.
interface (OSPFv3)
To define the interfaces on which Open Shortest Path First Version 3 (OSPFv3) runs, use the interface command in area configuration mode. To disable OSPFv3 routing for an interface, use the no form of this command.
interface type instance
no interface type instance
Syntax Description
Defaults
An interface is not defined.
Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the interface command to associate a specific interface with an OSPFv3 area. The interface remains associated with the area even when the IPv6 address of the interface changes.
Similar to IPv4 behavior for the interface command, all configured IPv6 addresses are advertised on an interface after the interface is associated to the OSPF routing process. However, one difference is that IPv6 addresses can have multiple primary addresses.
This command places the router in interface configuration mode (prompt: config-router-ar-if), from which you can configure interface-specific settings. Commands configured under this mode (such as the cost command) are automatically bound to that interface.
Task ID
Examples
The following example shows how to define two interfaces that belong to area 1. The cost value for packets on Packet-over-SONET/SDH (POS) interface 0/3/0/1 is set at 40; the cost value for POS interface 0/3/0/2 is 65:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 1RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# cost 40RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitRP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/2RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# cost 65RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitlog adjacency changes (OSPFv3)
To change the default syslog messages for Open Shortest Path First Version 3 (OSPFv3) neighbor state changes, use the log adjacency changes command in router ospfv3 configuration mode. To suppress all adjacency change messages, use the disable keyword.
log adjacency changes [detail | disable]
Syntax Description
detail
(Optional) Provides all (DOWN, INIT, 2WAY, EXSTART, EXCHANGE, LOADING, FULL) adjacency state changes.
disable
(Optional) Disables the neighbor state change messages.
Defaults
Neighbor state change messages are enabled.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
By default, you are notified of OSPFv3 neighbor changes without explicitly configuring the log adjacency changes command. The syslog messages that are sent provide a high-level view of changes to the state of the OSPFv3 peer relationship.
Task ID
Examples
The following example shows how to disable neighbor state change messages:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# log adjacency changes disableThe following example shows how to re-enable syslog messages for any OSPFv3 neighbor state changes:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# log adjacency changesmaximum interfaces (OSPFv3)
To control the maximum number of interfaces that can be configured under an Open Shortest Path First Version 3 (OSPFv3) process, use the maximum interfaces command in the router ospfv3 configuration mode. To remove the maximum interfaces command from the configuration file and restore the system to its default condition with respect to the routing protocol, use the no form of this command.
maximum interfaces value
no maximum interfaces
Syntax Description
value
Maximum number of interfaces that can be configured for this OSPFv3 process. Range is 1 to 1024.
Defaults
value: 255 interfaces
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to allow a maximum of 500 interfaces in an OSPFv3 process:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# maximum interfaces 500maximum paths (OSPFv3)
To control the maximum number of parallel routes that the Open Shortest Path First Version 3 (OSPFv3) can support, use the maximum paths command in router ospfv3 configuration mode. To remove the maximum paths command from the configuration file and restore the system to its default condition with respect to the routing protocol, use the no form of this command.
maximum paths routes-number
no maximum paths
Syntax Description
routes-number
Maximum number of parallel routes that OSPFv3 can install in a routing table. Range is 1 to 32 for Cisco CRS-1s and 1 to 16 for Cisco XR 12000 Series Routers.
Defaults
Cisco CRS-1: 16 paths
Cisco XR 12000 Series Router: 16 pathsCommand Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to allow a maximum of two paths to a destination:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# maximum paths 2maximum redistributed-prefixes (OSPFv3)
To limit the number of prefixes redistributed into Open Shortest Path First Version 3 (OSPFv3) or to generate a warning when the number of prefixes redistributed into OSPFv3 reaches a maximum, use the maximum redistributed-prefixes command in router ospfv3 configuration mode. To remove the values, use the no form of this command.
maximum redistributed-prefixes limit [threshold] [warning-only]
no maximum redistributed-prefixes
Syntax Description
Defaults
limit: 10240
threshold: 75 percentCommand Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If someone mistakenly injects a large number of IPv6 routes into OSPFv3, perhaps by redistributing Border Gateway Protocol (BGP) into OSPFv3, the network can be severely flooded. Limiting the number of redistributed routes prevents this potential problem.
When the maximum redistributed-prefixes command is configured, if the number of redistributed routes reaches the maximum value configured, no more routes are redistributed (unless the warning-only keyword is configured).
The redistribution limit applies only to external IPv6 prefixes. Default routes and summarized routes are not limited.
The limit is tracked separately for each not-so-stubby-area (NSSA) because redistribution to NSSAs is done independently for each NSSA and independently of all other regular areas.
Select a maximum value based on your knowledge of how many prefixes are redistributed on the router to the OSPFv3 process.
Task ID
Examples
This example shows how to set a maximum of 2000 prefixes that can be redistributed into OSPFv3 process 1. If the number of prefixes redistributed reaches 75 percent of 2000 (1500 prefixes), a warning message is logged. Another warning is logged if the limit is reached and no more routes are redistributed.
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# redistribute bgp 2406RP/0/RP0/CPU0:router(config-ospfv3)# maximum redistributed-prefixes 2000mtu-ignore (OSPFv3)
To prevent the Open Shortest Path First Version 3 (OSPFv3) router process from checking whether neighbors are using the same maximum transmission unit (MTU) on a common interface when exchanging database descriptor (DBD) packets, use the mtu-ignore command in the appropriate mode. To return to the default state, use the no form of this command.
mtu-ignore [disable]
no mtu-ignore
Syntax Description
disable
(Optional) Disables the attribute in instances in which it is specified at a higher level in the configuration.
Note
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the MTU ignore parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the MTU ignore parameter specified for the process.
If this command is not specified at any level, then OSPFv3 checks the MTU received from neighbors when exchanging DBD packets.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the mtu-ignore command to check whether OSPFv3 neighbors are using the same MTU on a common interface. This check is performed when neighbors exchange DBD packets. If the receiving MTU in the DBD packet is higher than the MTU configured on the incoming interface, OSPF adjacency is not established.
Task ID
Examples
The following example shows how to disable MTU mismatch detection on received DBD packets on Packet-over-SONET/SDH (POS) interface 0/1/0/3:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/1/0/3RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# mtu-ignoreneighbor (OSPFv3)
To configure Open Shortest Path First Version 3 (OSPFv3) routers interconnecting to nonbroadcast networks, use the neighbor command in interface configuration mode. To remove a configuration, use the no form of this command.
neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out]
no neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out]
Syntax Description
Defaults
No configuration is specified.
priority number: 0
poll-interval seconds: 120 seconds (2 minutes)Command Modes
Interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
One neighbor entry must be included in the software configuration for each known nonbroadcast network neighbor. The neighbor address must be the IPv6 link-local address of the interface.
If a neighboring router has become inactive (hello packets have not been seen for the router dead interval period), it may still be necessary to send hello packets to the dead neighbor. These hello packets are sent at a reduced rate called the poll interval.
When the router starts up, it sends only hello packets to those routers with nonzero priority; that is, routers that are eligible to become designated routers (DRs) and backup designated routers (BDRs). After the DR and BDR are selected, the DR and BDR then start sending hello packets to all neighbors to form adjacencies.
Task ID
Examples
The following example shows how to declare a router at address fe80::3203:a0ff:fe9d:f3fe on a nonbroadcast network:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar)# network non-broadcastRP/0/RP0/CPU0:router(config-ospfv3-ar-if)# neighbor fe80::3203:a0ff:fe9d:f3feRelated Commands
Sets the router priority, which helps determine the designated router for this network.
network (OSPFv3)
To configure the Open Shortest Path First Version 3 (OSPFv3) network type to a type other than the default for a given medium, use the network command in the appropriate mode. To return to the default value, use the no form of this command.
network {broadcast | non-broadcast | {point-to-multipoint [non-broadcast] | point-to-point}}
no network
Syntax Description
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the network parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the network parameter specified for the process.
If this command is not specified at any level, then the OSPFv3 network type is the default of the given medium.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the network command to configure broadcast networks as NBMA networks when, for example, routers in your network do not support multicast addressing.
Configuring NBMA networks as either broadcast or nonbroadcast assumes that there are virtual circuits from every router to every router or fully meshed network. However, there are other configurations where this assumption is not true; for example, a partially meshed network. In these cases, you can configure the OSPFv3 network type as a point-to-multipoint network. Routing between two routers that are not directly connected goes through the router that has virtual circuits to both routers. You need not configure neighbors when using this command.
If the network command is issued on an interface that does not allow it, this command is ignored.
OSPFv3 has two features related to point-to-multipoint networks. One feature applies to broadcast networks and the other feature applies to nonbroadcast networks:
•
•
Task ID
Examples
The following example shows how to configure an Ethernet interface as point-to-point:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface TenGigE0/1/0/3RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# network point-to-pointRelated Commands
nssa (OSPFv3)
To configure an area as a not-so-stubby area (NSSA), use the nssa command in area configuration mode. To remove the NSSA distinction from the area, use the no form of this command.
nssa [no-redistribution] [default-information-originate [metric metric-value | metric-type type-value]] [no-summary]
no nssa
Syntax Description
Defaults
No NSSA area is defined.
If you do not specify a value using the default-metric command, the default metric value is 10.
The default type-value is Type 2 external route.Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
A default route need not be defined in an NSSA ABR when the nssa command is configured. However, if this command is configured on an NSSA ASBR, then a default route must be defined.
Note
Task ID
Examples
The following example shows how to configure area 1 as an NSSA area:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# router-id 10.18.1.1RP/0/RP0/CPU0:router(config-ospfv3)# area 1RP/0/RP0/CPU0:router(config-ospfv3-ar)# nssaospfv3 name-lookup
To configure Open Shortest Path First Version 3 (OSPFv3) to look up Domain Name System (DNS) names, use the ospfv3 name-lookup command in global configuration mode. To disable this function, use the no form of this command.
ospfv3 name-lookup
no ospfv3 name-lookup
Syntax Description
This command has no arguments or keywords.
Defaults
Routers are displayed by router ID or neighbor ID.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the ospfv3 name-lookup command to simplify the task of searching for a router. Routers are displayed by name rather than by router ID or neighbor ID.
Task ID
Examples
The following example shows how to configure OSPFv3 to look up DNS names for use in all OSPFv3 show command displays:
RP/0/RP0/CPU0:router(config)# ospfv3 name-lookuppacket-size
To configure the size of Open Shortest Path First Version 3 (OSPFv3) packets up to the size specified by the maximum transmission unit (MTU), use the packet-size command in the appropriate mode. To disable this function and reestablish the default packet size, use the no form of this command.
packet-size bytes
no packet-size
Syntax Description
Defaults
If not specified, the default packet size is 1500 bytes.
Command Modes
Router configuration
Area configuration
Interface configurationCommand History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the packet-size command to customize the size of OSPFv3 packets. The OSPFv3 protocol compares the packet size and the MTU size and uses the lower packet size value.
Task ID
Examples
The following example shows how to configure the packet size on an interface:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router ospf 1RP/0/RP0/CPU0:router(config-ospf)# area 0RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/2RP/0/RP0/CPU0:router(config-ospf-ar-if)# packet-size 3500passive (OSPFv3)
To suppress the sending of Open Shortest Path First Version 3 (OSPFv3) packets on an interface, use the passive command in the appropriate mode. To remove the passive configuration, use the no form of this command.
passive [disable]
no passive
Syntax Description
disable
(Optional) Sends OSPFv3 updates.
Note
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the passive parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the passive parameter specified for the process.
If this command is not specified at any level, then the passive parameter is disabled and OSPFv3 updates are sent on the interface.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
OSPF routing information is neither sent nor received through the specified router interface. The specified interface address appears as a stub network in the OSPF domain.
Task ID
Examples
The following example shows that OSPFv3 updates run over Packet-over-SONET/SDH (POS) interface 0/3/0/0, 0/2/0/0, and 0/2/0/2. All other interfaces suppress sending OSPFv3 updates because they are in passive mode.
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# router-id 10.0.0.206RP/0/RP0/CPU0:router(config-ospfv3)# passiveRP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# passive disableRP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitRP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitRP/0/RP0/CPU0:router(config-ospfv3-ar)# exitRP/0/RP0/CPU0:router(config-ospfv3)# area 1RP/0/RP0/CPU0:router(config-ospfv3-ar)# passive disableRP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitRP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# passiveRP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitRP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/2RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# exitpriority (OSPFv3)
To set the router priority for an interface, which helps determine the designated router for an Open Shortest Path First Version 3 (OSPFv3) link, use the priority command in the appropriate mode. To return to the default value, use the no form of this command.
priority value
no priority
Syntax Description
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the priority parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the priority parameter specified by the process.
If this command is not specified at any level, then the default priority is 1.Command Modes
Interface configuration
Area configuration
Router ospfv3 configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When two routers attached to a network both attempt to become the designated router, the one with the higher router priority takes precedence. If there is a tie, the router with the higher router ID takes precedence. A router with a router priority set to zero is ineligible to become the designated router or backup designated router. Router priority is configured only for interfaces to broadcast and nonbroadcast multiaccess (NBMA) networks.
Task ID
Examples
The following example shows how to set the router priority value to 4 on Packet-over-SONET/SDH (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/1/0/1RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# priority 4Related Commands
Configures OSPFv3 routers interconnecting to nonbroadcast networks.
Configures the OSPFv3 network type to a type other than the default for a given medium.
range (OSPFv3)
To consolidate and summarize routes at an area boundary for Open Shortest Path First Version 3 (OSPFv3), use the range command in area configuration mode. To restore the default values, use the no form of this command.
range ipv6-prefix/prefix-length [advertise | not-advertise] [cost number]
no range ipv6-prefix/prefix-length [advertise | not-advertise] [cost number]
Syntax Description
Defaults
Routes are not consolidated and summarized for an area.
Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the range command only with Area Border Routers (ABRs). It is used to consolidate or summarize routes for an area. The result is that a single summary route is advertised to other areas by the ABR. Routing information is condensed at area boundaries. External to the area, a single route is advertised for each address range. This process is called route summarization.
You can use the range command to configure multiple ranges. Thus, OSPFv3 can summarize addresses for many different sets of address ranges.
Task ID
Examples
The following example shows how to specify one summary route to be advertised by the ABR to other areas for all IPv6 prefixes within the range defined by summary prefix 4004:f000::/32:
RP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# range 4004:f000::/32redistribute (OSPFv3)
To redistribute routes from one routing domain into Open Shortest Path First Version 3 (OSPFv3), use the redistribute command in router ospfv3 configuration mode. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
Border Gateway Protocol (BGP)
redistribute bgp process-id [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute bgp process-id [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Local Interface Routes
redistribute connected [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute connected [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Enhanced Interior Gateway Routing Protocol (EIGRP)
redistribute eigrp process-id [match {external [1 | 2] | internal}] [metric metric-value] [metric-type {1 | 2}] [route-policy policy-name] [tag tag-value]
no redistribute eigrp process-id [match {external [1 | 2] | internal}] [metric metric-value] [metric-type {1 | 2}] [route-policy policy-name] [tag tag-value]
Intermediate System-to-Intermediate System (IS-IS)
redistribute isis process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute isis process-id [level-1 | level-2 | level-1-2] [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Open Shortest Path First Version 3 (OSPFv3)
redistribute ospfv3 process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]}[metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute ospfv3 process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]}[metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Static
redistribute static [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute static [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Syntax Description
Defaults
Route redistribution is disabled.
metric metric-value: Default is 20 for routes from all protocols except BGP routes, in which the default is 1.
metric-type type-value: Type 2 external route
All routes from the OSPFv3 routing protocol are redistributed.
tag tag-value: If no value is specified, the remote autonomous system number is used for routes from Border Gateway Protocol (BGP); for other protocols, the default is 0.Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Disabling or changing the arguments of any keyword does not affect the state of other keywords.
In general, route redistribution from Level 1 to Level 2 is automatic. You might want to use this command to better control which Level 1 routes can be redistributed into Level 2.
Level 2 routes redistributed into Level 1 is called route leaking. Route leaking is disabled by default. That is, Level 2 routes are not automatically included in Level 1 link-state protocols. If you want to leak Level 2 routes into Level 1, you must enable that behavior by using this command.
Redistribution from Level 1 into Level 1 and from Level 2 into Level 2 is not allowed.
A router receiving a link-state packet with an internal metric considers the cost of the route from itself to the redistributing router plus the advertised cost to reach the destination. An external metric considers only the advertised metric to reach the destination.
Redistributed routing information should always be filtered by the distribute-list prefix-list out command. Use of this command ensures that only those routes intended by the administrator are passed along to the receiving routing protocol.
OSPFv3 Considerations
Whenever you use the redistribute or the default-information command to redistribute routes into an OSPFv3 routing domain, the router automatically becomes an ASBR. However, an ASBR does not, by default, generate a default route into the OSPFv3 routing domain.
When routes are redistributed between OSPFv3 processes, no OSPFv3 metrics are preserved.
When routes are redistributed into OSPF and no metric is specified with the metric keyword, OSPF uses 20 as the default metric for routes from all protocols except BGP routes, which get a metric of 1. Furthermore, when the router redistributes from one OSPFv3 process to another OSPFv3 process on the same router, and if no default metric is specified, the metrics in one process are carried to the redistributing process.
BGP Considerations
The only connected routes affected by this command are the routes not specified by the network (BGP) command.
Task ID
Examples
The following example shows how to cause static routes to be redistributed into an OSPFv3 domain:
RP/0/RP0/CPU0:router(config)# router ospfv3 109RP/0/RP0/CPU0:router(config-ospfv3)# redistribute isis level-1Related Commands
Redistributes routes into a routing domain.
Filters the routes redistributed into OSPFv3 from other routing protocols.
retransmit-interval (OSPFv3)
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the Open Shortest Path First Version 3 (OSPFv3) interface, use the retransmit-interval command in the appropriate mode. To return to the default value, use the no form of this command.
retransmit-interval seconds
no retransmit-interval
Syntax Description
seconds
Time (in seconds) between retransmissions. It must be greater than the expected round-trip delay between any two routers on the attached network. Range is 1 to 65535 seconds.
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the retransmit interval parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the retransmit interval parameter specified by the process.
If this command is not specified at any level, then the default retransmit interval is 5 seconds.Command Modes
Interface configuration
Area configuration
Router ospfv3 configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message. If the router receives no acknowledgment, it resends the LSA.
The setting of this parameter should be conservative, or needless retransmission results. The value should be larger for serial lines and virtual links.
Task ID
Examples
The following example shows how to set the retransmit interval value to 8 seconds while in interface configuration mode:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/2/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# retransmit-interval 8router-id (OSPFv3)
To configure a router ID for the Open Shortest Path First Version 3 (OSPFv3) routing process, use the router-id command in router ospfv3 configuration mode. To cause the software to use the default method of determining the router ID, use the no form of this command.
router-id {router-id}
no router-id {router-id}
Syntax Description
Defaults
If this command is not configured, the router ID is the highest IP address for an interface on the router, with any loopback interface taking precedence.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
We recommend that you use the router-id command to explicitly specify a unique 32-bit numeric value for the router ID. This configuration ensures that OSPFv3 can function regardless of the interface address configuration.
OSPF attempts to obtain a router ID in the following ways (in order of preference):
1.
2.
3.
4.
If the OSPFv3 process cannot obtain a router ID from any of these sources, the router issues the following error message:
%OSPFv3-4-NORTRID : OSPFv3 process 1 cannot run - configure a router ID for this processAt this point, OSPFv3 is effectively passive on all its interfaces. To run OSPFv3, make a router ID available by one of the methods described.
Task ID
Examples
The following example shows how to assign the IP address of 10.0.0.10 to the OSPFv3 process 109:
RP/0/RP0/CPU0:router(config)# router ospfv3 109RP/0/RP0/CPU0:router(config-ospfv3)# router-id 10.0.0.10Related Commands
router ospfv3
To configure an Open Shortest Path First Version 3 (OSPFv3) routing process, use the router ospfv3 command in global configuration mode. To terminate an OSPFv3 routing process, use the no form of this command.
router ospfv3 process-name
no router ospfv3 process-name
Syntax Description
process-name
Name that uniquely identifies an OSPFv3 routing process. The process name is any alphanumeric string no longer than 40 characters.
Defaults
No OSPFv3 routing process is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You can specify multiple OSPFv3 routing processes in each router.
Task ID
Examples
The following example shows how to instantiate an OSPFv3 routing process with a process name of 1:
RP/0/RP0/CPU0:router(config)# router ospfv3 1Related Commands
show ospfv3
To display general information about Open Shortest Path First Version 3 (OSPFv3) routing processes, use the show ospfv3 command in EXEC mode.
show ospfv3 [process-name]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following sample output from the show ospfv3 command:
RP/0/RP0/CPU0:router# show ospfv3 1Routing Process "ospfv3 test" with ID 3.3.3.3It is an autonomous system boundary routerRedistributing External Routes from,staticMaximum number of redistributed prefixes 10240Threshold for warning message 75%Initial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsInitial LSA throttle delay 0 msecsMinimum hold time for LSA throttle 5000 msecsMaximum wait time for LSA throttle 5000 msecsMinimum LSA arrival 1000 msecsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsMaximum number of configured interfaces 255Number of external LSA 1. Checksum Sum 0x004468Number of areas in this router is 1. 1 normal 0 stub 0 nssaArea BACKBONE(0) (Inactive)Number of interfaces in this area is 1SPF algorithm executed 1 timesNumber of LSA 3. Checksum Sum 0x018109Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Table 1 describes the significant fields shown in the display.
Related Commands
show ospfv3 border-routers
To display the internal Open Shortest Path First Version 3 (OSPFv3) routing table entries to an area border router (ABR) and autonomous system boundary router (ASBR), use the show ospfv3 border-routers command in EXEC mode.
show ospfv3 [process-name] border-routers [router-id]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show ospfv3 border-routers command:
RP/0/RP0/CPU0:router# show ospfv3 border-routersOSPFv3 1 Internal Routing TableCodes: i - Intra-area route, I - Inter-area routei 10.0.0.207 [1] via fe80::3034:30ff:fe33:3742, POS 0/3/0/0, ABR/ASBR, Area 1, SPF 3i 10.0.0.207 [10] via fe80::204:c0ff:fe22:73fe, Ethernet0/0/0/0, ABR/ASBR, Area 0, SPF 7Table 2 describes the significant fields shown in the display.
Related Commands
show ospfv3 database
To display lists of information related to the Open Shortest Path First Version 3 (OSPFv3) database for a specific router, use the show ospfv3 database command in EXEC mode.
show ospfv3 [process-name [area-id]] database
show ospfv3 [process-name [area-id]] database [adv-router [router-id]]]
show ospfv3 [process-name [area-id]] database [database-summary]
show ospfv3 [process-name [area-id]] database [external] [link-state-id]
show ospfv3 [process-name [area-id]] database [external] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [external] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [grace] [link-state-id] [adv-router [router-id]] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [inter-area prefix] [link-state-id]
show ospfv3 [process-name [area-id]] database [inter-area prefix] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [inter-area prefix] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [inter-area router] [link-state-id]
show ospfv3 [process-name [area-id]] database [inter-area router] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [inter-area router] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [link] [link-state-id]
show ospfv3 [process-name [area-id]] database [link] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [link] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [network] [link-state-id]
show ospfv3 [process-name [area-id]] database [network] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [network] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [nssa-external] [link-state-id]
show ospfv3 [process-name [area-id]] database [nssa-external] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [nssa-external] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [prefix] [ref-lsa] [router | network] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [prefix] [ref-lsa] [router | network] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [prefix] [link-state-id]
show ospfv3 [process-name [area-id]] database [prefix] [link-state-id] [internal] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [prefix] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [router] [link-state-id]
show ospfv3 [process-name [area-id]] database [router] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] database [router] [link-state-id] [internal] [self-originate]
show ospfv3 [process-name [area-id]] database [self-originate]
show ospfv3 [process-name [area-id]] database [unknown [area | as | link]] [link-state-id] [internal] [adv-router [router-id]] [self-originate]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The various forms of this command deliver information about different OSPFv3 link-state advertisements.
Task ID
Examples
The following is sample output from the show ospfv3 database command with no arguments or keywords:
RP/0/RP0/CPU0:router# show ospfv3 databaseOSPFv3 Router with ID (10.0.0.207) (Process ID 1)Router Link States (Area 0)ADV Router Age Seq# Fragment ID Link count Bits0.0.0.1 163 0x80000039 0 2 None10.0.0.206 145 0x80000005 0 1 EB10.0.0.207 151 0x80000004 0 1 EB192.168.0.0 163 0x80000039 0 1 NoneNet Link States (Area 0)ADV Router Age Seq# Link ID Rtr count10.0.0.207 152 0x80000002 1 3192.168.0.0 163 0x80000039 1 2Inter Area Prefix Link States (Area 0)ADV Router Age Seq# Prefix10.0.0.206 195 0x80000001 3002::/5610.0.0.207 197 0x80000001 3002::/5610.0.0.206 195 0x80000001 3002::206/12810.0.0.207 182 0x80000001 3002::206/128Inter Area Router Link States (Area 0)ADV Router Age Seq# Link ID Dest RtrID10.0.0.207 182 0x80000001 167772366 10.0.0.20610.0.0.206 182 0x80000001 167772367 10.0.0.207Link (Type-8) Link States (Area 0)ADV Router Age Seq# Link ID Interface0.0.0.1 163 0x80000039 1 Et0/0/0/010.0.0.207 202 0x80000001 1 Et0/0/0/010.0.0.206 200 0x80000001 2 Et0/0/0/0Intra Area Prefix Link States (Area 0)ADV Router Age Seq# Link ID Ref-lstype Ref-LSID192.168.0.0 163 0x80000039 0 0x2002 1192.168.0.0 163 0x80000039 1 0x2001 010.0.0.207 157 0x80000001 1001 0x2002 1Table 3 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the external keyword:
RP/0/RP0/CPU0:router# show ospfv3 database externalOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Type-5 AS External Link StatesLS age: 189LS Type: AS External LinkLink State ID: 0Advertising Router: 10.0.0.206LS Seq Number: 80000002Checksum: 0xa303Length: 36Prefix Address: 2222::Prefix Length: 56, Options: NoneMetric Type: 2 (Larger than any link state path)Metric: 20External Route Tag: 0Table 4 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the inter-area prefix keyword:
RP/0/RP0/CPU0:router# show ospfv3 database inter-area prefixOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Inter Area Prefix Link States (Area 0)LS age: 715LS Type: Inter Area Prefix LinksLink State ID: 0Advertising Router: 10.0.0.206LS Seq Number: 80000002Checksum: 0x3cb5Length: 36Metric: 1Prefix Address: 3002::Prefix Length: 56, Options: NoneTable 5 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the inter-area router keyword:
RP/0/RP0/CPU0:router# show ospfv3 database inter-area routerOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Inter Area Router Link States (Area 0)LS age: 1522Options: (V6-Bit E-Bit R-bit DC-Bit)LS Type: Inter Area Router LinksLink State ID: 167772366Advertising Router: 10.0.0.207LS Seq Number: 80000002Checksum: 0xcaaeLength: 32Metric: 1Destination Router ID: 10.0.0.206Table 6 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the link keyword:
RP/0/RP0/CPU0:router# show ospfv3 database linkOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Link (Type-8) Link States (Area 0)LS age: 620Options: (V6-Bit E-Bit R-bit DC-Bit)LS Type: Link-LSA (Interface: Ethernet0/0/0/0)Link State ID: 1 (Interface ID)Advertising Router: 10.0.0.207LS Seq Number: 80000003Checksum: 0x7235Length: 56Router Priority: 1Link Local Address: fe80::204:c0ff:fe22:73feNumber of Prefixes: 1Prefix Address: 7002::Prefix Length: 56, Options: NoneTable 7 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the network keyword:
RP/0/RP0/CPU0:router# show ospfv3 database networkOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Net Link States (Area 0)LS age: 1915Options: (V6-Bit E-Bit R-bit DC-Bit)LS Type: Network LinksLink State ID: 1 (Interface ID of Designated Router)Advertising Router: 10.0.0.207LS Seq Number: 80000004Checksum: 0x4330Length: 36Attached Router: 10.0.0.207Attached Router: 0.0.0.1Attached Router: 10.0.0.206Table 8 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the prefix keyword:
RP/0/RP0/CPU0:router# show ospfv3 database prefixOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Intra Area Prefix Link States (Area 1)Routing Bit Set on this LSALS age: 356LS Type: Intra-Area-Prefix-LSALink State ID: 0Advertising Router: 10.0.0.206LS Seq Number: 8000001eChecksum: 0xcdaaLength: 44Referenced LSA Type: 2001Referenced Link State ID: 0Referenced Advertising Router: 10.0.0.206Number of Prefixes: 1Prefix Address: 8006::Prefix Length: 56, Options: None, Metric: 1Table 9 describes the significant fields shown in the display.
The following is sample output from the show ospfv3 database command with the router keyword:
RP/0/RP0/CPU0:router# show ospfv3 database routerOSPFv3 Router with ID (10.0.0.206) (Process ID 1)Router Link States (Area 0)LS age: 814Options: (V6-Bit E-Bit R-bit)LS Type: Router LinksLink State ID: 0Advertising Router: 0.0.0.1LS Seq Number: 8000003cChecksum: 0x51caLength: 56Number of Links: 2Link connected to: a Transit NetworkLink Metric: 10Local Interface ID: 1Neighbor (DR) Interface ID: 1Neighbor (DR) Router ID: 10.0.0.207Link connected to: a Transit NetworkLink Metric: 10Local Interface ID: 2Neighbor (DR) Interface ID: 1Neighbor (DR) Router ID: 10.0.0.0Table 10 describes the significant fields shown in the display.
Related Commands
show ospfv3 flood-list
To display a list of Open Shortest Path First Version 3 (OSPFv3) link-state advertisements (LSAs) waiting to be flooded over an interface, use the show ospfv3 flood-list command in EXEC mode.
show ospfv3 [process-name] [area-id] flood-list [interface-type interface-instance]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show ospfv3 flood-list command to display OSPFv3 packet pacing.
Task ID
Examples
The following sample output from the show ospfv3 flood-list command shows three entries for the OSPFv3 1 process running over Packet-over-SONET/SDH (POS) interface 0/3/0/0:
RP/0/RP0/CPU0:router# show ospfv3 flood-list POS 0/3/0/0Flood Lists for OSPFv3 1Interface POS 0/3/0/0, Queue length 3Link state retransmission due in 24 msecDisplaying 3 entries from flood list:Type LS ID ADV RTR Seq NO Age Checksum3 0.0.0.199 10.0.0.207 0x80000002 3600 0x00c9243 0.0.0.200 10.0.0.207 0x80000002 3600 0x0089664 10.0.0.206 10.0.0.207 0x80000008 0 0x001951Table 11 describes the significant fields shown in the display.
Related Commands
show ospfv3 interface
To display Open Shortest Path First Version 3 (OSPFv3) interface information, use the show ospfv3 interface command in EXEC mode.
show ospfv3 [process-name] [area-id] interface [interface-type interface-instance]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show ospfv3 interface command when the adjacency between two neighboring routers is not forming. Adjacency means that the routers synchronize their databases when they discover each other.
You can look at the output to check the physical link and line protocol status and to confirm that the network type and timer intervals match those of the neighboring routers.
Task ID
Examples
The following is sample output from the show ospfv3 interface command when Packet-over-SONET/SDH (POS) interface 0/2/0/0 is specified:
RP/0/RP0/CPU0:router# show ospfv3 interface POS 0/2/0/0POS 0/2/0/0 is up, line protocol is upLink Local address fe80::203:a0ff:fe9d:f3fe, Interface ID 2Area 0, Process ID 1, Instance ID 0, Router ID 10.0.0.206Network Type BROADCAST, Cost: 10Transmit Delay is 1 sec, State BDR, Priority 1Designated Router (ID) 10.0.0.207, local address fe80::204:c0ff:fe22:73feBackup Designated router (ID) 10.0.0.206, local address fe80::203:a0ff:fe9d:f3feTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:06Index 0/2/1, flood queue length 0Next 0(0)/0(0)/0(0)Last flood scan length is 2, maximum is 9Last flood scan time is 0 msec, maximum is 1 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 10.0.0.207 (Designated Router)Suppress hello for 0 neighbor(s)Table 12 describes the significant fields shown in the display.
Related Commands
show ospfv3 neighbor
To display Open Shortest Path First Version 3 (OSPFv3) neighbor information on an individual interface basis, use the show ospfv3 neighbor command in EXEC mode.
show ospfv3 [process-name] [area-id] neighbor [interface-type interface-instance] [neighbor-id] [detail]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show ospfv3 neighbor command when the adjacency between two neighboring routers is not forming. Adjacency means that the routers synchronize their databases when they discover each other.
Task ID
Examples
The following is sample output from the show ospfv3 neighbor command showing two lines of summary information for each neighbor:
RP/0/RP0/CPU0:router# show ospfv3 neighborNeighbors for OSPFv3 1Neighbor ID Pri State Dead Time Interface ID Interface10.0.0.207 1 FULL/ - 00:00:35 3 POS 0/3/0/0Neighbor is up for 01:08:0510.0.0.207 1 FULL/DR 00:00:35 2 Ethernet0/0/0/0Neighbor is up for 01:08:05Total neighbor count: 2Table 13 describes the significant fields shown in the display.
The following is sample output showing summary information about the neighbor that matches the neighbor ID:
RP/0/RP0/CPU0:router# show ospfv3 neighbor 10.0.0.207Neighbors for OSPFv3 1Neighbor 10.0.0.207In the area 0 via interface Ethernet0/0/0/0Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73feNeighbor priority is 1, State is FULL, 6 state changesDR is 10.0.0.207 BDR is 10.0.0.206Options is 0x13Dead timer due in 00:00:38Neighbor is up for 01:09:21Index 0/1/2, retransmission queue length 0, number of retransmission 1First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecNeighbor 10.0.0.207In the area 1 via interface POS 0/3/0/0Neighbor: interface-id 3, link-local address fe80::3034:30ff:fe33:3742Neighbor priority is 1, State is FULL, 6 state changesOptions is 0x13Dead timer due in 00:00:38Neighbor is up for 01:09:21Index 0/1/1, retransmission queue length 0, number of retransmission 1First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecTotal neighbor count: 2Table 14 describes the significant fields shown in the display.
The following sample output shows the neighbors that match the neighbor ID on the interface when the interface along with the neighbor ID is specified:
RP/0/RP0/CPU0:router# show ospfv3 neighbor POS 0/3/0/1 10.0.0.207Neighbors for OSPFv3 1Neighbor 10.0.0.207In the area 0 via interface POS 0/3/0/1Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73feNeighbor priority is 1, State is FULL, 6 state changesDR is 10.0.0.207 BDR is 10.0.0.206Options is 0x13Dead timer due in 00:00:39Neighbor is up for 01:11:21Index 0/1/2, retransmission queue length 0, number of retransmission 1First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecTotal neighbor count: 1Table 15 describes the significant fields shown in the display.
The following sample output shows all neighbors on the interface when the interface is specified:
RP/0/RP0/CPU0:router# show ospfv3 neighbor POS 0/3/0/1Neighbors for OSPFv3 1Neighbor ID Pri State Dead Time Interface ID Interface10.0.0.207 1 FULL/DR 00:00:37 2 POS 0/3/0/1Neighbor is up for 01:12:33Total neighbor count: 1Table 16 describes the significant fields shown in the display.
The following is sample output showing detailed neighbor information for Packet-over-SONET/SDH (POS) interface 0/3/0/1:
RP/0/RP0/CPU0:router# show ospfv3 neighbor POS 0/3/0/1 detailNeighbors for OSPFv3 1Neighbor 10.0.0.207In the area 0 via interface POS 0/3/0/1Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73feNeighbor priority is 1, State is FULL, 6 state changesDR is 10.0.0.207 BDR is 10.0.0.206Options is 0x13Dead timer due in 00:00:39Neighbor is up for 01:13:40Index 0/1/2, retransmission queue length 0, number of retransmission 1First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)Last retransmission scan length is 1, maximum is 1Last retransmission scan time is 0 msec, maximum is 0 msecTotal neighbor count: 1Table 17 describes the significant fields shown in the display.
Related Commands
show ospfv3 request-list
To display the first ten link-state requests pending that the local router is making to the specified Open Shortest Path First Version 3 (OSPFv3) neighbor and interface, use the show ospfv3 request-list command in EXEC mode.
show ospfv3 [process-name] [area-id] request-list [interface-type interface-instance] [neighbor-id]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You might use this command when the databases of two neighboring routers are out of synchronization or if the adjacency is not forming between them. Adjacency means that the routers synchronize their databases when they discover each other.
You can look at the list to determine if one router is trying to request a particular database update. Entries that appear to be suspended in the list usually indicate that updates are not being delivered. One possible reason for this behavior is a maximum transmission unit (MTU) mismatch between the routers.
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that actually exist.
Task ID
Examples
The following sample output shows request lists for neighbor 10.0.0.207 on the OSPFv3 1 process:
RP/0/RP0/CPU0:router# show ospfv3 1 request-list 10.0.0.207 POS 0/3/0/0Request Lists for OSPFv3 1Neighbor 10.0.0.207, interface POS 0/3/0/0 address fe80::3034:30ff:fe33:3742Type LS ID ADV RTR Seq NO Age Checksum1 192.168.58.17 192.168.58.17 0x80000012 12 0x0036f32 192.168.58.68 192.168.58.17 0x80000012 12 0x00083fTable 18 describes the significant fields shown in the display.
Related Commands
show ospfv3 retransmission-list
To display the first ten link-state entries in the retransmission list that the local router sends to the specified neighbor over the specified interface, use the show ospfv3 retransmission-list command in EXEC mode.
show ospfv3 [process-name] [area-id] retransmission-list [interface-type interface-instance] [neighbor-id]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You might use this command when the databases of two neighboring routers are out of synchronization or if the adjacency is not forming between them. Adjacency means that the routers synchronize their databases when they discover each other.
You can look at the list to determine if one router is trying to request a particular database update. Entries that appear to be suspended in the list usually indicate that updates are not being delivered. One possible reason for this behavior is a maximum transmission unit (MTU) mismatch between the routers.
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that actually exist.
Task ID
Examples
The following sample output shows the retransmission list for neighbor 10.0.124.4 on Packet-over-SONET/SDH (POS) interface 0/3/0/0:
RP/0/RP0/CPU0:router# show ospfv3 retransmission-list 10.0.124.4 POS 0/3/0/0Neighbor 10.0.124.4, interface POS 0/3/0/0 address fe80::3034:30ff:fe33:3742Table 19 describes the significant fields shown in the display.
Related Commands
Configures an OSPFv3 routing process.
Displays the first ten link-state requests pending that the local router is making to the specified neighbor and interface.
show ospfv3 routes
To display the Open Shortest Path First Version 3 (OSPFv3) route table, use the show ospfv3 routes command in EXEC mode.
show ospfv3 [process-name] routes [external | connected] [ipv6-prefix/prefix-length]
show ospfv3 [process-name] routes summary
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show ospfv3 routes command to display the OSPFv3 private routing table (which contains only routes calculated by OSPFv3). If there is something wrong with a route in the Routing Information Base (RIB), check the OSPFv3 copy of the route to determine if it matches the RIB contents. If it does not match, there is a synchronization problem between OSPFv3 and the RIB. If the routes match and the route is incorrect, OSPFv3 has made an error in its routing calculation.
Task ID
Examples
The following sample output shows the route table for OSPFv3 process 1:
RP/0/RP0/CPU0:router# show ospfv3 1 routesRoute Table for OSPFv3 1 with ID 10.3.4.2* 3000:11:22::/64, Inter, cost 21/0, area 1POS 0/3/0/0, fe80::3034:30ff:fe33:374210.0.0.207/200* 3000:11:22:1::/64, Inter, cost 31/0, area 1POS 0/3/0/0, fe80::3034:30ff:fe33:374210.0.0.207/1* 3333::/56, Ext2, cost 20/1, P:0 F:0POS 0/3/0/0, fe80::3034:30ff:fe33:374210.0.0.207/0* 6050::/56, Ext2, cost 20/1, P:0 F:0POS 0/3/0/0, fe80::3034:30ff:fe33:374210.0.0.207/1* 7002::/56, Intra, cost 10/0, area 0Ethernet0/0/0/0, connected* 3000:11:22::/64, Inter, cost 21/0, area 1POS 0/3/0/0, fe80::3034:30ff:fe33:374210.0.0.207/200Table 20 describes the significant fields in the display.
Related Commands
show ospfv3 summary-prefix
To display Open Shortest Path First Version 3 (OSPFv3) aggregated summary address information, use the show ospfv3 summary-prefix command in EXEC mode.
show ospfv3 [process-name] summary-prefix
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show ospfv3 summary-prefix command if you configured summarization of external routes with the summary-prefix command and you want to display configured summary addresses.
Task ID
Examples
The following sample output shows the summary prefix address for the OSPFv3 1 process:
RP/0/RP0/CPU0:router# show ospfv3 1 summary-prefixOSPFv3 Process 1, Summary-prefix4004:f000::/32 Metric 20, Type 2, Tag 0Table 21 describes the significant fields shown in the display.
Related Commands
Configures an OSPFv3 routing process.
Creates aggregate addresses for routes being redistributed from another routing protocol into OSPFv3.
show ospfv3 virtual-links
To display parameters and the current state of Open Shortest Path First Version 3 (OSPFv3) virtual links, use the show ospfv3 virtual-links command in EXEC mode.
show ospfv3 [process-name] virtual-links
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The information displayed in the show ospfv3 virtual-links command is useful in debugging OSPFv3 routing operations.
Task ID
Examples
The following sample output shows the virtual links for the OSPFv3 1 process:
RP/0/RP0/CPU0:router# show ospfv3 1 virtual-linksVirtual Links for OSPFv3 1Virtual Link to router 172.31.101.2 is upInterface ID 16, IPv6 address 3002::206Transit area 0.0.0.1, via interface POS 0/3/0/0, Cost of using 11Transmit Delay is 5 sec, State POINT_TO_POINT,Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 0:00:08Adjacency State FULLTable 22 describes the significant fields shown in the display.
Related Commands
show protocols (OSPFv3)
To display information about the Open Shortest Path First Version 3 (OSPFv3) process running on the router, use the show protocols command in EXEC mode.
show protocols [afi-all | ipv4 | ipv6] [all | protocol]
Syntax Description
Defaults
The default address family is IPv4.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example is sample output from the show protocols command:
RP/0/RP0/CPU0:router# show protocols ipv6 ospfv3Routing Protocol OSPFv3 1Router Id:10.0.0.1Distance:110Redistribution:NoneArea 0POS 0/2/0/2Loopback1Table 23 describes the significant fields shown in the display.
stub (OSPFv3)
To define an area as a stub area for Open Shortest Path First Version 3 (OSPFv3), use the stub command in area configuration mode. To disable this function, use the no form of this command.
stub [no-summary]
no stub
Syntax Description
no-summary
(Optional) Prevents an area border router (ABR) from sending summary link advertisements into the stub area. Areas with this option are known as totally stubby areas.
Defaults
No stub area is defined.
Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You must configure the stub command on all routers in the stub area. Use the default-cost area command on the ABR of a stub area to specify the cost of the default route advertised into the stub area by the ABR.
Two stub area router configuration commands exist: the stub and default-cost commands. In all routers attached to the stub area, the area should be configured as a stub area using the stub command. Use the default-cost command only on an ABR attached to the stub area. The default-cost command provides the metric for the summary default route generated by the ABR into the stub area.
To further reduce the number of link-state advertisements (LSAs) sent into a stub area, you can configure the no-summary keyword on the ABR to prevent it from sending summary LSAs (LSA Type 3) into the stub area.
A stub area does not accept information about routes external to the autonomous system.
Task ID
Examples
The following example shows how to create stub area 5 and specifies a cost of 20 for the default summary route sent into this stub area:
RP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# area 5RP/0/RP0/CPU0:router(config-ospfv3-ar)# stubRP/0/RP0/CPU0:router(config-ospfv3-ar)# default-cost 20Related Commands
summary-prefix (OSPFv3)
To create aggregate addresses for routes being redistributed from another routing protocol into Open Shortest Path First Version 3 (OSPFv3) protocol, use the summary-prefix command in router ospfv3 configuration mode. To stop summarizing redistributed routes, use the no form of the command.
summary-prefix ipv6-prefix/prefix-length [not-advertise] [tag tag]
no summary-prefix ipv6-prefix/prefix-length
Syntax Description
Defaults
When this command is not used in router configuration mode, aggregate addresses are not created for routes being redistributed from another routing protocol into the OSFPv3 protocol.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the summary-prefix command to cause an OSPFv3 Autonomous System Boundary Router (ASBR) to advertise one external route as an aggregate for all redistributed routes that are covered by the address. This command summarizes only routes from other routing protocols that are being redistributed into OSPFv3.
You can use this command multiple times to summarize multiple groups of addresses. The metric used to advertise the summary is the lowest metric of all the more specific routes. This command helps reduce the size of the routing table.
If you want to summarize routes between OSPFv3 areas, use the range command.
Task ID
Examples
In the following example, if summary prefix 4004:f000:132 is configured and routes 4004:f000:1::/64, 4004:f000:2::/64, and 4004:f000:3::/64 are redistributed into OSPFv3; only route 4004:f000::/32 is advertised in an external link-state advertisement:
RP/0/RP0/CPU0:router(config-ospfv3)# summary-prefix 4004:f000::/32Related Commands
timers lsa arrival
To set the minimum interval at which the software accepts the same link-state advertisement (LSA) from Open Shortest Path First Version 3 (OSPFv3) neighbors, use the timers lsa arrival command in router ospfv3 configuration mode. To restore the default value, use the no form of this command.
timers lsa arrival milliseconds
no timers lsa arrival
Syntax Description
milliseconds
Minimum delay (in milliseconds) that must pass between acceptance of the same LSA arriving from neighbors. Range is 0 to 60000 milliseconds.
Defaults
1000 milliseconds
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the timers lsa arrival command to control the minimum interval for accepting the same LSA. The same LSA is an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. If an instance of the same LSA arrives sooner than the interval that is set, the LSA is dropped.
We recommended that the milliseconds value of the timers lsa arrival command be less than or equal to the hold-interval value of the timers throttle lsa all command for the neighbor.
Task ID
Examples
The following example shows how to set the minimum interval for accepting the same LSA at 2000 milliseconds:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers throttle lsa all 200 10000 45000RP/0/RP0/CPU0:router(config-ospfv3)# timers lsa arrival 2000Related Commands
timers pacing flood
To configure link-state advertisement (LSA) flood packet pacing, use the timers pacing flood command in router ospfv3 configuration mode. To restore the default flood packet pacing value, use the no form of this command.
timers pacing flood milliseconds
no timers pacing flood
Syntax Description
milliseconds
Time (in milliseconds) at which LSAs in the flooding queue are paced in between updates. Range is 5 milliseconds to 100 milliseconds.
Defaults
milliseconds: 33
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Configuring OSPFv3 flood pacing timers allows you to control interpacket spacing between consecutive link-state update packets in the OSPF transmission queue. Use the timers pacing flood command to control the rate at which LSA updates occur, thereby preventing high CPU or buffer utilization that can result when an area is flooded with a very large number of LSAs.
The default settings for OSPFv3 packet pacing timers are suitable for the majority of OSPFv3 deployments. Do not change the packet pacing timers unless all other options to meet OSPFv3 packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flood timers. Furthermore, no guidelines exist for changing timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis. The network operator assumes risks associated with changing the default flood timer values.
Task ID
Examples
The following example shows how to configure LSA flood packet-pacing updates to occur in 55-millisecond intervals for OSPFv3 routing process 1:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers pacing flood 55Related Commands
timers pacing lsa-group
To change the interval at which Open Shortest Path First Version 3 (OSPFv3) link-state advertisements (LSAs) are collected into a group and refreshed, checksummed, or aged, use the timers pacing lsa-group command in router ospfv3 configuration mode. To restore the default value, use the no form of this command.
timers pacing lsa-group seconds
no timers pacing lsa-group
Syntax Description
seconds
Interval (in seconds) at which LSAs are grouped and refreshed, checksummed, or aged. Range is 10 to 1800 seconds.
Defaults
seconds: 240
OSPFv3 LSA group pacing is enabled by default.Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the timers pacing lsa-group command to control the rate at which LSA updates occur so that high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs can be reduced. The default settings for OSPFv3 packet pacing timers are suitable for the majority of deployments. Do not change the packet pacing timers unless all other options to meet OSPFv3 packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. Furthermore, no guidelines exist for changing timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis. The network operator assumes the risks associated with changing the default timer values.
Cisco IOS XR software groups the periodic refresh of LSAs to improve the LSA packing density for the refreshes in large topologies. The group timer controls the interval used for group refreshment of LSAs; however, this timer does not change the frequency that individual LSAs are refreshed (the default refresh rate is every 30 minutes).
The duration of the LSA group pacing is inversely proportional to the number of LSAs the router is handling. For example, if you have about 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.
Task ID
Examples
The following example shows how to configure OSPFv3 group packet-pacing updates between LSA groups to occur in 60-second intervals for OSPFv3 routing process 1:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers pacing lsa-group 60Related Commands
Displays general information about OSPFv3 routing processes.
Configures LSA flood packet pacing.
Configures LSA retransmission packet pacing.
timers pacing retransmission
To configure link-state advertisement (LSA) retransmission packet pacing, use the timers pacing retransmission command in router ospfv3 configuration mode. To restore the default retransmission packet pacing value, use the no form of this command.
timers pacing retransmission milliseconds
no timers pacing retransmission
Syntax Description
milliseconds
Time (in milliseconds) at which LSAs in the retransmission queue are paced. Range is 5 milliseconds to 100 milliseconds.
Defaults
milliseconds: 66
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the timers pacing retransmission command to control interpacket spacing between consecutive link-state update packets in the OSPFv3 retransmission queue. This command controls the rate at which LSA updates occur. When an area is flooded with a very large number of LSAs, the LSA updates can result in high CPU or buffer utilization. Using this command reduces CPU or buffer utilization.
The default settings for OSPFv3 packet retransmission pacing timers are suitable for the majority of deployments. Do not change the packet retransmission pacing timers unless all other options to meet OSPFv3 packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. Furthermore, no guidelines exist for changing timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis. The network operator assumes risks associated with changing the default packet retransmission pacing timer values.
Task ID
Examples
The following example shows how to configure LSA flood pacing updates to occur in 55-millisecond intervals for OSPFv3 routing process 1:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers pacing retransmission 55Related Commands
timers throttle lsa all (OSPFv3)
To set rate-limiting values for Open Shortest Path First Version 3 (OSPFv3) link-state advertisement (LSA) generation, use the timers throttle lsa all command in router ospfv3 configuration mode. To restore the default values, use the no form of this command.
timers throttle lsa all start-interval hold-interval max-interval
no timers throttle lsa all
Syntax Description
Defaults
start-interval: 500 milliseconds
hold-interval: 5000 milliseconds
max-interval: 5000 millisecondsCommand Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The "same LSA" is defined as an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. We recommended that you keep the milliseconds value of the timers lsa arrival command less than or equal to the hold-interval value of the timers throttle lsa all command.
Task ID
Examples
This example shows how to customize OSPFv3 LSA throttling so that the start interval is 200 milliseconds, the hold interval is 10,000 milliseconds, and the maximum interval is 45,000 milliseconds. The minimum interval between instances of receiving the same LSA is 2000 milliseconds.
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers throttle lsa all 200 10000 45000RP/0/RP0/CPU0:router(config-ospfv3)# timers lsa arrival 2000Related Commands
Displays general information about OSPFv3 routing processes.
Sets the minimum interval at which the software accepts the same LSA from OSPFv3 neighbors.
timers throttle spf (OSPFv3)
To turn on Open Shortest Path First Version 3 (OSPFv3) shortest path first (SPF) throttling, use the timers throttle spf command in router ospfv3 configuration mode. To turn off SPF throttling, use the no form of this command.
timers throttle spf spf-start spf-hold spf-max-wait
no timers throttle spf spf-start spf-hold spf-max-wait
Syntax Description
Defaults
SPF throttling is not set.
Command Modes
Router ospfv3 configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The first wait interval between SPF calculations is the amount of time (in milliseconds) specified by the spf-start argument. Each consecutive wait interval is twice the current hold level (in milliseconds) until the wait time reaches the maximum time (in milliseconds) as specified by the spf-max-wait argument. Subsequent wait times remain at the maximum until the values are reset or a link-state advertisement (LSA) is received between SPF calculations.
Tip
Task ID
Examples
The following example shows how to change the start, hold, and maximum wait interval values to 5, 1000, and 90,000 milliseconds, respectively:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# timers throttle spf 5 1000 90000trace
To specify the Open Shortest Path First Version 3 (OSPFv3) buffer size, use the trace command in router ospfv3 configuration mode. To return to the default value, use the no form of this command.
trace {convergence | error | ifmgr | rtrid} max-trace-entries
no trace {convergence | error | ifmgr | rtrid}
Syntax Description
Defaults
No default behavior or values
Command Modes
Router ospfv3 configuration
Command History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Trace buffers are used to store various traffic and processing events during the runtime. Large buffers can store more events. If the buffer becomes full, old entries are overwritten by the latest entries. In a large network, user may want to increase the trace buffer size to accommodate more events.
Task ID
Examples
The following example shows how to set the trace entries:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# trace error 2500transmit-delay (OSPFv3)
To set the estimated time required to send a link-state update packet on the interface, use the transmit-delay command in the appropriate mode. To return to the default value, use the no form of this command.
transmit-delay seconds
no transmit-delay seconds
Syntax Description
Defaults
1 second
Command Modes
Process configuration
Area configuration
Interface configuration
Virtual-link configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Link-state advertisements (LSAs) in the update packet must have their ages incremented by the amount specified in the seconds argument before transmission. The value assigned should take into account the transmission and propagation delays for the interface.
If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. This setting has more significance on very low-speed links.
Task ID
Examples
The following example shows how to configure a transmit delay of 3 seconds for Packet-over-SONET/SDH (POS) interface POS 0/3/0/0:
RP/0/RP0/CPU0:router(config)# router ospfv3 1RP/0/RP0/CPU0:router(config-ospfv3)# area 0RP/0/RP0/CPU0:router(config-ospfv3-ar)# interface POS 0/3/0/0RP/0/RP0/CPU0:router(config-ospfv3-ar-if)# transmit-delay 3Related Commands
virtual-link (OSPFv3)
To define an Open Shortest Path First Version 3 (OSPFv3) virtual link, use the virtual-link command in area configuration mode. To remove a virtual link, use the no form of this command.
virtual-link router-id
no virtual-link
Syntax Description
Defaults
No virtual links are defined.
Command Modes
Area configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
In OSPFv3, when there exists a path through another non-backbone area over which the virtual link can function, all areas must be connected to a backbone area. If the connection to the backbone is lost, it can be repaired by establishing a virtual link.
Virtual links, which are defined in the submode of the area they transit, are in effect virtual point-to-point interfaces belonging to area 0 (the backbone). The virtual links inherit parameter values from the backbone area, rather than the transit area in which they are defined.
Each virtual link neighbor must include the router ID of the virtual link neighbor for the link to be properly established. Use the show ospfv3 command to display the router ID of an OSPFv3 process.
Use the virtual-link command to place the router in virtual-link configuration mode (config-router-ar-vl), from which you can configure virtual-link-specific settings. Commands configured under this mode (such as the transmit-delay command) are automatically bound to that virtual link.
Task ID
Examples
The following example shows how to establish a virtual link with default values for all optional parameters:
RP/0/RP0/CPU0:router(config)# router ospfv3 201RP/0/RP0/CPU0:router(config-ospfv3)# area 1RP/0/RP0/CPU0:router(config-ospfv3-ar)# virtual-link 10.3.4.5Related Commands
Displays general information about OSPF routing processes.
Sets the estimated time required to send a link-state update packet on the interface.
Feedback