Table Of Contents
OSPF Commands on Cisco IOS XR Software
address-family (OSPF)
area (OSPF)
authentication (OSPF)
authentication-key (OSPF)
auto-cost (OSPF)
capability opaque
clear ospf process
clear ospf redistribution
clear ospf routes
clear ospf statistics
cost (OSPF)
database-filter all out (OSPF)
dead-interval (OSPF)
default-cost (OSPF)
default-information originate (OSPF)
default-metric (OSPF)
demand-circuit (OSPF)
distance (IP)
distance ospf
distribute-list
flood-reduction (OSPF)
hello-interval (OSPF)
ignore lsa mospf
interface (OSPF)
log adjacency changes (OSPF)
max-metric
maximum interfaces (OSPF)
maximum paths (OSPF)
maximum redistributed-prefix
message-digest-key
mpls traffic-eng area (OSPF)
mpls traffic-eng router-id (OSPF)
mtu-ignore (OSPF)
neighbor (OSPF)
neighbor database-filter all out
network (OSPF)
nsf (OSPF)
nsf interval (OSPF)
nsf lifetime (OSPF)
nssa (OSPF)
ospf name-lookup
packet-size
passive (OSPF)
priority (OSPF)
range (OSPF)
redistribute (OSPF)
retransmit-interval (OSPF)
router-id (OSPF)
router ospf
show ospf
show ospf border-routers
show ospf database
show ospf flood-list
show ospf interface
show ospf mpls traffic-eng
show ospf neighbor
show ospf request-list
show ospf retransmission-list
show ospf route
show ospf summary-prefix
show ospf virtual-links
show protocols (OSPF)
stub (OSPF)
summary-prefix (OSPF)
timers lsa group-pacing
timers lsa min-arrival
timers throttle lsa all (OSPF)
timers throttle spf (OSPF)
transmit-delay (OSPF)
virtual-link (OSPF)
OSPF Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor the Open Shortest Path First (OSPF) routing protocol.
For detailed information about OSPF concepts, configuration tasks, and examples, see the Implementing OSPF on Cisco IOS XR Software configuration guide.
address-family (OSPF)
To enter address family configuration mode for Open Shortest Path First (OSPF), use the address-family command in the router configuration mode. To disable address family configuration mode, use the no form of this command.
address-family ipv4 [unicast]
no address-family ipv4 [unicast]
Syntax Description
ipv4
|
Specifies IP Version 4 (IPv4) address prefixes.
|
unicast
|
(Optional) Specifies unicast address prefixes.
|
Defaults
An address family is not specified.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 version 2 provides routing services for IPv4 unicast topologies, so this command has no effect.
Examples
The following example shows how to configure the OSPF router process with IPv4 unicast address prefixes:
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# address-family ipv4 unicast
area (OSPF)
To configure an Open Shortest Path First (OSPF) area, use the area command in router configuration mode. To terminate an OSPF area, use the no form of this command.
area area-id
no area area-id
Syntax Description
area-id
|
Identifier of an OSPF area. The area-id argument can be specified as either a decimal value or an IP address.
|
Defaults
No OSPF area is defined.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 area command to explicitly configure an area. Commands configured under the area configuration mode (such as the interface [OSPF] and authentication commands), are automatically bound to that area.
To modify or remove the area, the area-id argument format must be the same as the format used when creating the area. Otherwise, even if the actual 32-bit value matches, the area is not matched. For example, if you create an area with an area-id of 10 it would not match an area-id of 0.0.0.10.
Note
To remove the specified area from the router configuration, use the no area area-id command. The no area area-id command removes the area and all area options, such as authentication, default-cost, nssa, range, stub, virtual-link, and interface.
Examples
The following example shows how to configure area 0 and Packet-over-SONET (POS) interface 0/2/0/0. POS interface 0/2/0/0 is bound to area 0 automatically.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/2/0/0
authentication (OSPF)
To enable plain text, Message Digest 5 (MD5) authentication, or null authentication for an Open Shortest Path First (OSPF) interface, use the authentication command in the appropriate mode. To remove such authentication, use the no form of this command.
authentication [message-digest | null]
no authentication
Syntax Description
message-digest
|
(Optional) Specifies that MD5 is used.
|
null
|
(Optional) Specifies that no authentication is used. Useful for overriding password or MD5 authentication if configured for an area.
|
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 configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF interfaces that are to communicate with each other through OSPF. If you specified plain text authentication, use the authentication-key command to specify the plain text password.
If you enable MD5 authentication with the message-digest keyword, you must configure a password with the message-digest-key interface command.
Examples
The following example shows how to set authentication for areas 0 and 1 of OSPF routing process 201. Authentication keys are also provided.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 201
RP/0/RP0/CPU0:router(config-ospf)# router-id 10.1.1.1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# authentication
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# authentication-key mykey
RP/0/RP0/CPU0:router(config-ospf-ar-if)# exit
RP/0/RP0/CPU0:router(config-ospf)# area 1
RP/0/RP0/CPU0:router(config-ospf-ar)# authentication
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/0
RP/0/RP0/CPU0:router(config-ospf-ar-if)# authentication-key mykey1
Related Commands
authentication-key (OSPF)
To assign a password to be used by neighboring routers that are using the Open Shortest Path First (OSPF) simple password authentication, use the authentication-key command in the appropriate mode. To remove a previously assigned OSPF password, use the no form of this command.
authentication-key [clear | encrypted] password
no authentication-key
Syntax Description
clear
|
(Optional) Specifies that the key be clear text.
|
encrypted
|
(Optional) Specifies that the key be encrypted using a two-way algorithm.
|
password
|
Any contiguous string of characters up to 8 bytes in length that can be entered from the keyboard.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the OSPF password parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the OSPF password parameter specified for the process.
If this command is not specified at any level, then no password is specified.
Clear is the default if the clear or encrypted keyword is not specified.
Command Modes
Interface configuration
Area configuration
Router configuration
Virtual-link configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The 0 and 7 keywords were changed to clear and encrypted.
|
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 password created by this command is used as a "key" that is inserted directly into the OSPF header when the Cisco IOS XR software originates routing protocol packets. A separate password can be assigned to each network on an individual interface basis. All neighboring routers on the same network must have the same password to be able to exchange OSPF information.
The authentication-key command must be used with the authentication command. If the authentication command is not configured, the password provided by the authentication-key command is ignored and no authentication is adopted by the OSPF interface.
Note
The authentication-key command cannot be used with the authentication command when the message-digest or null keyword is configured.
Examples
The following example shows how to enable the authentication key with the string yourpass:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 201
RP/0/RP0/CPU0:router(config-ospf)# authentication-key yourpass
Related Commands
auto-cost (OSPF)
To control how the Open Shortest Path First (OSPF) protocol calculates default metrics for the interface, use the auto-cost command in router configuration mode. To revert to the default reference bandwidth, use the no form of this command.
auto-cost {reference-bandwidth mbps | disable}
no auto-cost [reference-bandwidth | disable]
Syntax Description
reference-bandwidth mbps
|
Specifies a rate in Mbps (bandwidth). Range is 1 to 4294967.
|
disable
|
Assigns a cost based on interface type.
|
Defaults
mbps: 100 Mbps
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF calculates the OSPF metric for an interface according to the bandwidth of the interface.
The OSPF metric is calculated as the mbps value divided by bandwidth, with mbps equal to 108 by default.
If you have multiple links with high bandwidth (such as OC-192), you might want to use a larger number to differentiate the cost on those links. That is, the metric calculated using the default mbps value is the same for all high-bandwidth links.
Recommended usage of cost configuration for all OSPF configured interfaces is to be consistent: Either explicitly configure (by using the cost command) or choose default (by using the auto-cost command).
The value set by the cost command overrides the cost resulting from the auto-cost command.
Note
The configuration setting of this command must be duplicated on every OSPF router in the autonomous system.
Examples
The following example shows how to set the reference value for the auto cost calculation to 1000 Mbps:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# auto-cost reference-bandwidth 1000
Related Commands
Command
|
Description
|
cost (OSPF)
|
Explicitly specifies the cost of sending a packet on an interface.
|
capability opaque
To control opaque link-state advertisement (LSA) support capability of the Open Shortest Path First (OSPF) protocol, use the capability opaque command in router configuration mode. To prevent Multiprotocol Label Switching traffic engineering (MPLS TE) topology information flooded to the network through opaque LSAs, use the disable form of this command.
capability opaque [disable]
no capability opaque [disable]
Syntax Description
enable
|
(Optional) Enables opaque LSA support capability.
|
disable
|
(Optional) Disables opaque LSA support capability.
|
Defaults
Opaque LSAs are allowed.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The enable keyword was removed.
|
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.
Control opaque LSA support capability must be enabled for OSPF to support MPLS TE. The MPLS TE topology information is flooded to the network through opaque LSAs of OSPF.
Examples
The following example shows how to prevent OSPF from supporting opaque services:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# capability opaque disable
clear ospf process
To reset an Open Shortest Path First (OSPF) router process without stopping and restarting it, use the clear ospf process command in EXEC mode.
clear ospf [process-name] process
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only the specified routing process is affected. Otherwise, all OSPF processes are reset.
|
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF router process is reset, OSPF releases all resources allocated, cleans up the internal database, and shuts down and restarts all interfaces that belong to the process.
Examples
The following example shows how to reset all OSPF processes:
RP/0/RP0/CPU0:router# clear ospf process
The following example shows how to reset the OSPF process 1:
RP/0/RP0/CPU0:router# clear ospf 1 process
Related Commands
Command
|
Description
|
router ospf
|
Configures an OSPF routing process.
|
clear ospf redistribution
To clear all routes redistributed from other protocols out of the Open Shortest Path First (OSPF) routing table, use the clear ospf redistribution command in EXEC mode.
clear ospf [process-name] redistribution
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only the specified routing process is affected. Otherwise, all OSPF routes are cleared.
|
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf redistribution command to cause the routing table to be read again. OSPF regenerates and sends Type 5 and Type 7 link-state advertisements (LSAs) to its neighbors. If an unexpected route has appeared in the OSPF redistribution, using this command corrects the issue.
Note
Use of this command can cause a significant number of LSAs to flood the network. We recommend that you use this command with caution.
Examples
The following example shows how to clear all redistributed routes across all processes from other protocols:
RP/0/RP0/CPU0:router# clear ospf redistribution
clear ospf routes
To clear all Open Shortest Path First (OSPF) routes from the OSPF routing table, use the clear ospf routes command in EXEC mode.
clear ospf [process-name] routes
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only the specified routing process is affected. Otherwise, all OSPF routes are cleared.
|
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The topology keyword was replaced with the routes keyword.
|
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.
Examples
The following example shows how to clear all OSPF routes from the OSPF routing table and recompute valid routes. When the OSPF routing table is cleared, OSPF routes in the global routing table are also recalculated.
RP/0/RP0/CPU0:router# clear ospf routes
Related Commands
Command
|
Description
|
router ospf
|
Configures an OSPF routing process.
|
clear ospf statistics
To clear the Open Shortest Path First (OSPF) statistics of neighbor state transitions, use the clear ospf statistics command in EXEC mode.
clear ospf [process-name] statistics [neighbor [interface-type interface-instance] [ip-address]]
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only the specified routing process is affected. Otherwise, all OSPF statistics of neighbor state transitions are cleared.
|
neighbor
|
(Optional) Clears the state transition counters of the specified neighbor only.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
ip-address
|
(Optional) IP address of a specified neighbor for whom you want to clear the state transition counter.
|
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf statistics command to reset OSPF counters. Reset is useful to detect changes in counter values.
Examples
The following example shows how to reset the OSPF transition state counters for all neighbors on Packet-over-SONET (POS) interface 0/2/0/0:
RP/0/RP0/CPU0:router# clear ospf statistics neighbor POS 0/2/0/0
Related Commands
Command
|
Description
|
router ospf
|
Configure s an OSPF routing process.
|
cost (OSPF)
To explicitly specify the cost of sending a packet on an Open Shortest Path First (OSPF) interface, 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
cost
|
Unsigned integer value expressed as the link-state metric. Range is 1 to 65535.
|
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 calculated by the auto-cost command.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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. Cisco IOS XR software does not support type of service (ToS), so you can assign only one cost for each interface.
In general, the path cost is calculated using the following formula:
10^8 / bandwidth (the default auto cost is set to 100 Mbps)
This calculation is the default reference bandwidth used by the auto-costing calculation which establishes the interface auto-cost The auto-cost command can set this reference bandwidth to some other value. The cost command is used to override the auto-costing calculated default value for interfaces.
Using this formula, the default path cost is 1 for any interface that has a link bandwidth of 100 Mbps or higher. If this value does not suit the network, configure the reference bandwidth for auto calculating costs based on the link bandwidth.
The value set by the cost command overrides the cost resulting from the auto-cost (OSPF) command.
Examples
The following example shows how to set the cost value to 65 for Packet-over-SONET (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# cost 65
Related Commands
Command
|
Description
|
auto-cost (OSPF)
|
Controls how the OSPF protocol calculates default metrics for the interface.
|
database-filter all out (OSPF)
To filter outgoing link-state advertisements (LSAs) to an Open Shortest Path First (OSPF) interface, use the database-filter all out command in interface configuration mode. To restore the forwarding of LSAs to the interface, use the disable form of the command.
database-filter all out [disable | enable]
Syntax Description
disable
|
(Optional) Disables filtering.
|
enable
|
(Optional) Enables filtering.
|
Defaults
The database filter is disabled.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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-file all out command to perform the same function that the neighbor database-filter all out command performs on a neighbor basis.
Examples
The following example shows how to prevent flooding of OSPF LSAs to broadcast, nonbroadcast, or point-to-point networks reachable through Packet-over-SONET (POS) interface 0/1/0/1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# database-filter all out
Related Commands
dead-interval (OSPF)
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 configuration mode. To return to the default time, use the no form of this command.
dead-interval seconds
no dead-interval
Syntax Description
seconds
|
Integer that specifies the interval (in seconds). Range is 1 to 65535. The value must be the same for all nodes on the network.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the dead interval parameter specified by 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 at any level, then the dead interval is four times the interval set by the hello-interval (OSPF) command.
Command Modes
Interface configuration
Area configuration
Router configuration
Virtual-link configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 dead interval value must be the same for all routers and access servers on a specific network.
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.
Examples
The following example shows how to set the OSPF dead interval to 40 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# dead-interval 40
Related Commands
Command
|
Description
|
hello-interval (OSPF)
|
Specifies the interval between hello packets that the Cisco IOS XR software sends on the interface.
|
default-cost (OSPF)
To specify a cost for the default summary route sent into a stub area or not-so-stubby area (NSSA), 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
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 command in the area 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.
Examples
The following example shows how to assign a default cost of 20 to a stub area (the Packet-over-SONET (POS) interface 0/4/0/3 is also configured in the stub area):
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 201
RP/0/RP0/CPU0:router(config-ospf)# area 10.15.0.0
RP/0/RP0/CPU0:router(config-ospf-ar)# stub
RP/0/RP0/CPU0:router(config-ospf-ar)# default-cost 20
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/4/0/3
Related Commands
Command
|
Description
|
stub (OSPF)
|
Defines an area as a stub area.
|
default-information originate (OSPF)
To generate a default external route into an Open Shortest Path First (OSPF) routing domain, use the default-information originate command in router configuration mode. To disable this feature, use the no form of this command.
default-information originate [always] [metric metric-value] [metric-type type-value] [policy
policy-name]
no default-information originate
Syntax Description
always
|
(Optional) Always advertises the default route regardless of whether the routing table has a default route.
|
metric metric-value
|
(Optional) Specifies the metric used for generating the default route. If you omit a value and do not specify a value using the default-metric command, the default metric value is 10. Range is 1 to 16777214.
|
metric-type type-value
|
(Optional) Specifies the external link type associated with the default route advertised into the OSPF routing domain. It can be one of the following values:
• 1—Type 1 external route
• 2—Type 2 external route
|
policy policy-name
|
(Optional) Specifies that a routing policy be used and the routing policy name.
|
Defaults
When you do not use this command in router configuration mode, no default external route is generated into an OSPF routing domain.
metric-value: 10
type-value: 2
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 originate command to redistribute routes into an OSPF routing domain, the software automatically becomes an Autonomous System Boundary Router (ASBR). However, an ASBR does not, by default, generate a default route into the OSPF routing domain. The software still must have a default route for itself before it generates one, except when you have specified the always keyword.
For information about routing policies, see the Routing Policy Commands on Cisco IOS XR Software module of the Cisco IOS XR Routing Command Reference.
Examples
The following example shows how to specify a metric of 100 for the default route redistributed into the OSPF routing domain and an external metric type of Type 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# redistribute igrp 108 metric 100
RP/0/RP0/CPU0:router(config-ospf)# default-information originate metric 100 metric-type 1
Related Commands
Command
|
Description
|
redistribute (OSPF)
|
Redistributes routes from one routing domain into a specified OSPF process.
|
default-metric (OSPF)
To set default metric values for routes redistributed from another protocol into the Open Shortest Path First (OSPF) protocol, use the default-metric command in router configuration mode. To return to the default state, use the no form of this command.
default-metric value
no default-metric value
Syntax Description
value
|
Default metric value appropriate for the specified routing protocol. Range is 1 to 16777214.
|
Defaults
Built-in, automatic metric translations, as appropriate for each routing protocol. Current metrics are displayed in the show ospf summary-prefix command output. Note that this output is only displayed if there are routes currently redistributed from protocols.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following example shows how to advertise Intermediate System-to-Intermediate System (IS-IS) protocol-derived routes into OSPF and assign a metric of 10:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf# default-metric 10
RP/0/RP0/CPU0:router(config-ospf)# redistribute isis 15
Related Commands
demand-circuit (OSPF)
To configure the Open Shortest Path First (OSPF) protocol to treat the interface as an OSPF 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 | enable]
no demand-circuit
Syntax Description
disable
|
(Optional) Disables the interface as an OSPF demand circuit.
|
enable
|
(Optional) Enables the interface as an OSPF demand circuit.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the demand circuit parameter specified by 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 circuit is not a demand circuit.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
The disable keyword was added.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 this command. Periodic hello messages are suppressed and periodic refreshes of link-state advertisements (LSAs) do not flood the demand circuit. Use the demand-circuit command to allow 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.
Examples
The following example shows how to set the configuration for an OSPF demand circuit:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# demand-circuit
distance (IP)
To define an administrative distance, use the distance command in router configuration mode. To remove the distance command from the configuration file and restore the system to its default condition in which the software removes a distance definition, use the no form of this command.
distance weight [ip-address mask [access-list-name]]
no distance weight ip-address mask [access-list-name]
Syntax Description
weight
|
Administrative distance. Range is 1 to 255. Used alone, the weight argument specifies a default administrative distance that the software uses when no other specification exists for a routing information source. Routes with a distance of 255 are not installed in the routing table. Table 67 lists the default administrative distances.
|
ip-address
|
(Optional) IP address in four-part, dotted-decimal notation.
|
mask
|
(Optional) IP address mask in four-part, dotted-decimal format. A bit set to 1 in the mask argument instructs the software to ignore the corresponding bit in the address value.
|
access-list-name
|
(Optional) Name of an IP access list to be applied to incoming routing updates.
|
Defaults
If this command is not specified at the area level, then the administrative distance is the default, as specified in Table 67.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The ip-address and mask arguments for the no form of the command were changed from optional to required.
|
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 administrative distance is an integer from 10 to 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means that the routing information source cannot be trusted at all and should be ignored. Weight values are subjective; no quantitative method exists for choosing weight values.
If an access list is used with this command, it is applied when a network is being inserted into the routing table. This behavior allows you to filter networks based on the IP address of the router supplying the routing information. For example, you could filter possibly incorrect routing information from networking devices not under your administrative control.
The order in which you enter distance commands can affect the assigned administrative distances in unexpected ways (see the "Examples" section for further clarification).
Table 67 lists default administrative distances.
Table 67 Default Administrative Distances
Route Source
|
Default Distance
|
Connected interface
|
0
|
Static route
|
1
|
External Border Gateway Protocol (BGP)
|
20
|
OSPF
|
110
|
IS-IS
|
115
|
Internal BGP
|
200
|
Unknown
|
255
|
Examples
In the following example, the router ospf command sets up OSPF routing in autonomous system number 1. The first distance command sets the default administrative distance to 255, which instructs the software to ignore all routing updates from networking devices for which an explicit distance has not been set. The second distance command sets the administrative distance for all networking devices on the Class C network 192.168.40.0 to 90.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# distance 255
RP/0/RP0/CPU0:router(config-ospf)# distance 90 192.168.40.0 0.0.0.255
Related Commands
Command
|
Description
|
distance bgp
|
Allows the use of external, internal, and local administrative distances that could be a better route to a BGP node.
|
distance ospf
|
Allows the use of external, internal, and local administrative distances that could be a better route to an OSPF node.
|
router ospf
|
Configures the OSPF routing process.
|
distance ospf
To define Open Shortest Path First (OSPF) route administrative distances based on route type, use the distance ospf command in router configuration mode. To restore the default value, use the no form of this command.
distance ospf {intra-area | inter-area | external} distance
no distance ospf
Syntax Description
intra-area | inter-area | external
|
Sets the type of area. It can be one of the following values:
• intra-area—All routes within an area.
• inter-area—All routes from one area to another area.
• external—All routes from other routing domains, learned by redistribution.
|
distance
|
Route administrative distance.
|
Defaults
distance: 110
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf command to perform the same function as the distance command used with an access list. However, the distance ospf 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 ospf command is when you have multiple OSPF processes with mutual redistribution, and you want to prefer internal routes from one over external routes from the other.
Examples
The following example shows how to change the external distance to 200, making the route less reliable:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# redistribute ospf 2
RP/0/RP0/CPU0:router(config-ospf)# distance ospf external 200
RP/0/RP0/CPU0:router(config-ospf)# exit
RP/0/RP0/CPU0:router(config)# router ospf 2
RP/0/RP0/CPU0:router(config-ospf)# redistribute ospf 1
RP/0/RP0/CPU0:router(config-ospf)# distance ospf external 200
Related Commands
Command
|
Description
|
distance (IP)
|
Defines an administrative distance.
|
distribute-list
To filter networks received or transmitted in Open Shortest Path First (OSPF) updates, use the distribute-list command in the appropriate mode. To change or cancel the filter, use the no form of this command.
distribute-list access-list-name {in | out [bgp | connected | ospf | static]}
no distribute-list access-list-name {in | out}
Syntax Description
access-list-name
|
Standard IP access list name. The list defines which networks are to be received and which are to be suppressed in routing updates.
|
in
|
Applies the access list to incoming routing updates.
|
out
|
Applies the access list to outgoing routing updates. The out keyword is available only in router configuration mode.
|
bgp
|
(Optional) Applies the access list to BGP routes.
|
connected
|
(Optional) Applies the access list to connected routes.
|
ospf
|
(Optional) Applies the access list to OSPF routes (not the current OSPF process).
|
static
|
(Optional) Applies the access list to statically configured routes.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the distribute list parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the distribute list parameter specified for the process.
If this command is not specified at any level, then the distribute list is disabled.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 command to limit which OSPF routes are installed on this router. The distribute-list command does not affect the OSPF protocol itself.
Examples
The following example shows how to prevent OSPF routes from the 172.17.10.0 network from being installed if they are learned in area 0:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ipv4 access-list 3
RP/0/RP0/CPU0:router(config-ipv4-acl)# deny 172.17.10.0 0.0.0.255
RP/0/RP0/CPU0:router(config-ipv4-acl)# permit any any
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# distribute-list 3 in
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/3
flood-reduction (OSPF)
To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the flood-reduction command in the appropriate mode. To remove this functionality from the configuration, use the no form of this command.
flood-reduction [enable | disable]
no flood-reduction [enable | disable]
Syntax Description
enable
|
(Optional) Turns on this functionality at a specific level.
|
disable
|
(Optional) Turns off this functionality at a specific level.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the flood reduction parameter specified by the 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 configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 supporting the OSPF demand circuit are compatible and can interact with routers supporting flooding reduction.
Examples
The following example shows how to reduce the flooding of unnecessary LSAs for area 0:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# flood-reduction
Related Commands
hello-interval (OSPF)
To specify the interval between hello packets that are sent on the Open Shortest Path First (OSPF) 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
seconds
|
Interval (in seconds). The value must be the same for all nodes on a specific network. Range is 1 to 65535.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the hello interval parameter specified by the 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 configuration
Virtual-link configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 occurs. This value must be the same for all routers and access servers on a specific network.
Examples
The following example shows how to set the interval between hello packets to 15 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# hello-interval 15
Related Commands
Command
|
Description
|
dead-interval (OSPF)
|
Sets the time period for which hello packets are suspended before neighbors declare the router down.
|
ignore lsa mospf
To suppress the sending of syslog messages when the router receives link-state advertisement (LSA) Type 6 multicast Open Shortest Path First (MOSPF) packets, which are unsupported, use the ignore lsa mospf command in router configuration mode. To restore the sending of syslog messages, use the no form of this command.
ignore lsa mospf
no ignore lsa mospf
Syntax Description
This command has no arguments or keywords.
Defaults
When you do not specify this command in router configuration mode, each MOSPF packet received by the router causes the router to send a syslog message.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Cisco routers do not support LSA Type 6 (MOSPF), and they generate syslog messages if they receive such packets. If the router is receiving many MOSPF packets, you might want to configure the router to ignore the packets and thus prevent a large number of syslog messages.
Examples
The following example shows how to configure the router to suppress the sending of syslog messages when it receives MOSPF packets:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# ignore lsa mospf
interface (OSPF)
To define the interfaces on which the Open Shortest Path First (OSPF) protocol runs, use the interface command in area configuration mode. To disable OSPF routing for interfaces, use the no form of this command.
interface type instance
no interface type instance
Syntax Description
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
When you do not specify this command in configuration mode, OSPF routing for interfaces is not enabled.
Command Modes
Area configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 area. The interface remains associated with the area even when the IP address of the interface changes.
Examples
The following example shows how the OSPF routing process 109 defines four OSPF areas (0, 2, 3, and 10.9.50.0), and associates an interface with each area:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS4/0/0/3
RP/0/RP0/CPU0:router(config-ospf)# area 2
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/3
RP/0/RP0/CPU0:router(config-ospf)# area 3
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS3/0/0/2
RP/0/RP0/CPU0:router(config-ospf)# area 10.9.50.0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS3/0/0/1
log adjacency changes (OSPF)
To configure the router to send a syslog message when the state of an Open Shortest Path First (OSPF) neighbor changes, use the log adjacency changes command in router configuration mode. To turn off this function, use the disable keyword. To log all state changes, use the detail keyword.
log adjacency changes [detail | disable]
Syntax Description
detail
|
(Optional) Provides detailed information about adjacency changes.
|
disable
|
(Optional) Disables sending adjacency change messages.
|
Defaults
The router sends a syslog message when the state of an OSPF neighbor changes.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 log adjacency changes command to display high-level changes to the state of the peer relationship. Configure this command if you want to know about OSPF neighbor changes.
Examples
The following example shows how to configure the software to send a syslog message for any OSPF neighbor state changes:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# log adjacency changes enable
max-metric
To configure the Open Shortest Path First (OSPF) protocol to signal other networking devices not to prefer the local router as an intermediate hop in their shortest path first (SPF) calculations, use the max-metric command in router configuration mode. To disable this function, use the no form of this command.
max-metric router-lsa [on-startup {wait-for-bgp | announce-time}]
no max-metric router-lsa
Syntax Description
router-lsa
|
Always originates router link-state advertisements (LSAs) with the maximum metric.
|
on-startup
|
(Optional) Sets the maximum metric temporarily after a reboot.
|
wait-for-bgp
|
(Optional) Causes OSPF to originate router LSAs with the maximum metric and allows Border Gateway Protocol (BGP) to decide when to start originating router LSAs with a normal metric instead of the maximum metric.
|
announce-time
|
(Optional) The time (in seconds) that router LSAs are originated with the maximum metric of 0XFFFF.
|
Defaults
Router LSAs are originated with normal link metrics.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 max-metric command to cause the software to originate router LSAs with router link metrics set to LSInfinity (0XFFFF). This feature can be useful in Internet backbone routers that run both OSPF and BGP because OSPF converges more quickly than BGP and may begin attracting traffic before BGP has converged, resulting in dropped traffic.
If this command is configured, the router advertises its locally generated router LSAs with a metric of 0XFFFF. This action allows the router to converge but not attract transit traffic if there are better, alternative paths around this router. After the specified announce-time value or notification from BGP has expired, the router advertises the local router LSAs with the normal metric (interface cost).
If this command is configured with the on-startup keyword, then the maximum metric is temporarily set only after reboot is initiated. If this command is configured without the on-startup keyword, then the maximum metric is permanently used until the configuration is removed.
This command might be useful when you want to connect a router to an OSPF network, but do not want real traffic flowing through it if there are better, alternative paths. If there are no alternative paths, this router still accepts transit traffic as before.
Some cases where this command might be useful are as follows:
•
During a router reload, you prefer that OSPF wait for BGP to converge before accepting transit traffic. If there are no alternative paths, the router still accepts transit traffic.
•
A router is in critical condition (for example, it has a very high CPU load or does not have enough memory to store all LSAs or build the routing table).
•
When you want to gracefully introduce or remove a router to or from the network.
•
When you have a test router in a lab, connected to a production network.
Note
For older OSPF implementations (RFC 1247), router links in received router LSAs with a metric and cost of LSInfinity are not used during SPF calculations. Hence, no transit traffic is set to the routers originating such router LSAs.
Examples
The following example shows how to configure OSPF to originate router LSAs with the maximum metric until BGP indicates that it has converged:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# max-metric router-lsa on-startup wait-for-bgp
maximum interfaces (OSPF)
To limit the number of interfaces that can be configured for an Open Shortest Path First (OSPF) process, use the maximum interfaces command in router configuration mode. To return to the default limit, use the no form of this command.
maximum interfaces number-interfaces
no maximum interfaces
Syntax Description
number-interfaces
|
Number of interfaces. Range is 1 to 1024.
|
Defaults
If the command is not specified, the default is 255.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 maximum interface command to increase or decrease the limit on the number of interfaces configured for an OSPF process.
You cannot configure a limit lower than the number of interfaces currently configured for the OSPF process. To lower the limit, remove interfaces from the OSPF configuration until the number of configured interfaces is at or below the desired limit. You may then apply the new, lower limit.
Examples
The following example shows how to configure a maximum interface limit of 700 on a router:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# maximum interfaces 700
Related Commands
maximum paths (OSPF)
To control the maximum number of parallel routes that the Open Shortest Path First (OSPF) protocol can support, use the maximum paths command in router 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 maximum
no maximum paths
Syntax Description
maximum
|
Maximum number of parallel routes that OSPF 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-1s: 32 paths
Cisco XR 12000 Series Routers: 16 paths
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following example shows how to allow a maximum of two paths to a destination:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# maximum paths 2
maximum redistributed-prefix
To limit the aggregate number of routes that may be redistributed into an Open Shortest Path First (OSPF) process, use the maximum redistributed-prefix command in router configuration mode. To return to the default limit, use the no form of this command.
maximum redistributed-prefix maximum [threshold-value] [warning-only]
no maximum redistributed-prefix
Syntax Description
maximum
|
Number of routes. Range is 1 to 28672.
|
threshold-value
|
(Optional) Threshold value (as a percentage) at which to generate a warning message. Range is 1 to 100.
|
warning-only
|
(Optional) Gives only a warning when the limit is exceeded.
|
Defaults
If the command is not specified, the default is 10000.
The threshold value defaults to 75%.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
The threshold-value argument and warning-only keyword were added.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 maximum redistributed-prefix command to increase or decrease the maximum number of routes redistributed for an OSPF process.
If the maximum value is less than the existing number of routes, existing routes remain configured, but no new routes are redistributed.
Examples
The following example shows how to configure a maximum number of routes that can be redistributed for an OSPF routing process:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# maximum redistributed-prefix 15000
Related Commands
message-digest-key
To enable Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication, use the message-digest-key command in the appropriate mode. To remove an old MD5 key, use the no form of this command.
message-digest-key key-id md5 {key | clear key | encrypted key}
no message-digest-key key-id
Syntax Description
key-id
|
Key number. Range is 1 to 255.
|
md5
|
Enables OSPF MD5 authentication.
|
key
|
Alphanumeric string of up to 16 characters.
|
clear
|
Specifies that the key be clear text.
|
encrypted
|
Specifies that the key be encrypted using a two-way algorithm.
|
Defaults
If this command is not specified in interface configuration mode, then the interface adopts the message digest key parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the message digest key parameter specified for the process.
If this command is not specified at any level, then OSPF MD5 authentication is disabled.
Command Modes
Interface configuration
Area configuration
Router configuration
Virtual-link configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The 0 and 7 keywords were replaced with the clear and encrypted keywords.
|
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.
Usually, one key individual interface is used to generate authentication information when packets are sent and to authenticate incoming packets. The same key identifier on the neighbor router must have the same key value.
For authentication to be enabled, you must configure the message-digest-key command together with the authentication command and its message-digest keyword. Both the message-digest-key and authentication commands can be inherited from a higher configuration level.
The process of changing keys is as follows. Suppose the current configuration is:
message-digest-key 100 md5 OLD
You change the configuration to the following:
message-digest-key 101 md5 NEW
The system assumes its neighbors do not have the new key yet, so it begins a rollover process. It sends multiple copies of the same packet, each authenticated by different keys. In this example, the system sends out two copies of the same packet—the first one authenticated by key 100 and the second one authenticated by key 101.
Rollover allows neighboring routers to continue communication while the network administrator is updating them with the new key. Rollover stops after the local system finds that all its neighbors know the new key. The system detects that a neighbor has the new key when it receives packets from the neighbor authenticated by the new key.
After all neighbors have been updated with the new key, the old key should be removed. In this example, you would enter the following:
no ospf message-digest-key 100
Then, only key 101 is used for authentication on interface 1.
We recommend that you not keep more than one key individual interface. Every time you add a new key, you should remove the old key to prevent the local system from continuing to communicate with a hostile system that knows the old key. Removing the old key also reduces overhead during rollover.
Note
The MD5 key is always stored in encrypted format on the router. The clear and encrypted keywords inform the router whether the value that is entered is encrypted or unencrypted.
Examples
The following example shows how to set a new key 19 with the password 8ry4222:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# message-digest-key 19 md5 8ry4222
Related Commands
mpls traffic-eng area (OSPF)
To configure an Open Shortest Path First (OSPF) area for Multiprotocol Label Switching traffic engineering (MPLS TE), use the mpls traffic-eng area command in router configuration mode. To remove the MPLS TE area, use the no form of this command.
mpls traffic-eng area area-id
no mpls traffic-eng area area-id
Syntax Description
area-id
|
Integer that specifies an OSPF area in which MPLS TE is supported. Currently only one area is supported.
|
Defaults
MPLS TE is not configured for OSPF.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 mpls traffic-eng area command for OSPF to support MPLS traffic engineering. OSPF provides the flooding mechanism that is used to flood TE link information.
We recommend that you configure the mpls traffic-eng router-id command instead of using the router-id command in global configuration mode.
OSPF support for MPLS TE is a component of the overall MPLS TE feature. Other MPLS TE software components must also be configured for this feature to be fully supported.
Examples
The following example shows how to associate loopback interface 0 with area 0, and area 0 is declared to be an MPLS area:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# router-id 10.10.10.10
RP/0/RP0/CPU0:router(config-ospf)# mpls traffic-eng router-id loopback 0
RP/0/RP0/CPU0:router(config-ospf)# mpls traffic-eng area 0
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface loopback 0
Related Commands
mpls traffic-eng router-id (OSPF)
To specify that the traffic engineering router identifier for the node is the IP address associated with a given Open Shortest Path First (OSPF) interface, use the mpls traffic-eng router-id command in router configuration mode. To disable this feature, use the no form of this command.
mpls traffic-eng router-id {router-id | interface-type interface-instance}
no mpls traffic-eng router-id {ip-address | interface-type interface-number}
Syntax Description
router-id
|
The 32-bit router ID value specified in four-part, dotted-decimal notation (must be in the valid IP address range of 0.0.0.0 to 255.255.255.255).
|
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
If this command is specified in router configuration mode, then the traffic engineering router identifier for the node is the IP address associated with a given interface.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
This identifier of the router acts as a stable IP address for the traffic engineering configuration. This IP address is flooded to all nodes. For all traffic engineering tunnels originating at other nodes and ending at this node, you must set the tunnel destination to the traffic engineering router identifier of the destination node, because that is the address that the traffic engineering topology database at the tunnel head uses for its path calculation.
Note
We recommend that loopback interfaces be used for Multiprotocol Label Switching traffic engineering (MPLS TE) because they are more stable than physical interfaces.
Examples
The following example shows how to specify the traffic engineering router identifier as the IP address associated with loopback interface 0:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# mpls traffic-eng router-id loopback 0
Related Commands
mtu-ignore (OSPF)
To prevent Open Shortest Path First (OSPF) 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 reset to default, use the no form of this command.
mtu-ignore [disable | enable]
no mtu-ignore
Syntax Description
disable
|
(Optional) Enables checking for whether OSPF neighbors are using the MTU on a common interface.
|
enable
|
(Optional) Disables checking for whether OSPF neighbors are using the MTU on a common interface.
|
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 OSPF checks the MTU received from neighbors when exchanging DBD packets.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
The disable keyword was added.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 with the enable keyword to check whether OSPF 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.
Examples
The following example shows how to disable MTU mismatch detection on receiving DBD packets:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# mtu-ignore
neighbor (OSPF)
To configure Open Shortest Path First (OSPF) 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 ip-address [cost number] [priority number] [poll-interval seconds]
no neighbor ip-address [cost number] [priority number] [poll-interval seconds]
Syntax Description
ip-address
|
Interface IP address of the neighbor.
|
cost number
|
(Optional) Assigns a cost to the neighbor, in the form of an integer from 1 to 65535. Neighbors with no specific cost configured assume the cost of the interface, based on the cost command. On point-to-multipoint interfaces, cost number is the only keyword and argument combination that works. The cost keyword does not apply to nonbroadcast multiaccess (NBMA) networks.
|
priority number
|
(Optional) Specifies an 8-bit number indicating the router priority value of the nonbroadcast neighbor associated with the IP address specified. The priority keyword does not apply to point-to-multipoint interfaces.
|
poll-interval seconds
|
(Optional) Specifies an unsigned integer value (in seconds) reflecting the poll interval. RFC 1247 recommends that this value be much larger than the hello interval. The poll-interval keyword does not apply to point-to-multipoint interfaces.
|
Defaults
No configuration is specified.
priority number: 0
poll-interval seconds: 120 seconds (2 minutes)
Command Modes
Interface configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 include one neighbor entry in the software configuration for each known nonbroadcast network neighbor. The neighbor address must be on the primary address of the interface.
If a neighboring router has become inactive (hello packets have not been received 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 start sending hello packets to all neighbors to form adjacencies.
To filter all outgoing OSPF link-state advertisement (LSA) packets for the neighbor, use the neighbor database-filter all out command.
Examples
The following example shows how to declare a router at address 172.16.3.4 on a nonbroadcast network, with a priority of 1 and a poll interval of 180 seconds:
RP/0/0/0:router(config-ospf-ar-if)# neighbor 172.16.3.4 priority 1 poll-interval 180
The following example illustrates a network with nonbroadcast:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS1/0/0/3
RP/0/RP0/CPU0:router(config-if)# ip address 172.16.3.10 255.255.255.0
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# network nonbroadcast
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.4 priority 1 poll-interval 180
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.5 cost 10 priority 1
poll-interval 180
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.6 cost 15 priority 1
poll-interval 180
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.7 priority 1 poll-interval 180
Related Commands
neighbor database-filter all out
To filter all outgoing link-state advertisements (LSAs) to an Open Shortest Path First (OSPF) neighbor, use the neighbor database-filter all out command in interface configuration mode. To restore the forwarding of LSAs to the neighbor, use the no form of this command.
neighbor ip-address database-filter all out
no neighbor ip-address database-filter all out
Syntax Description
ip-address
|
IP address of the neighbor to which outgoing LSAs are blocked.
|
Defaults
Instead of all outgoing LSAs being filtered to the neighbor, they are flooded to the neighbor.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 neighbor database-filter all out command to filter all outgoing OSPF LSA packets during synchronization and flooding for point-to-multipoint neighbors on nonbroadcast networks. More neighbor options are available with the neighbor command.
Examples
The following example shows how to prevent flooding of OSPF LSAs to point-to-multipoint networks to the neighbor at IP address 10.2.3.4:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 10.2.3.4 database-filter all out
Related Commands
Command
|
Description
|
neighbor (OSPF)
|
Configures OSPF routers interconnecting to nonbroadcast networks.
|
network (OSPF)
To configure the Open Shortest Path First (OSPF) 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
broadcast
|
Sets the network type to broadcast.
|
non-broadcast
|
Sets the network type to nonbroadcast multiaccess (NBMA).
|
point-to-multipoint
|
Sets the network type to point-to-multipoint.
|
non-broadcast
|
(Optional) Sets the point-to-multipoint network to be nonbroadcast. If you use this keyword, the neighbor command is required.
|
point-to-point
|
Sets the network type to point-to-point.
|
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 OSPF network type is the default of the given medium.
POS interfaces default to point-to-point and GigE and TenGigE interfaces default to broadcast.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF network type as a point-to-multipoint network. Routing between two routers that are not directly connected go through the router that has virtual circuits to both routers. You need not configure neighbors when using this command.
If this command is issued on an interface that does not allow it, this command is ignored.
OSPF has two features related to point-to-multipoint networks. One feature applies to broadcast networks; the other feature applies to nonbroadcast networks:
•
On point-to-multipoint, broadcast networks, you can use the neighbor command, and you must specify a cost to that neighbor.
•
On point-to-multipoint, nonbroadcast networks, you must use the neighbor command to identify neighbors. Assigning a cost to a neighbor is optional.
Examples
The following example shows how to configure the OSPF network as a nonbroadcast network:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.4 priority 1 poll-interval 180
Related Commands
Command
|
Description
|
neighbor (OSPF)
|
Configures OSPF routers interconnecting to nonbroadcast networks.
|
nsf (OSPF)
To configure nonstop forwarding (NSF) for the Open Shortest Path First (OSPF) protocol, use the nsf command in router configuration mode. To remove this command from the configuration file and restore the system to its default condition, use the no form of this command.
nsf {cisco [enforce global] | ietf [helper disable]}
no nsf {[cisco [enforce global] | ietf [helper disable]}
Syntax Description
cisco
|
Enables Cisco Nonstop Forwarding.
|
enforce global
|
(Optional) Cancels NSF restart when non-NSF network device neighbors are detected.
|
ietf
|
Enables Internet Engineering Task Force (IETF) graceful restart.
|
helper disable
|
(Optional) Disables router helper support.
|
Defaults
NSF is disabled.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 NSF feature allows for the forwarding of data packets to continue along known routes while routing protocol information (such as OSPF) is being restored following a switchover.
Use the nsf command if the router is expected to perform NSF during restart. To experience the full benefits of this feature, configure all neighboring routers with NSF.
When this command is used without the optional cisco enforce global keywords and non-NSF neighbors are detected, the NSF restart mechanism aborts on the interfaces of those neighbors and functions properly on others.
When this command is used with the optional cisco enforce global keywords and non-NSF neighbors are detected, NSF restart is canceled for the entire OSPF process.
IETF restart provides an NSF mechanism that lets data seamlessly flow with no packet drops during the transient period when OSPF attempts to recover after a process restart or RP failover, within the guidelines of RFC 3623.
By default, neighbors in helper mode listen to both the NSF Cisco- and NSF IETF-type LSAs. The nsf command enables one type of mechanism that would undergo an RP failover or, anticipating an OSPF process restart. If the cisco or ietf keywords are not entered, NSF is not enabled, irrespective of neighbors in listening mode for both NSF Cisco and NSF IETF.
Examples
The following example shows how to cancel NSF restart for the entire OSPF process if non-NSF neighbors are detected on any network interface during restart:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# nsf cisco enforce global
nsf interval (OSPF)
To configure the minimum time between nonstop forwarding (NSF) restart attempts for the Open Shortest Path First (OSPF) protocol, use the nsf interval command in router configuration mode. To remove this command from the configuration file and restore the system to its default condition, use the no form of this command.
nsf interval seconds
no nsf interval seconds
Syntax Description
seconds
|
Length of time (in seconds) between restart attempts. Range is 90 to 3600 seconds.
|
Defaults
seconds: 90
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 you use the nsf interval command, the OSPF process must be up for at least 90 seconds before OSPF attempts to perform an NSF restart.
Examples
The following example shows how to configure the minimum time between NSF restart attempts at 120 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# nsf interval 120
nsf lifetime (OSPF)
To configure the maximum time that routes are held in the Routing Information Base (RIB) following an Open Shortest Path First (OSPF) process restart, use the nsf lifetime command in router configuration mode. To remove this command from the configuration file and restore the system to its default condition, use the no form of this command.
nsf lifetime seconds
no nsf lifetime seconds
Syntax Description
seconds
|
The length of time (in seconds) that routes are held in the RIB. Range is 90 to 3600 seconds.
|
Defaults
seconds: 90
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 you use this command, the OSPF process must reconverge within the maximum length of time configured. If the convergence exceeds this length of time, routes are purged out of RIB and nonstop forwarding (NSF) restart may fail.
Examples
The following example shows how to configure the maximum lifetime for OSPF NSF at 120 seconds:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# nsf lifetime 120
nssa (OSPF)
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] [no-summary]
no nssa
Syntax Description
no-redistribution
|
(Optional) Imports routes only into the normal areas, but not into the NSSA area, by the redistribute command when the router is an NSSA Area Border Router (ABR).
|
default-information- originate
|
(Optional) Generates a Type 7 default into the NSSA area. This keyword takes effect only on an NSSA ABR or NSSA Autonomous System Boundary Router (ASBR).
|
no-summary
|
(Optional) Prevents an ABR from sending summary link advertisements into the NSSA.
|
Defaults
No NSSA area is defined.
Command Modes
Area configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 NSSA does not flood Type 5 external LSAs from the core into the area, but can import autonomous system external routes in a limited fashion within the area.
Examples
The following example shows how to configure area 1 as an NSSA area:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 1
RP/0/RP0/CPU0:router(config-ospf-ar)# nssa
ospf name-lookup
To configure the Open Shortest Path First (OSPF) protocol to look up Domain Name System (DNS) names, use the ospf name-lookup command in global configuration mode. To disable this function, use the no form of this command.
ospf name-lookup
no ospf 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
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf name-lookup command to easily to identify a router when executing all OSPF show command displays. The router is displayed by name rather than by its router ID or neighbor ID.
Examples
The following example shows how to configure OSPF to identify a router by name:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# ospf name-lookup
packet-size
To configure the size of Open Shortest Path First (OSPF) packets up to the size specified by the maximum transmission unit (MTU), use the packet-size command in the appropriate router configuration 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
bytes
|
Size in bytes. Range is 576 to 10000 bytes.
|
Defaults
If command is not specified, the default packet size is 1500 bytes.
Command Modes
Router configuration
Area configuration
Interface configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF packets. The OSPF protocol compares the packet size and the MTU size and uses the lower packet size value.
Examples
The following example shows how to configure the packet size on an interface:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/2
RP/0/RP0/CPU0:router(config-ospf-ar-if)# packet-size 3500
passive (OSPF)
To suppress the sending of Open Shortest Path First (OSPF) updates on an interface, use the passive command in the appropriate configuration mode. To remove the passive configuration, use the no form of this command.
passive [enable | disable]
no passive
Syntax Description
enable
|
(Optional) Suppresses OSPF updates.
|
disable
|
(Optional) Sends OSPF updates.
|
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 OSPF updates are sent on the interface.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 interface. The interface appears as a stub network in the OSPF Router (Type 1) link-state advertisement (LSA).
Examples
The following example shows that Packet-over-SONET (POS) interface 1/0/0/2 reduces OSPF updates because passive mode is enabled; however, POS interface 0/1/0/3 receives normal OSPF traffic flow:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/2
RP/0/RP0/CPU0:router(config-ospf-ar-if)# passive enable
RP/0/RP0/CPU0:router(config-ospf-ar-if)# exit
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS1/0/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# end
priority (OSPF)
To set the router priority for an interface, which helps determine the designated router for an Open Shortest Path First (OSPF) link, use the priority command in the appropriate configuration mode. To return to the default value, use the no form of this command.
priority value
no priority value
Syntax Description
value
|
8-bit unsigned integer indicating the router priority value. Range is 0 to 255.
|
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 for the process.
If this command is not specified at any level, then the default priority is 1.
Command Modes
Interface configuration
Area configuration
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 multiaccess networks (in other words, not point-to-point networks).
This priority value is used when you configure the Open Shortest Path First (OSPF) protocol for nonbroadcast networks using the neighbor command for OSPF.
Examples
The following example shows that priority is set through the priority and neighbor commands for Routers A and B and that the neighbor priority value must reflect that of the neighbor router:
Router A
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.0.0.2 255.255.255.0
RP/0/RP0/CPU0:router(config-if)# exit
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RP0/CPU0:router(config-ospf-ar-if)# priority 4
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 10.0.0.1 priority 6
Router B
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:router(config-if)# exit
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/2/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RP0/CPU0:router(config-ospf-ar-if)# priority 6
RP/0/RP0/CPU0:router(config-ospf-ar-if)# neighbor 10.0.0.2 priority 4
Related Commands
Command
|
Description
|
neighbor (OSPF)
|
Configures OSPF routers interconnecting to nonbroadcast networks.
|
network (OSPF)
|
Configures the OSPF network type to a type other than the default for a given medium.
|
range (OSPF)
To consolidate and summarize routes at an area boundary, use the range command in area configuration mode. To disable this function, use the no form of this command.
range ip-address mask [advertise | not-advertise]
no range address mask [advertise | not-advertise]
Syntax Description
ip-address
|
IP address in four-part, dotted-decimal notation.
|
mask
|
IP address mask.
|
advertise
|
(Optional) Sets the address range status to advertise and generates a Type 3 summary link-state advertisement (LSA).
|
not-advertise
|
(Optional) Sets the address range status to DoNotAdvertise. The Type 3 summary LSA is suppressed and the component networks remain hidden from other networks.
|
Defaults
When this command is not specified for Area Border Routers (ABRs), routes at an area boundary are not consolidated or summarized. The default for the optional parameter is advertise.
Command Modes
Area configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 Router (ABRs). Use the command 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.
Multiple range configurations specifying the range command can be configured. Thus, the OSPF protocol can summarize addresses for many different sets of address ranges.
Examples
The following example shows area 36.0.0.0 consisting of interfaces whose IP addresses have "10.31.x.x" as the first two octets. The range command summarizes interfaces. Instead of advertising eight networks individually, the single route 10.31.0.0 255.255.0.0 is advertised:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 201
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS 0/3/0/2
RP/0/RP0/CPU0:router(config-ospf)# area 36.0.0.0
RP/0/RP0/CPU0:router(config-ospf-ar)# range 10.31.0.0 255.255.0.0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS0/1/0/0
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/1/0/0
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/1/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/1/0/2
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/1/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/2/0/0
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/2/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/2/0/2
RP/0/RP0/CPU0:router(config-ospf-ar-if)# interface POS0/2/0/3
RP/0/RP0/CPU0:router(config-ospf-ar-if)# end
redistribute (OSPF)
To redistribute routes from one routing domain into OSPF, use the redistribute command in router 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]
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 (OSPF)
redistribute ospf 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 ospf process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]}[metric
metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
IP Static Routes
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
bgp
|
Distributes routes from the BGP protocol.
|
process-id
|
For the bgp keyword, an autonomous system number, which is a 16-bit decimal number. Range is 1 to 65535.
For the isis keyword, an IS-IS instance name from which routes are to be redistributed. The value takes the form of a string. A decimal number can be entered, but it is stored internally as a string.
For the ospf keyword, an OSPF instance name from which routes are to be redistributed. The value takes the form of a string. A decimal number can be entered, but it is stored internally as a string.
|
metric metric-value
|
(Optional) Specifies the metric used for the redistributed route. Range is 1 to 16777214. Use a value consistent with the source protocol.
|
metric-type {1 | 2}
|
(Optional) Specifies the external link type associated with the route advertised into the OSPF routing domain. It can be one of two values:
• 1—Type 1 external route
• 2—Type 2 external route
|
tag tag-value
|
(Optional) Specifies the 32-bit dotted-decimal value attached to each external route. This value is not used by the OSPF protocol itself, but is carried in the External LSAs. Range is 0 to 4294967295.
|
policy policy-name
|
(Optional) Specifies the identifier of a configured policy. A policy is used to filter the importation of routes from this source routing protocol to OSPF.
|
connected
|
Distributes routes that are established automatically by virtue of having enabled IP on an interface.
|
isis
|
Distributes routes from the IS-IS protocol.
|
level-1
|
(Optional) Redistributes Level 1 routes into other IP routing protocols independently.
|
level-1-2
|
(Optional) Distributes both Level 1 and Level 2 routes into other IP routing protocols.
|
level-2
|
(Optional) Distributes Level 2 routes into other IP routing protocols independently.
|
ospf
|
Distributes routes from the OSPF protocol.
|
match {internal | external [1 | 2] | nssa-external [1 | 2]}
|
(Optional) Specifies the criteria by which OSPF routes are redistributed into other routing domains. It can be one or more of the following:
• internal—Routes that are internal to a specific autonomous system (intra- and inter-area OSPF routes).
• external [1 | 2]—Routes that are external to the autonomous system, but are imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [1 | 2]—Routes that are external to the autonomous system, but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA) external routes.
For the external and nssa-external options, if a type is not specified, then both Type 1 and Type 2 are assumed.
If no match is specified, the default is no filtering.
|
static
|
Redistributes IP static routes.
|
Defaults
Route redistribution is disabled.
metric metric-value: Default is 20 for routes from all protocols except BGP routes, for which the default is 1.
metric-type: Type 2 external route
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Redistributed routing information should always be filtered by the policy policy-name keyword and argument. This filtering ensures that only those routes intended by the administrator are redistributed by OSPF.
For information about routing policies, see the Routing Policy Commands on Cisco IOS XR Software module of the Cisco IOS XR Routing Command Reference.
OSPF Considerations
Whenever you use the redistribute or default-information originate (OSPF) command to redistribute routes into an OSPF routing domain, the router automatically becomes an ASBR. However, an ASBR does not, by default, generate a default route into the OSPF routing domain.
When routes are redistributed between OSPF processes, no OSPF 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.
Examples
The following example shows how to cause BGP routes to be redistributed into an OSPF domain:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 110
RP/0/RP0/CPU0:router(config-ospf)# redistribute bgp 100
The following example shows how to redistribute the specified IS-IS process routes into an OSPF domain. The IS-IS routes are redistributed with a metric of 100.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# redistribute isis 108 metric 100
In the following example, network 10.0.0.0 appears as an external link-state advertisement (LSA) in OSPF 1:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/1
RP/0/RP0/CPU0:router(config-if)# ip address 10.0.0.0 255.0.0.0
RP/0/RP0/CPU0:router(config)# interface POS 0/2/0/2
RP/0/RP0/CPU0:router(config)# ip address 10.99.0.0 255.0.0.0
RP/0/RP0/CPU0:router(config)# router ospf 1
RP/0/RP0/CPU0:router(config-ospf)# redistribute ospf 2
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/2/0/2
RP/0/RP0/CPU0:router(config)# router ospf 2
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/1/0/1
Related Commands
retransmit-interval (OSPF)
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the Open Shortest Path First (OSPF) interface, use the retransmit-interval command in the appropriate configuration 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 for 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 configuration
Virtual-link configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following example shows how to set the retransmit interval value to 8 seconds in interface configuration mode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 201
RP/0/RP0/CPU0:router(config-ospf)# area 0
RP/0/RP0/CPU0:router(config-ospf-ar)# interface POS 0/2/0/1
RP/0/RP0/CPU0:router(config-ospf-ar-if)# retransmit-interval 8
router-id (OSPF)
To configure a router ID for the Open Shortest Path First (OSPF) process, use the router-id command in router 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 | interface-type interface-instance}
no router-id {router-id | interface-type interface-instance}
Syntax Description
router-id
|
32-bit router ID value specified in four-part, dotted-decimal notation.
|
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
If this command is not configured, the router ID is the highest IP version 4 (IPv4) address for an interface on the router, with any loopback interface taking precedence.
Command Modes
Router configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
It is good practice to use the router-id command to explicitly specify a unique 32-bit numeric value for the router ID. This action ensures that OSPF can function regardless of the interface address configuration.
OSPF attempts to obtain a router ID from the following sources, in order of decreasing preference:
1.
The 32-bit numeric value specified by the OSPF router-id command in router configuration mode. (This value can be any 32-bit value. It is not restricted to the IPv4 addresses assigned to interfaces on this router, and need not be a routable IPv4 address.)
2.
The primary IPv4 address of the interface specified by the OSPF router-id command.
3.
The 32-bit numeric value specified by the router-id command in global configuration mode. (This value must be an IPv4 address assigned to an interface on this router.)
4.
The primary IPv4 address of the interface specified by the router-id command in global configuration mode.
5.
The highest IPv4 address assigned to any loopback interface.
6.
The primary IPv4 address of an interface over which this OSPF process is running.
Note
Unlike OSPF version 3, OSPF version 2 is guaranteed to have at least one interface with an IPv4 address configured.
Examples
The following example shows how to assign the IP address of 172.20.10.10 to the OSPF process 109:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
RP/0/RP0/CPU0:router(config-ospf)# router-id 172.20.10.10
Related Commands
Command
|
Description
|
clear ospf process
|
Resets an OSPF router process without stopping and restarting it.
|
ipv4 address
|
Sets a primary IPv4 address for an interface.
|
router ospf
To configure an Open Shortest Path First (OSPF) routing process, use the router ospf command in global configuration mode. To terminate an OSPF routing process, use the no form of this command.
router ospf process-name
no router ospf process-name
Syntax Description
process-name
|
Name that uniquely identifies an OSPF routing process. The process name is any alphanumeric string no longer than 40 characters without spaces.
|
Defaults
No OSPF routing process is defined.
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 OSPF routing processes in each router.
All OSPF configuration commands must be configured under an OSPF routing process. For example, two of these commands are the default-metric command and the router-id command.
Examples
The following example shows how to instantiate an OSPF routing process called 109:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router ospf 109
Related Commands
show ospf
To display general information about Open Shortest Path First (OSPF) routing processes, use the show ospf command in EXEC mode.
show ospf [process-name]
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only information for the specified routing process is displayed.
|
Defaults
IPv4 and unicast address prefixes
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf command to provide basic information about the OSPF processes running on the router. Additional options provide in-depth information.
Examples
The following is sample output from the show ospf command:
RP/0/RP0/CPU0:router# show ospf
Routing Process "ospf 1" with ID 1.1.1.1
Supports only single TOS(TOS0) routes
It is an area border router
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Initial LSA throttle delay 500 msecs
Minimum hold time for LSA throttle 5000 msecs
Maximum wait time for LSA throttle 5000 msecs
Minimum LSA interval 5000 msecs. Minimum LSA arrival 1 secs
Maximum number of configured interfaces 255
Number of external LSA 0. Checksum Sum 00000000
Number of opaque AS LSA 0. Checksum Sum 00000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 2. 2 normal 0 stub 0 nssa
External flood list length 0
Non-Stop Forwarding enabled
Area BACKBONE(0) (Inactive)
Number of interfaces in this area is 2
SPF algorithm executed 8 times
Number of LSA 2. Checksum Sum 0x01ba83
Number of opaque link LSA 0. Checksum Sum 00000000
Number of DCbitless LSA 0
Number of indication LSA 0
Number of interfaces in this area is 1
SPF algorithm executed 9 times
Number of LSA 2. Checksum Sum 0x0153ea
Number of opaque link LSA 0. Checksum Sum 00000000
Number of DCbitless LSA 0
Number of indication LSA 0
Table 68 describes the significant fields shown in the display.
Table 68 show ospf Field Descriptions
Field
|
Description
|
Routing Process "ospf 201" with ID 172.22.110.200
|
OSPF process name.
|
Supports only
|
Number of types of service supported (Type 0 only).
|
It is
|
Types are internal, area border, or autonomous system boundary.
|
Redistributing External Routes from
|
Lists of redistributed routes, by protocol.
|
SPF schedule delay
|
Delay time of SPF calculations.
|
Minimum LSA interval
|
Minimum interval between LSAs.
|
Minimum LSA arrival
|
Minimum elapsed time between accepting an update for the same link-state advertisement (LSA).
|
external LSA
|
Total number of Type 5 LSAs in the LSDB.
|
opaque LSA
|
Total number of Type 10 LSAs in the LSDB.
|
DCbitless...AS LSA
|
Total number of Demand Circuit Type 5 and Type 11 LSAs.
|
DoNotAge...AS LSA
|
Total number of Type 5 and Type 11 LSAs with the DoNotAge bit set.
|
Number of areas
|
Number of areas in router, area addresses, and so on.
|
Area BACKBONE
|
Backbone is area 0.
|
show ospf border-routers
To display the internal Open Shortest Path First (OSPF) routing table entries to an Area Border Router (ABR) and Autonomous System Boundary Router (ASBR), use the show ospf border-routers command in EXEC mode.
show ospf [process-name] border-routers [router-id]
Syntax Description
process-name
|
(Optional) OSPF process name. If this argument is included, only information for the specified routing process is included.
|
router-id
|
(Optional) Router ID associated with the border router. The router-id can be any 32-bit router ID value specified in four-part, dotted-decimal notation. No default exists.
|
Defaults
IPv4 and unicast address prefixes
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router. The router-id argument was added.
|
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 ospf border-routers command to list all OSPF border routers visible to the specified processes and also to ascertain the OSPF topology of the router.
Examples
The following is sample output from the show ospf border-routers command:
RP/0/RP0/CPU0:router# show ospf border-routers
OSPF 1 Internal Routing Table
Codes: i - Intra-area route, I - Inter-area route
i 172.31.97.53 [1] via 172.16.1.53, POS 3/0/0/0, ABR/ASBR , Area 0, SPF 3
Table 69 describes the significant fields shown in the display.
Table 69 show ospf border-routers Field Descriptions
Field
|
Description
|
i
|
Type of this route; i indicates an intra-area route, I an interarea route.
|
172.31.97.53
|
Router ID of destination.
|
[1]
|
Cost of using this route.
|
172.16.1.53
|
Next hop toward the destination.
|
POS 3/0/0/0
|
Packets destined for 172.16.1.53 are sent over Packet-over-SONET (POS) interface 3/0/0/0.
|
ABR/ASBR
|
Router type of the destination; it is either an Area Border Router (ABR) or Autonomous System Boundary Router (ASBR) or both.
|
Area 0
|
Area ID of the area from which this route is learned.
|
SPF 3
|
Internal number of the shortest path first (SPF) calculation that installs this route.
|
show ospf database
To display lists of information related to the Open Shortest Path First (OSPF) database for a specific router, use the show ospf database command in EXEC mode.
show ospf [process-name] [area-id] database
show ospf [process-name] [area-id] database [adv-router ip-address]
show ospf [process-name] [area-id] database [asbr-summary] [link-state-id]
show ospf [process-name] [area-id] database [asbr-summary] [link-state-id] [adv-router
[ip-address]]
show ospf [process-name] [area-id] database [asbr-summary] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [database-summary]
show ospf [process-name] [area-id] database [external] [link-state-id]
show ospf [process-name] [area-id] database [external] [link-state-id] [adv-router [ip-address]]
show ospf [process-name] [area-id] database [external] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [network] [link-state-id]
show ospf [process-name] [area-id] database [network] [link-state-id] [adv-router [ip-address]]
show ospf [process-name] [area-id] database [network] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [nssa-external] [link-state-id]
show ospf [process-name] [area-id] database [nssa-external] [link-state-id] [adv-router
[ip-address]]
show ospf [process-name] [area-id] database [nssa-external] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [opaque-area] [link-state-id]
show ospf [process-name] [area-id] database [opaque-area] [link-state-id] [adv-router]
[ip-address]]
show ospf [process-name] [area-id] database [opaque-area] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [opaque-as] [link-state-id]
show ospf [process-name] [area-id] database [opaque-as] [link-state-id] [adv-router
[ip-address]]
show ospf [process-name] [area-id] database [opaque-as] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [opaque-link] [link-state-id]
show ospf [process-name] [area-id] database [opaque-link] [link-state-id] [adv-router
[ip-address]]
show ospf [process-name] [area-id] database [opaque-link] [link-state-id] [self-originate]
show ospf [process-name] [area-id] database [router] [link-state-id]
show ospf [process-name] [area-id] database [router] [adv-router [ip-address]]
show ospf [process-name] [area-id] database [router] [self-originate] [link-state-id]
show ospf [process-name] [area-id] database [self-originate]
show ospf [process-name] [area-id] database [summary] [link-state-id]
show ospf [process-name] [area-id] database [summary] [link-state-id] [adv-router [ip-address]]
show ospf [process-name] [area-id] database [summary] [link-state-id] [self-originate]
[link-state-id]
Syntax Description
process-name
|
(Optional) OSPF process name that uniquely identifies an OSPF routing process. The process name is any alphanumeric string no longer than 40 characters. If this argument is included, only information for the specified routing process is included.
|
area-id
|
(Optional) Area number used to define the particular area.
|
adv-router ip-address
|
(Optional) Displays all LSAs of the specified router.
|
asbr-summary
|
(Optional) Displays information only about the Autonomous System Boundary Router (ASBR) summary LSAs.
|
link-state-id
|
(Optional) Portion of the Internet environment that is being described by the advertisement. The value entered depends on the link-state type of the advertisement. It must be entered in the form of an IP address.
When the link-state advertisement (LSA) is describing a network, the link-state-id can take one of two forms:
• The network IP address (as in Type 3 summary link advertisements and in autonomous system external link advertisements).
• A derived address obtained from the link-state ID.
Note Masking the link-state ID of a network link advertisement with the subnet mask of the network yields the IP address of the network.
When the LSA is describing a router, the link-state ID is always the OSPF router ID of the described router.
When an autonomous system external advertisement (LS Type = 5) is describing a default route, its link-state ID is set to Default Destination (0.0.0.0).
|
self-originate
|
(Optional) Displays only self-originated LSAs (from the local router).
|
database-summary
|
(Optional) Displays how many of each type of LSA for each area there are in the database and the total.
|
external
|
(Optional) Displays information only about the external LSAs.
|
network
|
(Optional) Displays information only about the network LSAs.
|
nssa-external
|
(Optional) Displays information only about the not-so-stubby area (NSSA) external LSAs.
|
opaque-area
|
(Optional) Displays information about the opaque Type 10 LSAs. Type 10 denotes an area-local scope. Refer to RFC 2370 for more information on the opaque LSA options.
|
opaque-as
|
(Optional) Displays information about the opaque Type 11 LSAs. Type 11 denotes that the LSA is flooded throughout the autonomous system.
|
opaque-link
|
(Optional) Displays information about the opaque Type 9 LSAs. Type 9 denotes a link-local scope.
|
router
|
(Optional) Displays information only about the router LSAs.
|
summary
|
(Optional) Displays information only about the summary LSAs.
|
Defaults
IPv4 and unicast address prefixes
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 the show ospf database command deliver information about different OSPF link-state advertisements. This command can be used to examine the link-state database (LSD) and its contents. Each router participating in an area having identical database entries pertaining to that area (with the exception of LSAs that are being flooded). Numerous options (such as network and router) are used to display portions of the database.
Examples
The following is sample output from the show ospf database command when no arguments or keywords are used:
RP/0/RP0/CPU0:router# show ospf database
OSPF Router with ID (172.20.1.11) (Process ID 1)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
172.20.1.8 172.20.1.8 1381 0x8000010D 0xEF60 2
172.20.1.11 172.20.1.11 1460 0x800002FE 0xEB3D 4
172.20.1.12 172.20.1.12 2027 0x80000090 0x875D 3
172.20.1.27 172.20.1.27 1323 0x800001D6 0x12CC 3
Link ID ADV Router Age Seq# Checksum
172.22.1.27 172.20.1.27 1323 0x8000005B 0xA8EE
172.22.1.11 172.20.1.11 1461 0x8000005B 0x7AC
Type-10 Opaque Link Area Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Opaque ID
10.0.0.0 172.20.1.11 1461 0x800002C8 0x8483 0
10.0.0.0 172.20.1.12 2027 0x80000080 0xF858 0
10.0.0.0 172.20.1.27 1323 0x800001BC 0x919B 0
10.0.0.1 172.20.1.11 1461 0x8000005E 0x5B43 1
Table 70 describes the significant fields shown in the display.
Table 70 show ospf database Field Descriptions
Field
|
Description
|
Link ID
|
Router ID number.
|
ADV Router
|
ID of the advertising router.
|
Age
|
Link-state age.
|
Seq#
|
Link-state sequence number (detects old or duplicate LSAs).
|
Checksum
|
Fletcher checksum of the complete contents of the LSA.
|
Link count
|
Number of interfaces detected for the router.
|
Opaque ID
|
Opaque LSA ID number.
|
The following is sample output from the show ospf database command with the asbr-summary keyword:
RP/0/RP0/CPU0:router# show ospf database asbr-summary
OSPF Router with ID (192.168.0.1) (Process ID 300)
Summary ASB Link States (Area 0.0.0.0)
Options: (No TOS-capability)
LS Type: Summary Links (AS Boundary Router)
Link State ID: 172.17.245.1 (AS Boundary Router address)
Advertising Router: 172.17.241.5
Table 71 describes the significant fields shown in the display.
Table 71 show ospf database asbr-summary Field Descriptions
Field
|
Description
|
OSPF Router with ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID (ASBR).
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSAs.
|
Network Mask
|
Network mask implemented.
|
TOS
|
Type of service.
|
Metric
|
Link-state metric.
|
The following is sample output from the show ospf database command with the external keyword:
RP/0/RP0/CPU0:router# show ospf database external
OSPF Router with ID (192.168.0.1) (Process ID 300)
Type-5 AS External Link States
Options: (No TOS-capability)
LS Type: AS External Link
Link State ID: 172.17.0.0 (External Network Number)
Advertising Router: 172.17.70.6
Network Mask: 255.255.0.0
Metric Type: 2 (Larger than any link state path)
Table 72 describes the significant fields shown in the display.
Table 72 show ospf database external Field Descriptions
Field
|
Description
|
OSPF Router with Router ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID (external network number).
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence number (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSA.
|
Network Mask
|
Network mask implemented.
|
Metric Type
|
External type.
|
TOS
|
Type of service.
|
Metric
|
Link-state metric.
|
Forward Address
|
Forwarding address. Data traffic for the advertised destination is forwarded to this address. If the forwarding address is set to 0.0.0.0, data traffic is forwarded instead to the originator of the advertisement.
|
External Route Tag
|
External route tag, a 32-bit field attached to each external route. This tag is not used by the OSPF protocol itself.
|
The following is sample output from the show ospf database command with the network keyword:
RP/0/RP0/CPU0:router# show ospf database network
OSPF Router with ID (192.168.0.1) (Process ID 300)
Net Link States (Area 0.0.0.0)
Options: (No TOS-capability)
Link State ID: 172.23.1.3 (address of Designated Router)
Advertising Router: 192.168.0.1
Attached Router: 192.168.0.1
Attached Router: 172.23.241.5
Attached Router: 172.23.1.1
Attached Router: 172.23.54.5
Attached Router: 172.23.1.5
Table 73 describes the significant fields shown in the display.
Table 73 show ospf database network Field Descriptions
Field
|
Description
|
OSPF Router with ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID of the designated router.
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence number (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSA.
|
Network Mask
|
Network mask implemented.
|
Attached Router
|
List of routers attached to the network, by IP address.
|
The following is sample output, carrying Multiprotocol Label Switching traffic engineering (MPLS TE) specification information, from the show ospf database command with the opaque-area keyword with a link-state-id of adv-router:
RP/0/RP0/CPU0:router# show ospf database opaque-area adv-router 172.20.1.12
OSPF Router with ID (172.20.1.11) (Process ID 1)
Type-10 Opaque Link Area Link States (Area 0)
Options: (No TOS-capability, DC)
LS Type: Opaque Area Link
Advertising Router: 172.20.1.12
MPLS TE router ID : 172.20.1.12
Link connected to Point-to-Point network
Interface Address : 172.21.1.12
Neighbor Address : 172.21.1.11
Maximum bandwidth : 193000
Maximum reservable bandwidth : 125000
Priority 0 : 125000 Priority 1 : 125000
Priority 2 : 125000 Priority 3 : 125000
Priority 4 : 125000 Priority 5 : 125000
Priority 6 : 125000 Priority 7 : 100000
Table 74 describes the significant fields shown in the display.
Table 74 show ospf database opaque-area Field Descriptions
Field
|
Description
|
OSPF Router with ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID.
|
Opaque Type
|
Opaque link-state type.
|
Opaque ID
|
Opaque ID number.
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSA.
|
Fragment number
|
Arbitrary value used to maintain multiple traffic engineering LSAs.
|
Link ID
|
Link ID number.
|
Interface Address
|
ID address of the interface.
|
Neighbor Address
|
IP address of the neighbor.
|
Admin Metric
|
Administrative metric value used by MPLS TE.
|
Maximum bandwidth
|
Specifies maximum bandwidth (in kbps).
|
Maximum reservable bandwidth
|
Specifies maximum reservable bandwidth (in kbps).
|
Number of Priority
|
Priority number.
|
Affinity Bit
|
Used by MPLS TE.
|
The following is sample output from the show ospf database command with the router keyword:
RP/0/RP0/CPU0:router# show ospf database router
OSPF Router with ID (192.168.0.1) (Process ID 300)
Router Link States (Area 0.0.0.0)
Options: (No TOS-capability)
Link State ID: 172.23.21.6
Advertising Router: 172.23.21.6
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 172.23.21.5
(Link Data) Router Interface address: 172.23.21.6
Table 75 describes the significant fields shown in the display.
Table 75 show ospf database router Field Descriptions
Field
|
Description
|
OSPF Router with ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID.
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSA.
|
AS Boundary Router
|
Definition of router type.
|
Number of Links
|
Number of active links.
|
Link ID
|
Link type.
|
Link Data
|
Router interface address.
|
TOS
|
Type of service metric (Type 0 only).
|
The following is sample output from show ospf database command with the summary keyword:
RP/0/RP0/CPU0:router# show ospf database summary
OSPF Router with ID (192.168.0.1) (Process ID 300)
Summary Net Link States (Area 0.0.0.0)
Options: (No TOS-capability)
LS Type: Summary Links (Network)
Link State ID: 172.23.240.0 (Summary Network Number)
Advertising Router: 172.23.241.5
Table 76 describes the significant fields shown in the display.
Table 76 show ospf database summary Field Descriptions
Field
|
Description
|
OSPF Router with ID
|
Router ID number.
|
Process ID
|
OSPF process name.
|
LS age
|
Link-state age.
|
Options
|
Type of service options (Type 0 only).
|
LS Type
|
Link-state type.
|
Link State ID
|
Link-state ID (summary network number).
|
Advertising Router
|
ID of the advertising router.
|
LS Seq Number
|
Link-state sequence (detects old or duplicate LSAs).
|
Checksum
|
Link-state checksum (Fletcher checksum of the complete contents of the LSA).
|
Length
|
Length (in bytes) of the LSA.
|
Network Mask
|
Network mask implemented.
|
TOS
|
Type of service.
|
Metric
|
Link-state metric.
|
The following is sample output from show ospf database command with the database-summary keyword:
RP/0/RP0/CPU0:router# show ospf database database-summary
OSPF Router with ID (172.19.65.21) (Process ID 1)
LSA Type Count Delete Maxage
Process 1 database summary
LSA Type Count Delete Maxage
Table 77 describes the significant fields shown in the display.
Table 77 show ospf database database-summary Field Descriptions
Field
|
Description
|
LSA Type
|
Link-state type.
|
Count
|
Number of advertisements in that area for each link-state type.
|
Delete
|
Number of LSAs that are marked "Deleted" in that area.
|
Maxage
|
Number of LSAs that are marked "Maxaged" in that area.
|
show ospf flood-list
To display a list of Open Shortest Path First (OSPF) link-state advertisements (LSAs) waiting to be flooded over an interface, use the show ospf flood-list command in EXEC mode.
show ospf [process-name] [area-id] flood-list interface-type interface-instance
Syntax Description
process-name
|
(Optional) OSPF process name that uniquely identifies an OSPF routing process. The process name is any alphanumeric string no longer than 40 characters. If this argument is included, only information for the specified routing process is included.
|
area-id
|
(Optional) Area number used to define the particular area.
|
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
All interfaces.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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 ospf flood-list command to display LSAs in flood queue and queue length.
Flood list information is transient and normally the flood lists are empty.
Examples
The following is sample output from the show ospf flood-list command for interface POS 3/0/0/0:
RP/0/RP0/CPU0:router# show ospf flood-list POS 3/0/0/0
Interface POS3/0/0/0, Queue length 20
Link state retransmission due in 12 msec
Displaying 6 entries from flood list:
Type LS ID ADV RTR Seq NO Age Checksum
5 10.2.195.0 200.0.0.163 0x80000009 0 0xFB61
5 10.1.192.0 200.0.0.163 0x80000009 0 0x2938
5 10.2.194.0 200.0.0.163 0x80000009 0 0x757
5 10.1.193.0 200.0.0.163 0x80000009 0 0x1E42
5 10.2.193.0 200.0.0.163 0x80000009 0 0x124D
5 10.1.194.0 200.0.0.163 0x80000009 0 0x134C
Table 78 describes the significant fields shown in the display.
Table 78 show ospf flood-list Field Descriptions
Field
|
Description
|
POS3/0/0/0
|
Interface for which information is displayed.
|
Queue length
|
Number of LSAs waiting to be flooded.
|
Link state retransmission due in
|
Length of time (in milliseconds) before next link-state transmission.
|
Type
|
Type of LSA.
|
LS ID
|
Link-state ID of the LSA.
|
ADV RTR
|
IP address of the advertising router.
|
Seq NO
|
Sequence number of the LSA.
|
Age
|
Age of the LSA (in seconds).
|
Checksum
|
Checksum of the LSA.
|
show ospf interface
To display Open Shortest Path First (OSPF) interface information, use the show ospf interface command in EXEC mode.
show ospf [process-name] [area-id] interface [type instance]
Syntax Description
process-name
|
(Optional) OSPF process name that uniquely identifies an OSPF routing process. The process name is any alphanumeric string no longer than 40 characters. If this argument is included, only information for the specified routing process is included.
|
area-id
|
(Optional) Area number used to define the particular area.
|
type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
All interfaces
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following is sample output from the show ospf interface command when Packet-over-SONET (POS) interface 3/0/0/0 is specified:
RP/0/RP0/CPU0:router# show ospf interface POS3/0/0/0
POS3/0/0/0 is up, line protocol is up
Internet Address 172.16.254.202/24, Area 0
Process ID 1, Router ID 192.77.99.1, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 172.16.254.10, Interface address 172.16.254.10
Backup Designated router (ID) 172.16.254.28, Interface address 172.16.254.28
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Index 1/1, flood queue length 0
Last flood scan length is 3, maximum is 3
Last flood scan time is 1 msec, maximum is 1 msec
Neighbor Count is 8, Adjacent neighbor count is 2
Adjacent with neighbor 172.16.254.28 (Backup Designated Router)
Adjacent with neighbor 172.16.254.10 (Designated Router)
Suppress hello for 0 neighbor(s)
Table 79 describes the significant fields shown in the display.
Table 79 show ospf interface Field Descriptions
Field
|
Description
|
POS
|
Status of the physical link.
|
line protocol
|
Operational status of the protocol.
|
Internet Address
|
Interface IP address, subnet mask, and area address.
|
Process ID
|
OSPF process ID, router ID, network type, and link-state cost.
|
Transmit Delay
|
Transmit delay, interface state, and router priority.
|
Designated Router
|
Designated router ID and respective interface IP address.
|
Backup Designated router
|
Backup designated router ID and respective interface IP address.
|
Timer intervals configured
|
Configuration of timer intervals.
|
Hello
|
Number of seconds until next hello packet is sent over this interface.
|
Index 1/1
|
Area and autonomous system flood indexes.
|
Next 0x0(0)
|
Next area and autonomous system flood information, data pointer, and index.
|
Last flood scan length
|
Length of last flood scan.
|
Last flood scan time
|
Time (in milliseconds) of last flood scan.
|
Neighbor Count
|
Count of network neighbors and list of adjacent neighbors.
|
Suppress hello
|
Count of neighbors suppressing hello messages.
|
show ospf mpls traffic-eng
To display information about the links and fragments available on the local router for traffic engineering, use the show ospf mpls traffic-eng command in EXEC mode.
show ospf [process-name] [area-id] [interface-type interface-instance] mpls traffic-eng {link |
fragment}
Syntax Description
process-name
|
(Optional) OSPF process name that uniquely identifies an OSPF routing process. The process name is any alphanumeric string no longer than 40 characters. If this argument is included, only information for the specified routing process is included.
|
area-id
|
(Optional) Area number used to define the particular area.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
link
|
Provides detailed information about the links over which traffic engineering is supported on the local router.
|
fragment
|
Provides detailed information about the traffic engineering fragments on the local router.
|
Defaults
All links or fragments
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following is sample output from the show ospf mpls traffic-eng command when the link keyword is specified:
RP/0/RP0/CPU0:router# show ospf mpls traffic-eng link
OSPF Router with ID (10.10.10.10) (Process ID 1)
Area 0 has 2 MPLS TE links. Area instance is 67441.
Link is associated with fragment 1. Link instance is 67441
Link connected to Point-to-Point network
Interface Address : 10.10.10.2
Neighbor Address : 10.10.10.3
Maximum bandwidth : 19440000
Maximum global pool reservable bandwidth : 25000000
Maximum sub pool reservable bandwidth : 3125000
Global pool unreserved BW
Priority 0 : 25000000 Priority 1 : 25000000
Priority 2 : 25000000 Priority 3 : 25000000
Priority 4 : 25000000 Priority 5 : 25000000
Priority 6 : 25000000 Priority 7 : 25000000
Priority 0 : 3125000 Priority 1 : 3125000
Priority 2 : 3125000 Priority 3 : 3125000
Priority 4 : 3125000 Priority 5 : 3125000
Priority 6 : 3125000 Priority 7 : 3125000
Link is associated with fragment 0. Link instance is 67441
Link connected to Point-to-Point network
Interface Address : 10.10.25.4
Neighbor Address : 10.10.25.5
Maximum bandwidth : 19440000
Maximum global pool reservable bandwidth : 25000000
Maximum sub pool reservable bandwidth : 3125000
Global pool unreserved BW
Priority 0 : 25000000 Priority 1 : 25000000
Priority 2 : 25000000 Priority 3 : 25000000
Priority 4 : 25000000 Priority 5 : 25000000
Priority 6 : 25000000 Priority 7 : 25000000
Priority 0 : 3125000 Priority 1 : 3125000
Priority 2 : 3125000 Priority 3 : 3125000
Priority 4 : 3125000 Priority 5 : 3125000
Priority 6 : 3125000 Priority 7 : 3125000
Table 80 describes the significant fields shown in the display.
Table 80 show ospf mpls traffic-eng link Field Descriptions
Field
|
Description
|
Link ID
|
Link type.
|
Interface address
|
IP address of the interface.
|
Neighbor address
|
IP address of the neighbor.
|
Admin Metric
|
Administrative distance metric value used by Multiprotocol Label Switching traffic engineering (MPLS TE).
|
Maximum bandwidth
|
Bandwidth capacity of the link (in kbps).
|
Maximum global pool reservable bandwidth
|
Maximum amount of bandwidth that is available for reservation in the global pool.
|
Maximum sub pool reservable bandwidth
|
Maximum amount of bandwidth that is available for reservation in the subpool.
|
Number of Priority
|
Priority number.
|
Global pool unreserved BW
|
Amount of unreserved bandwidth that is available in the global pool.
|
Sub pool unreserved BW
|
Amount of unreserved bandwidth that is available in the subpool.
|
Affinity Bit
|
Used by MPLS TE. Attribute values required for links carrying this tunnel. A 32-bit dotted-decimal number. Valid values are from 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1.
|
The following is sample output from the show ospf mpls traffic-eng command when the fragment keyword is specified:
RP/0/RP0/CPU0:router# show ospf mpls traffic-eng fragment
OSPF Router with ID (10.10.10.10) (Process ID 1)
Area 0 has 2 MPLS TE fragment. Area instance is 67441.
MPLS router address is 10.10.10.10
Fragment 0 has 1 link. Fragment instance is 67441.
Fragment has 1 link the same as last update.
Fragment advertise MPLS router address
Link is associated with fragment 0. Link instance is 67441
Link connected to Point-to-Point network
Interface Address : 10.10.25.4
Neighbor Address : 10.10.25.5
Maximum bandwidth : 19440000
Maximum global pool reservable bandwidth : 25000000
Maximum sub pool reservable bandwidth : 3125000
Global pool unreserved BW
Priority 0 : 25000000 Priority 1 : 25000000
Priority 2 : 25000000 Priority 3 : 25000000
Priority 4 : 25000000 Priority 5 : 25000000
Priority 6 : 25000000 Priority 7 : 25000000
Priority 0 : 3125000 Priority 1 : 3125000
Priority 2 : 3125000 Priority 3 : 3125000
Priority 4 : 3125000 Priority 5 : 3125000
Priority 6 : 3125000 Priority 7 : 3125000
Fragment 1 has 1 link. Fragment instance is 67441.
Fragment has 0 link the same as last update.
Link is associated with fragment 1. Link instance is 67441
Link connected to Point-to-Point network
Interface Address : 10.10.10.2
Neighbor Address : 10.10.10.3
Maximum bandwidth : 19440000
Maximum global pool reservable bandwidth : 25000000
Maximum sub pool reservable bandwidth : 3125000
Global pool unreserved BW
Priority 0 : 25000000 Priority 1 : 25000000
Priority 2 : 25000000 Priority 3 : 25000000
Priority 4 : 25000000 Priority 5 : 25000000
Priority 6 : 25000000 Priority 7 : 25000000
Priority 0 : 3125000 Priority 1 : 3125000
Priority 2 : 3125000 Priority 3 : 3125000
Priority 4 : 3125000 Priority 5 : 3125000
Priority 6 : 3125000 Priority 7 : 3125000
Table 81 describes the significant fields shown in the display.
Table 81 show ospf mpls traffic-eng fragment Field Descriptions
Field
|
Description
|
Area instance
|
Number of times traffic engineering information or any link changed.
|
Link instance
|
Number of times any link changed.
|
Link ID
|
Link type.
|
Interface address
|
IP address of the interface.
|
Neighbor address
|
IP address of the neighbor.
|
Admin Metric
|
Administrative distance metric value used by MPLS TE.
|
Maximum bandwidth
|
Bandwidth capacity of the link (in kbps).
|
Maximum global pool reservable bandwidth
|
Maximum amount of bandwidth that is available for reservation in the global pool.
|
Maximum sub pool reservable bandwidth
|
Maximum amount of bandwidth that is available for reservation in the subpool.
|
Number of Priority
|
Priority number.
|
Global pool unreserved BW
|
Amount of unreserved bandwidth that is available in the global pool.
|
Sub pool unreserved BW
|
Amount of unreserved bandwidth that is available in the subpool.
|
Affinity Bit
|
Used by MPLS TE. Attribute values required for links carrying this tunnel. A 32-bit dotted-decimal number. Valid values are from 0x0 to 0xFFFFFFFF, representing 32 attributes (bits), where the value of an attribute is 0 or 1.
|
show ospf neighbor
To display Open Shortest Path First (OSPF) neighbor information on an individual interface basis, use the show ospf neighbor command in EXEC mode.
show ospf [process-name] [area-id] neighbor [interface-type interface-instance] [neighbor-id]
[detail]
Syntax Description
process-name
|
(Optional) Name that uniquely identifies an OSPF routing process. The process name is defined by the router ospf command. If this argument is included, only information for the specified routing process is displayed.
|
area-id
|
(Optional) Area ID. If you do not specify an area, all areas are displayed.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
neighbor-id
|
(Optional) Neighbor ID.
|
detail
|
(Optional) Displays all neighbors given in detail (lists all neighbors).
|
Defaults
All neighbors
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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.
Examples
The following is sample output from the show ospf neighbor command showing two lines of summary information for each neighbor:
RP/0/RP0/CPU0:router# show ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
192.168.199.137 1 FULL/DR 0:00:31 172.31.80.37 POS 0/3/0/2
Neighbor is up for 18:45:22
192.168.48.1 1 FULL/DROTHER 0:00:33 192.168.48.1 POS 0/3/0/3