SupportDocumentationSwitchesCampus SwitchS3700&S5700&S6700Reference GuidesCommand Reference

CloudEngine S5700 V600R022C01 Command Reference

OSPF Configuration Commands

OSPF Configuration Commands

abr-summary

Function

The abr-summary command configures route summarization on an area border router (ABR).

The undo abr-summary command disables route summarization from an ABR.

By default, route summarization is not configured on ABRs.

Format

abr-summary ip-address mask [ [ advertise | [ cost { cost-value | inherit-minimum } ] | [ generate-null0-route ] ] * | [ not-advertise | [ cost { cost-value | inherit-minimum } ] ] * | [ generate-null0-route | [ advertise ] | [ cost { cost-value | inherit-minimum } ] ] * ]

undo abr-summary ip-address mask

Parameters

Parameter Description Value
ip-address

Specifies the IP address of a summary route.

The value is in dotted decimal notation.
mask

Specifies the IP address mask of the summary route.

The value is in dotted decimal notation.
advertise

Advertises the summary route.

By default, the summary route is advertised.

-
cost cost-value

Specifies the cost of the summary route.

The value is an integer ranging from 0 to 16777214.

By default, the largest cost of the specific routes for summarization is used as the cost of the summary route.
inherit-minimum

Indicates that the smallest cost of the specific routes for summarization is used as the cost of the summary route.

-
generate-null0-route

Generates a black-hole route in the RM module to prevent routing loops.

-
not-advertise

Prevents the summary route from being advertised.

By default, the summary route is advertised.

-

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a large-scale OSPF network, route lookup may slow down because of the large size of the routing table. To reduce the size of the routing table and simplify management, configure route summarization.

This command enables routes with the same IP prefix to be summarized into one route. If a link connected to a device within an IP address range that has been summarized alternates between Up and Down, the link status change is not advertised to the devices beyond the IP address range. This prevents route flapping and improves network stability.

The abr-summary command configures route summarization on an ABR. When an ABR transmits routing information to other areas, it originates Type 3 Link Status Advertisements (LSAs) per network segment. If contiguous segments exist in this area, run the abr-summary command to summarize these segments into one segment so that the ABR sends only one summary LSA. The summarization reduces the routing table size and improves performance of the device.

Prerequisites

The segments that need to be summarized have been specified using the network command.

Precautions

  • This command applies only to ABRs and is used to summarize routes in an area. Using the asbr-summary command, you can configure an AS boundary router (ASBR) to summarize the routes imported by OSPF.
  • In the same process, ABRs in different areas cannot be configured with abr-summary summarized routes with the same prefix mask.
  • The cost inherit-minimum command can be run only in a VPN OSPF process.

Example

# In OSPF area 1, summarize routes in the network segments (10.42.10.0/24 and 10.42.110.0/24) into one 10.42.0.0/16, and advertise the summary route to other areas.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 1
[HUAWEI-ospf-100-area-0.0.0.1] network 10.42.10.0 0.0.0.255
[HUAWEI-ospf-100-area-0.0.0.1] network 10.42.110.0 0.0.0.255
[HUAWEI-ospf-100-area-0.0.0.1] abr-summary 10.42.0.0 255.255.0.0

area

Function

The area command creates an OSPF area and displays the OSPF area view.

The undo area command deletes a specified area.

By default, no OSPF area is created.

Format

area { area-id | area-idipv4 }

undo area { area-id | area-idipv4 }

Parameters

Parameter Description Value
area-id

Specifies the area ID in decimal format.

The value is an integer from 0 to 4294967295.

A decimal value is automatically converted to a dotted-decimal notation value based on the following rules:

  • For a value of 255 or less, it is padded directly with three zeros in the format X.X.X.X. For example, a value of 255 will be converted to 0.0.0.255.
  • For a value of 256 or greater, each X in the format X.X.X.X can be a maximum of 255. Starting from the right-most X, the X to its immediate left increments by 1 each time it reaches 256. For example, a value of 256 will be converted to 0.0.1.0, 511 will be converted to 0.0.1.255, and 65536 will be converted to 0.1.0.0.
area-idipv4

Specifies an area ID in IP address format.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The number of devices increases with the network expansion, which leads to a large LSDB on each OSPF-enabled device on a large-scale network. Consequently, route flapping frequently occurs, and a large number of OSPF packets are transmitted on the network, which wastes bandwidth resources.

OSPF addresses the preceding problem by logically partitioning an AS into different areas.

Prerequisites

Before creating and entering an OSPF area, you need to enter the OSPF process.

Precautions

After an AS is partitioned into different areas, not all areas are equal. The area with ID 0 is a backbone area. The backbone area is responsible for forwarding inter-area routes. In addition, the routing information between non-backbone areas must be forwarded through the backbone area.

The first time the area command is run, an OSPF area is created and the OSPF area view is displayed; running the area command later enters the OSPF area view only.

If the undo area command is run, all configurations in the OSPF area are deleted. Therefore, exercise caution when using the command.

Example

# Enter the view of an OSPF area.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 0

asbr-summary

Function

The asbr-summary command configures an AS boundary router (ASBR) to summarize routes imported by OSPF.

The undo asbr-summary command disables ASBRs from summarizing routes imported by OSPF.

By default, ASBRs do not summarize routes imported by OSPF.

Format

asbr-summary ip-address mask [ [ not-advertise | generate-null0-route ] | tag tag-value | cost cost-value | distribute-delay interval ] *

undo asbr-summary ip-address mask

Parameters

Parameter Description Value
ip-address

Specifies the IP address of a summary route.

The value is in dotted decimal notation.
mask

Specifies the IP address mask of the summary route.

The value is in dotted decimal notation.
not-advertise

Prevents the summary route from being advertised.

If this parameter is not specified, the summary route is advertised.

-
generate-null0-route

Generates a black-hole route in the RM module to prevent routing loops.

-
tag tag-value

Specifies the tag of the summary route.

The value is an integer ranging from 0 to 4294967295.
cost cost-value

Specifies the cost of a summary route.

The value is an integer ranging from 0 to 16777214.

By default:

  • For Type 1 external routes, the largest cost of the routes for summarization is used as the cost of the summary route.
  • For Type 2 external routes, the largest cost of the routes for summarization plus 1 is used as the cost of the summary route.
distribute-delay interval

Specifies the delay for advertising a summary route.

The value is an integer ranging from 1 to 65535.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a large-scale OSPF network, route lookup may slow down because of the large size of the routing table. To reduce the size of the routing table and simplify management, configure route summarization.

Routes with the same IP prefix can be summarized into one route. If a link connected to a device within an IP address range that has been summarized alternates between Up and Down, the link status change is not advertised to the devices beyond the IP address range. This prevents route flapping and improves network stability.

Imported routes with the same prefix can be summarized into one route and advertised as one route using the asbr-summary command. Route summarization reduces the routing table size and improves device performance.

After route summarization:

  • If the local device is an ASBR in a common area, the local device summarizes all imported Type 5 LSAs within the summarized address range.
  • If the local device is an ASBR in an NSSA, the local device summarizes all imported Type 7 LSAs within the summarized address range.
  • If the local device functions as both an ASBR and ABR in an NSSA, the local device summarizes all imported Type 5 and Type 7 LSAs within the address range. It also summarizes the Type 5 LSAs that are translated from Type 7 LSAs.

Precautions

In case of a large number of summary routes, you can set a delay in advertising them. This ensures that the summary routes advertised each time contain more valid routes and prevents incorrect routing information in case of network flapping.

Example

# Configure route summarization for imported routes.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] asbr-summary 10.2.0.0 255.255.0.0 not-advertise tag 2 cost 100

authentication-mode (OSPF area view)

Function

The authentication-mode command configures an authentication mode and a password for an OSPF area.

The undo authentication-mode command cancels the configuration.

By default, authentication is not configured for an OSPF area. Configuring authentication is recommended to ensure system security.

Format

authentication-mode simple [ plain SPlainText | [ cipher ] SCipherText ]

authentication-mode { md5 | hmac-md5 | hmac-sha256 } [ KeyID { plain MPlainText | [ cipher ] MCipherText } ]

authentication-mode keychain Keychain-Name

undo authentication-mode

Parameters

Parameter Description Value
plain

Indicates plaintext authentication. You can only type in plaintext passwords, and the passwords are displayed in plaintext in the configuration file.

When configuring an authentication password, select the ciphertext mode. If you select the plaintext mode, the password is saved as a plaintext in the configuration file, which has a high risk. To ensure device security, change the password periodically.

By default, cipher takes effect for simple authentication.
SPlainText

Specifies a plaintext password.

The value is a character string.

  • In simple mode, the value is a string of 1 to 8 characters.

Description:

The value cannot contain question marks (?) or spaces but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
cipher

Specifies the ciphertext mode. You can enter a cleartext or a ciphertext, but the password is displayed in ciphertext in the configuration file.

By default, cipher takes effect for MD5, HMAC-MD5, or HMAC-SHA256 authentication.
SCipherText

Specifies a ciphertext password.

The value is a character string.

  • In simple mode, a simple password is a string of 1 to 8 characters, and a ciphertext password is a string of 24 to 128 characters.

Description:

The value cannot contain question marks (?) or spaces but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
simple

Sets the simple authentication mode.

By default, the simple authentication mode is cipher.

To prevent high security risks, you are advised to select the ciphertext mode. To ensure device security, change the password periodically.

-
md5

Indicates MD5 authentication.

For the sake of security, using the HMAC-SHA256 algorithm rather than the MD5 algorithm is recommended.

-
hmac-md5

Indicates HMAC-MD5 authentication.

For the sake of security, using the HMAC-SHA256 algorithm rather than the HMAC-MD5 algorithm is recommended.

-
hmac-sha256

Indicates HMAC SHA256 ciphertext authentication.

-
KeyID

This object indicates the key ID for ciphertext authentication on an interface. The key ID must be the same as that on the peer end.

The value is an integer ranging from 1 to 255.
MPlainText

Specifies a plaintext password.

The value is a character string.

  • In md5, hmac-md5, or hmac-sha256 mode, the value is a string of 1 to 255 characters.

Description:

The value cannot contain question marks (?) or spaces but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
MCipherText

Specifies a ciphertext password.

The value is a character string.

  • In md5, hmac-md5, or hmac-sha256 mode, the value is a string of 1 to 255 plaintext characters or a string of 20 to 432 ciphertext characters.

Description:

The value cannot contain question marks (?) or spaces but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
keychain

Specifies the keychain authentication mode.

Before configuring keychain authentication, run the keychain command to create a keychain, the key-id command to configure a key ID, the key-string command to configure a password, and the algorithm command to configure an algorithm. Otherwise, OSPF authentication fails.

Currently, OSPF supports MD5, SHA-1, SHA-256, SM3, HMAC-MD5, HMAC-SHA1-12, HMAC-SHA1-20, HMAC-SHA256, HMAC-SHA384, and HMAC-SHA512 algorithms.

If the dependent keychain is deleted, the neighbor relationship may be interrupted. Therefore, exercise caution when deleting the keychain.

To ensure high security, using the HMAC-SHA256 algorithm instead of the SHA-1 and MD5 algorithms is recommended.

-
Keychain-Name

Specifies the name of a keychain.

The value is a string of 1 to 47 case-insensitive characters.

The value cannot contain question marks (?) and spaces However, when double quotation marks are used around the password, spaces are allowed in the password. In this case, the double quotation marks at both ends of the password are used as a part of the password.

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF authentication can be configured to improve network security and meet high security demands. When area authentication is used, interfaces on all devices in an area must have the same area authentication mode and the password.

Precautions

The priority of area authentication is lower than that of interface authentication. The priority of interface authentication is set using the ospf authentication-mode command.

For security purposes, md5 and hmac-md5 are not recommended. If they must be used, run the install feature-software WEAKEA command to install the weak security algorithm/protocol feature package WEAKEA first.

Example

# Configure HMAC SHA256 authentication for OSPF area 0.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 0
[HUAWEI-ospf-100-area-0.0.0.0] authentication-mode hmac-sha256 1 cipher YsHsjx_202206

bandwidth-config enable

Function

The bandwidth-config enable command enables a device to use the configuration bandwidth of each OSPF interface to calculate the cost for the interface.

The undo bandwidth-config enable command disables a device from using the configuration bandwidth of each OSPF interface to calculate the cost for the interface.

By default, the configuration bandwidth of an OSPF interface is not used in cost calculation for the interface.

Format

bandwidth-config enable

undo bandwidth-config enable

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

External factors may affect the physical bandwidth of links and change the physical bandwidth of interfaces, which in turn affects network performance. To configure a device to adjust and optimize route selection rules, you can run the bandwidth command in the interface view to set configuration bandwidth for the interface, and then run the bandwidth-config enable command to enable the device to calculate the cost for the interface based on the configuration bandwidth of the interface.

Precautions

  • If the bandwidth command is not run, the cost is calculated based on the physical bandwidth of each OSPF interface.
  • If the bandwidth-config enable command is not run, the cost is calculated based on the physical bandwidth of each OSPF interface.

Example

# Enable a device to use the configuration bandwidth of each OSPF interface to calculate the cost for the interface.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] bandwidth-config enable

bandwidth-reference (OSPF view)

Function

The bandwidth-reference command sets the bandwidth reference value for interface cost calculation.

The undo bandwidth-reference command restores the default configuration.

The default bandwidth reference value is 100 Mbit/s.

Format

bandwidth-reference value

undo bandwidth-reference

Parameters

Parameter Description Value
value

Specifies the bandwidth reference value for interface cost calculation.

The value is an integer ranging from 1 to 2147483648, in Mbit/s.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The interface cost calculation formula is as follows: Interface cost = Bandwidth reference value/Interface bandwidth. The system only supports integer interface costs. If a calculated result is smaller than 1, such as 0.3, the system takes 1 as the result. If a calculated result is greater than 1 but not an integer, such as 2.3, the system takes the integer (2 in this example) as the result. If the bandwidth-reference command is executed to configure a new bandwidth reference value, the interface cost will be changed, and OSPF will re-select routes.

Configuration Impact

After the bandwidth-reference command is configured in a process, bandwidth reference values of all interfaces in the process are changed to the specified value.

Example

# Set the bandwidth reference value to 1000 Mbit/s.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] bandwidth-reference 1000

bfd all-interfaces (OSPF view)

Function

The bfd all-interfaces command sets the parameter values of a BFD session.

The undo bfd all-interfaces command restores the default parameter values of a BFD session.

By default, BFD is disabled.

Format

bfd all-interfaces { min-tx-interval transmit-interval | min-rx-interval receive-interval | detect-multiplier multiplier-value | frr-binding } *

undo bfd all-interfaces { min-tx-interval [ transmit-interval ] | min-rx-interval [ receive-interval ] | detect-multiplier [ multiplier-value ] | frr-binding } *

Parameters

Parameter Description Value
min-tx-interval transmit-interval

Specifies the minimum interval at which BFD packets are sent to the remote device.

The value is an integer that ranges from 3 to 1000, in milliseconds.
min-rx-interval receive-interval

Specifies the minimum interval for receiving BFD messages from the peer.

The value is an integer that ranges from 3 to 1000, in milliseconds.
detect-multiplier multiplier-value

Specifies the local detect multiplier.

The value is an integer ranging from 3 to 50. The default value is 3.
frr-binding

Associates the BFD session status with the link status on an interface. If BFD detects a link fault on an interface, the BFD session goes Down, triggering FRR. Traffic is then quickly switched to the backup link, minimizing service loss.

This parameter is supported only by S6730-H-V2, S5732-H-V2, S5735I-S-V2, and S5735-S-V2 series.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Any link failure or topology change causes routers to re-calculate routes, and the convergence of routing protocols affects network performance.

If BFD is associated with routing protocols, BFD can fast detect faults and notify routing protocols of the faults immediately, which speeds up the convergence of routing protocols.

OSPF IP FRR requires the lower layer to fast respond to the link change so that traffic can be rapidly switched to the backup link if a link fails. In such a case, if frr-binding is configured, the association between the BFD session status and link status is enabled on an interface. If the BFD session on the interface becomes Down, the link goes Down immediately.

Prerequisites

BFD has been enabled in the OSPF process using the bfd all-interfaces enable command.

Example

# Configure BFD in an OSPF process and set the minimum interval at which BFD packets are sent to 30 ms.
<HUAWEI> system-view
[HUAWEI] ospf
[HUAWEI-ospf-1] bfd all-interfaces enable
[HUAWEI-ospf-1] bfd all-interface min-tx-interval 30

bfd all-interfaces enable (OSPF view)

Function

The bfd all-interfaces enable command enables BFD in an OSPF process.

The undo bfd all-interfaces enable command disables BFD in an OSPF process.

The bfd all-interfaces incr-cost command enables an OSPF process to adjust the cost based on BFD.

The undo bfd all-interfaces incr-cost command disables an OSPF process from adjusting the cost based on BFD.

By default, BFD is disabled.

By default, an OSPF process does not adjust the cost based on BFD.

Format

bfd all-interfaces enable

bfd all-interfaces incr-cost { cost | max-reachable }

undo bfd all-interfaces enable

undo bfd all-interfaces incr-cost [ cost | max-reachable ]

Parameters

Parameter Description Value
incr-cost cost

Specifies a cost adjustment value.

The value is an integer that ranges from 1 to 65534 .
max-reachable

Adjusts the link cost to the maximum link cost 65535.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

BFD can fast detect a fault on a network, minimizing the impact of the fault on services.

You can enable BFD either on an interface or in an OSPF process. The configurations of BFD on an interface take precedence over those in an OSPF process. When BFD detects a fault and the system recovers quickly, the interface is disconnected due to BFD Down. As a result, the link is unstable and traffic is lost.

To ensure network reliability and solve the preceding problems, run the bfd all-interfaces incr-cost command to adjust the link cost. When the OSPF process detects that the BFD session goes Down, OSPF automatically increases the cost of the interface so that the link in the BFD Down state is not selected, traffic can be transmitted over other links.

When an interface detects that a BFD session goes Up, the cost of the interface is automatically restored to the original value. If link quality changes frequently, BFD status changes frequently too, causing link instability, which may in turn lead to traffic loss. To solve the preceding problem, you can configure the bfd all-interfaces incr-cost wtr command on an OSPF interface to set a delay after which the interface cost is restored. A BFD status change within the delay does not cause a path calculation change, ensuring network reliability.

Prerequisites

Before running the bfd all-interfaces incr-cost command, run the bfd all-interfaces enable command to enable BFD in the OSPF process.

Precautions

The interface-specific BFD-associated cost value has a higher priority than the process-specific BFD-associated cost value.

A BFD session can be created only when the bfd all-interfaces enable command is run on both ends to enable global BFD. In addition, BFD sessions can be created only between the two ends that have set up an OSPF neighbor relationship in the Full state.

The bfd all-interfaces command run in the OSPF view and the ospf bfd block command are mutually exclusive.

Example

# Configure an OSPF process to adjust the link cost to 5 based on BFD.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] bfd all-interfaces enable
[HUAWEI-ospf-100] bfd all-interfaces incr-cost 5

clear route loop-detect ospf alarm-state

Function

The clear route loop-detect ospf alarm-state command exits the routing loop alarm-state and clears loop detection alarms.

Format

clear route loop-detect ospf alarm-state

Parameters

None

Views

System view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

If the device detects an OSPF routing loop, it reports an alarm. Because the device cannot automatically detect whether the routing loop is eliminated, you need to run this command after the routing loop is eliminated to prevent the device from advertising a large link cost for imported routes and manually clear the OSPF routing loop alarm.

Example

# Exits the routing loop alarm-state and clear the loop-detect alarm.
<HUAWEI> system-view
[HUAWEI] clear route loop-detect ospf alarm-state

default (OSPF view)

Function

The default command configures default parameters for OSPF to import external routes. The parameters include the cost, type (Type 1 or Type 2), and tag.

The undo default command restores the default setting.

By default, the default cost of the external routes is 1; the type of the imported external routes is Type 2; the default tag value is 1.

Format

default { cost { costvalue | inherit-metric } | tag tagvalue | type typevalue } *

undo default { cost [ { costvalue | inherit-metric } ] | tag [ tagvalue ] | type [ typevalue ] } *

Parameters

Parameter Description Value
cost costvalue

Specifies the default cost of the external routes imported by OSPF.

The value is an integer ranging from 0 to 16777214. The default value is 1.
inherit-metric

Indicates that the cost of the imported route is the one carried in the route. If no cost is specified, the default cost set using the default command is used.

-
tag tagvalue

Specifies the tag of the external routes.

The value is an integer ranging from 0 to 4294967295. The default value is 1.
type typevalue

Specifies the type of the external routes.

The value is 1 or 2.

  • 1: Type 1 external route
  • 2: Type 2 external route

The default value is 2.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The imported external routes carry various parameters that can change the priorities and next hops of those routes in the OSPF routing table.

By setting default parameters for OSPF to import external routes, you can control OSPF route selection.

The route tag is used to identify protocol-related information. For example, it can be used to differentiate AS numbers when OSPF receives BGP routes. In addition, configuring tag can filter OSPF routes carrying tags.

Precautions

You can run the following commands to set the cost of the imported routes. The priorities of the imported routes are in descending order.

  • Run the apply cost command to set the route cost.
  • Run the import-route (OSPF view) command to set the cost of the imported route.
  • Run the default (OSPF view) command to set the default cost of imported routes.

    The priority of the default (OSPF view) command is the lowest. Therefore, when configuring this command, check whether other commands are configured. If other commands are configured, the function of this command does not take effect.

Example

# Set the default values of the cost, type, and tag.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] default cost 10 tag 100 type 2

default-cost

Function

The default-cost command sets the cost of the Type 3 default routes that OSPF sends to a Stub area.

The undo default-cost command restores the default setting.

By default, the cost of the Type 3 default routes that OSPF sends to a Stub area is 1.

Format

default-cost costvalue

undo default-cost

Parameters

Parameter Description Value
costvalue

Specifies the cost of the Type 3 default routes that OSPF sends to a Stub area.

The value ranges from 0 to 16777214.

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Configuring the cost of a default route can control OSPF route selection result, improving network flexibility.

This command is applicable only to the ABRs connected to a Stub area.

Prerequisites

A default route exists in the local routing table.

Example

# Set area 1 as a Stub area, and set the cost of the Type 3 default routes to be sent to this Stub area to 20.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 1
[HUAWEI-ospf-100-area-0.0.0.1] stub
[HUAWEI-ospf-100-area-0.0.0.1] default-cost 20

default-route-advertise (OSPF view)

Function

The default-route-advertise command advertises default routes to a common OSPF area.

The undo default-route-advertise command disables advertisement of default routes to a common OSPF area.

By default, default routes are not advertised to a common OSPF area.

Format

default-route-advertise [ [ always | permit-calculate-other ] | cost costvalue | type typevalue | { route-policy route-policy-name } | distribute-delay delaytimer | tag tagvalue ] *

default-route-advertise summary cost costvalue

default-route-advertise [ permit-calculate-other | cost costvalue | type typevalue | { route-policy route-policy-name } | distribute-delay delaytimer | permit-ibgp | tag tagvalue | permit-preference-less-than preference-val ] *

undo default-route-advertise

Parameters

Parameter Description Value
always

Generates and advertises an LSA that describes a default route, regardless of whether the local device has active default routes from processes other than the local OSPF process.

-
permit-calculate-other

Generates and advertises an ASE LSA that describes the default route only when there is an active default route of another OSPF process in the local routing table. The Router still calculates the default routes from other Routers.

If neither always nor permit-calculate-other is configured,

  • If the local device has active default routes from processes other than the local OSPF process, the device no longer calculates the default routes from other devices.
  • If the local device does not have active default routes from processes other than the local OSPF process, the device still calculates the default routes from other devices.

-
cost costvalue

Specifies the cost of external routes.

  • Cost of a Type 1 external route = Cost of the route from the Router to the related ASBR + Cost of the route from the ASBR to the destination.
  • Cost of a Type 2 external route = Cost of the route from the ASBR to the destination.

The value is an integer ranging from 0 to 16777214. The default value is 1.
type typevalue

Specifies the type of the external routes.

The value is 1 or 2.

  • 1: Type 1 external route
  • 2: Type 2 external route

The default value is 2.
route-policy route-policy-name

Specifies the name of a route-policy. When a device's routing table contains matching default routes that are generated from processes other than the local OSPF process, a device advertises the default routes based on the route-policy configuration.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
distribute-delay delaytimer

Specifies the delay timer for advertising the default route.

The value is an integer ranging from 1 to 65535.
tag tagvalue

Specifies the VPN route tag.

The value is an integer ranging from 0 to 4294967295. The default value is 1.
summary

Advertises the Type 3 summary LSA of the specified default route. Before specifying this parameter, ensure that VPN is enabled. Otherwise, routes cannot be advertised.

-
permit-ibgp

Imports IBGP routes.

-
permit-preference-less-than preference-val

Allows the device to import the default route whose preference value is smaller than the configured value.

The value is an integer ranging from 1 to 256.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The import-route (OSPF) command cannot be used to import the default route of an external route. To import the default route generated by other protocols, you must run the default-route-advertise command on the ASBR to advertise the default route to the entire common OSPF area.

If the ASBR has a default route, the ASBR advertises the default route 0.0.0.0 in the entire OSPF area after the default-route-advertise command is run.

If the ASBR does not have a default route, run the default-route-advertise command with always specified.

  • If always is configured, the ASBR advertises the default route 0.0.0.0 in the entire OSPF area regardless of whether the ASBR has a default route. The ASBR is configured to always display the default route in the routing table and does not calculate the default routes from other devices.
  • If always is not configured, the LSA that describes the default route is generated only when there are active default routes of non-OSPF processes (except BGP) in the routing table of the local device.

    When there are active BGP default routes in the routing table of the local device, the following situations occur:
  • If the ospf process-id vpn-instance vpn-instance-name command is not run, an active default EBGP route in the routing table can be imported to OSPF after the default-route-advertise command is run. In this case, the OSPF process cannot import IBGP routes. To import active default IBGP routes in the routing table to OSPF, run the default-route-advertise permit-ibgp command.
  • If the ospf process-id vpn-instance vpn-instance-name command is configured:
  • In addition, the vpn-instance-capability simple command is run. After the default-route-advertise command is run, the active default EBGP route in the routing table can be imported to OSPF. In this case, the OSPF process cannot import IBGP default routes. To import active default IBGP routes in the routing table to OSPF, run the default-route-advertise permit-ibgp command.
  • If the vpn-instance-capability simple command is not run and the default-route-advertise command is run, active BGP (including EBGP and IBGP) default routes in the routing table can be imported to OSPF.

    Importing IBGP routes may cause routing loops. Therefore, exercise caution when configuring IBGP route import.

    In a scenario where primary and backup paths exist, packet loss may occur when traffic is switched back from the backup path to the primary path. When there are a large number of routes, traffic loss is more serious. To solve this problem, run the default-route-advertise distribute-delay delaytimer command on the device on the primary path to delay sending the OSPF default route. This ensures that traffic is switched back after the device on the primary path completes updating forwarding entries.

Configuration Impact

After the default-route-advertise command is configured on the ASBR, the ASBR will generate a Type 5 ASE LSA with link state ID 0.0.0.0 and mask 0.0.0.0. In addition, it will advertise the ASE LSA in an entire OSPF area.

If a route-policy is configured, default routes are advertised based on the following principles:

  • If a default route matches the route-policy, a new default route is generated on an OSPF device based on the parameters configured in the route-policy. Parameters such as cost, tag, and type can be configured in the route-policy.
  • If the default route does not match the route-policy, and always is configured, the default route is still advertised.
  • If always is not configured, the OSPF device will not advertise the default route.
  • If always is configured, OSPF devices will advertise the default route. In addition, only always configured in the default-route-advertise command takes effect on advertisement of default routes.

Precautions

  • The OSPF default route advertisement mode depends on the type of the area where the default route is imported. This command is used only to advertise the default route to a common OSPF area. For stub areas, totally stub areas, and totally NSSAs, default routes are automatically advertised. In an NSSA, run the nssa default-route-advertise command to advertise default routes.
  • If the default-route-advertise command is run in an OSPF process and always is not specified, the default LSA is advertised based on the activated default route of another OSPF process in the IP routing table. The priority of the depended default route must be higher than that of the OSPF route, otherwise, OSPF may fail to advertise the default LSA or a loop may occur. To prevent loops, you are advised to specify permit-preference-less-than to prevent low-priority activated default routes from being imported. This parameter is used only when always is not specified.
  • Before advertising a default route in an OSPF routing domain, the compares the priorities of the default routes. If a static default route is configured on an OSPF device, to add the default route advertised by OSPF to the current routing table, ensure that the priority of the configured static default route is lower than that of the default route advertised by OSPF.

Example

# Advertise the ASE LSA of the default route to the OSPF area, with no default route on the local device.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] default-route-advertise always

description (OSPF area view)

Function

The description command configures a description for an OSPF area.

The undo description command deletes the description.

By default, no description is configured for an OSPF area.

Format

description description

undo description

Parameters

Parameter Description Value
description

Specifies the description of an OSPF area.

The value is a string of 1 to 80 characters.

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The description of an OSPF area helps identify special areas, facilitating network maintenance.

Example

# Configure a description for OSPF area 1.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 1
[HUAWEI-ospf-100-area-0.0.0.1] description this is a stub area

description (OSPF view)

Function

The description command configures a description for an OSPF process.

The undo description command deletes the configured description.

By default, no description is configured for an OSPF process.

Format

description description

undo description

Parameters

Parameter Description Value
description

Specifies a description for an OSPF process.

The description text is a string of 1 to 80 case-sensitive characters, spaces supported.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The description of an OSPF process helps identify special processes, facilitating network maintenance.

Configuration Impact

If you run the command multiple times, only the latest configuration takes effect.

Example

# Configure a description for the OSPF process.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] description this process contains 3 areas

display debugging ospf

Function

The display debugging ospf command displays information about current OSPF debugging functions.

Format

display debugging ospf

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

When a large amount of information is output, the display debugging ospf command can be used to view information about the enabled OSPF debugging functions. Based on the command output, you can disable some unnecessary debugging functions to minimize the debugging information output.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about current OSPF debugging functions.
<HUAWEI> display debugging ospf
OSPF 1 All Route Calculation debugging switch is on 
OSPF 1 RTCALC-NSSA debugging switch is on 
OSPF 1 RTCALC-INTER debugging switch is on 
OSPF 1 RTCALC-ASE debugging switch is on 
OSPF 1 RTCALC-INTRA debugging switch is on 
OSPF 1 RTCALC-ASBR debugging switch is on
Table 2-449 Description of the display debugging ospf command output
Item Description
OSPF 1 RTCALC-ASBR debugging switch is on

The OSPF 1 RTCALC-ASBR debugging function is enabled.
OSPF 1 All Route Calculation debugging switch is on

The OSPF 1 All Route Calculation debugging function is enabled.
OSPF 1 RTCALC-NSSA debugging switch is on

The OSPF 1 RTCALC-NSSA debugging function is enabled.
OSPF 1 RTCALC-INTER debugging switch is on

The OSPF 1 RTCALC-INTER debugging function is enabled.
OSPF 1 RTCALC-ASE debugging switch is on

The OSPF 1 RTCALC-ASE debugging function is enabled.
OSPF 1 RTCALC-INTRA debugging switch is on

The OSPF 1 RTCALC-INTRA debugging function is enabled.

display ospf abr-asbr

Function

The display ospf abr-asbr command displays information about the ABRs and ASBRs of OSPF.

Format

display ospf [ process-id ] abr-asbr [ router-id ]

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
router-id

Specifies the router ID of an ABR or ASBR.

Dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

An ABR can belong to two or more areas, and one of the areas must be a backbone area. An ABR is used to connect the backbone area and non-backbone areas. It can be physically or logically connected to the backbone area.

An ASBR exchanges routing information with other ASs. An ASBR may not reside at the boundary of an AS. It can be an internal router or an ABR. If an OSPF device imports external routes, the router is an ASBR.

To view information about the ABRs and ASBRs of OSPF, run the display ospf abr-asbr command.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about the ABRs and ASBRs of OSPF.
<HUAWEI> display ospf abr-asbr
OSPF Process 1 with Router ID 10.1.1.1
                  Routing Table to ABR and ASBR

 Type        Destination     Area            Cost       NextHop         RtType  
 INTRA-AREA  10.1.1.2        0.0.0.1         1          10.3.1.2        ABR/ASBR
Table 2-450 Description of the display ospf abr-asbr command output
Item Description
Type

Intra-area or inter-area router.
Destination

Router ID of the ABR or ASBR.
Area

Area ID.
Cost

Cost of the route from the local router to the ABR or ASBR.
NextHop

IP address of the next hop through which packets are transmitted to the ABR or ASBR.
RtType

ABR or ASBR.

display ospf asbr-summary

Function

The display ospf asbr-summary command displays information about OSPF route summarization.

Format

display ospf [ process-id ] asbr-summary [ ip-address mask ]

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
ip-address

Specifies the IP address.

If no IP address is specified, summarization information of all imported routes is displayed.

The value is in dotted decimal notation.
mask

Specifies the address mask for matching.

If an IP address is specified, a mask must be specified.

The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

Route summarization reduces the amount of routing information transmitted between areas and the routing table size and improves routing performance.

After route summarization is configured using the asbr-summary command, you can run the display ospf asbr-summary command to view the route summarization information, which facilitates troubleshooting.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about OSPF route summarization.
<HUAWEI> display ospf asbr-summary
OSPF Process 1 with Router ID 192.168.1.2
 Total summary address count: 1

 net         : 10.0.0.0
 mask        : 255.0.0.0
 tag         : 10
 status      : Advertise
 Cost        : 0 (Not Configured)
 Delay       : 30 (Configured)
 Number of routes : 2
 Destination     Net Mask        Proto      Process   Type     Metric

 10.1.0.0        255.255.0.0     Static     1         2        10
 10.2.0.0        255.255.0.0     Static     1         2        10
Table 2-451 Description of the display ospf asbr-summary command output
Item Description
Process

Process ID.
Total summary address count

Number of routes that are summarized using the asbr-summary command.
net

Network address of the summarized route.
tag

Tag of the summarized route.
status

Advertisement status of the summarized route:

  • Advertise: indicates that the summarized route is advertised.
  • DoNotAdvertise: indicates that the summarized route is not advertised.
Cost

Cost of the summarized route.
Delay

Delay for advertising a summary route.
Number of routes

Number of summarized routes.
Destination

Destination address of the routes that are summarized.
Net Mask

Mask of the routes that are summarized.
Mask

Network mask of the summarized route.
Proto

Protocol of the routes that are summarized.
Type

Type of the imported AS external route, Type 1 or Type 2.
Metric

Cost of the routes that are summarized.

display ospf bfd session

Function

The display ospf bfd session command displays information about a BFD-enabled neighbor.

Format

display ospf [ process-id ] bfd session { all | interfaceName | interfaceType interfaceNum | NbrRouterId }

display ospf [ process-id ] bfd session { interfaceName | interfaceType interfaceNum } NbrRouterId

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
all

Displays all the interfaces that are enabled with BFD in the OSPF process.

-
interfaceName

Specifies the name of an interface.

-
interfaceType

Specifies the type of an interface.

-
interfaceNum

Specifies the interface number.

-
NbrRouterId

Specifies the router ID of a neighbor.

Dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

In BFD for OSPF, a BFD session is associated with OSPF. The BFD session fast detects a link fault and then notifies OSPF of the fault, which enables OSPF to fast respond to the change of the network topology.

The display ospf bfd session command displays information about a BFD-enabled neighbor.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about BFD-enabled neighbors.
<HUAWEI> display ospf bfd session all
OSPF Process 1 with Router ID 3.3.3.3
  Area 0.0.0.0 interface 10.2.2.1 ( 10GE1/0/1 )'s BFD Sessions

 NeighborId:10.2.2.2          AreaId:0.0.0.0           Interface:10GE1/0/1          
 BFDState:up                  rx    :50                tx       :50               
 Multiplier:3                 BFD Local Dis:16385      LocalIpAdd:10.2.2.1        
 RemoteIpAdd:10.2.2.2         Diagnostic Info:No diagnostic information

   Total UP/DOWN/UNKNOWN BFD Session Number : 1 / 0 / 0
Table 2-452 Description of the display ospf bfd session command output
Item Description
Router ID

Local router ID.
BFD Local Dis

Local discriminator of the BFD session.
rx

Interval at which BFD packets are received.
tx

Interval at which BFD packets are sent.
Diagnostic Info

Diagnostic information.
Total UP/DOWN/UNKNOWN BFD Session Number

Total number of BFD sessions in the Up, Down, or Unknown state.
NeighborId

Router ID of the neighbor.
BFDState

BFD status:

  • up.
  • down.
  • unknown.
LocalIpAdd

Local IP address.
RemoteIpAdd

Remote IP address.
AreaId

Region ID.
Interface

Interface used to set up the BFD session.
Multiplier

Remote detection multiplier.

display ospf brief

Function

The display ospf brief command displays brief OSPF information.

Format

display ospf [ process-id ] brief

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no OSPF process ID is specified, brief information about all OSPF processes is displayed.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

In addition to brief OSPF information, running this command also displays the following information:

  • Router ID
  • VPN domain ID

    When locating OSPF faults, you can run the display ospf brief command to view brief OSPF information.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display OSPF brief information.
<HUAWEI> display ospf brief
OSPF Process 1 with Router ID 10.9.9.9
                  OSPF Protocol Information
RouterID: 10.9.9.9          Border Router: AREA 
Multi-VPN-Instance is not enabled 
Global DS-TE Mode is disabled 
Graceful-restart capability: disabled 
Helper support capability  : not configured 
OSPF Stub Router State Reason: Startup Synchronize
    Router LSA stub links with cost 65535
    Summary LSA with cost 16777214 
    External LSA with cost 16777214 
Spf-schedule-interval: max 10000ms, start 500ms, hold 1000ms 
Default ASE parameters: Metric: 1 Tag: 0 Type: 2 
Route Preference: 10 
ASE Route Preference: 150 
Intra Route Preference: 50 
Inter Route Preference: 50 
SPF Computation Count: 56 
RFC 1583 Compatible
OSPF is in LSDB overflow status(remain time: 205s)
Retransmission limitation is disabled
Import routes limitation is enabled
  Self ASE LSA count: 8
  Current status: Normal
bfd enabled
BFD Timers: Tx-Interval 10 , Rx-Interval 10 , Multiplier 3 
Area Count: 2   Nssa Area Count: 1 
ExChange/Loading Neighbors: 0

 Area: 0.0.0.0             (MPLS TE not enabled)
 Authtype: None   Area flag: Normal
 SPF scheduled count: 2
 Exchange/Loading neighbors: 0
 Router ID conflict state: Normal

 Interface: 10.1.1.1 (10GE1/0/1)
 Cost: 1       State: DR      Type: Broadcast      MTU: 1500
 Priority: 1
 Designated Router: 10.1.1.1
 Backup Designated Router: 0.0.0.0
 Timers: Hello 10, Dead 40, Wait 40, Poll 120, Retransmit 5, Transmit Delay 1

 Area: 0.0.0.1             (MPLS TE not enabled)
 Authtype: None   Area flag: NSSA
 SPF scheduled count: 1
 Exchange/Loading neighbors: 0
 NSSA Translator State: Elected
 Router ID conflict state: Normal
 Import routes limitation is enabled
  Self NSSA LSA count: 2
  Current status: Normal

 Interface: 10.1.1.1 (10GE1/0/1)
 Cost: 1       State: P-2-P   Type: P2P      MTU: 1500
 Timers: Hello 10, Dead 40, Wait 40, Poll 120, Retransmit 5, Transmit Delay 1

<HUAWEI> display ospf brief
OSPF Process 1 with Router ID 1.1.1.1
RouterID: 1.1.1.1          Border Router:
 Multiple VPN instance is not enabled
 Global DS-TE Mode is disabled
 Graceful-restart capability is disabled
 Helper support capability is not configured
 SPF schedule interval        : Max 5000ms, Start 50ms, Hold 200ms
 Default ASE parameters       : Metric: 1 Tag: 1 Type: 2
 Route preference             : 10
 ASE route preference         : 150
 Intra route preference       : 10
 Inter route preference       : 10
 SPF computation count        : 2
 RFC 1583 compatible
 Retransmission limitation is disabled
 Import routes limitation is disabled
 Area count                   : 1
 Nssa area count              : 0
 Exchange/Loading neighbors   : 0

 Area: 0.0.0.1          MPLS TE not enabled

 Authtype: None   Area flag: Normal
 SPF scheduled count: 2
 Exchange/Loading neighbors: 0
 Router ID conflict state: Normal

 Interface: 192.1.1.1 (Vlanif100)
 Cost: 1       State: BDR         Type: Broadcast            MTU: 1500
 Priority: 1
 Designated Router: 192.168.1.2
 Backup Designated Router: 192.168.1.1
 Timers: Hello 10, Dead 40, Wait 40, Poll 120, Retransmit 5, Transmit Delay 1
Table 2-453 Description of the display ospf brief command output
Item Description
OSPF Stub Router State Reason

Reason why the Stub Router state is displayed. This state is displayed only when a stub router is restarting.
OSPF is in LSDB overflow status(remain time: 205s)

The maximum number of external routes in the OSPF LSDB is in the overload state (the remaining time of the overload timer is 205s).

When the number of external routes in the OSPF LSDB reaches or exceeds 90% of the maximum number, the following information is displayed:

OSPF LSDB is approaching overflow limit .

To configure the maximum number of external routes supported by the OSPF LSDB, run the lsdb-overflow-limit number command.
Router LSA stub links with cost 65535

The maximum cost 65535 is set for stub links in router LSAs. The function is enabled using the stub-router command.
Router ID conflict state

Router ID conflict state.
Border Router

Border router:

  • AS: autonomous system border router (ASBR).
  • AREA: area border router (ABR).
  • NSSA: ABR of a Not-So-Stubby Area (NSSA).
Multi-VPN-Instance

Whether VPN multi-instance is enabled.
Global DS-TE Mode

Global DS-TE Mode is disabled.
Graceful-restart capability

Whether graceful restart is enabled:

  • disabled: Graceful restart is disabled. You can run the graceful-restart command to enable graceful restart.
  • planned only: The planned-GR mode is supported.
  • un-planned: The unplanned GR mode is supported.
  • totally: The totally GR mode is supported.
  • planned and un-planned: Planned-GR and unplanned-GR are supported.
Helper support capability

Whether the Helper mode is enabled:

  • enabled: The Helper mode is enabled.
  • disabled: The Helper mode is disabled. You can run the graceful-restart command to enable it.
State

Interface status, which can be Down, Waiting, Loopback, P-2-P, DR, BDR, or DR OTHER. DR, BDR, and DR OTHER exist only on broadcast and NBMA networks, and P-2-P exists only on P2P and P2MP networks.
Summary LSA with cost 16777214

Summary-LSAs with cost 16777214 are advertised. The function is enabled using the stub-router command.
External LSA with cost 16777214

The device is configured to advertise external LSAs with cost 16777214 using the stub-router command.
Default ASE parameters

Default parameter values of the external link status advertisement (LSA), including:

  • Metric: indicates the metric value.
  • Tag: route tag.
  • Type: indicates the route type.
ASE Route Preference

Priority of the external route.
Route Preference

Default route priority.
Intra Route Preference

Priority of the intra-area route.
Inter Route Preference

Priority of the inter-area route.
SPF Computation Count

Number of SFP calculation times.
SPF scheduled count

Number of times that SPF calculation is performed.
SPF schedule interval

SPF timer.
RFC 1583 Compatible

RFC 1583 compatibility is enabled. If RFC 1583 compatibility is not enabled, you can run the rfc1583 compatible command to configure the rules defined in RFC 2328 to be compatible with those defined in RFC 1583.
Retransmission limitation

Whether a retransmission limit is configured.
Import routes limitation

Whether a limit is configured on the number of LSAs generated when an OSPF process imports external routes.
Self ASE LSA count

Number of ASE LSAs.

This field is displayed only in a process.
Self NSSA LSA count

Number of NSSA LSAs.

This field is displayed only in an NSSA.
Current status

A limit has been configured on the number of LSAs generated when an OSPF process imports external routes. The current status can be:

  • Normal: The lower alarm threshold is not exceeded.
  • Approach limit: The alarm threshold is about to be reached, and the number of LSAs has reached 90% of the upper alarm threshold.
  • Exceed limit: The number has reached or exceeded the maximum.
bfd enabled

Enable BFD.
BFD Timers

BFD session parameters.
Area Count

Number of areas in the process.
Area

Area ID.
Area flag

Area attribute. The options are as follows:

  • Normal: common area.
  • Vlink: transmission area of the virtual link.
  • Stub: stub area.
  • Nssa: NSSA area.
Nssa Area Count

Number of Not-So-Stubby Areas (NSSAs) in the current process.
Exchange/Loading neighbors

Number of neighbors in ExChange or Loading state.
Designated Router

Interface of the designated router (DR).
Backup Designated Router

Interface of the BDR.
NSSA Translator State

NSSA translator role.
MPLS TE

Whether MPLS TE is enabled.
RouterID

Router ID of the current device.
Authtype

Area authentication type.
Interface

Interface information in the area.
Cost

Cost of an OSPF interface.
Type

Type of an interface. The options are as follows:

  • PTP: indicates that the interface type is P2P.
  • Broadcast: indicates that the interface is a broadcast interface.
  • NBMA: The interface type is NBMA.
  • PTMP: indicates that the interface is a P2MP interface.
MTU

Maximum transmission unit (MTU) of an interface.
Priority

Interface priority.
Timers

Timer intervals:

  • Hello: interval at which an interface sends Hello packets, which can be set using the ospf timer hello command.
  • Dead: OSPF neighbor dead interval, which can be set using the ospf timer dead command.
  • Wait: OSPF wait interval, which can be set using the ospf timer wait command.
  • Poll: interval at which poll Hello packets are sent on NBMA networks, which can be set using the ospf timer poll command.
  • Retransmit: interval at which an interface retransmits LSAs, which can be set using the ospf timer retransmit command.
  • Transmit Delay: LSA transmission delay, which can be set using the ospf trans-delay command.
Spf-schedule-interval

Interval for performing the shortest path first (SPF) calculation.

display ospf cumulative

Function

The display ospf cumulative command displays OSPF statistics.

Format

display ospf [ process-id ] cumulative

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no OSPF process ID is specified, statistics of all the OSPF processes are displayed.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view OSPF statistics, run the display ospf cumulative command. The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display OSPF statistics.
<HUAWEI> display ospf cumulative

          OSPF Process 1 with Router ID 1.1.1.1
                  Cumulations

  IO Statistics
               Type        Input     Output
              Hello        17591      17701
     DB Description            9         12
     Link-State Req            4          4
  Link-State Update          209        109
     Link-State Ack          100        202

  ASE: (Disabled)
  LSAs originated by this router
  Router: 1
  Network: 2
  Sum-Net: 0
  Sum-Asbr: 0
  External: 0
  NSSA: 0
  Opq-Link: 0
  Opq-Area: 0
  Opq-As: 0
  LSAs Originated: 3  LSAs Received: 206

  Routing Table:
    Intra Area: 1  Inter Area: 0  ASE: 0

  Up Interface Cumulate: 1
      Interface Cumulate:
  =======================================================

     Interface cumulative data. (Process 1)
  -------------------------------------------------------
  Down:        0 Loopback:     0 Waiting:     0 P-2-P:    0
  DR:          0 BDR:          1 DROTHER:     0

      Neighbor Cumulate:
  =======================================================

     Neighbor cumulative data. (Process 1)
  -------------------------------------------------------
  Down:        0 Init:         0 Attempt:     0 2-Way:    0
  Exstart:     0 Exchange:     0 Loading:     0 Full:     1
  Retransmit Count: 0

      Interface cumulative data. (Total)
  -------------------------------------------------------
  Down:     0 Loopback:     0 Waiting:     0 P-2-P:    0
  DR:       0 BDR:          1 DROTHER:     0


      Neighbor cumulative data. (Total)
  -------------------------------------------------------
  Down:        0 Init:         0 Attempt:     0 2-Way:    0
  Exstart:     0 Exchange:     0 Loading:     0 Full:     1
  Retransmit Count: 0
Table 2-454 Description of the display ospf cumulative command output
Item Description
Router

Router LSA.
IO Statistics

Statistics of the transmitted packets and LSAs.
Type

OSPF packet type.
Input

Number of packets received.
Output

Number of sent packets.
Hello

OSPF Hello packet.
DB Description

OSPF Database Description packet.
Link-State Ack

OSPF Link State Acknowledgement packet.
Link-State Req

OSPF Link State Request packet.
Link-State Update

OSPF Link State Update packet.
LSAs originated by this router

Detailed statistics of the transmitted LSAs.
LSAs Originated

Generated LSAs.
LSAs Received

Received LSAs.
Routing Table

Routing table.
Intra Area

Number of intra-area routes.
Inter Area

Number of inter-area routes.
Up Interface Cumulate

Statistics of interfaces that are Up.
Interface cumulative data

Detailed statistics of interfaces:

  • Down.
  • Loopback.
  • Waiting.
  • P-2-P.
  • DR.
  • BDR.
  • DROTHER.
Interface Cumulate

Interface status statistics.
Neighbor Cumulate

Statistics of neighbors.
Neighbor cumulative data

Detailed statistics of neighbors:

  • Down.
  • Init.
  • Attempt.
  • 2-Way.
  • Exstart.
  • Exchange.
  • Loading.
  • Full.
Retransmit Count

Total number of nodes in the retransmission list.
ASE

Number of ASE routes (when there are no ASE routes, Disabled is displayed).
Network

Network LSA.
Sum-Net

Type-3 summary LSA.
Sum-Asbr

Type 4 summary LSA.
External

AS external LSA.
NSSA

NSSA.
Opq-Link

Number of Type 9 Opque LSAs.
Opq-Area

Number of Type 10 Opque LSAs.
Opq-As

Number of Type 11 Opque LSAs.

display ospf ecmp-group

Function

The display ospf ecmp-group command displays information about OSPF ECMP groups.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

display ospf [ process-id ] ecmp-group

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

When OSPF load balancing is implemented, the display ospf ecmp-group command can be used to check whether indirect next hop IDs are correctly assigned. This helps to implement a rapid route switchover.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about OSPF ECMP groups.
<HUAWEI> display ospf ecmp-group
OSPF Process 1 with Router ID 10.1.1.1
                 OSPF ECMP Group Information
----------------------------------------------------------------
 ECMPGroupId MtId Flag  RefCnt    NextHop
----------------------------------------------------------------
   0x1000048    0 D          1    10.1.1.1
----------------------------------------------------------------
               Flags: D-Direct, URT
Used ECMP Group Number: 1

Total Used ECMP Group Number: 1
Unused ECMP Group Number: 39
Unused ECMP Group List:
0x1000049, 0x100004a, 0x100004b, 0x100004c, 0x100004d, 0x100004e, 0x100004f, 0x1000050, 0x1000051, 0x1000052, 0x1000053, 0x1000054, 0x1000055, 0x1000056, 0x1000057, 0x1000058, 0x1000059, 0x100005a, 0x100005b, 0x100005c, 0x100005d, 0x100005e, 0x100005f, 0x1000060, 0x1000061, 0x1000062, 0x1000063, 0x1000064, 0x1000065, 0x1000067, 0x1000068, 0x1000069, 0x100006a, 0x100006b, 0x100006c, 0x100006d, 0x100006e, 0x100006f, 0x1000070, 0x1000071, 0x1000072, 0x1000073, 0x1000074, 0x1000075, 0x1000076, 0x1000077, 0x1000078, 0x1000079, 0x100007a, 0x100007b, 0x100007c, 0x100007d, 0x100007e, 0x100007f, 0x1000080, 0x1000081, 0x1000082, 0x1000083, 0x1000084
Table 2-455 Description of the display ospf ecmp-group command output
Item Description
OSPF ECMP Group Information

Information about an OSPF ECMP group.
ECMPGroupId

ID of an ECMP group.
MtId

Topology ID.
RefCnt

Number of times that an ECMP group is referenced.
NextHop

Routing information on the next hop.
Used ECMP Group Number

Number of used ECMP groups in a process.
Total Used ECMP Group Number

Total number of used ECMP groups.
Unused ECMP Group Number

Number of remaining ECMP groups.
Unused ECMP Group List

List of remaining ECMP groups.
Flags

Flag of an ECMP group:

  • D: Direct route.
  • URT: Unicast route.

display ospf error

Function

The display ospf error command displays OSPF error information.

Format

display ospf process-id error

display ospf [ process-id ] error lsa

display ospf error

display ospf process-id error interface { interface-name | interface-type interface-number }

display ospf error interface { interface-name | interface-type interface-number }

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no OSPF process ID is specified, error information about all OSPF processes is displayed.

The value is an integer ranging from 1 to 4294967295.
lsa

Display the OSPF LSA errors.

-
interface interface-name

Specifies the name of an interface.

-
interface-type

Specifies the type of an interface.

-
interface-number

Specifies an interface number.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

When locating OSPF faults, you can run the display ospf error command to obtain OSPF error information. You can then analyze OSPF faults according to the OSPF error information.

If error statistics keep increasing rapidly, locate the fault based on the error type.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display OSPF error information.
<HUAWEI> display ospf error
OSPF Process 1 with Router ID 10.1.1.1
                  OSPF error statistics

General packet errors:
 0           : IP: received my own packet     113         : Bad packet
 0           : Bad version                    0           : Bad checksum
 0           : Bad area id                    0           : Drop on unnumbered interface
 0           : Bad virtual link               0           : Bad authentication type
 0           : Bad authentication key         0           : Packet too small
 1           : Packet size > ip length        0           : Transmit error
 7           : Interface down                 1           : Unknown neighbor
 0           : Bad authentication sequence number 
 15          : TTL error                      0           : Packet too long
 3           : Bad network segment            2           : Bad RouterId
 1           : Bad destination address        0           : Packet received from silent interface

HELLO packet errors:
 1           : Netmask mismatch               50          : Hello timer mismatch
 0           : Dead timer mismatch            0           : Extern option mismatch
 0           : Router id confusion            0           : Virtual neighbor unknown
 0           : NBMA neighbor unknown          0           : Invalid Source Address
 1           : Invalid DR                     0           : LSDB overflow
 147         : DR/BDR mismatch                0           : Neighbor reach limit
 0           : Hold down state                0           : memory overload
 0           : CPU overload

DD packet errors:
 534         : Neighbor state low             0           : Router id confusion
 0           : Extern option mismatch         0           : Unknown LSA type
 0           : MTU option mismatch            0           : CPU overload
 0           : Exchange neighbor limit

LS ACK packet errors:
 1           : Neighbor state low             0           : Unknown LSA type

LS REQ packet errors:
 0           : Neighbor state low             0           : Empty request
 0           : Bad request

LS UPD packet errors:
 0           : Neighbor state low             17          : Newer self-generate LSA
 0           : LSA checksum bad               12          : Received less recent LSA
 2           : Unknown LSA type               0           : Ignore receive LSA
 7           : Received LSA within LSA Arrival interval

Opaque errors:  
 0           : 9-out of flooding scope        32          : 10-out of flooding scope
 13          : 11-out of flooding scope       0           : Unknown TLV type
 12          : RI LSA TLV ERROR               25          : RI LSA Sub TLV ERROR
 19          : ExtendPrefix LSA TLV ERROR     0           : ExtendPrefix LSA Sub TLV ERROR
 8           : ExtendLink LSA TLV ERROR       0           : ExtendLink LSA Sub TLV ERROR
 0           : EIA-ASBR LSA TLV ERROR         0           : EIA-ASBR TLV ERROR
 0           : EIA-ASBR Sub TLV ERROR

SR TLV errors:
 1           : Bad SR-Algorithm TLV           3           : Bad SID/Label Range TLV
 2           : Bad SID/Label Sub TLV          1           : Bad Extended Prefix  TLV
 1           : Bad Prefix-SID Sub TLV         1           : Bad Extended Prefix Range TLV
 3           : Bad LAN Adj-SID Sub TLV        2           : Bad Adj-SID Sub TLV 
 1           : Bad Extended Link TLV          0           : Bad Flex-Algo Definition TLV
 0           : Bad Exclude AG Sub TLV         0           : Bad Include-Any AG Sub TLV
 0           : Bad Include-All AG Sub TLV     0           : Bad FAD Flags Sub TLV
 0           : Bad ASLA Sub TLV               0           : Bad TE Metric Sub TLV
 0           : Bad Link Delay Sub TLV         0           : Bad Extended AG Sub TLV
 0           : Bad AG Sub TLV                 0           : Bad FAPM Sub TLV
 0           : Bad FAAM Sub TLV

Retransmission for packet over Limitation errors:
 0           : Number for DD Packet           0           : Number for Update Packet
 0           : Number for Request Packet

Receive Grace LSA errors:
 0           : Number of invalid LSAs         0           : Number of policy failed LSAs
 0           : Number of wrong period LSAs

Configuration errors:
 0           : Tunnel cost mistake
 1           : The network type of the neighboring interface is not consistent
# Display OSPFv3 LSA errors.
<HUAWEI> display ospf error lsa
OSPF Process  1  with Router ID 10.1.1.14

 Last Received Bad LSA Header
    LS Age             : 36
    Link State Type    : 0x0008
    Link State ID      : 10.0.1.66
    Advertising Router : 10.2.2.22
    LS Sequence Number : 0x80000002
    LS Checksum        : 0x00bd2e
    Length             : 96
    Interface          : 10GE1/0/1
    Recv Time          : 2011-05-27 14:37:17

<HUAWEI> display ospf error lsa
OSPF Process  1  with Router ID 10.1.1.14

 Last Received Bad LSA Header
    LS Age             : 36
    Link State Type    : 0x0008
    Link State ID      : 10.0.1.66
    Advertising Router : 10.2.2.22
    LS Sequence Number : 0x80000002
    LS Checksum        : 0x00bd2e
    Length             : 96
    Interface          : 100GE1/0/1
    Recv Time          : 2011-05-27 14:37:17
Table 2-456 Description of the display ospf error command output
Item Description
Router id confusion

The router IDs on the two ends are the same.
General packet errors

General packet errors.
IP: received my own packet

The interface receives the packet sent by itself.
Bad packet

The parsed packet is incorrect, including the checksum of the length field.
Bad version

The OSPF version is incorrect (not version 2).
Bad checksum

The OSPF checksum is incorrect.
Bad area id

The area ID in the received packet does not match the local area ID. (Vlink can receive packets from area 0. Area ID inconsistency in other cases is considered an error.).
Bad virtual link

V-link receives illegal packets.
Bad authentication type

Packet authentication is incorrect.
Bad authentication key

Packet authentication key is incorrect.
Bad authentication sequence number

Indicates bad authentication sequence number errors.
Bad request

Error request.
Bad network segment

The source address in the Hello packet does not match the network segment of the local interface address.
Bad RouterId

The router ID in the non-Hello packet is different from the router ID of the neighbor.
Bad destination address

A non-DR/BDR interface receives a packet with the destination address 224.0.0.6, or the destination address is not the local interface address or the multicast address 224.0.0.5 or 224.0.0.6, the vlink/sham link/NBMA interface and the v3 P2MP non-broadcast interface receive multicast packets with destination addresses 224.0.0.5 and 224.0.0.6.
Bad SR-Algorithm TLV

The length of the algorithm TLV of the RI LSA is incorrect.
Bad SID/Label Range TLV

The range TLV length of the device LSA is incorrect.
Bad SID/Label Sub TLV

The length of the SID sub TLV of the RI LSA is incorrect.
Bad Extended Prefix TLV

The length of the extend prefix TLV in the extend prefix LSA is incorrect.
Bad Prefix-SID Sub TLV

The length of the prefix SID sub-TLV in the extend prefix LSA is incorrect.
Bad Extended Prefix Range TLV

The length of the range TLV in the extended prefix LSA is incorrect.
Bad LAN Adj-SID Sub TLV

The length of the lan adj sid sub TLV in the extended link LSA is incorrect.
Bad Adj-SID Sub TLV

Failed to check the length of adj sid sub tlv in the extended link LSA.
Bad Extended Link TLV

An error occurred when checking the TLV length of the extended link in the extended link LSA.
Bad Flex-Algo Definition TLV

The Flex-Algo definition TLV is incorrect.
Bad Exclude AG Sub TLV

The Exclude extended admin group sub-TLV is incorrect.
Bad Include-Any AG Sub TLV

The Include-Any extended admin group sub-TLV is incorrect.
Bad Include-All AG Sub TLV

The Include-All extended management group sub-TLV is incorrect.
Bad FAD Flags Sub TLV

The FAD flag sub-TLV is incorrect.
Bad ASLA Sub TLV

The sub-TLV of the specific application link attribute is incorrect.
Bad TE Metric Sub TLV

The TE Metric sub-TLV is incorrect.
Bad Link Delay Sub TLV

The link delay sub-TLV is incorrect.
Bad Extended AG Sub TLV

The extended admin group sub-TLV is incorrect.
Bad AG Sub TLV

Administrative group sub-TLV error.
Bad FAPM Sub TLV

FAPM sub-TLV error.
Bad FAAM Sub TLV

FAAM sub-TLV error.
Drop on unnumbered interface

The unnumbered interface receives packets (the interface must be of the P2P type).
Packet too small

The length of the received packet does not equal the sum of the IP header length and the packet length.
Packet size > ip length

The length of the OSPF packet is greater than the permitted length of the IP packet.
Packet too long

The packet length exceeds 65535 bytes.
Packet received from silent interface

Packets are received from the silent interface.
Transmit error

Transmitting packets to socket fails.
Interface down

Number of times that the OSPF interface goes Down.
Interface

Interface that receives the LSA.
Unknown neighbor

OSPF packets are received from non-OSPF neighbors on NBMA networks, virtual links, and sham links.
Unknown LSA type

The router receives unknown LSAs.
TTL error

The TTL value in the packet is 0.
HELLO packet errors

Hello packet errors.
Netmask mismatch

The address mask does not match the local address mask.
Hello timer mismatch

The Hello intervals on the two ends are inconsistent.
Dead timer mismatch

The Dead intervals on the two ends are inconsistent.
Extern option mismatch

The extension attributes of the Hello packet are not consistent.
Virtual neighbor unknown

The router ID of the packet is inconsistent with that of the neighbor that is configured for the virtual link.
NBMA neighbor unknown

The status of the NBMA neighbor is not active.
Invalid DR

Statistics about Hello packets with non-zero DR priorities received by a P2P interface.
LSDB overflow

Number of received Hello packets when the OSPF LSDB is overloaded.
Neighbor state low

Following situations:

  • A DD packet is received, but its neighbor status is lower than 2-way.
  • An LSR packet is received, but its neighbor status is lower than Exchange.
  • An LSU packet is received, but its neighbor status is lower than Exchange.
  • An LSAck packet is received, but its neighbor status is lower than Exchange.
Neighbor reach limit

The number of neighbors exceeds the upper limit.
Hold down state

The neighbor is in the holddown state.
memory overload

The received packets are ignored due to memory overload.
CPU overload

The received packets are ignored because the CPU is overloaded.
DD packet errors

Database description (DD) packet errors.
LSA checksum bad

LSA checksum error.
MTU option mismatch

The MTU check of the OSPF interface is enabled, and the MTU of the DD packet received by the interface is greater than the MTU of the interface.
Exchange neighbor limit

The number of neighbors in the Exchange state exceeds the upper limit, and the establishment of neighbors is controlled.
LS ACK packet errors

LS Ack packet errors.
LS REQ packet errors

LSR packet errors.
LS UPD packet errors

LSU packet errors.
LS Age

Aging time of the LSA.
LS Sequence Number

Sequence number in the LSA header.
LS Checksum

LSA checksum.
Empty request

Empty LSR packets.
Newer self-generate LSA

Number of new self-generated LSAs. This field is reserved for future use.
Received less recent LSA

The LSA older than the local LSA is received.
Received LSA within LSA Arrival interval

An LSA is received within the LSA arrival interval.
Ignore receive LSA

The sum of received LSA ignored.
Opaque errors

Opaque errors.
9-out of flooding scope

Number of Type 9 LSAs that exceed the flooding scope.
10-out of flooding scope

Number of Type 10 LSAs that exceed the flooding scope.
11-out of flooding scope

Number of Type 11 LSAs that exceed the flooding scope.
RI LSA TLV ERROR

The length of the main TLV in the RI LSA is incorrect.
RI LSA Sub TLV ERROR

The length of the sub TLV in the RI LSA is incorrect.
ExtendPrefix LSA TLV ERROR

The length of the main TLV in the extend prefix LSA is incorrect.
ExtendPrefix LSA Sub TLV ERROR

The length of the sub TLV in the Extend prefix LSA is incorrect.
ExtendLink LSA TLV ERROR

An error occurred when checking the length of the main TLV of the extended link LSA.
ExtendLink LSA Sub TLV ERROR

The length of the sub TLV of the extended link LSA is incorrect.
EIA-ASBR LSA TLV

EIA-ASBR LSA error.
EIA-ASBR TLV ERROR

EIA-ASBR TLV error.
EIA-ASBR Sub TLV ERROR

EIA-ASBR sub-TLV error.
SR TLV errors

segment-routing TLV error.
Link State Type

LSA type.
Link State ID

LSA state ID.
Retransmission for packet over Limitation errors

Indicates the number of times that the number of retransmitted packets exceeds the threshold.
Number for DD Packet

Number of times that retransmitting DD packets expires.
Number for Update Packet

Number of times that retransmitting LSU packets expires.
Number for Request Packet

Number of times that retransmitting count of Request packets excceds the limit.
Number of invalid LSAs

Total number of invalid LSAs.
Number of policy failed LSAs

Total number of LSAs rejected by a policy.
Number of wrong period LSAs

Total number of wrong period LSAs.
Receive Grace LSA errors

Number of received incorrect Grace LSAs.
Configuration errors

Configuration errors.
Tunnel cost mistake

Number of times that the cost of the OSPF tunnel interface is smaller than 1. This count increases by one each time the cost of the OSPF tunnel interface is smaller than one. If the cost is smaller than one, the cost is calculated as one.
The network type of the neighboring interface is not consistent

Network types of the neighboring interfaces are different.
Last Received Bad LSA Header

Last received LSA.
Advertising Router

Advertising router.
Length

Length of the LSA.
Recv Time

LSA receiving time.

display ospf graceful-restart

Function

The display ospf graceful-restart command displays the status of OSPF GR.

Format

display ospf [ process-id ] graceful-restart [ verbose ]

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
verbose

Displays detailed information about OSPF GR.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view details of the GR and the statistics, run the display ospf graceful-restart command.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display detailed information about OSPF GR.
<HUAWEI> display ospf graceful-restart verbose
OSPF Process 1 with Router ID 10.1.1.1               

 Helper-policy support                : planned, strict lsa check
 Current GR state                     : normal

 Number of restarting neighbors : 0

 Last exit reason:
  On Helper     : none
  All area count      : 1
              Area ID    : 0.0.0.1
 Authtype       :  None     Area flag : Normal
 Normal interface count: 1
 Interface: 10.6.6.2 (Vlanif100)
 GR state : Normal                  State: BDR          Type: Broadcast
 Neighbor count of this interface : 1
 Neighbor          IP address         GR state     Helper period   Grace Period Left   Last Helper Exit reason
 10.1.1.1           10.6.6.1            Normal       0               0                   none
# Display the status of OSPF GR in non-IETF mode.
<HUAWEI> display ospf graceful-restart
OSPF Process 1 with Router ID 10.1.1.1               

 Helper-mode                          : non-ietf
 Helper-policy support                : --
 Current GR state                     : normal

 Number of restarting neighbors : 0

 Last exit reason:
  On Helper     : none
# Display the status of OSPF GR in IETF mode.
<HUAWEI> display ospf graceful-restart
OSPF Process 1 with Router ID 10.1.1.1               

 Helper-policy support                : planned and un-planned, strict lsa check
 Current GR state                     : normal

 Number of restarting neighbors : 0

 Last exit reason:
  On Helper     : none
Table 2-457 Description of the display ospf graceful-restart command output
Item Description
Helper-policy support

Policy that supports the Helper:

  • planned: indicates that the Helper supports only planned GR.
  • un-planned: indicates the Helper supports unplanned GR.
  • strict lsa check: indicates that the Helper supports strict external LSA check.
  • ignore external lsa check: indicates that the Helper does not check external LSAs.
  • never: indicates that the device does not support the Helper mode.
Current GR state

Current GR status:

  • Normal: indicates that GR is in the Normal state.
  • Helper: indicates that the device enters the Helper mode.
GR state

GR status of an interface:

  • Normal.
  • Helper.
Number of restarting neighbors

Number of restarted routers displayed on the Helper.
Last exit reason

Reason why the device exits from GR.

  • none: indicates that GR is not implemented.
  • successful exit: indicates that the OSPF process exits after GR is implemented successfully.
  • grace period expire recv flush grace lsa: indicates that the GR restarter deletes the flushed grace LSA.
  • recv change lsa: indicates that the local interface receives the changed LSA.
  • recv two grace lsa: indicates that the local interface receives two grace LSAs.
  • recv one way hello: indicates that the local interface receives a 1-way Hello packet from the peer interface. That is, the neighbor goes Down.
  • policy check fail: indicates that the Helper policy check fails.
  • nbr reset: indicates that NBR restarts.
  • if change: indicates that the status of an interface changes. For example, the interface changes from Up to Down or the configuration of the interface changes.
  • proc change: indicates that the configuration of the Helper in this OSPF instance changes.
Last Helper Exit reason

Cause for exiting the helper mode of the neighbor for the last time:

  • none: indicates that GR does not occur.
  • successful exit: indicates that GR is correctly performed and ended.
  • grace period expired: indicates that the GR period expires.
  • received flushed grace LSA: indicates that flushed grace LSAs are received.
  • flooding changed LSA: indicates that changed LSAs are received.
  • received multiple grace LSA: indicates that multiple grace LSAs are received.
  • received 1-way hello packet: indicates that 1-way Hello packets are received.
  • policy check failed for received grace LSA: indicates that the Helper policy is not matched.
  • neighbor reset: indicates that topology changes after the reset command is run on the neighbor of the helper.
  • interface state changed: indicates that the interface status is changed.
  • graceful restart unconfigured at process level: indicates that GR is not configured for the neighbor.
On Helper

Reason why the Helper exits from GR.
Helper period

Period of the GR helper.
All area count

Number of areas in the process.
Area ID

Area ID.
Area flag

Area flag:

  • Normal.
  • NSSA.
  • Stub.
Authtype

Authentication type.
Normal interface count

Number of interfaces in the area.
Neighbor count of this interface

Number of neighbors on the interface.
Neighbor

Neighbor ID.
IP address

IP address of a neighboring interface.
Grace Period Left

Remaining time of the GR Helper.
Helper-mode

Helper mode.
Interface

IP address of the interface.
State

Interface status:

  • Point to Point.
  • DR.
  • BDR.
  • DROther.
  • Waiting.
  • Down.
Type

Interface type:

  • P2P.
  • P2MP.
  • NBMA.
  • Broadcast.

display ospf hostname-table

Function

The display ospf hostname-table command displays information about OSPF dynamic hostnames.

Format

display ospf [ process-id ] hostname-table

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To facilitate network management, configure dynamic hostnames to identify routers. After you run the hostname command to configure a dynamic hostname for a device, the device generates a router information (RI) Opaque LSA.

After a device receives a RI Opaque LSA, you can run the display ospf hostname-table command on the router to check the mapping between the router ID and the dynamic hostname.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about OSPF dynamic hostnames.
<HUAWEI> display ospf hostname-table
OSPF Process 1 with Router ID 10.3.3.3
                Hostname table information

                Area: 0.0.0.1

 Router ID            Hostname
 10.3.3.3             RTR_BLR
 10.1.1.1             RTR_SHANGHAI
 255.255.255.254      RTR_BJI

                Area: 0.0.0.2

 Router ID            Hostname
 10.3.3.3             RTR_BLR
 10.30.1.1            RTR_DELHI

                AS-Scope

 Router ID            Hostname
 10.20.1.1            RTR_SHENZHEN
 255.255.255.254      RTR_BJI
Table 2-458 Description of the display ospf hostname-table command output
Item Description
Router ID

Router ID.
Hostname

OSPF hostname.
Area

Area ID.
Scope

Flooding scope.

-Area OSPF area range (divided based on the area ID).

-AS-Scope: OSPF autonomous system (AS) scope.

display ospf interface

Function

The display ospf interface command displays OSPF interface information.

Format

display ospf [ process-id ] interface [ interface-name | interface-type interface-number | all ] [ verbose ]

display ospf [ process-id ] interface no-peer

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
interface-type

Interface type.

-
interface-number

Specifies the number of an interface based on which information about VLANs in which users go online dynamically is to be displayed.

-
all

Displays information about all OSPF interfaces.

-
verbose

Displays detailed information about OSPF interfaces.

-
no-peer

Specifies to display the interfaces whose states are Up but have no neighbors.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To check the configuration and operating status of OSPF, run the display ospf interface command. The command output helps you locate faults and verify configurations.

The command output includes such information as all OSPF interfaces, interface types, status, and attributes. If an OSPF neighbor relationship fails to be established or routes are incorrectly calculated, you can run the command to check whether OSPF interfaces are normal.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about OSPF interfaces that have no neighbors.
<HUAWEI> display ospf interface no-peer
OSPF Process 1 with Router ID 172.16.6.185
                  Interfaces

 Area: 0.0.0.0          (MPLS TE not enabled)
 Interface             IP Address      Type         State    Cost    Pri  
 Loop2147483647        172.16.6.185    P2P          P-2-P    0       1
# Display information about the specified OSPF interface.
<HUAWEI> display ospf interface 10GE1/0/1
OSPF Process 1 with Router ID 1.1.1.1
                  Interfaces

 Area: 0.0.0.0               (MPLS TE not enabled)
 Interface: 192.168.1.1 ( 10GE1/0/1 ) --> 192.168.1.2
 Cost: 1       State: P-2-P         Type: P2P            MTU: 1500
 Timers: Hello 10 , Dead 40 , Wait 40 , Poll 120 , Retransmit 5 , Transmit Delay 1
Multi-area interface
# Display OSPF interface information.
<HUAWEI> display ospf interface
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                  
 Area: 0.0.0.0             (MPLS TE not enabled)
 Interface                IP Address      Type      State    Cost    Pri
 10GE1/0/1                192.168.1.1     P2P       P-2-P    1       100
Table 2-459 Description of the display ospf interface command output
Item Description
OSPF Process 1 with Router ID 1.1.1.1

OSPF process ID and router ID.
Interface

Interface name.
IP Address

IP address of the interface.
Type

Interface type: P2P, P2MP, broadcast, or NBMA.
State

Status of the interface, which is determined by the OSPF interface state machines:

  • Down: The status of the interface is Down. If an interface is Down, the interface is unavailable and cannot be used to transmit traffic.
  • Loopback: The interface connecting to the network on the router is in the Loopback state. The loopback interface cannot be used to transmit data but can collect interface information through ICMP ping operations or bit error detection.
  • Waiting: The router is determining the DR and BDR on the network. The DR or BDR election mechanism is not implemented until the waiting period ends. This prevents unnecessary changes in the DR and BDR roles.
  • P-2-P: The interface is connected to the P2P network or a virtual link.
  • DROther: The router itself is not elected as the BDR. Instead, another router connecting to the broadcast network or NBMA network is elected as the DR. The router starts to set up adjacency with the DR and BDR (if existing).
  • BDR: The router functions as the BDR on the network, and will turn into a DR when the current DR fails. The router sets up adjacency with other routers that access the network.
  • DR: The router functions as the DR on the network. The router sets up adjacency with other routers that access the network.
Cost

Cost of the interface.
Pri

Priority of the device interface during the DR and BDR election. The greater the value, the higher the priority.
Hello

Interval at which Hello packets are sent, which can be set using the ospf timer hello command.
Dead

OSPF neighbor dead interval, which can be set using the ospf timer dead command.
Wait

The wait timer on an OSPF interface, which can be set using the ospf timer wait command.
Poll

Interval at which poll Hello packets are sent on NBMA networks, which can be set using the ospf timer poll command.
Retransmit

Interval at which LSAs are retransmitted, which can be set using the ospf timer retransmit command.
Transmit Delay

LSA transmission delay, which can be set using the ospf trans-delay command.
MPLS TE not enabled

MPLS TE is disabled.
Area

ID of the area to which the interface belongs.
MTU

MTU of the interface.
Timers

Timer intervals:

  • Hello: interval at which an interface sends Hello packets, which can be set using the ospf timer hello command.
  • Dead: OSPF neighbor dead interval, which can be set using the ospf timer dead command.
  • Wait: OSPF wait interval, which can be set using the ospf timer wait command.
  • Poll: interval at which poll Hello packets are sent on NBMA networks, which can be set using the ospf timer poll command.
  • Retransmit: interval at which an interface retransmits LSAs, which can be set using the ospf timer retransmit command.
  • Transmit Delay: LSA transmission delay, which can be set using the ospf trans-delay command.
flapping-count

Number of valid interface flapping events.
threshold

Flapping suppression threshold on an interface.

display ospf lsdb

Function

The display ospf lsdb command displays the OSPF Link-State Database (LSDB).

Format

display ospf [ process-id ] lsdb [ { [ { router | network | summary | asbr | ase | opaque-as [ origin ] | opaque-area [ origin ] | opaque-link [ origin ] | nssa } [ link-state-id ] ] [ originate-router [ advertising-router-id ] | hostname hostname | self-originate ] } ] [ age { min-value min-age-value | max-value max-age-value } * ]

display ospf [ process-id ] lsdb [ { [ { router | network | summary | asbr | ase | opaque-as [ origin ] | opaque-area [ origin ] | opaque-link [ origin ] | nssa } [ link-state-id ] ] [ originate-router [ advertising-router-id ] | self-originate ] } ] [ age { min-value min-age-value | max-value max-age-value } * ] resolve-hostname

Parameters

Parameter Description Value
process-id

process-id.

The value is an integer ranging from 1 to 4294967295.
router

Displays historical information about Router LSAs.

-
network

Displays historical information about Network LSAs.

-
summary

Displays information about the network summary LSA.

-
asbr

Displays historical information about ASBR-summary LSAs.

-
ase

Displays information about the AS external LSA.

-
opaque-as

Displays information about the opaque AS LSA.

-
origin

Display the original content of the LSA.

-
opaque-area

Displays information about the opaque area LSA.

-
opaque-link

Displays information about the opaque link LSA.

-
nssa

Displays information about the status of external links in the NSSA.

-
link-state-id

Specifies the LSID of an LSA.

The value is in dotted decimal notation.
originate-router

Displays the LSA of the advertising router.

-
advertising-router-id

Specifies the router ID of the LSA advertising device.

The value is in dotted decimal notation.
hostname hostname

Displays information about the LSDB of a host.

The value is a string of 1 to 255 case-insensitive characters, spaces not supported.
self-originate

Displays the status of self-generated links.

-
age

Displays the LSAs that age in the scope.

-
min-value min-age-value

Displays the LSAs that age equal or more than min-age-value.

The value is an integer ranging from 0 to 3600.
max-value max-age-value

Displays the LSAs that age equal or less than max-age-value.

The value is an integer ranging from 0 to 3600.
resolve-hostname

Displays the hostname resolved from a router ID.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display ospf lsdb command displays information about the LSDB in various modes, including:

  • Brief information about the LSDB
  • LSAs of a specified type
  • LSAs of the originating device
  • Locally originated LSAs

    The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about the opaque-as LSAs in the LSDB.
<HUAWEI> display ospf 1 lsdb opaque-as

          OSPF Process 1 with Router ID 10.2.2.1
                  Link State Database

  Type      : Opq-As
  Ls id     : 10.0.0.0
  Adv rtr   : 10.1.1.1
  Ls age    : 551
  Len       : 48
  Options   :  E
  seq#      : 8000003d
  chksum    : 0xa1ac
  Opaque Type: 7
  Opaque Id: 0
  OSPFv2 Extended Prefix Opaque LSA TLV information:
    OSPFv2 Extended Prefix TLV:
      Route Type: AS-External
      AF: IPv4-Unicast
      Flags: 0xc0 (A|N|-|-|-|-|-|-)
      Prefix: 10.1.1.0/24
      Redistribute-list Sub-TLV:
        Flags    : --
        RouterId : 0x1010101-1,0x0-0
# Display information about opaque-area LSAs in the OSPF LSDB.
<HUAWEI> display ospf 1 lsdb opaque-area
          OSPF Process 1 with Router ID 10.1.1.1
                          Area: 0.0.0.0
                  Link State Database

  Type      : Opq-Area
  Ls id     : 10.0.0.1
  Adv rtr   : 10.1.1.1
  Ls age    : 639
  Len       : 200
  Options   :  E
  seq#      : 80000001
  chksum    : 0x2175
  Opaque Type: 1
  Opaque Id: 1
  Opaque lsa information:

     00 02 00 b0 00 01 00 01 02 00 00 00 00 02 00 04
     0a 01 01 01 00 03 00 04 0a 01 01 01 00 04 00 04
     00 00 00 00 00 05 00 04 00 00 00 01 80 02 00 04
     00 00 00 01 00 06 00 04 00 00 00 00 00 07 00 04
     00 00 00 00 80 00 00 04 00 00 00 00 00 09 00 04
     00 00 00 00 00 08 00 20 00 00 00 00 00 00 00 00
     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     00 00 00 00 00 00 00 00 80 01 00 20 00 00 00 00
     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 09
     00 00 00 00 00 00 00 00 00 00 00 00 00 0c 00 04
     00 01 00 01
 

  Type      : Opq-Area
  Ls id     : 10.0.0.4
  Adv rtr   : 10.1.1.1
  Ls age    : 940
  Len       : 32
  Options   :  E
  seq#      : 80000003
  chksum    : 0xbdb8
  Opaque Type: 4
  Opaque Id: 0
  Router-Information LSA TLV information:
    SR-Algorithm TLV:
      Algorithm: SPF
    SID/Label Range TLV:
      Range Size: 50001
      SID/Label Sub-TLV:
        Label: 200000
    Dynamic Hostname TLV:
      Hostname: mckck
    Node MSD TLV:
      MSD Type  : 1
      MSD Value : 10 


  Type      : Opq-Area
  Ls id     : 10.0.0.7
  Adv rtr   : 10.1.1.1
  Ls age    : 1158
  Len       : 44
  Options   :  E
  seq#      : 80000024
  chksum    : 0x58fc
  Opaque Type: 7
  Opaque Id: 0
  OSPFv2 Extended Prefix Opaque LSA TLV information:
    OSPFv2 Extended Prefix Range TLV:
      AF: IPv4-Unicast
      Flags: 0x00 (-|-|-|-|-|-|-|-)
      Prefix: 10.5.5.5/32
      Range: 1
      Prefix SID Sub-TLV:
        Flags: 0x60 (-|NP|M|-|-|-|-|-)
        MT ID: 0
        Algorithm: SPF
        Index: 1
                          Area: 0.0.0.1
                  Link State Database


  Type      : Opq-Area
  Ls id     : 10.0.0.8
  Adv rtr   : 10.1.1.1
  Ls age    : 13
  Len       : 56
  Options   :  E
  seq#      : 8000014a
  chksum    : 0x7ff8
  Opaque Type: 8
  Opaque Id: 0
  OSPFv2 Extended Link Opaque LSA TLV information:
    OSPFv2 Extended Link TLV:
      Link Type: P-2-P
      Link ID: 10.2.2.2
      Link Data: 10.0.0.12
      Remote IPv4 Address Sub-TLV:
        Remote Address: 10.0.0.2
      Local Remote Interface ID Sub-TLV:
        Local Interface ID: 9
        Remote Interface ID: 0
# Display original information about Opaque-area LSAs in the LSDB.
<HUAWEI> display ospf 1 lsdb opaque-area origin
          OSPF Process 1 with Router ID 10.1.1.1
                          Area: 0.0.0.0
                  Link State Database

  Type      : Opq-Area
  Ls id     : 10.0.0.4
  Adv rtr   : 10.1.1.1
  Ls age    : 4
  Len       : 64
  Options   :  E
  seq#      : 80000003
  chksum    : 0x71fd
  Opaque Type: 4
  Opaque Id: 0
  Opaque lsa information:

     00 08 00 01 00 00 00 00 00 09 00 0c 00 03 e9 00 
     00 01 00 03 00 3e 80 00 00 07 00 06 48 55 41 57 
     45 49 00 00 00 0c 00 02 01 0a 00 00
# Display information about the OSPF LSDB.
<HUAWEI> display ospf lsdb
          OSPF Process 1 with Router ID 10.1.1.1
                  Link State Database

                          Area: 0.0.0.0
 Type      LinkState ID    AdvRouter        Age  Len   Sequence       Metric
 Router    10.1.1.1         10.1.1.1           93  48    80000004            1
 Router    10.2.2.2         10.2.2.2           92  48    80000004            1
 Sum-Net   172.16.1.0      10.1.1.1         1287  28    80000002            2
 Sum-Net   192.168.1.0     10.1.1.1         1716  28    80000001            1
 Sum-Net   172.17.1.0      10.2.2.2         1336  28    80000001            2
 Sum-Net   192.168.2.0     10.2.2.2           87  28    80000002            1
# Display information about router LSAs in the OSPF LSDB.
<HUAWEI> display ospf 1 lsdb router 1.1.1.1

          OSPF Process 1 with Router ID 1.1.1.1
                          Area: 0.0.0.0
                  Link State Database


  Type      : Router
  Ls id     : 1.1.1.1
  Adv rtr   : 1.1.1.1
  Ls age    : 430
  Len       : 48
  Options   :  ABR  E
  seq#      : 80000014
  chksum    : 0xf615
  Link count: 2
     Link ID: 10.1.1.2
     Data   : 10.1.1.1
     Link Type: TransNet
     Metric : 1
     Link ID: 1.1.1.1
     Data   : 255.255.255.255
     Link Type: StubNet
     Metric : 0
# Display information about network LSAs in the OSPF LSDB.
<HUAWEI> display ospf 1 lsdb network 10.1.1.2

          OSPF Process 1 with Router ID 1.1.1.1
                          Area: 0.0.0.0
                  Link State Database


  Type      : Network
  Ls id     : 10.1.1.2
  Adv rtr   : 2.2.2.2
  Ls age    : 571
  Len       : 32
  Options   :  E
  seq#      : 80000004
  chksum    : 0x2f08
  Net mask  : 255.255.255.0
     Attached Router: 1.1.1.1
     Attached Router: 2.2.2.2
Table 2-460 Description of the display ospf lsdb command output
Item Description
Link Data

Link data.
Link Type

Link type of the OSPFv2 extended link TLV.
Link ID

For extended link TLVs, Link ID indicates the OSPFv2 link ID.

For router LSAs, link IDs have different meanings in different link types.

  • If the link type is P2P, Link ID indicates the router ID of the neighbor.
  • If the link type is TransNet, Link ID indicates the IP address of the DR.
  • If the link type is Stub, Link ID indicates the IP address.
  • If the link type is Virtual Link, Link ID indicates the router ID of the neighbor.
Link count

Number of router LSA links.
Type

LSA type: Router, Network, Sum-Net, Sum-Asbr, NSSA, External, Opq-Link, Opq-Area, or Opq-As.
Ls age

LSA aging time.
Ls id

Link state ID of the LSA that causes route calculation.
Adv rtr

Router ID of the device that generates the LSA that causes route calculation.
Len

LSA length.
Options

LSDB option.

  • E: allows the flooding of AS-External-LSAs.
  • MC: forwards IP multicast packets.
  • N/P: indicates that Type 7 LSAs are processed.
  • DC: processes on-demand links.
chksum

Check LSDB num.
Opaque lsa information

Detailed Opaque LSA information.
Opaque Id

Opaque ID, distinguishing between a type of LSAs from others that are applied to the same type of applications.
Opaque Type

LSA application type.

Value 1 indicates traffic engineering; value 3 indicates OSPF graceful restart.
OSPFv2 Extended Prefix Range TLV

OSPFv2 Extended Prefix Range TLV information.
OSPFv2 Extended Prefix TLV

OSPFv2 Extended Prefix TLV information.
OSPFv2 Extended Link TLV

OSPFv2 Extended Link TLV information.
OSPFv2 Extended Prefix Opaque LSA TLV information

OSPFv2 extended prefix Opaque LSA TLV information.
OSPFv2 Extended Link Opaque LSA TLV information

OSPFv2 extended link Opaque LSA TLV information.
Prefix

Prefix information.
Prefix SID Sub-TLV

Information about the OSPFv2 prefix SID sub-TLV.
Route Type

Route type.
Flags

OSPFv2 extended prefix range TLV flag.
Flags

Flag of the flexible algorithm prefix metric sub-TLV.
Flags

Flexible algorithm definition flag.
RouterId

Router ID.
Router-Information LSA TLV information

Router-information (RI) LSA TLV information.
SR-Algorithm TLV

SR-Algorithm TLV information.
SID/Label Range TLV

SID/Label Range TLV information.
SID/Label Sub-TLV

SID/Label Sub-TLV information.
Range Size

SID range.
Range

Prefix Range.
Dynamic Hostname TLV

Dynamic Hostname TLV information.
Hostname

Name of the host that advertises routes.
Node MSD TLV

Displays the maximum stack depth TLV information of a node.
MSD Type

Maximum stack depth type.
MSD Value

Maximum stack depth.
MT ID

Multi-topology ID of the OSPFv2 prefix SID sub-TLV.
Remote IPv4 Address Sub-TLV

Remote IPv4 Address Sub-TLV information.
Remote Address

Remote IPv4 address.
Remote Interface ID

Remote interface ID.
Local Remote Interface ID Sub-TLV

Local Remote Interface ID Sub-TLV information.
Local Interface ID

ID of the local interface.
LinkState ID

Link State ID in the LSA header.
AdvRouter

Device that advertises or generates LSAs.
Age

Aging time of the LSA.
Sequence

Sequence number of the LSA (in the LSA header).
Metric

Cost.
Metric

Prefix metric of the flexible algorithm.
Data

(Router LSA) Link Data:

  • If the link type is P2P, TransNet, or Virtual Link, Data indicates the IP address.
  • If the link type is Stub, Link Data indicates the mask of the IP address.
Net mask

(Network LSA) network mask.
Attached Router

(Network LSA) router that connects to the network.
Area

Area whose LSDB information needs to be displayed.
Label

Start SID of a range.
AF

Address family.
Algorithm

Algorithm of the OSPFv2 prefix SID sub-TLV:

  • SPF.
  • Algorithm 128–255.
Index

Index of the OSPFv2 prefix SID sub-TLV.
UDA-Length

Mask length of the user-defined application identifier bit.

display ospf lsdb brief

Function

The display ospf lsdb brief command displays brief information about the OSPF Link-State Database (LSDB).

Format

display ospf [ process-id ] lsdb brief

Parameters

Parameter Description Value
process-id

process-id.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display ospf lsdb brief command displays brief information about the OSPF LSDB, which helps you locate faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Displays OSPF LSDB brief information.
<HUAWEI> display ospf lsdb brief
2020-03-09 15:52:18.616

          OSPF Process 1 with Router ID 10.33.33.33
                  LS Database Statistics

 Area ID         Stub   Router   Network  S-Net   S-ASBR   Type-7   | Subtotal
 0.0.0.0         0      1        0        0       0        0        | 1
 0.0.0.1         0      0        0        0       0        0        | 0
 Total           0      1        0        0       0        0        |
 -------------------------------------------------------------------+---------
 Area ID         Opq-9  Opq-10                                      | Subtotal
 0.0.0.0         0      0                                           | 0
 0.0.0.1         0      0                                           | 0
 Total           0      0                                           |
 -------------------------------------------------------------------+---------
                 ASE      Opq-11                                    | Subtotal
 Total           12       0                                         | 12
 -------------------------------------------------------------------+---------
                                                                    | Total
                                                                    | 13
Table 2-461 Description of the display ospf lsdb brief command output
Item Description
Router

Number of Router-LSAs.
Area ID

Area ID.
Network

Number of Network-LSAs.
S-Net

Number of Summary-Net-LSAs.
S-ASBR

Number of Summary-ASBR-LSAs.
Type-7

Number of Type-7 LSAs.
Subtotal

Total number of horizontal items in the displayed information.
Total

Total number of vertical items in the displayed information.
Opq-9

Number of Opaque-9 LSAs.
Opq-10

Number of Opaque-10 LSAs.
ASE

Number of AS-External LSAs.
Opq-11

Number of Opaque-11 LSAs.

display ospf nexthop

Function

The display ospf nexthop command displays OSPF next hop information.

Format

display ospf [ process-id ] nexthop

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view information about all the OSPF next hops, run the display ospf nexthop command. The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display OSPF next hop information.
<HUAWEI> display ospf nexthop
OSPF Process 1 with Router ID 10.1.1.1
                  Routing Nexthop information

Next hops:
 Address        Type  Refcount   Intf Addr         Intf Name
--------------------------------------------------------------
 192.168.0.1    Local 1          192.168.0.1       LoopBack1
 10.10.1.1      Local 1          10.10.1.1         10GE1/0/7
 10.20.1.1      Local 1          10.20.1.1         10GE1/0/8

<HUAWEI> display ospf nexthop
OSPF Process 1 with Router ID 10.1.1.1
                  Routing Nexthop information

Next hops:
 Address        Type  Refcount   Intf Addr       Intf Name
--------------------------------------------------------------
 192.168.0.1    Local 1          192.168.0.1     LoopBack1
 10.10.1.1      Local 1          10.10.1.1       100GE1/0/7
 10.20.1.1      Local 1          10.20.1.1       100GE1/0/8
Table 2-462 Description of the display ospf nexthop command output
Item Description
Next hops

Detailed information about the next hop.
Address

Next hop.
Type

Type of the route passing through the next hop. Local indicates that the route is destined for the local network segment.
Refcount

Number of OSPF routes that use the next hop.
Intf Addr

Interface address.
Intf Name

Interface name.

display ospf peer

Function

The display ospf peer command displays information about neighbors in each OSPF area.

Format

display ospf [ process-id ] peer [ interfaceName | interfaceType interfaceNum | { neighbor-id | hostname hostnamestr } | brief | last-nbr-down ]

display ospf [ process-id ] peer { { interfaceName | interfaceType interfaceNum } { neighbor-id [ resolve-hostname ] | hostname hostnamestr } }

display ospf [ process-id ] peer [ interfaceName | interfaceType interfaceNum | neighbor-id | brief ] resolve-hostname

display ospf [ process-id ] peer [ interfaceType interfaceNum | neighbor-id | brief ] dns-hostname

display ospf [ process-id ] peer { interfaceType interfaceNum | neighbor-id [ dns-hostname ] | dns-hostname hostnamestr }

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
interfaceName

Specifies the name of an interface.

-
interfaceType

Specifies the type of an interface.

-
interfaceNum

Specifies the interface number.

The value is a string of 1 to 63 case-sensitive characters. It cannot contain spaces.
neighbor-id

Specifies the router ID of a neighbor.

The value is in dotted decimal notation.
hostname hostnamestr

Specifies a dynamic hostname.

The value is a string of 1 to 255 characters.
brief

Displays summaries of OSPF neighbors in each area.

-
last-nbr-down

Displays brief information about the last neighbor that goes Down in the OSPF area.

-
resolve-hostname

Displays information about resolved dynamic hostnames.

-
dns-hostname hostnamestr

Displays information about neighbors with a specified static hostname.

The value is a string of 1 to 255 characters.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The command output can display information about OSPF neighbors, and help you troubleshoot OSPF faults, verify the configurations of OSPF neighbors, and check whether the neighbor performs Graceful Restart (GR).

The command output includes such information as all OSPF interfaces, interface types, status, and attributes. If an OSPF neighbor relationship fails to be established or routes are incorrectly calculated, you can run the command to check whether OSPF interfaces are normal.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display brief information about OSPF neighbors.
<HUAWEI> display ospf 1 peer brief
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                   Peer Statistic Informations

  Total number of peer(s): 2
  Peer(s) in full state: 2

-------------------------------------------------------------------------
 Area Id         Interface      Neighbor id      State
 0.0.0.0         10GE1/0/7        1.1.1.2          Full
 0.0.0.1         10GE1/0/8        1.1.1.2          Full
-------------------------------------------------------------------------

<HUAWEI> display ospf 1 peer brief
(M) Indicates MADJ interface
          OSPF Process 1 with Router ID 1.1.1.1
                   Peer Statistic Informations

  Total number of peer(s): 2
  Peer(s) in full state: 2

-------------------------------------------------------------------------
 Area Id         Interface      Neighbor id      State
 0.0.0.0         100GE1/0/7        1.1.1.2          Full
 0.0.0.1         100GE1/0/8        1.1.1.2          Full
-------------------------------------------------------------------------
# Display information about the OSPF neighbor that goes Down for the last time.
<HUAWEI> display ospf 1 peer last-nbr-down

          OSPF Process 1 with Router ID 10.1.1.1

                         Last Down OSPF Peer

         Neighbor Ip Address : 10.2.1.2
         Neighbor Area   Id  : 0.0.0.0
         Neighbor Router Id  : 10.1.1.2
         Interface           : 10GE1/0/1 (9)
         Immediate Reason    : Neighbor Down Due to Kill Neighbor
         Primary Reason      : Hello Not Seen
         Down Time           : 2010-02-11 06:50:23

<HUAWEI> display ospf 1 peer last-nbr-down

          OSPF Process 1 with Router ID 10.1.1.1

                         Last Down OSPF Peer

         Neighbor Ip Address : 10.2.1.2
         Neighbor Area   Id  : 0.0.0.0
         Neighbor Router Id  : 10.1.1.2
         Interface           : 100GE1/0/1 (9)
         Immediate Reason    : Neighbor Down Due to Kill Neighbor
         Primary Reason      : Hello Not Seen
         Down Time           : 2010-02-11 06:50:23
# Display information about the OSPF neighbor.
<HUAWEI> display ospf peer
OSPF Process 1 with Router ID 1.1.1.1
 Area 0.0.0.0 interface 192.168.1.1 ( 10GE1/0/8 )'s neighbors
  Router ID: 2.2.2.2         Address : 192.168.1.2
  State    : 2-Way           Mode    : Nbr is  Slave   Priority: 1
  DR       : 192.168.1.4     BDR     : 192.168.1.3     MTU     : 0
  Dead timer due (in seconds) : 32
  Retrans timer interval      : 5
  Neighbor up time            : 00h04m14s
  Neighbor up time stamp      : 2020-06-08 01:41:57
  Authentication Sequence     : 0

<HUAWEI> display ospf peer
OSPF Process 1 with Router ID 1.1.1.1
 Area 0.0.0.0 interface 192.168.1.1 ( 100GE1/0/8 )'s neighbors
  Router ID: 2.2.2.2         Address : 192.168.1.2
  State    : 2-Way           Mode    : Nbr is  Slave   Priority: 1
  DR       : 192.168.1.4     BDR     : 192.168.1.3     MTU     : 0
  Dead timer due (in seconds) : 32
  Retrans timer interval      : 5
  Neighbor up time            : 00h04m14s
  Neighbor up time stamp      : 2020-06-08 01:41:57
  Authentication Sequence     : 0
Table 2-463 Description of the display ospf peer command output
Item Description
(M) Indicates MADJ interface

Multi-area adjacency interface.
OSPF Process 1 with Router ID 1.1.1.1

OSPF process ID and router ID.
Router ID

Router ID of the neighbor.
Total number of peer(s)

Total information of neighbors.
Peer(s) in full state

Number of entries with the neighbor state Full.
Area

Area to which the neighbor belongs.
Area Id

Area to which the neighbor belongs.
Interface

Interface that connects to the neighbor.
Neighbor up time stamp

Time when the peer went Up.
Neighbor id

Neighbor ID.
Neighbor Ip Address

Interface IP address of the neighbor.
Neighbor Area Id

Area to which the neighbor belongs.
Neighbor Router Id

Router ID of the neighbor.
Neighbor up time

Time when the peer went Up.
State

Neighbor status:

  • Down: It is the initial status of the neighbor, indicating that the neighbor does not receive any information. On an NBMA network, when the neighbor is Down, Hello packets can still be transmitted at the poll interval, which is longer than the Hello interval.
  • Attempt: It exists only on an NBMA network, indicating that two ends are attempting to establish the neighbor relationship. The interval at which Hello packets are sent is the Hello interval, which is shorter than the poll interval.
  • Init: It indicates that the Hello packet has been received from the neighbor.
  • 2-Way: It indicates that the Hello packet has been received from the neighbor, and the neighbor list of the Hello packet contains the local router ID. That is, the two ends can interwork.
  • ExStart: It is the first step of establishing adjacencies. In this step, the master and slave relationship and Database Description (DD) sequence number are negotiated.
  • Exchange: It indicates that the LSDBs start to be synchronized. In this process, DD packets, Link Status Request (LSR) packets, and Link Status Update (LSU) packets are exchanged.
  • Loading: It indicates that the LSDBs are being synchronized. In this process, LSR packets and LSU packets are exchanged.
  • Full: It indicates that the LSDB of the neighbor has been synchronized, and the Full adjacency is established between both ends.
Mode

Master or slave in the process of exchanging DD packets:

  • Nbr is Master: indicates that the neighbor is the master and actively sends DD packets.
  • Nbr is Slave: The neighbor is the slave and cooperates with the master to send DD packets.
DR

DR.
BDR

Backup designated router.
MTU

Maximum Transmission Unit (MTU) value of the neighboring interface.
Dead timer due in 32 sec

The Dead timer expires in x seconds.
Dead timer due (in seconds)

Remaining time (in seconds) of the Dead timer.
Retrans timer interval

Interval for retransmitting LSAs, in seconds.
Authentication Sequence

Authentication sequence number.
Down Time

Time when the neighbor goes Down.
Address

Interface IP address of the neighbor.
Immediate Reason

Direct reason why the neighbor goes Down.

  • Neighbor Down Due to Inactivity: The inactivity timer expires.
  • Neighbor Down Due to LL Down: The link is Down. For example, the interface goes Down or the IP address of the link is deleted.
  • Neighbor Down Due to Kill Neighbor: The Kill Neighbor event occurs on the neighbor state machine of the interface.
  • Neighbor Down Due to 1-Wayhello: The neighbor goes Down because only one end receives Hello packets.
  • Received: Neighbor Down Due to AdjOK?: An AdjOK? event occurs on the interface.
  • Neighbor Down Due to SequenceNum Mismatch: A Sequence Number Mismatch event occurs on the neighbor state machine of the interface.
  • Neighbor Down Due to BadLSreq: A BadLSreq event occurs on the neighbor state machine of the interface.
Primary Reason

Root Cause of the Neighbor Down Event.

  • Hello Not Seen: No Hello packet is received.
  • Interface Parameter Mismatch: indicates that the parameters of the interfaces on both ends of the link do not match.
  • Logical Interface State Change: The status of the logical interface changes.
  • Link Fault or Interface Configuration Change: The link is faulty or the interface configuration is changed.
  • OSPF Process Reset: indicates that the OSPF process is restarted.
  • Area reset: The area restarts because the area type changes.
  • Area Option Mis-match: The area options of the interfaces on both ends of the link do not match.
  • Vlink Peer Not Reachable: The neighbor on the virtual link is unreachable.
  • Sham-Link Unreachable: The sham-link is unreachable.
  • Undo Network Command: The network command is deleted.
  • Undo NBMA Peer: The neighbor configuration on the NBMA interface is deleted.
  • Passive Interface Down: The neighbor relationship goes Down because the silent-interface command is configured on the local interface and the interface is disabled from receiving and sending OSPF packets.
  • Opaque Capability Enabled: The Opaque capability is enabled.
  • Opaque Capability Disabled: indicates that the Opaque capability is disabled.
  • Virtual Interface State Change: indicates that the status of the interface on the virtual link changes.
  • BFD Session Down: The BFD session is Down.
  • Retransmission Limit Exceed: The retransmission limit is reached.
  • 1-Wayhello Received: Only one end receives Hello packets.
  • Router State Change from DR or BDR to DROTHER: The interface state machine changes from DR or BDR to DROTHER.
  • Neighbor State Change from DR or BDR to DROTHER: The interface state machine changes from DR or BDR to DROTHER.
  • NSSA Area Configure Change: indicates that the configuration of the NSSA area changes.
  • Stub Area Configure Change: indicates that the configuration of the stub area changes.
  • Received Invalid DD Packet: indicates that invalid DD packets are received.
  • Not Received DD during RouterDeadInterval: No DD packet is received when the Dead timer starts.
  • M,I,MS bit or SequenceNum Incorrect: The M, I, and MS bits in the received DD packets do not comply with the protocol.
  • Unable Opaque Capability,Find 9,10,11 Type Lsa: indicates that LSAs of types 9, 10, and 11 are received, but the Opaque capability is not enabled.
  • Not NSSA,Find 7 Type Lsa in Summary List: indicates that the local area does not belong to the NSSA but Type 7 LSAs are found in the summary table.
  • LSrequest Packet,Unknown Reason: indicates that LSR packets are received due to unknown reasons.
  • NSSA or STUB Area,Find 5 ,11 Type Lsa: indicates that the local area belongs to the NSSA or Stub area, but Type 5 and Type 11 LSAs are discovered.
  • LSrequest Packet,Request Lsa is Not in the Lsdb: indicates that the neighbor requests an LSA from the local process or area but the requested LSA does not exist in the LSDB of the local process or area.
  • LSrequest Packet, exist same lsa in the Lsdb: indicates that the OSPF process receives an identical LSA in the local LSDB, and the LSA exists in the request list of the neighbor.
  • LSrequest Packet, exist newer lsa in the Lsdb: indicates that the local process receives an updated LSA that already exists in the local LSDB and in the request list of the neighbor.
  • Neighbor state was not full when LSDB overflow: If the neighbor status does not reach Full, the neighbor goes Down.
  • Filter LSA configuration change: indicates that the LSA-filter configuration changes.
  • ACL changed for Filter LSA: indicates that the ACL configuration of LSA-filter changes.
  • Reset Ospf Peer: indicates that the OSPF neighbor is restarted.
  • Interface Reset: Restart the interface.
  • Undo OSPF Interface, Undo area, Undo network: The interface, area, or network is disabled.
  • UNDO OSPF Area: The area is disabled.
  • CPU Overload: The CPU is overloaded.
  • Interface State Change to Standby: The interface becomes standby.
  • Undo Router-Id: The router ID is deleted.
  • Neighbor Router-Id changed or Ip Conflicted: The router ID of the neighbor changed or the IP address conflicted.
  • Component is in Implement stat: indicates that the component status is incomplete.
  • Seqeunce Number mismatched: The sequence number does not match.
  • I Bit Incorrect in DD: The I bit in DD packets does not match.
  • MS Bit Incorrect in DD: The MS bit in DD packets does not match.
  • Options Incorrect in DD: The option fields of DD packets do not match.
  • The MTU of the DD packet received by the Received MTU mismatched DD Packet does not match.
  • OSPF Process Shutdown: The OSPF process is shut down.
  • OSPF Max Nbr In Adj: indicates that the number of OSPF neighbors exceeds the maximum value.
  • OSPF Dcn Intf Para MisMatch: OSPF DCN interface parameters do not match.
  • OSPF Gr Master ForceDown: "OSPF Gr is forcibly shut down.
  • DD retrans times upto limit: The number of retransmitted DD packets reaches the upper limit.
  • Neighbor state was not full when LSDB overflow: OSPF flow control.
  • Received DD packet without R bit in graceful-restart status: indicates that DD packets received in GR state do not carry the R bit.
  • Memory Overload: The memory is overloaded.
  • Undo OSPF Interface, Undo area: Delete an interface or an area.
Priority

Priority of the neighbor.

display ospf request-queue

Function

The display ospf request-queue command displays the OSPF request list.

Format

display ospf [ process-id ] request-queue [ InterfaceName | interfaceType interfaceNum ] [ neighbor-id ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
InterfaceName

Specifies the name of an interface.

-
interfaceType

Specifies the type of an interface.

-
interfaceNum

Specifies the interface number.

-
neighbor-id

The router ID of a neighbor.

The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view OSPF statistics, run the display ospf cumulative command. The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display the OSPF request list.
<HUAWEI> display ospf request-queue
OSPF Process 1 with Router ID 1.1.1.1
OSPF Request List
The Router's Neighbor is Router ID 4.4.4.4         Address 10.1.4.2
Interface 10.1.4.1        Area 0.0.0.2
Request list:
Type       LinkState ID      AdvRouter         Sequence   Age
Router     1.1.1.1           1.1.1.1           8000001b   677
Table 2-464 Description of the display ospf request-queue command output
Item Description
Router ID

Router ID of the current route.
Request list

Request list.
The Router's Neighbor is Router ID

Router ID of the neighbor.
Address

IP address of the neighboring interface.
Interface

IP address of an interface.
Area

Area to which the local router belongs.
Type

LSA type:

Router LSA, network LSA, network summary LSA, ASBR summary LSA, AS external LSA, or opaque LSA.
LinkState ID

Link state ID in the LSA header.
AdvRouter

Advertising router in the LSA header.
Sequence

Sequence number in the LSA header.
Age

Aging time in the LSA header.

display ospf retrans-queue

Function

The display ospf retrans-queue command displays the OSPF retransmission list.

Format

display ospf [ process-id ] retrans-queue [ InterfaceName | interfaceType interfaceNum ] [ neighbor-id ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
InterfaceName

Specifies the name of an interface.

-
interfaceType

Specifies the type of an interface.

-
interfaceNum

Specifies the interface number.

-
neighbor-id

The router ID of a neighbor.

The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view OSPF statistics, run the display ospf cumulative command. The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display the OSPF retransmission list.
<HUAWEI> display ospf retrans-queue
OSPF Process 1 with Router ID 10.1.1.1
                  OSPF Retransmit List
 Area 0.0.0.0 interface 10.10.1.1 (10GE1/0/1)'s neighbors
  Retransmit list:
  Neighbor ID: 10.1.1.2
 Type             LinkState ID      AdvRouter         Sequence   Age
 1                10.1.1.1          10.1.1.1          8000000b     4
 5                10.1.1.0         10.1.1.1          80000001     4
 5                10.1.2.0         10.1.1.1          80000001     4
 5                10.1.3.0         10.1.1.1          80000001     4
 5                10.1.4.0         10.1.1.1          80000001     4
 5                10.1.5.0         10.1.1.1          80000001     4
 5                10.1.6.0         10.1.1.1          80000001     4
 5                10.1.7.0         10.1.1.1          80000001     4
 5                10.1.8.0         10.1.1.1          80000001     4
 5                10.1.9.0         10.1.1.1          80000001     4
 5                10.1.10.0        10.1.1.1          80000001     4

<HUAWEI> display ospf retrans-queue
OSPF Process 1 with Router ID 10.1.1.1
                  OSPF Retransmit List
 Area 0.0.0.0 interface 10.10.1.1 (100GE1/0/1)'s neighbors
  Retransmit list:
  Neighbor ID: 10.1.1.2
 Type             LinkState ID      AdvRouter         Sequence   Age
 1                10.1.1.1         10.1.1.1          8000000b     4
 5                10.1.1.0         10.1.1.1          80000001     4
 5                10.1.2.0         10.1.1.1          80000001     4
 5                10.1.3.0         10.1.1.1          80000001     4
 5                10.1.4.0         10.1.1.1          80000001     4
 5                10.1.5.0         10.1.1.1          80000001     4
 5                10.1.6.0         10.1.1.1          80000001     4
 5                10.1.7.0         10.1.1.1          80000001     4
 5                10.1.8.0         10.1.1.1          80000001     4
 5                10.1.9.0         10.1.1.1          80000001     4
 5                10.1.10.0        10.1.1.1          80000001     4
Table 2-465 Description of the display ospf retrans-queue command output
Item Description
Router ID

Router ID of the current route.
Retransmit list

Retransmission list.
Area

Area ID.
interface

IP address of the interface.
Neighbor ID

Neighbor ID.
Type

LSA type.
LinkState ID

Link state ID in the LSA header.
AdvRouter

Advertising router in the LSA header.
Sequence

Sequence number in the LSA header.
Age

Aging time in the LSA header.

display ospf router-id conflict

Function

The display ospf router-id conflict command displays information about router ID conflicts (if any).

Format

display ospf [ process-id ] router-id conflict

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

If router ID conflicts exist on the network and are not resolved automatically, route flapping may occur. To check information about router ID conflicts (if any), run the display ospf router-id conflict command. The command output helps with the check on incorrect configurations.

Precautions

  • The obtained router ID conflicts do not necessarily exist on the network.
  • The command displays information about the router ID conflicts only between two devices.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about router ID conflicts (if any).
<HUAWEI> system-view
[HUAWEI] display ospf router-id conflict
OSPF Process 2 with Router ID 2.2.2.2
                     Router ID conflict Information
                     ------------------------------

                            Area: 0.0.0.0

Conflict Router ID  : 10.10.10.10
Begin Time          : 2018-07-10 15:42:42+06:00 DST
End Time            : 2018-07-10 15:47:54+06:00 DST
Detect Result       : A router ID conflict may halt between two remote devices.
Lsa1                :
    IP Addr         : 3.3.3.3
    IP Addr         : 4.4.4.4
Lsa2                :
    IP Addr         : 192.168.1.1
    IP Addr         : --
Table 2-466 Description of the display ospf router-id conflict command output
Item Description
Conflict Router ID

Conflicting router ID.
Begin Time

Begin time of the conflict detection.
End Time

End time of the conflict detection.
Detect Result

Detection result.
Lsa1

Interface IP address in the LSA of one of the devices with the conflicting router ID.
IP Addr

Interface IP address of the device with the conflicting router ID.
Lsa2

Interface IP address in the LSA of the other device with the conflicting router ID.
Area

Area ID.

display ospf routing

Function

The display ospf routing command displays the OSPF routing table.

Format

display ospf [ process-id ] routing [ ip-address [ mask | mask-length ] ] [ [ interface { interface-name | interfaceType interfaceNum } ] [ nexthop nexthop-ip-address ] ] * [ age { min-value min-age-value | max-value max-age-value } * ]

Parameters

Parameter Description Value
process-id

OSPF process ID.

The value is an integer ranging from 1 to 4294967295.
ip-address

Specifies a destination IP address.

It is in dotted decimal notation.
mask

Specifies a subnet mask.

It is in dotted decimal notation.
mask-length

Specifies the length of the prefix.

The value is an integer ranging from 0 to 32.
interface interfaceType interfaceNum

Specifies the type or the number of an interface.

-
interface interface-name

Specifies an interface name.

The value is a character string.
nexthop nexthop-ip-address

Specifies a next-hop IP address.

The value is in dotted decimal notation.
age

Displays information based on the age time.

-
min-value min-age-value

Displays information about OSPF routes with the age value greater than or equal to the min-age-value value.

The value is an integer ranging from 0 to 4294967295.
max-value max-age-value

Displays information only about LSAs with the age value less than or equal to the max-age-value value.

The value is an integer ranging from 0 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view the OSPF routing table, run the display ospf routing command.

The command output can help you troubleshoot OSPF faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display the routes to a specified OSPF router.
<HUAWEI> display ospf routing router-id 10.1.1.1
OSPF Process 1 with Router ID 10.1.1.1

 Destination    : 10.1.1.2             Route Type          : Intra-area
 Area           : 0.0.0.1              AdvRouter           : 10.1.1.2
 Type           : ASBR                 Age                 : 00:00:33
 URT Cost       : 1
 NextHop        : 10.1.2.2             Interface           : 10GE1/0/1
 Backup NextHop : 10.1.3.3             Backup Interface    : 10GE1/0/8
 Backup Type    : LFA LINK

<HUAWEI> display ospf routing router-id 10.1.1.1
OSPF Process 1 with Router ID 10.1.1.1

 Destination    : 10.1.1.2             Route Type          : Intra-area
 Area           : 0.0.0.1              AdvRouter           : 10.1.1.2
 Type           : ASBR                 Age                 : 00:00:33
 URT Cost       : 1
 NextHop        : 10.1.2.2             Interface           : 100GE1/0/1
 Backup NextHop : 10.1.3.3             Backup Interface    : 100GE1/0/8
 Backup Type    : LFA LINK
# Display the routes to a specified destination address.
<HUAWEI> display ospf routing 10.1.1.1

OSPF Process 1 with Router ID 1.1.1.1

 Destination    : 10.1.1.0/24
 AdverRouter    : 10.1.1.1             Tag                 : 1
 Cost           : 1                    Type                : Type2
 NextHop        : 10.1.2.2             Interface           : 100GE1/0/1
 Priority       : High                 Age                 : 00h00m00s
 Backup NextHop : 10.1.3.3             Backup Interface    : 100GE1/0/1
 Backup Type    : LFA LINK

<HUAWEI> display ospf routing 10.1.1.1

OSPF Process 1 with Router ID 1.1.1.1

 Destination    : 10.1.1.0/24
 AdverRouter    : 10.1.1.1             Tag                 : 1
 Cost           : 1                    Type                : Type2
 NextHop        : 10.1.2.2             Interface           : 10GE1/0/1
 Priority       : High                 Age                 : 00h00m00s
 Backup NextHop : 10.1.3.3             Backup Interface    : 10GE1/0/1
 Backup Type    : LFA LINK
# Display the OSPF routing table.
<HUAWEI> display ospf routing

OSPF Process 1 with Router ID 4.4.4.4

 Routing for Network
 ------------------------------------------------------------------------------
 Destination        Cost      Type           Next-Hop         AdvRouter       Area
 172.16.1.0/24      1         Inter-area     192.168.2.1     2.2.2.2         0.0.0.2
                    4         Inter-area     192.168.2.3     2.2.2.2         0.0.0.2
 192.168.0.0/24     2         Inter-area     192.168.2.1     2.2.2.2         0.0.0.2
 
 Total Nets: 3
 Intra Area: 1  Inter Area: 2  ASE: 0  NSSA: 0
Table 2-467 Description of the display ospf routing command output
Item Description
Destination

Destination network.
AdverRouter

Advertiser.
Area

Area ID.
Cost

Cost to the destination address.
Type

Type of the destination network:

  • Inter-area: inter-area routes.
  • Stub: routes advertised through router LSAs. The routes correspond to the direct routes of non-broadcast and non-NBMA networks.
  • Transit: routes advertised through network-LSAs.
  • Direct: direct route.
NextHop

Next hop to the destination address.
Interface

Outbound interface of the route.
Priority

Priority of a route.

  • Critical: The convergence priority of OSPF routes is critical.
  • High: The convergence priority of OSPF routes is high.
  • Medium: The convergence priority of OSPF routes is medium.
  • Low: The convergence priority of OSPF routes is low.
Tag

Route Distinguisher.
AdvRouter

Advertiser.
Total Nets

Total number of networks in an area, between areas, in ASE areas, and in NSSAs.
Intra Area

Total number of intra-area networks (stub networks and transit networks).
Inter Area

Total number of inter-area networks.
Route Type

The type of Route.
Age

Time after the route was generated.
URT Cost

Cost of the route.
Backup NextHop

IP address of the next backup hop.
Backup Interface

Outbound interface of the next backup route.
Backup Type

Type of the backup next hop:

  • LFA LINK: OSPF LFA link protection.
  • LFA LINK-NODE: OSPF LFA link protection node.
ASE

Total number of networks in the ASE area.
NSSA

Total number of networks in the NSSA.

display ospf routing router-id

Function

The display ospf routing router-id command displays OSPF node information.

Format

display ospf [ process-id ] routing router-id [ router-id-value ] [ age { min-value min-age-value | max-value max-age-value } * ]

Parameters

Parameter Description Value
process-id

Specifies the OSPF process ID.

The value is an integer ranging from 1 to 4294967295.
router-id router-id-value

Specifies the router ID of a destination router.

The value is in dotted decimal notation.
age

Displays information based on the age time.

-
min-value min-age-value

Displays information about only LSAs with the age value greater than or equal to the min-age-value value.

The value is an integer ranging from 0 to 4294967295.
max-value max-age-value

Displays information only about LSAs with the age value less than or equal to the max-age-value value.

The value is an integer ranging from 0 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

You can view the route of a specified interface or next hop.

The command output helps you troubleshoot OSPF faults.

You can run the display ospf routing router-id command to query the next hop of a device.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display the routes to a specified OSPF device.
<HUAWEI> display ospf routing router-id 10.1.1.1
OSPF Process 1 with Router ID 10.1.1.1

 Destination    : 10.1.1.2             Route Type          : Intra-area
 Area           : 0.0.0.1              AdvRouter           : 10.1.1.2
 Type           : ASBR                 Age                 : 00:00:33
 URT Cost       : 1
 NextHop        : 10.1.2.2             Interface           : 10GE1/0/1
 Backup NextHop : 10.1.3.3             Backup Interface    : 10GE1/0/2
 Backup Type    : LFA LINK
Table 2-468 Description of the display ospf routing router-id command output
Item Description
Destination

Destination network.
Route Type

Route type.
Type

Node type.
Area

Area ID.
AdvRouter

Advertiser.
Age

Time after the route was generated.
URT Cost

Cost value.
NextHop

Next-hop address to the destination address.
Interface

Outbound interface of a route.
Backup NextHop

IP address of the next backup hop.
Backup Interface

Outbound interface of the next backup route.
Backup Type

Type of the backup next hop:

  • LFA LINK: OSPF LFA protection link.
  • LFA LINK-NODE: OSPF LFA link protection node.
  • REMOTE LFA LINK: OSPF remote LFA link protection node.
  • REMOTE LFA LINK-NODE: OSPF TI-LFA link protection node.
  • TI-LFA LINK-NODE: OSPF TI-LFA link protection node.

display ospf spf-statistics

Function

The display ospf spf-statistics command displays route calculation statistics in OSPF processes.

Format

display ospf [ process-id ] spf-statistics [ verbose ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no OSPF process ID is specified, this command displays brief information about route calculation statistics in all processes.

The value is an integer ranging from 1 to 4294967295.
verbose

Displays the detailed statistics.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display ospf spf-statistics command displays route calculation statistics in OSPF processes, including the time when route calculation occurs, cause of route calculation, and number of changed routes.

When identifying the cause of OSPF route flapping, you can run this command to obtain OSPF route calculation statistics, and then identify the cause according to the command output.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display detailed information about route calculation statistics in OSPF process 1.
<HUAWEI> display ospf 1 spf-statistics verbose
OSPF Process 1 with Router ID 2.2.2.2

Routing table change statistics:

Index: 1   This spf calculation is External increment calculation
           Time     : 2008-11-29,17:36:59
           Intra    : 0 Added,0 Deleted
           Inter    : 0 Added,0 Deleted
           External : 10 Added,0 Deleted
           The reason of calculation is:LSA
           NO.     Type          LS ID             Adv Router
           1       External      10.1.5.0          1.1.1.1
           2       External      10.1.3.0          1.1.1.1
           3       External      10.1.9.0          1.1.1.1
           4       External      10.1.4.0          1.1.1.1
           5       External      10.1.2.0          1.1.1.1
           6       External      10.1.8.0          1.1.1.1
           7       External      10.1.7.0          1.1.1.1
           8       External      10.1.6.0          1.1.1.1
           9       External      10.1.10.0         1.1.1.1
           10      External      10.1.1.0          1.1.1.1
# Display brief information about route calculation statistics in OSPF process 1.
<HUAWEI> display ospf 1 spf-statistics
OSPF Process 1 with Router ID 2.2.2.2

Routing table change statistics:

Date          Time            Intra       Inter    External    Reason
2008-08-14    10:17:16        17          17       17          LSA
2008-08-14    09:16:47        77          62       127         Other
2008-08-14    08:16:37        0           0        0           LSA
2008-08-14    07:04:40        24          230      108         LSA
2008-08-14    06:03:15        204         230      18          Other
2008-08-14    05:02:55        34          236      128         LSA
2008-08-14    04:01:49        54          130      158         LSA
2008-08-14    03:01:48        44          220      138         LSA
2008-08-14    02:01:43        22          233      158         LSA
2008-08-14    01:00:53        977         897      907         LSA
Table 2-469 Description of the display ospf spf-statistics command output
Item Description
Routing table change statistics

Statistics about routing table changes.
External

External route.
Time

Time when the route calculation was triggered.
Intra

Intra-area route.
Inter

Number of inter-area routes in the routing table which are changed because of route calculation.
The reason of calculation is

Possible causes of route calculation are as follows:

  • LSA: indicates that route calculation is triggered by LSAs.
  • Topo: The fault is caused by a topology change.
  • Other: indicates that the fault is caused by other reasons, for example, the configuration changes or the interface goes Down.
NO.

Sequence number of the LSA that causes route calculation, which ranges from 1 to 10.
Type

Type of the LSA that causes route calculation, including Router, Network, Sum-Net, External, and NSSA.
LS ID

Link state ID of the LSA that causes route calculation.
Adv Router

Router ID of the device that generates the LSA that causes route calculation.
Date

Date when route calculation occurs.
Reason

Possible causes of route calculation are as follows:

  • LSA: indicates that route calculation is triggered by LSAs.
  • Topo: The fault is caused by a topology change.
  • Other: indicates that the fault is caused by other reasons, for example, the configuration changes or the interface goes Down.
Index

Index of statistics.

display ospf statistics maxage-lsa

Function

The display ospf statistics maxage-lsa command displays information about router LSAs that have reached the aging time.

Format

display ospf [ process-id ] statistics maxage-lsa

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no process ID is specified, information about all OSPF processes is displayed.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To check information about router LSAs that have reached the aging time, run the display ospf statistics maxage-lsa command. The command output helps locate the cause of route flapping.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about router LSAs that have reached the aging time.
<HUAWEI> display ospf statistics maxage-lsa

          OSPF Process 1 with Router ID 1.1.1.1
                  Statistics of Router-LSAs
          ---------------------------------------------------

                          Area: 0.0.0.0
LinkState ID           MaxAge count        Last Five MaxAge Times
------------------------------------------------------------------
1.1.1.1                           1           2020-07-16 11:26:17
Table 2-470 Description of the display ospf statistics maxage-lsa command output
Item Description
LinkState ID

Link state ID in the LSA header.
MaxAge count

Number of times an LSA reached the aging time.
Last Five MaxAge Times

Time when the LSA reached the aging time for the last five times.
Area

Area whose LSDB information needs to be displayed.

display ospf statistics updated-lsa

Function

The display ospf statistics updated-lsa command displays the frequent updates of the LSAs that the LSDB receives.

Format

display ospf [ process-id ] statistics updated-lsa [ originate-router adv-rtr-id | history ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

If no OSPF process ID is specified, this command displays brief information about all processes.

The value is an integer ranging from 1 to 4294967295.
originate-router adv-rtr-id

Specifies the router ID of the advertising device.

The value is in dotted decimal notation.
history

Displays the update records of all the received LSAs in the LSDB.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display ospf statistics updated-lsa command is used to display the frequent updates of LSAs, facilitating routing flapping troubleshooting.

  • If the history parameter is not configured, the display ospf statistics updated-lsa command only displays the updates of LSAs within the latest hour.
  • If the history parameter is configured, the display ospf statistics updated-lsa command displays the change history of LSAs within the last 24 hours.

Precautions

  • If you run the reset ospf command to restart the OSPF process, the real-time and historical statistics on the process are cleared.
  • The display ospf statistics updated-lsa command is used only to display the frequent updates of LSAs. The updated LSAs are compared with the LSAs in the local LSDB, and those with the age greater than 900 (except those with the age of 3600) will not be displayed.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display the update records of LSAs.
<HUAWEI> display ospf statistics updated-lsa history
OSPF Process 1 with Router ID 1.1.1.1
          History Information for Received LSAs

 Record  1:
 Begin time: 11:39:32/2011/04/25
 End   time: 11:41:32/2011/04/25

 no Record

 Record  2:
 Begin time: 11:37:32/2011/04/25
 End   time: 11:39:32/2011/04/25

 AdvRouter      : 1.1.1.1           Total           : 18
 Router(1)      : 0                 Network(2)      : 0
 Summary-Net(3) : 0                 Summary-Asbr(4) : 18
 External(5)    : 0                 NSSA(7)         : 0
 Opaque-link(9) : 0                 Opaque-area(10) : 0
 Opaque-as(11)  : 0

 AdvRouter      : 2.2.2.2           Total           : 5
 Router(1)      : 3                 Network(2)      : 2
 Summary-Net(3) : 0                 Summary-Asbr(4) : 0
 External(5)    : 0                 NSSA(7)         : 0
 Opaque-link(9) : 0                 Opaque-area(10) : 0
 Opaque-as(11)  : 0

 AdvRouter      : 3.3.3.3           Total           : 5
 Router(1)      : 3                 Network(2)      : 2
 Summary-Net(3) : 0                 Summary-Asbr(4) : 0
 External(5)    : 0                 NSSA(7)         : 0
 Opaque-link(9) : 0                 Opaque-area(10) : 0
 Opaque-as(11)  : 0

 AdvRouter      : 4.4.4.4           Total           : 5
 Router(1)      : 2                 Network(2)      : 2
 Summary-Net(3) : 0                 Summary-Asbr(4) : 0
 External(5)    : 1                 NSSA(7)         : 0
 Opaque-link(9) : 0                 Opaque-area(10) : 0
 Opaque-as(11)  : 0
# Display the LSA updates of the specified advertising device.
<HUAWEI> display ospf statistics updated-lsa originate-router 1.1.1.1
OSPF Process 1 with Router ID 2.2.2.2
               Statistics of Received LSAs

 Begin time: 11:37:32/2011/04/25

 AdvRouter      : 1.1.1.1
 Total          : 6                 Updated at      : 11:37:41/2011/04/25
 Router(1)      : 3                 Network(2)      : 2
 Summary-Net(3) : 0                 Summary-Asbr(4) : 0
 External(5)    : 1                 NSSA(7)         : 0
 Opaque-link(9) : 0                 Opaque-area(10) : 0
 Opaque-as(11)  : 0
# Display the LSA updates within the last one hour.
<HUAWEI> display ospf statistics updated-lsa
OSPF Process 1 with Router ID 1.1.1.1
               Statistics of Received LSAs

 Begin time: 11:37:32/2011/04/25

 AdvRouter           Total        Updated at
 1.1.1.1             18           11:37:40/2011/04/25
 2.2.2.2             5            11:37:40/2011/04/25
 3.3.3.3             5            11:37:41/2011/04/25
 4.4.4.4             5            11:37:41/2011/04/25
 5.5.5.5             2            11:37:40/2011/04/25
 6.6.6.6             3            11:37:40/2011/04/25
 7.7.7.7             5            11:37:40/2011/04/25
 8.8.8.8             6            11:37:41/2011/04/25
Table 2-471 Description of the display ospf statistics updated-lsa command output
Item Description
Record

Record number.
Begin time

Start time of statistics collection.
End time

End time of statistic collection.
AdvRouter

Advertising Device.
Total

Total update times of LSAs.
Router(1)

Update times of Router LSAs.
Network(2)

Update times of Network LSAs.
Summary-Net(3)

Update times of Network Summary LSAs.
Summary-Asbr(4)

Update times of ASBR Summary LSAs.
External(5)

Update times of AS External LSAs.
NSSA(7)

Update times of Type 7 LSAs.
Opaque-link(9)

Update times of Type 9 LSAs.
Opaque-area(10)

Update times of Type 10 LSAs.
Opaque-as(11)

Update times of Type 11 LSAs.
Updated at

Latest update time.

display ospf topology

Function

The display ospf topology command displays information about the topology based on which OSPF routes are calculated.

Format

display ospf [ process-id ] topology [ area { area-id | area-ipv4 } ] [ statistics ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
area area-id

Specifies the ID of an OSPF area.

The value is an integer ranging from 0 to 4294967295.
area-ipv4

Specifies the ID of an OSPF area in IP address format.

The value is in the format of an IPv4 address.
statistics

Displays statistics about the topology based on which OSPF routes are calculated.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view information about the topology based on which OSPF routes are calculated, including the cause of route calculation, and the number of changed routes, run the display ospf topology command. The command output helps you diagnose OSPF route flapping.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display detailed information about the topology based on which OSPF routes are calculated.
<HUAWEI> display ospf topology
OSPF Process 1 with Router ID 10.9.9.9
 Bits :
 B - ABR    E - ASBR    V - VIRTUAL    NT - NSSA translator

 OSPF Area 0.0.0.0 topology
 Type  ID            Bits    Metric    Next-Hop        Interface
 Rtr   10.8.8.8      B       1         10.11.11.1      10GE1/0/8.1
 Rtr   10.9.9.9      E       1         -               -
 Net   10.11.11.1    B       1         10.11.11.2      10GE1/0/8.1

<HUAWEI> display ospf topology
OSPF Process 1 with Router ID 10.9.9.9
 Bits :
 B - ABR    E - ASBR    V - VIRTUAL    NT - NSSA translator

 OSPF Area 0.0.0.0 topology
 Type  ID            Bits    Metric    Next-Hop        Interface
 Rtr   10.8.8.8      B       1         10.11.11.1      100GE1/0/8.1
 Rtr   10.9.9.9      E       1         -               -
 Net   10.11.11.1    B       1         10.11.11.2      100GE1/0/8.1
Table 2-472 Description of the display ospf topology command output
Item Description
ID

Route advertiser.
Bits

Device type.
B - ABR

Area border router.
E - ASBR

Autonomous system boundary router.
V - VIRTUAL

Virtual link device.
NT - NSSA translator

ABR in an NSSA that translates LSAs.
Type

LSA type.
Metric

Cost of the route.
Next-Hop

Router ID of the next hop.
Interface

Interface of the next hop.

display ospf topology verbose

Function

The display ospf topology verbose command displays the SPF tree information depending on process and area for OSPFv2.

Format

display ospf [ process-id ] topology [ area { area-id | area-ipv4 } ] verbose

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
area area-id

Specifies the ID of an OSPF area.

The value is an integer ranging from 0 to 4294967295.
area-ipv4

Specifies the ID of an OSPF area in IP address format.

The value is in the format of an IPv4 address.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The display ospf topology command displays topology information about route calculation in an OSPF process, including the time when route calculation occurs, causes, and number of changed routes. To check the cause of OSPF route flapping, you can run this command to obtain information about OSPF route calculation and diagnose OSPF route flapping based on the information.

Prerequisites

To view information about the topology based on which OSPF routes are calculated, including the time when route calculation is performed, cause of route calculation, and the number of changed routes, run the display ospf topology command. The command output helps you diagnose OSPF route flapping.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display detailed information about the topology based on which OSPF routes are calculated.
<HUAWEI> display ospf topology verbose

          OSPF Process 1 with Router ID 1.1.1.1
Bits :
B - ABR    E - ASBR    V - VIRTUAL    NT - NSSA translator

Shortest Path Tree for Area: 0.0.0.0

Node: Router    1.1.1.1    Cost: 0 Cost(tunnel): 0
    BitFlags : B
    Neighbors: 1 (Children:(1) Parents:(0))
    Neighbor List:
        router  6.6.6.6, Child, cost: 100
Table 2-473 Description of the display ospf topology verbose command output
Item Description
Bits

Device type.
B - ABR

Area border router.
E - ASBR

Autonomous system boundary router.
V - VIRTUAL

Virtual link device.
NT - NSSA translator

ABR in an NSSA that translates LSAs.
Shortest Path Tree for Area

Display detailed information about the topology based on which OSPF routes are calculated in a specified area.
BitFlags

Device type.
Neighbor List

Neighbor router ID list.
cost

Cost of the route.
Neighbors

Neighbor quantity.
Node

Node Type.

display ospf troubleshooting

Function

The display ospf troubleshooting command displays information about OSPF neighbor disconnections.

Format

display ospf troubleshooting

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To check information about OSPF neighbor disconnections, run the display ospf troubleshooting command.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display diagnostic information about OSPF neighbor disconnections.
<HUAWEI> display ospf troubleshooting
Total counts: 2
--------------------------------------------------------------------------------
Sequence   Time                      Event Description                          
--------------------------------------------------------------------------------
 1         2015-11-25 09:28:18       The OSPF 1 peer 1.1.1.1 went Down because o
                                     f mismatched Hello timers. Please check the
                                      OSPF Hello timer configuration.(Interface 
                                     = 100GE1/0/1, PingResult = 5 packets suc
                                     cess, 0 packets timeout)
 2         2015-11-25 09:27:42       The OSPF 1 peer 1.1.1.1 went Down because 1
                                     -way Hello packets were received. Please ch
                                     eck the status of neighbor interface.(Inter
                                     face = 100GE1/0/1)
--------------------------------------------------------------------------------

<HUAWEI> display ospf troubleshooting
Total counts: 2
--------------------------------------------------------------------------------
Sequence   Time                      Event Description                          
--------------------------------------------------------------------------------
 1         2015-11-25 09:28:18       The OSPF 1 peer 1.1.1.1 went Down because o
                                     f mismatched Hello timers. Please check the
                                      OSPF Hello timer configuration.(Interface 
                                     = 10GE1/0/1, PingResult = 5 packets suc
                                     cess, 0 packets timeout)
 2         2015-11-25 09:27:42       The OSPF 1 peer 1.1.1.1 went Down because 1
                                     -way Hello packets were received. Please ch
                                     eck the status of neighbor interface.(Inter
                                     face = 10GE1/0/1)
--------------------------------------------------------------------------------
Table 2-474 Description of the display ospf troubleshooting command output
Item Description
Total counts

The count of OSPF neighbor disconnections.
Sequence

Sequence number.
Time

Time when the OSPF neighbor disconnection occurred.
Event Description

Description of the OSPF neighbor disconnection event.

display ospf vlink

Function

The display ospf vlink command displays OSPF virtual links.

Format

display ospf [ process-id ] vlink

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After OSPF areas are defined, OSPF route updates between non-backbone areas are transmitted through a backbone area. Therefore, OSPF requires that all non-backbone areas maintain the connectivity with the backbone area and the backbone areas in different OSPF areas maintain the connectivity with each other. In real world situations, this requirement may not be met because of some restrictions. To resolve this problem, you can configure OSPF virtual links.

The display ospf vlink command displays OSPF virtual link information, which can help you troubleshoot OSPF virtual link faults.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display OSPF virtual links.
<HUAWEI> display ospf vlink
OSPF Process 1 with Router ID 1.1.1.1
                  Virtual Links
 Virtual-link Neighbor-id  -> 2.2.2.2, Neighbor-State: Full
 Interface: 10.1.1.1 (10GE1/0/1)
 Cost: 1  State: P-2-P  Type: Virtual
 Transit Area: 0.0.0.1
 Timers: Hello 10 , Dead 40 , Retransmit 5 , Transmit Delay 1
 GR State: Normal
Table 2-475 Description of the display ospf vlink command output
Item Description
Virtual-link Neighbor-id

ID of the neighboring router that is connected through the virtual link.
Transit Area

Transit area ID if the current interface is a virtual link.
GR State

GR status:

  • Normal: indicates that no GR is performed.
  • Doing GR: indicates that the Router is performing GR.
  • Complete GR: indicates that the Router finishes GR.
  • Helper: indicates that the Router is Helper when the neighbor is performing GR.
Neighbor-State

Neighbor status, such as Down, Init, 2-Way, ExStart, Exchange, Loading, and Full.
Interface

Information about interfaces in the area is listed, including the IP address and name of the main interface. If the interface cannot be identified, Unknown is displayed.
Cost

Cost.
State

Interface state.
Type

Interface type.
Timers

Interval for sending Hello messages, Dead time, polling interval (NBMA), retransmission interval, and transmission delay on the interface.

dn-bit-check disable

Function

The dn-bit-check disable command disables OSPF from checking the DN bit in LSAs.

The undo dn-bit-check disable command enables OSPF to check the DN bit in LSAs.

The dn-bit-check disable command disables OSPFv3 from checking the DN bit in LSAs.

The undo dn-bit-check disable command enables OSPFv3 to check the DN bit in LSAs.

By default, OSPF is enabled to check the DN bit in LSAs.

By default, OSPFv3 is enabled to check the DN bit in LSAs.

Format

dn-bit-check disable { ase | nssa }

dn-bit-check disable summary [ router-id router-id ]

undo dn-bit-check disable { ase | nssa }

undo dn-bit-check disable summary [ router-id router-id ]

Parameters

Parameter Description Value
ase

Indicates that the DN bit in ASE LSAs is not checked.

-
nssa

Indicates that the DN bit in NSSA LSAs is not checked.

-
summary

Indicates that the DN bit in summary LSAs is not checked.

-
router-id router-id

Specifies the ID of the router that checks the DN bit in the summary LSA.

The value is in dotted decimal notation.

Views

OSPFv3 view, OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In the VPN option A scenario, the local PE imports BGP routes to generate LSAs and advertise the generated LSAs to the peer PE. According to standard protocols, setting of the DN bit is restricted. The peer PE may fail to calculate a route. In this situation, you need to use the dn-bit-check disable command to disable OSPF from checking the DN bit in LSAs.

To prevent routing loops, the OSPF multi-instance process uses a bit as a flag. The bit is called DN bit.

In a VPN Option A scenario, the local ASBR (ASBR1) imports BGP routes to generate LSAs, advertises the LSAs to the peer ASBR (ASBR2), and exchange OSPFv3 routes with ASBR2. According to the standard protocol, ASBR2 cannot calculate the BGP routes imported by ASBR1 due to the DN bit check mechanism, causing traffic loss. To disable ASBR2 from checking the DN bit in LSAs, run the

dn-bit-check disable command.

OSPFv3 multi-instance processes use a bit flag called the DN bit to prevent routing loops.

Prerequisites

  • A VPN instance has been created using the ip vpn-instance vpn-instance-name command and the VPN instance view is displayed.
  • The BGP-VPN instance IPv6 address family view has been enabled using the ipv6-family vpn-instance-name command in the VPN instance view.
  • The ospfv3[ process-id ] [ vpn-instance vpn-instance-name ] command has been run to enable an OSPFv3 multi-instance process and enter its view.

Configuration Impact

After the dn-bit-check disable command is run, routing loops may occur. If the parameter ase or nssa is specified, the DN bit in ASE LSAs or NSSA LSAs is not checked. You can use the route-tag command to set the same tag value to prevent routing loops. Therefore, run the dn-bit-check disable command only in the scenario specified in Usage Scenario.

After the dn-bit-check disable command is run to disable OSPFv3 from checking the DN bit in LSAs, routing loops may occur. If ase or nssa is configured, you can set the same VPN route tag for imported VPN routes using the route-tag command in the OSPFv3 view to prevent routing loops. You are advised to run the dn-bit-check disable command only in VPN Option A scenarios.

Precautions

The dn-bit-check disable command can be configured only for private OSPF processes. The configuration of this command takes effect only on PEs.

The dn-bit-set disable command disables OSPF from checking the DN bit in LSAs on the local PE.

Example

# Disable OSPF from checking the DN bit in summary LSAs.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv4-family
[HUAWEI-vpn-instance-huawei-af-ipv4] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospf 100 vpn-instance huawei
[HUAWEI-ospf-100] dn-bit-check disable summary router-id 1.1.1.1
# Disable OSPFv3 from checking the DN bit in Type 3 LSAs.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv6-family
[HUAWEI-vpn-instance-huawei-af-ipv6] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospfv3 100 vpn-instance huawei
[HUAWEI-ospfv3-100] dn-bit-check disable summary router-id 1.1.1.1

dn-bit-set disable

Function

The dn-bit-set disable command disables OSPF from setting the DN bit in LSAs.

The undo dn-bit-set disable command enables OSPF to set the DN bit in LSAs.

The dn-bit-set disable command disables OSPFv3 from setting the DN bit in LSAs.

The undo dn-bit-set disable command enables OSPFv3 to set the DN bit in LSAs.

By default, OSPF is enabled to set the DN bit in LSAs.

By default, OSPFv3 is enabled to set the DN bit in LSAs.

Format

dn-bit-set disable { summary | ase | nssa }

undo dn-bit-set disable { summary | ase | nssa }

Parameters

Parameter Description Value
summary

Sets the DN bit in Type 3 LSAs.

-
ase

Sets the DN bit in AS-external-LSAs.

-
nssa

Sets the DN bit in NSSA LSAs.

-

Views

OSPFv3 view, OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To prevent routing loops, the OSPF multi-instance process uses a bit as a flag. The bit is called DN bit. In the VPN option A scenario, the local PE imports BGP routes to generate LASs and advertise the generated LASs to the peer PE. According to standard protocols, setting of the DN bit is restricted. The peer PE may fail to calculate a route. In this situation, you can run the dn-bit-set disable command to disable OSPF from setting the DN bit in LSAs or run the undo dn-bit-set disable command to enable OSPF to set the DN bit in LSAs.

Prerequisites

  • A VPN instance has been created using the ip vpn-instance vpn-instance-name command and the VPN instance view is displayed.
  • The BGP-VPN instance IPv6 address family view has been enabled using the ipv6-family vpn-instance-name command in the VPN instance view.
  • The ospfv3[ process-id ] [ vpn-instance vpn-instance-name ] command has been run to enable an OSPFv3 multi-instance process and enter its view.

Configuration Impact

When the dn-bit-set disable command is used to disable OSPF from setting the DN bit in LSAs, routing loops may occur. If the parameter ase or nssa is specified, the DN bit in ASE LSAs or NSSA LSAs is not set. You can use the route-tag command to set the same tag value to prevent routing loops. Therefore, it is recommended that the dn-bit-set disable command be used in only the scenarios specified in Usage Scenario.

If the dn-bit-set disable ase command is configured, the DN bit is not set in type 5 LSAs that are translated from type 7 LSAs even if the DN bit is set in type 7 LSAs.

After the dn-bit-check disable command is run to disable OSPFv3 from checking the DN bit in LSAs, routing loops may occur. If ase or nssa is configured, you can set the same VPN route tag for imported VPN routes using the route-tag command in the OSPFv3 view to prevent routing loops. You are advised to run the dn-bit-set disable command only in VPN Option A scenarios.

Precautions

The dn-bit-set disable command can be configured for only private OSPF processes. The configuration of this command takes effect only on PEs.

The dn-bit-check disable command can be used to prevent OSPF running on the peer PE from checking the DN bit when calculating routes.

The dn-bit-set disable command can be run only in OSPFv3 VPN processes and takes effect only on PEs.

Example

# Disable OSPF from setting the DN bit in ASE LSAs.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv4-family
[HUAWEI-vpn-instance-huawei-af-ipv4] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospf 100 vpn-instance huawei
[HUAWEI-ospf-100] dn-bit-set disable ase
# Disable OSPFv3 from setting the DN bit in AS-external-LSAs.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv6-family
[HUAWEI-vpn-instance-huawei-af-ipv6] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospfv3 100 vpn-instance huawei
[HUAWEI-ospfv3-100] dn-bit-set disable ase

domain-id

Function

The domain-id command sets the ID for an OSPF domain.

The undo domain-id command restores the default setting.

By default, the domain ID is null.

Format

domain-id { null | { domain-idvalue | domain-idvalue_ipv4 } [ [ type { 0005 | 0105 | 0205 | 8005 } value domainTypeValue ] | secondary ] * }

undo domain-id [ { domain-idvalue | domain-idvalue_ipv4 } [ type { 0005 | 0105 | 0205 | 8005 } value domainTypeValue ] ]

Parameters

Parameter Description Value
null

Indicates that the OSPF domain ID is null.

-
domain-idvalue

Specifies the ID of an OSPF domain as an integer.

It is an integer, the value ranges from 0 to 4294967295. The value is converted to dotted decimal notation (with 256 as a carry) when the ID is displayed.
domain-idvalue_ipv4

Specifies the ID of an OSPF domain as an IP address.

It is in dotted decimal notation, it is displayed as entered.
type

Specifies the domain ID type.

-
0005

Specifies the type 0x0005.

-
0105

Specifies the type 0x0105.

-
0205

Specifies the type 0x0205.

-
8005

Specifies the type 0x8005.

-
value domainTypeValue

Specifies the value of the OSPF domain ID.

The value is a hexadecimal number ranging from 0 to FFFF, and the default value is 0.
secondary

Indicates the ID of a secondary domain.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Domain IDs are used to identify domains.

If the local OSPF area and an OSPF area of a remote VPN attempt to exchange Type 3 LSAs, the two areas must be in the same OSPF domain. You can run the domain-id command to configure the same domain ID for the two OSPF areas.

The routes that are imported from a PE Router are advertised using External-LSAs. The routes destined for different nodes in the same OSPF domain are advertised based on Type-3 LSAs. This requires that the nodes in the same OSPF domain be configured with the same domain ID.

OSPF direct routes to a PE do not carry the domain ID, whereas BGP direct routes to a PE do.

If the undo domain-id command with no parameter specified is executed, the primary domain ID will be deleted.

Configuration Impact

Before sending routes to a remote CE Router, a PE Router sends Type-3 LSAs or Type-5 LSAs to the CE based on domain ID. If local domain IDs are the same as or compatible with remote domain IDs in BGP routes, the PE advertises Type 3 routes. If local domain IDs are different from or incompatible with remote domain IDs in BGP routes, the PE advertises Type 5 routes.

Precautions

  • Each OSPF domain has one or multiple domain IDs. One of them is a primary ID, and the others are secondary IDs.
  • If an OSPF instance does not have a specific domain ID, its ID is considered as null.
  • If the value of the domain ID is 0, secondary cannot be configured.
  • The maximum number of domain-id secondary items configured in an OSPF process is 1000.
  • The domain-id command cannot be run on a public network.

Example

# Set the VPN domain ID in OSPF VPN extension.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance vpn1
[HUAWEI-vpn-instance-vpn1] ipv4-family
[HUAWEI-vpn-instance-vpn1-af-ipv4] quit
[HUAWEI-vpn-instance-vpn1] quit
[HUAWEI] ospf 1 vpn-instance vpn1
[HUAWEI-ospf-1] domain-id 234

eca-route-type compatible

Function

The eca-route-type compatible command sets the route type of the extended community attribute of OSPF VPN to 0x8000.

The undo eca-route-type compatible command restores the route type of the extended community attribute of OSPF VPN to 0x0306.

By default, the route type of the extended community attribute of OSPF VPN is 0x0306.

Format

eca-route-type compatible

undo eca-route-type compatible

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The eca-route-type compatible command is used in OSPF VPN scenarios.

  • For the device supporting standard protocol, you can set the route type of the extended community attribute of OSPF VPN to 0x0306 and configure the device to identify both 0x0306 and 0x8000 route types.
  • For the device that does not support standard protocol, you can set the route type of the extended community attribute of OSPF VPN to 0x8000 and configure the device to identify only the 0x8000 route type.

    By running the eca-route-type compatible command enables devices to communicate with each other and avoid the failure in parsing the route type because the route type of the extended community attribute of OSPF VPN is unrecognized.

Precautions

The eca-route-type compatible command cannot be run on the public network.

Example

# Set the route type of the extended community attribute of OSPF VPN to 0x8000.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv4-family
[HUAWEI-vpn-instance-huawei-af-ipv4] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospf 1 vpn-instance huawei
[HUAWEI-ospf-1] eca-route-type compatible

filter (OSPF area view)

Function

The filter export command filters the outgoing Type-3 LSAs of the local area.

The undo filter export command restores the default setting.

The filter import command filters incoming Type-3 LSAs of the local area.

The undo filter import command restores the default setting.

By default, outgoing Type-3 LSAs of the local area are not filtered.

By default, the incoming Type-3 LSAs are not filtered.

Format

filter { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export

filter { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } import [ include-abr-summary ]

filter acl-number export

filter acl-number import [ include-abr-summary ]

undo filter [ acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name | acl-number ] export

undo filter [ acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name | acl-number ] import

Parameters

Parameter Description Value
acl-name acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
ip-prefix ip-prefix-name

Specifies the name of an IP prefix list.

The value is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
route-policy route-policy-name

Specifies the name of a routing policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
include-abr-summary

Specifies a route-policy for the summarized route on the ABR.

-
acl-number

Specifies the basic ACL number.

The value is an integer ranging from 2000 to 2999.

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can run the filter export command to filter LSAs in an area to prevent useless LSAs from being sent to other areas. This reduces the size of the LSDB and speeds up network convergence.

You can run the filter import command to filter LSAs in an area to prevent unnecessary LSAs from being received from other areas. This reduces the size of the LSDB and speeds up network convergence.

Configuration Impact

After filtering conditions are set for the outgoing Type-3 LSAs to be advertised using the filter export command, only the outgoing Type-3 LSAs that match the filtering conditions can be advertised.

After filtering conditions are set for the incoming Type-3 LSAs using the filter import command, only the incoming Type-3 LSAs that match the filtering conditions can be accepted.

Precautions

  • This command can be configured only on ABRs.
  • To set filtering conditions for the incoming Type 3 LSAs in an area, run the filter import command in the area.
  • To set filtering conditions for the outgoing Type 3 LSAs in an area, run the filter export command in the area.

Example

# Configure OSPF to filter outgoing Type-3 LSAs.
<HUAWEI> system-view
[HUAWEI] ip ip-prefix prefix1 deny 1.1.1.1 24
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] filter ip-prefix prefix1 export
# Filter incoming Type-3 LSAs within the local area.
<HUAWEI> system-view
[HUAWEI] ip ip-prefix prefix1 deny 1.1.1.1 24
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 1
[HUAWEI-ospf-100-area-0.0.0.1] filter ip-prefix prefix1 import

filter-lsa-out peer

Function

The filter-lsa-out peer command configures a device to filter the LSAs to be sent to the specified neighbor on a P2MP network.

The undo filter-lsa-out peer command cancels the configuration.

By default, the LSAs that are to be sent to the specified neighbor on a P2MP network are not filtered.

Format

filter-lsa-out peer peer-addr { all | { ase [ acl { ase-acl-num | ase-acl-name } ] | nssa [ acl { nssa-acl-num | nssa-acl-name } ] | summary [ acl { sum-acl-num | sum-acl-name } ] } * }

undo filter-lsa-out peer peer-addr

Parameters

Parameter Description Value
peer-addr

Specifies the IP address of a P2MP neighbor.

The value is in dotted decimal notation.
all

Filters all the outgoing LSAs except Grace LSAs.

-
ase

Filters AS-external LSAs (Type-5 LSAs).

-
acl sum-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
acl sum-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
acl ase-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
acl ase-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
acl nssa-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
acl nssa-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
nssa

Filters outgoing NSSA LSAs (Type 7).

-
summary

Filters outgoing network summary LSAs (Type 3).

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a P2MP network, when multiple P2MP links exist between two devices, you can configure the local router to filter the outgoing LSAs on the specified link. This can reduce unnecessary LSA retransmission attempts and save bandwidth resources.

For a named ACL, configure filtering rules, only the source address range that is specified by the source parameter and the period of time that is specified by the time-range parameter take effect.

Prerequisites

The network type has been changed to P2MP using the ospf network-type p2mp command.

Precautions

Configure a router to filter the outgoing LSAs on the specified OSPF interface, run the ospf filter-lsa-out command.

After the filter-lsa-out peer command is run, the LSAs that other devices have received before will not be deleted immediately, but it will be deleted after a period of time (usually no more than one hour).

Example

# On a P2MP network, configure a device to filter all the LSAs (except Grace LSAs) sent to neighbor 10.1.1.1.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] filter-lsa-out peer 10.1.1.1 all

filter-policy export (OSPF view)

Function

The filter-policy export command filters imported routes to be advertised based on a filtering policy.

The undo filter-policy export command restores the default setting.

By default, the imported routes to be advertised are not filtered.

Format

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export direct

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export bgp

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export static

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export rip [ protocolID ]

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export isis [ protocolID ]

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export ospf [ protocolID ]

filter-policy acl-number export direct

filter-policy acl-number export bgp

filter-policy acl-number export static

filter-policy acl-number export rip [ protocolID ]

filter-policy acl-number export isis [ protocolID ]

filter-policy acl-number export ospf [ protocolID ]

filter-policy acl-number export

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export direct

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export bgp

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export static

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export rip [ protocolID ]

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export isis [ protocolID ]

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export ospf [ protocolID ]

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export

Parameters

Parameter Description Value
acl-name acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
ip-prefix ip-prefix-name

Specifies the name of an IP prefix list.

The value is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
route-policy route-policy-name

Specifies the name of a routing policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
direct

Filters direct routes.

-
bgp

Filters BGP routes.

This parameter is supported only by S6730-H-V2, S5732-H-V2, S5735I-S-V2, and S5735-S-V2 series.

-
static

Filters static routes.

-
rip

Filters RIP routes.

-
protocolID

Displays information about the ABR or ASBR of an OSPF route in a specified OSPF process.

The value is an integer ranging from 1 to 4294967295. The default value is 1.
isis

Filters IS-IS routes.

This parameter is supported only by S6730-H-V2, S5732-H-V2, S5735I-S-V2, and S5735-S-V2 series.

-
ospf

Filters OSPF routes.

-
acl-number

Specifies the basic ACL number.

The value is an integer ranging from 2000 to 2999.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After OSPF imports external routes using the import-route command, you can use the filter-policy export command to filter the imported routes to be advertised. Only the external routes that match the filtering rules can be translated into AS-external LSAs and advertised.

The or parameter can be specified to determine a specified protocol or process. If the or parameter is not specified, OSPF filters all imported routes.

Precautions

This command can be configured only on the ASBR because AS-external-LSAs are generated by an ASBR.

Example

# Configure OSPF to use a route-policy named poacl to filter imported routes when OSPF advertises them.
<HUAWEI> system-view
[HUAWEI] acl 2000
[HUAWEI-acl4-basic-2000] rule deny source 1.1.1.1 24
[HUAWEI-acl4-basic-2000] quit
[HUAWEI] route-policy poacl permit node 10
[HUAWEI-route-policy] if-match acl 2000
[HUAWEI-route-policy] quit
[HUAWEI] ospf 1
[HUAWEI-ospf-1] filter-policy route-policy poacl export
# Configure OSPF to use a filter policy to filter imported IS-IS routes when OSPF advertises them.
<HUAWEI> system-view
[HUAWEI] ip ip-prefix prefix1 deny 1.1.1.1 24
[HUAWEI] ospf 100
[HUAWEI-ospf-100] import-route isis
[HUAWEI-ospf-100] filter-policy ip-prefix prefix1 export

filter-policy import (OSPF view)

Function

The filter-policy import command configures a filtering policy to filter the routes received by OSPF.

The undo filter-policy import command restores the default setting.

By default, OSPF does not filter received routes.

Format

filter-policy acl-number import

filter-policy { acl-name acl-name | ip-prefix ip-prefix-name | { route-policy route-policy-name } [ secondary ] } import

undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | { route-policy route-policy-name } [ secondary ] ] import

Parameters

Parameter Description Value
acl-number

Specifies the basic ACL number.

The value is an integer ranging from 2000 to 2999.
acl-name acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
ip-prefix ip-prefix-name

Specifies the name of an IP prefix list.

The value is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
route-policy route-policy-name

Specifies the name of a routing policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
secondary

Indicates the suboptimal route.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can run the filter-policy import command to set a filtering policy for the received routes. Only the routes that pass the filtering are added to the routing information base (RIB) table and advertised. The routes that do not pass the filtering are not added to the RIB table or advertised. OSPF is a dynamic routing protocol based on the link state, and routing information is carried in the link-state database (LSDB). Therefore, the filter-policy import command cannot be used to filter the advertised and received LSAs. This command is used to filter the routes calculated by OSPF. Only the routes that pass the filtering are added to the RIB routing table.

Precautions

When the rule command is used to configure a filtering rule for a named ACL, only the source address range that is specified in source and the time period that is specified in time-range take effect on the filtering rule.

Example

# Configure OSPF to filter the received routes.
<HUAWEI> system-view
[HUAWEI] ip ip-prefix prefix1 deny 1.1.1.1 24
[HUAWEI] ospf 100
[HUAWEI-ospf-100] filter-policy ip-prefix prefix1 import

flooding-control

Function

The flooding-control command restricts the flooding of OSPF update LSAs.

The undo flooding-control command restores the default configuration.

By default, the flooding of update LSAs is not restricted.

Format

flooding-control [ number number-value | timer-interval timer-interval-value ] *

undo flooding-control [ number number-value | timer-interval timer-interval-value ] *

Parameters

Parameter Description Value
number number-value

Sets the maximum number of Update packets that can be sent at each interval during update LSA flooding.

The value is an integer ranging from 1 to 1000. The default value is 50.
timer-interval timer-interval-value

Sets the interval at which Update packets are sent during update LSA flooding.

The value is an integer ranging from 30 to 100000, in milliseconds. The default value is 30.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a local device has multiple neighbors or needs to flood a large number of update LSAs, an OSPF neighbor will receive a large number of Link State Update (LSU) packets within a short time. As a result, the established OSPF neighbor relationships may be terminated, because the neighbor may discard the Hello packets used to maintain neighbor relationships if it is busy processing the burst LSU packets. In this case, OSPF neighbors will exchange more packets to re-establish their neighbor relationships, exacerbating the problem of excessive packets.

To resolve the problem, run the flooding-control command on the local device to set the maximum number of Update packets that can be sent at each interval during update LSA flooding.

If the interval for sending Update packets during LSA flooding is less than 100 ms, LSAs are updated at the interval of 100 ms due to the timer limit.

Precautions

The parameter setting in this command directly affects the flooding speed. If the setting is improper, LSAs may fail to be synchronized in time, affecting network-wide routes. Therefore, you are not advised to use this function unless otherwise specified.

Example

# Set the number of Update packets to be sent during update LSA flooding to 100 and the interval for sending Update packets to 150 ms.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] flooding-control number 100 timer-interval 150

frr

Function

The frr command creates an OSPF FRR view and enters the OSPF FRR view.

The undo frr command exits from the OSPF FRR view and deletes the OSPF FRR view.

By default, no OSPF FRR view is created.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

frr

undo frr

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF IP FRR needs to be configured in the OSPF FRR view. To create an OSPF FRR view and enter the OSPF FRR view, run the frr command. To enable OSPF IP FRR, run the loop-free-alternate command so that a loop-free backup link can be generated.

Prerequisites

OSPF has been enabled using the ospf command.

Precautions

A link with the cost 65535 cannot participate in FRR path calculation.

Example

# Create an OSPF FRR view and enter the OSPF FRR view.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] frr

frr-policy route

Function

The frr-policy route command configures a filtering policy for OSPF/OSPFv3 IP FRR backup routes to control whether OSPF/OSPFv3 backup routes are added to the routing table.

The undo frr-policy route command disables the device from filtering backup routes for OSPF/OSPFv3 IP FRR.

By default, OSPF/OSPFv3 IP FRR-enabled backup routes are not filtered.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

frr-policy route { route-policy route-policy-name }

undo frr-policy route

Parameters

Parameter Description Value
route-policy route-policy-name

Specifies the name of an IP FRR filtering policy.

The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

OSPF FRR view, OSPFv3 FRR view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF/OSPFv3 IP FRR can rapidly switch traffic from a faulty link to a backup link, ensuring uninterrupted traffic transmission. OSPF/OSPFv3 IP FRR is a method to improve OSPF/OSPFv3 network reliability. After an OSPF/OSPFv3 IP FRR filtering policy is configured using the frr-policy route command, only the OSPF/OSPFv3 backup routes that meet the filtering conditions can be added to the forwarding table. If the primary link fails, OSPF/OSPFv3 can quickly switch traffic to the backup route.

Prerequisites

The system has entered the OSPFv3 IP FRR view using the frr command, and OSPFv3 IP FRR has been enabled using the loop-free-alternate command.

The system has entered the OSPF IP FRR view using the frr command, and OSPF IP FRR has been enabled using the loop-free-alternate command.

Precautions

If the command is run more than once, the last configuration overrides the previous one.

Example

# Configure OSPF IP FRR filtering policy abc.
<HUAWEI> system-view
[HUAWEI] route-policy abc permit node 10
[HUAWEI-route-policy] quit
[HUAWEI] ospf 1
[HUAWEI-ospf-1] frr
[HUAWEI-ospf-1-frr] loop-free-alternate
[HUAWEI-ospf-1-frr] frr-policy route route-policy abc
# Configure OSPFv3 IP FRR filtering policy abc.
<HUAWEI> system-view
[HUAWEI] route-policy abc permit node 10
[HUAWEI-route-policy] quit
[HUAWEI] ospfv3 1
[HUAWEI-ospfv3-1] frr
[HUAWEI-ospfv3-1-frr] loop-free-alternate
[HUAWEI-ospfv3-1-frr] frr-policy route route-policy abc

graceful-restart (OSPF view)

Function

The graceful-restart command configures a device as a GR helper.

The undo graceful-restart command cancels the configuration.

By default, the device does not function as a GR helper.

Format

graceful-restart [ helper-role { { { ip-prefix ip-prefix-name | acl-number acl-number | acl-name acl-name } | ignore-external-lsa | planned-only } * } ]

graceful-restart helper-role never

graceful-restart non-ietf

undo graceful-restart [ helper-role [ { { ip-prefix [ ip-prefix-name ] | acl-number [ acl-number ] | acl-name [ acl-name ] } | ignore-external-lsa | planned-only } * ] ]

undo graceful-restart helper-role never

undo graceful-restart non-ietf

Parameters

Parameter Description Value
helper-role

Indicates the GR Helper mode.

-
ip-prefix ip-prefix-name

Specifies the name of an IP prefix list.

The name is a string of 1 to 169 case-sensitive characters except spaces. When double quotation marks are used to include the string, spaces are allowed in the string.
acl-number acl-number

Specifies the basic ACL number.

The value is an integer ranging from 2000 to 2999.
acl-name acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 32 case-sensitive characters, spaces not supported.
ignore-external-lsa

Prevents the device from checking Type 5 and Type 7 LSAs.

-
planned-only

Indicates that the device supports only planned GR.

By default, the device supports both planned GR and unplanned GR.
never

Indicates that the router does not support the Helper mode.

-
non-ietf

Enables the non-IETF mode.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After an OSPF process is restarted through GR, the restarter and the helper reestablish the neighbor relationship, exchange routing information, synchronize LSDBs, and update routing tables and FIBs to ensure network stability.

Prerequisites

The Opaque-LSA capability has been enabled using the opaque-capability enable command.

Precautions

The graceful-restart non-ietf and graceful-restart [ helper-role { { { { ip-prefix | acl-number | acl-name } | ignore-external-lsa | planned-only } * } | never } ] commands are mutually exclusive.

If the GR restarter fails to complete GR within 1800s, the GR helper in non-IETF mode exits the helper mode.

In non-IETF mode, only broadcast interfaces can be simulated as P2P interfaces.

Example

# Configure a device as an OSPF GR helper and configure the helper to support only planned GR.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] opaque-capability enable
[HUAWEI-ospf-1] graceful-restart helper-role planned-only

hostname

Function

The hostname command enables the OSPF dynamic hostname function.

The undo hostname command disables the OSPF dynamic hostname function.

By default, the OSPF dynamic hostname function is disabled.

Format

hostname [ host-name ]

undo hostname

Parameters

Parameter Description Value
host-name

Specifies the OSPF hostname.

The value is a string of 1 to 255 characters.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To facilitate network planning, configure hostnames to identify devices. After you run the hostname command to configure a dynamic hostname for a router, a device configured with a dynamic hostname generates a Router Information (RI) Opaque LSA. You can view the mapping between the router ID and hostname of the device through the RI Opaque LSA.

The rules based on which RI Opaque LSAs are generated on ASBRs are as follows:

  • If the device is an ASBR:
  • If an ASBR is connected to an NSSA or a stub area, the ASBR generates and floods Type 10 RI Opaque LSAs (Type 10 RI LSAs) to the NSSA or stub area.
  • If an ASBR is connected to a common area (non-NSSA or non-stub area), the ASBR generates and floods AS RI LSAs (Type 11 RI LSAs).
  • If an ASBR is connected to an NSSA or a stub area but not to a common area, the ASBR does not generate AS-wide RI Opaque LSAs.
  • If the device is an ABR or an intra-area device, it floods RI Opaque LSAs to its connected area.

    After all devices flood RI Opaque LSAs, you can run the display ospf hostname-table command on the devices that learn RI Opaque LSAs to view the mapping between router IDs and hostnames.

Prerequisites

The Opaque LSA capability has been enabled using the opaque-capability enable command.

Precautions

If you specify in this command, is advertised as the dynamic hostname. If no is specified in this command, the hostname specified in the sysname command is advertised as the dynamic hostname.

Example

# Configure OSPF hostname BLR and enable the OSPF dynamic hostname function.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] opaque-capability enable
[HUAWEI-ospf-100] hostname BLR

ignore-receive-lsa advertise-router (OSPF view)

Function

The ignore-receive-lsa advertise-router command configures the device to discard LSAs of a specified type.

The undo ignore-receive-lsa advertise-router command cancels the configuration of discarding LSAs of a specified type.

By default, the device is not configured to discard LSAs of a specified type.

Format

ignore-receive-lsa advertise-router adv-rtr-id [ lsa-type type-value [ area { area-id | area-idipv4 } ] | link-state-id ls-id ] *

undo ignore-receive-lsa advertise-router adv-rtr-id [ lsa-type type-value [ area { area-id | area-idipv4 } ] | link-state-id ls-id ] *

Parameters

Parameter Description Value
adv-rtr-id

Specifies the router ID of the LSA advertising device.

The value is in dotted decimal notation.
lsa-type type-value

LSA type.

The value is in hexadecimal notation. The value ranges from 0 to ffff.
area area-id

Specifies the area ID in decimal format.

The value is a decimal integer ranging from 0 to 4294967295.
area-idipv4

Specifies an area ID in IP address format.

The value is in dotted decimal notation.
link-state-id ls-id

Specifies the LSID of an LSA.

The value is in dotted decimal notation.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

  1. When abnormal LSAs cause devices on the entire network to repeatedly restart and the LSA that causes protocol restarts is located, you can use this command as a last resort to prevent the devices from constantly restarting. However, incorrect configurations may cause loops.
  2. If an LSA is an attack packet, is not supposed to appear in the local area, and causes serious problems such as device restarts, but it does not affect topology path computation, and the attack source cannot be found temporarily, you can run this command to temporarily filter out the LSA.
  3. If an LSA is an attack packet, is not supposed to appear in the local area, causes serious problems such as restarts of network-wide devices, and affect topology path computation, you can run the command on all the devices on the network to configure them not to accept the LSA, preventing the LSA from participating in network-wide path computation.

    (Note: To filter out LSAs that affect topology path computation, they must be filtered out of all LSDBs on the entire network. If they are filtered out of only some of LSDBs, routing loops may occur.)
  4. If an LSA is an unreachable residual LSA, the device that advertised the LSA is never reachable, and the LSA does not affect topology path computation, you can configure the device to filter out the LSA after receiving it from a neighbor.

Configuration Impact

If this command is incorrectly configured, services cannot be restored even if the undo command is run. In this case, you may need to reset the process or neighbor to restore services.

To filter out the LSA that affects topology path computation, you must ensure that it is removed from all the LSDBs on the entire network. Otherwise, routing loops may occur.

This command is not recommended for LSAs that exist on the network because normal LSAs may be filtered out.

Precautions

  • This command is not used to defend against attacks. It violates the protocol processing principle and affects services. Therefore, exercise caution when running this command. If an attack source exists, you are advised to isolate the attack source. Attacked LSAs can have any key and cannot be defended by commands.
  • If the fault is caused by a bug, you are advised to run this command temporarily. After installing the patch, run the undo command immediately, and check whether services are affected. If services are affected, re-establish all neighbor relationships to restore services.

Example

# Discards LSAs advertised by 2.2.2.2.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] ignore-receive-lsa advertise-router 2.2.2.2
Warning: The operation will cause ospf lsdb not correct and can not recover ospf lsdb by undo command,need reset all neighbors to recover lsdb. Continue? [Y/N]:Y
[HUAWEI-ospf-100]

import-rib protocol ospf

Function

The import-rib protocol ospf command imports public network or other VPN instance routes to a VPN instance routing table.

The undo import-rib protocol ospf command restores the default configuration.

By default, public network or other VPN instance routes are not imported to VPN instance routing tables.

Format

import-rib vpn-instance vpn-instance-name protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

import-rib public protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

undo import-rib vpn-instance vpn-instance-name protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

undo import-rib public protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

Parameters

Parameter Description Value
ospf process-id

Imports OSPF routes from the specified process (process-id).

The value is an integer ranging from 1 to 4294967295.
valid-route

Imports valid routes of the corresponding route type.

-
route-policy route-policy-name

Specifies the name of a route-policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
vpn-instance vpn-instance-name

Specifies the name of a VPN instance.

The value is a string of 1 to 31 case-sensitive characters without spaces. The VPN instance name cannot be _public_. If the character string is quoted by double quotation marks, the character string can contain spaces.
public

Imports routes from the public network BGP routing table.

-

Views

VPN instance IPv4 address family view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In VPN networking, users in a VPN instance can communicate with users in another VPN instance only if the two VPN instances have matching VPN targets, but cannot communicate with public network users. To enable a VPN to communicate with the public network, you have to ensure that the VPN and public network users can obtain routes to each other. To import public network routes to a VPN instance, run the import-rib public command.

In VPN networking, users of a VPN instance can communicate with users of another VPN instance only if the two VPN instances have matching VPN targets. To enable users in different VPN instances to communicate with each other, ensure that users in different VPN instances can obtain routes from each other. To import routes from another VPN instance to a specified VPN instance, run the import-rib vpn-instance command.

In an intelligent traffic control scenario, traffic of different users are distributed to different VPNs. To enable the traffic to reach the public network, run the import-rib public command to import public network routes to each VPN instance routing table.

When VLAN tag termination sub-interfaces are used to import routes between VPN and public network instances, traffic forwarding depends on direct routes (Vlink direct routes) generated based on user entries. However, the direct routes imported between VPN and public network instances do not contain Vlink direct routes. As a result, traffic fails to be forwarded. To solve this problem, route import between VPN and public network instances newly supports import of Vlink direct routes.

Precautions

If you run the import-rib public command on a device without adding the valid-route keyword, the device will import all routes of the specified type from the public network instance's corresponding routing table to the specified VPN instance. If an imported route is preferred in this routing table, the device will advertise the route to other devices and deliver the route to the VPN instance's IP routing table to guide traffic forwarding.

If you run the import-rib public command with only the valid-route keyword added, the device will import the valid IP routes of the specified type from the public network instance's corresponding routing table to the specified VPN instance. If the imported routes are preferred in this routing table, the device will advertise these routes to other devices and deliver these routes to the VPN instance's IP routing table to guide traffic forwarding.

Example

# Configure the device to import valid public network OSPF routes to the VPN instance vrf1.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance vrf1
[HUAWEI-vpn-instance-vrf1] ipv4-family
[HUAWEI-vpn-instance-vrf1-af-ipv4] import-rib public protocol ospf 1 valid-route

import-rib vpn-instance protocol

Function

The ip import-rib vpn-instance protocol command imports routes in a VPN instance routing table to the public network routing table.

The undo ip import-rib vpn-instance protocol command restores the default configuration.

The ipv6 import-rib vpn-instance protocol command enables a device to import IPv6 routes from a VPN instance to the public network instance's IPv6 routing table.

The undo ipv6 import-rib vpn-instance protocol command disables a device from importing IPv6 routes from a VPN instance to the public network instance's IPv6 routing table.

By default, routes in VPN instance routing tables are not imported to the public network routing table.

By default, a device does not import IPv6 routes from a VPN instance to the public network instance's IPv6 routing table.

Format

ip import-rib vpn-instance vpn-instance-name protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

ipv6 import-rib vpn-instance vpn-instance-name protocol ospfv3 process-id [ valid-route ] [ route-policy route-policy-name ]

undo ip import-rib vpn-instance vpn-instance-name protocol ospf process-id [ valid-route ] [ route-policy route-policy-name ]

undo ipv6 import-rib vpn-instance vpn-instance-name protocol ospfv3 process-id [ valid-route ] [ route-policy route-policy-name ]

Parameters

Parameter Description Value
vpn-instance-name

Specifies a VPN instance name.

The value is a string of 1 to 31 case-sensitive characters, which do not contain spaces. The VPN instance name cannot be _public_. The character string can contain spaces if it is enclosed with double quotation marks (").
protocol

Specifies the type of routes to be imported.

-
ospf process-id

Imports OSPF routes from the specified process (process-id).

The value is an integer ranging from 1 to 4294967295.
valid-route

Imports only valid routes of a specified route type.

-
route-policy route-policy-name

Specifies the name of a route-policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
ospfv3 process-id

Imports OSPFv3 routes. process-id specifies the ID of an OSPFv3 process.

The value is an integer ranging from 1 to 4294967295.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In a VPN scenario, one VPN can communicate with another VPN if they have matching VPN targets, but VPNs cannot communicate with the public network. To enable a VPN to communicate with the public network, you have to ensure that the VPN and public network can obtain routes to each other. To import the VPN instance routes to public network, run the ip import-rib vpn-instance command.

In an intelligent traffic control scenario, traffic of different users are distributed to different VPNs. To enable public-network traffic to reach the VPNs, run the ip import-rib vpn-instance command to import routes in each VPN instance routing table to the public network routing table.

Traffic forwarding relies on direct routes (Vlink direct routes) generated based on user entries. When VLAN tag termination sub-interfaces are used for route import between VPN and public network, Vlink direct routes cannot be imported. As a result, traffic forwarding is interrupted. To solve this problem, route import between VPN and public network newly supports import of Vlink direct routes.

In an IPv6 VPN networking, IPv6 users of two VPNs with matching VPN targets can communicate, but IPv6 VPN users cannot communicate with IPv6 public network users. To enable IPv6 VPN users to communicate with IPv6 public network users, you must configure IPv6 route import between VPN and public network instances. To enable a device to import IPv6 routes from a VPN instance to the public network instance, run the ipv6 import-rib vpn-instance command.

Traffic forwarding relies on direct routes (Vlink direct routes) generated based on user entries. When VLAN tag termination sub-interfaces are used for route import between VPN and public network, Vlink direct routes cannot be imported. As a result, traffic forwarding is interrupted. To solve this problem, route import between VPN and public network newly supports import of Vlink direct routes.

Precautions

If you run the ip import-rib vpn-instance command on a device without adding the valid-route, the device will import the optimal IP route of the specified type from the specified VPN instance to the public network instance's corresponding routing table. If the imported route is preferred in this routing table, the device will advertise the route to other devices and deliver the route to the IP routing table to guide traffic forwarding.

If you run the ip import-rib vpn-instance command with only the valid-route keyword added, the device will import the valid IP routes of the specified type from the specified VPN instance to the public network instance's corresponding routing table. If the imported routes are preferred in this routing table, the device will advertise these routes to other devices and deliver these routes to the IP routing table to guide traffic forwarding.

If you run the ipv6 import-rib vpn-instance command on a device without adding the valid-route keyword, the device will import the optimal IPv6 route of the specified type from the specified VPN instance to the public network instance's corresponding routing table. If the imported route is preferred in this routing table, the device will advertise the route to other devices and deliver the route to the IPv6 routing table to guide traffic forwarding.

If you run the ipv6 import-rib vpn-instance command with only the valid-route keyword added, the device will import the valid IPv6 routes of the specified type from the specified VPN instance to the public network instance's corresponding routing table. If the imported routes are preferred in this routing table, the device will advertise these routes to other devices and deliver these routes to the IPv6 routing table to guide traffic forwarding.

Example

# Configure the device to import OSPF routes in the routing table of the VPN instance vrf1 to the public network routing table.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance vrf1
[HUAWEI-vpn-instance-vrf1] ipv4-family
[HUAWEI-vpn-instance-vrf1-af-ipv4] route-distinguisher 100:1
[HUAWEI-vpn-instance-vrf1-af-ipv4] vpn-target 111:1 both
[HUAWEI-vpn-instance-vrf1-af-ipv4] quit
[HUAWEI-vpn-instance-vrf1] quit
[HUAWEI] ip import-rib vpn-instance vrf1 protocol ospf 1 valid-route

import-route (OSPF view)

Function

The import-route command imports routes learned by other protocols.

The undo import-route command cancels the configuration.

By default, routes learned by other protocols are not imported.

Format

import-route { direct | static | bgp [ permit-ibgp ] } [ cost cost | { route-policy route-policy-name } | tag tag | type type ] *

import-route { ospf | isis | rip } [ process-id-rip ] [ cost cost | { route-policy route-policy-name } | tag tag | type type ] *

undo import-route { direct | static | bgp }

undo import-route { ospf | isis | rip } [ process-id-rip ]

Parameters

Parameter Description Value
direct

Imports direct routes.

-
static

Imports static routes.

After the parameter is specified, only active static routes can be imported.

-
bgp

Imports BGP routes.

For an OSPF process that is not bound to a VPN instance or is bound to a VPN instance but the vpn-instance-capability simple command is run, the parameter imports only EBGP routes.

-
permit-ibgp

Imports IBGP routes.

NOTICE:

For an OSPF process that is not bound to a VPN instance or is bound to a VPN instance but the vpn-instance-capability simple command is run, importing IBGP routes may cause routing loops. Therefore, exercise caution when using this parameter.

-
cost cost

Specifies a route cost.

The value is an integer ranging from 0 to 16777214. The default value is 1.
route-policy route-policy-name

Specifies the name of a routing policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
tag tag

Specifies the tag of an external LSA.

The value is an integer ranging from 0 to 4294967295. The default value is 1.
type type

Specifies the type of the external routes.

The value is 1 or 2.

  • 1: Type 1 external route
  • 2: Type 2 external route

The default value is 2.
ospf

Imports OSPF routes.

-
isis

Imports IS-IS routes.

-
rip

Imports RIP routes.

-
process-id-rip

Specifies the process ID of the protocol whose routes are imported.

The value is an integer ranging from 1 to 4294967295. The default value is 1.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Importing the routes discovered by other routing protocols can enrich OSPF routing information.

OSPF routes are classified into the following types in the descending order of priorities:

  • Intra-area routes: refer to the routes in an area within an AS.
  • Inter-area routes: refer to the routes between areas of the same AS. Intra-area routes and area external routes are internal routes of an AS.
  • Type 1 external routes: When the cost of external routes is almost the same as that of AS internal routes and can be compared with the cost of OSPF routes, these external routes have a high reliability and can be configured as Type 1 external routes.
  • Type 2 external routes: When the cost of the routes from an ASBR to the destination outside an AS is much greater than the cost of the internal routes to the ASBR, these external routes have a low reliability and can be configured as Type 2 external routes.

    For an OSPF process that is not bound to a VPN instance or is bound to a VPN instance but the vpn-instance-capability simple command is run, only EBGP routes are imported after the import-route bgp command is configured. IBGP routes are also imported after the import-route bgp permit-ibgp command is configured. If IBGP routes are imported, routing loops may occur. In this case, run the preference (OSPF) and preference (BGP) commands to prevent loops by specifying priorities of OSPF and BGP routes. If IBGP routes need to be imported, configure the import-route bgp permit-ibgp command, and run the preference (OSPF) and preference (BGP) commands to set the priority of OSPF ASE routes lower than that of IBGP routes (priority value of OSPF ASE routes larger than that of IBGP routes).

    For an OSPF process that is bound to a VPN instance and the vpn-instance-capability simple command is not run, configuring the import-route bgp command imports both EBGP routes and IBGP routes, no matter whether the import-route bgp permit-ibgp command is configured.

Prerequisites

A route-policy has been created using the route-policy command.

Procedure

The costs of a Type 1 external route and a Type 2 external route are as follows:

  • The cost of a Type 1 external route equals the cost for the OSPF device to reach an ASBR plus the cost of the route from the ASBR to the destination.
  • The cost of a Type 2 external route equals the cost of the route from an ASBR to the destination.

Implementation Procedure

The costs of a Type 1 external route and a Type 2 external route are as follows:

  • The cost of a Type 1 external route equals the cost for the OSPF device to reach an ASBR plus the cost of the route from the ASBR to the destination.
  • The cost of a Type 2 external route equals the cost of the route from an ASBR to the destination.

Configuration Impact

OSPF does not have a good mechanism to prevent loops of imported external routes. Therefore, exercise caution when configuring OSPF to import external routes to prevent loops caused by manual configurations. You are advised to specify a tag, route-filter, or route-policy when importing routes and configure the policy to inherit the cost mode.

After a policy for importing routes is configured using the route-policy parameter in the command, the OSPF process can import only the routes that meet the policy. This prevents the device from passively importing unnecessary routes.

Precautions

You can use the default (OSPF) command to configure default parameters for OSPF to import external routes, including the cost, type (Type 1 or Type 2), tag, and number of routes.

The import-route (OSPF) command cannot import the default route of an external protocol. To enable a router to advertise the default route of an external protocol it learns when updating the OSPF routing table to other routers within the area, run the default-route-advertise (OSPF) command.

Example

# Import Type 2 OSPF routes, with tag 33 and cost 50.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] import-route isis 1 type 2 tag 33 cost 50

import-route limit

Function

The import-route limit command configures a limit on the number of LSAs generated when an OSPF process imports external routes.

The undo import-route limit command deletes the limit configured on the number of LSAs generated when an OSPF process imports external routes.

The import-route limit command configures a limit on the number of LSAs generated when an OSPFv3 process imports external routes.

The undo import-route limit command deletes the limit configured on the number of LSAs generated when an OSPFv3 process imports external routes.

By default, OSPF does not limit the number of LSAs generated by imported external routes.

Format

import-route limit limit-number [ threshold-alarm { upper-limit upper-limit-value | lower-limit lower-limit-value } * ]

undo import-route limit [ limit-number ] [ threshold-alarm [ upper-limit upper-limit-value | lower-limit lower-limit-value ] * ]

Parameters

Parameter Description Value
limit-number

Specifies a limit on the number of LSAs generated when an OSPFv3 process imports external routes.

The value is an integer ranging from 1 to 4294967295.
threshold-alarm

Indicates an alarm threshold.

-
upper-limit upper-limit-value

Specifies the upper alarm threshold, in percentage.

The value is an integer ranging from 1 to 100. The default value is 80.
lower-limit lower-limit-value

Specifies the lower alarm threshold, in percentage.

The value is an integer ranging from 1 to 100. The default value is 70.

Views

OSPFv3 view, OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If OSPF imports a large number of external routes and advertises them to a device with a smaller routing table capacity, the device may restart unexpectedly. To address this problem, run the import-route limit command to configure a limit on the number of LSAs generated when an OSPF process imports external routes. Check the overload status based on the value of the Current status field in the display ospf brief command output.

  • Normal: The number of LSAs generated when an OSPF process imports external routes is less than or equal to the lower alarm threshold (in percentage) multiplied by the maximum number allowed.
  • Approach limit: The number of LSAs generated when an OSPF process imports external routes is approaching (reaching or exceeding 90% of) the upper alarm threshold.
  • Exceed limit: The number of LSAs generated when an OSPF process imports external routes has reached or exceeded the maximum number allowed.

    Ensure that upper-limit-value is greater than or equal to lower-limit-value.

    The system generates alarms based on the following rules:
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.7 hwOspfv2ImportAseRouteThreshold alarm if the number of ASE LSAs generated when an OSPF process imports external routes exceeds the upper alarm threshold (in percentage) multiplied by the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.8 hwOspfv2ImportAseRouteThresholdClear alarm if the number falls to or below the lower alarm threshold (in percentage) multiplied by the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.9 hwOspfv2ImportAseRouteExceed alarm if the number of ASE LSAs generated when an OSPF process imports external routes is greater than or equal to the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.10 hwOspfv2ImportAseRouteExceedClear alarm if the number of ASE LSAs generated when an OSPF process imports external routes falls below 90% of the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.11 hwOspfv2ImportNssaRouteThreshold alarm if the number of NSSA LSAs generated when an OSPF process imports external routes exceeds the upper alarm threshold (in percentage) multiplied by the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.12 hwOspfv2ImportNssaRouteThresholdClear alarm if the number falls to or below the lower alarm threshold (in percentage) multiplied by the maximum number allowed.
  • The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.13 hwOspfv2ImportNssaRouteExceed alarm if the number of NSSA LSAs generated when an OSPF process imports external routes is greater than or equal to the maximum number allowed.

    The system generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.14 hwOspfv2ImportNssaRouteExceedClear alarm if the number of NSSA LSAs generated when an OSPF process imports external routes falls below 90% of the maximum number allowed.

    If OSPFv3 imports a large number of external routes and advertises them to a device with a smaller routing table capacity, the device may restart unexpectedly. To address this problem, run the import-route limit command to configure a limit on the number of LSAs generated when an OSPFv3 process imports external routes.

    Ensure that upper-limit-value is greater than or equal to lower-limit-value.

    The system generates alarms based on the following rules:
  • The system generates the OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.19 hwOspfv3ImportAseRouteExceed alarm if the number of AS-external-LSAs generated when an OSPFv3 process imports external routes is greater than or equal to the maximum number allowed.
  • The system generates the OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.20 hwOspfv3ImportAseRouteExceedClear alarm if the number of AS-external-LSAs generated when an OSPFv3 process imports external routes falls below 90% of the maximum number allowed.
  • The system generates the OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.17 hwOspfv3ImportAseRouteThreshold alarm if the number of AS-external-LSAs generated when an OSPFv3 process imports external routes exceeds limit-number * upper-limit-value /100.
  • The system generates the OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.18 hwOspfv3ImportAseRouteThresholdClear alarm if the number falls to or below limit-number * lower-limit-value /100.

Example

# Set the limit on the number of LSAs generated when an OSPF process imports external routes, the upper alarm threshold, and lower alarm threshold to 3000, 85%, and 75%, respectively.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] import-route limit 3000 threshold-alarm upper-limit 85 lower-limit 75
# Set the limit on the number of LSAs generated when an OSPFv3 process imports external routes, the upper alarm threshold, and lower alarm threshold to 3000, 85%, and 75%, respectively.
<HUAWEI> system-view
[HUAWEI] ospfv3 100
[HUAWEI-ospfv3-100] import-route limit 3000 threshold-alarm upper-limit 85 lower-limit 75

loop-free-alternate

Function

The loop-free-alternate command enables OSPF/OSPFv3 IP FRR and generates a loop-free backup route.

The undo loop-free-alternate command disables OSPF/OSPFv3 IP FRR.

By default, FRR is disabled.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

loop-free-alternate

undo loop-free-alternate

Parameters

None

Views

OSPF FRR view, OSPFv3 FRR view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Loop-free alternate (LFA) is a method of implementing IP FRR. With LFA, a device can generate a loop-free backup link to implement basic IP FRR functions. OSPF IP FRR takes effect only after the loop-free-alternate command is run.

Prerequisites

An OSPF FRR view has been created and the system has entered the OSPF FRR view using the frr command.

An OSPFv3 FRR view has been created and the system has entered the OSPFv3 FRR view using the frr command.

Precautions

  • If a link that carries important services cannot function as the backup link of other links, run the ospf frr block command on the interface connected to the link before configuring OSPF IP FRR. In this way, OSPF IP FRR does not calculate the link connected to the interface as a backup link.
  • If a link that carries important services cannot function as a backup link for other links, run the ospfv3 frr block command on the interface connected to the link before configuring OSPFv3 IP FRR. In this way, OSPFv3 IP FRR does not calculate the link connected to the interface as a backup link.
  • If OSPF IP FRR is configured only for specified routes, run the frr-policy route route-policy route-policy-name command to configure a filtering policy for OSPF IP FRR. Only the backup OSPF routes that meet the filtering conditions can be added to the forwarding table. When this route fails, OSPF can quickly switch traffic to the backup route.
  • This command takes effect regardless of whether the same route is advertised by multiple nodes.

Example

# Enable OSPF IP FRR through LFA.
<HUAWEI> system-view
[HUAWEI] ospf
[HUAWEI-ospf-1] frr
[HUAWEI-ospf-1-frr] loop-free-alternate
# Enable OSPFv3 IP FRR through LFA.
<HUAWEI> system-view
[HUAWEI] ospfv3
[HUAWEI-ospfv3-1] frr
[HUAWEI-ospfv3-1-frr] loop-free-alternate

lsa-age refresh disable

Function

The lsa-age refresh disable command disables OSPF LSA aging management.

The undo lsa-age refresh disable command enables OSPF LSA aging management.

By default, OSPF LSA aging management is enabled.

Format

lsa-age refresh disable

undo lsa-age refresh disable

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an exception occurs in the age field of LSAs, LSAs may be aged unexpectedly, causing LSA flapping or a route calculation error. For example, if the abnormal aging time is 2500s and the actual aging time is 500s, LSAs are aged prematurely. To address this problem, OSPF LSA aging management is enabled by default. If the aging time in a received LSA is greater than 1800s, OSPF considers the LSA abnormal and changes the aging time to 1700s until the aging time values of all LSAs in the area become the same. In this case, routes can be calculated correctly.

Example

# Disable OSPF LSA aging management.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] lsa-age refresh disable

lsa-arrival-interval (OSPF view)

Function

The lsa-arrival-interval command sets the interval at which LSAs are received.

The undo lsa-arrival-interval command restores the default configuration.

By default, the intelligent timer is enabled. The maximum interval at which LSAs are updated is 1000 milliseconds (ms), the initial interval is 500 ms, and the Holdtime interval is 500 ms.

Format

lsa-arrival-interval interval

lsa-arrival-interval intelligent-timer max-interval start-interval hold-interval

undo lsa-arrival-interval

Parameters

Parameter Description Value
interval

Specifies the interval at which LSAs are received.

The value is an integer ranging from 0 to 10000, in ms.
intelligent-timer

Enables an intelligent timer to receive LSAs.

-
max-interval

Specifies the maximum interval at which LSAs are received.

The value ranges from 1 to 300000, in milliseconds.
start-interval

Specifies the initial interval at which LSAs are received.

The value ranges from 0 to 60000, in milliseconds.
hold-interval

Specifies the Holdtime interval at which LSAs are received.

The value is an integer ranging from 1 to 60000, in milliseconds.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF defines that the interval at which LSAs are received is 1s, which prevents network connections or frequent route flapping from consuming excessive network bandwidth or device resources.

On a stable network that requires fast route convergence, you can change the interval at which LSAs are received to 0s. In this manner, the device can fast respond to topology or route changes, which speeds up route convergence.

On an unstable network, routes are calculated frequently, which consumes a great number of CPU resources. In addition, LSPs that describe the unstable topology are generated and transmitted on the unstable network. Frequently processing such LSAs affects the rapid and stable operation of the entire network. You can configure an intelligent timer so that the device can dynamically adjust the interval according to the user configuration and the frequency of triggering events (such as route calculation) to speed up network convergence.

If there is no special network requirement, default values are recommended.

Implementation Procedure

After the intelligent timer is enabled:

  • The initial interval for receiving LSAs is specified by the parameter start-interval.
  • The interval for receiving LSAs for the nth (n≥2) time is equal to hold-interval x 2^(n-2).
  • When the interval specified by hold-interval x 2^(n-2) reaches the maximum interval specified by max-interval, OSPF receives LSAs at the maximum interval for three consecutive times. Then, the mechanism goes back to Step 1, and OSPF receives LSAs at the initial interval specified by start-interval.

Precautions

Setting the interval in the lsa-arrival-interval command to be a value less than or equal to the Holdtime interval specified in the lsa-originate-interval command is recommended.

Example

# Set the interval at which LSAs are received to 0 milliseconds.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] lsa-arrival-interval 0

lsa-arrival-interval suppress-flapping

Function

The lsa-arrival-interval suppress-flapping command configures a suppression period in case received OSPF LSAs flap.

The undo lsa-arrival-interval suppress-flapping command restores the default suppression period.

By default, the suppression period is 10s, and the suppression threshold is 30.

Format

lsa-arrival-interval suppress-flapping suppress-interval [ threshold threshold ]

undo lsa-arrival-interval suppress-flapping

Parameters

Parameter Description Value
suppress-interval

Specifies the suppression period that takes effect when received OSPF LSAs flap.

The value is an integer ranging from 0 to 600, in seconds. The default value is 10s.
threshold threshold

Specifies the suppression threshold that takes effect when received OSPF LSAs flap.

The value is an integer ranging from 3 to 100. The default value is 30.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If no flapping occurs among received OSPF LSAs, the configuration of the lsa-arrival-interval command prevents the device from frequently receiving LSAs. If received OSPF LSAs flap, the configuration of the lsa-arrival-interval suppress-flapping command minimizes the impact of the flapping on services. The larger value of the two intervals specified in the commands is used as the suppression period.

The suppression mechanism takes effect based on the following rules:

  • Flapping detection: OSPF starts a flapping counter. If the interval between two OSPF LSAs that are received successively is less than or equal to 10s, OSPF records a flapping event and increases the flapping_count by 1.
  • Suppression phase: If the flapping_count is greater than or equal to suppression threshold, flapping suppression takes effect.
  • Suppression exit: If the interval between two OSPF LSAs that are received successively is greater than 10s, OSPF resets the flapping_count and exits from suppression.

Example

# Set the suppression period that takes effect when received OSPF LSAs flap to 200s.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] lsa-arrival-interval suppress-flapping 200

lsa-originate-interval

Function

The lsa-originate-interval command sets the interval at which LSAs are updated.

The undo lsa-originate-interval command restores the default configuration.

By default, the intelligent timer is enabled; the maximum interval at which LSAs are updated is 5000 ms, the initial interval is 500 ms, and the Holdtime interval is 1000 ms.For Type-3,Type-4 and Type-10 LSAs, the default interval is 5s.

Format

lsa-originate-interval { 0 | intelligent-timer max-interval start-interval hold-interval [ other-type interval ] | other-type interval [ intelligent-timer max-interval start-interval hold-interval ] }

undo lsa-originate-interval

Parameters

Parameter Description Value
0

Sets the interval at which LSAs are updated to 0 ms, that is, deletes the initial interval (5s) for updating LSAs.

-
intelligent-timer

Sets the intelligent timer to update OSPF Type-1 LSA (Router LSA) , Type-2 LSA (Network LSA).

-
max-interval

Specifies the maximum interval at which LSAs are updated.

The value ranges from 1 to 300000, in milliseconds.
start-interval

Specifies the initial interval at which LSAs are updated.

The value ranges from 0 to 60000, in milliseconds.
hold-interval

Specifies the Holdtime interval at which LSAs are updated.

The value is an integer ranging from 1 to 60000, in milliseconds.
other-type interval

Sets the interval to update OSPF Type-3 LSA (Network-summary-LSA), Type-4 LSA (ASBR-summary-LSA) and Type-10 LSA (Opaque LSA).

The value is an integer ranging from 0 to 10, in seconds. The default value is 5.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF sets a 5-second update interval for LSAs. This prevents network connections or frequent route flapping from consuming excessive network bandwidth or device resources. On a stable network that requires fast route convergence, you can alter the interval to 0 seconds. In this manner, LSAs indicating topology or route changes can be advertised immediately, which speeds up route convergence. When the network is unstable, route calculation may be performed frequently, which consumes a large number of CPU resources. In addition, LSAs that describe the unstable topology are generated and transmitted on the unstable network. Frequently processing such LSAs affects the rapid and stable operation of the entire network. You can configure an intelligent timer so that the device can dynamically adjust the interval based on the user configuration and the frequency of triggering events (such as route calculation) to quickly stabilize the network.

If there is no special requirement for the network, using the default value is recommended.

Due to the timer restriction, when the configured interval is less than 100 ms, the interval is updated based on 100 ms.

Implementation Procedure

The interval for updating LSAs is as follows:

  1. The initial interval for updating LSAs is specified by start-interval.
  2. The interval for updating LSAs for the nth (n≥2) time is equal to hold-interval x 2^(n-2).
  3. When the interval specified by hold-interval x 2^(n-2) reaches the maximum interval specified by max-interval, OSPF updates LSAs at the maximum interval for three consecutive times. Then, OSPF goes back to Step 1 to update LSAs at the initial interval specified by start-interval.

Precautions

Setting the interval in the lsa-originate-interval command to be a value greater than or equal to the Holdtime interval specified in the lsa-arrival-interval command is recommended.

Example

# Set the interval at which LSAs are updated to 0 milliseconds.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] lsa-originate-interval 0

lsa-originate-interval suppress-flapping

Function

The lsa-originate-interval suppress-flapping command configures a suppression period in case the OSPF LSAs to be sent flap.

The undo lsa-originate-interval suppress-flapping command restores the default suppression period.

By default, the suppression period is 10s, and the suppression threshold is 30.

Format

lsa-originate-interval suppress-flapping interval [ threshold threshold ]

undo lsa-originate-interval suppress-flapping

Parameters

Parameter Description Value
interval

Specifies the suppression period that takes effect when the OSPF LSAs to be sent flap.

The value is an integer ranging from 0 to 600, in seconds. The default value is 10s.
threshold threshold

Specifies the suppression threshold that takes effect when the OSPF LSAs to be sent flap.

The value is an integer ranging from 3 to 100. The default value is 30.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If no flapping occurs among the OSPF LSAs to be sent, the configuration of the lsa-originate-interval command prevents the device from frequently sending LSAs. If the OSPF LSAs to be sent flap, the configuration of the lsa-originate-interval suppress-flapping command minimizes the impact of the flapping on services. The larger value of the two intervals specified in the commands is used as the suppression period.

The suppression mechanism takes effect based on the following rules:

  • Flapping detection: OSPF starts a flapping counter. If the interval between two OSPF LSAs that are sent successively is less than or equal to 10s, OSPF records a flapping event and increases the flapping_count by 1.
  • Suppression phase: If the flapping_count is greater than or equal to threshold, flapping suppression takes effect.
  • Suppression exit: If the interval between two OSPF LSAs that are sent successively is greater than 10s, OSPF resets the flapping_count and exits from suppression.

Example

# Set the suppression period that takes effect when the OSPF LSAs to be sent flap to 200s.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] lsa-originate-interval suppress-flapping 200

lsdb-overflow-limit

Function

The lsdb-overflow-limit command configures a maximum number of external routes supported by the OSPF LSDB.

The undo lsdb-overflow-limit command deletes the configured maximum number of external routes supported by the OSPF LSDB.

By default, the maximum number of external routes supported by the OSPF LSDB is not set.

Format

lsdb-overflow-limit number

undo lsdb-overflow-limit [ number ]

Parameters

Parameter Description Value
number

Specifies the maximum number of external routes supported by the OSPF LSDB.

The value is an integer ranging from 1 to 1000000.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If OSPF incorrectly imports a large number of external routes on a network, the device may fail to process the routes due to resource limitations.

To address this problem, run the lsdb-overflow-limit command to set the maximum number of external routes in the OSPF LSDB. If the number of external routes imported by OSPF exceeds the maximum number allowed by the LSDB, the device deletes the non-default external routes generated by itself and maintains normal forwarding of other external routes imported by OSPF.

The OSPF is in LSDB overflow status field in the display ospf brief command output indicates that the current OSPF process is in the overload state. OSPF LSDB is approaching overflow limit: indicates that the number of external routes in the OSPF LSDB reaches 90% of the maximum number.

Alarms about the number of external routes in the OSPF LSDB are described as follows:

  • When the number of external routes in the OSPF LSDB reaches 90% of the maximum number, the device generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.15 hwOspfv2LsdbApproachingOverflow alarm.
  • When the preceding alarm is cleared, the device generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.16 hwOspfv2LsdbApproachingOverflowClear alarm. When the number of external routes in the OSPF LSDB exceeds the maximum number, the device generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.17 hwOspfv2LsdbOverflow alarm.

    When the number of external routes in the OSPF LSDB falls below the maximum number, the device generates the OSPF_1.3.6.1.4.1.2011.5.25.155.31.18 hwOspfv2LsdbOverflowClear alarm.

Example

# Set the maximum number of external routes supported by the OSPF LSDB to 400000.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] lsdb-overflow-limit 400000

maxage-lsa route-calculate-delay

Function

The maxage-lsa route-calculate-delay command configures the route calculation delay function to suppress frequent OSPF LSA flapping.

The undo maxage-lsa route-calculate-delay command disables the function.

By default, route calculation is delayed in case of frequent OSPF LSA flapping.

Format

maxage-lsa route-calculate-delay delay-interval

undo maxage-lsa route-calculate-delay

Parameters

Parameter Description Value
delay-interval

Specifies a route calculation delay.

The value is an integer ranging from 0 to 65535, in seconds. The default value is 20 seconds.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Frequent OSPF LSA flapping on the remote device may lead to route flapping on the local device, affecting services. To address this problem, run the maxage-lsa route-calculate-delay command to configure the local device to delay route calculation in the case of frequent OSPF LSA flapping, which suppresses route flapping locally.

Example

# Set the route calculation delay to suppress frequent OSPF LSA flapping to 200s.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] maxage-lsa route-calculate-delay 200

maximum load-balancing (OSPF view)

Function

The maximum load-balancing command sets the maximum number of equal-cost routes for carrying out load balancing.

The undo maximum load-balancing command restores the default setting.

By default, the maximum number of equal-cost routes supported by OSPF is 128.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

maximum load-balancing number

undo maximum load-balancing

Parameters

Parameter Description Value
number

Specifies the maximum number of equal-cost routes.

The value is an integer that ranges from 1 to 128.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If multiple routes with the same cost to the same destination are available, they can carry out load balancing. The maximum load-balancing command sets the maximum number of equal-cost routes for carrying out load balancing. This optimizes route selection rules and meet traffic forwarding requirements on a complex network.

Configuration Impact

Packets will be load-balanced by multiple equal-cost routes to one destination.

Load balancing is performed either per-destination or per-packet. By default, packets are load-balanced per-destination.

The undo maximum load-balancing command restores the default equal-cost routes that are discovered by OSPF for load balancing.

Follow-up Procedure

If the number of equal-cost routes on the network is greater than the value specified using the maximum load-balancing command and you need to specify valid routes for load balancing, run the nexthop ip-address weight value command to set weights for the routes to increase the priority of the valid routes to be specified.

Precautions

To disable load balancing, set the value of number to 1.

Example

# Restore the default maximum number of equal-cost routes for load balancing.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] undo maximum load-balancing
# Set the maximum number of the equal-cost routes.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] maximum load-balancing 2

network (OSPF area view)

Function

The network command specifies the interface that runs OSPF and the area to which the interface belongs.

The undo network command disables OSPF from an interface.

By default, the interface does not belong to any area.

Format

network address wildcard-mask

network address wildcard-mask description text

undo network address wildcard-mask

Parameters

Parameter Description Value
address

Specifies the address of a network segment where an interface resides.

The value is in dotted decimal notation.
wildcard-mask

Specifies the wildcard mask of an IP address, which is similar to the reversed form of an IP address mask. "1" represents that the corresponding bit in the IP address is ignored, and "0" represents that this bit must be reserved.

The value is in dotted decimal notation.
description text

Specifies the description of an OSPF network segment.

The value is a string of 1 to 80 case-sensitive characters, spaces not supported.

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can configure one or more interfaces in an area by using the address and wildcard-mask parameters.

OSPF can run on an interface only when the following conditions are met:

  • The mask length of the IP address of the interface is greater than or equal to the mask length specified in the network (OSPF) command.
  • The primary IP address of the interface must be in the range of the network segment specified by the network (OSPF) command. Otherwise, the interface does not run OSPF even if the secondary IP address of the interface is in the range of the network segment specified by the network (OSPF) command.

    When wildcard-mask in the network command is all 0s and the IP address of the interface is the same as the IP address configured in the network address command, the interface also runs OSPF.

Precautions

  • For the same network address wildcard-mask, the last description specified by description takes effect.
  • For the loopback interface, by default, OSPF advertises its IP address through 32-bit host routes, which is irrelevant to the mask length of the IP address on the interface.
  • To advertise the network segment route of a loopback interface, run the ospf network-type command to configure the network type as broadcast or NBMA.
  • If a large number of interfaces that do not need to run OSPF services borrow the IP address of a loopback interface, running the ospf enable command rather than the network command on the loopback interface is recommended. If the network command is run on the loopback interface, the configurations of some commands, such as the command used to configure, delete, or modify the loopback interface's IP address or the undo network command, may fail to be delivered, and device performance is affected after a master/slave main control board switchover is performed.

Example

# Specify the primary IP address of the interface that runs OSPF to be in the network segment of 192.168.1.0/24, and the ID of the OSPF area where the interface resides to 2. In addition, specify the description for the network segment.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 2
[HUAWEI-ospf-100-area-0.0.0.2] network 192.168.1.0 0.0.0.255 description this network is connected to Beijing

nexthop weight (OSPF view)

Function

The nexthop weight command sets a priority for equal-cost routes. After OSPF calculates the equal-cost routes, the next hop is chosen from these equal-cost routes based on the priority value. The smaller the value, the higher the priority.

The undo nexthop command cancels the priority of equal-cost routes.

By default, the value of weight-value is 255, and equal-cost routes load balance traffic.

Format

nexthop ip-address weight value

undo nexthop ip-address

Parameters

Parameter Description Value
ip-address

Specifies the IP address of the next hop.

The value is in dotted decimal notation.
value

Specifies a priority for the next hop. The smaller the value, the higher the priority.

The value is an integer that ranges from 1 to 254.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the number of equal-cost routes on the network is greater than the value specified using the maximum load-balancing command and you need to specify valid routes for load balancing, run the nexthop weight command to set a higher priority for the valid routes to be specified.

Example

# Set the priority of equal-cost routes in OSPF.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] nexthop 10.0.0.3 weight 1

nssa (OSPF area view)

Function

The nssa command configures an NSSA.

The undo nssa command cancels the configuration of an NSSA.

By default, an OSPF area is not configured as an NSSA.

Format

nssa [ { default-route-advertise [ backbone-peer-ignore ] } | no-import-route | no-summary | set-n-bit | suppress-forwarding-address | translator-always | translator-interval interval-value | zero-address-forwarding ] *

undo nssa

Parameters

Parameter Description Value
default-route-advertise

Configure the ABR or ASBR to generate default Type 7 LSAs and advertise them to the NSSA.

-
backbone-peer-ignore

Prevents the ABR from checking the neighbor status when the ABR generates default Type 7 LSAs and advertises them to the NSSA. Specifically, the ABR generates default Type 7 LSAs and advertises them to the NSSA as long as an interface that is Up exist in the backbone area.

-
no-import-route

Indicates that no external route is imported to an NSSA.

-
no-summary

Indicates that an ABR is prevented from sending summary LSAs to the NSSA.

-
set-n-bit

Sets the N-bit in DD packets.

-
suppress-forwarding-address

Sets the forwarding address (FA) of the Type 5 LSA translated by the NSSA ABR to 0.0.0.0.

-
translator-always

Indicates an ABR in an NSSA as an all-the-time translator. Multiple ABRs in an NSSA can be configured as translators.

-
translator-interval interval-value

Specifies the timeout period of a translator.

The value is an integer ranging from 1 to 120, in seconds. The default value is 40.
zero-address-forwarding

Sets the FA of the generated NSSA LSAs to 0.0.0.0 when external routes are imported by the ABR in an NSSA.

-

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An NSSA is configured in the scenario where AS external routes are to be imported but not forwarded to save system resources. AS external routes can be imported to an NSSA and transmitted to the entire NSSA.

All devices in an NSSA must be configured with NSSA attributes using the nssa command. Parameters of the nssa command are used as follows:

  • Default Type 7 LSAs are generated and advertised to an NSSA when the following conditions are met:
  1. Neighbors in the Full state and interfaces in the Up state must exist in the backbone area.
  2. The default-route-advertise parameter is configured.
  3. The route 0.0.0.0 exists in the local routing table. (If the vpn-instance-capability simple command is configured for a private network, the default-route-advertise command must be configured, and a default route exists in the local routing table.)
  4. The OSPF process is bound to a VPN instance.

    If condition 1 or 4 is met, the ABR can generate default Type 7 LSAs and advertise them to the NSSA. If conditions 2 and 3 are met, the ASBR can generate default Type 7 LSAs and advertise them to the NSSA.
  • If an ASBR also functions as an ABR, set the no-import-route parameter to prevent external routes imported using the import-route command from being advertised to the NSSA.
  • To reduce the number of LSAs that are transmitted to the NSSA, set the parameter no-summary on an ABR. This prevents the ABR from transmitting Type 3 LSAs to the NSSA.

    After the nssa default-route-advertise backbone-peer-ignore no-summary command is run, the ABR generates default Type 7 and Type 3 LSAs as long as an interface that is Up exists in the backbone area. The default Type 3 LSAs preferentially take effect.
  • After set-n-bit is configured, the N-bit is set in the DD packets during the synchronization between the local and neighboring devices.
  • If multiple ABRs are deployed in an NSSA, the system automatically selects an ABR (generally the with the largest router ID) as a translator to translate Type 7 LSAs into Type 5 LSAs. You can also configure translator-always on an ABR to specify the ABR as a translator. If you configure translator-always on two ABRs, they both function as translators and implement load balancing. If a fixed translator is required to prevent LSA flooding caused by translator changes, you can run this command to specify a fixed translator in advance.
  • The translator-interval parameter is used to ensure a smooth translator switchover. The value of translator-interval must be greater than the flooding period.

Configuration Impact

Configuring or deleting NSSA attributes may trigger routing updates in the area. A second configuration of NSSA attributes can be implemented or canceled only after a routing update is complete.

Precautions

Set a loopback address for the Router in the NSSA so that the loopback address can be automatically selected as the FA. If other Routers have routes of the same cost to the Router in the NSSA, load balancing is performed.

When the last ordinary area (other than a stub area or NSSA) in an OSPF process is deleted, useless Type 5 LSAs originated by the local Router in the area will be deleted immediately. The local Router still reserves useless Type 5 LSAs received from other Routers. These useless Type 5 LSAs will not be deleted until the aging time reaches 3600s.

Example

# Configure area 1 as an NSSA.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] nssa

opaque-capability enable

Function

The opaque-capability enable command enables the opaque LSA capability.

The undo opaque-capability command disables the opaque LSA capability.

By default, the opaque LSA capability is disabled.

Format

opaque-capability enable

undo opaque-capability

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Opaque LSAs provide a generic mechanism for OSPF extension:

  • OSPF supports OSPF GR through Type 9 LSAs.
  • OSPF supports OSPF loop detection for the imported routes through Type 11 LSAs.

    Before configuring OSPF GR or loop detection for the imported routes, enable the opaque LSA capability using the opaque-capability enable command.

Configuration Impact

Enabling or disabling the opaque LSA capability may delete and re-establish all sessions and instances.

Example

# Enable OSPF opaque LSA capability.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] opaque-capability enable

ospf

Function

The ospf command creates and runs an OSPF process.

The undo ospf command terminates an OSPF process.

By default, OSPF is disabled, that is, no OSPF process runs.

Format

ospf process-id [ router-id route-id | vpn-instance vpname ] *

ospf [ router-id route-id | vpn-instance vpname ] *

undo ospf process-id

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295. The default value is 1.
router-id route-id

Specifies a router ID.

The value is in dotted decimal notation.
vpn-instance vpname

Specifies the name of a VPN instance.

The value is a string of 1 to 31 case-sensitive characters.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Creating an OSPF process is a prerequisite for configuring OSPF-related parameters.

OSPF supports multi-process. Multiple OSPF processes can run on the same device, which are independent of each other. Route exchange between different OSPF processes is similar to route exchange between different routing protocols.

The device ID can be manually configured. If no device ID is specified using a command, OSPF uses the system ID or interface IP address as the device ID.

The router ID is re-selected in the following situations:

  • This command is used to reconfigure an OSPF router ID.
  • The router ID of the system is reconfigured, and the OSPF process is restarted.
  • The system ID or IP address that was originally elected as the system router ID is deleted, and the OSPF process is restarted.

If the device is restarted in DB mode, the router ID saved in the DB table before the restart is used. If the device is restarted in CFG mode and the router id command is not configured on the device, the router ID of the interface that completes configuration restoration the earliest is used as the router ID after the restart.

Description:

To improve network stability, you are advised to manually configure a router ID.

Configuration Impact

After an OSPF process is disabled using undo ospf command, the receive end still maintains the LSAs generated by this OSPF process. These invalid LSAs occupy system memory and are not deleted until the LSA age field (aging time) reaches 3600 seconds.

Precautions

An interface on a device belongs to only one OSPF process.

If a VPN instance is specified, the OSPF process specified in this command belongs to this VPN instance. If no VPN instance is specified, the OSPF process specified in this command belongs to the global VPN instance. vpn-instance-name cannot be changed after being specified.

Setting a unique router ID for each process on a device is recommended. If an incorrect operation or planning causes a router ID conflict between processes, route flapping occurs.

Running the undo ospf process-id command will also delete all configurations from the OSPF view. Therefore, exercise caution when running this command.

Example

# Run an OSPF process.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv4-family
[HUAWEI-vpn-instance-huawei-af-ipv4] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospf 100 router-id 10.10.10.1 vpn-instance huawei

ospf authentication-mode

Function

The ospf authentication-mode command sets the authentication mode and password used between neighboring nodes.

The ospf authentication-mode null command configures the null authentication mode on an interface.

The undo ospf authentication-mode command deletes the authentication mode from an interface.

By default, an interface does not authenticate OSPF packets.

Format

ospf authentication-mode simple [ plain plain-text | [ cipher ] cipher-text ]

ospf authentication-mode { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ]

ospf authentication-mode null

ospf authentication-mode keychain keychain-name

undo ospf authentication-mode

Parameters

Parameter Description Value
plain

Indicates the cleartext authentication.

When configuring an authentication password, select the ciphertext mode because the password is saved in configuration files in cleartext if you select cleartext mode, which has a high risk. To ensure device security, change the password periodically.

By default, cipher takes effect for simple authentication.
plain-text

Specifies a plaintext password.

The value is a string of characters.

  • When simple is configured, plain-text is a string of 1 to 8 characters.
  • When md5, hmac-md5 or hmac-sha256 is configured, plain-text is a string of 1 to 255 characters.

A password cannot contain a question mark (?), but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
cipher

Indicates the cipher mode.

In MD5/HMAC-MD5 authentication mode, if this parameter is not specified, the password is in cipher text by default.
cipher-text

Specifies a ciphertext.

The value is a string of characters.

  • In simple mode, a simple password is a string of 1 to 8 characters, and a ciphertext password is a string of 24 to 128 characters.
  • In md5, hmac-md5 or hmac-sha256 mode, if the value is a string of 1 to 255 characters, the password is a plaintext; if the value is a string of 20 to 432 characters, the password is a ciphertext password.

The value cannot contain question marks (?) or spaces. However, when double quotation marks are used around the password, spaces are allowed in the password. In this case, the double quotation marks are used as a part of the password.
simple

Sets the simple authentication mode.

By default, the cipher type is used in simple authentication.

  • The length of a simple password ranges from 1 to 8 characters.
  • A ciphertext password is a string of 24 to 128 characters.
  • To prevent high security risks, you are advised to select the ciphertext mode. To ensure device security, change the password periodically.

-
md5

Indicates MD5 authentication.

For the sake of security, using the HMAC-SHA256 algorithm rather than the MD5 algorithm is recommended.

Because $@$@ is used to distinguish old and new passwords in an upgrade, an MD5 authentication password must not start and end with $@$@.
hmac-md5

Indicates HMAC-MD5 authentication.

For the sake of security, using the HMAC-SHA256 algorithm rather than the HMAC-MD5 algorithm is recommended.

-
hmac-sha256

Indicates HMAC SHA256 ciphertext authentication.

-
key-id

This object indicates the key ID for ciphertext authentication on an interface. The key ID must be the same as that on the peer end.

The value is an integer ranging from 1 to 255.
null

Indicates null authentication.

-
keychain

Configures keychain authentication.

Before configuring keychain authentication, run the keychain command to create a keychain, the key-id command to configure a key ID, the key-string command to configure a password, and the algorithm command to configure an algorithm. Otherwise, OSPF authentication fails.

Currently, OSPF supports MD5, SHA-1, SHA-256, SM3, HMAC-MD5, HMAC-SHA1-12, HMAC-SHA1-20, HMAC-SHA256, HMAC-SHA384, and HMAC-SHA512 algorithms.

If the dependent keychain is deleted, the neighbor relationship may be interrupted. Therefore, exercise caution when deleting the keychain.

To ensure high security, using the HMAC-SHA256 algorithm instead of the SHA-1 and MD5 algorithms is recommended.

-
keychain-name

Specifies the name of a keychain.

The value is a string of 1 to 47 case-insensitive characters.

The value cannot contain question marks (?) and spaces However, when double quotation marks are used around the password, spaces are allowed in the password. In this case, the double quotation marks at both ends of the password are used as a part of the password.

Views

100GE interface view, 10GE sub-interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE sub-interface view, GE electrical interface view, Loopback interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Due to inherent defects and flawed implementation of the TCP/IP protocol suite, there are an increasing number of attacks, which poses greater threats on TCP/IP networks than ever before. The attacks on network devices may lead to network failures. To configure an authentication mode and a password for an OSPF interface to improve OSPF network security, run the ospf authentication-mode command.

Configuration Impact

Interface authentication is used to set authentication mode and password used between neighboring devices. It takes precedence over area authentication. If both interface authentication and area authentication are configured, the authentication succeeds as long as the interface authentication succeeds. If authentication is configured on an interface, OSPFv3 neighbor relationships can be established on the interface as long as interface authentication succeeds, regardless of the area authentication configuration or whether area authentication is configured.

Precautions

Null indicates an authentication mode, which does not mean that no authentication is configured.

Interfaces on the same network segment must be configured with the same authentication mode and password.

For security purposes, md5 and hmac-md5 are not recommended. If they must be used, run the install feature-software WEAKEA command to install the weak security algorithm/protocol feature package WEAKEA first.

Example

# Set the authentication mode and password used between neighboring nodes.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf authentication-mode hmac-sha256 1 cipher YsHsjx_202206

ospf authentication-mode multi-area

Function

The ospf authentication-mode multi-area command configures an authentication mode for a multi-area adjacency interface.

The ospf authentication-mode multi-area null command configures null authentication for a multi-area adjacency interface.

The undo ospf authentication-mode multi-area command deletes the authentication mode configured for a multi-area adjacency interface.

By default, a multi-area adjacency interface does not authenticate OSPF packets.

Format

ospf authentication-mode simple [ plain plain-text | [ cipher ] cipher-text ] multi-area { area-id | area-id-ipv4 }

ospf authentication-mode { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ] multi-area { area-id | area-id-ipv4 }

ospf authentication-mode null multi-area { area-id | area-id-ipv4 }

ospf authentication-mode keychain keychain-name multi-area { area-id | area-id-ipv4 }

undo ospf authentication-mode multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
plain

Indicates the cleartext authentication.

When configuring an authentication password, select the ciphertext mode because the password is saved in configuration files in cleartext if you select cleartext mode, which has a high risk. To ensure device security, change the password periodically.

By default, cipher takes effect for simple authentication.
plain-text

Specifies a pliantext password.

The value is a string of characters.

  • In simple mode, the value is a string of 1 to 8 characters.
  • In md5, hmac-md5, or hmac-sha256 mode, the value is a string of 1 to 255 characters.

A password cannot contain a question mark (?), but can contain spaces if surrounded by double quotation marks (""). In this case, the double quotation marks are part of the password.
cipher

Indicates the cipher mode.

In MD5/HMAC-MD5 authentication mode, if this parameter is not specified, the password is in cipher text by default.
cipher-text

Specifies a ciphertext.

The value is a string of characters.

  • In simple mode, a simple password is a string of 1 to 8 characters, and a ciphertext password is a string of 24 to 128 characters.
  • In md5, hmac-md5 or hmac-sha256 mode, if the value is a string of 1 to 255 characters, the password is a plaintext; if the value is a string of 20 to 432 characters, the password is a ciphertext password.

The value cannot contain question marks (?) or spaces. However, when double quotation marks are used around the password, spaces are allowed in the password. In this case, the double quotation marks are used as a part of the password.
area-id

Specifies the ID of an OSPF area.

The value can be a decimal integer or an IP address. If the value is an integer, it ranges from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255
md5

Indicates MD5 authentication.

Configuring HMAC-SHA256 rather than MD5 is recommended for the sake of security.

Because $@$@ is used to distinguish old and new passwords in an upgrade, an MD5 authentication password must not start and end with $@$@.
hmac-md5

Indicates HMAC-MD5 authentication.

onfiguring HMAC-SHA256 rather than HMAC-MD5 is recommended for the sake of security.

-
hmac-sha256

Indicates HMAC SHA256 ciphertext authentication.

-
key-id

This object indicates the key ID for ciphertext authentication on an interface. The key ID must be the same as that on the peer end.

The value is an integer ranging from 1 to 255.
null

Indicates null authentication.

-
keychain

Specifies the keychain authentication mode.

Before configuring this parameter, run the keychain command to create a keychain, and run the key-id, key-string, and algorithm commands to configure a key ID, a password, and an authentication algorithm for the keychain. Otherwise, OSPF authentication fails.

Currently, OSPF supports the MD5, SHA-1, SHA-256, SM3, HMAC-MD5, HMAC-SHA1-12, HMAC-SHA1-20, HMAC-SHA256, HMAC-SHA384, and HMAC-SHA512 algorithms.

-
keychain-name

Specifies the name of a keychain.

The value is a string of 1 to 47 case-insensitive characters.

The value cannot contain question marks (?) and spaces However, when double quotation marks are used around the password, spaces are allowed in the password. In this case, the double quotation marks at both ends of the password are used as a part of the password.
simple

Sets the simple authentication mode.

To prevent high security risks, you are advised to select the ciphertext mode. To ensure device security, change the password periodically.
  • The length of a simple password ranges from 1 to 8.
  • A ciphertext password is a string of 24 to 128 characters.

By default, the simple authentication mode is cipher.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Due to inherent defects and flawed implementation of the TCP/IP protocol suite, there are an increasing number of attacks, which poses greater threats on TCP/IP networks than ever before. The attacks on network devices may lead to network failures. To configure an authentication mode and a password for an OSPF interface to improve OSPF network security, run the ospf authentication-mode command.

Prerequisites

Run the ospf enable multi-area command first.

Configuration Impact

Interface authentication is used to set authentication mode and password used between neighboring devices. It takes precedence over area authentication.

Precautions

Null indicates an authentication mode, which does not mean that no authentication is configured.

Interfaces on the same network segment must be configured with the same authentication mode and password.

For security purposes, md5 and hmac-md5 are not recommended. If they must be used, run the install feature-software WEAKEA command to install the weak security algorithm/protocol feature package WEAKEA first.

Example

# Configure HMAC-SHA256 authentication on a specified interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf authentication-mode hmac-sha256 1 cipher YsHsjx_202206 multi-area 1

ospf bfd

Function

The ospf bfd command enables bidirectional forwarding detection (BFD) on an OSPF interface, or sets parameter values for a BFD session.

The undo ospf bfd command disables BFD from an interface, or restores the default parameter values of a BFD session.

By default, BFD is not enabled in the OSPF interface view.

Format

ospf bfd { min-tx-interval transmit-interval | min-rx-interval receive-interval | detect-multiplier multiplier-value | frr-binding } *

undo ospf bfd { min-tx-interval [ transmit-interval ] | min-rx-interval [ receive-interval ] | detect-multiplier [ multiplier-value ] | frr-binding } *

Parameters

Parameter Description Value
min-tx-interval transmit-interval

Specifies the minimum interval at which BFD packets are sent to the remote device.

The value is an integer ranging from 3 to 1000, in milliseconds.
min-rx-interval receive-interval

Specifies the minimum interval for receiving BFD messages from the peer.

The value is an integer ranging from 3 to 1000, in milliseconds.
detect-multiplier multiplier-value

Specifies the local detect multiplier.

The value is an integer ranging from 3 to 50. The default value is 3.
frr-binding

Binds the BFD session state to the link state.

This parameter is supported only by S6730-H-V2, S5732-H-V2, S5735I-S-V2, and S5735-S-V2 series.

-

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A link fault or topology change on a network causes route recalculation in an area. Shortening the convergence time of routing protocols is important to improve network performance.

Link faults cannot be completely avoided. Therefore, it is feasible to speed up fault detection and notify routing protocols of the faults. BFD is associated with routing protocols. Once a link fails, BFD can speed up the convergence of routing protocols.

When OSPF IP FRR is configured, the lower layer must be able to quickly respond to link changes so that traffic can be quickly switched to the backup link. After frr-binding is configured, the BFD session status is bound to the link status of the interface. When BFD detects a link fault on an interface, the BFD session goes Down and triggers FRR to switch traffic from the faulty link to the backup link.

Prerequisites

BFD has been enabled on the interface.

Implementation Procedure

The receive-interval is negotiated by the local and peer ends by comparing the values of the local min-rx-interval and the peer min-tx-interval. If the local end fails to receive a BFD packet from the peer end within an interval of receive-interval * multiplier-value, the local end considers the peer end Down.

Configuration Impact

If global BFD is not enabled, you can enable BFD on an interface, but BFD sessions cannot be set up in this case. Similarly, if only parameters of a BFD session are set but the ospf bfd enable command is not used, the BFD session cannot be set up.

BFD configured on an interface takes precedence over BFD configured for a process. If BFD is enabled on an interface, the BFD parameters on the interface are used to establish BFD sessions.

Precautions

  • After BFD is enabled, BFD sessions can be created only between the two ends that have set up an OSPF neighbor relationship and the relationship is in the Full state.
  • The ospf bfd enable command and ospf bfd block command are mutually exclusive in function, and the later configuration overwrites the previous one.
  • After BFD is disabled from an interface using the undo ospf bfd enable command, the parameters for setting up BFD sessions remain.

Example

# Enable BFD on vlanif100 and set the minimum receiving interval to 400 ms and local detection multiplier to 4.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf bfd enable
[HUAWEI-Vlanif100] ospf bfd min-rx-interval 400 detect-multiplier 4

ospf bfd (interface view)

Function

The ospf bfd enable command enables BFD on an OSPF interface.

The undo ospf bfd enable command disables BFD from an interface.

The ospf bfd incr-cost command enables an OSPF interface to adjust the cost based on BFD.

The undo ospf bfd incr-cost command disables an OSPF interface from adjusting the cost based on BFD.

The ospf bfd incr-cost block command blocks an OSPF interface from adjusting the cost based on BFD.

The undo ospf bfd incr-cost block command unblocks an OSPF interface from adjusting the cost based on BFD.

By default, BFD is not enabled in the OSPF interface view.

By default, an OSPF interface does not adjust the cost based on BFD.

By default, an OSPF interface is not blocked from adjusting the cost based on BFD.

Format

ospf bfd enable

ospf bfd incr-cost { cost | max-reachable }

ospf bfd incr-cost block

undo ospf bfd incr-cost [ cost | max-reachable ]

undo ospf bfd incr-cost block

undo ospf bfd enable

Parameters

Parameter Description Value
cost

Specifies a cost increment value for the interface.

The value is an integer that ranges from 1 to 65534 .
max-reachable

Adjusts the link cost of an OSPF interface to the maximum link cost 65535.

-
enable

Enables BFD.

-

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Either a link fault or topology change on a network will cause routes to be re-calculated within an area. As such, speeding up the convergence of a routing protocol is critical to improving the network performance.

As link faults are inevitable, rapidly detecting these faults and notifying routing protocols is an effective way to quickly resolve such issues. This includes associating BFD with a routing protocol to speed up convergence of the routing protocol once a link fault occurs.

On a network where BFD detects a link fault, even if the fault is rectified quickly, the involved interface is disconnected due to the fact that the associated BFD session is down. As a result, the link is unstable and traffic is lost. To ensure network reliability and solve the preceding problems, run the ospf bfd incr-cost command on an OSPF interface to adjust the link cost. When the OSPF interface detects that the BFD session goes Down, the OSPF interface automatically increases the link cost so that the link in the BFD Down state is not preferentially selected, traffic can be transmitted over other links.

When an interface detects that a BFD session goes Up, the cost of the interface is automatically restored to the original value. To prevent frequent BFD status changes caused by link quality, traffic loss may occur due to link instability. To solve the preceding problem, run the ospf bfd incr-cost wtr command on an OSPF interface to set a delay after which the interface cost is restored. A BFD status change within the delay does not cause a path calculation change, ensuring network reliability.

Prerequisites

Before running the ospf bfd enable command, you need to enable BFD globally.

Before running the ospf bfd incr-cost and ospf bfd incr-cost block commands, you need to run the ospf bfd enable command to enable BFD on the interface.

Configuration Impact

If global BFD is not enabled, you can enable BFD on an interface, but BFD sessions cannot be set up in this case. Similarly, if only parameters of a BFD session are set but the ospf bfd enable command is not used, the BFD session cannot be set up.

BFD configured on an interface takes precedence over BFD configured for a process. If BFD is enabled on an interface, the BFD parameters on the interface are used to establish BFD sessions.

Precautions

  • After BFD is enabled, OSPF establishes BFD sessions only with neighbors in the Full state.
  • The ospf bfd enable and ospf bfd block commands cannot take effect at the same time. The later command overrides the previous one.
  • After BFD is disabled on an interface using the undo ospf bfd enable command, BFD session parameters still exist on the interface.
  • The cost value associated with BFD configured on an interface takes precedence over that associated with BFD configured in a process.
  • The ospf bfd incr-cost block and ospf bfd incr-cost { cost | max-reachable } commands cannot take effect at the same time. The latest configuration overrides the previous one.

Example

# Enable BFD function on the specified interface.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf bfd enable

ospf bfd block

Function

The ospf bfd block command prevents an interface from dynamically setting up a BFD session.

The undo ospf bfd block command cancels the configuration.

By default, BFD is enabled in the OSPF interface view.

Format

ospf bfd block

undo ospf bfd block

Parameters

None

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the bfd all-interfaces enable command is run in an OSPF process, all interfaces on which neighbor relationships are in Full state in the OSPF process create BFD sessions. To disable BFD on a multi-area adjacency interface, run the ospf bfd block multi-area command.

Prerequisites

BFD has been enabled on these interfaces.

Precautions

The ospf bfd enable and ospf bfd block commands cannot both take effect. The later configuration overrides the previous one.

Example

# Disable Vlanif 1 from dynamically establishing a BFD session.
<HUAWEI> system-view
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf bfd block

ospf bfd block multi-area

Function

The ospf bfd block multi-area command disables BFD on a multi-area adjacency interface.

The undo ospf bfd block multi-area command enables BFD on a multi-area adjacency interface.

By default, BFD is enabled on multi-area adjacency interfaces.

Format

ospf bfd block multi-area { area-id | area-id-ipv4 }

undo ospf bfd block multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the bfd all-interfaces enable command is run in an OSPF process, all interfaces on which neighbor relationships are in Full state in the OSPF process create BFD sessions. To disable BFD on a multi-area adjacency interface, run the ospf bfd block multi-area command.

Prerequisites

  • BFD has been enabled on the interface.
  • the ospf enable multi-area command has been run.

Example

# Disable BFD on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf bfd block multi-area 1

ospf bfd enable per-link one-arm-echo

Function

The ospf bfd enable per-link one-arm-echo command enables OSPF link-based loopback detection.

By default, OSPF link-based loopback detection is disabled.

Format

ospf bfd enable per-link one-arm-echo

Parameters

None

Views

VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Multiple physical interfaces can be bound to an Eth-Trunk interface in a VLAN. If the per-link one-arm-echo parameter is not specified, the BFD session may go Down as long as one physical interface goes Down. As a result, the OSPF neighbor relationship goes Down. If per-link one-arm-echo is specified, BFD sessions go Down only when all physical interfaces are Down. This ensures that OSPF neighbor relationships can be established.

Prerequisites

BFD has been enabled on the interface.

Example

# Configure the BFD feature on the vlanif 1 interface.
<HUAWEI> system-view
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface vlanif 1
[HUAWEI-Vlanif1] ospf bfd enable per-link one-arm-echo

ospf cost

Function

The ospf cost command sets a cost for an OSPF interface.

The undo ospf cost command restores the default cost.

By default, the cost of an OSPF interface is calculated using the following formula: Interface cost = Bandwidth reference value/Interface bandwidth, in which the bandwidth reference value can be changed using the bandwidth-reference command.

Format

ospf cost value

undo ospf cost

Parameters

Parameter Description Value
value

Specifies the cost of an OSPF interface.

The value is an integer ranging from 1 to 65535.

Views

100GE interface view, 10GE sub-interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE sub-interface view, GE electrical interface view, Loopback interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF can automatically calculate the link cost of an interface based on the interface bandwidth or set the link cost using the ospf cost command. When there are multiple routes with the same discovery protocol, cost, and destination address, these routes meet the conditions for load balancing. You can determine whether to perform load balancing by changing the interface cost according to the actual networking.

If the cost of an OSPF interface is not set using the ospf cost command, OSPF automatically calculates the cost of the interface based on the interface bandwidth. The calculation formula is as follows: Cost of an interface = Bandwidth reference value/Interface bandwidth. The integer of the calculation result is used as the cost of the interface. If the calculation result is smaller than 1, the cost of the interface is 1. You can change the interface cost by changing the bandwidth reference value.

By default, the bandwidth reference value of OSPF is 100 Mbit/s. For example, according to the formula 100000000/ bandwidth, the default cost of an Ethernet (100 Mbit/s) interface is 1. The cost of a trunk interface is the sum of all member interfaces, and the member interfaces are variable. Therefore, a trunk interface does not have a default cost.

Precautions

OSPF does not support the ospf cost command on null interfaces.

The OSPF cost does not take effect on the TE tunnel interface.

Example

# Set the cost of an interface that runs OSPF to 65.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf cost 65

ospf cost multi-area

Function

The ospf cost multi-area command configures a cost for an OSPF multi-area adjacency interface.

The undo ospf cost multi-area command restores the default cost.

By default, the cost is calculated using the Interface cost = Bandwidth reference value/Interface bandwidth formula, in which the bandwidth reference value can be changed using the bandwidth-reference command.

Format

ospf cost cost multi-area { area-id | area-id-ipv4 }

undo ospf cost multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
cost

Specifies a cost.

The value is an integer ranging from 1 to 65535.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF can automatically calculate the link cost of an interface based on the interface bandwidth or have the link cost set using the ospf cost command. When there are multiple routes with the same discovery protocol, cost, and destination address, these routes meet the conditions for load balancing. You can determine whether to perform load balancing by changing the interface cost according to the actual networking.

If the cost of a multi-area adjacency interface is not set using the ospf cost multi-area command, OSPF automatically calculates the cost of the interface based on the interface bandwidth. The calculation formula is as follows: Cost of an interface = Bandwidth reference value/Interface bandwidth. The integer of the calculation result is used as the cost of the interface. If the calculation result is smaller than 1, the cost of the interface is 1. You can change the cost of an interface by changing the bandwidth reference value.

By default, the bandwidth reference value of OSPF is 100 Mbit/s, and the cost of an Ethernet (100 Mbit/s) interface is 1.

The bandwidth of a trunk interface is the sum of all member interfaces, and the member interfaces are variable. Therefore, the trunk interface does not have a default interface cost.

Prerequisites

Run the ospf enable multi-area command first.

Precautions

The ospf cost multi-area command does not apply to null interfaces.

Example

# Set the cost to 65 for multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf cost 65 multi-area 1

ospf cpu-overload control disable

Function

The ospf cpu-overload control disable command disables OSPF CPU overload control.

The undo ospf cpu-overload control disable command restores the default configuration.

By default, OSPF CPU overload control is enabled.

Format

ospf cpu-overload control disable

undo ospf cpu-overload control disable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a device's CPU is overloaded, each module needs to take necessary measures to control its own CPU usage accordingly. Upon receiving a CPU overload notification from the system, the OSPF module controls the speeds of some internal computing processes and the establishment of neighbor relationships based on the CPU overload condition to enhance the resilience of OSPF. In this case, new neighbor relationships cannot be established. For original neighbor relationships, if a neighbor relationship is in the Full state, it will be retained; if a neighbor relationship is in a non-Full state, establishment of the neighbor relationship is paused and can continue only after the CPU recovers from overload.

Precautions

The ospf cpu-overload control disable command takes effect for both OSPF and OSPFv3.

Example

# Disable OSPF CPU overload control.
<HUAWEI> system-view
[HUAWEI] ospf cpu-overload control disable

ospf dr-priority

Function

The ospf dr-priority command sets the priority of an interface that runs for the DR or BDR.

The undo ospf dr-priority command restores the default value.

By default, the priority is 1.

Format

ospf dr-priority priovalue

undo ospf dr-priority

Parameters

Parameter Description Value
priovalue

Specifies the priority of the interface that runs for the DR or BDR. The greater the value, the higher the priority.

The value is an integer ranging from 0 to 255.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The priority of an interface determines whether the interface is qualified to be a DR or BDR. The interface with the highest priority is elected as the DR. If the priority of an interface is 0, it cannot be elected as a DR or BDR. On a broadcast or an NBMA network, you can set the priority of an interface to control the DR or BDR selection.

Configuration Impact

When the DR and BDR are elected on a network segment, they send DD packets to all neighboring nodes and set up adjacencies with all neighboring nodes.

Precautions

OSPF does not support the configuration of DR priorities on null interfaces.

According to the protocol, the OSPF DR/BDR does not have preemption. Therefore, reconfiguring the DR priority of a device does not change the DR or BDR on the network. You can use either of the following methods to re-elect a DR or BDR. However, the methods will interrupt the OSPF neighbor relationship between devices. Therefore, this methods are not recommended.

  • Restart OSPF processes on all devices.
  • Run the shutdown and undo shutdown commands in sequence on the interfaces where OSPF neighbor relationships are established.

Example

# Set the priority of the interface that runs for the DR or BDR to 8.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf dr-priority 8

ospf enable

Function

The ospf enable command enables OSPF on the interface.

The undo ospf enable command disables OSPF from the interface.

By default, OSPF is not enabled on interfaces.

Format

ospf enable [ process-id ] area { area-id | areaidipv4 }

undo ospf enable [ process-id ] area { area-id | areaidipv4 }

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The·value·is·an·integer·ranging·from·1·to·4294967295.·The·default·value·is·1.
area area-id

Specifies an area ID in the format of a decimal integer.

The value is an integer ranging from 0 to 4294967295.
areaidipv4

Specifies an area ID in the format of an IP address.

The value is in dotted decimal notation.

Views

100GE interface view, 10GE sub-interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE sub-interface view, GE electrical interface view, Loopback interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The ospf enable command configuration takes precedence over the network command configuration.

After the undo ospf enable command is run to disable OSPF from an interface, the network configuration takes effect on the interface automatically.

Configuration Impact

Switching between the ospf enable command and the network command causes the protocol status of the interface to go down or up.

To prevent service loss or system breakdown caused by the number of enabled IGP interfaces exceeding the specified specification during system running, the system controls the number of enabled IGP interfaces. An alarm is generated in the following situations:

  • The number of IGP-enabled interfaces is greater than the independent IGP specification, that is, the number of IS-IS interfaces plus the number of OSPF interfaces x 4 / 3 > independent IGP specification.
  • The number of IGP-enabled interfaces is not greater than the independent IGP specification but greater than the combined IGP specification. In addition, the number of BGP-enabled interfaces is greater than the combined BGP specification.

    The independent IGP specification is greater than the combined specification. The idependent IGP specifications, combined specifications, and combined BGP specifications vary according to products. For details, contact Huawei engineers.

Precautions

The area specified in the ospf enable command must have been created. Otherwise, the configuration does not take effect.

The configured interface and the OSPF process must be in the same VPN.

  • The ospf enable command can be configured on an interface before an OSPF process is created. The interface specified in the ospf enable command and the created OSPF process must be in the same VPN.
  • If a process is created before the ospf enable command is run on an interface, the process of the interface and existing process must belong to the same VPN. Otherwise, the ospf enable command cannot be run.
  • If no OSPF process is created, interfaces that belong to different VPN instances cannot be added to the same OSPF process.

Example

# Enable the interface in the specified OSPF area.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf enable 1 area 0

ospf enable multi-area

Function

The ospf enable multi-area command enables OSPF on a multi-area adjacency interface.

The undo ospf enable multi-area command disables OSPF on a multi-area adjacency interface.

By default, OSPF is disabled on a multi-area adjacency interface.

Format

ospf enable multi-area { area-id | area-id-ipv4 }

undo ospf enable multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
area-id

Specifies the ID of an OSPF area.

The value is an integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area.

The value is in dotted decimal notation.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In OSPF, intra-area links take precedence over inter-area links. Therefore, even if a high-speed link exists between two areas, a low-speed intra-network link rather than the high-speed link is used to transmit inter-area traffic. To address this problem, run the ospf enable multi-area command to enable OSPF on a multi-area adjacency interface so that a link can be shared by multiple areas.

Prerequisites

OSPF has been enabled on the interface using the ospf enable [ process-id ] area area-id command.

Example

# Enable OSPF on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-10GE1/0/1] ospf enable multi-area 1

ospf filter-lsa-out

Function

The ospf filter-lsa-out command configures an OSPF interface to filter outgoing LSAs on a P2P, broadcast, or NBMA network.

The undo ospf filter-lsa-out command prevents an OSPF interface from filtering outgoing LSAs on a P2P, broadcast, or NBMA network.

By default, outgoing LSAs are not filtered on a P2P, broadcast, or NBMA network.

Format

ospf filter-lsa-out { all | { ase [ acl { ase-acl-num | ase-acl-name } ] | nssa [ acl { nssa-acl-num | nssa-acl-name } ] | summary [ acl { sum-acl-num | sum-acl-name } ] } * }

undo ospf filter-lsa-out

Parameters

Parameter Description Value
all

Filters all LSAs except Grace LSAs.

-
ase

Filters AS-external LSAs (Type-5 LSAs).

-
acl

Specifies the ACL for route filtering.

-
ase-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
ase-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters starting with a letter. It cannot contain spaces.
nssa

Filters outgoing NSSA LSAs (Type 7).

-
nssa-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
nssa-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters, spaces not supported. The value starts with a letter or digit but cannot contain only digits.
summary

Filters outgoing network summary LSAs (Type 3).

-
sum-acl-num

Specifies the number of a basic ACL.

The value is an integer ranging from 2000 to 2999.
sum-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters, spaces not supported. The value starts with a letter or digit but cannot contain only digits.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When multiple links exist between two devices on a P2P, broadcast, or NBMA network, the ospf filter-lsa-out command configures the local device to filter outgoing LSAs before sending them along specified links. This can reduce the unnecessary retransmission of LSAs and save bandwidth resources.

Configuration Impact

Filtering outgoing LSAs on an OSPF interface can prevent useless LSAs from being sent to neighbors. This can reduce the size of the LSDB of neighbors and speed up the network convergence.

After the command is configured on an interface, the OSPF neighbor relationship of the interface will automatically re-establish.

Precautions

Configure the filtering rules for a named ACL only the source address range that is specified in source and the period that is specified in time-range take effect.

Grace LSAs are used to inform the neighbor of the Graceful Restart (GR) time, cause, and interface instance ID when GR starts and ends. The command is not used to filter the grace LSAs.

After the ospf filter-lsa-out command is run, the LSAs that other devices have received before will not be deleted immediately, but it will be deleted after a period of time (usually no more than one hour).

Example

# Configure an interface to filter all outgoing LSAs except grace LSAs.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf filter-lsa-out all

ospf filter-lsa-out multi-area

Function

The ospf filter-lsa-out multi-area command enables an OSPF multi-area adjacency interface to filter the LSAs to be sent.

The undo ospf filter-lsa-out multi-area command disables an OSPF multi-area adjacency interface from filtering the LSAs to be sent.

By default, OSPF multi-area adjacency interfaces do not filter the LSAs to be sent.

Format

ospf filter-lsa-out { all | { ase [ acl { ase-acl-num | ase-acl-name } ] | nssa [ acl { nssa-acl-num | nssa-acl-name } ] | summary [ acl { sum-acl-num | sum-acl-name } ] } * } multi-area { area-id-integer | area-id-ipv4 }

undo ospf filter-lsa-out multi-area { area-id-integer | area-id-ipv4 }

Parameters

Parameter Description Value
all

Filters all LSAs except Grace LSAs.

-
ase

Filters AS-external LSAs (Type-5 LSAs).

-
acl

Specifies the ACL for route filtering.

-
ase-acl-num

Specifies the number of a basic ACL.

The value is an integer that ranges from 2000 to 2999.
ase-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters, spaces not supported. The name must start with a letter or digit, and cannot contain only digits.
nssa

Filters NSSA LSAs (Type-7 LSAs).

-
nssa-acl-num

Specifies the number of a basic ACL.

The value is an integer that ranges from 2000 to 2999.
nssa-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters, spaces not supported. The name must start with a letter or digit, and cannot contain only digits.
summary

Filters Network-summary LSAs (Type-3 LSAs).

-
sum-acl-num

Specifies the number of a basic ACL.

The value is an integer that ranges from 2000 to 2999.
sum-acl-name

Specifies the name of a named basic ACL.

The value is a string of 1 to 64 case-sensitive characters, spaces not supported. The name must start with a letter or digit, and cannot contain only digits.
area-id-integer

Specifies the ID of an OSPF area.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area.

The value is in the format of an IP address.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If multiple links exist between two devices, you can run the ospf filter-lsa-out multi-area command to configure the local device to filter the LSAs to be sent. This prevents unnecessary LSA transmission and reserves bandwidth resources.

Prerequisites

The ospf enable multi-area command has been run.

Configuration Impact

The ospf filter-lsa-out multi-area command prevents useless LSAs from being sent to OSPF neighbors, which reduces the size of the neighbors' LSDBs and speeds up network convergence.

After the ospf filter-lsa-out multi-area command is run on an interface, the neighbor relationships on the interface are reestablished.

Precautions

When filtering conditions are configured for a named ACL, only the configurations specified by source and time-range take effect.

Grace LSAs are used to inform neighbors of the graceful restart (GR) time, cause, and interface instance ID when a GR starts or ends. The ospf filter-lsa-out multi-area command does not apply to Grace LSAs.

Example

# Configure multi-area adjacency interface VLANIF 1 to filter all outgoing LSAs except Grace LSAs.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf filter-lsa-out all multi-area 1

ospf frr block

Function

The ospf frr block command blocks FRR on a specified OSPF interface.

The undo ospf frr block command restores the default configuration.

By default, FRR is not blocked on an interface.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

ospf frr block

undo ospf frr block

Parameters

None

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To prevent the link that travels through the devices running important services from becoming a backup link, run the ospf frr block command on the devices. In this manner, services on the devices are not affected when FRR calculation is performed.

Precautions

Before configuring OSPF IP FRR, run the ospf frr block command to block FRR on a specified interface. In this manner, the link where the interface resides is not calculated as a backup link during FRR calculation.

Example

# Block OSPF IP FRR on the interface.
<HUAWEI> system-view
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf frr block

ospf maxage-lsa auto-protect disable

Function

The ospf maxage-lsa auto-protect disable command disables master/slave board switching triggered by abnormal OSPF LSA aging.

The undo ospf maxage-lsa auto-protect disable command enables master/slave board switching triggered by abnormal OSPF LSA aging.

By default, master/slave board switching triggered by abnormal OSPF LSA aging is enabled.

Format

ospf maxage-lsa auto-protect disable

undo ospf maxage-lsa auto-protect disable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When the local device's aging timer expires, the local device incorrectly clears all Router LSAs from the peer device, which causes route flapping and service interruptions. To resolve this issue, master/slave board switching triggered by abnormal OSPF LSA aging is automatically enabled. Master/Slave board switching is triggered to restore network connections and service traffic when the following condition is met:

(Number of incorrectly cleared Router LSAs/Total number of Router LSAs) x 100%>=80% (Router LSAs are those sent by the peer device to the local device)

To disable master/slave board switching triggered by abnormal OSPF LSA aging, run the ospf maxage-lsa auto-protect disable command.

Example

# Disable master/slave board switching triggered by abnormal OSPF LSA aging.
<HUAWEI> system-view
[HUAWEI] ospf maxage-lsa auto-protect disable

ospf mib-binding

Function

The ospf mib-binding command binds an OSPF process to SNMP and enables OSPF to respond to SNMP requests.

The undo ospf mib-binding command removes the binding.

By default, OSPF processes are not bound to SNMP.

Format

ospf mib-binding process-id

undo ospf mib-binding

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The OSPF MIB is a virtual database of the device status maintained by the managed devices.

When multiple OSPF processes are started, you can specify the OSPF process to be processed by the OSPF MIB by binding the OSPF MIB to a specified OSPF process.

Example

# Bind an OSPF process to SNMP.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] quit
[HUAWEI] ospf mib-binding 100

ospf mtu-enable

Function

The ospf mtu-enable command enables an interface to add its actual MTU in DD packets to be sent and check whether the MTU in a received DD packet is greater than the local MTU.

The undo ospf mtu-enable command restores the default configuration.

By default, an interface adds the MTU 0 (not the actual MTU) in DD packets to be sent and does not check the MTUs in received DD packets.

Format

ospf mtu-enable

undo ospf mtu-enable

Parameters

None

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To improve compatibility with a non-Huawei device, an OSPF-enabled Huawei device adds the MTU 0 in DD packets to be sent and does not check the MTUs in received DD packets, allowing an OSPF neighbor relationship to be set up even if the two ends have different MTU settings.

However, under the default configuration, the non-Huawei device may discard an OSPF packet received from the Huawei device if the packet's actual MTU is greater than the MTU of the non-Huawei device. If the discarded packet is an LSU, an OSPF neighbor relationship can still be set up, but the route carried in the LSU fails to be learned, causing service interruptions.

To resolve this issue, run the ospf mtu-enable command to configure an interface to add the actual MTU in DD packets to be sent and check whether the MTU in a received DD packet is greater than the local MTU. If the interface MTU settings of the local and remote ends are different, an OSPF neighbor relationship cannot enter the Full state. In this manner, MTU inconsistency can then be identified in time.

Precautions

The command cannot be run on a null interface.

After the command is configured, the OSPF neighbor relationship is reestablished.

Example

# Configure the interface to fill in the MTU value when sending DD packets.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf mtu-enable

ospf mtu-enable multi-area

Function

The ospf mtu-enable multi-area command enables a multi-area adjacency interface to add its actual MTU in DD packets to be sent and check whether the MTU in a received DD packet is greater than the local MTU.

The undo ospf mtu-enable multi-area command restores the default configuration.

By default, a multi-area adjacency interface adds the MTU 0 (not the actual MTU) in DD packets to be sent and does not check the MTUs in received DD packets.

Format

ospf mtu-enable multi-area { area-id | area-id-ipv4 }

undo ospf mtu-enable multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To improve compatibility with a non-Huawei device, an OSPF-enabled Huawei device adds the MTU 0 in DD packets to be sent and does not check the MTUs in received DD packets, allowing an OSPF neighbor relationship to be set up even if the two ends have different MTU settings.

However, under the default configuration, the non-Huawei device may discard an OSPF packet received from the Huawei device if the packet's actual MTU is greater than the MTU of the non-Huawei device. If the discarded packet is an LSU, an OSPF neighbor relationship can still be set up, but the route carried in the LSU fails to be learned, causing service interruptions.

To resolve this issue, run the ospf mtu-enable multi-area command to configure a multi-area adjacency interface to add the actual MTU in DD packets to be sent and check whether the MTU in a received DD packet is greater than the local MTU. If the interface MTU settings of the local and remote ends are different, an OSPF neighbor relationship cannot enter the Full state. In this manner, MTU inconsistency can then be identified in time.

Prerequisites

The ospf enable multi-area command has been run.

Precautions

The ospf mtu-enable multi-area command does not apply to null interfaces.

After the ospf mtu-enable multi-area command is run, the OSPF neighbor relationship is reestablished.

Example

# Enable multi-area adjacency interface to add its MTU to the DD packets to be sent.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf mtu-enable multi-area 1

ospf multi-area

Function

The ospf frr block multi-area command blocks FRR on a specified OSPF multi-area adjacency interface.

The undo ospf frr block multi-area command restores the default configuration.

By default, FRR is not blocked on a multi-area adjacency interface.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

ospf frr block multi-area { area-id | area-id-ipv4 }

undo ospf frr block multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can run the ospf frr block multi-area command on a device that transmits important services to prevent the device from becoming a node on the backup link. This prevents services from being affected after FRR calculation.

Prerequisites

The ospf enable multi-area command has been run.

Precautions

Before configuring OSPF IP FRR, run the ospf frr block command to block FRR on a specified interface. In this manner, the link where the interface resides is not calculated as a backup link during FRR calculation.

Example

# Disable OSPF IP FRR on a multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf frr block multi-area 1

ospf network-type

Function

The ospf network-type command sets the network type for an OSPF interface.

The undo ospf network-type command restores the default network type.

By default, the network type of an interface is determined by the physical interface. For details, see "IP Routing" > "OSPF Configuration" > "Configuring OSPF on the NBMA or P2MP Network" > "Configuring Network Types for OSPF Interfaces" in the Configuration Guide.

Format

ospf network-type { broadcast | p2p | p2mp | nbma }

undo ospf network-type

Parameters

Parameter Description Value
broadcast

Indicates that the network type of the interface is changed to broadcast.

-
p2p

Indicates that the network type of the interface is changed to point-to-point.

-
p2mp

Indicates that the network type of the interface is changed to point-to-multipoint.

-
nbma

Indicates that the network type of the interface is changed to NBMA.

-

Views

100GE interface view, 10GE sub-interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE sub-interface view, GE electrical interface view, Loopback interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When link layer protocols remain unchanged, you can change network types and configure OSPF features to flexibly build networks.

  • On the broadcast network, if there is a device that does not support multicast addresses, you can change the network type of the interface to NBMA.
  • If the network type of the interface is NBMA which is then changed to broadcast, no neighbors need to be configured.

    The network type can be changed from NBMA to broadcast only when a direct virtual circuit is available between any two devices (the network must be fully meshed). If the condition is not met, change the network type to point-to-multipoint. In this manner, two indirectly connected devices can communicate with the help of one or two directly connected and reachable devices. After the network type of the interface is changed to point-to-multipoint, no neighbors need to be configured.

    If there are only two devices that run OSPF in the same network segment, the network type of an interface can be changed to P2P.

Precautions

  • The command cannot be run on a null interface.
  • When the network type of an interface is NBMA, or the network type of an interface is changed to NBMA manually, run the peer command to configure a neighbor.
  • If the network type of an OSPF interface is NBMA, OSPF does not advertise the interface's information to RSVP-TE, and TE tunnels passing through this interface fail to go Up.
  • Generally, the network types of two OSPF interfaces on the both ends of the link must be identical. Otherwise, the two interfaces cannot set up a neighbor relationship.
  • The network type of an interface on a star network cannot be set to P2P. Otherwise, a deadlock tends to occur if the Layer 2 link connected to the interface goes down and then recovers.

Example

# Set network type of an interface to NBMA.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf network-type nbma

ospf network-type p2p peer-ip-ignore

Function

The ospf network-type p2p peer-ip-ignore command sets the network type for an OSPF interface.

By default, the network type of an interface is determined by the physical interface.

Format

ospf network-type p2p peer-ip-ignore

Parameters

Parameter Description Value
p2p

Indicates that the network type of the interface is changed to point-to-point.

-
peer-ip-ignore

Disables network segment check when IP address unnumbering is not configured for a P2P interface changed from a broadcast interface and the interface tries to establish an OSPF neighbor relationship. By default, if peer-ip-ignore is not specified in the command, OSPF checks the network segment of the two ends during which an OSPF neighbor relationship is to be established. Specifically, OSPF performs an AND operation on the local subnet mask and the local IP address and on the local subnet mask and the remote IP address. An OSPF neighbor relationship can be established only when the results on the two ends are the same.

-

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When link layer protocols remain unchanged, you can change network types and configure OSPF features to flexibly build networks.

If there are only two devices that run OSPF in the same network segment, the network type of an interface can be changed to P2P.

Precautions

Generally, the network types of two OSPF interfaces on the both ends of the link must be identical. Otherwise, the two interfaces cannot set up a neighbor relationship.

Example

# Set network type of 10GE 1/0/1 to point-to-point type.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf network-type p2p peer-ip-ignore

ospf p2mp-mask-ignore

Function

The ospf p2mp-mask-ignore command prevents a device from checking the network mask on a Point-to-Multipoint (P2MP) network.

The undo ospf p2mp-mask-ignore command configures the device to check the network mask on a P2MP network.

By default, no device on a P2MP network checks the network mask.

Format

ospf p2mp-mask-ignore

undo ospf p2mp-mask-ignore

Parameters

None

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF checks the network masks carried in Hello packets. If the network mask carried in a received Hello packet is not the same as the network mask of the local device, the Hello packet is discarded.

On a P2MP network, when the mask lengths of devices are different, you can use the ospf p2mp-mask-ignore command to prevent the device from checking the network mask in Hello packets. In this manner, the OSPF neighbor relationship can be established.

Prerequisites

A non-fully connected Non-Broadcast Multi-Access (NBMA) network has been changed to common P2MP network using the ospf network-type p2mp command.

Example

# Prevent the device from checking the network mask on a P2MP network.
<HUAWEI> system-view
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf network-type p2mp
[HUAWEI-Vlanif1] ospf p2mp-mask-ignore

ospf peer hold-max-cost timer

Function

The ospf peer hold-max-cost timer command sets a period during which OSPF keeps the maximum cost in local LSAs.

The undo ospf peer hold-max-cost timer command restores the default configuration.

By default, no such a period is set after an OSPF neighbor relationship is established.

Format

ospf peer hold-max-cost timer timer

undo ospf peer hold-max-cost timer [ timer ]

Parameters

Parameter Description Value
timer timer

Specifies a period during which OSPFv3 keeps the maximum cost in local LSAs.

The value is an integer ranging from 100 to 1000000, in milliseconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When an OSPF interface changes from Down to Up, the OSPF neighbor relationship is re-established. When IGP route convergence ends, traffic is switched back. IGP routes converge fast. Many services that depend on IGP routes may require a delayed switchback. In this case, you can run the ospf peer hold-max-cost command so that OSPF keeps the maximum cost in local LSAs for a specified period after the OSPF neighbor relationship reaches Full state. During this period, the traffic forwarding path remains unchanged. After this period elapses, the original cost is restored, and traffic is switched back.

Example

# Set the period during which OSPF keeps the maximum cost in local LSAs on an interface to 1000 ms.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf peer hold-max-cost timer 1000

ospf router-id auto-recover disable

Function

The ospf router-id auto-recover disable command disables automatic router ID recovery after a router detects a router ID conflict.

The undo ospf router-id auto-recover disable command enables automatic router ID recovery after a router detects a router ID conflict.

By default, automatic router ID recovery takes effect after a router detects a router ID conflict.

Format

ospf router-id auto-recover disable

undo ospf router-id auto-recover disable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a router ID conflict occurs in an OSPF area, the system selects a new router ID, which prevents route flapping and reduces route calculation operations. Other protocols will not go Down when the CPU usage is controlled.

NOTE:

  • If the automatic recovery function is enabled and a router ID conflict occurs between indirectly connected routers in one OSPF area, the system replaces the conflicted router ID with a newly calculated one. The automatic recovery function takes effect on both configured and automatically generated router IDs.
  • The system can replace a router ID in a maximum of three attempts in case the router ID conflict persists.

Example

# Disable automatic router ID recovery after a router detects a router ID conflict.
<HUAWEI> system-view
[HUAWEI] ospf router-id auto-recover disable

ospf smart-discover

Function

The ospf smart-discover command enables smart-discover on an interface.

The undo ospf smart-discover command disables smart-discover from an interface.

By default, smart-discover is disabled on interfaces.

Format

ospf smart-discover

undo ospf smart-discover

Parameters

None

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Generally, routers periodically send Hello packets through OSPF interfaces to establish and maintain OSPF neighbor relationships and elect a DR or BDR on a multi-access network (broadcast or NBMA network). However, Hello packets are not sent to neighbors until the Hello timer expires, which slows down the establishment of neighbor relationships and DR or BDR election.

To address this problem, run the ospf smart-discover multi-area command to enable smart-discover on a multi-area adjacency interface so that Hello packets are sent to neighbors immediately, regardless of the Hello timer.

Implementation Procedure

If smart-discover is enabled on a broadcast or NBMA interface, it works as follows:

  • If the neighbor status reaches 2-way for the first time or returns to Init from 2-way or a higher state, the smart-discover-capable interface sends Hello packets to its neighbor immediately when detecting that the neighbor's status changes.
  • If the interface status of the DR or BDR on the multi-access network changes, the smart-discover-capable interface sends Hello packets within its network segment and participates in DR or BDR election.

    The fast neighbor relationship establishment process on a P2P or P2MP network is similar to that on a broadcast or NBMA network.

Precautions

The default interval for sending Hello packets varies according to the network type.

Example

# Enable smart-discover.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf smart-discover

ospf smart-discover multi-area

Function

The ospf smart-discover multi-area command enables smart-discover on a multi-area adjacency interface.

The undo ospf smart-discover multi-area command disables smart-discover on a multi-area adjacency interface.

By default, smart-discover is disabled on multi-area adjacency interfaces.

Format

ospf smart-discover multi-area { area-id | area-id-ipv4 }

undo ospf smart-discover multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Generally, routers periodically send Hello packets through OSPF interfaces to establish and maintain OSPF neighbor relationships and elect a DR or BDR on a multi-access network (broadcast or NBMA network). However, Hello packets are not sent to neighbors until the Hello timer expires, which slows down the establishment of neighbor relationships and DR or BDR election.

To address this problem, run the ospf smart-discover multi-area command to enable smart-discover on a multi-area adjacency interface so that Hello packets are sent to neighbors immediately, regardless of the Hello timer.

Prerequisites

The ospf enable multi-area command has been run.

Implementation Procedure

If smart-discover is enabled on a broadcast or NBMA interface, it works as follows:

  • If the neighbor status reaches 2-way for the first time or returns to Init from 2-way or a higher state, the smart-discover-capable interface sends Hello packets to its neighbor immediately when detecting that the neighbor's status changes.
  • If the interface status of the DR or BDR on the multi-access network changes, the smart-discover-capable interface sends Hello packets within its network segment and participates in DR or BDR election.

    The fast neighbor relationship establishment process on a P2P or P2MP network is similar to that on a broadcast or NBMA network.

Configuration Impact

The interval at which Hello packets are sent is determined by the interval at which Hello packets are sent.

Precautions

The default interval for sending Hello packets varies according to the network type.

Example

# Enable smart-discover on a multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf smart-discover multi-area 1

ospf suppress-flapping interface disable

Function

The ospf suppress-flapping interface disable command disables OSPF interface flapping suppression.

The undo ospf suppress-flapping interface disable command enables OSPF interface flapping suppression.

By default, OSPF interface flapping suppression is enabled.

Format

ospf suppress-flapping interface disable

undo ospf suppress-flapping interface disable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If OSPF interfaces frequently alternate between up and down, the interfaces will flap, and protocol packets will be frequently exchanged, affecting OSPF services. To address this issue, run the undo ospf suppress-flapping interface disable command to enable interface flapping suppression. This function allows a device to delay interface state changes to up.

By default, interface flapping suppression is enabled globally for all OSPF interfaces. If this function is not needed, run the ospf suppress-flapping interface disable command to disable it.

Example

# Disable OSPF interface flapping suppression.
<HUAWEI> system-view
[HUAWEI] ospf suppress-flapping interface disable

ospf suppress-flapping peer

Function

The ospf suppress-flapping peer command configures detection parameters for OSPF neighbor relationship flapping suppression.

The undo ospf suppress-flapping peer command restores the default detection parameters.

The ospf suppress-flapping peer disable command disables OSPF neighbor relationship flapping suppression from an interface.

The undo ospf suppress-flapping peer disable command enables OSPF neighbor relationship flapping suppression on an interface.

The ospf suppress-flapping peer hold-down command configures the Hold-down mode and sets duration for this mode.

The undo ospf suppress-flapping peer hold-down command cancels the Hold-down mode.

The ospf suppress-flapping peer hold-max-cost disable command disables the Hold-max-cost mode.

The undo ospf suppress-flapping peer hold-max-cost disable command enables the Hold-max-cost mode.

By default, the detection interval of OSPF neighbor flapping suppression is 60s, the suppression threshold is 10, and the interval for exiting from suppression is 120s.

By default, OSPF neighbor flapping suppression is enabled on all interfaces.

By default, the Hold-down mode is disabled and the Hold-max-cost mode is enabled.

Format

ospf suppress-flapping peer disable

ospf suppress-flapping peer hold-down interval

ospf suppress-flapping peer hold-max-cost disable

ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } *

undo ospf suppress-flapping peer disable

undo ospf suppress-flapping peer hold-down [ interval ]

undo ospf suppress-flapping peer hold-max-cost disable

undo ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } *

Parameters

Parameter Description Value
hold-down interval

Specifies the duration of the Hold-down mode.

The value is an integer ranging from 1 to 86400, in seconds.
detecting-interval detecting-interval

Specifies the detection interval of OSPF neighbor relationship flapping suppression.

Each OSPF interface on which OSPF neighbor relationship flapping suppression is enabled starts a flapping counter. If the interval between two successive neighbor status changes from Full to a non-Full state is shorter than detecting-interval, a valid flapping_event is recorded, and the flapping_count increases by 1.

The value is an integer ranging from 1 to 300, in seconds. The default value is 60s.
threshold threshold

Specifies the threshold of OSPF neighbor relationship flapping suppression.

When the flapping_count reaches or exceeds threshold, flapping suppression takes effect.

The value is an integer ranging from 1 to 1000. The default value is 10.
resume-interval resume-interval
  • Specifies a flapping detection clearance threshold for OSPF neighbor flapping suppression.

If the interval between two successive neighbor status changes from Full to a non-Full state is greater than resume-interval, the flapping_count is cleared.

  • If OSPF neighbor flapping suppression works in Hold-max-cost mode, resume-interval specifies the duration of the Hold-max-cost mode.

The value of resume-interval must be greater than that of detecting-interval.

The value is an integer ranging from 2 to 1000, in seconds. The default value is 120s.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can set detection parameters for OSPF neighbor flapping suppression on a specified interface according to the actual situation of the network. The default values are recommended.

By default, OSPF neighbor flapping suppression is enabled globally. That is, OSPF neighbor flapping suppression is enabled on all interfaces in a process. To disable OSPF neighbor flapping suppression on a specified interface, run the ospf suppress-flapping peer disable command.

After an interface enters the flapping suppression state, all neighbors connected to the interface enter the flapping suppression state.

OSPF neighbor flapping suppression has two modes: Hold-down and Hold-max-cost.

  • Hold-down mode: To prevent frequent flooding and topology changes during neighbor relationship establishment, the neighbor relationship cannot be re-established within a period of time. This prevents frequent LSDB synchronization and a large number of packets from being exchanged.
  • Hold-max-cost mode: In this mode, the link cost is set to the maximum value (65535) within a period of time to prevent service traffic from passing through flapping links.

    The Hold-down mode and Hold-max-cost mode can be used together. If both modes take effect, the system enters the Hold-down mode first. After the system exits the Hold-down mode, the system enters the Hold-max-cost mode.

    By default, the Hold-max-cost mode takes effect. To configure the Hold-down mode and set duration for this mode, run the ospf suppress-flapping peer hold-down interval command.

    When OSPF neighbor flapping suppression uses the Hold-max-cost mode, you can run the ospf suppress-flapping peer resume-interval resume-interval command to set the duration of the Hold-max-cost mode. The value ranges from 2 to 1000, in seconds. The default value is 120s.

Prerequisites

OSPF neighbor relationship flapping suppression must have been enabled globally before you configure detection parameters for it. By default, the function is enabled. If it is disabled, run the undo suppress-flapping peer disable command to enable it before you configure the detection parameters.

OSPF neighbor relationship flapping suppression must have been enabled globally before you enable the function on an interface using the undo ospf suppress-flapping peer disable command. By default, the function is enabled globally. If it is disabled, run the undo suppress-flapping peer disable command to enable it first.

OSPF neighbor relationship flapping suppression must have been enabled globally before you configure the Hold-down mode and set duration for this mode. By default, the function is enabled. If it is disabled, run the undo suppress-flapping peer disable command to enable it before you configure the Hold-down mode and set duration for this mode.

OSPF neighbor relationship flapping suppression must have been enabled globally before you configure duration for the Hold-max-cost mode. By default, the function is enabled. If it is disabled, run the undo suppress-flapping peer disable command to enable it before you configure duration for the Hold-max-cost mode.

Precautions

The Hold-max-cost mode takes effect only unidirectionally. If a remote device does not support OSPF neighbor relationship flapping suppression, bidirectional traffic between the local and remote devices may travel along different paths.

When the OSPF neighbor relationship flaps again, the hold-max-cost timer will be restarted. If the flapping persists, the corresponding link may fail to exit from the flapping suppression state.

If hold-down is configured, flapping suppression works first in hold-down mode and then in hold-max-cost mode by default. If only the hold-down mode is required, run the ospf suppress-flapping peer hold-max-cost disable command to disable the hold-max-cost mode.

Example

# Disable OSPF neighbor relationship flapping suppression from an interface.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf suppress-flapping peer disable
# Configure the Hold-down mode and set its duration to 200s on an interface.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf suppress-flapping peer hold-down 200
# Disable the Hold-max-cost mode on an interface.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf suppress-flapping peer hold-max-cost disable
# Set the detection interval of OSPF neighbor relationship flapping suppression to 5s, the suppression threshold to 40, and the interval for exiting from suppression to 20s on an interface.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf suppress-flapping peer detecting-interval 5 threshold 40 resume-interval 20

ospf suppress-flapping peer multi-area

Function

The ospf suppress-flapping peer disable multi-area command disables OSPF neighbor relationship flapping suppression on a multi-area adjacency interface.

The undo ospf suppress-flapping peer disable multi-area command enables OSPF neighbor relationship flapping suppression on a multi-area adjacency interface.

The ospf suppress-flapping peer hold-max-cost disable multi-area command disables the Hold-max-cost mode on a multi-area adjacency interface.

The undo ospf suppress-flapping peer hold-max-cost disable multi-area command enables the Hold-max-cost mode on a multi-area adjacency interface.

The ospf suppress-flapping peer multi-area command configures detection parameters for OSPF neighbor relationship flapping suppression on a multi-area adjacency interface.

The undo ospf suppress-flapping peer multi-area command restores the default detection parameters.

The ospf suppress-flapping peer hold-down multi-area command configures the Hold-down mode and sets duration for this mode on a multi-area adjacency interface.

The undo ospf suppress-flapping peer hold-down multi-area command cancels the Hold-down mode on a multi-area adjacency interface.

By default, OSPF neighbor relationship flapping suppression is enabled on all multi-area adjacency interfaces.

By default, the Hold-max-cost mode is enabled on a multi-area adjacency interface.

By default, the detection interval of OSPF neighbor relationship flapping suppression on multi-area adjacency interfaces is 60s, the suppression threshold is 10, and the interval for exiting from suppression is 120s.

By default, the Hold-down mode is disabled on a multi-area adjacency interface.

Format

ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } * multi-area { area-id | area-id-ipv4 }

ospf suppress-flapping peer disable multi-area { area-id | area-id-ipv4 }

ospf suppress-flapping peer hold-down interval multi-area { area-id | area-id-ipv4 }

ospf suppress-flapping peer hold-max-cost disable multi-area { area-id | area-id-ipv4 }

undo ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } * multi-area { area-id | area-id-ipv4 }

undo ospf suppress-flapping peer disable multi-area { area-id | area-id-ipv4 }

undo ospf suppress-flapping peer hold-down [ interval ] multi-area { area-id | area-id-ipv4 }

undo ospf suppress-flapping peer hold-max-cost disable multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
detecting-interval detecting-interval

Specifies the detection interval of OSPF neighbor relationship flapping suppression.

Each OSPF interface on which OSPF neighbor relationship flapping suppression is enabled starts a flapping counter. If the interval between two successive neighbor status changes from Full to a non-Full state is shorter than detecting-interval, a valid flapping_event is recorded, and the flapping_count increases by 1.

The value is an integer ranging from 1 to 300, in seconds. The default value is 60s.
threshold threshold

Specifies the threshold of OSPF neighbor relationship flapping suppression.

When the flapping_count reaches or exceeds threshold, flapping suppression takes effect.

The value is an integer ranging from 1 to 1000. The default value is 10.
resume-interval resume-interval
  • Specifies the interval for exiting OSPF neighbor relationship flapping suppression.

If the interval between two successive neighbor status changes from Full to a non-Full state is longer than resume-interval, the flapping_count is reset.

  • If OSPF neighbor relationship flapping suppression works in Hold-max-cost mode, resume-interval indicates the duration of this mode.

resume-interval must be greater than detecting-interval.

The value is an integer ranging from 2 to 1000, in seconds. The default value is 120s.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255
hold-down interval

Specifies the duration of the Hold-down mode.

The value is an integer ranging from 1 to 86400, in seconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, OSPF neighbor relationship flapping suppression is enabled on all multi-area adjacency interfaces in the same OSPF process. To disable the function from one of the interfaces, run the ospf suppress-flapping peer disable multi-area area-id command.

When a multi-area adjacency interface enters the flapping suppression state, all neighbor relationships on the interface enter the state accordingly.

Flapping suppression works in either Hold-down or Hold-max-cost mode.

  • Hold-down mode: In the case of frequent flooding and topology changes during neighbor relationship establishment, interfaces prevent neighbor relationship reestablishment during Hold-down suppression, which minimizes LSDB synchronization attempts and packet exchanges.
  • Hold-max-cost mode: If the traffic forwarding path changes frequently, interfaces use 65535 as the cost of the flapping link during Hold-max-cost suppression, which prevents traffic from passing through the flapping link.

    Flapping suppression can also work first in Hold-down mode and then in Hold-max-cost mode.

    By default, the Hold-max-cost mode takes effect on a multi-area adjacency interface. To configure the Hold-down mode and set duration for this mode, run the ospf suppress-flapping peer hold-down interval multi-area area-id command.

    To configure detection parameters for OSPF neighbor relationship flapping suppression on a multi-area adjacency interface, run the ospf suppress-flapping peer multi-area command. However, keeping the default configurations is recommended.

Example

# Disable the Hold-max-cost mode on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf suppress-flapping peer hold-max-cost disable multi-area 1
# Set the detection interval of OSPF neighbor relationship flapping suppression to 5s, the suppression threshold to 40, and the interval for exiting from suppression to 20s on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf suppress-flapping peer detecting-interval 5 threshold 40 resume-interval 20 multi-area 1
# Configure the Hold-down mode and set its duration to 200s on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf suppress-flapping peer hold-down 200 multi-area 1
# Disable OSPF neighbor relationship flapping suppression on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf suppress-flapping peer disable multi-area 1

ospf suppress-reachability

Function

The ospf suppress-reachability command enables an OSPF interface to suppress the advertisement of interface addresses.

The undo ospf suppress-reachability command enables an OSPF interface to advertise its interface addresses.

By default, an OSPF interface will advertise its interface addresses.

Format

ospf suppress-reachability [ disable ]

undo ospf suppress-reachability [ disable ]

Parameters

Parameter Description Value
disable

Disables OSPF from suppressing the advertisement of interface addresses.

-

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To enable an OSPF interface to suppress the advertisement of interface addresses, run the ospf suppress-reachability command.

Example

# Enable the interface to suppress the advertisement of interface addresses.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf suppress-reachability

ospf timer dead

Function

The ospf timer dead command sets a dead interval for the OSPF neighbor in the instance to which an interface belongs.

The undo ospf timer dead command restores the default value.

By default, for a P2P and broadcast interface, the dead interval for OSPF neighbors is 40 seconds; on an NBMA interface, the interval is 120 seconds.

Format

ospf timer dead interval

undo ospf timer dead

Parameters

Parameter Description Value
interval

Specifies a dead interval for OSPF neighbors.

The value is an integer ranging from 1 to 235926000.

Setting a dead interval that is longer than 10s for OSPF neighbors is recommended. If the dead interval is less than 10s, the session may be terminated.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If no Hello packet is received from a neighbor within a dead interval, the neighbor is considered invalid. The dead interval on OSPF interfaces must be greater than the transmission interval of Hello messages. In addition, the dead intervals of devices on the same network segment must be the same.

By default, the dead interval of OSPF neighbors is four times the transmission interval of Hello messages.

Precautions

The command cannot be run on a null interface.

If the dead interval of an OSPF neighbor is shorter than 10s, the session may be closed. Therefore, if dead interval is shorter than 10s, the actual dead interval of an OSPF neighbor is not shorter than 10s. If the conservative mode is configured using the ospf timer hello command, the configured dead timer takes effect even when its value is less than 10s.

Example

# Set the dead interval on the interface to 60 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf timer dead 60

ospf timer dead multi-area

Function

The ospf timer dead multi-area command configures a dead interval of OSPF neighbor relationships for a multi-area adjacency interface.

The undo ospf timer dead multi-area command restores the default dead interval.

By default, the dead interval of OSPF neighbor relationships on a P2P multi-area adjacency interface is 40s.

Format

ospf timer dead interval multi-area { area-id | area-id-ipv4 }

undo ospf timer dead multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
interval

Specifies the dead interval of OSPF neighbor relationships.

The value is an integer ranging from 1 to 235926000, in seconds.

Setting a value that is larger than 20 for the interval is recommended. If the interval is less than 20s, adjacencies may be interrupted.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an interface does not receive Hello packets from an OSPF neighbor within the dead interval, the interface considers the neighbor Down. The dead interval must be greater than the interval at which Hello packets are sent, and devices on the same network segment must have the same dead interval.

By default, the dead interval of OSPF neighbor relationships is four times the interval at which Hello packets are sent.

Prerequisites

Run the ospf enable multi-area command first.

Precautions

The ospf timer dead multi-area command does not apply to null interfaces.

Example

# Set the dead interval of OSPF neighbor relationships to 60s for multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf timer dead 60 multi-area 1

ospf timer hello

Function

The ospf timer hello command sets the interval at which Hello packets are sent on an interface.

The undo ospf timer hello command restores the default value.

By default, for P2P and broadcast interfaces, the interval is 10 seconds, for P2MP and NBMA interfaces, the interval is 30 seconds.

Format

ospf timer hello interval [ conservative ]

undo ospf timer hello

Parameters

Parameter Description Value
interval

Specifies the interval at which Hello packets are sent on an interface.

The value is an integer ranging from 1 to 65535, in seconds.

Setting hello interval to be longer than 2s is recommended.
conservative

Indicates the conservative mode of the dead timer. If the conservative mode is configured, the value configured for the dead timer using the ospf timer dead command takes effect even when the value is less than 10s.

-

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Hello packets are periodically exchanged by OSPF interfaces to establish and maintain neighbor relationships. A Hello packet contains information about timers, DRs, BDRs, and known neighbors.

The smaller the interval value, the faster a network topology change can be detected, and the larger the route cost. Ensure that the parameters of this interface and the adjacent routers are consistent.

To speed up OSPF convergence in the case of a link failure, configuring BFD For OSPF is recommended. If the remote end does not support BFD for OSPF or you do not want to configure BFD for OSPF, specify conservative when you run the ospf timer hello command. If the conservative mode is configured, the value configured for the dead timer using the ospf timer dead command takes effect even when the value is less than 10s; if the value configured for the dead timer is greater than 10s, services may be affected.

Precautions

The ospf timer hello command cannot be run on a null interface.

  • If the configured interval (X) for sending Hello packets is less than 10s, the actual interval (Y) for sending Hello packets is calculated using the following formula:

    Y = X/2 + X%2, where X/2 refers to the rounded-off value of X divided by 2, and X%2 refers to X mod 2. For example, if X equals 5, then X/2 equals 2, and X%2 equals 1.
  • If the interval for sending Hello packets is set and the ospf timer dead command is not run, the dead interval for OSPF neighbors is four times the interval for sending Hello packets. Therefore, if the interval for sending Hello packets is less than or equal to 2s, the dead interval for OSPF neighbors is less than 10s. In this case, if no Hello packets are received within the dead interval, the neighbor relationships are disconnected. To prevent neighbor relationship flapping and improve network reliability, the system automatically sets the dead interval for OSPF neighbors to 10s if the actual dead interval is less than 10s. However, if the conservative mode is enabled for the dead interval for OSPF neighbors, the dead interval that is four times the interval for sending Hello packets is still used to check whether OSPF neighbors are valid.

If OSPF packets are encapsulated with GRE packets, you are advised to set the interval for sending Hello packets to a large value. As OSPF Hello packets are encapsulated into GRE data packets, which have a low priority and may be easily discarded during network congestion, OSPF may fail to receive Hello packets within the dead time, interrupting the neighbor relationship.

Example

# Set the interval at which Hello packets are sent on the interface to 20 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf timer hello 20

ospf timer hello multi-area

Function

The ospf timer hello multi-area command configures the interval at which a multi-area adjacency interface sends Hello packets.

The undo ospf timer hello multi-area command restores the default interval at which a multi-area adjacency interface sends Hello packets.

By default, a P2P multi-area adjacency interface sends Hello packets at an interval of 10s.

Format

ospf timer hello interval multi-area { area-id | area-id-ipv4 }

undo ospf timer hello multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
interval

Specifies the interval at which the multi-area adjacency interface sends Hello packets.

The value is an integer ranging from 1 to 65535, in seconds.

Setting a value that is larger than 20 for the interval is recommended. If the interval is less than 20s, adjacencies may be interrupted.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

OSPF interfaces use Hello packets to establish and maintain adjacencies. A Hello packet includes information about the designated router (DR), backup designated router (BDR), timers, and known neighbors.

To set the interval at which Hello packets are sent, run the ospf timer hello multi-area command. The hello interval value will be added to Hello packets. A smaller hello interval value indicates a larger route cost and a higher speed in detecting topology changes. Ensure that parameters on the interface and those on its neighbor are the same.

Prerequisites

The ospf enable multi-area command has been run.

Precautions

The ospf timer hello multi-area command does not apply to null interfaces.

Example

# Configure the interval at which multi-area adjacency interface sends Hello packets to 20s.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf timer hello 20 multi-area 1

ospf timer poll

Function

The ospf timer poll command sets the poll interval at which Hello packets are sent on an NBMA network.

The undo ospf timer poll command restores the default value.

The default interval is 120 seconds.

Format

ospf timer poll interval

undo ospf timer poll

Parameters

Parameter Description Value
interval

Specifies a poll interval.

The value is an integer ranging from 1 to 3600, in seconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an NBMA network, if a neighbor is invalid, the device sends Hello packets to the neighbor at the poll interval set using the ospf timer poll command. The poll interval must be at least 4 times the Hello interval.

Precautions

The command cannot be run on a null interface.

Example

# Set the poll interval at which Hello packets are sent on an interface to 130 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf timer poll 130

ospf timer retransmit

Function

The ospf timer retransmit command sets the interval at which LSAs are retransmitted on an interface.

The undo ospf timer retransmit command restores the default value.

The default interval is 5 seconds.

Format

ospf timer retransmit interval

undo ospf timer retransmit

Parameters

Parameter Description Value
interval

Specifies an interval at which LSAs are retransmitted on an interface.

The value is an integer ranging from 1 to 3600, in seconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After sending an LSA to its neighbor, a device needs to wait for the LSAck packet from the neighbor. If the user does not receive the LSAck packet from the neighbor within the nth retransmission interval, the user retransmits the LSA to the neighbor. In the preceding information,

Interval at which LSAs are retransmitted for the first time = Configured interval at which LSAs are retransmitted,

Interval at which LSAs are retransmitted for the second time = Configured interval at which LSAs are retransmitted,

Interval at which LSAs are retransmitted for the third time = Configured interval at which LSAs are retransmitted,

Interval for retransmitting LSAs for the fourth time = Configured interval for retransmitting LSAs x 2,

Interval at which LSAs are retransmitted for the fifth time = Configured interval at which LSAs are retransmitted x 2^2,

... ...

Interval for retransmitting LSAs for the nth time = Configured interval for retransmitting LSAs, that is, interval x 2^(n-3)

If interval x 2^(n-3) is greater than 30, the interval for retransmitting LSAs for the nth time is 30.

If the configured interval for retransmitting LSAs is greater than 30s, the interval for retransmitting LSAs for the nth time is equal to the configured interval.

The interval for retransmitting LSAs between neighboring devices should not be set too small. Otherwise, LSAs are retransmitted unnecessarily.

Precautions

The command cannot be run on a null interface.

Example

# Specify the interval at which LSAs are retransmitted between the interface and the adjacent routers to 8 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf timer retransmit 8

ospf timer retransmit multi-area

Function

The ospf timer retransmit multi-area command configures an LSA retransmission interval on a multi-area adjacency interface.

The undo ospf timer retransmit multi-area command restores the default LSA retransmission interval.

By default, the LSA retransmission interval on multi-area adjacency interfaces is 5s.

Format

ospf timer retransmit interval multi-area { area-id | area-id-ipv4 }

undo ospf timer retransmit multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
interval

Specifies an LSA retransmission interval.

The value is an integer ranging from 1 to 3600, in seconds.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To set up an OSPF neighbor relationship with a neighbor, a device sends an LSA and waits for an LSAck packet from the neighbor. If the device does not receive an LSAck packet within the specified interval, it retransmits the LSA.

The LSA retransmission interval must not be too small; otherwise, unnecessary retransmission occurs.

Prerequisites

The ospf enable multi-area command has been run.

Precautions

The ospf timer retransmit multi-area command does not apply to null interfaces.

Example

# Set the LSA retransmission interval to 8s on multi-area adjacency interface.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf timer retransmit 8 multi-area 1

ospf timer wait

Function

The ospf timer wait command sets the wait timer on an OSPF interface.

The undo ospf timer wait command restores the default value.

By default, on broadcast interfaces, the wait interval is 40 seconds; on NBMA interfaces, it is 120 seconds.

Format

ospf timer wait interval

undo ospf timer wait

Parameters

Parameter Description Value
interval

Specifies the wait timer on an OSPF interface.

The value is an integer ranging from 1 to 235926000, in seconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To change the wait timer, run the ospfv3 timer wait command. If no Backup Seen event is received within the timer, the designated router (DR) election starts. Setting a proper value for the wait timer can slow down changes of the DR and the backup designated router (BDR) on the network, reducing network flapping. When setting the wait timer, note the following points:

  • The wait timer takes effect only on broadcast and NBMA interfaces.
  • The value of the wait timer cannot be greater than the value of the dead timer.

Precautions

The command cannot be run on a null interface.

Example

# Set the wait timer on an interface to 30 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf timer wait 30

ospf trans-delay

Function

The ospf trans-delay command sets the delay for transmitting LSAs on an interface.

The undo ospf trans-delay command restores the default value.

By default, the delay is 1 second.

Format

ospf trans-delay delayvalue

undo ospf trans-delay

Parameters

Parameter Description Value
delayvalue

Specifies the delay for transmitting LSAs on an interface.

The value is an integer ranging from 1 to 500, in seconds.

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The aging time of each LSA in the LSDB increases by one every second, but LSAs do not age during transmission. To configure an LSA transmission delay on a multi-area adjacency interface so that an extension period (the configured delay) is added to the LSAs to be sent, run the ospf trans-delay multi-area command. This configuration is extremely important on low-speed networks.

Precautions

The command cannot be run on a null interface.

Example

# Specify the delay for transmitting LSAs on an interface to 3 seconds.
<HUAWEI> system-view
[HUAWEI] vlan 100
[HUAWEI-vlan100] interface vlanif 100
[HUAWEI-Vlanif100] ospf trans-delay 3

ospf trans-delay multi-area

Function

The ospf trans-delay multi-area command configures an LSA transmission delay on a multi-area adjacency interface.

The undo ospf trans-delay multi-area command restores the default LSA transmission delay.

By default, the LSA transmission delay on multi-area adjacency interfaces is 1s.

Format

ospf trans-delay delayValue multi-area { area-id | area-id-ipv4 }

undo ospf trans-delay multi-area { area-id | area-id-ipv4 }

Parameters

Parameter Description Value
delayValue

Specifies an LSA transmission delay.

The value is an integer ranging from 1 to 500, in seconds.
area-id

Specifies the ID of an OSPF area. The value is an integer.

The value can be a decimal integer ranging from 0 to 4294967295 or in the format of an IP address.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255

Views

100GE interface view, 10GE interface view, 25GE sub-interface view, 25GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view, Multi-GE sub-interface view, Multi-GE interface view, Tunnel interface view, VBDIF interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The aging time of each LSA in the LSDB increases by one every second, but LSAs do not age during transmission. To configure an LSA transmission delay on a multi-area adjacency interface so that an extension period (the configured delay) is added to the LSAs to be sent, run the ospf trans-delay multi-area command. This configuration is extremely important on low-speed networks.

Prerequisites

The ospf enable multi-area command has been run.

Precautions

The ospf trans-delay multi-area command does not apply to null interfaces.

Example

# Set the LSA transmission delay on multi-area adjacency interface to 3s.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] area 1
[HUAWEI-ospf-1-area-0.0.0.1] quit
[HUAWEI-ospf-1] quit
[HUAWEI] vlan 1
[HUAWEI-vlan1] quit
[HUAWEI] interface Vlanif 1
[HUAWEI-Vlanif1] ospf enable 1 area 0
[HUAWEI-Vlanif1] ospf enable multi-area 1
[HUAWEI-Vlanif1] ospf trans-delay 3 multi-area 1

ospf valid-ttl-hops

Function

The ospf valid-ttl-hops command enables OSPF GTSM and set the TTL value to be checked.

The undo ospf valid-ttl-hops command disables OSPF GTSM.

By default, OSPF GTSM is disabled.

Format

ospf valid-ttl-hops ttl [ nonstandard-multicast ] [ vpn-instance vpn-instance-name ]

undo ospf valid-ttl-hops [ ttl ] [ nonstandard-multicast ] [ vpn-instance vpn-instance-name ]

Parameters

Parameter Description Value
ttl

Specifies the TTL value to be checked.

The value is an integer that ranges from 1 to 255. If you specify the parameter hops, the valid range of the TTL value in the packet to be checked is [ 255-hops+1, 255 ].
nonstandard-multicast

Specifies the GTSM configuration is also valid for multicast packets.

When the.

nonstandard-multicast parameter is configured:

  • The TTL values of the multicast packets which will be sent are set to 255.
  • Received multicast packets are not checked.

-
vpn-instance vpn-instance-name

Specifies the name of a VPN instance. If this parameter is specified, it indicates that only the TTL value of the packets in the specified VPN instance needs to be checked.

The value is a string of 1 to 31 case-sensitive characters. It cannot contain spaces. The VPN instance name cannot be _public_. If the character string is quoted by double quotation marks, the character string can contain spaces.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an OSPF network requires high security, you can configure GTSM to improve network security. GTSM defends against attacks through TTL detection. If an attacker continuously sends simulated OSPF unicast packets to a device, the device receives these packets and finds that they are local packets. Then, the device directly sends the packets to OSPF on the control plane for processing, the device does not check the validity of these packets. As a result, the control plane of the device is busy processing these packets, and the CPU usage is high. GTSM protects a device by checking whether the TTL value in the IP packet header is within a pre-defined range to enhance system security.

This command can be used to enable OSPF GTSM and check the TTL value.

  • After the ospf valid-ttl-hops command is run, OSPF GTSM can be enabled, regardless of the public network or VPN.
  • If vpn-instance is specified in the command, only the TTL values of OSPF packets in a specified VPN instance are checked, performs the default action (configured using the gtsm default-action command) on OSPF packets that do not match GTSM policies in the public network instance and other VPN instances. If vpn-instance is not specified, only the TTL values of OSPF packets in the public network instance are checked, and the default action is taken on OSPF packets that do not match the GTSM policy in the private network instance.

Precautions

  • If a VPN instance is specified in the ospf valid-ttl-hops command and an interface is bound to the VPN instance, all the unicast packets sent to this interface are discarded when the set TTL value is smaller than the actual TTL value on the network.
  • If a virtual link or sham link is configured, the configured TTL value must be the same as the actual TTL value. That is, the number of devices that the virtual link or sham link passes through is counted. Otherwise, packets sent from neighbors over the virtual link or sham link are discarded.
  • The default TTL value of OSPF packets sent by a device is 1. After the ospf valid-ttl-hops command is run, the TTL value of OSPF packets sent by the device changes to 255, if the ospf valid-ttl-hops command is run only on one end of a neighbor, OSPF unicast packets may fail to be forwarded. Although the established OSPF neighbor relationship is not affected, the new OSPF neighbor relationship cannot go Up.
  • After the ospf valid-ttl-hops hops command is run, the valid TTL range of the detected packet changes to [255-hops+1, 255]. For example, if the value of hops is 5, the received OSPF packet is valid only when the TTL value of the packet ranges from 251 to 255.

Example

# Enable OSPF GTSM, and set the maximum number of TTL hops to 5 for the packets that can be received from the public network.
<HUAWEI> system-view
[HUAWEI] ospf valid-ttl-hops 5

peer (OSPF view)

Function

The peer command sets an IP address and a DR priority for an adjacent device on an NBMA network.

The undo peer command cancels the configured IP address and DR priority.

By default, IP address and a DR priority for an adjacent device on an NBMA network is not set.

Format

peer ip-address [ dr-priority priority ]

undo peer ip-address

Parameters

Parameter Description Value
ip-address

Specifies the IP address for an adjacent router.

Dotted decimal notation.
dr-priority priority

Sets a priority for an adjacent router for DR election.

The value is an integer ranging from 0 to 255. The default value is 1.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an NBMA network (such as an X.25 network), the entire network can be fully meshed if adjacent router mapping is configured. With the mapping, there is a virtual link between any two routers. In this case, the OSPF network can be considered as a broadcast network where a DR or BDR can be selected. However, adjacent routers cannot be detected dynamically by broadcasting Hello packets. To address this problem, run the peer command to specify an IP address and a DR priority for each adjacent router.

Example

# Set the IP address of the adjacent router to 1.1.1.1 on an NBMA network.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] peer 1.1.1.1

preference (OSPF view)

Function

The preference command sets a priority for OSPF routes.

The undo preference command restores the default value.

By default, the priority of OSPF routes is 10. When ASE is specified, the default value is 150.

Format

preference { preferencevalue | { route-policy route-policy-name } } *

preference { ase | intra | inter } { preferencevalue | { route-policy route-policy-name } } *

undo preference

undo preference { ase | intra | inter }

Parameters

Parameter Description Value
preferencevalue

Specifies a priority of OSPF routes.

The smaller the priority value, the higher the priority.

The value is an integer ranging from 1 to 255.
route-policy route-policy-name

Specifies the name of a routing policy.

The value is a string of 1 to 200 case-sensitive characters without spaces. The character string can contain spaces if it is enclosed with double quotation marks (").
ase

Sets a priority for AS external routes.

-
intra

Sets a priority for intra-area routes.

-
inter

Sets a priority for inter-area routes.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a device runs multiple dynamic routing protocols at the same time, routing information may be shared and selected among the routing protocols. The system sets a default preference for each routing protocol. If different protocols have routes to the same destination, the route with a higher priority is selected. To set a preference for an OSPF route, run this command.

When configuring the route-policy parameter, you can set the preference for matched routes by using the routing policy.

  • If the apply preference clause is configured for the route-policy, the route preference is as follows:
  • Matched routes: The preference is set by the apply clause.
  • Routes that do not match the route-policy: The preference of these routes is the one set using the preference command.

    In the following example, the preference of the routes that match the route-policy abc is set to 50 and the preference of the routes that do not match the route-policy abc is set to 30.

    route-policy abc permit node 1

    if-match cost 20

    apply preference 50

    ospf 1

    preference 30 route-policy abc
  • If the apply preference clause is not configured in the route-policy, the preference of routes is the one set by the preference command.

    In the above example, if the apply preference 50 clause is not included in the policy abc, the preference of all routes is set to 30.

Configuration Impact

When there are routes discovered by multiple routing protocols on the same router, you can enable the router to prefer OSPF routes by setting highest priority for them.

Example

# Set the priority of external routes in OSPF process 200 to 130.
<HUAWEI> system-view
[HUAWEI] ospf 200
[HUAWEI-ospf-200] preference ase 130
# Set the priority of routes in OSPF process 100 to 150.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] preference 150

prefix-priority (OSPF view)

Function

The prefix-priority command sets a convergence priority for OSPF routes.

The undo prefix-priority command restores the default value.

By default, in an OSPF routing table, the convergence priority of public network 32-bit host routes and default routes is medium, and the convergence priority of other OSPF routes is low; in an IP routing table, the convergence priority of public network 32-bit host routes and default routes is high, and the convergence priority of other OSPFv3 routes is medium.

Format

prefix-priority { critical | high | medium } ip-prefix ip-prefix-name

undo prefix-priority { critical | high | medium }

Parameters

Parameter Description Value
critical

Sets the convergence priority of OSPF routes to critical.

-
high

Sets the convergence priority of OSPFv3 routes to high.

-
medium

Sets the convergence priority of OSPFv3 routes to medium.

-
ip-prefix ip-prefix-name

Specifies the prefix list name.

The value is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To set the convergence priority of OSPF routes based on a specified IP prefix list, run the prefix-priority command. The command takes effect on the public network only.

After the prefix-priority command is used in the OSPF view, OSPF route calculation, link-state advertisement (LSA) flooding, and LSDB synchronization can be implemented according to the configured priority. Therefore, route convergence can be controlled.

Configuration Impact

The convergence priorities of OSPF routes can be critical, high, medium, low, and very-low. The priorities in the corresponding IP routing table are critical, high, high, medium, and low. The priorities are listed in descending order.When an LSA meets multiple priorities, the highest priority takes effect.

OSPF calculates LSAs in the sequence of intra-area routes, inter-area routes, and AS external routes. This command enables OSPF to calculate the three types of routes separately according to the specified route calculation priorities. Convergence priorities are critical, high, medium, low and very-low. To speed up the processing of LSAs with the higher priority, during LSA flooding, the LSAs need to be placed into the corresponding critical, high, medium, low and very-low queues according to priorities.

Precautions

By default, the convergence priorities of public OSPF host routes, direct routes, static routes, and other protocol (such as BGP and RIP) routes are medium, high, medium, and low respectively. On the public network, the convergence priority of OSPF 32-bit host routes is medium.

Example

# Set the convergence priority of OSPF routes of 10.0.0.0/8 to critical.
<HUAWEI> system-view
[HUAWEI] ip ip-prefix critical-prefix index 10 permit 10.0.0.0 8
[HUAWEI] ospf 1
[HUAWEI-ospf-1] prefix-priority critical ip-prefix critical-prefix

reset ospf counters

Function

The reset ospf counters command clears OSPF statistics.

Format

reset ospf [ process-id ] counters [ neighbor [ interface-name [ all-areas | area { area-id | area-id-ipv4 } ] | interface-type interface-number [ all-areas | area { area-id | area-id-ipv4 } ] ] [ router-id ] ]

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
neighbor

Indicates a neighbor.

-
interface-name

Specifies the name of an interface.

-
all-areas

Clears statistics of all OSPF areas.

-
area area-id

Specifies the ID of an OSPF area. The value is an integer.

The value is a decimal integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies the ID of an OSPF area, in the format of an IP address.

The value is in the format X.X.X.X, where each X represents a value from 0 to 255
interface-type

Interface type.

-
interface-number

Specifies the number of an interface based on which information about VLANs in which users go online dynamically is to be displayed.

-
router-id

The router ID of a neighbor.

The value is in dotted decimal notation.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

To reset OSPF statistics, run the reset ospf counters command. Clearing OSPF statistics does not affect OSPF services.

Once deleted, statistics cannot be restored. Therefore, exercise caution when deleting statistics.

Example

# Reset OSPF statistics.
<HUAWEI> reset ospf counters

reset ospf counters maxage-lsa

Function

The reset ospf counters maxage-lsa command deletes the statistics about router LSAs that have reached the aging time.

Format

reset ospf [ process-id ] counters maxage-lsa

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

After the statistics about router LSAs that have reached the aging time are deleted, OSPF services are not affected.

Note:

Statistics cannot be restored after being deleted. Therefore, exercise caution when running the command.

Example

# Delete the statistics about router LSAs that have reached the aging time.
<HUAWEI> reset ospf counters maxage-lsa

reset ospf frr

Function

The reset ospf frr command resets OSPF IP FRR.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

reset ospf [ process-id ] frr

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process. If this parameter is not specified, FRR is reset in all OSPF processes.

The value is an integer ranging from 1 to 4294967295.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

This command is a maintenance command. It can be used to forcibly reset FRR without deleting the FRR configuration.

Prerequisites

FRR has been configured in an OSPF process.

Configuration Impact

OSPF IP FRR calculation does not affect the normal running of OSPF.

Example

# Reset FRR in an OSPF process.
<HUAWEI> reset ospf frr

reset ospf peer

Function

The reset ospf peer command restarts OSPF neighbors.

Format

reset ospf [ process-id ] peer [ interface-name [ all-areas | area { area-id | area-id-address } ] | interface-type interface-number [ all-areas | area { area-id | area-id-address } ] ] router-id

Parameters

Parameter Description Value
process-id

Specifies an OSPF process ID. If the parameter is not specified, all OSPF processes are restarted.

The value is an integer ranging from 1 to 4294967295.
interface-name

Specifies the name of an interface.

-
all-areas

Clears statistics of all OSPF areas.

-
area area-id

Specifies an area ID in the format of a decimal integer.

The value is an integer ranging from 0 to 4294967295.
area-id-address

Specifies an area ID in the format of an IP address.

The value is in dotted decimal notation.
interface-type

Interface type.

-
interface-number

Specifies the number of an interface based on which information about VLANs in which users go online dynamically is to be displayed.

-
router-id

Specifies a router ID in the format of an IPv4 address.

The value is in dotted decimal notation.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

To restart OSPF neighbors, run the reset ospf peer command.

Once deleted, statistics cannot be restored. Therefore, exercise caution when deleting statistics.

Example

# Restart OSPF neighbors.
<HUAWEI> reset ospf peer 1.1.1.1

reset ospf process

Function

The reset ospf process command restarts an OSPF process.

Format

reset ospf [ process-id ] process

Parameters

Parameter Description Value
process-id

Specifies an OSPF process ID.

If the parameter is not specified, all OSPF processes are restarted.

The value is an integer ranging from 1 to 4294967295.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

To restart an OSPF process, run the reset ospf process command.

If OSPF connections are reset, OSPF neighbor relationships will be interrupted and the original information cannot be restored. Exercise caution when using the reset ospf command.

Configuration Impact

After the reset ospf process command is run, the following situations may occur:

  • If the router ID is changed, a new router ID will take affect.
  • The DR and BDR are reselected.
  • OSPF configuration will not be lost before OSPF restarts.

Example

# Restart all OSPF processes.
<HUAWEI> reset ospf process

reset ospf redistribution

Function

The reset ospf redistribution command re-imports OSPF routes.

Format

reset ospf [ process-id ] redistribution

Parameters

Parameter Description Value
process-id

Specifies the ID of an OSPF process. If this parameter is not specified, OSPF routes are re-imported in all OSPF processes.

The value is an integer ranging from 1 to 4294967295.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

To re-import OSPF routes, run the reset ospf redistribution command.

Example

# Re-import OSPF routes in OSPF process 1.
<HUAWEI> reset ospf 1 redistribution

reset ospf spf

Function

The reset ospf spf command enables a device to recalculate OSPF routes.

Format

reset ospf [ process-id ] spf

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

To enable a device to recalculate OSPF routes, run the reset ospf spf command. This command improves maintainability and does not affect services.

Example

# Reset OSPF route calculation.
<HUAWEI> reset ospf spf

reset ospf suppress-flapping peer

Function

The reset ospf suppress-flapping peer command forces an interface to exit from OSPF neighbor relationship flapping suppression.

Format

reset ospf process-id suppress-flapping peer [ interface-name [ all-areas | area { area-id | area-id-ipv4 } ] | interface-type interface-number [ all-areas | area { area-id | area-id-ipv4 } ] ]

reset ospf process-id suppress-flapping peer [ interface-name [ all-areas | area { area-id | area-id-ipv4 } ] | interface-type interface-number [ all-areas | area { area-id | area-id-ipv4 } ] ] notify-peer

Parameters

Parameter Description Value
process-id

process-id Specifies the ID of an OSPF process.

The value is an integer ranging from 1 to 4294967295.
all-areas

Clears statistics of all OSPF areas.

-
area area-id

Specifies an area ID in the format of a decimal integer.

The value is an integer ranging from 0 to 4294967295.
area-id-ipv4

Specifies an area ID in the format of an IP address.

The value is in dotted decimal notation.
interface-type

Specifies the type of an interface.

-
interface-number

Specifies an interface number.

-
notify-peer

Instructs neighbors to exit from OSPF neighbor relationship flapping suppression too.

-

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

Interfaces exit from flapping suppression in the following scenarios:

  • The suppression timer expires.
  • The corresponding OSPF process is reset.
  • The reset ospf suppress-flapping peer command is run.
  • An OSPF neighbor is reset using the reset ospf peer command.
  • OSPF neighbor relationship flapping suppression is disabled globally using the suppress-flapping peer disable command in the OSPF view.

    If notify-peer is specified when the reset ospf suppress-flapping peer command is run on a device, the device sends Hello packets in which HelloInterval and RouterDeadInterval are 0s to its neighbors to instruct the neighbors to exit from OSPF neighbor relationship flapping suppression too. If the neighbors fail to receive such Hello packets, the function of notify-peer does not take effect. To force the neighbors to exit from OSPF neighbor relationship flapping suppression, run the reset ospf suppress-flapping peer command on them.

    The OSPF process or the specified interface exits from flapping suppression in the following scenarios:
  • The suppression timer expires.
  • The OSPF process is reset.
  • The reset ospf suppress-flapping peer command is run.
  • An OSPF neighbor is reset using the reset ospf peer command.
  • OSPF neighbor relationship flapping suppression is disabled globally using the suppress-flapping peer disable (OSPF) command.

    If notify-peer is specified when the reset ospf suppress-flapping peer command is run on a device, the device sends Hello packets in which HelloInterval and RouterDeadInterval are 0s to its neighbors to instruct the neighbors to exit from OSPF neighbor relationship flapping suppression too. If the neighbors fail to receive such Hello packets, the function of notify-peer does not take effect. To force the neighbors to exit from OSPF neighbor relationship flapping suppression, run the reset ospf suppress-flapping peer command on them.

Example

# Force interfaces to exit from OSPF neighbor relationship flapping suppression.
<HUAWEI> reset ospf 1 suppress-flapping peer
# Force an OSPF multi-area adjacency interface to exit from OSPF neighbor relationship flapping suppression.
<HUAWEI> reset ospf 1 suppress-flapping peer 10GE1/0/1 area 1

retransmission-limit

Function

The retransmission-limit command sets the maximum number of retransmissions.

The undo retransmission-limit command disables the retransmission limit.

By default, the number of retransmissions is not set.

Format

retransmission-limit max-number

retransmission-limit

undo retransmission-limit

Parameters

Parameter Description Value
max-number

Specifies the maximum number of retransmissions.

The value is an integer ranging from 2 to 255. The default value is 30.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The retransmission-limit command can be used to enable retransmission limit for OSPF (RL-for OSPF) to prevent dead loops caused by repeated transmissions when neighbors cannot receive packets.

Configuration Impact

The OSPF retransmission limit takes effect on the following packets:

  • DD packets
  • Update packets
  • Request packets

    If the three types of packets cannot receive response packets, enable RL-for OSPF, limit the number of retransmissions, and disconnect the neighbor when the number of retransmissions exceeds the specified value.

Example

# Enable OSPF retransmission limit and set the maximum number of retransmissions to 40.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] retransmission-limit 40

rfc1583 compatible

Function

The rfc1583 compatible command configures a device to comply with the route selection rules defined in RFC 1583. This configuration facilitates OSPF route selection.

The undo rfc1583 compatible command configures a device to comply with the route selection rules defined in RFC 2328.

The rfc1583 compatible command configures a device to comply with the route selection rules defined in RFC 1583. This configuration facilitates OSPFv3 route selection.

The undo rfc1583 compatible command configures a device to comply with the route selection rules defined in RFC 5340.

By default, OSPF configures the rules defined in RFC 1583.

By default, OSPFv3 configures the rules defined in RFC 5340.

Format

rfc1583 compatible

undo rfc1583 compatible

Parameters

None

Views

OSPFv3 view, OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

RFC 2328 and RFC 1583 define two different route selection rules for the OSPF protocol. When enabling OSPF, you need to configure the route selection rules for the OSPF domain according to the networking plan to ensure that the route selection rules for the OSPF domain are the same. For example, OSPF supports the route selection rules defined in RFC 1583 by default. If other devices in the OSPF domain support the route selection rules defined in RFC 2328, run the undo rfc1583 compatible command to use the route selection rules defined in RFC 2328.

RFC 5340 and RFC 1583 define two types of OSPFv3 route selection rules. When enabling OSPFv3, configure the same route selection rules for OSPFv3 domains based on the networking plan. For example, OSPFv3 supports the route selection rules defined in RFC 5340 by default. If other devices in the OSPFv3 domain support the route selection rules defined in RFC 1583, run the rfc1583 compatible command to use the route selection rules defined in RFC 1583.

When multiple AS-External LSAs advertise routes to the same destination, RFC 1583, RFC 2328, and RFC 5340 define different rules for selecting the optimal route. RFC 1583 prefers intra-area routes. RFC 2328 and RFC 5340 prefer intra-area routes in non-backbone areas. Selecting RFC 2328 or 5340 can reduce the burden on the backbone area.

Example

# Configure a device to comply with the route selection rules defined in RFC 2328.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] undo rfc1583 compatible
# Configure a device to comply with the route selection rules defined in RFC 1583.
<HUAWEI> system-view
[HUAWEI] ospfv3 1
[HUAWEI-ospfv3-1] rfc1583 compatible

rfc1583 compatible different-area-path prefer lower-cost

Function

The rfc1583 compatible different-area-path prefer lower-cost command changes the route selection rule in RFC 1583-compatible mode to be the same as the default route selection rule on the ASBR. That is, if the area IDs of intra and inter routes are different, the route with the smaller cost is preferred; if the area IDs of intra and inter routes are the same, the route with the larger area ID is preferred.

The undo rfc1583 compatible different-area-path prefer lower-cost command restores the default route selection rule in RFC 1583 compatible mode.

The rfc1583 non-compatible backbone-area-path prefer intra command changes the route selection rule in RFC 1583-incompatible mode to be the same as the default route selection rule on the ASBR. That is, when the area IDs of the intra and inter paths are the same and both areas are backbone areas, the intra-ASBR path is preferred.

The undo rfc1583 non-compatible backbone-area-path prefer intra command restores the route selection rule in RFC 1583 incompatible mode to the default rule.

By default, OSPF route selection rules are not configured.

Format

rfc1583 compatible different-area-path prefer lower-cost

rfc1583 non-compatible backbone-area-path prefer intra

undo rfc1583 compatible different-area-path prefer lower-cost

undo rfc1583 non-compatible backbone-area-path prefer intra

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Devices of different vendors or different series of devices of the same vendor are deployed on the same network. For the intra- and inter-route paths to the ASBR, the route selection rules may be different in RFC 1583-compatible and RFC 1583-incompatible scenarios. The different route selection rules may cause loops. To prevent routing loops, you can use a command to change the route selection rule to the default rule on the ASBR.

Example

# Configure the device in RFC 1583 compatibility mode to preferentially select the path with the smallest cost.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] rfc1583 compatible
[HUAWEI-ospf-1] rfc1583 compatible different-area-path prefer lower-cost
# Configure the device in RFC 1583 non-compatibility mode to preferentially select intra-area paths.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] undo rfc1583 compatible
[HUAWEI-ospf-1] rfc1583 non-compatible backbone-area-path prefer intra

route loop-detect ospf enable

Function

The route loop-detect ospf enable command enables loop detection for routes imported into OSPF.

The undo route loop-detect ospf enable command disables loop detection for routes imported into OSPF.

By default, loop detection is disabled for routes imported into OSPF.

Format

route loop-detect ospf enable

undo route loop-detect ospf enable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When an OSPF process imports routes, routing loops may occur. You can run the route loop-detect ospf enable command to enable loop detection for routes imported into OSPF. When a device detects that it has imported a route advertised by itself, the device advertises a large link cost for the route so that other devices can preferentially select another path after learning the route. This prevents routing loops.

Precautions

OSPF uses opaque LSAs to detect loops of imported routes. Therefore, the opaque LSA capability must be enabled using the opaque-capability enable command.

After a loop is removed, the loop cannot be automatically removed and the alarm cannot be automatically cleared. Manual intervention is required. For example, after a routing policy or route tag is correctly configured, run the clear route loop-detect ospf alarm-state command to exit the loop state and clear the alarm.

A single process supports loop detection for a maximum of 100,000 routes. If more than 100,000 routes are imported, loops cannot be detected for the excess routes. The system checks the number of routes for loop detection at 03:00 every day. If the number of routes for loop detection is less than 100,000, the system performs loop detection on the previous excess imported routes. The maximum number of imported routes for loop detection is still 100,000.

During the period when a large cost is advertised for looped routes, the apply cost command does not take effect.

Summary routes and NSSA routes do not support loop detection.

The default route advertised using the default-route-advertise command supports only loop detection and does not support self-healing.

Only loops caused by inter-process route import between two devices can be detected. If more than two devices import routes between processes, loops cannot be detected.

Router ID conflicts are not supported, including intra-AS and inter-AS router ID conflicts. A router ID conflict may trigger incorrect detection.

If the OSPF process that imports routes also calculates routes with the same prefix and the calculated routes work in load balancing mode with the imported routes across processes, loops cannot be detected.

Example

# Enable loop detection.
<HUAWEI> system-view
[HUAWEI] route loop-detect ospf enable

route-tag (OSPF view)

Function

The route-tag command sets the VPN route tag for imported VPN routes.

The undo route-tag command restores the default setting.

By default, the first two bytes of a tag value are fixed at 0xD000, and the last two bytes are the local BGP AS number. For example, if the local BGP AS number is 100, the default tag value in decimal notation is 3489661028; if the BGP AS number is greater than 65535, the tag value is 0, and you can manually change the tag value. If BGP is not configured, the default tag value is 0.

Format

route-tag tag

route-tag disable

undo route-tag

Parameters

Parameter Description Value
tag

Specifies the VPN route tag.

The value is an integer ranging from 0 to 4294967295.
disable

Indicates that the VPN route tag is not used to detect loops.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The route-tag command can only be used in VPN scenarios to prevent loops on Type-5 and Type-7 LSAs when a CE is dual-homed to PEs.

In a networking where a CE is dual-homed to PEs, PE1 generates Type-5 and Type-7 LSAs based on the imported BGP routes and sends the LSAs to the CE. Then the CE sends the LSAs to PE2. Because OSPF routes have higher priorities over BGP routes, PE2 replaces BGP routes with OSPF routes, causing loops. After the route-tag command is run, if the tag values of the PE and an LSA are the same, the PE will neglect the LSA and a loop is prevented.

Precautions

  • Configuring the same VPN route tag on the PEs within the same area is recommended.
  • Different OSPF processes can be configured with the same VPN route tag.

    The priority of VPN route tags varies with the command.
  • The priority of the VPN route tag configured using the import-route command is the highest.
  • The priority of the VPN route tag configured using the route-tag command is medium.
  • The priority of the VPN route tag configured using the default tag command is the lowest.

Example

# Set the VPN route tag for OSPF process 100 to 100 in the VPN instance named huawei.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv4-family
[HUAWEI-vpn-instance-huawei-af-ipv4] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospf 100 vpn-instance huawei
[HUAWEI-ospf-100] route-tag 100

safe-sync enable

Function

The safe-sync enable command enables secure synchronization.

The undo safe-sync enable command disables secure synchronization.

By default, secure synchronization is not enabled.

Format

safe-sync enable

undo safe-sync enable

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In OSPF-BGP association, the router LSA originated on a device in the stub-router state is discarded after the device is restarted. Due to the limit on the LSA retransmission interval, its neighbor still uses the previous router LSA to calculate the route that passes through the device. As a result, temporary packet loss occurs before the device establishes the neighbor relationship with the peer end.

After secure synchronization is configured on a device to be restarted, when the device synchronizes the LSDB with the peer end, it deletes or updates the LSA that is received from the peer end if the LSA was generated by itself. Then, the neighbor state machines of the restarted device and its peer end can reach the Full state, and the neighbor relationship between them can be established.

Example

# Enable secure synchronization in OSPF process 100.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] safe-sync enable

sham-hello enable (OSPF view)

Function

The sham-hello enable command enables the OSPF sham-hello function.

The undo sham-hello command disables the OSPF sham-hello function.

By default, the OSPF sham-hello function is disabled.

Format

sham-hello enable

undo sham-hello

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To enable the OSPF sham-hello function, run the sham-hello enable command. After the command is run, the device can maintain neighbor relationships through not only Hello packets but also LSU and LSAck packets, which strengthens OSPF neighbor relationships.

Example

# Enable the OSPF sham-hello function.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] sham-hello enable

silent-interface (OSPF view)

Function

The silent-interface command disables an interface from receiving and sending OSPF packets.

The undo silent-interface command restores the default setting.

By default, an interface can receive and send OSPF packets.

Format

silent-interface { all | { interface-name | interface-type interface-number } }

undo silent-interface { all | { interface-name | interface-type interface-number } }

Parameters

Parameter Description Value
all

Indicates all interfaces in a specified process.

-
interface-name

Specifies an interface name.

-
interface-type

Specifies the type of an interface.

-
interface-number

Specifies the interface number.

-

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To prevent the local router from sending its OSPF routing information to other routers on a network and from receiving routing update information advertised by other routers, run the silent-interface command.

Disabling interfaces from receiving or sending OSPF packets is a solution to routing loops.

Configuration Impact

After an OSPF interface is set to be in the silent state, the interface can still advertise its direct routes. Hello packets on the interface, however, will be blocked, and no neighbor relationship can be established on the interface. This can enhance the networking adaptability of OSPF and reduce the consumption of system resources.

Precautions

If the undo silent-interface command has been run in the current process, running the silent-interface all command causes the undo silent-interface command configuration to be deleted. As a result, the OSPF neighbor relationship established using the interface specified in the undo silent-interface command goes down.

Example

# Disable an interface from sending or receiving OSPF packets.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] silent-interface 10GE1/0/1

spf-schedule-interval

Function

The spf-schedule-interval command sets the interval for OSPF to calculate routes.

The undo spf-schedule-interval command restores the default setting.

By default, the intelligent timer is enabled. The maximum interval for the SPF calculation is 5000 ms, the initial interval is 50 ms, and the Holdtime interval is 200 ms.

Format

spf-schedule-interval interval1

spf-schedule-interval intelligent-timer max-interval start-interval hold-interval [ conservative ]

spf-schedule-interval millisecond interval2

undo spf-schedule-interval

Parameters

Parameter Description Value
interval1

Specifies the interval for OSPF to perform the SPF calculation.

The value is an integer that ranges from 1 to 10, in seconds.
intelligent-timer

Sets the interval for the SPF calculation of OSPF through an intelligent timer.

-
max-interval

Specifies the maximum interval for OSPF to perform the SPF calculation.

The value ranges from 1 to 300000, in milliseconds.
start-interval

Specifies the initial interval for OSPF to perform the SPF calculation.

The value is an integer ranging from 1 to 60000, in milliseconds.
hold-interval

Specifies the Holdtime interval for OSPF to perform the SPF calculation.

The value is an integer ranging from 1 to 60000, in milliseconds.
conservative

Enables conservative mode for OSPF to perform the SPF calculation.

-
millisecond interval2

Specifies the interval for OSPF to perform the SPF calculation.

The value ranges from 1 to 10000, in milliseconds.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Based on the LSDB, the device that runs OSPF calculates the SPT with itself as the root based on the SPF arithmetic, and determines the next hop to the destination network according to the SPT. By adjusting SPF calculation interval, you can reduce bandwidth and router resources that are consumed by the frequent change of the network.

On a network where the convergence time of routes is required to be shorter, set millisecond as the unit of interval to increase the frequency of calculating routes. This increases route convergence. In other networking environments, the default value is recommended.

When an OSPF LSDB changes, shortest paths must be recalculated. If a network changes frequently, the shortest path is calculated accordingly, resulting in excessive consumption of system resources, affecting device efficiency. You can configure an intelligent timer and set a proper interval for the SPF calculation to prevent the excessive consumption of device memory and bandwidth resources.

If the intelligent timer is enabled using intelligent-timer, the interval for SPF calculation is as follows:

  • The initial interval for SPF calculation is specified by the parameter start-interval.
  • The interval for the SPF calculation for the nth (n≥2) time is equal to hold-interval x 2^(n-2).
  • When the interval specified by hold-interval x 2^(n-2) reaches the maximum interval specified by max-interval, OSPF always uses the maximum interval for SPF calculation.
  • If the interval between the last SPF calculation and the current SPF calculation exceeds max-interval and no flapping occurs within max-interval, the intelligent timer exits.
  • If no flapping occurs in the previous SPF calculation but flapping occurs in the current SPF calculation, the SPF calculation is delayed by start-interval. After the SPF calculation is complete, the current interval is used.

    If a common timer is used, the interval for the SPF calculation is as follows:
  • The interval for the first SPF calculation is 0. That is, the SPF calculation is performed immediately after the first route change is received.
  • The interval for the SPF calculation for the nth (n≥2) time is specified by interval1 or millisecond interval2.

Example

# Set the interval for OSPF to calculate routes to 6s.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] spf-schedule-interval 6

stub (OSPF area view)

Function

The stub command configures an area as a stub area.

The undo stub command cancels the configuration.

By default, no area is configured as a stub area.

Format

stub [ no-summary | { default-route-advertise backbone-peer-ignore } ] *

undo stub

Parameters

Parameter Description Value
no-summary

Prevents the ABR from sending Summary LSAs to the stub area.

-
default-route-advertise

Controls the default route's advertisement.

-
backbone-peer-ignore

Prevents the ABR from checking the neighbor status.

-

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

There are two stub area-related commands: stub and default-cost (OSPF). If you want to configure one area as a stub area, run the stub command on all devices in the area.

The default-cost (OSPF) command is used to specify the cost of the default summary route that the ABR sends to the stub area. The command takes effect only when it is run on an ABR.

On an ABR, you can configure no-summary in the stub command to prevent Type 3 LSAs from entering the stub area to which the ABR connects.

If default-route-advertise and backbone-peer-ignore are configured in the command, the ABR is prevented from checking the neighbor status when it generates a default Type 3 LSA and advertises it to the stub area.

Example

# Configure OSPF area 1 as a stub area.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 1
[HUAWEI-ospf-100-area-0.0.0.1] stub no-summary default-route-advertise backbone-peer-ignore

stub-router

Function

The stub-router command configures a stub device.

The undo stub-router command restores the default configuration.

By default, no router is configured as a stub router.

Format

stub-router [ [ on-startup [ interval ] ] | [ include-stub ] | [ external-lsa [ externallsa-metric ] ] | [ summary-lsa [ summarylsa-metric ] ] ] *

undo stub-router

Parameters

Parameter Description Value
on-startup interval

Specifies an interval for the device to remain as a stub router after being restarted.

The value is an integer ranging from 5 to 65535, in seconds. The default value is 500 seconds.
include-stub

Sets the maximum cost 65535 for the stub links in router-LSAs.

-
external-lsa externallsa-metric

Advertises external-LSAs with the configured or default maximum cost.

The value is an integer ranging from 1 to 16777215. The default value is 16711680.
summary-lsa summarylsa-metric

Advertises summary-LSAs with the configured or default maximum cost.

The value is an integer ranging from 1 to 16777215. The default value is 16711680.

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the stub-router command is run on a device, the device instructs other OSPF devices not to use the stub device to forward data by increasing the cost (65535) of the links in the device-LSA generated by the device. Because the cost is not infinite, other devices can still have a route to the local stub device. In the device-LSA generated by the stub device, when the stub device functions as a transit node, the cost of all links is set to 65535.

For stub links generated by the local device (for example, routes to the local loopback interface), the default costs of external LSAs and summary LSAs remain unchanged.

To change the cost of the local stub link, add the include-stub parameter.

To change the cost of the local external LSA, add the external-lsa parameter.

To change the cost of the local summary LSA, add the summary-lsa parameter.

Example

# Configure the stub router.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] stub-router
# Configure the stub router to advertise external-LSAs and summary-LSAs with cost 16777214.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] stub-router on-startup 65535 include-stub external-lsa 16777214 summary-lsa 16777214

suppress-flapping peer disable (OSPF view)

Function

The suppress-flapping peer disable command disables OSPF neighbor relationship flapping suppression globally.

The undo suppress-flapping peer disable command enables OSPF neighbor relationship flapping suppression globally.

By default, OSPF neighbor relationship flapping suppression is enabled globally.

Format

suppress-flapping peer disable

undo suppress-flapping peer disable

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an interface carrying OSPF services alternates between Up and Down, OSPF neighbor relationship flapping occurs on the interface. During the flapping, OSPF frequently sends Hello packets to reestablish the neighbor relationship, synchronizes LSDBs, and recalculates routes. In this process, a large number of packets are exchanged, adversely affecting neighbor relationship stability, OSPF services, and other OSPF-dependent services, such as BGP. OSPF neighbor relationship flapping suppression can address this problem by delaying OSPF neighbor relationship reestablishment or preventing service traffic from passing through flapping links.

By default, OSPF neighbor relationship flapping suppression is enabled globally. To disable this function globally, run the suppress-flapping peer disable command.

Example

# Disable neighbor relationship flapping suppression globally.
<HUAWEI> system-view
[HUAWEI] ospf
[HUAWEI-ospf-1] suppress-flapping peer disable

suppress-reachability

Function

The suppress-reachability command suppresses the advertisement of all interface addresses in an OSPF process.

The undo suppress-reachability command restores the default setting.

By default, OSPF interfaces can advertise its addresses in the OSPF process.

Format

suppress-reachability

undo suppress-reachability

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To suppress the advertisement of all interface addresses in an OSPF process, run the suppress-reachability command.

Example

# Suppress the advertisement of all interface addresses in OSPF process 100.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] suppress-reachability

tiebreaker preference (OSPF FRR view)

Function

The tiebreaker preference command sets the solution of selecting a backup path for OSPF IP FRR.

The undo tiebreaker preference command restores the default solution of selecting a backup path for OSPF IP FRR.

By default, the solution of selecting a backup path for OSPF IP FRR is node-protection path first.

This command is supported only on the S6730-H-V2, S5732-H-V2, S5735-S-V2 and S5735I-S-V2.

Format

tiebreaker { node-protecting | lowest-cost } preference value

undo tiebreaker { node-protecting | lowest-cost } [ preference value ]

Parameters

Parameter Description Value
node-protecting

Sets the solution of selecting a backup path for OSPF IP FRR to node-protection path first.

-
lowest-cost

Sets the solution of selecting a backup path for OSPF IP FRR to smallest-cost path first.

-
preference value

Specifies a priority for the solution. The larger the value, the higher the priority.

The value is an integer ranging from 1 to 255.

By default, the priority of the node-protection path first solution is 40, and the priority of the smallest-cost path first solution is 20.

Views

OSPF FRR view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the solution of selecting a backup path for OSPF IP FRR is node-protection path first. In some cases, the solution needs to be changed to smallest-cost path first because of data forwarding capacity or link cost consideration. To change the solution of selecting a backup path for OSPF IP FRR to smallest-cost path first, run the tiebreaker command.

Prerequisites

The OSPF FRR view has been displayed using the frr command, and OSPF IP FRR has been enabled using the loop-free-alternate command.

Example

# Set the solution of selecting a backup path for OSPF IP FRR to smallest-cost path first.
<HUAWEI> system-view
[HUAWEI] ospf 1
[HUAWEI-ospf-1] frr
[HUAWEI-ospf-1-frr] loop-free-alternate
[HUAWEI-ospf-1-frr] tiebreaker lowest-cost preference 255

vlink-peer

Function

The vlink-peer command creates and configures a virtual link.

The undo vlink-peer command deletes the virtual link or restores the default setting.

By default, no virtual link is configured.

Format

vlink-peer router-id [ hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval | dead dead-interval | smart-discover | [ simple [ plain SPlainText | [ cipher ] SCipherText ] | { hmac-sha256 | md5 | hmac-md5 } [ key-id { plain MPlainText | [ cipher ] MCipherText } ] | authentication-null | keychain keychain-name ] ] *

undo vlink-peer router-id

undo vlink-peer router-id { hello | retransmit | trans-delay | dead | simple | hmac-sha256 | md5 | hmac-md5 | authentication-null | keychain | smart-discover }

Parameters

Parameter Description Value
router-id

Specifies the router ID of a virtual link neighbor.

The value is in dotted decimal notation.
hello hello-interval

Specifies the interval at which Hello packets are sent on an interface.

This value must be equal to hello-interval value of the Device that sets up the virtual link through the interface.

The value is an integer ranging from 1 to 65535 seconds. The default value is 10 seconds.
retransmit retransmit-interval

Specifies the interval at which LSAs are retransmitted.

The value is an integer ranging from 1 to 3600, in seconds. The default value is 5 seconds.
trans-delay trans-delay-interval

Specifies the delay in sendingLSAs on an interface.

The value is an integer ranging from 1 to 3600, in seconds. The default value is 1 second.
dead dead-interval

Specifies the dead interval.

This value must be equal to dead-interval of the Device that sets up a virtual link through the interface. In addition, the value must be at least 4 times of hello-interval.

The value is an integer ranging from 1 to 235926000, in seconds. The default value is 40 seconds.
smart-discover

Enables the device to proactively send Hello packets.

-
simple

Indicates the simple authentication mode.

  • The new password is at least eight characters long and contains at least two of the following types: upper-case letters, lower-case letters, digits, and special characters.
  • For security purposes, you are advised to configure a password in ciphertext mode. To further improve device security, periodically change the password.

-
plain

Indicates the plaintext authentication. You can only type in the plaintext, and it is displayed as a plaintext in the configuration file.

When configuring an authentication password, select the ciphertext mode because the password is saved as a plaintext in the configuration file if you select the plaintext mode, which has a high risk. In addition, to ensure device security, change the password periodically.

-
SPlainText

Specifies a plaintext password.

The value is a string of characters.

  • In simple mode, the value is a string of 1 to 8 characters.
  • In md5, hmac-md5 or hmac-sha256 mode, the value is a string of 1 to 255 characters.

Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password.
cipher

Indicates the cipher authentication.

You can type in a simpletext or ciphertext, but it is displayed as the ciphertext in the configuration file.

-
SCipherText

Specifies a ciphertext.

The value is a string of characters.

  • For simple authentication, a simpletext is 1 to 8 characters, and a ciphertext password is 24 to 128 characters.
  • For MD5, HMAC-MD5, or HMAC-SHA256 authentication, a simpletext is 1 to 255 characters, and a ciphertext password is 20 to 432characters.

Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password.
hmac-sha256

Indicates the HMAC-SHA256 authentication mode.

By default, the hmac-sha256 authentication mode is cipher.

-
md5

Indicates the MD5 authentication mode.

By default, the md5 authentication mode is cipher.

For the sake of security, using the HMAC-SHA256 algorithm rather than the MD5 algorithm is recommended.

-
hmac-md5

Indicates the HMAC-MD5 authentication mode.

By default, the hmac-md5 authentication mode is cipher.

For the sake of security, using the HMAC-SHA256 algorithm rather than the HMAC-MD5 algorithm is recommended.

-
key-id

Specifies a key ID for ciphertext authentication.

The key ID must be consistent with that of the peer.

The value is an integer ranging from 1 to 255.
MPlainText

Specifies a plaintext password.

The value is a string of characters.

  • In simple mode, the value is a string of 1 to 8 characters.
  • In md5, hmac-md5 or hmac-sha256 mode, the value is a string of 1 to 255 characters.

Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password.
MCipherText

Specifies a ciphertext.

The value is a string of characters.

  • For simple authentication, a simpletext is 1 to 8 characters, and a ciphertext password is 24 to 128 characters.
  • For MD5, HMAC-MD5, or HMAC-SHA256 authentication, a simpletext is 1 to 255 characters, and a ciphertext password is 20 to 432characters.

Except the question mark (?) and space. However, when quotation marks (") are used around the password, spaces are allowed in the password.
authentication-null

Sets the null authentication mode.

-
keychain

Indicates the keychain authentication.

Before configuring this parameter, run the keychain command to create a keychain. Then, run the key-id, key-string, and algorithm commands to configure a key ID, a password, and an authentication algorithm for this keychain. Otherwise, the OSPF authentication fails.

If the dependent keychain is deleted, the neighbor relationship may be interrupted. Therefore, exercise caution when deleting the keychain.

-
keychain-name

Specifies the name of a keychain.

The value is a string of 1 to 47 case-insensitive characters, It cannot contain question marks (?). If spaces are used, the string must start and end with double quotation marks (&quot;).

Views

OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After OSPF is divided into different areas, OSPF routes between non-backbone areas are updated by route exchange with the backbone area. Therefore, OSPF requires that all non-backbone areas keep connected to the backbone area and devices within the backbone area also keep connected. In real-world scenarios, however, these requirements cannot be met due to various limitations. Configuring OSPF virtual links can solve the problem.

Configuration Impact

Establish virtual links between the non-backbone areas and the backbone area, and between devices within the backbone area to ensure connectivity in an OSPF network.

Follow-up Procedure

Different vendors may use different MTUs as default settings. To ensure consistency, run the undo ospf mtu-enable command to set the default MTU to 0 when DD packets are sent on an OSPF interface.

If the MTU of DD packets is configured, the neighbor relationship will be reestablished.

Precautions

The md5 and hmac-md5 parameters in this command can be used only after the weak security algorithm/protocol feature package has been installed using the install feature-software WEAKEA command.

The default parameter values are recommended when a virtual link is configured; however, you can modify the parameter values as needed. Suggested parameter configurations are as follows:

  • The smaller the hello value, the faster the device detects network changes and the more network resources are consumed.
  • If the retransmit parameter is set too small, unnecessary LSAs may be retransmitted. Setting the parameter to a large value is recommended on a low-speed network.
  • The authentication mode of the virtual link must be the same as that of the backbone area.

    The virtual link function does not apply to DCN processes.

Example

# Configure a virtual link with the peer Router ID 1.1.1.1.
<HUAWEI> system-view
[HUAWEI] ospf 100
[HUAWEI-ospf-100] area 2
[HUAWEI-ospf-100-area-0.0.0.2] vlink-peer 1.1.1.1

vpn-instance-capability simple

Function

The vpn-instance-capability simple command enables the device to directly calculate routes instead of conducting routing loop detection.

The undo vpn-instance-capability command enables a device to check the DN bit in received summary LSAs (Type 5 and Type 7 LSAs) to prevent routing loops and check the DN bit and route tag in the received ASE LSAs to prevent routing loops.

By default, the routing loop detection is enabled.

Format

vpn-instance-capability simple

undo vpn-instance-capability

Parameters

None

Views

OSPFv3 view, OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The vpn-instance-capability simple command takes effect only for the OSPF or OSPFv3 processes bound to a VPN instance.

Example

# Disable OSPFv3 routing loop detection.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance huawei
[HUAWEI-vpn-instance-huawei] ipv6-family
[HUAWEI-vpn-instance-huawei-af-ipv6] quit
[HUAWEI-vpn-instance-huawei] quit
[HUAWEI] ospfv3 100 vpn-instance huawei
[HUAWEI-ospfv3-100] vpn-instance-capability simple
# Disable routing loop detection for OSPF.
<HUAWEI> system-view
[HUAWEI] ip vpn-instance vrf1
[HUAWEI-vpn-instance-vrf1] route-distinguisher 100:1
[HUAWEI-vpn-instance-vrf1-af-ipv4] vpn-target 3:3 export-extcommunity
[HUAWEI-vpn-instance-vrf1-af-ipv4] vpn-target 4:4 import-extcommunity
[HUAWEI-vpn-instance-vrf1-af-ipv4] quit
[HUAWEI-vpn-instance-vrf1] quit
[HUAWEI] ospf 100 vpn-instance vrf1
[HUAWEI-ospf-100] vpn-instance-capability simple
Translation
Favorite
Download
Update Date：2023-11-14
Document ID：EDOC1100291031
Views：100967
Downloads：750
Average rating：0.0Points

Related Documents

Digital Signature File

digtal sigature tool