-
Cisco IOS IP Routing Protocols Command Reference
-
Introduction
-
BGP Commands: A through B
-
BGP Commands: C through I
-
BGP Commands: M through neighbor soo
-
BGP Commands: neighbor timers through show bgp nsap summary
-
BGP Commands: show ip bgp through T
-
EIGRP Commands: A through I
-
EIGRP Commands: M through V
-
Integrated IS-IS Commands: A through I
-
Integrated IS-IS Commands: L through V
-
On-Demand Routing Commands
-
OSPF Commands: A through ip ospf demand-circuit
-
OSPF Commands: ip ospf flood-reduction through R
-
OSPF Commands: show ip ospf through T
-
IP Routing Protocol-Independent Commands: A through R
-
IP Routing Protocol-Independent Commands: S through T
-
RIP Commands
-
Table Of Contents
ip ospf message-digest-key md5
neighbor database-filter all out
nsf ietf helper strict-lsa-checking
ip ospf flood-reduction
To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the ip ospf flood-reduction command in interface configuration mode. To disable this feature, use the no form of this command.
ip ospf flood-reduction
no ip ospf flood-reduction
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
All routers supporting the Open Shortest Path First (OSPF) demand circuit are compatible and can interact with routers supporting flooding reduction.
Examples
The following example reduces the flooding of unnecessary LSAs on serial interface 0:
interface serial 0ip ospf flood-reductionRelated Commands
show ip ospf interface
Displays OSPF-related interface information.
show ip ospf neighbor
Displays OSPF-neighbor information on a per-interface basis.
ip ospf hello-interval
To specify the interval between hello packets that the Cisco IOS software sends on the interface, use the ip ospf hello-interval command in interface configuration mode. To return to the default time, use the no form of this command.
ip ospf hello-interval seconds
no ip ospf hello-interval
Syntax Description
seconds
Specifies the interval (in seconds). The value must be the same for all nodes on a specific network. The range is from 1 to 65535.
Defaults
10 seconds (Ethernet)
30 seconds (nonbroadcast)
Command Modes
Interface configuration
Command History
Usage Guidelines
This value is advertised in the hello packets. The smaller the hello interval, the faster topological changes will be detected, but more routing traffic will ensue. This value must be the same for all routers and access servers on a specific network.
Examples
The following example sets the interval between hello packets to 15 seconds:
interface ethernet 1ip ospf hello-interval 15Related Commands
ip ospf dead-interval
Sets the time period for which hello packets must not have been seen before neighbors declare the router down.
ip ospf lls
To enable Link-Local Signaling (LLS) on an interface, regardless of the router-level LLS setting, use the ip ospf lls command in interface configuration mode. To reconfigure the router-level LLS setting on the specific interface, use the no or default version of this command.
ip ospf lls [disable]
{no | default} ip ospf lls [disable]
Syntax Description
Defaults
LLS is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
By default, each Open Shortest Path First (OSPF) interface inherits the LLS setting from the router level. The ip ospf lls interface-level command takes precedence over the capability lls router-level command. For example, if you have entered the no capability lls command to disable LLS at the router level, you can use the ip ospf lls command to selectively enable LLS for specific interfaces, in order to allow the router to enable OSPF nonstop forwarding (NSF) awareness only for these specified interfaces.
To unconfigure the interface LLS setting, enter either the default ip ospf lls command or the no ip ospf lls command to restore the default LLS setting for the interface that has been configured at the router level. For example, if the capability lls command is enabled (by default) at the router level, you can use either the default ip ospf lls command or the no ip ospf lls command to disable LLS on specific interfaces, for instance, to interoperate on network segments where there are routers that do not properly handle LLS.
Note
If the network is running OSPF with the LLS feature enabled by default, LLS is globally enabled for all interfaces. If a router in the network is connected to a non-Cisco device that is not in compliance with RFC 2328, there may be network difficulties involving the forming of OSPF neighbors. In this situation, we recommend that you use the ip ospf lls command with the disable keyword to disable LLS on the router that is connected to the non-Cisco device.
Examples
In following example, LLS is disabled on Ethernet interface 2/0:
Router(config)# interface Ethernet2/0Router(config-if)# ip address 10.1.145.2 255.255.0.0Router(config-if)# no ip directed-broadcastRouter(config-if)# ip ospf message-digest-key 1 md5 testingRouter(config-if)# ip ospf lls disableRelated Commands
ip ospf message-digest-key md5
To enable Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication, use the ip ospf message-digest-key md5 command in interface configuration mode. To remove an old MD5 key, use the no form of this command.
ip ospf message-digest-key key-id encryption-type md5 key
no ip ospf message-digest-key key-id
Syntax Description
Defaults
OSPF MD5 authentication is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Usually, one key per interface is used to generate authentication information when sending packets and to authenticate incoming packets. The same key identifier on the neighbor router must have the same key value.
The process of changing keys is as follows. Suppose the current configuration is as follows:
interface ethernet 1ip ospf message-digest-key 100 md5 OLDYou change the configuration to the following:
interface ethernet 1ip ospf message-digest-key 101 md5 NEWThe 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 once 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:
interface ethernet 1no ip ospf message-digest-key 100Then, only key 101 is used for authentication on Ethernet interface 1.
We recommend that you not keep more than one key per 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
Examples
The following example sets a new key 19 with the password 8ry4222:
interface ethernet 1ip ospf message-digest-key 10 md5 xvv560qleip ospf message-digest-key 19 md5 8ry4222Related Commands
ip ospf mtu-ignore
To disable Open Shortest Path First (OSPF) maximum transmission unit (MTU) mismatch detection on receiving Database Descriptor (DBD) packets, use the ip ospf mtu-ignore command in interface configuration mode. To reset to default, use the no form of this command.
ip ospf mtu-ignore
no ip ospf mtu-ignore
Syntax Description
This command has no keywords or arguments.
Defaults
OSPF MTU mismatch detection is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
OSPF checks whether 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 IP MTU configured on the incoming interface, OSPF adjacency will not be established.
Examples
The following example disables MTU mismatch detection on receiving DBD packets:
interface serial 0/0ip ospf mtu-ignoreip ospf name-lookup
To configure Open Shortest Path First (OSPF) to look up Domain Name System (DNS) names for use in all OSPF show EXEC command displays, use the ip ospf name-lookup command in global configuration mode. To disable this function, use the no form of this command.
ip ospf name-lookup
no ip ospf name-lookup
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command makes it easier to identify a router because the router is displayed by name rather than by its router ID or neighbor ID.
Examples
The following example configures OSPF to look up DNS names for use in all OSPF show EXEC command displays:
ip ospf name-lookupip ospf network
To configure the Open Shortest Path First (OSPF) network type to a type other than the default for a given medium, use the ip ospf network command in interface configuration mode. To return to the default value, use the no form of this command.
ip ospf network {broadcast | non-broadcast | {point-to-multipoint [non-broadcast] | point-to-point}}
no ip ospf network
Syntax Description
Defaults
Depends on the network type.
Command Modes
Interface configuration
Command History
Usage Guidelines
Using this feature, you can configure broadcast networks as NBMA networks when, for example, routers in your network do not support multicast addressing. You can also configure nonbroadcast multiaccess networks (such as X.25, Frame Relay, and Switched Multimegabit Data Service (SMDS)) as broadcast networks. This feature saves you from needing to configure neighbors.
Configuring NBMA networks as either broadcast or nonbroadcast assumes that there are virtual circuits from every router to every router or fully meshed networks. 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 will go through the router that has virtual circuits to both routers. You need not configure neighbors when using this feature.
If this command is issued on an interface that does not allow it, this command will be ignored.
OSPF has two features related to point-to-multipoint networks. One feature applies to broadcast networks; the other feature applies to nonbroadcast networks:
•
•
Examples
The following example sets your OSPF network as a broadcast network:
interface serial 0ip address 192.168.77.17 255.255.255.0ip ospf network broadcastencapsulation frame-relayThe following example illustrates a point-to-multipoint network with broadcast:
interface serial 0ip address 10.0.1.1 255.255.255.0encapsulation frame-relayip ospf cost 100ip ospf network point-to-multipointframe-relay map ip 10.0.1.3 202 broadcastframe-relay map ip 10.0.1.4 203 broadcastframe-relay map ip 10.0.1.5 204 broadcastframe-relay local-dlci 200!router ospf 1network 10.0.1.0 0.0.0.255 area 0neighbor 10.0.1.5 cost 5neighbor 10.0.1.4 cost 10Related Commands
ip ospf prefix-suppression
To prevent OSPF from advertising all IP prefixes that belong to a specific interface, except for prefixes that are associated with secondary IP addresses, use the ip ospf prefix-suppression command in interface configuration mode. To remove the per-interface configuration from the interface and allow the interface to inherit the IP prefix suppression setting from the router configuration, use the no form of this command.
ip ospf prefix-suppression [disable]
no ip ospf prefix-suppression
Syntax Description
disable
(Optional) Specifies that OSPF will advertise the interface IP prefix, regardless of the router mode configuration for IP prefix suppression.
Command Default
All IP prefixes that are associated with the interface are advertised.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
You can suppress IP prefixes on a per-interface basis for all interface types by entering the ip ospf prefix-suppression command in interface configuration mode.
When the ip ospf prefix-suppression command is configured, it takes precedence over the prefix-suppression router configuration command. If the prefix-suppression router configuration command has been entered, the interfaces for the specified OSPF process will inherit the prefix suppression setting from the router configuration command.
When you enter the ip ospf prefix-suppression command, prefix generation for any interface type, including loopbacks and passive interfaces, are suppressed. Only prefixes associated with secondary IP addressees remain unaffected.
Examples
The following example suppresses all IP prefixes, except for secondary IP addresses, for Ethernet interface 1/1:
interface ethernet 1/1ip ospf prefix-suppressionRelated Commands
ip ospf priority
To set the router priority, which helps determine the designated router for this network, use the ip ospf priority command in interface configuration mode. To return to the default value, use the no form of this command.
ip ospf priority number-value
no ip ospf priority
Syntax Description
Command Default
Priority of 1
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
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 to point-to-point networks).
This priority value is used when you configure Open Shortest Path First (OSPF) for nonbroadcast networks using the neighbor router configuration command for OSPF.
Examples
The following example sets the router priority value to 4:
interface ethernet 0ip ospf priority 4Related Commands
ip ospf resync-timeout
To configure how long the router will wait before taking a neighbor adjacency down if the out-of-band resynchronization (oob-resync) has not taken place since the time a restart signal (Open Shortest Path First [OSPF] hello packet with RS-bit set) was received from the neighbor, use the ip ospf resync-timeout command in interface configuration mode. To restore the default value, use the no form of this command.
ip ospf resync-timeout seconds
no ip ospf resync-timeout
Syntax Description
Command Default
The default value is 40 seconds or the value set for the interface's OSPF dead interval, whichever is greater.
Command Modes
Interface configuration
Command History
Usage Guidelines
When an OSPF nonstop forwarding (NSF) router performs a route processor (RP) switchover, it notifies its neighbors, via a special hello packet, of such action and requests that each neighbor help resynchronize the Link State Database.
When a neighbor (that is NSF-aware) receives the special hello packet from the NSF-capable router, it starts a resync timeout timer and waits to synchronize its database with the NSF-capable router. If the NSF-capable router does not initiate the database resynchronization process before the resync-timeout timer expires, the NSF-aware neighbor will take down the adjacency with the NSF-capable router.
By default, the resync-timeout timer is set to 40 seconds or the dead interval of the interface, whichever is greater. (By default, the dead interval is 4 times the hello interval; the hello interval defaults to 10 seconds for Ethernet or 30 seconds for nonbroadcast.) The ip ospf resync-timeout command allows the resync-timeout to be changed and independent of the dead interval or default value.
Examples
This example sets the OSPF resync-timeout interval to 50 seconds:
interface GigabitEthernet 6/0/0ip ospf resync-timeout 50Related Commands
ip ospf retransmit-interval
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the interface, use the ip ospf retransmit-interval command in interface configuration mode. To return to the default value, use the no form of this command.
ip ospf retransmit-interval seconds
no ip ospf retransmit-interval
Syntax Description
seconds
Time (in seconds) between retransmissions. The range is from 1 to 65535 seconds. The default is 5 seconds.
Defaults
5 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
When a router sends an LSA to its neighbor, it keeps the LSA until it receives back the acknowledgment message. If the router receives no acknowledgment, it will resend the LSA.
The setting of the seconds argument should be greater than the expected round-trip delay between any two routers on the attached network. The setting of this parameter should also be conservative, or needless LSA retransmissions may occur. The value should be larger for serial lines and virtual links.
Note
Examples
The following example sets the retransmit interval value to 8 seconds:
interface ethernet 2ip ospf retransmit-interval 8ip ospf shutdown
To initiate an Open Shortest Path First (OSPF) protocol graceful shutdown at the interface level, use the ip ospf shutdown command in interface configuration mode. To restart the OSPF protocol on an interface, use the no form of this command
ip ospf shutdown
no ip ospf shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
No OSPF graceful shutdown is performed.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ip ospf shutdown command to put OSPF under a specific interface in shutdown mode.
Examples
The following example shows how to initiate an OSPF protocol shutdown on the Ethernet 0 interface:
Router(config)# interface ethernet 0Router(config-if)# ip ospf shutdownRelated Commands
shutdown (router ospf)
Initiates a graceful shutdown of the OSPF protocol under the current instance.
ip ospf transmit-delay
To set the estimated time required to send a link-state update packet on the interface, use the ip ospf transmit-delay command in interface configuration mode. To return to the default value, use the no form of this command.
ip ospf transmit-delay seconds
no ip ospf transmit-delay
Syntax Description
seconds
Time (in seconds) required to send a link-state update. The range is from 1 to 65535 seconds. The default is 1 second.
Defaults
1 second
Command Modes
Interface configuration
Command History
Usage Guidelines
Link-state advertisements (LSAs) in the update packet must have their ages incremented by the amount specified in the seconds argument before transmission. The value assigned should take into account the transmission and propagation delays for the interface.
If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. This setting has more significance on very low-speed links.
Examples
The following example sets the retransmit delay value to 3 seconds:
interface ethernet 0ip ospf transmit-delay 3ip ospf ttl-security
To configure the Time-to-Live (TTL) security check feature on a specific interface, use the ip ospf ttl-security command in interface configuration mode. To disable TTL security on an interface, use the no form of this command.
ip ospf ttl-security [hops hop-count | disable]
no ip ospf ttl-security
Syntax Description
hops hop-count
(Optional) Configures the maximum number of IP hops. The hop-count argument range is from 1 to 254.
disable
(Optional) Disables TTL security on an interface.
Command Default
TTL security is disabled on all OSPF interfaces.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Use the ip ospf ttl-security command to configure TTL security on a specific interface.
The disable keyword can be used to disable TTL security on a specific interface but is only useful if the ttl-security all-interfaces command was used in router mode to first configure TTL security on all OSPF interfaces. In this way, all OSPF interfaces can be configured with TTL security and then individual interfaces can be disabled. This can save time as opposed to configuring each interface one-by-one from the start.
Examples
The following example shows how to effectively use the disable keyword to disable TTL security on the Ethernet 0/0 interface after the feature has first been configured on all OSPF interfaces:
Router# configure terminalRouter(config)# router ospf 1Router(config-router)# ttl-security all-interfacesRouter(config-router)# exitRouter(config)# interface ethernet 0/0Router(config-if)# ip ospf ttl-security disableRelated Commands
ttl-security all-interfaces
Configures TTL security check on all OSPF interfaces.
limit retransmissions
To change or remove the limit in the number of retransmissions of database exchange and update packets for both demand and non-demand circuits, use the limit retransmissions command in router configuration mode. To reset the maximum number of retransmissions back to the default value of 24, use the no form of this command.
limit retransmissions [dc {max-number | disable}] [non-dc {max-number | disable}]
no limit transmissions [dc | non-dc]
Syntax Description
Defaults
Maximum number of retransmissions is 24.
Command Modes
Router configuration
Command History
Usage Guidelines
Cisco IOS Release 12.2(4)T added a limit to the number of retransmissions of database exchange and update packets for both demand and nondemand circuits. The retransmission of these packets stops once this retry limit is reached, thus preventing unnecessary use of the link in continual retransmission of the packets if, for some reason, a neighbor is not responding during adjacency forming.
The limit for both demand circuit and nondemand circuit retransmissions is 24.
The limit-retransmissions command allows you to either remove (disable) the limit or change the maximum number of retransmissions to be a number from 1 to 255. The configuration of this command provides for backward compatibility for previous or other releases of Cisco IOS Software or other routers that do not have this feature.
Note
Examples
The following example shows how to set the maximum number of demand circuit retransmissions to 10:
limit retransmissions dc 10The following example shows how to remove the limit for the number of demand circuit retransmissions:
limit retransmissions dc disableThe following example shows how to set the maximum number of demand circuit retransmissions to 10 and to set the maximum number of nondemand circuit retransmissions to 20:
limit retransmissions dc 10 non-dc 20The following example shows how to set the maximum number of demand circuit retransmissions to 10, and to remove the limit for the number of nondemand circuit retransmissions:
limit retransmissions dc 10 non-dc disableThe following example shows how to reset both the demand circuit and nondemand circuit maximum number of retransmissions back to the default of 24:
no limit retransmissionsRelated Commands
local-rib-criteria
To specify that the OSPF local Routing Information Base (RIB) will be used for route validation, use the local-rib-criteria command in router configuration mode. To remove local RIB route validation, use the no form of this command.
local-rib-criteria [forwarding-address] [inter-area-summary] [nssa-translation]
no local-rib-criteria [forwarding-address] [inter-area-summary] [nssa-translation]
Syntax Description
Command Default
The global RIB (not the local RIB) is used for route validation.
Command Modes
Router configuration (config-router)
Command History
Usage Guidelines
If the local-rib-criteria is command is entered without any optional keywords, the local RIB will be used as criteria for all of the options (forwarding address, inter-area summary, and NSSA translation).
You can enter the local-rib-criteria command with one or more of the optional keywords to configure the OSPF routing process to use the local RIB only for forwarding address, inter-area-summary, or NSSA translation route generation.
Note
Note
Examples
The following example specifies that the local RIB should be used as the criteria for NSSA translation:
router ospf 23local-rib-criteria nssa-translationThe following example enables all local RIB criteria options:
router ospf 1
local-rib-criteria
The following example specifies that the local RIB will be used only for inter-area summary route generation:
router ospf 1
local-rib-criteria inter-area-summary
log-adjacency-changes
To configure the router to send a syslog message when an Open Shortest Path First (OSPF) neighbor goes up or down, use the log-adjacency-changes command in router configuration mode. To turn off this function, use the no form of this command.
log-adjacency-changes [detail]
no log-adjacency-changes [detail]
Syntax Description
detail
(Optional) Sends a syslog message for each state change, not just when a neighbor goes up or down.
Command Default
Enabled
Command Modes
Router configuration
Command History
Usage Guidelines
This command allows you to know about OSPF neighbors going up or down without turning on the debug ip ospf packet command or the debug ipv6 ospf adjacency command. The log-adjacency-changes command provides a higher level view of those changes of the peer relationship with less output than the debug command provides. The log-adjacency-changes command is on by default but only up/down (full/down) events are reported, unless the detail keyword is also used.
Examples
The following example configures the router to send a syslog message when an OSPF neighbor state changes:
log-adjacency-changes detailRelated Commands
debug ip ospf packet
Displays information about each OSPF packet received for IPv4.
debug ipv6 ospf
Displays debugging information for OSPF for IPv6.
max-lsa
To limit the number of nonself-generated link-state advertisements (LSAs) that an Open Shortest Path First (OSPF) routing process can keep in the OSPF link-state database (LSDB), use the max-lsa command in router configuration mode. To remove the limit of non self-generated LSAs that an OSPF routing process can keep in the OSPF LSDB, use the no form of this command.
max-lsa maximum-number [threshold-percentage] [warning-only] [ignore-time minutes] [ignore-count count-number] [reset-time minutes]
no max-lsa maximum-number [threshold-percentage] [warning-only] [ignore-time minutes] [ignore-count count-number] [reset-time minutes]
Syntax Description
Defaults
The number of nonself-generated LSAs that an OSPF routing process can keep in the OSPF LSDB is not limited.
threshold-percentage: 75 percent
warning-only warning message: disabled
ignore-time minutes: 5 minutes
ignore-count count-number: 5 times
reset-time minutes: 10 minutesCommand Modes
Router configuration
Command History
Usage Guidelines
To prevent the OSPF process from endlessly changing from the normal state of operation to the ignore state as a result of the LSA count exceeding the maximum configured number immediately after it returns from the ignore state to the normal state of operation, the OSPF process keeps a counter on how many times the process went into the ignore state. This counter is called the ignore count. If the ignore count exceeds the maximum number of LSAs that is specified by the ignore-count keyword and counter-number argument, the OSPF process remains in the ignore state permanently. To return the OSPF process to the state of normal operation, enter the clear ip ospf command.
If the router is placed into a permanent ignore state, we recommend that you identify and correct the cause of the problem involving the router that is generating the LSAs, or, if possible, increase the limit that has been configured by the max-lsa command before you try to bring the router back into normal operation.
If the router that has generated large numbers of LSAs is not reachable, these LSAs cannot be removed from the OSPF area and domain. As a result, any other router leaving the ignore state and returning to normal operation may reach the ignore state again. We recommend that you take one of the following actions in order to bring the router back into the network:
•
•
•
When the warning-only keyword is used, the OSPF process never enters the ignore state. When the LSA count exceeds the maximum limit that is specified by the maximum-number argument, only an error message is logged and the OSPF process continues in its normal operation.
When the max-lsa command is entered for the first time or when any of the parameters of the command are changed, the OSPF process undergoes a soft-reset procedure.
Examples
The following example sets a limit of 12,000 LSAs that can be received before the OSPF process enters the ignore state:
Router(config)# router ospf 100Router(config-router)# router-id 209.165.201.0Router(config-router)# log-adjacency-changesRouter(config-router)# max-lsa 12000Router(config-router)# network 209.165.201.1 255.255.255.255In the following example, an OSPF process has remained in the ignore state permanently. When the clear ip ospf command is entered the OSPF process returns to the state of normal operation and clears redistribution based on the OSPF routing process ID.
Router(config-router)# clear ip ospf 100 processRelated Commands
max-metric router-lsa
To configure a router that is running the Open Shortest Path First (OSPF) protocol to advertise a maximum metric so that other routers do not prefer the router as an intermediate hop in their shortest path first (SPF) calculations, use the max-metric router-lsa command in router address family topology or router configuration mode. To disable the advertisement of a maximum metric, use the no form of this command.
max-metric router-lsa [external-lsa [max-metric-value]] [include-stub] [on-startup {seconds | wait-for-bgp}] [summary-lsa [max-metric-value]]
no max-metric router-lsa [external-lsa [max-metric-value]] [include-stub] [on-startup {seconds | wait-for-bgp}] [summa
