4.13. OSPF Command Reference
4.13.1. Command Hierarchies
- Tools Commands (refer to the Tools chapter in the 7705 SAR OAM and Diagnostics Guide)
4.13.1.1. Configuration Commands
4.13.1.2. Show Commands
4.13.1.4. Debug Commands
4.13.2. Command Descriptions
4.13.2.1. Configuration Commands
4.13.2.1.1. Generic Commands
shutdown
Syntax
Context
Description
This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they can be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system-generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default
OSPF Protocol — the Open Shortest Path First (OSPF) protocol is created in the no shutdown state
OSPF Interface — when an IP interface is configured as an OSPF interface, OSPF on the interface is in the no shutdown state by default
4.13.2.1.2. Global Commands
ospf
Syntax
Context
Description
This command activates OSPF on the router and enables access to the context to define OSPF parameters.
Before OSPF can be activated on the router, the router ID must be configured.
The router ID uniquely identifies the router within an AS. In OSPF, routing information is exchanged between autonomous systems, which are groups of networks that share routing information. The router ID can be set to be the same as the system interface address (loopback address).
The router ID is derived by one of the following methods:
- defining the value using the config>router>router-id ip-address command
- defining the system interface using the config>router>interface ip-int-name command (used if the router ID is not specified with the config>router>router-id ip-address command)
- inheriting the last 4 bytes of the MAC address
When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. To force the new router ID, issue the shutdown and no shutdown commands for OSPF or restart the entire router.
The no form of the command reverts to the default value.
Default
no ospf
ospf3
Syntax
Context
Description
This command activates OSPFv3 on the router and enables access to the context to define OSPFv3 parameters.
Before OSPFv3 can be activated on the router, the router ID must be configured.
The router ID uniquely identifies the router within an AS. In OSPFv3, routing information is exchanged between autonomous systems, which are groups of networks that share routing information. The router ID can be set to be the same as the system interface address (loopback address).
The router ID is derived by one of the following methods:
- defining the value using the config>router>router-id ip-address command
- defining the system interface using the config>router>interface ip-int-name command (used if the router ID is not specified with the config>router>router-id ip-address command)
- inheriting the last 4 bytes of the MAC address
When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. To force the new router ID, issue the shutdown and no shutdown commands for OSPFv3 or restart the entire router.
The no form of the command reverts to the default value.
Default
no ospf3
advertise-tunnel-link
Syntax
Context
Description
This command enables the forwarding adjacency feature. With this feature, OSPF advertises an RSVP-TE LSP as a link so that other routers in the network can include it in their SPF calculations. The RSVP-TE LSP is advertised as an unnumbered point-to-point link and the link-state advertisement (LSA) has no traffic engineering opaque sub-TLVs as per RFC 3906.
The forwarding adjacency feature can be enabled independently from the IGP shortcut feature (rsvp-shortcut). If both features are enabled for a given OSPF instance, the forwarding adjacency feature takes precedence.
When this feature is enabled, each node advertises a point-to-point unnumbered link for each best-metric tunnel to the router ID of any endpoint node. The node does not include the tunnels as IGP shortcuts in the SPF calculation directly. Instead, when the LSA advertising the corresponding point-to-point unnumbered link is installed in the local routing database, the node performs an SPF calculation using the link like any other link LSA.
The link bidirectional check requires that a regular link or tunnel link exists in the reverse direction for the tunnel to be used in the SPF calculation.
An RSVP-TE LSP can be excluded from being used as a forwarding adjacency with the config>router>mpls>lsp>no igp-shortcut command.
The no form of this command disables forwarding adjacency and therefore disables the advertisement of RSVP-TE LSPs into OSPF.
Default
no advertise-tunnel-link
asbr
Syntax
Context
Description
This command configures the router as an Autonomous System Boundary Router (ASBR) if the router is to be used to distribute external routes into the OSPF domain. When a router is configured as an ASBR, the export policies into the OSPF domain take effect. If no policies are configured, no external routes are redistributed into the OSPF domain.
The no form of the command removes the ASBR status and withdraws the routes redistributed from the routing table into OSPF from the link-state database.
Only the base OSPF instance is supported; therefore, the domain ID may not need to be configured. However, in order to prevent routing loops (where routes learned from one domain are redistributed back into the domain), the domain ID can be used to tag external LSAs – indicating which domain or network they have learned the route from.
Default
no asbr — the router is not an ASBR
Parameters
disable-ldp-sync
Syntax
Context
Description
This command disables the IGP-LDP synchronization feature on all interfaces participating in the OSPF or IS-IS routing protocol. When this command is executed, IGP immediately advertises the actual value of the link cost for all interfaces that have the IGP-LDP synchronization enabled if the currently advertised cost is different. IGP-LDP synchronization will then be disabled for all interfaces. This command does not delete the interface configuration.
The no form of this command restores the default settings and re-enables IGP-LDP synchronization on all interfaces participating in the OSPF or IS-IS routing protocol and for which the ldp-sync-timer is configured (refer to the 7705 SAR Router Configuration Guide for information on configuring the ldp-sync-timer).
Default
no disable-ldp-sync
export
Syntax
Context
Description
This command specifies export route policies to determine which routes are exported from the routing table manager to OSPF. Export policies are only in effect if OSPF is configured as an ASBR.
If no export policy is specified, non-OSPF routes are not exported from the routing table manager to OSPF.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.
The no form of the command removes all policies from the configuration.
Refer to the 7705 SAR Router Configuration Guide for information on defining route policies.
Default
no export — no export route policies specified
Parameters
The specified names must already be defined.
external-db-overflow
Syntax
Context
Description
This command enables limits on the number of non-default, AS-external LSA entries that can be stored in the link-state database (LSDB) and specifies a wait timer before processing these entries after the limit is exceeded.
The limit value specifies the maximum number of entries that can be stored in the LSDB. Placing a limit on these LSAs in the LSDB protects the router from receiving an excessive number of external routes that consume excessive memory or CPU resources. If the number of routes reaches or exceeds the limit, the table is in an overflow state. When in an overflow state, the router will not originate any new AS-external LSAs and will withdraw all the self-originated non-default external LSAs.
The seconds value specifies the time to wait after an overflow state before regenerating and processing non-default, AS-external LSAs. The waiting period acts like a dampening period, preventing the router from continuously running shortest path first (SPF) calculations caused by the excessive number of non-default, AS-external LSAs.
The external-db-overflow must be set identically on all routers attached to any regular OSPF area. OSPF stub areas and not-so-stubby areas (NSSAs) are excluded.
The no form of the command disables limiting the number of non-default, AS-external LSA entries.
Default
no external-db-overflow
Parameters
external-preference
Syntax
Context
Description
This command configures the preference for OSPF external routes. The preference for internal routes is set with the preference command.
A route can be learned by the router from different protocols, in which case, the costs are not comparable. When this occurs, the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is based on the default preferences as defined in Table 32.
Table 32: Route Preference Defaults by Route Type
Route Type | Preference | Configurable |
Direct attached | 0 | No |
Static routes | 5 | Yes |
OSPF internal | 10 | Yes |
IS-IS level 1 internal | 15 | Yes |
IS-IS level 2 internal | 18 | Yes |
OSPF external | 150 | Yes |
IS-IS level 1 external | 160 | Yes |
IS-IS level 2 external | 165 | Yes |
If multiple routes are learned with the same preference using the same protocol, the lowest-cost route is used. If multiple routes are learned with the same preference using the same protocol and the costs (metrics) are equal, the decision of which route to use is determined by the configuration of ECMP in the config>router context. Refer to the 7705 SAR Router Configuration Guide for information on ECMP.
 | Note: To configure a preference for static routes, use the config>router>static-route command. Refer to the 7705 SAR Router Configuration Guide for information. |
The no form of the command reverts to the default value.
Default
external-preference 150 — OSPF external routes have a default preference of 150
Parameters
graceful-restart
Syntax
Context
Description
This command enables or disables Graceful Restart for OSPF. Graceful Restart is not fully implemented on the 7705 SAR, meaning that the router will never request graceful restart support from its neighbors. However, Graceful Restart must be enabled before the 7705 SAR can be configured for Graceful Restart Helper mode.
The no form of the command disables Graceful Restart and removes all Graceful Restart configurations in the OSPF instance.
Default
no graceful-restart
helper-disable
Syntax
Context
Description
This command enables or disables Graceful Restart Helper mode for OSPF. In helper mode, if a grace LSA is received from an OSPF neighbor, the 7705 SAR keeps the link toward that neighbor up and operational until the specified grace period in the grace LSA expires or the graceful restart is successful, whichever comes first.
The no form of the command enables Graceful Restart Helper mode and is the default when graceful-restart is enabled.
Default
no helper-disable
loopfree-alternate
Syntax
Context
Description
This command enables Loop-Free Alternate (LFA) computation by SPF under the OSPF routing protocol instance.
When this command is enabled, the OSPF SPF attempts to precalculate both a primary next hop and a LFA backup next hop for every learned prefix. When found, the LFA next hop is populated into the routing table along with the primary next hop for the prefix.
The no form of this command disables the LFA SPF calculation.
Default
no loop-free alternate
loopfree-alternate-exclude
Syntax
Context
Description
This command excludes from the LFA SPF calculation any prefixes that match a prefix entry in a prefix policy. If a prefix is excluded, it is not included in the LFA SPF calculation, regardless of its priority. Prefix policies are created with the command config>router> policy-options>prefix-list (for information on prefix lists, refer to the 7705 SAR Router Configuration Guide, “Route Policies”).
The default action of the loopfree-alternate-exclude command, when not explicitly specified in the prefix policy, is to “reject”. Therefore, even if the default-action reject statement was not explicitly stated for the prefix policy, a prefix that does not match any entry in the policy will be used in the LFA SPF calculation.
The no form of the command deletes the excluded prefix policy.
Default
no loop-free-alternate-exclude
Parameters
multicast-import
Syntax
Context
Description
This command administratively enables the submission of routes into the multicast RTM by OSPF.
The no form of the command disables the submission of routes into the multicast RTM.
Default
no multicast-import
overload
Syntax
Context
Description
This command changes the overload state of the local router so that it appears to be overloaded. When overload is enabled, the router can participate in OSPF routing, but is not used for transit traffic. Traffic destined for directly attached interfaces continues to reach the router.
To put the IGP in an overload state, enter a timeout value. The IGP will enter the overload state until the timeout timer expires or a no overload command is executed.
If no timeout is specified, the overload state is maintained indefinitely.
If the overload command is encountered during the execution of an overload-on-boot command, the overload command takes precedence. This situation could occur as a result of a saved configuration file where both parameters are saved. When the file is saved by the system, the overload-on-boot command is saved after the overload command.
Use the no form of this command to return to the default. When the no overload command is executed, the overload state is terminated regardless of the reason the protocol entered the overload state.
Default
no overload
Parameters
overload-include-stub
Syntax
Context
Description
This command is used to determine if the OSPF stub networks should be advertised with a maximum metric value when the system goes into an overload state for any reason. When enabled, the system uses the maximum metric value. When this command is enabled and the router is in overload, all stub interfaces, including loopback and system interfaces, will be advertised at the maximum metric.
Default
no overload-include-stub
overload-on-boot
Syntax
Context
Description
When the router is in an overload state, the router is used only if there is no other router to reach the destination. This command configures OSPF upon boot-up in the overload state until one of the following events occurs:
- the timeout timer expires (if a timeout has been specified)
- a manual override of the current overload state is entered with the no overload command
If no timeout is specified, the overload state is maintained indefinitely.
The no overload command does not affect the overload-on-boot function.
The no form of the command removes the overload-on-boot functionality from the configuration.
Default
no overload-on-boot
Parameters
preference
Syntax
Context
Description
This command configures the preference for OSPF internal routes.
A route can be learned by the router from different protocols, in which case, the costs are not comparable. When this occurs, the preference is used to decide which route will be used.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is based on the default preferences as defined in Table 32. If multiple routes are learned with the same preference using the same protocol and the costs (metrics) are equal, the decision of which route to use is determined by the configuration of ECMP in the config>router context. Refer to the 7705 SAR Router Configuration Guide for information on ECMP.
The no form of the command reverts to the default value.
Default
preference 10 — OSPF internal routes have a preference of 10
Parameters
reference-bandwidth
Syntax
Context
Description
This command configures the reference bandwidth used to calculate the default costs of interfaces based on their underlying link speed.
The default interface cost is calculated as follows:
cost = reference bandwidth/bandwidth
The default reference bandwidth is 100 000 000 kb/s or 100 Gb/s; therefore, the default auto-cost metrics for various link speeds are as follows:
- 10 Mb/s link: default cost of 10000
- 100 Mb/s link: default cost of 1000
- 1 Gb/s link: default cost of 100
- 10 Gb/s link: default cost of 10
The reference-bandwidth command assigns a default cost to the interface based on the interface speed. To override this default cost on a particular interface, use the metric metric command in the config>router>ospf>area>interface ip-int-name or config>router> ospf3>area>interface ip-int-name context.
The no form of the command resets the reference bandwidth to the default value.
Default
reference-bandwidth 100000000
Parameters
router-id
Syntax
Context
Description
This command configures the router ID to be used under the global routing table context (GRT). The 7705 SAR supports a single OSPF instance in the GRT context; therefore, changing the router ID has a global implication.
When configuring the router ID in the base instance of OSPF, the value overrides the router ID configured in the config>router context.
The default value for the base instance is inherited from the configuration in the config>router context. If the router ID in the config>router context is not configured, the following applies:
- the system uses the system interface address (which is also the loopback address)
- if a system interface address is not configured, the last 4 bytes of the chassis MAC address are used
When configuring a new router ID, the instance is not automatically restarted with the new router ID. The next time the instance is initialized, the new router ID is used.
To force the new router ID to be used, issue the shutdown and no shutdown commands for the instance, or reboot the entire router.
The no form of the command to reverts to the default value.
Default
0.0.0.0 (base OSPF)
Parameters
rsvp-shortcut
Syntax
Context
Description
This command enables the use of an RSVP-TE shortcut for resolving OSPF routes. When the command is enabled, OSPF includes RSVP-TE LSPs originating on this node and terminating on the router ID of a remote node as direct links with a metric equal to the operational metric provided by MPLS.
The SPF algorithm will always use the IGP metric to build the SPF tree, and the LSP metric value does not update the SPF tree calculation. During the IP reach to determine the reachability of nodes and prefixes, LSPs are overlaid and the LSP metric is used to determine the subset of paths that are of an equal lowest cost to reach a node or a prefix. If the relative-metric option for this LSP is enabled (in the config>router>mpls>lsp>igp-shortcut context), OSPF will apply the shortest cost between the endpoints of the LSP plus the value of the offset, instead of the LSP operational metric, when calculating the cost of a prefix that is resolved to the LSP.
When a prefix is resolved to a tunnel next hop, the packet is sent labeled with the label stack corresponding to the NHLFE of the RSVP-TE LSP. Any network event that causes an RSVP-TE LSP to go down will trigger a full SPF calculation, which may result in a new route being installed over another RSVP-TE LSP shortcut as a tunnel next hop or over a regular IP next hop.
When the rsvp-shortcut command is enabled, all RSVP-TE LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured with the config>router>mpls> lsp>to command, corresponds to a router ID of a remote node. A specific LSP can be excluded from being used as a shortcut with the config>router>mpls>lsp>no igp-shortcut command.
If ECMP is enabled on the system and multiple equal-cost paths exist for the route over a set of tunnel next hops (based on the hashing routine supported for IPv4 packets), there are two possibilities:
- if the destination is the tunnel endpoint, the system selects the tunnel with the lowest tunnel ID (the IP next hop is never used)
- if the destination is different from the tunnel endpoint, the system:
- selects tunnel endpoints where the LSP metric is lower than the IGP cost
- prefers tunnel endpoints over IP next hops
ECMP is not performed across both the IP and tunnel next hops.
OSPF can populate the multicast RTM with the prefix IP next hop when both rsvp-shortcut and multicast-import are enabled. The unicast RTM can still use the tunnel next hop for the same prefix.
The forwarding adjacency feature (advertise-tunnel-link) can be enabled independently from the shortcuts feature. If both features are enabled for a given OSPF instance, the forwarding adjacency feature takes precedence.
The no form of this command disables the resolution of IGP routes using RSVP shortcuts.
Default
no rsvp-shortcut
timers
Syntax
Context
Description
This command enables the context that allows for the configuration of OSPF timers. Timers control the delay between receipt of a link-state advertisement (LSA) requiring an SPF calculation and the minimum time between successive SPF calculations.
Changing the timers affects CPU usage and network reconvergence times. Lower values reduce reconvergence time but increase CPU usage. Higher values reduce CPU usage but increase reconvergence time.
Default
n/a
lsa-arrival
Syntax
Context
Description
This command defines the minimum delay that must pass between receipt of the same link-state advertisements (LSAs) arriving from neighbors.
It is recommended that the configured lsa-generate lsa-second-wait interval for the neighbors be equal to or greater than the lsa-arrival-time.
Use the no form of this command to return to the default.
Default
no lsa-arrival
Parameters
lsa-generate
Syntax
Context
Description
This command customizes the throttling of OSPF LSA generation. Timers that determine when to generate the first, second, and subsequent LSAs can be controlled with this command. Subsequent LSAs are generated at increasing intervals of the lsa-second-wait timer until a maximum value is reached.
It is recommended that the lsa-arrival-time be equal to or less than the lsa-second-wait interval.
Use the no form of this command to return to the default.
Default
no lsa-generate
Parameters
When an LSA is generated, the initial wait period commences. If, within the specified lsa-initial-wait period, another topology change occurs, the lsa-initial-wait timer applies.
spf-wait
Syntax
Context
Description
This command defines the maximum interval between two consecutive SPF calculations in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs can be controlled with this command. Subsequent SPF runs (if required) will occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the spf-second-wait interval is 1000, the next SPF will run after 2000 ms, and the next SPF will run after 4000 ms, and so on, until it reaches the spf-wait value. The SPF interval will stay at the spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to spf-initial-wait.
The timer must be entered in increments of 100 ms. Values entered that do not match this requirement will be rejected.
Use the no form of this command to return to the default.
Default
no spf-wait
Parameters
traffic-engineering
Syntax
Context
Description
This command enables traffic engineering route calculations constrained by nodes or links.
Traffic engineering enables the router to perform route calculations constrained by nodes or links. The traffic engineering capabilities of this router are limited to calculations based on link and nodal constraints.
The no form of the command disables traffic engineered route calculations.
Default
no traffic-engineering
unicast-import-disable
Syntax
Context
Description
This command allows one IGP to import its routes into the multicast RTM (also known as the RPF RTM [Reverse Path Forwarding - Route Table Manager]) while another IGP imports routes only into the unicast RTM. Import policies can redistribute routes from an IGP protocol into the RPF RTM. By default, the IGP routes will not be imported into the RPF RTM, since such an import policy must be explicitly configured.
The no form of the command enables importing IGP routes into the RPF RTM.
Default
disabled (unicast-import-disable)
4.13.2.1.3. Area Commands
area
Syntax
Context
Description
This command enables the context to configure an OSPF area. An area is a collection of network segments within an AS that have been administratively grouped together. The area ID can be specified in dotted-decimal notation or as a 32-bit decimal integer.
The no form of the command deletes the specified area from the configuration. Deleting the area also removes the OSPF configuration of all the interfaces, virtual links, address ranges, and so on, that are currently assigned to this area.
The 7705 SAR supports a maximum of four areas.
Default
no area — no OSPF areas are defined
Parameters
area-range
Syntax
Context
Description
This command creates ranges of addresses on an Area Border Router (ABR) for the purpose of route summarization or suppression. When a range is created, the range is configured to be advertised or not advertised to other areas. Multiple range commands can be used to summarize or hide different ranges. In the case of overlapping ranges, the most specific range command applies.
ABRs send summary link advertisements to describe routes to other areas. To minimize the number of advertisements that are flooded, you can summarize a range of IP addresses and send reachability information about these addresses in an LSA.
The ip-prefix/mask parameter applies in the ospf context. The ipv6-prefix/prefix-length parameter applies in the ospf3 context.
The no form of the command deletes the range advertisement or non-advertisement.
Default
no area-range — no range of addresses is defined
Special Cases
Parameters
blackhole-aggregate
Syntax
Context
Description
This command installs a low-priority blackhole route for the entire aggregate. Existing routes that make up the aggregate will have a higher priority and only the components of the range for which no route exists will be blackholed.
When performing area aggregation, addresses may be included in the range for which no actual route exists. This can cause routing loops. To avoid this problem, configure the blackhole aggregate option.
The no form of this command removes this option.
Default
blackhole-aggregate
key-rollover-interval
Syntax
Context
Description
This command configures the key rollover interval.The no form of the command resets the configured interval to the default setting.
Default
10
Parameters
loopfree-alternate-exclude
Syntax
Context
Description
This command instructs OSPF to exclude a specific interface or all interfaces participating in a specific OSPF area from the LFA SPF calculation. The LFA SPF calculation can therefore be run only where it is needed.
If an interface is excluded from the LFA SPF in OSPF, it is excluded in all areas.
Default
no loopfree-alternate-exclude
nssa
Syntax
Context
Description
This command enables the context to configure an OSPF Not So Stubby Area (NSSA) and adds or removes the NSSA designation from the area.
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is that an NSSA has the capability to flood external routes that it learns throughout its area and via an ABR to the entire OSPF domain.
Existing virtual links of a non-stub area or NSSA are removed when the designation is changed to NSSA or stub.
An area can be designated as stub or NSSA but never both at the same time.
By default, an area is not configured as an NSSA area.
The no form of the command removes the NSSA designation and configuration context from the area.
Default
no nssa
originate-default-route
Syntax
Context
Description
This command enables the generation of a default route and its LSA type into an NSSA by an NSSA ABR or ASBR.
The functionality of the type-7 parameter and the type-nssa parameter is the same. The type-7 parameter is available in the ospf context; the type-nssa parameter is available in the ospf3 context. Include the type-7 or type-nssa parameter to inject a type 7 LSA default route instead the type 3 LSA into the NSSA configured with no summaries.
To revert to a type 3 LSA, enter the originate-default-route command without the type-7 or type-nssa parameter.
When configuring an NSSA with no summaries, the ABR will inject a type 3 LSA default route into the NSSA area. Some older implementations expect a type 7 LSA default route.
The no form of the command disables origination of a default route.
Default
no originate-default-route
Parameters
redistribute-external
Syntax
Context
Description
This command enables the redistribution of external routes into the Not So Stubby Area (NSSA) on an NSSA area border router (ABR) that is exporting the routes into non-NSSA areas.
NSSAs are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is that the NSSA has the capability to flood external routes that it learns (providing it is an ASBR) throughout its area and via an ABR to the entire OSPF domain.
The no form of the command disables the default behavior to automatically redistribute external routes into the NSSA area from the NSSA ABR.
Default
redistribute-external
summaries
Syntax
Context
Description
This command enables sending summary (type 3) advertisements into a stub area or NSSA on an ABR.
This parameter is particularly useful to reduce the size of the routing and link-state database (LSDB) tables within the stub or NSSA area.
By default, summary route advertisements are sent into the stub area or NSSA.
The no form of the command disables sending summary route advertisements and, for stub areas, only the default route is advertised by the ABR.
Default
summaries
stub
Syntax
Context
Description
This command enables access to the context to configure an OSPF stub area and adds or removes the stub designation from the area.
External routing information is not flooded into stub areas. All routers in the stub area must be configured with the stub command.
Existing virtual links of a non-stub area or NSSA are removed when its designation is changed to NSSA or stub.
An OSPF area cannot be both an NSSA and a stub area at the same time.
By default, an area is not a stub area.
The no form of the command removes the stub designation and configuration context from the area.
Default
no stub
default-metric
Syntax
Context
Description
This command configures the metric used by the ABR for the default route into a stub area.
The default metric should only be configured on an ABR of a stub area.
An ABR generates a default route if the area is a stub area.
The no form of the command reverts to the default value.
Default
default-metric 1
Parameters
4.13.2.1.4. Interface/Virtual Link Commands
interface
Syntax
Context
Description
This command creates a context to configure an OSPF interface.
By default, interfaces are not activated in any interior gateway protocol, such as OSPF, unless explicitly configured.
The no form of the command deletes the OSPF interface configuration for this interface. The shutdown command in the config>router>ospf>area>interface context can be used to disable an interface without removing the configuration for the interface.
Default
no interface
Parameters
If the IP interface name does not exist or does not have an IP address configured, an error message will be returned.
If the IP interface exists in a different area, it will be moved to this area.
advertise-subnet
Syntax
Context
Description
This command enables advertising point-to-point interfaces as subnet routes (network number and mask). When disabled, point-to-point interfaces are advertised as host routes.
The no form of the command disables advertising point-to-point interfaces as subnet routes, meaning they are advertised as host routes.
Default
advertise-subnet
auth-keychain
Syntax
Context
Description
This command associates an authentication keychain with the OSPF interface or virtual link. The keychain is a collection of keys used to authenticate OSPF messages from remote peers. The keychain allows the rollover of authentication keys during the lifetime of a session and also supports stronger authentication algorithms than clear text and MD5.
The keychain must already be defined in the config>system>security>keychain context.
Either the authentication-key command or the auth-keychain command can be used by OSPF, but both cannot be supported at the same time. If both commands are configured, the auth-keychain configuration will be applied and the authentication-key command will be ignored.
By default, authentication is not enabled.
Default
no auth-keychain
Parameters
authentication
Syntax
Context
Description
This command configures an interface with a static security association (SA) used to authenticate OSPFv3 packets.
The no form of the command removes the SA name from the configuration.
Parameters
authentication-key
Syntax
Context
Description
This command configures the password used by the OSPF interface or virtual link to send and receive OSPF protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for correct protocol communication. If the authentication-type is configured as password, the authentication key must be configured.
Either the authentication-key command or the auth-keychain command can be used by OSPF, but both cannot be supported at the same time. If both commands are configured, the auth-keychain configuration will be applied and the authentication-key command will be ignored.
By default, no authentication key is configured.
The no form of the command removes the authentication key.
Default
no authentication-key
Parameters
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
authentication-type
Syntax
Context
Description
This command enables authentication and specifies the type of authentication to be used on the OSPF interface.
Both simple password and message-digest authentication are supported.
By default, authentication is not enabled on an interface.
The no form of the command disables authentication on the interface.
Default
no authentication-type
Parameters
bfd-enable
Syntax
Context
Description
This command enables the use of bidirectional forwarding (BFD) to control the state of the associated OSPF interface. By enabling BFD on an OSPF interface, the state of the interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for BFD are set via the BFD command under the IP interface.
The optional remain-down-on-failure parameter can be specified on OSPF interfaces that are enabled for BFD, to keep OSPF from reaching the Full state if the BFD session to that neighbor cannot be established. This option is disabled by default and should be used only if there is a chance that unicast packets might be discarded while multicast packets are forwarded.
The no form of this command removes BFD from the associated OSPF adjacency.
Default
no bfd-enable
Parameters
dead-interval
Syntax
Context
Description
This command configures the time, in seconds, that OSPF waits before declaring a neighbor router down. If no Hello packets are received from a neighbor for the duration of the dead interval, the router is assumed to be down. The minimum interval must be two times the hello interval.
The no form of the command reverts to the default value.
Default
40
Special Cases
Parameters
hello-interval
Syntax
Context
Description
This command configures the interval between OSPF hellos issued on the interface or virtual link.
The hello interval, in combination with the dead interval, is used to establish and maintain the adjacency. Use this parameter to edit the frequency that Hello packets are sent.
Reducing the interval, in combination with an appropriate reduction in the associated dead-interval, allows for faster detection of link and/or router failures but results in higher processing costs.
The no form of this command reverts to the default value.
Default
10
Special Cases
Parameters
interface-type
Syntax
Context
Description
This command configures the interface type to be either broadcast or point-to-point.
Use this command to set the interface type of an Ethernet link to point-to-point to avoid having to carry the broadcast adjacency maintenance overhead of the link, provided that the link is used as a point-to-point link.
If the interface type is not known when the interface is added to OSPF, and the IP interface is subsequently bound (or moved) to a different interface type, this command must be entered manually.
The no form of the command reverts to the default value.
Default
broadcast – if the physical interface is Ethernet or unknown
point-to-point – if the physical interface is T1, E1, or SONET/SDH
Special Cases
Parameters
lfa-policy-map
Syntax
Context
Description
This command applies a route next-hop policy template to an OSPF interface. When a route next-hop policy template is applied to an interface in OSPF, it is applied in all areas.
If the interface has been excluded from LFA with the loopfree-alternate-exclude command, the LFA policy has no effect on the interface.
If the route next-hop policy template is applied to a loopback interface or to the system interface, the command will not be rejected, but the policy will have no effect on the interface.
The no form of the command deletes the mapping of a route next-hop policy template to an OSPF interface.
Default
no lfa-policy-map
Parameters
message-digest-key
Syntax
Context
Description
This command configures a message digest key when MD5 authentication is enabled on the interface. Multiple message digest keys can be configured.
The no form of the command removes the message digest key identified by the key-id.
Default
no message-digest-key
Parameters
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
metric
Syntax
Context
Description
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of the command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
Default
no metric
Parameters
mtu
Syntax
Context
Description
This command configures the OSPF or OSPFv3 interface MTU value used when negotiating an OSPF or OSPFv3 adjacency.
The operational OSPF MTU value is calculated as follows.
If this command is not configured:
- the OSPF or OSPFv3 interface operational MTU derives the MTU value from the IP interface MTU (which is derived from the port MTU); for example, port MTU minus 14 bytes for a null-encapsulated Ethernet port
- for OSPF (not OSPFv3), if the derived MTU value is less than 576 bytes, the OSPF interface operational MTU is set to 576 bytes. If a lower interface MTU is required, you must explicitly configure it using this command.
If this command is configured:
- for OSPF (not OSPFv3):
- if the OSPF interface MTU is less than 576 bytes, it becomes the operational OSPF MTU, regardless of the port MTU value
- if the OSPF interface MTU is equal to or greater than 576 bytes, and the derived interface MTU is less than 576 bytes, the operational OSPF MTU is set to 576 bytes
- if the OSPF interface MTU is equal to or greater than 576 bytes, and the derived interface MTU is greater than 576 bytes, the operational OSPF MTU is set to the lesser of the values configured with this command and the derived MTU
The port MTU must be set to 512 bytes or higher, since OSPF cannot support port MTU values lower than 512 bytes. - for OSPFv3:
- the operational OSPF MTU is set to the lesser of the values configured with this command and the derived MTU
- this applies only when the port MTU is set to 1280 bytes or higher, since OSPFv3 cannot support port MTU values less than 1280 bytes
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured with this command.
If the OSPF mtu command is configured to a value less than the interface or port MTU value, then the OSPF MTU value will be used to transmit OSPF packets.
Use the no form of this command to revert to the default.
Default
no mtu — uses the value derived from the port MTU
Parameters
passive
Syntax
Context
Description
This command adds the passive property to the OSPF interface where passive interfaces are advertised as OSPF interfaces but do not run the OSPF protocol.
By default, only interface addresses that are configured for OSPF will be advertised as OSPF interfaces. The passive parameter allows an interface to be advertised as an OSPF interface without running the OSPF protocol.
While in passive mode, the interface will ignore ingress OSPF protocol packets and not transmit any OSPF protocol packets.
The no form of the command removes the passive property from the OSPF interface.
Default
no passive
priority
Syntax
Context
Description
This command configures the priority of the OSPF interface that is used in an election of the designated router on the subnet.
This parameter is only used if the interface is of type broadcast. The router with the highest-priority interface becomes the designated router. A router with priority 0 is not eligible to be a designated router or backup designated router.
The no form of the command resets the interface priority to the default value.
Default
1
Parameters
retransmit-interval
Syntax
Context
Description
This command specifies the length of time, in seconds, that OSPF will wait before retransmitting an unacknowledged link-state advertisement (LSA) to an OSPF neighbor.
The value should be longer than the expected round-trip delay between any two routers on the attached network. If the retransmit interval expires and no acknowledgment has been received, the LSA will be retransmitted.
The no form of this command reverts to the default interval.
Default
5
Parameters
transit-delay
Syntax
Context
Description
This command configures the estimated time, in seconds, that it takes to transmit a link-state advertisement (LSA) on the interface or virtual link.
The no form of this command reverts to the default delay time.
Default
1
Parameters
virtual-link
Syntax
Context
Description
This command configures a virtual link to connect ABRs to the backbone.
The backbone area (area 0.0.0.0) must be contiguous and all other areas must be connected to the backbone area. If it is not practical or possible to connect an area to the backbone, the ABRs must be connected via a virtual link. The two ABRs form a point-to-point-like adjacency across the transit area. A virtual link can only be configured while in the area 0.0.0.0 context.
The router-id specified in this command must be associated with the virtual neighbor. The transit area cannot be a stub area or an NSSA.
The no form of the command deletes the virtual link.
Default
no virtual-link
Parameters
4.13.2.2. Show Commands
| Note: The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration. |
ospf
Syntax
Context
Description
This command enables the context to display OSPF information.
ospf3
Syntax
Context
Description
This command enables the context to display OSPFv3 information.
area
Syntax
Context
Description
This command displays configuration information about all areas or the specified area. When detail is specified, operational and statistical information will be displayed.
Parameters
Output
The following outputs are examples of OSPF area information:
- OSPF detailed area information (Output Example, Table 33)
- OSPF detailed LFA information (Output Example, Table 34)
Table 33: Show Area Output Fields
Label | Description |
Area Id | A 32-bit integer uniquely identifying an area |
Type | NSSA: this area is configured as an NSSA area |
Standard: this area is configured as a standard area (not NSSA or stub) | |
Stub: this area is configured as a stub area | |
LFA | Indicates whether interfaces in this area are included in the LFA SPF calculation |
Virtual Links | The number of virtual links configured through this transit area |
Total Nbrs | The total number of neighbors in this area |
Active IFs | The active number of interfaces configured in this area |
Total IFs | The total number of interfaces configured in this area |
Area Bdr Rtrs | The total number of ABRs reachable within this area |
AS Bdr Rtrs | The total number of ASBRs reachable within this area |
SPF Runs | The number of times that the intra-area route table has been calculated using this area’s link-state database |
Last SPF Run | The time that the last intra-area SPF was run on this area |
Router LSAs | The total number of router LSAs in this area |
Network LSAs | The total number of network LSAs in this area |
Summary LSAs | The summary of LSAs in this area |
Asbr-summ LSAs | The summary of ASBR LSAs in this area |
Nssa-ext LSAs | The total number of NSSA-EXT LSAs in this area |
Area opaque LSAs | The total number of opaque LSAs in this area |
Total LSAs | The sum of LSAs in this area excluding autonomous system external LSAs |
LSA Cksum Sum | The 32-bit unsigned sum of the link-state database advertisements LS checksums contained in this area’s link-state database. This checksum excludes AS External LSAs (type 5). |
LSA Count | The total number of link-state advertisements in this area’s link-state database, excluding AS External LSAs |
Blackhole Range | False: no blackhole route is installed for aggregates configured in this area |
True: a lowest-priority blackhole route is installed for aggregates configured in this area | |
Unknown LSAs | The total number of unknown LSAs in this area |
No. of OSPF Areas | The number of areas configured on the router |
Table 34: Show Area LFA Output Fields
Label | Description |
Node | The IP address of the source node |
Metric | The cost to the primary route next hop |
Interface | The interface name of the primary next hop |
Nexthop | The IP address of the primary next hop |
LFA Interface | The interface name of the LFA backup next hop |
LFA Metric | The cost to the LFA backup next hop |
LFA type | The LFA protection type: link protection or node protection |
LFA Nexthop | The IP address of the LFA backup next hop |
database
Syntax
Context
Description
This command displays information about the OSPF link-state database.
When no command line options are specified, the command displays a summary output for all database entries.
Parameters
Output
The following output is an example of OSPF database information, and Table 35 describes the fields.
Table 35: Show Database Output Fields
Label | Description |
Type/ LSA Type | The LSA type |
Area ID | The OSPF area identifier |
Link State ID | The link-state ID is an LSA type-specific field containing either a number to distinguish several LSAs from the same router, an interface ID, or a router ID; it identifies the piece of the routing domain being described by the advertisement |
Adv Rtr Id/ Adv Router Id | The router identifier of the router advertising the LSA |
Age | The age of the link-state advertisement in seconds |
Sequence/ Sequence No | The signed 32-bit integer sequence number |
Cksum/ Checksum | The 32-bit unsigned sum of the link-state advertisements' LS checksums |
No. of LSAs | The number of LSAs displayed |
Options | EA: external attribute LSA support |
DC: demand circuit support | |
R: if clear, a node can participate in OSPF topology distribution without being used to forward transit traffic | |
N: type 7 LSA support | |
MC: multicast support (not applicable) | |
E: external routes support | |
V6: not applicable | |
Prefix Options | P: propagate NSSA LSA |
MC: multicast support (not applicable) | |
LA: local address capability; if set, the prefix is an IPv6 interface address of the advertising router (not applicable) | |
NU: no unicast capability; if set, the prefix is excluded from IPv6 unicast calculations (not applicable) | |
Flags | None: no flags set |
V: the router is an endpoint for one or more fully adjacent virtual links having the described area as the transit area | |
E: the router is an AS Boundary Router | |
B: the router is an Area Border Router | |
Link Count | The number of links advertised in the LSA |
Link Type (n) | The link type of the nth link in the LSA |
Network (n) | The network address of the nth link in the LSA |
Metric-0 (n) | The cost metric of the nth link in the LSA |
interface
Syntax
Context
Description
This command displays the details of the OSPF interface, which can be identified by IP address or IP interface name. If neither is specified, all in-service interfaces are displayed.
The area option displays all interfaces configured in the specified area.
The detail option produces a great amount of data. It is recommended that this option be used only when requesting a specific interface.
Parameters
Output
The following outputs are examples of OSPF interface information:
- OSPF standard interface information (Output Example, Table 36)
- OSPF detailed interface information (Output Example, Table 37)
Table 36: Show Interface Output Fields
Label | Description |
If Name | The interface name |
Area Id | A 32-bit integer uniquely identifying the area to which this interface is connected. Area ID 0.0.0.0 is used for the OSPF backbone. |
Designated rtr | The IP interface address of the router identified as the designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no designated router |
Bkup Desig Rtr | The IP interface address of the router identified as the backup designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no backup designated router |
Adm | Dn: OSPF on this interface is administratively shut down |
Up: OSPF on this interface is administratively enabled | |
Opr | Down: the initial interface state. In this state, the lower-level protocols have indicated that the interface is unusable. |
Wait: the router is trying to determine the identity of the (backup) designated router for the network | |
PToP: the interface is operational, and connects either to a physical point-to-point network or to a virtual link | |
DR: this router is the designated router for this network | |
BDR: this router is the backup designated router for this network | |
ODR: the interface is operational and part of a broadcast or NBMA network on which another router has been selected to be the designated router | |
No. of OSPF Interfaces | The number of interfaces listed |
Table 37: Show Detailed Interface Output Fields
Label | Description |
Interface | The IP address of this OSPF interface |
IP Address | The IP address and mask of this OSPF interface |
Interface Name | The interface name |
Area Id | A 32-bit integer uniquely identifying the area to which this interface is connected. Area ID 0.0.0.0 is used for the OSPF backbone. |
Priority | The priority of this interface. Used in multi-access networks, this field is used in the designated router election algorithm. |
Hello Intrvl | The length of time, in seconds, between the Hello packets that the router sends on the interface. This value must be the same for all routers attached to a common network. |
Rtr Dead Intrvl | The number of seconds that a router's Hello packets have not been seen before its neighbors declare the router down. This should be some multiple of the Hello interval. This value must be the same for all routers attached to a common network. |
Retrans Intrvl | The number of seconds between link-state advertisement retransmissions, for adjacencies belonging to this interface. This value is also used when retransmitting database description and link-state request packets. |
Poll Intrvl | The larger time interval, in seconds, between the Hello packets sent to an inactive non-broadcast multi-access neighbor |
Cfg Metric | The metric to be advertised for this interface |
Advert Subnet | False: when a point-to-point interface is configured as false, then the subnet is not advertised and the endpoints are advertised as host routes |
True: when a point-to-point interface is configured as true, then the subnet is advertised | |
Transit Delay | The estimated number of seconds it takes to transmit a link-state update packet over this interface |
Cfg IF Type | The configured interface type |
Passive | False: this interfaces operates as a normal OSPF interface with regard to adjacency forming and network and link behavior |
True: no OSPF Hellos will be sent out on this interface and the router advertises this interface as a stub network or link in its router LSAs | |
Cfg MTU | The desired size of the largest packet that can be sent or received on this OSPF interface, specified in octets. This size does include the underlying IP header length, but not the underlying layer headers and trailers. |
LFA | Indicates whether the interface is included in the LFA SPF calculation |
LFA NH Template | Indicates whether an LFA next-hop policy template is applied to this interface |
Auth Type | Identifies the authentication procedure to be used for the packet |
None: routing exchanges over the network/subnet are not authenticated | |
Simple: a 64-bit field is configured on a per-network basis. All packets sent on a particular network must have this configured value in their OSPF header 64-bit authentication field. This essentially serves as a “clear” 64-bit password. | |
MD5: a shared secret key is configured on all routers attached to a common network or subnet. For each OSPF protocol packet, the key is used to generate and verify a “message digest” that is appended to the end of the OSPF packet. | |
Admin Status | Disabled: OSPF on this interface is administratively shut down |
Enabled: OSPF on this interface is administratively enabled | |
Oper State | Down: the initial interface state. In this state, the lower-level protocols have indicated that the interface is unusable. |
Waiting: the router is trying to determine the identity of the (backup) designated router for the network | |
Point To Point: the interface is operational and connects either to a physical point-to-point network or to a virtual link | |
Designated Rtr: this router is the designated router for this network | |
Other Desig Rtr: the interface is operational and part of a broadcast or NBMA network on which another router has been selected to be the designated router | |
Backup Desig Rtr: this router is the backup designated router for this network | |
Designated Rtr | The IP interface address of the router identified as the designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no designated router |
Backup Desig Rtr | The IP interface address of the router identified as the backup designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no backup designated router |
IF Type | Broadcast: LANs, such as Ethernet |
NBMA: X.25, Frame Relay and similar technologies | |
Point-To-Point: links that are definitively point-to-point | |
Network Type | Stub: OPSF has not established a neighbor relationship with any other OSPF router on this network; therefore, only traffic sourced or destined for this network will be routed to this network |
Transit: OPSF has established at least one neighbor relationship with another OSPF router on this network; therefore, traffic en route to other networks may be routed via this network | |
Oper MTU | The operational size of the largest packet that can be sent or received on this OSPF interface, specified in octets. This size includes the underlying IP header length, but not the underlying layer headers and trailers. |
Last Enabled | The time that this interface was last enabled to run OSPF on this interface |
Te Metric | The TE metric configured for this interface. This metric is flooded out in the TE metric sub-TLV in the OSPF TE LSAs. Depending on the configuration, either the TE metric value or the native OSPF metric value is used in CSPF computations. |
Te State | The MPLS interface TE status from OSPF standpoint |
Admin Groups | The bit-map inherited from the MPLS interface that identifies the admin groups to which this interface belongs |
Ldp Sync | Specifies whether the IGP-LDP synchronization feature is enabled or disabled on all interfaces participating in the OSPF routing protocol |
Ldp Sync Wait | The time to wait for the LDP adjacency to come up |
Ldp Timer State | The state of the LDP sync time left on the OSPF interface |
Ldp Tm Left | The time left before OSPF reverts back to advertising normal metrics for this interface |
Nbr Count | The number of OSPF neighbors on the network for this interface |
If Events | The number of times this OSPF interface has changed its state, or an error has occurred since this interface was last enabled |
Tot Rx Packets | The total number of OSPF packets received on this interface since this interface was last enabled |
Tot Tx Packets | The total number of OSPF packets transmitted on this interface since this interface was last enabled |
Rx Hellos | The total number of OSPF Hello packets received on this interface since this interface was last enabled |
Tx Hellos | The total number of OSPF Hello packets transmitted on this interface since this interface was last enabled |
Rx DBDs | The total number of OSPF database description packets received on this interface since this interface was last enabled |
Tx DBDs | The total number of OSPF database description packets transmitted on this interface since this interface was last enabled |
Rx LSRs | The total number of Link-State Requests (LSRs) received on this interface since this interface was last enabled |
Tx LSRs | The total number of Link-State Requests (LSRs) transmitted on this interface since this interface was last enabled |
Rx LSUs | The total number of Link-State Updates (LSUs) received on this interface since this interface was last enabled |
Tx LSUs | The total number of Link-State Updates (LSUs) transmitted on this interface since this interface was last enabled |
Rx LS Acks | The total number of Link-State Acknowledgments received on this interface since this interface was last enabled |
Tx LS Acks | The total number of Link-State Acknowledgments transmitted on this interface since this interface was last enabled |
Retransmits | The total number of OSPF retransmits sent on this interface since this interface was last enabled |
Discards | The total number of OSPF packets discarded on this interface since this interface was last enabled |
Bad Networks | The total number of OSPF packets received with invalid network or mask since this interface was last enabled |
Bad Virt Links | The total number of OSPF packets received on this interface that are destined for a virtual link that does not exist since this interface was last enabled |
Bad Areas | The total number of OSPF packets received with an area mismatch since this interface was last enabled |
Bad Dest Addrs | The total number of OSPF packets received with the incorrect IP destination address since this interface was last enabled |
Bad Auth Types | The total number of OSPF packets received with an invalid authorization type since this interface was last enabled |
Auth Failures | The total number of OSPF packets received with an invalid authorization key since this interface was last enabled |
Bad Neighbors | The total number of OSPF packets received where the neighbor information does not match the information this router has for the neighbor since this interface was last enabled |
Bad Pkt Types | The total number of OSPF packets received with an invalid OSPF packet type since this interface was last enabled |
Bad Lengths | The total number of OSPF packets received on this interface with a total length not equal to the length given in the packet itself since this interface was last enabled |
Bad Hello Int. | The total number of OSPF packets received where the hello interval given in the packet was not equal to that configured on this interface since this interface was last enabled |
Bad Dead Int. | The total number of OSPF packets received where the dead interval given in the packet was not equal to that configured on this interface since this interface was last enabled |
Bad Options | The total number of OSPF packets received with an option that does not match those configured for this interface or area since this interface was last enabled |
Bad Versions | The total number of OSPF packets received with bad OSPF version numbers since this interface was last enabled |
Bad Checksums | The total number of OSPF packets received with bad checksums since this interface was last enabled |
LSA Count | The total number of link-state advertisements in this area’s link-state database, excluding AS External LSAs |
LSA Checksum | The 32-bit unsigned sum of the link-state database advertisements’ LS checksums contained in this area’s link-state database. This checksum excludes AS External LSAs (type 5). |
lfa-coverage
Syntax
Context
Description
This command displays OSPF LFA coverage information.
Output
The following output is an example of LFA coverage information, and Table 38 describes the fields.
Table 38: Show LFA Coverage Output Fields
Label | Description |
Area | The OSPF area in which LFA is enabled |
Node | The number of nodes in the area on which LFA is enabled |
Prefix | The number of interfaces on the nodes on which LFA is enabled |
neighbor
Syntax
Context
Description
This command displays all neighbor information or all information on neighbors of a router identified by interface name or router ID.
The detail option produces a large amount of data. It is recommended that this option be used only when requesting a specific neighbor.
Parameters
Output
The following outputs are examples of OSPF neighbor information:
- OSPF standard neighbor information (Output Example, Table 39)
- OSPF detailed neighbor information (Output Example, Table 40)
Table 39: Show Neighbor Output Fields
Label | Description |
Interface-Name | The interface name or IP address this neighbor is using in its IP source address. On links with no address, this will not be 0.0.0.0, but the address of another of the neighbor's interfaces. |
Rtr Id | A 32-bit integer uniquely identifying the neighboring router in the Autonomous System |
State | Down: the initial state of a neighbor conversation. It indicates that there has been no recent information received from the neighbor. |
Attempt: this state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort should be made to contact the neighbor. | |
Init: in this state, a Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor (that is, the router itself did not appear in the neighbor's Hello packet). | |
Two Way: in this state, communication between the two routers is bidirectional | |
ExchStart: the first step in creating an adjacency between the two neighboring routers. The goal of this step is to decide which router is the master, and to decide upon the initial database descriptor sequence number. | |
Exchange: in this state, the router is describing its entire link-state database by sending database description packets to the neighbor | |
Loading: in this state, Link-State Request packets are sent to the neighbor asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state | |
Full: in this state, the neighboring routers are fully adjacent. These adjacencies will now appear in router-LSAs and network-LSAs. | |
Pri | The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become the designated router on this particular network. |
RetxQ | The current length of the retransmission queue |
TTL | The time until this neighbor is declared down; this timer is set to the dead router interval when a valid Hello packet is received from the neighbor |
No. of Neighbors | The number of adjacent OSPF neighbors on this interface |
Table 40: Show Detailed Neighbor Output Fields
Label | Description |
Neighbor IP Addr | The IP address this neighbor is using in its IP source address. On links with no IP address, this will not be 0.0.0.0, but the address of another of the neighbor's interfaces. |
Local IF IP Addr | The IP address of this OSPF interface |
Area Id | A 32-bit integer uniquely identifying the area to which this interface is connected. Area ID 0.0.0.0 is used for the OSPF backbone. |
Designated Rtr | The IP interface address of the router identified as the designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no designated router |
Neighbor Rtr Id | A 32-bit integer uniquely identifying the neighboring router in the AS |
Neighbor State | Down: the initial state of a neighbor conversation. It indicates that there has been no recent information received from the neighbor. |
Attempt: this state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort should be made to contact the neighbor. | |
Init: in this state, a Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor (that is, the router itself did not appear in the neighbor's Hello packet). | |
Two Way: in this state, communication between the two routers is bidirectional | |
Exchange start: the first step in creating an adjacency between the two neighboring routers. The goal of this step is to decide which router is the master, and to decide upon the initial database descriptor sequence number. | |
Exchange: in this state, the router is describing its entire link-state database by sending database description packets to the neighbor | |
Loading: in this state, Link-State Request packets are sent to the neighbor asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state | |
Full: in this state, the neighboring routers are fully adjacent. These adjacencies will now appear in router-LSAs and network-LSAs. | |
Priority | The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become the designated router on this particular network. |
Retrans Q Length | The current length of the retransmission queue |
Options | E: external routes support |
MC: multicast support (not applicable) | |
N/P: type 7 LSA support | |
EA: external attribute LSA support | |
DC: demand circuit support | |
O: opaque LSA support | |
Backup Desig Rtr | The IP interface address of the router identified as the backup designated router for the network in which this interface is configured Set to 0.0.0.0 if there is no backup designated router |
Events | The number of times this neighbor relationship has changed state, or an error has occurred |
Last Event Time | The time that the last event occurred that affected the adjacency to the neighbor |
Up Time | The uninterrupted time, in hundredths of seconds, that the adjacency to this neighbor has been up. To evaluate when the last state change occurred, see last event time. |
Time Before Dead | The time until this neighbor is declared down; this timer is set to the dead router interval when a valid Hello packet is received from the neighbor |
Bad Nbr States | The total number of OSPF packets received when the neighbor state was not expecting to receive this packet type since this interface was last enabled |
LSA Inst fails | The total number of times that an LSA could not be installed into the link-state database due to a resource allocation issue since this interface was last enabled |
Bad Seq Nums | The total number of times that a database description packet was received with a sequence number mismatch since this interface was last enabled |
Bad MTUs | The total number of times that the MTU in a received database description packet was larger than the MTU of the receiving interface since this interface was last enabled |
Bad Packets | The total number of times that an LS update was received with an illegal LS type or an option mismatch since this interface was last enabled |
LSA not in LSDB | The total number of times that an LS request was received for an LSA not installed in the LSDB of this router since this interface was last enabled |
Option Mismatches | The total number of times that an LS update was received with an option mismatch since this interface was last enabled |
Nbr Duplicates | The total number of times that a duplicate database description packet was received during the exchange state since this interface was last enabled |
range
Syntax
Context
Description
This command displays ranges of addresses on an ABR for the purpose of route summarization or suppression.
Parameters
Output
The following output is an example of OSPF range information, and Table 41 describes the fields.
Table 41: Show Area Range Output Fields
Label | Description |
Area Id | A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used for the OSPF backbone. |
Prefix | The mask for the range expressed as a decimal integer mask length or in dotted-decimal notation |
Advertise | False: the specified address/mask is not advertised outside the area |
True: the specified address/mask is advertised outside the area | |
LSDB Type | NSSA: this range was specified in the NSSA context, and specifies that the range applies to external routes (via type 7 LSAs) learned within the NSSA when the routes are advertised to other areas as type 5 LSAs |
Summary: this range was not specified in the NSSA context; the range applies to summary LSAs even if the area is an NSSA |
routes
Syntax
Context
Description
This command displays information on OSPF routes.
Parameters
Output
The following outputs are examples of OSPF route information.
spf
Syntax
Context
Description
This command displays statistics of shortest path first (SPF) calculations.
Parameters
Output
The following output is an example of SPF information, and Table 42 describes the fields.
Table 42: Show SPF Output Fields
Label | Description |
Total SPF Runs | The total number of incremental SPF runs triggered by new or updated LSAs |
Last Full SPF run @ | The date and time that the external OSPF SPF was last run |
Last Full SPF Time | The length of time, in seconds, when the last full SPF was run |
Intra SPF Time | The time that intra-area SPF was last run on this area |
Inter SPF Time | The total number of incremental SPF runs triggered by new or updated type 3 and type 4 summary LSAs |
Extern SPF Time | The total number of incremental SPF runs triggered by new or updated type 5 external LSAs |
RTM Updt Time | The time, in hundredths of seconds, used to perform a total SPF calculation |
Min/Avg/Max Full SPF Times | Min: the minimum time, in hundredths of seconds, used to perform a total SPF calculation |
Avg: the average time, in hundredths of seconds, of all the SPF calculations performed by this OSPF router | |
Max: the maximum time, in hundredths of seconds, used to perform a total SPF calculation | |
Min/Avg/Max RTM Updt Times | Min: the minimum time, in hundredths of seconds, used to perform an RTM update Note: the RTM update is performed after the SPF calculation. The update is used to inform the routing table manager of any route or cost changes from the latest SPF calculation. |
Avg: the average time, in hundredths of seconds, of all the RTM updates performed by this OSPF router | |
Max: the maximum time, in hundredths of seconds, used to perform an RTM update | |
Total Sum Incr SPF Runs | The total number of incremental SPF runs triggered by new or updated type 3 and type 4 summary LSAs |
Total Ext Incr SPF Runs | The total number of incremental SPF runs triggered by new or updated type 5 external LSAs |
Total LFA SPF Runs | The total number of incremental LFA SPF runs triggered by new or updated LSAs |
Last LFA SPF run @ | The date and time that the external OSPF LFA SPF was last run |
Last LFA SPF Time | The length of time, in seconds, when the last LFA SPF was run |
Min/Avg/Max LFA SPF Times | Min: the minimum time, in hundredths of seconds, used to perform an LFA SPF calculation |
Avg: the average time, in hundredths of seconds, of all the LFA SPF calculations performed by this OSPF router | |
Max: the maximum time, in hundredths of seconds, used to perform an LFA SPF calculation |
statistics
Syntax
Context
Description
This command displays the global OSPF statistics.
Output
The following output is an example of OSPF statistical information, and Table 43 describes the fields.
Table 43: Show OSPF Statistics Output Fields
Label | Description |
Rx Packets | The total number of OSPF packets received on all OSPF enabled interfaces |
Tx Packets | The total number of OSPF packets transmitted on all OSPF enabled interfaces |
Rx Hellos | The total number of OSPF Hello packets received on all OSPF enabled interfaces |
Tx Hellos | The total number of OSPF Hello packets transmitted on all OSPF enabled interfaces |
Rx DBDs | The total number of OSPF database description packets received on all OSPF enabled interfaces |
Tx DBDs | The total number of OSPF database description packets transmitted on all OSPF enabled interfaces |
Rx LSRs | The total number of OSPF Link-State Requests (LSRs) received on all OSPF enabled interfaces |
Tx LSRs | The total number of OSPF Link-State Requests (LSRs) transmitted on all OSPF enabled interfaces |
Rx LSUs | The total number of OSPF Link-State Updates (LSUs) received on all OSPF enabled interfaces |
Tx LSUs | The total number of OSPF Link-State Updates (LSUs) transmitted on all OSPF enabled interfaces |
Rx LS Acks | The total number of OSPF Link-State Acknowledgments received on all OSPF enabled interfaces |
New LSAs Recvd | The total number of new OSPF Link-State Advertisements received on all OSPF enabled interfaces |
New LSAs Orig | The total number of new OSPF Link-State Advertisements originated on all OSPF enabled interfaces |
Ext LSAs Count | The total number of OSPF External Link-State Advertisements |
No of Areas | The number of areas configured for OSPF (maximum 4) |
No of Interfaces | The number of interfaces configured for OSPF on the router |
No of Neighbors | The number of adjacent OSPF neighbors on this interface |
Retransmits | The total number of OSPF Retransmits transmitted on all OSPF enabled interfaces |
Discards | The total number of OSPF packets discarded on all OSPF enabled interfaces |
Bad Networks | The total number of OSPF packets received on all OSPF enabled interfaces with invalid network or mask |
Bad Virt Links | The total number of OSPF packets received on all OSPF enabled interfaces that are destined for a virtual link that does not exist |
Bad Areas | The total number of OSPF packets received on all OSPF enabled interfaces with an area mismatch |
Bad Dest Addrs | The total number of OSPF packets received on all OSPF enabled interfaces with the incorrect IP destination address |
Bad Auth Types | The total number of OSPF packets received on all OSPF enabled interfaces with an invalid authorization type |
Auth Failures | The total number of OSPF packets received on all OSPF enabled interfaces with an invalid authorization key |
Bad Neighbors | The total number of OSPF packets received on all OSPF enabled interfaces where the neighbor information does not match the information this router has for the neighbor |
Bad Pkt Types | The total number of OSPF packets received on all OSPF enabled interfaces with an invalid OSPF packet type |
Bad Lengths | The total number of OSPF packets received on all OSPF enabled interfaces with a total length not equal to the length given in the packet itself |
Bad Hello Int. | The total number of OSPF packets received on all OSPF enabled interfaces where the hello interval given in the packet was not equal to that configured for the respective interface |
Bad Dead Int. | The total number of OSPF packets received on all OSPF enabled interfaces where the dead interval given in the packet was not equal to that configured for the respective interface |
Bad Options | The total number of OSPF packets received on all OSPF enabled interfaces with an option that does not match those configured for the respective interface or area |
Bad Versions | The total number of OSPF packets received on all OSPF enabled interfaces with bad OSPF version numbers |
Bad Checksums | The total number of OSPF packets received with bad checksums since this interface was last enabled |
Failed SPF Attempts | The total number of failed SPF calculation attempts |
CSPF Requests | The total number of constraint-based SPF requests |
CSPF Request Drops | The total number of constraint-based SPF requests dropped |
CSPF Path Found | A path that fulfills the set of constraints defined in MPLS traffic engineering |
CSPF Path Not Found | A path that does not fulfill the set of constraints defined in MPLS traffic engineering |
Total SPF Runs | The total number of incremental SPF runs triggered by new or updated LSAs |
Total LFA SPF Runs | The total number of incremental LFA SPF runs triggered by new or updated LSAs |
status
Syntax
Context
Description
This command displays the general status of OSPF.
Output
The following output is an example of OSPF status information, and Table 44 describes the fields.
Table 44: Show OSPF Status Output Fields
Label | Description |
OSPF Cfg Router Id | The router ID configured for the router |
OSPF Oper Router ID | The operational router ID. The 7705 SAR defaults to the system IP address or, if not configured, the last 4 bytes of the system MAC address. |
OSPF Version | The current version number of the OSPF protocol: 2 |
OSPF Admin Status | Disabled: the OSPF process is disabled on all interfaces |
Enabled: the OSPF process is active on at least one interface | |
OSPF Oper Status | Disabled: the OSPF process is not operational on all interfaces |
Enabled: the OSPF process is operational on at least one interface | |
GR Helper Mode | Disabled: Graceful Restart Helper is disabled |
Enabled: Graceful Restart Helper is enabled | |
Preference | The route preference for OSPF internal routes |
External Preference | The route preference for OSPF external routes |
Backbone Router | False: this router is not configured as an OSPF backbone router |
True: this router is configured as an OSPF backbone router | |
Area Border Router | False: this router is not configured as an area border router |
True: this router is configured as an area border router | |
AS Border Router | False: this router is not configured as an Autonomous System border (boundary) router |
True: this router is configured as an Autonomous System border (boundary) router | |
Opaque LSA Support | False: this router does not support opaque LSAs |
True: this router supports opaque LSAs | |
Traffic Engineering Support | False: this router does not support traffic engineering |
True: this router supports traffic engineering | |
RFC 1583 Compatible | False: this router is not RFC 1583 compatible |
True: this router is RFC 1583 compatible | |
Demand Exts Support | False: this router does not demand external route support |
True: this router does demand external route support | |
In Overload State | False: this router is not in an overload state |
True: this router is in an overload state | |
In External Overflow State | False: this router is not in an external overflow state |
True: this router is in an external overflow state | |
Exit Overflow Interval | The time to wait before the router exits the overflow state |
Last Overflow Entered | Indicates when the router last entered an overflow state |
Last Overflow Exit | Indicates when the router last exited an overflow state |
External LSA limit | The number of external LSAs allowed |
Reference bandwidth | The configured reference bandwidth, in kilobits per second |
Init SPF Delay | The initial SPF calculation delay |
Sec SPF Delay | The SPF calculation delay between the first and second calculations |
Max SPF Delay | The maximum interval between two consecutive SPF calculations |
Min LS Arrival Interval | The minimum interval between LSAs |
Init LSA Gen Delay | The initial LSA generation delay |
Sec LSA Gen Delay | The delay between the generation of the first and second LSAs |
Max LSA Gen Delay | The maximum interval between two consecutive LSAs |
Last Ext SPF Run | The time that the last external SPF calculation was run |
Ext LSA Cksum Sum | The 32-bit unsigned sum of the LS checksums of the external LSAs contained in this area’s link-state database |
OSPF Last Enabled | The time that OSPF was last enabled on the interface |
Unicast Import | Indicates whether routes are imported into the unicast RTM |
Export Policies | Indicates whether any export routing policies have been applied to the OSPF interface |
Import Policies | Indicates whether any import routing policies have been applied to the OSPF interfaced |
Lfa Policies | Lists the defined LFA policies |
OSPF Ldp Sync Admin Status | Indicates whether the IGP-LDP synchronization feature is enabled or disabled on all interfaces participating in the OSPF routing protocol |
RSVP-Shortcut | Indicates whether RSVP-TE shortcuts (IGP shortcuts) are enabled |
Advertise-Tunnel-Link | Indicates whether forwarding adjacencies are enabled |
LFA | Indicates whether LFA is enabled |
virtual-link
Syntax
Context
Description
This command displays information for OSPF virtual links.
Parameters
Output
The following output is an example of OSPF virtual link information, and Table 45 describes the fields.
Table 45: Show Virtual Link Output Fields
Label | Description |
Nbr Rtr ID | The router IDs of neighboring routers |
Area Id | A 32-bit integer that identifies an area |
Local Interface | The IP address of the local egress interface used to maintain the adjacency to reach this virtual neighbor |
Metric | The metric value associated with the route. This value is used when importing this static route into other protocols. When the metric is configured as 0, then the metric configured in OSPF, default-metric, applies. This value is also used to determine which static route to install in the forwarding table. |
State | The operational state of the virtual link to the neighboring router |
Authentication | Specifies whether authentication is enabled for the interface or virtual link |
Hello Intrvl | The length of time, in seconds, between the Hello packets that the router sends on the interface |
Rtr Dead Intrvl | The total number of OSPF packets received where the dead interval given in the packet was not equal to that configured on this interface since the OSPF admin status was enabled |
Tot Rx Packets | The total number of OSPF packets received on this interface since the OSPF admin status was enabled |
Rx Hellos | The total number of OSPF Hello packets received on this interface since the OSPF admin status was enabled |
Rx DBDs | The total number of OSPF database description packets received on this interface since the OSPF admin status was enabled |
Rx LSRs | The total number of Link-State Requests (LSRs) received on this interface since the OSPF admin status was enabled |
Rx LSUs | The total number of Link-State Updates (LSUs) received on this interface since the OSPF admin status was enabled |
Rx LS Acks | The total number of Link-State Acknowledgments received on this interface since the OSPF admin status was enabled |
Tot Tx Packets | The total number of OSPF packets transmitted on this interface since the OSPF admin status was enabled |
Tx Hellos | The total number of OSPF Hello packets transmitted on this interface since the OSPF admin status was enabled |
Tx DBDs | The total number of OSPF database description packets transmitted on this interface since the OSPF admin status was enabled |
Tx LSRs | The total number of OSPF Link-State Requests (LSRs) transmitted on this interface since the OSPF admin status was enabled |
Tx LSUs | The total number of OSPF Hello packets transmitted on this interface since the OSPF admin status was enabled |
Tx LS Acks | The total number of OSPF Link-State Acknowledgments transmitted on this interface since the OSPF admin status was enabled |
Retransmits | The total number of OSPF retransmits sent on this interface since the OSPF admin status was last enabled |
Discards | The total number of OSPF packets discarded on this interface since the OSPF admin status was last enabled |
Bad Networks | The total number of OSPF packets received with invalid network or mask since the OSPF admin status was last enabled |
Bad Versions | The total number of OSPF packets received with bad OSPF version numbers since the OSPF admin status was last enabled |
Bad Areas | The total number of OSPF packets received with an area mismatch since the OSPF admin status was last enabled |
Bad Dest Addrs | The total number of OSPF packets received with the incorrect IP destination address since the OSPF admin status was last enabled |
Bad Auth Types | The total number of OSPF packets received with an invalid authorization type since the OSPF admin status was last enabled |
Auth Failures | The total number of OSPF packets received with an invalid authorization key since the OSPF admin status was last enabled |
Bad Neighbors | The total number of OSPF packets received where the neighbor information does not match the information this router has for the neighbor since the OSPF admin status was last enabled |
Bad Pkt Types | The total number of OSPF packets received with an invalid OSPF packet type since the OSPF admin status was last enabled |
Bad Lengths | The total number of OSPF packets received on this interface with a total length not equal to the length given in the packet itself since the OSPF admin status was last enabled |
Bad Hello Int. | The total number of OSPF packets received where the hello interval given in the packet was not equal to that configured on this interface since the OSPF admin status was last enabled |
Bad Dead Int. | The total number of OSPF packets received where the dead interval given in the packet was not equal to that configured on this interface since the OSPF admin status was last enabled |
Bad Options | The total number of OSPF packets received with an option that does not match those configured for this interface or area since the OSPF admin status was last enabled |
Retrans Intrvl | The length of time, in seconds, that OSPF waits before retransmitting an unacknowledged link-state advertisement (LSA) to an OSPF neighbor |
Transit Delay | The time, in seconds, that it takes to transmit a link-state advertisement (LSA) on the interface or virtual link |
Last Event | The date and time that an event was last associated with this OSPF interface |
virtual-neighbor
Syntax
Context
Description
This command displays virtual neighbor information.
The detail option produces a large amount of data. It is recommended that this option be used only when requesting information on a specific neighbor.
Parameters
Output
The following output is an example of OSPF virtual neighbor information, and Table 46 describes the fields.
Table 46: Show Virtual Neighbor Output Fields
Label | Description |
Nbr IP Addr | The IP address this neighbor is using in its IP source address. On links with no address, this will not be 0.0.0.0, but the address of another of the neighbor's interfaces. |
Nbr Rtr ID | The router IDs of neighboring routers |
Transit Area | The transit area ID that links the backbone area with the area that has no physical connection with the backbone |
RetxQ Len/ Retrans Q Length | The current length of the retransmission queue |
No. of Neighbors | The total number of OSPF neighbors adjacent on this interface, in a state of INIT or greater, since the OSPF admin status was enabled |
Nbr State | The operational state of the virtual link to the neighboring router |
Options | The total number of OSPF packets received with an option that does not match those configured for this virtual interface or transit area since the OSPF admin status was enabled |
Events | The total number of events that have occurred since the OSPF admin status was enabled |
Last Event Time | The date and time that an event was last associated with this OSPF interface |
Up Time | The uninterrupted time, in hundredths of seconds, that the adjacency to this neighbor has been up |
Dead Time/Time Before Dead | The amount of time, in seconds, until the dead router interval expires |
Bad Nbr States | The total number of OSPF packets received where the neighbor information does not match the information this router has for the neighbor since the OSPF admin status was last enabled |
LSA Inst fails | The total number of times an LSA could not be installed into the LSDB due to a resource allocation issue since the OSPF admin status was last enabled |
Bad Seq Nums | The total number of times that a database description packet was received with a sequence number mismatch since the OSPF admin status was last enabled |
Bad MTUs | The total number of times that the MTU in a received database description packet was larger than the MTU of the receiving interface since the OSPF admin status was enabled |
Bad Packets | The total number of times that an LS update was received with an illegal LS type or an option mismatch since the OSPF admin status was enabled |
LSA not in LSDB | The total number of times that an LS request was received for an LSA not installed in the LSDB of this router since the OSPF admin status was enabled |
Option Mismatches | The total number of times that an LS update was received with an option mismatch since the OSPF admin status was enabled |
Nbr Duplicates | The total number of times that a duplicate database description packet was received during the Exchange state since the OSPF admin status was enabled |
4.13.2.3. Clear Commands
ospf
Syntax
Context
Description
This command clears and resets OSPF protocol entities.
ospf3
Syntax
Context
Description
This command clears and resets OSPFv3 protocol entities.
database
Syntax
Context
Description
This command clears all LSAs received from other nodes and refreshes all self-originated LSAs.
Parameters
export
Syntax
Context
Description
This command re-evaluates all effective export route policies.
neighbor
Syntax
Context
Description
This command marks the neighbor as dead and reinitiates the affected adjacencies.
Parameters
statistics
Syntax
Context
Description
This command clears all neighbor, router, interface, SPF, and global statistics for OSPF.
4.13.2.4. Debug Commands
ospf
Syntax
Context
Description
This command enables the context for OSPF debugging purposes.
ospf3
Syntax
Context
Description
This command enables the context for OSPFv3 debugging purposes.
area
Syntax
Context
Description
This command enables or disables debugging for an OSPF area.
Parameters
area-range
Syntax
Context
Description
This command enables or disables debugging for an OSPF area range.
Parameters
cspf
Syntax
Context
Description
This command enables or disables debugging for an OSPF constraint-based shortest path first (CSPF).
Parameters
interface
Syntax
Context
Description
This command enables or disables debugging for an OSPF interface.
Parameters
leak
Syntax
Context
Description
This command enables or disables debugging for OSPF leaks.
Parameters
lsdb
Syntax
Context
Description
This command enables or disables debugging for an OSPF link-state database.
Parameters
misc
Syntax
Context
Description
This command enables or disables debugging for miscellaneous OSPF events.
neighbor
Syntax
Context
Description
This command enables or disables debugging for an OSPF neighbor.
Parameters
nssa-range
Syntax
Context
Description
This command enables or disables debugging for an NSSA range.
Parameters
packet
Syntax
Context
Description
This command enables or disables debugging for OSPF packets.
Parameters
rsvp-shortcut
Syntax
Context
Description
This command enables or disables debugging for RSVP-TE LSPs that are used as shortcuts.
Parameters
rtm
Syntax
Context
Description
This command enables or disables debugging for the OSPF routing table manager.
Parameters
spf
Syntax
Context
Description
This command enables or disables debugging for OSPF SPF. Information regarding overall SPF start and stop times are shown. To see detailed information regarding the SPF calculation of a given route, the route must be specified as an optional argument.
Parameters
virtual-neighbor
Syntax
Context
Description
This command enables or disables debugging for an OSPF virtual neighbor.