NetEngine AR600, AR6100, AR6200, and AR6300 V300R021 Command Reference
OSPF Configuration Commands
- Support for OSPF
- abr-summary (OSPF area)
- area (OSPF)
- asbr-summary
- authentication-mode (OSPF area)
- bandwidth-reference (OSPF)
- bfd all-interfaces (OSPF)
- default (OSPF)
- default-cost (OSPF Aera)
- default-route-advertise (OSPF)
- description (OSPF)
- description (OSPF Area)
- display default-parameter ospf
- display gtsm statistics
- display ospf abr-asbr
- display ospf asbr-summary
- display ospf bfd session
- display ospf brief
- display ospf cumulative
- display ospf error
- display ospf global-statistics
- display ospf graceful-restart
- display ospf interface
- display ospf lsdb
- display ospf migp-routing
- display ospf mesh-group
- display ospf nexthop
- display ospf peer
- display ospf request-queue
- display ospf retrans-queue
- display ospf routing
- display ospf sham-link
- display ospf spf-statistics
- display ospf statistics updated-lsa
- display ospf vlink
- display snmp-agent trap feature-name ospf all
- dn-bit-set
- dn-bit-check
- domain-id (OSPF)
- eca-route-type compatible
- enable log
- filter export (OSPF Area)
- filter import (OSPF Area)
- filter-lsa-out peer
- filter-policy export (OSPF)
- filter-policy import (OSPF)
- flooding-control
- frr (OSPF)
- frr-policy route (OSPF FRR)
- frr-priority static low
- graceful-restart (OSPF)
- graceful-restart helper-role (OSPF)
- gtsm default-action
- gtsm log drop-packet
- import-route (OSPF)
- local-mt filter-policy (OSPF)
- local-mt enable (OSPF)
- loop-free-alternate (OSPF FRR)
- lsa-arrival-interval
- lsa-originate-interval
- lsdb-overflow-limit
- maximum load-balancing (OSPF)
- maximum-routes
- mesh-group enable
- network (OSPF Area)
- nexthop (OSPF)
- nssa (OSPF Area)
- opaque-capability enable
- ospf
- ospf authentication-mode
- ospf bfd
- ospf bfd block
- ospf cost
- ospf dr-priority
- ospf enable
- ospf filter-lsa-out
- ospf frr block
- ospf maxage-lsa auto-protect disable
- ospf mib-binding
- ospf mtu-enable
- ospf network-type
- ospf p2mp-mask-ignore
- ospf router-id auto-recover disable
- ospf smart-discover
- ospf suppress-flapping peer
- ospf suppress-flapping peer disable
- ospf suppress-flapping peer hold-down
- ospf suppress-flapping peer hold-max-cost disable
- ospf timer dead
- ospf timer hello
- ospf timer poll
- ospf timer retransmit
- ospf trans-delay
- ospf valid-ttl-hops
- peer (OSPF)
- preference (OSPF)
- prefix-priority (OSPF)
- reset gtsm statistics
- reset ospf counters
- reset ospf process
- reset ospf redistribution
- reset ospf suppress-flapping peer
- retransmission-limit
- route-tag
- rfc1583 compatible
- sham-hello enable (OSPF)
- sham-link (OSPF Area)
- silent-interface (OSPF)
- snmp-agent trap enable feature-name ospf
- spf-schedule-interval
- stub (OSPF Area)
- stub-router (OSPF)
- suppress-flapping peer disable (OSPF)
- vlink-peer (OSPF area)
- vpn-instance-capability simple (OSPF)
Support for OSPF
Hardware Requirements
This section is applicable to all models. For details about differences for specific models, see the description in the corresponding section.
abr-summary (OSPF area)
Function
The abr-summary command configures route summarization on an Area Border Router (ABR).
The undo abr-summary command disables route summarization on an ABR.
By default, route summarization is not configured on ABRs.
Format
abr-summary ip-address mask [ [ advertise | not-advertise ] | cost { cost | inherit-minimum } ] *
abr-summary ip-address mask [ [ advertise [ generate-null0-route ] | not-advertise | generate-null0-route [ advertise ] ] | cost { cost | inherit-minimum } ] *
undo abr-summary ip-address mask
Parameters
Parameter | Description | Value |
---|---|---|
ip-address |
Specifies the IP address of a summarized route. |
The value is in dotted decimal notation. |
mask |
Specifies the mask of the IP address of the summarized route. |
The value is in dotted decimal notation. |
advertise | not-advertise |
Determines whether to advertise the summarized route. By default, the summarized route is advertised. |
- |
cost cost |
Specifies the cost of the summarized route. By default, the cost of the summarized route is the highest cost of specific routes. |
The value is an integer that ranges from 0 to 16777214. |
inherit-minimum |
Indicates that the smallest cost of specific routes is used as the cost of the summarized route. |
- |
generate-null0-route |
Generates a blackhole route to prevent routing loops. |
- |
Usage Guidelines
Usage Scenario
On a large-scale OSPF network, route search speed may decrease due to the large routing table size. Configure route summarization to reduce the routing table size and simplify management.
In route summarization, multiple routes with the same IP prefix are summarized into one. If a link connected to a device within a summarized IP address range alternates between Up and Down states, the link status change is not advertised to the devices outside the IP address range. This prevents route flapping and improves network stability.
The abr-summary command configures route summarization on an ABR. When the ABR sends routing information to other areas, it originates Type 3 LSAs for each network segment. If any contiguous segments exist in this area, run the abr-summary command to summarize these segments into one. The ABR then sends just one summarized LSA, and no LSAs that belong to the summarized network segment specified by the command. Therefore, the routing table size is reduced, and router performance is improved.
Precautions
This command applies only to ABRs for intra-area route summarization. The asbr-summary command configures AS Boundary Routers (ASBRs) to summarize the routes imported by OSPF.
Route summarization cannot be configured on ABRs in different areas of the same process.
Example
# In OSPF 100 area 1, summarize routes in two network segments, 10.42.10.0 and 10.42.110.0, into one route 10.42.0.0, and advertise the summarized 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 (OSPF)
Function
The area command creates an OSPF area and displays the OSPF area view.
The undo area command deletes a specified area.
By default, the system does not creates an OSPF area.
Parameters
Parameter | Description | Value |
---|---|---|
area-id | Specifies the area ID. The area with the area-id being 0 is a backbone area. | The value can be a decimal integer or in dotted decimal notation. When the value is an integer, the value ranges from 0 to 4294967295. |
Usage Guidelines
Usage Scenario
The number of devices increases with the expansion of the network. This leads to a large LSDB on every OSPF-enabled device on a large-scale network. Consequently, route flapping frequently occurs and thus a large number of OSPF packets are transmitted on the network, which wastes bandwidth resources.
OSPF resolves this problem by partitioning an AS into different areas. An area is regarded as a logical group and each group is identified by an area ID.
Configuration Impact
After OSPF partitions the AS into different areas, functions, such as the timer, filter, and summarization, of multiple devices in the same area, can be planned and configured uniformly in the area. Therefore, the size of the LSDB is reduced and the network performance is improved.
Prerequisites
Run the ospf command before you run the area command to start the OSPF process and enter the OSPF view.
Precautions
- At the border of an area resides a router instead of a link.
- A network segment or a link belongs to only one area. The area to which each OSPF interface belongs must be specified.
- The backbone area is responsible for forwarding inter-area routing information. The routing information between the non-backbone areas must be forwarded through the backbone area.
- 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.
asbr-summary
Function
The asbr-summary command configures AS Boundary Routers (ASBRs) to summarize the routes imported by OSPF.
The undo asbr-summary command disables ASBRs from summarizing the routes imported by OSPF.
By default, ASBRs do not summarize the routes imported by OSPF.
Format
asbr-summary ip-address mask [ [ not-advertise | generate-null0-route ] | tag tag | cost cost | distribute-delay interval ] *
asbr-summary type nssa-trans-type-reference [ cost nssa-trans-cost-reference ]
undo asbr-summary type
undo asbr-summary ip-address mask
Parameters
Parameter | Description | Value |
---|---|---|
ip-address |
Specifies the IP address of a summarized route. |
The value is in dotted decimal notation. |
mask |
Specifies the mask of the IP address of the summarized route. |
The value is in dotted decimal notation. |
not-advertise |
Indicates that the summarized route is not advertised. If this parameter is not specified, the summarized route is advertised. |
- |
generate-null0-route |
Generates a blackhole route to prevent routing loops. |
- |
tag tag |
Specifies the tag of the summarized route. |
The value is an integer that ranges from 0 to 4294967295. The default value is 1. |
cost cost |
Specifies the cost of the summarized route. By default, for Type 1 external routes, the cost of the summarized route is the highest cost of specific routes; for Type 2 external routes, the cost of the summarized route equals the highest cost of specific routes plus 1. |
The value is an integer that ranges from 0 to 16777214. |
distribute-delay interval |
Specifies the delay in advertising the summarized route. |
The value is an integer that ranges from 1 to 65535, in seconds. |
type nssa-trans-type-reference |
Enables OSPF to refer to Type 5 LSAs that have been translated from Type 7 LSAs when it sets types for summary routes on ASBRs. By default, when OSPF sets types for summary routes on ASBRs, OSPF does not refer to Type 5 LSAs that have been translated from Type 7 LSAs. |
- |
cost nssa-trans-cost-reference |
Enables OSPF to refer to Type 5 LSAs that have been translated from Type 7 LSAs when it sets costs for summary routes on ASBRs. By default, when OSPF sets types and costs for summary routes on ASBRs, OSPF does not refer to Type 5 LSAs that have been translated from Type 7 LSAs. |
- |
Usage Guidelines
Usage Scenario
On a large-scale OSPF network, route search speed may decrease due to the large routing table size. Configure route summarization to reduce the routing table size and simplify management.
In route summarization, multiple routes with the same IP prefix are summarized into one. If a link connected to a device within a summarized IP address range alternates between Up and Down states, the link status change is not advertised to the devices outside the IP address range. This prevents route flapping and improves network stability.
Imported routes with the same prefix can be summarized into one and advertised as one route using the asbr-summary command. Route summarization reduces routing information and routing table size, improving device performance.
After route summarization is implemented:
- If the local device is an ASBR in a common area, the local device summarizes all imported Type 5 LSAs within the summary address range.
- If the local device is an ASBR in an NSSA, the local device summarizes all imported Type 7 LSAs within the summary 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 summary address range, and summarizes the Type 5 LSAs that have been transformed from Type 7 LSAs.
Precautions
When a large number of routes are summarized, specify the distribute-delay parameter to set the delay in advertising the summarized routes. This ensures that the advertised summarized routes contain more valid routes and avoids network flapping and incorrect routing information.
Example
# Configure route summarization for the 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
# Cancel route summarization for the imported routes.
<Huawei> system-view
[Huawei] ospf 100
[Huawei-ospf-100] undo asbr-summary 10.2.0.0 255.255.0.0
authentication-mode (OSPF area)
Function
The authentication-mode command sets the authentication mode and password for an OSPF area.
The undo authentication-mode command cancels the authentication mode configured for an OSPF area.
By default, no authentication mode is configured.
Format
authentication-mode simple [ plain plain-text | [ cipher ] cipher-text ]
authentication-mode { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ]
authentication-mode keychain keychain-name
undo authentication-mode
Parameters
Parameter | Description | Value |
---|---|---|
simple |
Sets simple authentication. In simple authentication, the password type is cipher by default. NOTICE:
Simple authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
plain |
Sets a plain text password. Only a plain text password can be entered, and only plain text is displayed when the configuration file is viewed. NOTICE:
If plain is specified, the password is saved in the configuration file in plain text. This carries security risks. It is recommended to specify cipher to save the password in cipher text. |
- |
plain-text |
Sets a plain text password. |
The value is a string of case-sensitive characters that can be letters or digits without spaces. In simple authentication, the value is a string of 1 to 8 characters. In md5, hmac-md5 or hmac-sha256 authentication, the value is a string of 1 to 255 characters. |
cipher |
Sets a cipher text password. Either a plain or cipher text password can be entered, and cipher text is displayed when the configuration file is viewed. |
When cipher is configured, the password can only be entered in cipher text. Then, the password is displayed in cipher text in configuration files. MD5 authentication, HMAC-SHA256 authentication or HMAC-MD5 authentication defaults to use the password in cipher text. |
cipher-text |
Specifies the ciphertext password. |
The value is a string of case-sensitive characters that can be letters or digits without spaces. In simple authentication, the value is a string of 1 to 8 characters in plain text, or a string of 48, 24 or 32 characters in cipher text. In md5, hmac-sha256 or hmac-md5 authentication, the value is a string of 1 to 255 characters in plain text, or a string of 20 to 392 characters in cipher text. |
md5 |
Indicates MD5 authentication using the cipher text password. NOTICE:
MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-md5 |
Indicates HMAC MD5 authentication using the cipher text password. NOTICE:
HMAC-MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-sha256 |
Indicates HMAC-SHA256 authentication. |
- |
key-id |
Specifies authentication key ID of the interface's cipher authentication. The key ID must be consistent with that of the peer. |
The value is an integer that ranges from 1 to 255. |
keychain |
Indicates keychain authentication. NOTE:
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, OSPF authentication will fail. Currently, only the HMAC-MD5 and HMAC-SHA256 algorithms can be used in OSPF. |
- |
keychain-name |
Specifies the keychain name. |
The value is a string of 1 to 47 case-insensitive characters. Except the question mark (?) and space. However, when double quotation marks (") are used around the string, spaces are allowed in the string. |
Usage Guidelines
Precautions
The authentication modes and passwords of all the devices must be the same in any given area, but can differ between several areas.
The ospf authentication-mode command used in the interface view takes precedence over the authentication-mode command used in the OSPF area view.
bandwidth-reference (OSPF)
Function
The bandwidth-reference command sets the bandwidth reference value that is used to calculate interface costs.
The undo bandwidth-reference command restores the default bandwidth reference value.
The default bandwidth reference value is 100 Mbit/s.
Parameters
Parameter | Description | Value |
---|---|---|
value |
Specifies the bandwidth reference value for link cost calculation. |
The value is an integer ranging from 1 to 2147483648, in Mbit/s. The default value is 100 Mbit/s. |
Usage Guidelines
Usage Scenario
The calculation formula is as follows: Interface cost = Bandwidth reference value/Interface bandwidth. The integer of the calculated result is the interface cost. If the calculated result is smaller than 1, the interface cost value is 1. If the bandwidth-reference command is executed to configure a new bandwidth reference value, the interface cost will be changed. As a result, OSPF will re-select routes.
The calculation formula is as follows: cost = Reference bandwidth
(M)/Negotiated rate of the physical interface.
The default bandwidth reference value is 100 Mbit/s. The interface cost value is 100000000 divided by the interface bandwidth value.
Precautions
After the bandwidth-reference command is configured in a process view, bandwidth reference values of all interfaces in the process are changed to the specified value.
Generally, OSPF automatically calculate the link cost for an interface based on the bandwidth of the interface. You can modify the interface cost using the ospf cost command.
The bandwidth-reference command can be run on Eth-Trunk interfaces in a way similar to that on physical interfaces. If the command is run on an Eth-Trunk interface, the bandwidth of the Eth-Trunk interface is equal to the total bandwidth of all its member interfaces.
bfd all-interfaces (OSPF)
Function
The bfd all-interfaces enable command enables BFD in an OSPF process.
The bfd all-interfaces { min-rx-interval receive-interval | min-tx-interval transmit-interval | detect-multiplier multiplier-value | frr-binding } * command sets the parameter values of a BFD session.
The undo bfd all-interfaces enable command disables BFD in an OSPF process.
The undo bfd all-interfaces { min-rx-interval | min-tx-interval | detect-multiplier | frr-binding } * command restores the default parameter values of a BFD session.
By default, BFD is not enabled at OSPF process.
Format
bfd all-interfaces enable
undo bfd all-interfaces enable
bfd all-interfaces { min-rx-interval receive-interval | min-tx-interval transmit-interval | detect-multiplier multiplier-value | frr-binding } *
undo bfd all-interfaces { min-rx-interval | min-tx-interval | detect-multiplier | frr-binding } *
Parameters
Parameter | Description | Value |
---|---|---|
min-rx-interval receive-interval |
Indicates the minimum interval at which BFD packets are received from the remote end. |
The value is an integer ranging from 10 to 2000, in milliseconds. The default value is 1000 milliseconds. |
min-tx-interval transmit-interval |
Indicates the minimum interval at which BFD packets are sent to the remote end. |
The value is an integer ranging from 10 to 2000, in milliseconds. The default value is 1000 milliseconds. |
detect-multiplier multiplier-value |
Indicates the local detection multiplier. NOTE:
After BFD is enabled, OSPF establishes BFD sessions only with the neighbors in the Full state. |
The value is an integer ranging from 3 to 50. By default, it is 3. |
frr-binding |
Associates the BFD session status and link status on an interface. That is, when the BFD status goes Down, the link status of the interface also goes Down. This enables traffic to be switched to the backup path. NOTE:
AR611-S, AR611W-S, AR611, AR611W, AR611W-LTE4CN, AR617VW, AR617VW-LTE4, and AR617VW-LTE4EA do not support frr-binding parameter. |
- |
Usage Guidelines
Usage Scenario
BFD can fast detect faults in communication with neighbors, thus minimizing the impact of such faults on services.
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 in the case of a link failure. 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 status changes to Down accordingly, thus implementing fast fault sensing.
You can bind a BFD session to an interface or an OSPF process. If a BFD session is bound to an interface and an OSPF process, the BFD session bound to an interface takes precedence over that bound to an OSPF process.
Precautions
- receive-interval is negotiated between local min-rx-interval and remote min-tx-interval, and the smaller of local min-rx-interval and remote min-tx-interval is used as the remote min-tx-interval. If the local end does not receive any BFD packets within the interval of receive-interval × multiplier-value (local detection multiplier), it declares that the remote end is unreachable.
- An OSPF device sets up BFD sessions with only the neighbors in Exstart state. Two ends can set up a BFD session only when the bfd command is run on both ends to configure BFD globally and the bfd all-interfaces enable command is run.
- The bfd all-interfaces command and the ospf bfd block command are mutually exclusive.
default (OSPF)
Function
The default command configures default parameters for OSPF to import external routes. The parameters include the cost, type (Type 1 or Type 2), tag, and number of imported routes.
The undo default command restores the default setting.
By default, the default cost of the external routes is 1; the upper limit of the imported external routes is 2147483647; the type of the imported external routes is Type 2; the default tag value is 1.
Format
default { cost { cost-value | inherit-metric } | limit limit | tag tag | type type } *
undo default { cost | limit | tag | type } *
Parameters
Parameter | Description | Value |
---|---|---|
cost cost-value |
Specifies the default cost of the external routes imported by OSPF. |
The value is an integer ranging from 0 to 16777214. By default, it is 1. |
inherit-metric |
Indicates that the cost of the imported route is the cost carried in the route. If no cost is specified, the default cost set through the default command is used. |
- |
limit limit |
Specifies the default upper limit of the external routes to be imported within a given period. |
The value is an integer ranging from 1 to 2147483647. |
tag tag |
Specifies the tag of the external routes. |
The value is an integer ranging from 0 to 4294967295. By default, it is 1. |
type type |
Specifies the type of the external routes. |
The value is an integer ranging from 1 to 2. By default, it is 2.
|
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 change the OSPF routing policies.
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 applies the OSPF routing policies to tagged routes.
Follow-up Procedure
The priority of the default (OSPF) command is the lowest. Thus, ensure that no other commands are configured when configuring this command. Otherwise, this command cannot take effect.
Precautions
- Run the apply cost command to set the cost of a route.
- Run the import-route (OSPF) command to set the cost of an imported route.
- Run the default (OSPF) command to set the default cost of an imported route.
default-cost (OSPF Aera)
Function
The default-cost command sets the cost of the Type3 default route that is transmitted to the Stub or NSSA by OSPF.
The undo default-cost command restores the default setting.
By default, the cost of the Type3 default route transmitted to the Stub or NSSA is 1.
Parameters
Parameter | Description | Value |
---|---|---|
cost | Specifies the cost of the Type3 default route transmitted to the Stub or NSSA by OSPF. | The value is an integer ranging from 0 to 16777214. |
default-route-advertise (OSPF)
Function
The default-route-advertise command advertises default routes in a common OSPF area.
The undo default-route-advertise command disables advertisement of default routes in a common OSPF area.
By default, OSPF devices in a common OSPF area do not advertise default routes.
Format
default-route-advertise [ [ always | permit-calculate-other ] | cost cost | type type | route-policy route-policy-name [ match-any ] ] *
default-route-advertise summary cost cost
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 non-local OSPF process.
|
- |
permit-calculate-other |
Generates and advertises an ASE LSA that describes the default route only when the local device has active default routes learned from the non-local OSPF process. The device still calculates the default routes from other devices. NOTE:
If neither always nor permit-calculate-other is configured:
|
- |
cost cost |
Specifies the cost of the ASE LSA. |
The value is an integer that ranges from 0 to 16777214. The default value is 1. |
type type |
Specifies the type of the external routes. |
The value is 1 or 2. The default value is 2.
|
route-policy route-policy-name |
Specifies the name of a routing policy. The device advertises default routes according to the parameters of the configured routing policy when there are matched default OSPF routing entries generated by other processes. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
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. |
- |
match-any |
Indicates that a device matches the routing entry in the routing table by using a routing policy and then advertises the default route according to the parameters set through the routing policy. |
- |
Usage Guidelines
Usage Scenario
The import-route (OSPF) command cannot be used to import a default route from another AS. Running the default-route-advertise command on an ASBR can advertise a non-OSPF default route in a common OSPF area.
If the ASBR has a default route, the default-route-advertise command enables the ASBR to advertise the default route 0.0.0.0 to the OSPF area.
With always configured: The ASBR can advertise the default route 0.0.0.0 even if there is no default route. This allows the default route to retain in the routing table and prevents the ASBR from using a default route sent by another device.
Without always configured: The ASBR generates an LSA that describes a default route only when the local routing table contains an active default route that is not an OSPF except BGP route.
If the local routing table contains an active default BGP route, the default route can be injected to the OSPF routing table based on the following situations:
- Whether the ospf process-id vpn-instance vpn-instance-name command is run together with the vpn-instance-capability simple command:
- If the two commands are executed together, to inject an active default EBGP route into the OSPF routing table, run the default-route-advertise command. To inject an active default IBGP route to the OSPF routing table, run the import-route bgp permit-ibgp command before you run the default-route-advertise command.
- If only the ospf process-id vpn-instance vpn-instance-name command is run, to inject an active default EBGP or IBGP route into the OSPF routing table, run the default-route-advertise command.
- If the ospf process-id vpn-instance vpn-instance-name command is not run, to inject an active default EBGP route into the OSPF routing table, run the default-route-advertise command. To inject an active default IBGP route to the OSPF routing table, run the import-route bgp permit-ibgp command before you run the default-route-advertise command.
- Whether the ospf process-id vpn-instance vpn-instance-name command is run together with the vpn-instance-capability simple command:
Injecting an IBGP route into the OSPF routing table may cause a routing loop. Exercise caution when you perform this step.
- A route configured with type takes precedence over that not configured with type, and a route configured with a smaller type value takes precedence over that configured with a larger type value.
- A route configured with cost takes precedence over that not configured with cost, and a route configured with a smaller cost value takes precedence over that configured with a larger cost value.
- A route configured with tag takes precedence over that not configured with tag, and a route configured with a smaller tag value takes precedence over that configured with a larger tag value.
Prerequisites
Before advertising a default route, OSPF compares the priorities of default routes in an OSPF area and then advertises a default route with the highest priority. If a static default route is configured on an OSPF device, check that the priority of the static default route is lower than that of the default route to be advertised by OSPF. This ensures that the default route advertised by OSPF will be added to the routing table of the OSPF device.
Configuration Impact
After the default-route-advertise command is configured on the ASBR, the ASBR will generate a Type 5 ASE LSA with a link state ID of 0.0.0.0 and mask of 0.0.0.0. In addition, it will advertise the ASE LSA in an entire OSPF area.
If a routing policy is configured, default routes are advertised based on the following principles:
- If a default route matches the routing policy, a default route is generated on an OSPF device based on the parameters configured in the routing policy. Parameters such as cost, tag, and type can be configured in the routing policy.
- If the default route does not match the routing 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
In different OSPF areas, OSPF advertises default routes using different modes. This default-route-advertise command can be used to advertise default routes in a common OSPF area. In a stub area, totally stub area, or totally NSSA, default routes are advertised automatically. In an NSSA, the nssa default-route-advertise command is used to advertise default routes.
If the default-route-advertise command is used in multiple OSPF processes to generate default routes, routing loops tend to occur. To prevent this issue, you are advised to configure route-policies to filter routes so that default routes will not be learned from these OSPF processes.
description (OSPF)
Function
The description command configures the description of an OSPF process.
The undo description command deletes the description.
By default, there is no description of an OSPF process.
Parameters
Parameter | Description | Value |
---|---|---|
text | Specifies the description of an OSPF process. | The description is a string of 1 to 80 characters. |
description (OSPF Area)
Function
The description command configures the description of an OSPF area.
The undo description command deletes the description.
By default, there is no description of an OSPF area.
Parameters
Parameter | Description | Value |
---|---|---|
text | Specifies the description of an OSPF area. | The description is a string of 1 to 80 characters. |
display default-parameter ospf
Usage Guidelines
To display the default OSPF configuration, run display default-parameter ospf command.
Example
# Display the default OSPF configuration.
<Huawei> display default-parameter ospf
Process View:
-------------------------------------------------------
Default Metric : 1
Default Tag : 1
Default Type : 2
SPF Intelligent-timer Max-interval(msec) : 10000
SPF Intelligent-timer Start-interval(msec) : 500
SPF Intelligent-timer Hold-interval(msec) : 1000
Lsa Maxage (sec) : 3600
Lsa Refresh Time(sec) : 1800
Lsa Maxagediff Interval (sec) : 900
Minimum Lsa Arrival Interval(sec) : 1
Minimum Lsa Originate Interval(sec) : 5
Sham Link Cost : 1
VPN Domain ID : 0
VPN Router Tag : 0
Route Preference for Internal Routes : 10
Route Preference for External Routes : 150
-------------------------------------------------------
Area View:
-------------------------------------------------------
Default Stub Cost : 1
-------------------------------------------------------
Interface View:
-------------------------------------------------------
P2P&Broadcast Hello Interval(sec) : 10
P2MP&NBMA Hello Interval(sec) : 30
P2P&Broadcast Dead Interval(sec) : 40
P2MP&NBMA Dead Interval(sec) : 120
Poll Interval(sec) : 120
Router DR Priority : 1
Retransmit Interval(sec) : 5
Transmit Delay(sec) : 1
-------------------------------------------------------
Item |
Description |
---|---|
Process View |
Indicates the process view. |
Default Metric |
Indicates the default metric of the imported external route. |
Default Tag |
Indicates the default tag value of the imported external route. |
Default Type |
Indicates the default type of the imported external route. |
SPF Intelligent-timer Max-interval(msec) |
Indicates the default maximum interval of SPF calculation. |
SPF Intelligent-timer Start-interval(msec) |
Indicates the default start interval of SPF calculation. |
SPF Intelligent-timer Hold-interval(msec) |
Indicates the default hold interval of SPF calculation. |
Lsa Maxage(sec) |
Indicates the default maximum age of the LSA. |
Lsa Refresh Time(sec) |
Indicates the default maximum interval for generating an LSA. If the LS age of the LSAs generated by the device reaches the LSA Refresh Time, a new instance needs to be generated for the LSAs. |
Lsa Maxagediff Interval(sec) |
Indicates the default value difference in the MaxAge fields of LSAs. If the value difference in the MaxAge fields of two LSAs is greater than MaxAgeDiff Interval, the two LSAs are considered to belong to different instances of the same LSA. |
Minimum Lsa Arrival Interval(sec) |
Indicates the default minimum interval for receiving the same LSA. |
Minimum Lsa Originate Interval(sec) |
Indicates the default minimum interval for sending the same LSA. |
Sham Link Cost |
Indicates the default cost of the sham link. |
VPN Domain ID |
Indicates the default domain ID of the VPN. |
VPN Router Tag |
Indicates the default router tag of the VPN. |
Route Preference for Internal Routes |
Indicates the default preference of the internal route. |
Route Preference for External Routes |
Indicates the default preference of the external route. |
Area View |
Indicates the area view. |
Default Stub Cost |
Indicates the default cost of a stub area. |
Interface View |
Indicates the interface view. |
P2P&Broadcast Hello Interval(sec) |
Indicates the default interval for sending Hello packets on a P2P or broadcast network. |
P2MP&NBMA Hello Interval(sec) |
Indicates the default interval for sending Hello packets on a P2MP or NBMA network. |
P2P&Broadcast Dead Interval(sec) |
Indicates the default interval for declaring a neighbor to be Down after no Hello packets are received on a P2P or broadcast network. |
P2MP&NBMA Dead Interval(sec) |
Indicates the default interval for declaring a neighbor to be Down after no Hello packets are received on a P2MP or NBMA network. |
Poll Interval(sec) |
Indicates the default interval for the local device to send Hello packets to a neighbor in the Down state on the NBMA network. The value of Poll Interval is greater than the value of Hello Interval. |
Router DR Priority |
Indicates the default priority of the DR. |
Retransmit Interval(sec) |
Indicates the default interval for retransmitting packets. |
Transmit Delay(sec) |
Indicates the default estimated time for transmitting an LSU packet over this interface. LSAs in the LSU packet must have their age incremented by this amount before transmission. |
display gtsm statistics
Usage Guidelines
You can run the display gtsm statistics command to view GTSM statistics, including the total number of BGP, BGPv6, LDP, and OSPF packets, the number of packets that have passed, and the number of discarded packets, on all LPUs.
Example
# View GTSM statistics on all LPUs.
<Huawei> display gtsm statistics all
GTSM Statistics Table ---------------------------------------------------------------- SlotId Protocol Total Counters Drop Counters Pass Counters ---------------------------------------------------------------- 0 BGP 0 0 0 0 BGPv6 0 0 0 0 OSPF 0 0 0 0 LDP 0 0 0 0 OSPFv3 0 0 0 0 RIP 0 0 0 ----------------------------------------------------------------
Item |
Description |
---|---|
SlotId |
Slot ID |
Protocol |
Protocol type:
|
Total Counters |
Total number of packets |
Drop Counters |
Total number of dropped packets |
Pass Counters |
Total number of packets that have passed |
display ospf abr-asbr
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
router-id |
Specifies the router ID of an ABR or ASBR. |
In dotted decimal notation. |
Usage Guidelines
Area Border Router (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.
AS Boundary Router (ASBR) exchanges routing information with other ASs. An ASBR may not reside at the boundary of an AS. It can be an internal device or an ABR. If an OSPF device imports external routes, the device is an ASBR.
This command can view information about the ABRs and ASBRs of OSPF.
Example
# Display information about the ABRs and ASBRs of OSPF.
<Huawei> display ospf abr-asbr
OSPF Process 1 with Router ID 100.10.10.10 Routing Table to ABR and ASBR RtType Destination Area Cost Nexthop Type Intra-area 10.10.10.11 0.0.0.0 1 10.2.0.3 ABR
Item |
Description |
---|---|
RtType |
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 device to the ABR or ASBR |
NextHop |
Next hop address through which packets are transmitted to the ABR or ASBR |
Type |
Area border router (ABR) or as boundary router (ASBR) |
display ospf asbr-summary
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
ip-address |
Specifies the matched IP address. |
It is in dotted decimal notation. |
mask |
Specifies the mask of the IP address. If no IP address or mask is specified, summarization information of all the imported routes is displayed. |
It is in dotted decimal notation. |
Usage Guidelines
After an AS is divided into areas, configuring route aggregation can reduce routing information transmitted between areas, thus reducing the size of the routing table and improving route performance.
Run asbr-summary command displays information about OSPF route summarization.
Example
# Display summarization information about all the imported OSPF routes.
<Huawei> display ospf asbr-summary
OSPF Process 1 with Router ID 192.168.1.2
Summary Addresses
Total summary address count: 1
Summary Address
net : 10.0.0.0
mask : 255.0.0.0
tag : 10 (Configured)
status : Advertise
Cost : 0 (Not Configured)
delay : 30 (Configured)
The Count of Route is : 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
Item |
Description |
---|---|
Total Summary address count |
Number of routes that are being summarized through the asbr-summary command |
net |
Network address of the summarized route |
mask |
Network mask of the summarized route |
tag |
Tag of the summarized route |
status |
Advertisement status of the summarized route:
|
Cost |
Cost of the summarized route |
delay |
Delay for advertising the summarized route |
The Count of Route is |
Number of routes that are being summarized |
Destination |
Destination address of the routes that are being summarized |
Net Mask |
Mask of the routes that are being summarized |
Proto |
Protocol of the routes that are being summarized |
Process |
Process ID |
Type |
Type of the imported AS external route, Type 1 or Type 2 |
Metric |
Metric of the routes that are being summarized |
display ospf bfd session
Format
display ospf [ process-id ] bfd session interface-type interface-number [ router-id ]
display ospf [ process-id ] bfd session { router-id | all }
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
interface-type interface-number |
Specifies the type and number of the interface. |
- |
router-id |
Specifies the router ID of the neighbor. |
In dotted decimal notation. |
all |
Indicates all the OSPF-enabled interfaces in the OSPF process. |
- |
Usage Guidelines
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. This speeds up OSPF's response to the change of the network topology.
The display ospf bfd session command displays information about the BFD-enabled neighbor.
Example
# Display information about the BFD-enabled neighbor.
<Huawei> display ospf bfd session all
OSPF Process 1 with Router ID 10.3.3.3 Area 0.0.0.0 interface 100.1.1.1(GigabitEthernet1/0/0)'s BFD Sessions NeighborId:10.2.2.2 AreaId:0.0.0.0 Interface:GigabitEthernet1/0/0 BFDState:up rx :1000 tx :1000 Multiplier:3 BFD Local Dis:8198 LocalIpAdd:10.1.1.1 RemoteIpAdd:10.1.1.2 Diagnostic Info:No diagnostic information
Item |
Description |
---|---|
NeighborId |
Router ID of the neighbor |
AreaId |
Area ID |
Interface |
Interface through which the local device establishes a BFD session with the neighbor |
BFDState |
BFD status:
|
rx |
Negotiated minimum interval for receiving BFD packets |
tx |
Negotiated minimum interval for sending BFD packets |
Multiplier |
Remote detection multiplier |
BFD Local Dis |
Local discriminator dynamically assigned by BFD |
LocalIpAdd |
Local IP address |
RemoteIpAdd |
Remote IP address |
Diagnostic Info |
Diagnostic information:
|
display ospf 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 the OSPF processes is displayed. |
The value is an integer ranging from 1 to 65535. |
Usage Guidelines
Configure Router ID
Configure VPN domain ID
When locating OSPF faults, you can run the display ospf brief command to obtain OSPF brief information. You can then analyze OSPF faults according to the brief information.
Example
# Display OSPF brief information.
<Huawei> display ospf brief
OSPF Process 1 with Router ID 10.137.217.210 OSPF Protocol Information RouterID: 10.137.217.210 Border Router: AREA Multi-VPN-Instance is not enabled Global DS-TE Mode: Non-Standard IETF Mode Graceful-restart capability: disabled Helper support capability : not configured Applications Supported: MPLS Traffic-Engineering Spf-schedule-interval: max 10000ms, start 500ms, hold 1000ms Default ASE parameters: Metric: 1 Tag: 1 Type: 2 Route Preference: 10 ASE Route Preference: 150 SPF Computation Count: 1 RFC 1583 Compatible Retransmission limitation is disabled Area Count: 2 Nssa Area Count: 0 ExChange/Loading Neighbors: 0 Process total up interface count: 1 Process valid up interface count: 0 Area: 0.0.0.6 (MPLS TE not enabled) Authtype: None Area flag: Normal SPF scheduled Count: 1 ExChange/Loading Neighbors: 0 Router ID conflict state: Normal Area interface up count: 1 Interface: 10.10.1.2 (GigabitEthernet1/0/0) Cost: 1 State: DR Type: Broadcast MTU: 1500 Timers: Hello 10 , Dead 40 , Poll 120 , Retransmit 5 , Transmit Delay 1
Item |
Description |
---|---|
RouterID |
Indicates the current router ID |
Border Router |
Indicates the border router:
|
Multi-VPN-Instance is not enabled |
Indicates that the current process does not support multi-VPN-instance. |
Applications Supported: MPLS Traffic-Engineering |
Indicates that OSPF supports Traffic Engineering (TE). |
Graceful-restart capability |
Indicates whether graceful restart is enabled:
|
Helper support capability |
Indicates whether the Helper mode is enabled:
|
Spf-schedule-interval |
Indicates the interval for performing SPF calculation. |
Route Preference |
Indicates the preference of the default route |
Default ASE parameters |
Indicates the default parameters of the external LSA.
|
ASE Route Preference |
Indicates the preference of the ASE route. |
SPF Computation Count |
Indicates the number of times that SPF calculation is performed. |
RFC 1583 Compatible |
Indicates whether RFC 1583 compatibility is enabled. |
Retransmission limitation is disabled |
Indicates that retransmission limit is disabled. |
Area Count |
Indicates the number of areas in the current process. |
Nssa Area Count |
Indicates the number of NSSAs in the current process. |
ExChange/Loading Neighbors |
Number of neighbors in the Exchange state and neighbors in the Loading state. |
Process total up interface count |
Indicates the number of interfaces that are up. |
Process valid up interface count |
Indicates the number of interfaces that are valid. |
Area |
Indicates information about each area in the current process, including ID of the current area in dotted decimal notation. |
Authtype |
Indicates the area authentication type, including none-authentication, simple authentication, MD5 authentication, HMAC-SHA256 authentication, and HMAC-MD5 authentication. |
Area flag |
Indicates the flag used to describe the area attributes, including Transit/Vlink/Stub/Nssa/Normal. |
SPF scheduled Count |
Indicates the number of times that the SPF calculation is performed. |
Interface |
Indicates interface information in the area. |
Cost |
Indicates the cost of an OSPF interface. |
State |
Indicates the interface status, including Down, Waiting, Loopback, P-2-P, DR, and BDR DROTHER. DR and BDR DROTHER exist in only broadcast and NBMA networks, and P-2-P exists in only P2P and P2MP Vlinks. |
Type |
Indicates the interface type, including P2P, broadcast, NBMA, and P2MP. |
MTU |
Indicates the MTU value of the interface. |
Timers |
Indicates the interval of the timer. |
Hello |
Indicates the interval of the Hello timer. |
Dead |
Indicates the interval of the Dead timer. |
Poll |
Indicates the interval of the Poll timer. |
Retransmit |
Indicates the interval of the Retransmit timer. |
Transmit Delay |
(Optional) Indicates the delay for transmitting LSAs on the interface. |
Global DS-TE Mode |
Indicates the globally configured DS-TE mode:
|
Router ID conflict state |
Indicates the status of the automatic recovery function. The value can be one of the following:
|
display ospf 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 65535. |
Example
# Display OSPF statistics.
<Huawei> display ospf cumulative
OSPF Process 1 with Router ID 10.1.1.1 Cumulations IO Statistics Type Input Output Hello 26 62 DB Description 3 2 Link-State Req 1 1 Link-State Update 5 5 Link-State Ack 3 3 ASE: 2 Checksum Sum: 233779 LSAs originated by this router Router: 1 Network: 0 Sum-Net: 0 Sum-Asbr: 0 External: 3 NSSA: 0 Opq-Link: 0 Opq-Area: 0 Opq-As: 0 LSAs Originated: 4 LSAs Received: 14 Routing Table: Intra Area: 2 Inter Area: 0 ASE: 2 Up Interface Cumulate: 2 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 Neighbor cumulative data. (Total) ------------------------------------------------------- Down: 0 Init: 0 Attempt: 0 2-Way: 0 Exstart: 0 Exchange: 0 Loading: 0 Full: 1 Retransmit Count: 0
Item |
Description |
---|---|
IO Statistics |
Statistics of the transmitted packets and LSAs |
Type |
OSPF packet type |
Input |
Number of received packets |
Output |
Number of sent packets |
Hello |
OSPF Hello packet |
DB Description |
OSPF Database Description packet |
Link-State Req |
OSPF Link State Request packet |
Link-State Update |
OSPF Link State Update packet |
Link-State Ack |
OSPF Link State Acknowledgement packet |
Checksum Sum |
Checksum of the AS external LSA |
ASE |
Number of ASE routes (when there are no ASE routes, Disabled is displayed) |
LSAs originated by this router |
Detailed statistics of the transmitted LSAs |
Router |
Router LSA |
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 |
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 up state interface |
Neighbor Cumulate |
Statistics of neighbors |
Neighbor cumulative data. |
Detailed statistics of neighbors:
|
Retransmit Count |
Total number of nodes in the retransmission list |
display ospf error
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. If no OSPF process ID is specified, error information of all OSPF processes is displayed. |
The value is an integer ranging from 1 to 65535. |
lsa |
Display the OSPF LSA errors. |
- |
interface interface-type interface-number |
Specifies the type and number of interfaces. |
- |
Usage Guidelines
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.
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 0 : 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 0 : Packet size > ip length 0 : Transmit error 0 : Interface down 0 : Unknown neighbor 0 : Bad net segment 0 : Extern option mismatch 0 : Router id confusion 0 : Bad authentication sequence numb HELLO packet errors: 0 : Netmask mismatch 0 : Hello timer mismatch 0 : Dead timer mismatch 0 : Virtual neighbor unknown 0 : NBMA neighbor unknown 0 : Invalid Source Address DD packet errors: 0 : Neighbor state low 0 : Unknown LSA type 0 : MTU option mismatch LS ACK packet errors: 0 : 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 0 : Newer self-generate LSA 0 : LSA checksum bad 0 : Received less recent LSA 0 : Unknown LSA type Opaque errors: 0 : 9-out of flooding scope 0 : 10-out of flooding scope 0 : 11-out of flooding scope 0 : Unknown TLV type 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
Item |
Description |
---|---|
General packet errors |
Indicates general packet errors. |
IP: received my own packet |
Indicates that the packet sent by its own interface is received. |
Bad packet |
Indicates that the parsed packet is incorrect, including the checksum of the length field. |
Bad version |
Indicates that the OSPF version is incorrect, that is, it is not version 2. |
Bad checksum |
Indicates that the OSPF checksum is incorrect. |
Bad area id |
Indicates that the area ID in the received packet does not match the local area ID. (Vlink can receive packets from only Area 0 and its own area.) |
Drop on unnumbered interface |
Indicates that the unnumbered rather than P2P interface receives packets (the interface must be of the P2P type). |
Bad virtual link |
Indicates that the Vlink receives invalid packets. |
Bad authentication type |
Indicates that packet authentication is incorrect. |
Bad authentication key |
Indicates that authentication key is incorrect. |
Packet size > ip length |
Indicates that the length of the OSPF packet is greater than the permitted length of the IP packet. |
Bad net segment |
The source address of received packets is not on the same network segment as the IP address of the interface that receives packets. |
Packet too small |
Indicates that the length of the received packet does not equal the sum of the IP header length and the packet length. |
Transmit error |
Indicates that sending packets to the socket fails. |
Interface down |
Indicates the number of times that the OSPF interface goes Down. |
Unknown neighbor |
Indicates that OSPF packets are received from non-OSPF neighbors on NBMA networks, virtual links, and sham links. |
Extern option mismatch |
Indicates that the extension attributes of the Hello packets on the two ends are inconsistent. If the value of this field keeps increasing, the area types of the two devices that establish the neighbor relationship are inconsistent (the area type of one device is common area, and the area type of the other device is stub area or NSSA). In this case, configure the same area type for the two devices (in the OSPF area view, the stub command indicates the area type is stub and the stub command indicates the area type is nssa). |
HELLO packet errors |
Indicates Hello packet errors. |
Netmask mismatch |
Indicates that the address mask does not match the local address mask. |
Hello timer mismatch |
Indicates that the Hello intervals on the two ends are inconsistent. |
Dead timer mismatch |
Indicates that the Dead intervals on the two ends are inconsistent. |
Router id confusion |
Indicates that the router IDs on the two ends are the same. |
Bad authentication sequence numb |
Indicates the number of bad authentication sequence. |
Virtual neighbor unknown |
Indicates that the router ID of the packet is inconsistent with that of the neighbor that is configured by the virtual link. |
NBMA neighbor unknown |
Indicates that the status of the NBMA neighbor is not active. |
Invalid Source Address |
Indicates that the source address is invalid. |
DD packet errors |
Indicates DD packet errors. |
Neighbor state low |
Indicates the following situations:
|
Newer self-generate LSA |
Indicates the number of new self-generated LSAs. This field is reserved for future use. |
MTU option mismatch |
Indicates that 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. |
Unknown LSA type |
Indicates the unknown LSA type. |
LSA checksum bad |
Indicates that the LSA checksum is incorrect. |
LS ACK packet errors |
Indicates LSAck packet errors. |
LS REQ packet errors |
Indicates LSR packet errors. |
Empty request |
Indicates empty LSR packets. |
Bad request |
Indicates the BadRequest event in the protocol. |
LS UPD packet errors |
Indicates LSU packet errors. |
Received less recent LSA |
Indicates that the LSA older than the local LSA is received. |
Opaque errors |
Indicates opaque errors. |
9-out of flooding scope |
Indicates the number of Type 9 LSAs that exceed the flooding scope. |
10-out of flooding scope |
Indicates the number of Type 10 LSAs that exceed the flooding scope. |
11-out of flooding scope |
Indicates the number of Type 11 LSAs that exceed the flooding scope. |
Unknown TLV type |
Indicates the unknown TLV type. |
Retransmission for packet over Limitation errors |
Indicates the number of times that retransmitting packets expires. |
Number for DD Packet |
Indicates the number of times that retransmitting DD packets expires. |
Number for Update Packet |
Indicates the number of times that retransmitting LSU packets expires. |
Number for Request Packet |
Indicates the number of times that retransmitting LSR packets expires. |
Receive Grace LSA errors |
Indicates the number of received incorrect Grace LSAs. |
Number of invalid LSAs |
Indicates the number of invalid LSAs. |
Number of policy failed LSAs |
Indicates the number of policy failed LSAs. |
Number of wrong period LSAs |
Indicates the number of wrong period LSAs. |
Configuration errors |
Indicates configuration errors. |
Tunnel cost mistake |
Indicates the 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. |
<Huawei> display ospf error interface gigabitethernet 1/0/0
OSPF Process 1 with Router ID 20.1.1.1 OSPF error statistics Interface: GigabitEthernet1/0/0 (1.2.0.1) General packet errors: 0 : Bad version 0 : Bad checksum 0 : Bad area id 0 : Bad authentication type 0 : Bad authentication key 0 : Unknown neighbor 0 : Bad net segment 0 : Extern option mismatch 0 : Router id confusion HELLO packet errors: 0 : Netmask mismatch 0 : Hello timer mismatch 0 : Dead timer mismatch 0 : Invalid Source Address DD packet errors: 0 : MTU option mismatch LS REQ packet errors: 0 : Bad request LS UPD packet errors: 0 : LSA checksum bad Receive Grace LSA errors: 0 : Number of invalid LSAs 0 : Number of policy failed LSAs 0 : Number of wrong period LSAs
display ospf global-statistics
Function
The display ospf global-statistics command displays global OSPF statistics. If no OSPF process ID is specified, brief information about all the OSPF processes is displayed.
Format
display ospf global-statistics { process process-id | vpn-instance vpn-instance-name | public-instance | timewheel | brief }
Parameters
Parameter | Description | Value |
---|---|---|
process process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
vpn-instance vpn-instance-name |
Specifies the name of a VPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
public-instance |
Displays the statistics of all the public network instances. |
- |
timewheel |
Displays the number of updated or aged LSAs in different periods. |
- |
brief |
Displays brief information. |
- |
Usage Guidelines
To display global OSPF statistics, run display ospf global-statistics command. If no OSPF process ID is specified, brief information about all the OSPF processes is displayed.
Example
# Display global OSPF statistics, including statistics of neighbors, processes, and instances.
<Huawei> display ospf global-statistics brief
Neighbor cumulative data (OSPF total statistics):
----------------------------------------------------------
Down: 0 Init: 0 Attempt: 0 2-Way: 0
Exstart: 0 Exchange: 0 Loading: 0 Full: 2400
Instance Number: 1 Process Number: 2
HighSocketExpire: 27 HighSocketEmpty: 526275
Total Neighbor Number: 0
Total Press: LOW
Item |
Description |
---|---|
Neighbor cumulative data (OSPF total statistics) |
Neighbor statistics |
Instance Number |
Number of instances, including public network instances and VPN instances |
Process Number |
Number of OSPF processes running on the device |
HighSocketExpire |
Number of unprocessed messages in high-priority queues |
HighSocketEmpty |
Number of processed messages in high-priority queues |
Total Neighbor Number |
Total number of OSPF neighbors |
Total Press |
Total pressure of the current service In most cases, the Total Press field is LOW. If the number of retransmission timers or the number of LSAs being flooded in the OSPF processes exceeds a certain value (default 300), or the number of OSPF neighbors exceeds 300, the Total Press field is HIGH. If the number of retransmission timers and the number of LSAs being flooded in the OSPF processes fall below a certain value (default 300), and the number of OSPF neighbors falls below 300, the Total Press field is LOW. |
# Display global statistics of OSPF process 1.
<Huawei> display ospf global-statistics process 1
OSPF 1 statistics data:
-----------------------------------------
LSA NUM of Flood cache: 0
Packet NUM of FloodUpdt Hash: 0
Packet NUM of Flood Queue: 0
Item |
Description |
---|---|
LSA NUM of Flood cache |
Indicates the number of LSAs being flooded in the OSPF process. |
Packet NUM of FloodUpdt Hash |
Indicates the number of Update packets waiting to be flooded in the OSPF process, and the number does not reach the MTU. |
Packet NUM of Flood Queue |
Indicates the number of Update packets waiting to be flooded in the OSPF process, and the number reaches the MTU. |
# Display OSPF time wheel information.
<Huawei> display ospf global-statistics timewheel
=================== TimeWheel Info Begin ===================
TimeWheel current index is 2845, datanode count is 8
Bucket Number: 3596, Expiry time: 1306(s), Datanode Count: 0
High expiry time: 0, Low expiry time 527742(s)
Bucket Number: 3597, Expiry time: 1307(s), Datanode Count: 0
High expiry time: 0, Low expiry time 527743(s)
Bucket Number: 3598, Expiry time: 1308(s), Datanode Count: 0
Item |
Description |
---|---|
TimeWheel current index |
Indicates the current index of the time wheel. |
Datanode Count |
Indicates the total number of nodes in the time wheel. |
Bucket Number |
Indicates the total number of indexes of the time wheel. |
Expiry time |
Indicates the expiry time of the index. |
High expiry time |
Indicates the high expiry time corresponding to the index in the time wheel after the system starts. |
Low expiry time |
Indicates the low expiry time corresponding to the index in the time wheel after the system starts. |
display ospf graceful-restart
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
verbose |
Displays detailed information about OSPF GR. |
- |
Usage Guidelines
You can run the display ospf graceful-restart command to view details of the GR and the statistics.
Example
# Display OSPF GR information.
<Huawei> display ospf graceful-restart
OSPF Process 1 with Router ID 10.1.1.1 Graceful-restart capability : enabled Graceful-restart support : planned and un-planned, totally Helper-policy support : planned and un-planned, strict lsa check Current GR state : normal Graceful-restart period : 120 seconds Number of neighbors under helper: Normal neighbors : 0 Virtual neighbors : 0 Sham-link neighbors : 0 Total neighbors : 0 Number of restarting neighbors : 0 Last exit reason: On graceful restart : successful exit On Helper : none
# Display detailed information about OSPF GR.
<Huawei> display ospf graceful-restart verbose
OSPF Process 1 with Router ID 10.1.1.1 Graceful-restart capability : enabled Graceful-restart support : planned and un-planned, totally Helper-policy support : planned and un-planned, strict lsa check Current GR state : normal Graceful-restart period : 120 seconds Number of neighbors under helper: Normal neighbors : 0 Virtual neighbors : 0 Sham-link neighbors : 0 Total neighbors : 0 Number of restarting neighbors : 0 Last exit reason: On graceful restart : successful exit On Helper : none All area count : 1 Area ID : 0.0.0.0 Authtype : None Area flag : Normal Normal interface count: 1 Interface: 10.1.1.1 (GigabitEthernet1/0/0) GR state : normal State: P-2-P Type: P2P Last Helper Exit reason: none Neighbor count of this interface : 1 Neighbor IP address GR state Last Helper Exit reason 10.2.2.2 10.1.1.2 Normal none
Item |
Description |
---|---|
Graceful-restart capability |
Whether IETF GR is enabled:
|
Graceful-restart support |
IETF GR mode that is supported currently:
|
Helper-policy support |
Policy that supports the Helper:
|
Current GR state |
Current GR status:
|
Graceful-restart period |
GR period |
Number of neighbors under helper |
Number of neighbors in the Helper state:
|
Number of restarting neighbors |
Number of restarted devices displayed on the Helper |
Last exit reason |
Reason that a device exits from GR last time:
|
On graceful restart |
Reason that the Restarter exits from GR:
|
On Helper |
Reason that the Helper exits from GR:
|
All area count |
Number of areas in the process |
Area ID |
Area ID |
Authtype |
Authentication type |
Area flag |
Area attributes:
|
Normal interface count |
Number of interfaces in the area |
Interface |
IP address of the interface |
GR state |
GR status of the interface:
|
State |
Interface status:
|
Type |
Interface type:
|
Last Helper Exit reason |
Reason that the neighbor exits from the Helper mode the last time:
|
Neighbor count of this interface |
Total number of neighbors of this interface |
Neighbor |
Router ID of the neighbor |
IP address |
IP address of the neighboring interface |
GR state |
GR status of the neighbor:
|
display ospf interface
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
all |
Displays information about all OSPF interfaces. |
- |
interface-type interface-number |
Specifies the interface type and the interface number. |
- |
verbose |
Display verbose configuration information. |
- |
Usage Guidelines
The display ospf interface command output displays the configuration and operating status of OSPF, which facilitate fault location and configuration verification.
Example
# Display OSPF interface information.
<Huawei> display ospf interface
OSPF Process 1 with Router ID 192.168.1.1 Interfaces Area: 0.0.0.0 (MPLS TE not enabled) IP Address Type State Cost Pri DR BDR 192.168.1.2 Broadcast DR 1 1 192.168.1.2 192.168.1.3 Area: 0.0.0.1 (MPLS TE not enabled) IP Address Type State Cost Pri DR BDR 172.16.0.1 Broadcast DR 1 1 172.16.0.1 172.16.0.2
<Huawei> display ospf interface gigabitethernet 1/0/0
OSPF Process 1 with Router ID 1.1.1.1 Interfaces Interface: 192.168.1.1 ( gigabitethernet 1/0/0 ) Cost: 1 State: DR Type: Broadcast MTU: 1500 Priority: 1 Designated Router: 192.168.1.2 Backup Designated Router: 192.168.1.3 Timers: Hello 10 , Dead 40 , Poll 120 , Retransmit 5 , Transmit Delay 1 IO Statistics Type Input Output Hello 161367 10436 DB Description 18 18 Link-State Req 5 6 Link-State Update 203780 210 Link-State Ack 90411 276 ALLSPF GROUP ALLDR GROUP OpaqueId: 1 PrevState: BDR Effective cost: 1, enabled by OSPF Protocol. Suppress flapping peer: enable(flapping-count: 0, threshold: 20)
Item |
Description |
---|---|
Area |
ID of the area to which the interface belongs |
IP address |
IP address of the interface (regardless of whether TE is enabled on the interface) |
Type |
Interface type: P2P, PTMP, broadcast, or NBMA |
State |
Status of the interface, which is determined by the OSPF interface state machines
|
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. |
DR |
DR of the network where the interface resides |
BDR |
BDR of the network where the interface resides |
Interface |
Interface IP address + interface number + IP address of the neighbor, which is used for P2P |
MTU |
MTU value of the interface |
Priority |
Priority of the device interface during the DR and BDR election The greater the value, the higher the priority. The value is an integer ranging from 0 to 255. |
Designated Router |
DR of the network where the interface resides |
Backup Designated Router |
BDR of the network where the interface resides |
Timer Hello |
Interval for sending Hello packets |
Dead |
Dead time of devices |
Poll |
Interval for sending Poll packets |
Retransmit |
Interval for retransmitting LSAs |
Transmit Delay |
Interface transmission delay |
Suppress flapping peer |
Status of OSPF neighbor relationship flapping suppression:
|
display ospf lsdb
Format
display ospf [ process-id ] lsdb [ brief ]
display ospf [ process-id ] lsdb [ { router | network | summary | asbr | ase | nssa | opaque-link | opaque-area | opaque-as } [ link-state-id ] ] [ originate-router [ advertising-router-id ] | self-originate ] [ age { min-value min-age-value | max-value max-age-value } * ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
brief |
Displays brief information about the LSDB. |
- |
router |
Displays information about the device LSA. |
- |
network |
Displays information about the network LSA. |
- |
summary |
Displays information about the network summary LSA. |
- |
asbr |
Displays information about the ASBR summary LSA. |
- |
ase |
Displays information about the AS external LSA. |
- |
nssa |
Displays information about the status of external links in the NSSA. |
- |
opaque-link |
Displays information about the opaque link LSA. |
- |
opaque-area |
Displays information about the opaque area LSA. |
- |
opaque-as |
Displays information about the opaque AS LSA. |
- |
originate-router |
Displays the LSA of the advertising router. |
- |
link-state-id |
Specifies the ID of an LSA. |
The value is an IP address in dotted decimal notation. |
advertising-router-id |
Specifies the Router ID of the device that advertises the LSA. |
The value is an IP address in dotted decimal notation. |
self-originate |
Displays information about the self-originated LSA. |
- |
age |
Displays the LSAs that meet the age filtering rule. |
- |
min-value min-age-value |
Displays information about only LASs with the age value greater than or equal to the min-age-value value. |
The value is an integer ranging from 0 to 3600. |
max-value max-age-value |
Displays information only about LASs with the age value less than or equal to the max-age-value value. |
The value is an integer ranging from 0 to 3600. |
Usage Guidelines
By running the display ospf lsdb command displays information about the LSDB in various modes. That is, you can view any of the following:
- Brief information about the LSDB
- LSAs of a specified type
- LSAs of the originating device
- Locally originated LSAs
The command output can display information about the OSPF LSDB, which helps you troubleshoot OSPF faults.
Example
# Display brief 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.2.2.2 10.2.2.2 98 36 8000000B 1 Router 10.1.1.1 10.1.1.1 92 36 80000005 1 Network 10.1.1.2 10.2.2.2 98 32 80000004 0 Sum-Net 10.1.1.0 10.2.2.2 286 28 80000001 1 Sum-Net 10.1.1.0 10.1.1.1 282 28 80000001 1 Sum-Asbr 10.2.2.2 10.1.1.1 61 28 80000001 1
Item |
Description |
---|---|
Area |
Area whose LSDB information needs to be displayed |
Type |
LSA type: Router, Network, Sum-Net, Sum-Asbr, NSSA, External, Opq-Link, Opq-Area, and Opq-As |
LinkState ID |
Link State ID in the LSA header |
AdvRouter |
Device that advertises or generates LSAs |
Age |
Aging time of the LSA |
Len |
Size of the LSA |
Sequence |
Sequence number in the LSA header |
Metric |
Metric |
# Display brief information about the OSPF LSDB.
<Huawei> display ospf lsdb brief
OSPF Process 123 with Router ID 192.168.200.183 LS Database Statistics Area ID Stub Router Network S-Net S-ASBR Type-7 | Subtotal 0.0.0.0 0 0 0 0 0 0 | 0 Total 0 0 0 0 0 0 | -------------------------------------------------------------------+--------- Area ID Opq-9 Opq-10 | Subtotal 0.0.0.0 0 0 | 0 Total 0 0 | -------------------------------------------------------------------+--------- ASE Opq-11 | Subtotal Total 0 0 | 0 -------------------------------------------------------------------+--------- | Total | 0
Item |
Description |
---|---|
Area ID |
Area ID whose LSDB information needs to be displayed |
Stub |
The stub area that displays the LSDB information |
Router |
Device that advertises or generates LSAs |
Network |
Network that advertises or generates LSAs |
S-Net |
System Network that advertises or generates LSAs |
S-ASBR |
S-ASBR that advertises or generates LSAs |
Type-7 |
LSA type |
Subtotal |
Total number of stub areas |
# Display information about router LSAs in the LSDB.
<Huawei> display ospf lsdb router
OSPF Process 1 with Router ID 10.137.217.208 Area: 0.0.0.1 Link State Database Type : Router Ls id : 10.137.217.210 Adv rtr : 10.137.217.210 Ls age : 1564 Len : 36 Options : ABR E seq# : 80000003 chksum : 0xeb06 Link count: 1 * Link ID: 192.168.4.1 Data : 192.168.4.2 Link Type: TransNet Metric : 1 Type : Router Ls id : 10.137.217.208 Adv rtr : 10.137.217.208 Ls age : 1556 Len : 36 Options : E seq# : 80000005 chksum : 0xf6fe Link count: 1 * Link ID: 192.168.4.1 Data : 192.168.4.1 Link Type: TransNet Metric : 1 Priority : Medium
Item |
Description |
---|---|
Ls id |
Link State ID in the LSA header |
Adv rtr |
The device that advertises or generates LSAs |
Ls age |
Aging time of the LSA |
Options |
Indicates the Options field as below:
|
seq# |
Sequence number, which is used to check the order of LSAs |
Chksum |
LSA checksum |
Link count |
Number of links |
* Link ID |
Link ID of the router LSA, which is classified according to the link type
|
Data |
Link data of the router LSA
|
Link Type |
Link type of the router LSA: P-2-P, TransNet, StubNet, or Virtual |
Metric |
Link metric of the router LSA |
Priority |
OSPF convergence priority |
# Display information about network LSAs in the LSDB.
<Huawei> display ospf 1 lsdb network 10.1.1.1
OSPF Process 1 with Router ID 10.1.1.1
Area: 0.0.0.0
Link State Database
Type : Network
Ls id : 10.1.1.1
Adv rtr : 10.1.1.1
Ls age : 167
Len : 32
Options : E
seq# : 80000002
chksum : 0x3408
Net mask : 255.255.255.0
Priority : Low
Attached Router 10.2.2.2
Attached Router 10.1.1.1
Item |
Description |
---|---|
Net mask |
Network mask of the network LSA |
Attached Router |
Device that is connected to the network |
# Display information about network summary LSAs in the LSDB.
<Huawei> display ospf 1 lsdb summary 10.20.1.0
OSPF Process 1 with Router ID 10.1.1.1
Area: 0.0.0.0
Link State Database
Type : Sum-Net
Ls id : 10.1.1.0
Adv rtr : 10.2.2.2
Ls age : 419
Len : 28
Options : E
seq# : 80000001
chksum : 0x1d21
Net mask : 255.255.255.0
Tos 0 metric: 1
Priority : Medium
Item |
Description |
---|---|
Net mask |
Network mask of the network summary LSA |
Tos |
Type of service of the network summary LSA |
Metric |
Metric or cost of the route from the advertising router to the network, which is carried in the network summary LSA |
<Huawei> display ospf 1 lsdb asbr 10.2.2.2
OSPF Process 1 with Router ID 10.1.1.1 Area: 0.0.0.2 Link State Database Type : Sum-Asbr Ls id : 10.2.2.2 Adv rtr : 10.1.1.1 Ls age : 90 Len : 28 Options : E seq# : 80000001 chksum : 0xec62 Tos 0 metric: 1
<Huawei> display ospf 100 lsdb ase 10.1.1.0
OSPF Process 1 with Router ID 10.1.1.1 Link State Database Type : External Ls id : 10.1.1.0 Adv rtr : 10.2.2.2 Ls age : 569 Len : 36 Options : E seq# : 80000002 chksum : 0x90d0 Net mask : 255.255.255.0 TOS 0 Metric: 1 E type : 2 Forwarding Address : 0.0.0.0 Tag : 1 Priority : Medium
Item |
Description |
---|---|
Net mask |
Network mask of the ASE or NSSA LSA |
Tos |
Type of service of the ASE or NSSA LSA |
Metric |
Metric or cost of the route from the advertising router to the network, which is carried in the ASE or NSSA LSA |
E type |
E type of the ASE or NSSA LSA |
Forwarding Address |
Forwarding address of the ASE or NSSA LSA |
Tag |
32-bit tag, which is carried in ASE or NSSA LSA to avoid routing loops |
# Display information about NSSA external LSAs in the LSDB.
<Huawei> display ospf 1 lsdb nssa 192.168.1.0
OSPF Process 1 with Router ID 10.1.1.1
Area: 0.0.0.1
Link State Database
Type : NSSA
Ls id : 10.1.1.0
Adv rtr : 10.2.2.2
Ls age : 521
Len : 36
Options : None
seq# : 80000005
chksum : 0x9ea7
Net mask : 255.255.255.0
TOS 0 Metric: 1
E type : 2
Forwarding Address : 10.1.1.2
Tag : 1
Priority : Medium
# Display information about Opaque-link LSAs in the LSDB.
<Huawei> display ospf 1 lsdb opaque-link
OSPF Process 1 with Router ID 10.1.1.1
Area: 0.0.0.0
Link State Database
Link State Database for interface 10.1.1.1 (Vlanif200) Type: Broadcast
Type : Opq-Link
Ls id : 10.0.0.0
Adv rtr : 10.2.2.2
Ls age : 12
Len : 44
Options : E
seq# : 80000001
chksum : 0x9579
Opaque type : 3, Opaque ID : 0
Grace LSA TLV information:
Grace Period : 1800
GR reason : 1
IP address : 10.1.1.2
Item |
Description |
---|---|
Opaque Type |
Opaque-link LSA |
Opaque ID |
Opaque ID of an Opaque-link LSA (Link state ID in the LSA header consists of Opaque type and Opaque ID.) |
Grace LSA TLV information: |
GR information |
Grace Period |
GR waiting period |
GR reason |
Cause of GR
|
IP address |
Address of the interface that performs GR on the router |
# Display information about Opaque-area LSAs in the 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
display ospf migp-routing
Function
The display ospf migp-routing command displays OSPF Multicast IGP (MIGP) routing information.
Format
display ospf [ process-id ] migp-routing [ ip-address [ mask | mask-length ] ] [ interface interface-type interface-number ] [ nexthop nexthop-address ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
ip-address |
Specifies the IP address. |
In dotted decimal notation. |
mask |
Specifies the subnet mask. |
In dotted decimal notation. |
mask-length |
Specifies the mask length. |
The value is an integer ranging from 0 to 32. |
interface interface-type interface-number |
Specifies the type and the number of the interface. |
- |
nexthop nexthop-address |
Displays the route with the specified next hop IP address. |
In dotted decimal notation. |
Usage Guidelines
Usage Scenario
When multicast and MPLS TE tunnels are configured on the network, and the TE tunnels are configured with IGP Shortcut, the outbound interface that an IGP calculated for a route may be not a physical interface but a TE tunnel interface. Based on a unicast route to a multicast source address, a router can send a Join message through a TE tunnel interface. In this case, devices spanned by the TE tunnel cannot detect the Join message so that they do not create any multicast forwarding entry.
To solve this problem, you can run the local-mt enable command to configure local multicast topology (MT). MT allows multicast routing entries to be created correctly.
If local MT is enabled, and the outbound interface of the calculated route is a TE tunnel interface of IGP Shortcut type, the route management (RM) module creates a separate Multicast IGP (MIGP) routing table for the multicast protocol, calculates the physical outbound interface of the route, and adds the IP address of the physical outbound interface to the MIGP routing table.
Running the display ospf migp-routing command can view the physical outbound interface of the route with the outbound interface of the TE tunnel interface. The physical outbound interface is OSPF routing information in the MIGP routing table.
Precautions
- Local MT supports only OSPF processes of public network instances.
- Local MT does not support forwarding adjacency (FA).
Example
# Display OSPF MIGP routing information.
<Huawei> display ospf migp-routing
OSPF Process 1 with Router ID 10.2.2.2 MIGP Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 192.168.3.0/24 4 Stub 10.0.1.1 10.5.5.5 0.0.0.0 10.0.3.0/24 3 Transit 10.0.1.1 10.5.5.5 0.0.0.0 Total Nets: 4 Intra Area: 4 Inter Area: 0 ASE: 0 NSSA: 0
Item |
Description |
---|---|
Destination |
Indicates the destination IP address. |
Cost |
Indicates the cost of the route to the destination address. |
Type |
Router types are as follows:
|
NextHop |
Indicates the next hop address to the destination address. |
AdvRouter |
Indicates the advertising router. |
Area |
Indicates the area ID. |
Total Nets |
Indicates the total number of networks in an area, between areas, in ASE areas, and in NSSAs. |
Intra Area |
Indicates the total number of intra-area routes (that is, stub routes and transit routes). |
Inter Area |
Indicates the total number of inter-area routes. |
ASE |
Indicates the total number of routes in the ASE area. |
NSSA |
Indicates the total number of routes in the NSSA. |
# Display OSPF MIGP routing information with the specified next hop address.
<Huawei> display ospf migp-routing nexthop 10.0.1.1
OSPF Process 1 with Router ID 10.2.2.2 Destination : 192.168.3.0/24 AdverRouter : 10.5.5.5 Area : 0.0.0.0 Cost : 4 Type : Stub NextHop : 10.0.1.1 Interface : Vlanif10 Priority : Low Destination : 10.4.4.4/32 AdverRouter : 10.4.4.4 Area : 0.0.0.0 Cost : 3 Type : Stub NextHop : 10.0.1.1 Interface : Vlanif20 Priority : Medium
Item |
Description |
---|---|
Priority |
Indicates OSPF convergence priorities:
|
display ospf mesh-group
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. If no process ID is specified, brief information about mesh groups in all OSPF processes is displayed. |
The value is an integer ranging from 1 to 65535. |
brief |
Displays brief information about mesh groups in each OSPF area. |
- |
Usage Guidelines
When concurrent links exist between a router and its neighbor, run the mesh-group enable command to enable the mesh group function and identify the mesh group using the router ID of the router. When receiving LSAs, the router will select a main link to flood LSAs. The link interface does not flood reversely. This avoids repeated flooding, reducing link load and saving resources.
Running the display ospf mesh-group command can view brief information about mesh groups in a specified process in an OSPF area.
Example
# Display brief information about OSPF mesh groups.
<Huawei> display ospf mesh-group
OSPF Process 1 with Router ID 1.1.1.1 Mesh-Groups Area: 0.0.0.0 Mesh-Group ID: 2.2.2.2 Interface IP Address/Mask Nbr State GigabitEthernet1/0/0 192.168.4.1/24 Full Count of Interface in this Mesh-Group: 1 Count of Mesh-Group in this Area: 1
Item |
Description |
---|---|
Area |
OSPF area |
Mesh-Group ID |
Key ID of a mesh group, namely, the router ID of a neighbor |
Interface |
Interface enabled with the mesh-group feature |
IP Address/Mask |
IP address and mask of the interface enabled with the mesh-group feature |
Nbr State |
Neighbor status on the interface enabled with the mesh-group feature |
Count of Interface in this Mesh-Group |
Number of interfaces in the mesh group |
Count of Mesh-Group in this Area |
Number of mesh groups in the area |
display ospf nexthop
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
Usage Guidelines
The command output can display information about all the OSPF next hops, which helps you troubleshoot OSPF faults.
Example
# Display OSPF next hop information.
<Huawei> display ospf nexthop
OSPF Process 100 with Router ID 10.0.0.1 Routing Nexthop information Next hops: Address Type Refcount IntfAddr Intf Name ---------------------------------------------------------------------- 10.0.0.1 Local 3 10.0.0.1 GigabitEthernet1/0/0 10.0.0.2 Local 5 10.0.0.1 GigabitEthernet1/0/0
Item |
Description |
---|---|
Next hops |
Detailed information about the next hop. |
Address |
Address of the 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. |
IntfAddr |
IP address of the interface. |
Intf Name |
Name of the interface. |
display ospf peer
Format
display ospf [ process-id ] peer [ [ interface-type interface-number ] [ neighbor-id ] | brief | last-nbr-down ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
interface-type interface-number |
Specifies the interface type and the interface number. |
- |
neighbor-id |
Specifies the neighbor's Router ID. |
It is in dotted decimal notation. |
brief |
Displays brief information about neighbors in each OSPF area. |
- |
last-nbr-down |
Displays brief information about the last neighbor that goes Down in the OSPF area. |
- |
Usage Guidelines
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).
Example
# Display information about the OSPF neighbor.
<Huawei> display ospf peer
OSPF Process 1 with Router ID 10.1.0.5
Neighbors
Area 0.0.0.0 interface 10.1.0.17(GigabitEthernet1/0/0)'s neighbors
Router ID: 10.1.1.1 Address: 10.1.0.18 GR State: Normal
State: Full Mode:Nbr is Slave Priority: 1
DR: 10.1.0.18 BDR: 10.1.0.17 MTU: 0
Dead timer due in 35 sec
Retrans timer interval: 5
Neighbor is up for 00:00:05
Authentication Sequence: [ 0 ]
Item |
Description |
---|---|
Area |
Area to which the neighbor belongs |
interface |
Interface that connects to the neighbor |
Router ID |
Router ID of the neighbor |
Address |
Address of the neighboring interface |
GR State |
GR status after OSPF GR is enabled:
|
State |
Neighbor status:
|
Mode |
Master or slave in the process of exchanging DD packets:
|
Priority |
Priority of the neighboring device |
DR |
Designated router |
BDR |
Backup designated router |
MTU |
MTU value of the neighboring interface |
Dead timer due in 35 sec |
The dead timer due in 35 seconds |
Retrans timer interval |
Interval for retransmitting LSAs, in seconds |
Neighbor is up for |
Time before an OSPF neighbor relationship is established |
Authentication Sequence |
Authentication sequence number |
# Display brief information about OSPF neighbors.
<Huawei> display ospf 1 peer brief
OSPF Process 1 with Router ID 1.1.1.1 Peer Statistic Information ------------------------------------------------------------------- Area Id Interface Neighbor id State 0.0.0.0 GigabitEthernet1/0/0 3.3.3.3 Full ------------------------------------------------------------------- Total Peer(s): 1
Item |
Description |
---|---|
Area Id |
Area to which the neighbor belongs |
Interface |
Interface that connects to the neighbor |
Neighbor id |
Router ID of the neighbor |
State |
State of the neighbor |
# 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 : 20.2.1.2 Neighbor Area Id : 0.0.0.0 Neighbor Router Id : 2.2.2.2 Interface : GigabitEthernet1/0/0 Immediate Reason : Neighbor Down Due to Kill Neighbor Primary Reason : Logical Interface State Change Down Time : 2012-09-14 17:17:7
Item |
Description |
---|---|
Neighbor Ip Address |
Address of the neighboring interface |
Neighbor Area Id |
Area to which the neighbor belongs |
Neighbor Router Id |
Router ID of the neighbor |
Interface |
Interface that connects to the neighbor |
Immediate Reason |
Immediate reason that the neighbor goes Down:
|
Primary Reason |
Primary reason that the neighbor goes Down:
|
Down Time |
Time when the neighbor goes Down |
display ospf request-queue
Format
display ospf [ process-id ] request-queue [ interface-type interface-number ] [ neighbor-id ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
interface-type interface-number |
Specifies the interface type and number. |
- |
neighbor-id |
Specifies the neighbor's Router ID. |
It is in dotted decimal notation. |
Example
# Display the OSPF request list.
<Huawei> display ospf request-queue
OSPF Process 1 with Router ID 10.1.1.1
OSPF Request List
The Router's Neighbor is Router ID 10.4.4.4 Address 172.16.4.2
Interface 172.16.4.1 Area 0.0.0.2
Request list:
Type LinkState ID AdvRouter Sequence Age
Router 10.1.1.1 10.1.1.1 8000001b 677
Item |
Description |
---|---|
The Router's Neighbor is Router ID |
Router ID of the neighbor |
Address |
IP address of the neighboring interface |
Interface |
IP address of the interface |
Area |
Area to which the local device belongs |
Request list |
Request list |
Type |
LSA type: Router LSA, network LSA, network summary LSA, ASBR summary LSA, AS external LSA, NSSA LSA, and 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
Format
display ospf [ process-id ] retrans-queue [ interface-type interface-number ] [ neighbor-id ] [ low-level-of-retrans-times-range min-time ] [ high-level-of-retrans-times-range max-time ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
interface-type interface-number |
Specifies the interface type and number. |
- |
neighbor-id |
Specifies the neighbor's Router ID. |
It is in dotted decimal notation. |
low-level-of-retrans-times-range min-time |
Min value of LSA retrans timers range. |
The value is an integer ranging from 0 to 65535. |
high-level-of-retrans-times-range max-time |
Max value of LSA retrans timers range. |
The value is an integer ranging from 1 to 65535. |
Example
# Display the OSPF retransmission list.
<Huawei> display ospf retrans-queue
OSPF Process 1 with Router ID 10.1.1.1 OSPF Retransmit List The Router's Neighbor is Router ID 10.2.2.2 Address 192.168.0.2 Interface 192.168.0.1 Area 0.0.0.0 Retransmit list: Type LinkState ID AdvRouter Sequence Age Router 10.1.1.1 10.1.1.1 80000002 533
Item |
Description |
---|---|
The Router's Neighbor |
Basic information about the neighboring router |
Router ID |
Router ID of the neighbor |
Address |
IP address of the neighboring interface |
Interface |
IP address of the interface |
Area |
Area ID |
Retransmit list |
Retransmission list |
Type |
LSA type Router LSA, network LSA, network summary LSA, ASBR summary LSA, AS external LSA, NSSA LSA, and 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 routing
Format
display ospf [ process-id ] routing router-id [ router-id ]
display ospf [ process-id ] routing [ ip-address [ mask | mask-length ] ] [ interface interface-type interface-number ] [ nexthop nexthop-address ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
router-id router-id |
Specifies the router ID of a destination router. |
The value is in dotted decimal notation. |
ip-address |
Specifies the IP address. |
The value is in dotted decimal notation. |
mask |
Specifies the subnet mask. |
The value is in dotted decimal notation. |
mask-length |
Specifies the mask length. |
The value is an integer ranging from 0 to 32. |
interface interface-type interface-number |
Specifies the type and number of the interface. |
- |
nexthop nexthop-address |
Displays the route with the specified next hop IP address. |
The value is in dotted decimal notation. |
Usage Guidelines
By using this command with different parameters, you can view the routes of a specified interface or next hop.
The command output can help you troubleshoot OSPF faults.
Example
# Display the OSPF routing table.
<Huawei> display ospf routing
OSPF Process 1 with Router ID 10.2.2.9 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.12.12.0/24 1 Transit 10.12.12.10 10.2.2.9 0.0.0.1 10.13.13.0/24 1 Stub 10.13.13.1 10.2.2.9 0.0.0.0 10.11.11.0/24 2 Transit 10.12.12.11 10.0.0.1 0.0.0.1 Routing for ASEs Destination Cost Type Tag NextHop AdvRouter 10.0.0.0/8 1 Type2 1 10.12.12.11 10.0.0.1 Total Nets: 4 Intra Area: 3 Inter Area: 0 ASE: 1 NSSA: 0
Item |
Description |
---|---|
Destination |
Destination network |
Cost |
Cost of the route to the destination address |
Type |
Type of the destination network:
|
NextHop |
Next hop address to the destination address |
AdvRouter |
Device that advertises LSAs |
Area |
Area ID |
Tag |
Tag of the external route |
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 (that is, stub networks and transit networks) |
Inter Area |
Total number of inter-area networks |
ASE |
Total number of networks in the ASE area |
NSSA |
Total number of networks in the NSSA |
display ospf sham-link
Function
The display ospf sham-link command displays the sham links of the OSPF area.
If no OSPF process ID or area ID is specified, all sham links are displayed.
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
area area-id |
Specifies the ID of an OSPF area. |
The value is an integer ranging from 0 to 4294967295 or in the IPv4 address format. |
Usage Guidelines
To display the sham links of the OSPF area, run display ospf sham-link command. If no OSPF process ID or area ID is specified, all sham links are displayed.
Example
# Display all OSPF sham links.
<Huawei> display ospf sham-link
OSPF Process 100 with Router ID 10.1.1.2 Sham Link: Area NeighborId Source-IP Destination-IP State Cost 0.0.0.1 10.1.1.2 10.3.3.3 10.5.5.5 P-2-P 10
# Display the OSPF sham link of Area 1.
<Huawei> display ospf sham-link area 1
OSPF Process 100 with Router ID 10.1.1.2 Sham-Link: 10.3.3.3 --> 10.5.5.5 Neighbor ID: 10.1.1.2, State: Full Area: 0.0.0.1 Cost: 10 State: P-2-P, Type: Sham Timers: Hello 10 , Dead 40 , Retransmit 5 , Transmit Delay 1
Item |
Description |
---|---|
Area |
OSPF area that the sham link belongs to |
NeighborId |
Neighbor ID of the router |
Source-IP |
Source IP address of the sham link |
Destination-IP |
Destination IP address of the sham link |
State |
Interface status of the sham link (P-2-P indicates the point-to-point link.) |
Cost |
Cost of the sham link |
Type |
Connection type |
Timers |
Information about the following items: the interval for sending Hello messages, Dead time, retransmission interval, and transmission delay on the interface |
display ospf spf-statistics
Function
The display ospf spf-statistics command displays route calculation statistics in OSPF processes.
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. If no OSPF process ID is specified, brief information about route calculation statistics in all processes is displayed. |
The value is an integer ranging from 1 to 65535. |
verbose |
Displays detailed information about route calculation statistics. |
- |
Usage Guidelines
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
# Display brief information about route calculation statistics in OSPF process 1.
<Huawei> display ospf 1 spf-statistics
OSPF Process 1 with Router ID 10.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
Item |
Description |
---|---|
Date |
Date when route calculation occurs |
Time |
Time when route calculation occurs |
Intra |
Number of intra-area routes in the routing table, which are changed because of route calculation |
Inter |
Number of inter-area routes in the routing table, which are changed because of route calculation |
External |
Number of external routes in the routing table, which are changed because of route calculation |
Reason |
Cause of route calculation:
|
# Display detailed information about route calculation statistics in OSPF process 1.
<Huawei> display ospf 1 spf-statistics verbose
OSPF Process 1 with Router ID 10.10.10.2 Routing table change statistics: Index: 1 Time : 2008-11-29,17:36:59 Intra : 0 Added,0 Deleted, 0 Modified Inter : 0 Added,0 Deleted, 0 Modified External : 10 Added,0 Deleted, 0 Modified The reason of calculation is:LSA NO. Type LS ID Adv Router 1 External 10.1.5.0 10.10.10.1 2 External 10.1.3.0 10.10.10.1 3 External 10.1.9.0 10.10.10.1 4 External 10.1.4.0 10.10.10.1 5 External 10.1.2.0 10.10.10.1 6 External 10.1.8.0 10.10.10.1 7 External 10.1.7.0 10.10.10.1 8 External 10.1.6.0 10.10.10.1 9 External 10.1.10.0 10.10.10.1 10 External 10.1.1.0 10.10.10.1
Item |
Description |
---|---|
Time |
Date and time when route calculation occurs |
Intra |
Number of intra-area routes in the routing table, which are added, modified and deleted because of route calculation. |
Inter |
Number of inter-area routes in the routing table, which are added, modified and deleted because of route calculation. |
External |
Number of external routes in the routing table, which are added, modified and deleted because of route calculation. |
The reason of calculation is |
Cause of route calculation:
|
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 router that generates the LSA that causes route calculation |
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 advertising-router-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 the route calculation statistics in all processes. |
The value is an integer ranging from 1 to 65535. |
originate-router |
Specifies the link status of the advertising router. |
- |
advertising-router-id |
Specifies the ID of the advertising router. |
In dotted decimal notation |
history |
Specifies the update history of LSAs that the LSDB receives. |
- |
Usage Guidelines
Usage Scenario
The display ospf statistics updated-lsa command is used to display the frequent updates of LSAs, facilitating the location of the cause for a routing flapping.
- 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 update history of LSAs within the last 24 hours.
Precautions
- If you run the reset ospf process command to restart the OSPF process, the real-time and historical statistics on the process will be 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 will not be displayed except those with the age of 3600.
Example
# Display the LSA updates within the last one hour.
<Huawei> display ospf statistics updated-lsa
OSPF Process 1 with Router ID 10.1.1.1 Statistics of Received LSAs Begin time: 11:37:32/2011/04/25 AdvRouter Total Updated at 10.1.1.1 18 11:37:40/2011/04/25 10.2.2.2 5 11:37:40/2011/04/25 10.3.3.3 5 11:37:41/2011/04/25 10.4.4.4 5 11:37:41/2011/04/25 10.5.5.5 2 11:37:40/2011/04/25 10.6.6.6 3 11:37:40/2011/04/25 10.7.7.7 5 11:37:40/2011/04/25 10.8.8.8 6 11:37:41/2011/04/25
Item |
Description |
---|---|
Begin time |
Start time of collecting statistics |
AdvRouter |
Advertising router |
Total |
Total update times of LSAs |
Updated at |
Latest update time |
# Display the LSA updates of the specified advertising router.
<Huawei> display ospf statistics updated-lsa originate-router 10.1.1.1
OSPF Process 1 with Router ID 10.2.2.2 Statistics of Received LSAs Begin time: 2011-04-25 11:37:32 AdvRouter : 10.1.1.1 Total : 6 Updated at : 2011-04-25 11:37:41 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
Item |
Description |
---|---|
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 Type7 LSAs |
Opaque-link(9) |
Update times of Type9 LSAs |
Opaque-area(10) |
Update times of Type10 LSAs |
Opaque-AS(11) |
Update times of Type11 LSAs |
# Display the update history of LSAs.
<Huawei> display ospf statistics updated-lsa history
OSPF Process 1 with Router ID 10.1.1.1 History Information for Received LSAs Record 1: Begin time: 2011-04-25 11:39:32 End time : 2011-04-25 11:41:32 no Record Record 2: Begin time: 2011-04-25 11:37:32 End time : 2011-04-25 11:39:32 AdvRouter : 10.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 : 10.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 : 10.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 : 10.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
Item |
Description |
---|---|
Record |
Record number |
End time |
End time of collecting statistics |
display ospf vlink
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. |
Example
# Display OSPF virtual links.
<Huawei> display ospf vlink
OSPF Process 1 with Router ID 10.1.1.1
Virtual Links
Virtual-link Neighbor-id -> 10.2.2.2, Neighbor-State: Full
Interface: 10.1.1.1 (GigabitEthernet1/0/0)
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
Item |
Description |
---|---|
Virtual-link Neighbor-id |
ID of the neighboring router that is connected through the virtual link |
Neighbor-State |
Neighbor status, such as Down, Init, 2-Way, ExStart, Exchange, Loading, and Full |
Interface |
Information about interfaces in the area, that is, IP address and name of the primary interface (If the interface is a serial interface, Unknown is displayed.) |
Cost |
Cost |
State |
Interface status |
Type |
Interface type |
Transit Area |
Transit area ID if the current interface is a virtual link |
Timers |
Information about the following items: the interval for sending Hello messages, Dead time, retransmission interval, and transmission delay on the interface |
GR State |
GR status:
|
display snmp-agent trap feature-name ospf all
Function
The display snmp-agent trap feature-name ospf all command displays all trap messages of the OSPF module.
Usage Guidelines
To display all trap messages of the OSPF module, run display snmp-agent trap feature-name ospf all command.
Example
# Display all trap messages of the OSPF module.
<Huawei> display snmp-agent trap feature-name ospf all
------------------------------------------------------------------------------ Feature name: OSPF Trap number : 24 ------------------------------------------------------------------------------ Trap name Default switch status Current switch status ospfIfStateChange off off ospfVirtIfStateChange off off ospfNbrStateChange off off ospfVirtNbrStateChange off off ospfIfAuthFailure off off ospfVirtIfAuthFailure off off ospfIfRxBadPacket off off ospfVirtIfRxBadPacket off off ospfLsdbOverflow off off ospfLsdbApproachingOverflow off off ospfRestartStatusChange off off ospfNbrRestartHelperStatusChange off off ospfVirtNbrRestartHelperStatusChange off off ospfNssaTranslatorStatusChange off off ospfIfConfigError off off ospfVirtIfConfigError off off ospfTxRetransmit off off ospfVirtIfTxRetransmit off off ospfOriginateLsa off off ospfMaxAgeLsa off off hwOspfv2IntraAreaRouteridConflict on on hwOspfv2IntraAreaDRIpAddressConflict on on hwOspfv2IntraAreaRouterIdConflictRecovered on on hwOspfv2PeerFlappingSuppressStatusChange off off
Item |
Description |
---|---|
Feature name |
Name of the feature |
Trap number |
Number of traps |
Trap name |
Name of the trap:
|
Default switch status |
Status of the default trap switch:
|
Current switch status |
Status of the current trap switch:
|
dn-bit-set
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.
By default, OSPF is enabled to set the DN bit in LSAs.
Parameters
Parameter | Description | Value |
---|---|---|
summary |
Specifies that the DN bit is not set in summary LSAs. |
- |
ase |
Specifies that the DN bit is not set in ASE LSAs. |
- |
nssa |
Specifies that the DN bit is not set in NSSA LSAs. |
- |
Usage Guidelines
Usage Scenario
The dn-bit-set disable command can be used in the following scenarios:
- In the VPN option A scenario, the local PE imports BGP routes to generate LSAs and advertise the generated LSAs to the peer PE. Setting of the DN bit is restricted. The peer PE may fail to calculate a route. In this situation, the dn-bit-set disable command can be used to set the DN bit on or remove the setting of the DN bit from the local PE.
- When a PE is connected to an MCE, the MCE needs to calculate routes advertised by the PE. By default, the MCE does not check the DN bit. In this situation, the dn-bit-set disable command can be used to set the DN bit on or remove the setting of the DN bit from the local PE.
To prevent routing loops, the OSPF multi-instance process uses a bit as a flag. The bit is called DN bit.
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 converted from type 7 LSAs even if the DN bit is set in type 7 LSAs.
Precautions
The dn-bit-set disable command can be configured for only private OSPF processes. The configuration of this command takes effect only on the PEs.
The dn-bit-check disable command can be used to control whether OSPF running on the peer PE checks the DN bit when calculating routes.
Example
# Disable OSPF from setting the DN bit in ASE LSAs.
<Huawei> system-view
[Huawei] ip vpn-instance huawei
[Huawei-vpn-instance-huawei] route-distinguisher 100:1
[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
dn-bit-check
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.
By default, OSPF is enabled to check the DN bit in LSAs.
Format
dn-bit-check disable { summary [ router-id router-id ] | ase | nssa }
undo dn-bit-check disable { summary [ router-id router-id ] | ase | nssa }
Parameters
Parameter | Description | Value |
---|---|---|
summary |
Specifies that the DN bit in summary LSAs is not checked. |
- |
router-id router-id |
Specifies the ID of a device on which the DN bit in summary LSAs is checked. |
- |
ase |
Specifies that the DN bit in ASE LSAs is not checked. |
- |
nssa |
Specifies that the DN bit in NSSA LSAs is not checked. |
- |
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. 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.
Configuration Impact
When 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.
Precautions
When a PE is connected to an MCE, the MCE does not check the DN bit by default.
The dn-bit-check disable command can be configured only for private OSPF processes. The configuration of this command takes effect only on the PEs.
In this scenario, you can run the dn-bit-set disable command to set the DN bit on or remove the setting of the DN bit from 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] route-distinguisher 100:1
[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 10.1.1.1
domain-id (OSPF)
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-id [ type type value value | secondary ] * }
undo domain-id [ domain-id [ type type value value ] ]
Parameters
Parameter | Description | Value |
---|---|---|
domain-id |
Specifies the ID of an OSPF domain. |
The domain ID can be an integer or in dotted decimal notation.
|
null |
Indicates that the OSPF domain ID is null. |
- |
type type |
Specifies the type of the OSPF domain ID. |
The value can be 0005, 0105, 0205, or 8005. The default value is 0005. |
value value |
Specifies the value of the type of the OSPF domain ID. |
The value is a hexadecimal number that ranges from 0x0 to 0xffff, and the default value is 0x0. |
secondary |
Indicates the ID of a secondary domain. |
The maximum number of domain-id secondary in each OSPF process is 1000. |
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.
If the undo domain-id command without any parameter is executed, the primary domain ID will be deleted.
OSPF direct routes to the PE do not carry the domain ID, while BGP direct routes to the PE carry the domain ID.
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 is forbidden in public network.
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.
Usage Guidelines
Usage Scenario
The eca-route-type compatible command is used in OSPF VPN scenarios.
- For the router supporting RFC 4577, you can set the route type of the extended community attribute of OSPF VPN to 0x0306 and configure the router to identify both 0x0306 and 0x8000 route types.
- For the router that does not support RFC 4577, you can set the route type of the extended community attribute of OSPF VPN to 0x8000 and configure the router to identify only the 0x8000 route type.
By running the eca-route-type compatible command enables different routers 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 is forbidden in 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] route-distinguisher 100:1
[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
enable log
Function
The enable log command enables log.
The undo enable log command disables log.
By default, log is disabled.
Format
enable log [ config | error | state | snmp-trap ]
undo enable log [ config | error | state | snmp-trap ]
Parameters
Parameter | Description | Value |
---|---|---|
config | Enables the configuration log. | - |
state | Enables the state log. | - |
error | Enables the error log. | - |
snmp-trap | Enables the SNMP trap log. | - |
Usage Guidelines
Usage Scenario
Running the enable log command can enable the logging function. You can view running status of devices based on logs, facilitating device maintenance.
If the undo enable log command is executed, the logging function will be disabled. Then, running status of devices will be not displayed. This is inconvenient for network maintenance.
Precautions
Configuring different parameters in the enable log command can display different log information. If no parameter is not specified, the command output displays all log information.
filter export (OSPF Area)
Function
The filter export command filters the outgoing Type3 LSAs of the local area.
The undo filter export command restores the default setting.
By default, the outgoing Type3 LSAs of the local area cannot be filtered.
Format
filter { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export
undo filter [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export
Parameters
Parameter | Description | Value |
---|---|---|
acl-number |
Specifies the number of a basic ACL. |
The value is an integer ranging from 2000 to 2999. |
acl-name acl-name |
Specifies the name of a named ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
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, 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 name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
The command can be used to filter out invalid LSAs sent to neighbors to reduce the size of the LSDB and speed up network convergence.
Configuration Impact
After filtering conditions are set for the outgoing summary LSAs to be advertised using the filter export command, only the outgoing Type3 LSAs that pass the filtering can be advertised.
Precautions
- The command can be configured only on an ABR.
- For a named ACL configured using the acl name command, when the rule command is used to configure a filtering rule, the filtering rule takes effective only when the source address range is specified by the source parameter and the time period is specified by the time-range parameter.
- Run the filter import command to set filtering conditions for the incoming Type3 LSAs to be advertised.
filter import (OSPF Area)
Function
The filter import command filters the incoming Type3 LSAs of the local area.
The undo filter import command restores the default setting.
By default, the incoming Type3 LSAs cannot be filtered.
Format
filter { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } import
undo filter [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] import
Parameters
Parameter | Description | Value |
---|---|---|
acl-number |
Specifies the number of a basic ACL. |
The value is an integer ranging from 2000 to 2999. |
acl-name acl-name |
Specifies the name of an ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
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, 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 route-policy. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
After filtering conditions are set for the incoming summary LSAs to be advertised using the filter import command, only the incoming Type3 LSAs that pass the filtering can be received.
Configuration Impact
The command can be used to filter out invalid LSAs sent to neighbors to reduce the size of the LSDB and speed up network convergence.
Precautions
- The command can be configured only on an ABR.
- For a named ACL, when the rule command is used to configure a filtering rule, the filtering rule takes effective only when the source address range is specified by the source parameter and the time period is specified by the time-range parameter.
- Run the filter export command to set filtering conditions for the outgoing Type3 LSAs to be advertised.
filter-lsa-out peer
Function
The filter-lsa-out peer command configures a router to filter the LSAs that are sent by the specified neighbors on a P2MP network.
The undo filter-lsa-out peer command cancels the configuration.
By default, the LSAs that are sent by the specified neighbor on a P2MP network are not filtered.
Format
filter-lsa-out peer ip-address { all | { summary [ acl { acl-number | acl-name } ] | ase [ acl { acl-number | acl-name } ] | nssa [ acl { acl-number | acl-name } ] } * }
undo filter-lsa-out peer ip-address
Parameters
Parameter | Description | Value |
---|---|---|
ip-address | Specifies the IP address of a P2MP neighbor. This parameter is configured by the neighbor using the ip address command. |
The value is in dotted decimal notation. |
all | Filters all the outgoing LSAs except Grace LSAs. | - |
summary | Filters the outgoing network summary LSAs (Type 3). | - |
acl acl-number | Specifies the number of a basic ACL. | The value is an integer that ranges from 2000 to 2999. |
acl acl-name | Specifies the name of a named ACL. | The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
ase | Filters the outgoing AS external LSAs (Type 5). | - |
nssa | Filters the outgoing NSSA LSAs (Type 7). | - |
Usage Guidelines
Usage Scenario
On a P2MP network, when multiple P2MP links exist between two devices, you can configure the local device to filter the outgoing LSAs on the specified link. This can reduce unnecessary LSA retransmission attempts and save bandwidth resources.
For a named ACL, when the rule command is used to 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
OSPF does not regard a network as a P2MP network by default regardless of any link layer protocol. A P2MP network is forcibly changed from the network of another type. The network type has been changed to the P2MP by using the ospf network-type p2mp command.
Configuration Impact
This command is valid for all the interfaces of the OSPF process.
Follow-up Procedure
Configure a device to filter the outgoing LSAs on the specified OSPF interface by using the ospf filter-lsa-out command.
filter-policy export (OSPF)
Function
The filter-policy export command filters the imported routes when these routes are advertised based on a filtering policy.
The undo filter-policy export command restores the default setting.
By default, the imported routes to be advertised cannot be filtered.
Format
filter-policy { acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name } export [ protocol [ process-id ] ]
undo filter-policy [ acl-number | acl-name acl-name | ip-prefix ip-prefix-name | route-policy route-policy-name ] export [ protocol [ process-id ] ]
Parameters
Parameter | Description | Value |
---|---|---|
acl-number |
Specifies the number of a basic ACL. |
The value is an integer that ranges from 2000 to 2999. |
acl-name acl-name |
Specifies the name of a named ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
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, 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 name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
protocol process-id |
Filters imported routes of a specified protocol. The value can be direct, rip, isis, bgp, ospf, unr, or static. When the routing protocol is RIP, IS-IS, or OSPF, you can specify a process ID. |
The value is an integer that ranges from 1 to 65535. The default value is 1. |
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 pass the filtering can be converted into AS-external LSAs and advertised.
The protocol or process-id parameter can be specified to determine a specified protocol or process. If the protocol or process-id 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.
- For a named ACL, when the rule command is used to configure a filtering rule, the filtering rule takes effective only when the source address range is specified by the source parameter and the time period is specified by the time-range parameter.
filter-policy import (OSPF)
Function
The filter-policy import command configures a filtering policy to filter routes received by OSPF.
The undo filter-policy import command restores the default setting.
By default, OSPF does not filter routes.
Format
filter-policy { acl-number | 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 ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
ip-prefix ip-prefix-name |
Specifies the name of the address prefix list. |
The name 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 the route policy. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
secondary |
Specifies the secondary route. |
- |
Usage Guidelines
Usage Scenario
The filter-policy import command is used to set a filtering policy for received routes. Only the routes that pass the filtering can be added to the routing table. The routes that fail to pass the filtering cannot be added to the routing table but can be advertised.
The OSPF routing information is recorded in the LSDB. Instead of filtering the received or sent LSAs, the device filters routes calculated by OSPF using the filter-policy import command.
Precautions
For a named ACL configured using the acl command, when the rule command is used to configure a filtering rule, the filtering rule takes effective only when the source address range is specified by the source parameter and the time period is specified by the time-range parameter.
flooding-control
Function
The flooding-control command restricts the flooding of update LSAs.
The undo flooding-control command cancels the restriction on the flooding of update LSAs.
By default, this function is enabled when the number of neighbors exceeds 256.
Format
flooding-control [ number transmit-number | timer-interval transmit-interval ] *
undo flooding-control [ number | timer-interval ] *
Parameters
Parameter | Description | Value |
---|---|---|
number transmit-number | Sets the number of update LSAs to be flooded each time. | The value is an integer ranging from 1 to 1000. By default, the value is 50. |
timer-interval transmit-interval | Sets the interval for flooding update LSAs. | The value is an integer that ranges from 30 to 100000, in milliseconds. By default, the value is 30. |
Usage Guidelines
Usage Scenario
When multiple neighbors are configured or a large number of update LSAs are flooded, a router may receive a large number of update LSAs in a short period. If the router is busy processing these Update packets and discards the Hello packets that maintain neighbor relationships, neighbor relationships may be interrupted. During the reestablishment of neighbor relationships, more packets need to be exchanged, which deteriorates the processing of packets.
To avoid the preceding problem, you can run the flooding-control command to restrict the flooding of update LSAs to keep stable neighbor relationships.
Configuration Impact
After the flooding-control command is run, the flooding of update LSAs is immediately restricted.
Precautions
By default, a router spends 50 ms in flooding update LSAs each time. If not all the update LSAs are flooded within 50 ms, the router floods the remaining LSAs after the time specified by transmit-interval.
frr (OSPF)
Function
The frr command creates an OSPF FRR view and displays the OSPF FRR view.
The undo frr command enables the system to exit from an OSPF FRR view and deletes the OSPF FRR view.
By default, no OSPF FRR view is created.
AR600 series does not support this function.
Usage Guidelines
Usage Scenario
The frr command is used to enter the OSPF FRR view. OSPF FRR functions need to be configured in the OSPF FRR view.
OSPF IP FRR allows devices to fast switch traffic from faulty links to backup links without interrupting traffic. This function protects traffic and greatly improves the reliability of OSPF networks. OSPF IP FRR must be configured in the OSPF FRR view. The frr command run in the OSPF view creates and displays the OSPF FRR view.
Prerequisites
The OSPF function has been enabled using the ospf command.
Configuration Impact
The frr command is only used to enter the OSPF FRR view but not to enable FRR. To enable FRR, you need to run this command and other commands in the OSPF FRR view.
Follow-up Procedure
You can run the loop-free-alternate command to implement basic FRR functions. In this manner, the device can create the loop-free backup link.
frr-policy route (OSPF FRR)
Function
The frr-policy route command configures a filtering policy for the OSPF IP FRR backup routes. The filtering policy determines what kind of OSPF backup route can be added to the routing table.
The undo frr-policy route command cancels the filtering function.
By default, the filtering function is disabled.
AR600 series do not support this function.
Parameters
Parameter | Description | Value |
---|---|---|
route-policy route-policy-name |
Specifies the name of the policy used to filter OSPF backup routes. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
OSPF IP FRR allows devices to fast switch traffic on fault links to backup links without interrupting traffic. This protects traffic and greatly improves the reliability of OSPF networks.
After the filtering policy is configured using the frr-policy route command, only the OSPF backup route that satisfies filtering rules can be delivered to the forwarding table.
To protect the traffic over a specific OSPF route, you can configure a filtering policy route-policy-name that the OSPF route matches to ensure that the backup route can be added to the forwarding table. When this route fails, OSPF can fast switch the traffic to a backup route.
Prerequisites
Before using the frr-policy route command, the OSPF IP FRR view has been entered by using the frr command, and the function of OSPF IP FRR has been enabled by using the loop-free-alternate command.
Precautions
The frr-policy route command is cyclic in nature, and only the latest configuration takes effect.
frr-priority static low
Function
The frr-priority static low command enables dynamic backup links to take preference over static backup links so that the LFA algorithm is used to calculate the nexthop and outbound interface.
The undo frr-priority static command disables this function.
By default, this function is disabled, static backup links take preference over dynamic backup links during route selection.
AR600 series do not support this function.
Usage Guidelines
Usage Scenario
The nexthop and outbound interface of an OSPF loop-free backup link can be obtained using either of the following methods:
- For a static backup link, after IP FRR is enabled using the ip frr command in the system view or ip frr command in VPN instance view, configure a nexthop and an outbound interface for the static backup link.
- For a dynamic backup link, after OSPF IP FRR is enabled using the loop-free-alternate command, enable the device to use the LFA algorithm to calculate the nexthop and outbound interface for the dynamic backup link.
By default, static backup links take preference over dynamic backup links during route selection. However, static backup links are less flexible than dynamic backup links. If a link failure occurs, static backup links cannot update automatically, but dynamic backup links can. Therefore, to ensure automatic link updates, run the frr-priority static low command to enable dynamic backup links to take preference over static backup links so that the LFA algorithm is used to calculate the nexthop and outbound interface.
Prerequisites
The OSPF IP FRR view has been displayed using the frr command.
graceful-restart (OSPF)
Function
The graceful-restart command enables the GR function.
The undo graceful-restart command disables GR function.
By default, OSPF GR is disabled.
In practical application, in order to realize that business forwarding is not affected by motherboard failure, it is usually possible to configure OSPF GR in the hardware environment of dual motherboard to make sense.
AR600, AR6100, and AR6200 series support the GR Helper, and only AR6300 series support the GR Restarter.
Format
graceful-restart [ period period | planned-only | partial ] *
undo graceful-restart [ period | planned-only | partial ] *
Parameters
Parameter | Description | Value |
---|---|---|
period period |
Specifies the duration of GR. |
It is an integer ranging from 1s to 1800s. The default value is 120s. |
planned-only |
Indicates that the router supports only the planned GR. By default, the router supports both the planned GR and unplanned GR. |
- |
partial |
Indicates that the router partially supports the GR. By default, the router totally supports the GR. |
- |
Planned GR: indicates that a device manually restarts or performs a master/slave MPU switchover by using the command. Before the device restarts or performs a master/slave MPU switchover, Restarter will send a grace LSA.
Unplanned GR: indicates that a device restarts or performs a master/slave MPU switchover because of faults. A device directly performs a master/slave MPU switchover without sending a grace LSA, and then enters GR after the slave MPU goes Up. It is different from the planned GR.
Usage Guidelines
Usage Scenario
The graceful-restart command enables OSPF GR to avoid the route flapping due to the traffic interruption or master/slave MPU switchover. After the graceful-restart command is run to enable GR for a router, the Helper function is also enabled.
Prerequisites
Opaque LSAs provide a generic mechanism for OSPF extension:
- OSPF supports GR using Type 9 LSAs.
- OSPF supports TE using Type 10 LSAs.
Before configuring OSPF GR, you must enable opaque LSA capability running the opaque-capability enable command.
Configuration Impact
After an OSPF process is restarted using GR, the Restarter router and the Helper router reestablish the neighbor relationship, exchange routing information, synchronize the LSDB, and update the routing table and forwarding table. This implements OSPF fast convergence, prevents traffic interruption, and stabilizes the network topology.
Precautions
If there are special requirements on the GR Helper, run the graceful-restart helper-role command to configure the requirements.
graceful-restart helper-role (OSPF)
Function
The graceful-restart helper-role command configures a device as a GR helper.
The undo graceful-restart helper-role command cancels the configuration.
By default, the device does not function as a GR helper.
In practical application, in order to realize that business forwarding is not affected by motherboard failure, it is usually possible to configure OSPF GR in the hardware environment of dual motherboard to make sense.
AR600, AR6100, and AR6200 series support the GR Helper, and only AR6300 series support the GR Restarter.
Format
graceful-restart [ period period | partial | planned-only ] * helper-role { { [ ip-prefix ip-prefix-name | acl-number acl-number | acl-name acl-name ] | ignore-external-lsa | planned-only } * | never }
undo graceful-restart [ period | partial | planned-only ] * helper-role [ [ { ip-prefix | acl-number | acl-name } | ignore-external-lsa | planned-only ] * | never ]
Parameters
Parameter | Description | Value |
---|---|---|
period period |
Specifies the duration of GR. |
The value is an integer that ranges from 1 to 1800, in seconds. The default value is 120. |
planned-only |
Configures the device to support only planned GR. By default, the device supports both the planned GR and unplanned GR. |
- |
partial |
Configures the device to support partial GR. By default, the device supports totally GR. |
- |
ip-prefix ip-prefix-name |
Specifies the name of the address prefix list. The name is a string. |
The name 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. |
acl-number acl-number |
Specifies the basic ACL number. |
The value is an integer that ranges from 2000 to 2999. |
acl-name acl-name |
Specifies the name of a Named ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
ignore-external-lsa |
Indicates that the device does not check 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 device does not support the Helper mode. |
- |
Usage Guidelines
Usage Scenario
After an OSPF process is restarted through GR, only the restarter and the helper reestablish the neighbor relationship, then stabilizes the network topology.
Prerequisites
Before configuring GR of the device, you need to enable Opaque LSA by running the opaque-capability enable command.
gtsm default-action
Function
The gtsm default-action command sets the default action that is performed on the packets that do not match the GTSM policies.
The undo gtsm default-action drop command cancels the setting that the packets that do not match the GTSM policy cannot pass the filtering.
By default, the packets that do not match the GTSM policies can pass the filtering.
Parameters
Parameter | Description | Value |
---|---|---|
drop |
Indicates that the packets that do not match the GTSM policies cannot pass the filtering. The packets are dropped. |
- |
pass |
Indicates that the packets that do not match the GTSM policies can pass the filtering. |
- |
Usage Guidelines
Usage Scenario
For a network demanding high security, you can configure Generalized TTL Security Mechanism (GTSM) to improve the security of the OSPF network. GTSM defends against attacks by checking the Time-to-Live (TTL) value. If an attacker simulates real OSPF packets and keeps sending them to a router, an interface board on the router receives the packets and directly sends them to the main control board for OSPF processing, without checking the validity of the packets. In this case, the router is busy in processing these packets, causing high usage of the CPU. GTSM function protects the router by checking whether the TTL value in the IP packet header is in a pre-defined range to improve the system security.
GTSM only checks the TTL values of the packets that match the GTSM policy. The packets that do not match the GTSM policy can pass the filtering using the undo gtsm default-action drop command or using the gtsm default-action command to set the pass parameter, or be dropped after the gtsm default-action command is run to set the drop parameter.
Configuration Impact
If the default action to be taken on GTSM packets is drop, the connection cannot be established by the router. Therefore, GTSM ensures better security but reduces the ease of use.
Precautions
You can enable the log function by using the gtsm log drop-packet command to record the information about dropped packets for further fault location.
If you configure the default action by using the gtsm default-action command but not configure GTSM policy (the drop or pass parameter), GTSM does not take effect.
Example
# Set the default action performed on the packets that do not match the GTSM policies as "drop".
<Huawei> system-view
[Huawei] gtsm default-action drop
# Set the default action performed on the packets that do not match the GTSM policy as pass the filtering.
<Huawei> system-view
[Huawei] undo gtsm default-action drop
gtsm log drop-packet
Function
The gtsm log drop-packet command enables the log function on the slot. The information that GTSM drops packets is recorded in the log.
The undo gtsm log drop-packet command disables the log function on the slot.
By default, the information that GTSM drops packets is not recorded in the log.
Usage Guidelines
On the AR, the gtsm log drop-packet command can enable the log function only on the MPU, but not on LPUs.
Usage Scenario
For a network demanding higher security, you can configure Generalized TTL Security Mechanism (GTSM) to improve the security of the OSPF network. GTSM defends against attacks by checking the Time-to-Live (TTL) value. If an attacker simulates real OSPF packets and keeps sending them to a device, an interface board on the device receives the packets and directly sends them to the main control board for OSPF processing, without checking the validity of the packets. In this case, the device is busy in processing these packets, causing high usage of the CPU. GTSM function protects the device by checking whether the TTL value in the IP packet header is in a pre-defined range to improve the system security.
GTSM only checks the TTL values of the packets that match the GTSM policy. The packets that do not match the GTSM policy can be allowed or dropped by using the gtsm default-action command.
You can also enable the log function by using the gtsm log drop-packet command to record the information about dropped packets for further fault location.
Prerequisites
Run the gtsm default-action drop command to drop packets before the log function is enabled.
import-route (OSPF)
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 { limit limit-number | { bgp [ permit-ibgp ] | direct | unr | rip [ process-id-rip ] | static | isis [ process-id-isis ] | ospf [ process-id-ospf ] } [ cost cost | type type | tag tag | route-policy route-policy-name ] * }
undo import-route { limit | bgp | direct | unr | rip [ process-id-rip ] | static | isis [ process-id-isis ] | ospf [ process-id-ospf ] }
Parameters
Parameter | Description | Value |
---|---|---|
bgp |
Specifies the BGP protocol whose routes are imported. 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 |
IBGP routes that are permitted to be imported. The import of IBGP routes may cause route loops. Therefore, this command must not be configured unless it is necessary. 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. |
- |
direct |
Specifies the direct protocol whose routes are imported. |
- |
unr |
Specifies the imported source routing protocol as unr. User Network Route (UNR) is allocated if dynamic routing protocols cannot be used when users are getting online. |
- |
rip |
Specifies the imported source routing protocol as rip. |
- |
process-id-rip |
Specifies the process ID of the imported RIP routing protocol. |
The value is an integer ranging from 1 to 65535. The default value is 1. |
static |
Specifies the imported source routing protocol as static. NOTE:
The parameter can only active static routes are imported. |
- |
isis |
Specifies the imported source routing protocol as isis. |
- |
process-id-isis |
Specifies the process ID of the imported IS-IS routing protocol. |
The value is an integer ranging from 1 to 65535. The default value is 1. |
ospf |
Specifies the imported source routing protocol as ospf. |
- |
process-id-ospf |
Specifies the process ID of the imported OSPF routing protocol. |
The value is an integer ranging from 1 to 65535. The default value is 1. |
limit limit-number |
The maximum number of external routes that can be imported into an OSPF process. |
The value is an integer that ranges from 1 to 4294967295. |
cost cost |
Indicates the route cost. |
The value is an integer ranging from 0 to 16777214. The default value see the command default(OSPF). |
route-policy route-policy-name |
Imports only the route that meets the requirements of the specified route-policy. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
tag tag |
Specifies the tag of the external LSA. |
The value is an integer ranging from 0 to 4294967295. The default value see the command default(OSPF). |
type type |
Specifies the type of the external routes. |
The value is an integer ranging from 1 to 2. The default value see the command default(OSPF).
|
Usage Guidelines
Usage Scenario
Importing the routes discovered by other routing protocols can enrich OSPF routing information.
When OSPF imports external routes, you can set default values for some additional parameters using the import-route command, such as metric, route tag, and route type. A route tag is used to identify protocol-related information. For example, it can be used to differentiate AS numbers carried in BGP routes imported by OSPF.
By default, the cost of the external routes imported by OSPF is 1; the type of the imported external routes is Type 2; the default tag value of the imported routes is 1.
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 autonomous system.
Inter-area routes: refer to the routes between different 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 equals 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.
On a non-PE device, 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 preferences 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 preference of OSPF ASE routes lower than that of IBGP routes (preference value of OSPF ASE routes larger than that of IBGP routes).
On a PE, 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 or not. If the import-route bgp permit-ibgp command and the default-route-advertise (OSPF) command are both configured, the active IBGP default routes can be imported into OSPF.
Prerequisites
You must create a route-policy by running the route-policy command before running the import-route command to import certain external routes by the route-policy.
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
After a route-policy is configured, the OSPF process imports only routes of a network segment that satisfy certain conditions. This prevents devices from receiving routes not required.
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 device to advertise the default route of an external protocol it learns when updating the OSPF routing table to other devices within the area, run the default-route-advertise (OSPF) command.
After the import-route direct command is executed, routes to the network segment where the IP address of the management interface belongs are also imported in the OSPF routing table. Therefore, use this command with caution.
local-mt filter-policy (OSPF)
Function
The local-mt filter-policy command configures the filtering policy of OSPF Local Multicast-Topology (MT).
The undo local-mt filter-policy command deletes the filtering policy of OSPF local MT.
By default, the filtering policy of OSPF local MT is not configured.
Format
local-mt filter-policy { acl { acl-number | acl-name } | ip-prefix ip-prefix-name | route-policy route-policy-name }
undo local-mt filter-policy
Parameters
Parameter | Description | Value |
---|---|---|
acl acl-number |
Specifies the number of the basic access control list (ACL). |
The value is an integer ranging from 2000 to 2999. |
acl acl-name |
Specifies the name of a Named ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
ip-prefix ip-prefix-name |
Specifies the name of the IP prefix list. |
The name 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 the route policy. |
The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
When multicast and an MPLS TE tunnel are configured on a network and the TE tunnel is configured with IGP Shortcut, the outbound interface of the route calculated by an IGP is not an actual physical interface but a TE tunnel interface. The device uses a unicast route to the multicast source address to send multicast Join messages from the TE tunnel interface. The device through which the TE tunnel passes, however, cannot sense the multicast Join messages. As a result, multicast forwarding entries will not be created.
To avoid the preceding problem, you can create a proper multicast routing table to guide the forwarding of multicast packets by configuring local MT. After OSPF local MT is enabled, if the outbound interface of the calculated route is a TE tunnel interface of the IGP Shortcut type, the route management (RM) module creates a separate MIGP routing table for the multicast protocol, calculates the actual physical outbound interface for the route, and adds the physical interface to the MIGP routing table for multicast forwarding.
To control the number of entries in the MIGP routing table and speed up the MIGP routing table search, you can configure filtering conditions by using the local-mt filter-policy command to allow only the matching routes to the multicast source address to be added to the MIGP routing table.
Prerequisites
OSPF local MT has been enabled using the local-mt enable command.
Precautions
You are recommended to configure the routing policy before enabling local MT. This can prevent the excessive routes to the not-multicast source address from being added to the MIGP routing table and keeps the number of routes in the MIGP routing table within the upper limit.
When the rule(basic ACL6 view) or rule (basic ACL view) command is used to configure filtering rules for a named ACL configured using the acl command, 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.
local-mt enable (OSPF)
Function
The local-mt enable command enables OSPF Local Multicast-Topology (MT).
The undo local-mt enable command disables OSPF local MT.
By default, OSPF local MT is disabled.
Usage Guidelines
Usage Scenario
When multicast and an MPLS TE tunnel are configured on a network and the TE tunnel is configured with IGP Shortcut, the outbound interface of the route calculated by an IGP is not an actual physical interface but a TE tunnel interface. The device uses a unicast route to the multicast source address to send multicast Join messages from the TE tunnel interface. The device spanned by the TE tunnel, however, cannot sense the multicast Join messages. As a result, multicast forwarding entries will not be created on these devices.
To avoid the preceding problem, you can run the local-mt enable command to enable OSPF local Multicast-Topology (MT). MT allows the multicast routing entries to be correct created to guide the forwarding of multicast traffic.
After OSPF local MT is enabled, if the outbound interface of the calculated route is a TE tunnel interface of the IGP Shortcut type, the route management (RM) module creates a separate MIGP routing table for the multicast protocol, calculates the actual physical outbound interface for the route, and adds the physical interface to the MIGP routing table for multicast forwarding.
Prerequisites
IGP Shortcut feature has been enabled using the enable traffic-adjustment command.
Precautions
- To control the number of entries in the MIGP routing table and speed up the MIGP routing table search, you can run the local-mt filter-policy command to configure a policy for filtering multicast source address. Then only the multicast source address that matches the policy to be added to the MIGP routing table. Configure the routing policy before enabling local MT. This can prevent excessive routes to non-multicast source address from being added to the MIGP routing table and keeps the number of routes in the MIGP routing table within the upper limit.
- Local MT is applicable only to the OSPF process of a public network instance.
- OSPF local MT does not support forwarding adjacency (FA).
loop-free-alternate (OSPF FRR)
Function
The loop-free-alternate command enables OSPF IP FRR enable the device to use the LFA algorithm to calculate the nexthop and outbound interface for the dynamic backup link.
The undo loop-free-alternate command disables OSPF IP FRR.
By default, OSPF IP FRR is disabled.
AR600 series does not support this function.
Usage Guidelines
Usage Scenario
The Loop Free Alternate (LFA) is a method of implementing FRR. Through LFA, a device can generate a loop-free backup link and FRR can be implemented.
OSPF IP FRR takes effect only after the loop-free-alternate command is run.
Prerequisites
before configuring the command, you can create an OSPF IP FRR view and enter the OSPF IP FRR view by running the frr command.
Precautions
If you do not want the link that transmits important service traffic to function as the backup link of other links, you need to configure the ospf frr block command on the interface connecting to the link before configuring the OSPF IP FRR function. In this manner, the link will not be designated as the backup link during FRR calculation.
lsa-arrival-interval
Function
The lsa-arrival-interval command sets the interval for receiving LSAs.
The undo lsa-arrival-interval command restores the default interval for receiving LSAs.
By default, an intelligent timer is enabled. The interval for receiving LSAs is expressed in milliseconds. The maximum interval for updating LSAs is 1000 milliseconds (ms), the initial interval is 500 ms, and the Holdtime interval is 500 ms.
Format
lsa-arrival-interval { interval | intelligent-timer max-interval start-interval hold-interval }
undo lsa-arrival-interval
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies the interval for receiving LSAs. |
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 for receiving LSAs. |
The value is an integer ranging from 1 to 120000, in ms. The default value is 1000. |
start-interval |
Specifies the initial interval for receiving LSAs. |
The value is an integer ranging from 0 to 60000, in ms. The default value is 500. |
hold-interval |
Specifies the Holdtime interval for receiving LSAs. |
The value is an integer ranging from 1 to 60000, in ms. The default value is 500. |
Usage Guidelines
Usage Scenario
OSPF defines that the interval for receiving LSAs is 1s. This prevents network connections or frequent route flapping from consuming excessive network bandwidth or device resources.
On a stable network where routes need to be fast converged, you can change the interval for receiving LSAs to 0s. In this manner, the change of the topology or route can be immediately sensed, which speeds up route convergence.
If there is no special network requirement, default values are recommended.
Procedure
- The initial interval for receiving LSAs is specified by 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×2(n-2) reaches the maximum interval specified by max-interval, OSPF performs SPF calculation at the maximum interval until max-interval expires without flapping or the OSPF process is restarted.
Precautions
You are advised to set the receiving interval specified by lsa-arrival-interval to be a value smaller than or equal to the Holdtime interval specified bylsa-originate-interval.
lsa-originate-interval
Function
The lsa-originate-interval command sets the interval for updating LSAs.
The undo lsa-originate-interval command restores the default interval for updating LSAs.
By default, the intelligent timer is enabled; the maximum interval for updating LSAs is 5000 ms, the initial interval is 500 ms, and the Holdtime interval is 1000 ms.
Format
lsa-originate-interval { 0 | { intelligent-timer max-interval start-interval hold-interval | other-type interval } * }
lsa-originate-interval other-type interval [ intelligent-timer max-interval start-interval hold-interval ]
undo lsa-originate-interval
Parameters
Parameter | Description | Value |
---|---|---|
0 |
Sets the interval for updating LSAs to 0 ms, that is, deletes the initial interval (5000 ms) for updating LSAs. |
- |
intelligent-timer |
Enables an intelligent timer to update OSPF router LSAs and network LSAs. |
- |
max-interval |
Specifies the maximum interval for updating OSPF LSAs. |
The value is an integer ranging from 1 to 120000, in ms. The default value is 5000. |
start-interval |
Specifies the initial interval for updating OSPF LSAs. |
The value is an integer that ranges from 0 to 60000, in ms. The default value is 500. |
hold-interval |
Specifies the Holdtime interval for updating OSPF LSAs. |
The value is an integer ranging from 1 to 60000, in ms. The default value is 1000. |
other-type |
Sets the interval for updating the LSAs other than the OSPF router LSAs and network LSAs. |
- |
interval |
Specifies the interval for updating LSAs. |
The value is an integer ranging from 0 to 10, in seconds. The default value is 5. |
Usage Guidelines
Usage Scenario
OSPF sets the interval for updating LSAs to 5s. This prevents network connections or frequent route flapping from consuming excessive network bandwidth or device resources.
On a stable network where routes need to be fast converged, you can change the interval for updating LSAs to 0s. In this manner, the change of the topology or route can be immediately advertised on the network through LSAs, which speeds up route convergence.
If there is no special network requirement, default values are recommended.
To configure the maximum LSA suppression period, run the lsa-originate-interval suppress-flapping command. If frequent LSA flapping occurs, the larger value between lsa-originate-interval suppress-flapping and lsa-originate-interval is used to suppress LSA flapping.
Execution Process
After an intelligent timer is enabled, the interval for updating LSAs is as follows:
- The initial interval for updating LSAs is specified by start-interval.
- The interval for updating LSAs for the nth (n≥2) time is equal to hold-interval x 2(n-2).
- When the interval specified by hold-interval×2(n-2) reaches the maximum interval specified by max-interval, OSPF performs SPF calculation at the maximum interval until max-interval expires without flapping or the OSPF process is restarted.
Precautions
You are advised to set the receiving interval specified by lsa-originate-interval to be a value longer than or equal to the Holdtime interval specified by lsa-arrival-interval.
lsdb-overflow-limit
Function
The lsdb-overflow-limit command sets the maximum number of external LSAs in OSPF LSDB.
The undo lsdb-overflow-limit command removes the maximum number of external LSAs.
By default, the maximum number of external LSAs is not set.
Parameters
Parameter | Description | Value |
---|---|---|
number | Specifies the maximum number of external LSAs in LSDB. | The value is an integer ranging from 1 to 1000000. |
Usage Guidelines
Usage Scenario
When the number of external LSAs (Type 5 and Type 7 LSAs) imported by OSPF exceeds the limit, the excessive external LSAs cannot be processed properly and are discarded.
To avoid the preceding problem, you can set the maximum number of external LSAs in the LSDB to adjust and optimize OSPF networks.
Prerequisites
Running the display ospf lsdb brief command, you can see OSPF is in LSDB overflow status in the command output. Then, run the lsdb-overflow-limit command to set the maximum number of external LSAs imported by OSPF.
Precautions
The configuration of this command must be consistent in the entire AS.
maximum load-balancing (OSPF)
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.
- The AR6140H-S supports a maximum of 16 equal-cost routes.
- The AR651K, AR651, AR651W-8P, AR651W, AR657W, AR651-X8, AR651U-A4, AR651W-X4, AR6140K-9G-2AC, and AR6121K support a maximum of 8 equal-cost routes.
- The AR6140E-9G-2AC, AR6140-9G-2AC, AR6120-VW, AR6120, AR6121E, AR6121, AR6120-S, AR6140E-S, AR6140-S, AR6121-S, AR6121E-S, AR6121EC-S, and AR6121C-S support a maximum of 8 equal-cost routes.
- The AR-10 supports a maximum of 8 equal-cost routes.
- The AR651C, AR651F-Lite, AR611, AR611-S, AR611W-S, AR611W, AR611W-LTE4CN, AR617VW, AR617VW-LTE4, AR617VW-LTE4EA support a maximum of 4 equal-cost routes.
- The AR6140-16G4XG supports a maximum of 16 equal-cost routes.
- The devices equipped with the SRU-100H, SRU-200H, SRU-400HK, SRU-600HK, SRU-400H, and SRU-600H support a maximum of sixteen equal-cost routes.
- The devices equipped with the SRU-100HH support a maximum of 16 equal-cost routes.
Parameters
Parameter | Description | Value |
---|---|---|
number |
Specifies the maximum number of equal-cost routes. |
The value is an integer, the ranges as below:
|
Usage Guidelines
Usage Scenario
If a routing protocol discovers multiple routes with the same cost to a single destination, they can carry out load balancing. The maximum load-balancing command sets the maximum number of equal-cost routes that can carry out load balancing. This optimizes the routing policy and ensures traffic forwarding on a complex network.
Configuration Impact
Packets will be load-balanced by multiple equal-cost routes to a single destination.
Follow-up Procedure
If more existing equal-cost OSPF routes than the value set using the maximum load-balancing command are available, valid routes are selected for load balancing based on the following criteria:
- Route preference: Routes with lower preferences are selected for load balancing.
- Interface index: If routes have the same priorities, routes with higher interface index values are selected for load balancing.
- Next hop IP address: If routes have the same priorities and interface index values, routes with larger IP address are selected for load balancing.
If equal-cost routes need to be specified for load balancing, the nexthop ip-address weight value command allows routes with a specified weight to carry out load balancing.
Precautions
To disable load balancing, set the value of number to 1.
Example
# Set the maximum number of the equal-cost routes.
<Huawei> system-view
[Huawei] ospf 100
[Huawei-ospf-100] maximum load-balancing 2
# Restore the default maximum number of equal-cost routes for carrying out load balancing.
<Huawei> system-view
[Huawei] ospf 100
[Huawei-ospf-100] undo maximum load-balancing
maximum-routes
Function
The maximum-routes command sets the maximum number of routes of different types that OSPF supports.
The undo maximum-routes command restores the default maximum number of routes of different types that OSPF supports.
By default, OSPF supports a maximum number of 5000000 external routes, 1000000 inter-area routes, and 100000 intra-area routes.
Format
maximum-routes { external | inter | intra } number
undo maximum-routes { external | inter | intra }
Parameters
Parameter | Description | Value |
---|---|---|
external |
Indicates the maximum number of AS external routes that OSPF supports. |
- |
inter |
Indicates the maximum number of inter-area routes that OSPF supports. |
- |
intra |
Indicates the maximum number of intra-area routes that OSPF supports. |
- |
number |
Specifies the maximum number of routes of different types. |
The value is an integer.
|
Usage Guidelines
Usage Scenario
Based on the real world situation of a network such as the convergence speed, the maximum-routes command configures the maximum number of routes of different types to make full use of network resources and improve network performance.
Precautions
The maximum number of routes supported by OSPF cannot exceed the maximum number of all routes supported by the router.
The maximum-routes command configuration limits the maximum number of routes that can be locally calculated. Therefore, the command configuration affects the maximum number of routes that can be sent, but does not affect the maximum number of LSAs that can be received.
mesh-group enable
Function
The mesh-group enable command enables the mesh-group function.
The undo mesh-group enable command disables the mesh-group function.
By default, the mesh-group function is disabled.
Usage Guidelines
Usage Scenario
When concurrent links exist between the device and its neighbor, the mesh-group enable command enables the mesh-group function. The router ID of a neighboring device uniquely identifies a mesh group. After LSAs are received, the device selects a primary link to flood the received LSAs, without performing reverse flooding. This prevents repeated flooding, reduce the load on the links, and save system resources.
device interfaces that meet the following conditions can form a mesh group:
- The interfaces belong to the same area and OSPF process.
- The neighbor status is Exchange or Full.
- Each interface is connected only to one neighbor.
Precautions
After the device is enabled with the mesh-group function, if the router IDs of the directly connected neighbor are the same, the LSDBs of the entire network cannot be synchronized and routes cannot be calculated correctly. In this case, you need to reconfigure the router ID of the neighbor, and then restart the neighbor to validate the configured router ID.
network (OSPF Area)
Function
The network command specifies the interface that runs OSPF and the area to which the interface belongs.
The undo network command deletes the interface that runs OSPF.
By default, an interface does not belong to any area.
Format
network network-address wildcard-mask [ description text ]
undo network network-address wildcard-mask
Parameters
Parameter | Description | Value |
---|---|---|
network-address |
Specifies the address of the network segment where the 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 the mask of the IP address. For example, 0.0.0.255 indicates that the mask length is 24 bits. |
The value is in dotted decimal notation. |
description text |
Specifies the description of the specified OSPF network segment. |
The value is a string of 1 to 80 case-sensitive characters with spaces allowed. |
Usage Guidelines
Usage Scenario
After creating an OSPF process, you can run the network command to configure the network segments in an area and specify network-address and wildcard-mask to configure one or multiple interfaces in an area. To run OSPF on an interface, ensure that the primary IP address of this interface is in the network segment range specified in the network (OSPF) command. If the secondary IP address of the main interface is in the network segment range specified in this command, the main interface cannot run OSPF.
- The mask length of the interface's IP address is not less than that specified in the network command. OSPF uses a reverse mask. For example, 0.0.0.255 indicates that the mask length is 24 bits.
When the wildcard-mask parameter in the network command is set to all 0s, OSPF can run on the interface if the IP address of the interface is the IP address specified in the network network-address command.
- The primary address of the interface is within the network segment range specified in the network command.
Precautions
OSPF neighbor relationships cannot be established using the secondary IP addresses of interfaces.
After the network 0.0.0.0 255.255.255.255 command is executed, routes to the network segment where the IP address of the management interface belongs are also imported in the OSPF routing table. Therefore, use this command with caution.
For the same network address wildcard-mask, the last description configured by description takes effect.
On a loopback interface, by default, OSPF advertises its IP address in the form of a 32-bit host route, independent of the mask length of the IP address on the interface.
To advertise the network segment route of a loopback interface, you need to run the ospf network-type command to set the network type to broadcast or NBMA.
- When an OSPF sham link is configured, the local address cannot be advertised through the OSPF process of a private network.
- Two areas that overlap cannot be configured between different processes in the same instance, or between different areas in the same process.
- The ospf enable command configuration takes precedence over the network command configuration.
Example
# Configure the primary IP address of the interface that runs OSPF to be in the network segment of 192.168.1.0/24, set the ID of the OSPF area where the interface resides to 2, and configure 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 (OSPF)
Function
The nexthop command sets the preference for the equal-cost routes. After OSPF calculates the equal-cost routes, the next hop is chosen from these equal-cost routes based on the value of weight. The smaller the value is, the higher the preference is.
The undo nexthop command cancels the preference of these equal-cost routes.
By default, the value of weight is 255. Equal-cost routes have no preference, and they forward packets at the same time. Load balancing is performed among them.
Parameters
Parameter | Description | Value |
---|---|---|
ip-address |
Indicates the IP address of next hop. |
The value is in dotted decimal notation. |
weight value |
Indicates the weight of the next hop. The smaller the value is, the higher the preference of the route is. |
It is an integer that ranges from 1 to 254. |
nssa (OSPF Area)
Function
The nssa command configures an NSSA.
The undo nssa command cancels the configuration of an NSSA.
By default, no OSPF area is configured as an NSSA.
Format
nssa [ { default-route-advertise [ backbone-peer-ignore ] | suppress-default-route } | flush-waiting-timer interval-value | no-import-route | no-summary | set-n-bit | suppress-forwarding-address | translator-always | translator-interval interval-value | zero-address-forwarding | translator-strict ] *
undo nssa [ flush-waiting-timer interval-value ]
Parameters
Parameter | Description | Value |
---|---|---|
default-route-advertise |
Generates default Type7 LSAs on the ASBR and then advertises them to the NSSA. NOTE:
The ABR generates a default NSSA LSA (Type7 LSA) automatically and advertises it in the NSSA. Type 7 LSAs carrying the default route will be generated only when the default route 0.0.0.0/0 exists in the routing table on the ASBR. |
- |
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. |
- |
suppress-default-route |
Generates default Type-7 LSAs on the ASBR or ABR and then not advertises them to the NSSA. |
- |
flush-waiting-timer interval-value |
Indicates the interval for an ASBR to send aged Type 5 LSAs. The parameter takes effect only when it is set. |
The value is an integer that ranges from 1 to 40, in seconds. |
no-import-route |
Indicates that no external route is imported to an NSSA. |
- |
no-summary |
Indicates that an ABR is prohibited from sending summary LSAs to the NSSA. |
- |
set-n-bit |
Sets the N-bit in DD packets. |
- |
suppress-forwarding-address |
Sets the FA of the Type 5 LSAs translated from Type 7 LSAs by the NSSA ABR to 0.0.0.0. |
- |
translator-always |
Specifies 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. |
- |
translator-strict |
Configures the translator to perform strict check on the P-bit flag. The translator determines whether to translate Type 7 LSAs into Type 5 LSAs based on the P-bit flag. |
- |
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 routers in the NSSA must be configured with NSSA attributes using the nssa command.
The default-route-advertise parameter is configured to advertise Type 7 LSAs carrying the default route on the ASBR to the NSSA.
Regardless of whether the default route 0.0.0.0/0 exists in the routing table on the ABR, Type 7 LSAs carrying the default route will be generated. However, Type 7 LSAs carrying the default route will be generated only when the default route 0.0.0.0/0 exists in the routing table on the ASBR.
When the area to which the ASBR belongs is configured as an NSSA, invalid Type 5 LSAs from other routers in the area where LSAs are flooded will be reserved. These LSAs will be deleted only when the aging time reaches 40s. The router performance is affected because the forwarding of a large number of LSAs consumes the memory resources. To resolve such a problem, you can set the parameter flush-waiting-timer to the maximum value 40s for Type 5 LSAs so that the invalid Type 5 LSAs from other routers can be deleted in time.
When the LS age field value (aging time) in the header of an LSA reaches 40s, the LSA is deleted.
If an ASBR also functions as an ABR, flush-waiting-timer does not take effect. This prevents Type 5 LSAs in the non-NSSAs from being deleted.
- If an ASBR also functions as an ABR, the no-import-route parameter is configured to prevent external routes imported using the import-route command from being advertised to the NSSA.
- The no-summary parameter is configured on an ABR to reduce the number of LSAs that are transmitted to the NSSA. This implementation 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 exist in the backbone area. The default Type 3 LSAs preferentially take effect.
- After the set-n-bit parameter is configured, the N-bit is set in the database description (DD) packets during the synchronization between the router and neighboring routers.
- If multiple ABRs are deployed in the NSSA, the system automatically selects an ABR (generally the router with the largest router ID) as a translator to convert Type 7 LSAs into Type 5 LSAs. You can configure the translator-always parameter on an ABR to specify the ABR as an all-the-time translator. To specify two ABRs for load balancing, configure the translator-always parameter on the chosen ABRs to specify the ABRs as all-the-time translators. You can use this command to pre-configure a fixed translator to prevent LSA flooding caused by translator role changes.
- The translator-interval parameter is used to ensure uninterrupted services when translator roles change. The value of interval-value must be greater than the flooding period.
Configuration Impact
Configuring or deleting NSSA attributes may trigger routing update in the area. A second configuration of NSSA attributes can be implemented or canceled only after a routing update is complete.
Precautions
It is recommended that a loopback address be configured 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) under an OSPF process is deleted, useless Type 5 LSAs originated by the local router in the area where are flooded will be deleted immediately. The local router still reserves useless Type 5 LSAs from other routers. These useless Type 5 LSAs will be deleted only when the aging time reaches 40s.
opaque-capability enable
Function
The opaque-capability enable command enables the Opaque LSA capability so that an OSPF process can generate Opaque LSAs, and receive Opaque LSAs from neighbors.
The undo opaque-capability command disables the Opaque-LSA capability.
By default, the Opaque-LSA capability is disabled.
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 router-id | vpn-instance vpn-instance-name ] *
undo ospf process-id [ flush-waiting-timer time ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. By default, it is 1. |
router-id router-id |
Specifies a router ID. |
It is in dotted decimal notation. |
vpn-instance vpn-instance-name |
Specifies the name of a VPN instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
flush-waiting-timer time |
Indicates the interval for generating aged LSAs. The parameter takes effect only when it is set. |
The value is an integer that ranges from 1 to 40, in seconds. |
Usage Guidelines
Usage Scenario
You can set OSPF parameters only after creating an OSPF process.
OSPF supports multi-process. More than one OSPF process can run on the same device, and is independent of each other. Route interaction between different OSPF processes is similar to route interaction between different routing protocols.
The ID of an OSPF device can be configured manually. If no ID is specified through a command for an OSPF device, the system automatically selects an IP address of the interface as the router ID. The IP addresses of loopback interfaces are sequenced in descending order, and then the IP addresses of non-loopback interfaces are also sequenced in descending order. Among these IP addresses, the second largest one is selected as the router ID. If a router ID conflict occurs on a device, the conflicting IP address will be removed from the preceding sequence.
- The ospf command is used to re-configure an OSPF router ID, and then the OSPF process is restarted.
- The system router ID is re-configured, and then the OSPF process is restarted.
- The IP address of the original system router ID is deleted, and then the OSPF process is restarted.
Configuration Impact
After an OSPF process is disabled by using the undo ospf command, the receive end still maintains the LSAs generated by this OSPF process. These invalid LSAs occupy the system memory and are deleted only when the LS age field (aging time) reaches 3600 seconds. When the undo ospf process-id flush-waiting-timer time command is used to stop an OSPF process, the router regenerates an LSA in the set time and sets the LS age field to 3600 seconds. After other routers receive the LSA with the LS age field as 3600 seconds, they delete the LSA immediately. If the host does not send all the LSAs in the set time, other routers still reserve invalid LSAs.
When the LS age field (aging time) in the LSA header reaches 3600 seconds, this LSA is deleted.
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.
The router ID of each OSPF process must be unique on the entire network; otherwise, the OSPF neighbor relationship cannot be set up and routing information is incorrect. Configuring a unique router ID for each OSPF process on each OSPF device is recommended.
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 on an interface.
By default, an interface does not authenticate OSPF packets.
Format
ospf authentication-mode { simple [ plain plain-text | [ cipher ] cipher-text ] | null }
ospf authentication-mode { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ]
ospf authentication-mode keychain keychain-name
undo ospf authentication-mode
Parameters
Parameter | Description | Value |
---|---|---|
simple |
Indicates simple authentication. In simple authentication, the password type is cipher by default. NOTICE:
Simple authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
plain |
Indicates plain authentication. Only plain text can be entered, and only plain text is displayed when the configuration file is viewed. NOTICE:
If plain is selected, the password is saved in the configuration file in plain text. This carries security risks. It is recommended that cipher be specified to save the password in cipher text. |
When cipher is configured, enter only the password in plain text. Then, the password is displayed in plain text in configuration files. Simple authentication uses the password in plain text by default. |
plain-text |
Specifies a plain text password. |
plain-text is a string of 1 to 8 characters without spaces when simple is configured, and is a string of 1 to 255 characters without spaces when md5, hmac-md5 or hmac-sha256 is configured. |
cipher |
Indicates cipher authentication. Either plain text or cipher text can be entered, and cipher text is displayed when the configuration file is viewed. |
When cipher is configured, enter only the password in cipher text. Then, the password is displayed in cipher text in configuration files. MD5 authentication, HMAC-SHA256 authentication or HMAC-MD5 authentication uses the password in cipher text by default. |
cipher-text |
Specifies a cipher text password. |
The value is a string of characters without spaces. In simple authentication, a plain text password is a string of 1 to 8 characters and a cipher text password is a string of 48, 24 or 32 characters. In MD5 authentication, HMAC-SHA256 authentication or HMAC-MD5 authentication, a plain text password is a string of 1 to 255 characters and a cipher text password is a string of 20 to 392 characters. |
md5 |
Indicates MD5 authentication. NOTICE:
MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-md5 |
Indicates HMAC-MD5 authentication. NOTICE:
HMAC-MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-sha256 |
Indicates HMAC-SHA256 authentication. |
- |
key-id |
Specifies the authentication key ID of the interface's cipher authentication. The key ID must be consistent with that of the peer. |
The value is an integer that ranges from 1 to 255. |
keychain |
Indicates keychain authentication. NOTE:
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, OSPF authentication will fail. |
- |
keychain-name |
Specifies the keychain name. |
The value is a string of 1 to 47 case-insensitive characters. Except the question mark (?) and space. However, when double quotation marks (") are used around the string, spaces are allowed in the string. |
null |
Indicates null authentication. |
- |
Usage Guidelines
Usage Scenario
Due to the defects and non-strict implementation of the TCP/IP protocol suite and increasing attacks on TCP/IP networks, the impact generated by attacks on the network may become more serious. Attacks on network devices may lead to a network crash. To improve OSPF network security, configure authentication.
Configuration Impact
Interface authentication is used to set the authentication mode and password used between neighboring devices. It takes precedence over area authentication.
Precautions
Null authentication is an authentication method. It does not indicate that no authentication is configured.
The authentication mode and password configured for interfaces on the same network segment must be the same.
OSPF does not support the configuration on the null interface.
An authentication password does not contain spaces.
ospf bfd
Function
The ospf bfd command enables the BFD on the specified interface enabled with OSPF, or sets the parameter values of a BFD session.
The undo ospf bfd command deletes the BFD on the specified interface, or restores the default parameter values of a BFD session.
By default, BFD is not enabled or configured at OSPF interface view.
Format
ospf bfd enable
undo ospf bfd enable
ospf bfd { min-rx-interval receive-interval | min-tx-interval transmit-interval | detect-multiplier multiplier-value | frr-binding } *
undo ospf bfd { min-rx-interval [ receive-interval ] | min-tx-interval [ transmit-interval ] | detect-multiplier [ multiplier-value ] | frr-binding } *
Parameters
Parameter | Description | Value |
---|---|---|
enable |
Enables BFD. |
- |
min-rx-interval receive-interval |
Indicates the minimum interval at which BFD packets are received from the remote end. |
The value is an integer ranging from 10 to 2000, in milliseconds. The default value is 1000 milliseconds. |
min-tx-interval transmit-interval |
Indicates the minimum interval at which BFD packets are sent to the remote end. |
The value is an integer ranging from 10 to 2000, in milliseconds. The default value is 1000 milliseconds. |
detect-multiplier multiplier-value |
Specifies the local detection multiplier. NOTE:
After BFD is enabled, OSPF establishes BFD sessions only with neighbors in the Full state. |
The value is an integer ranging from 3 to 50. By default, it is 3. |
frr-binding |
Binds the BFD session status and the link status of an interface. That is, when the BFD status goes Down, the link status of the interface also goes Down. This enables traffic to be switched to the backup path. NOTE:
AR611-S, AR611W-S, AR611, AR611W, AR611W-LTE4CN, AR617VW, AR617VW-LTE4, and AR617VW-LTE4EA do not support frr-binding parameter. |
- |
Usage Guidelines
Usage Scenario
The link failure or the topology change causes devices to re-calculate routes. Therefore, the convergence of routing protocols must be sped up to improve the network performance.
Link faults are unavoidable. Therefore, a feasible solution is required to detect faults faster and notify the faults to routing protocols immediately. If BFD is associated with routing protocols, once a link fault occurs, BFD can speed up the convergence of routing protocols.
OSPF IP FRR requires the low layer to fast respond to the link change. Traffic, therefore, can be rapidly switched to the backup link when a link fails. After the frr-binding parameter is configured, the BFD status is bound to the link status of an interface. Specifically, when the BFD status goes Down, the link status of the interface also goes Down. This ensures that faults are detected quickly.
Prerequisites
The configured parameters of the BFD session are valid on an interface only when BFD is enabled on the interface.
Procedure
The receive-interval is obtained through the negotiation between the local end and peer end 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, it considers that the neighbor is Down.
Configuration Impact
If global BFD is not enabled, you can enable BFD on an interface but cannot set up BFD sessions. 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 in 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.
The ospf bfd enable command and the ospf bfd block command are mutually exclusive.
After BFD is disabled from an interface through the undo ospf bfd enable command, the parameters for setting up BFD sessions remain on this interface but do not take effect.
Example
# Enable BFD on GE1/0/0 and specify the minimum interval for receiving BFD packets to 400 ms and the local detection multiplier to 4.
<Huawei> system-view [Huawei] interface gigabitethernet 1/0/0
[Huawei-GigabitEthernet1/0/0] ospf bfd enable
[Huawei-GigabitEthernet1/0/0] ospf bfd min-rx-interval 400 detect-multiplier 4
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, the device does not prevent an interface from dynamically setting up a BFD session.
Usage Guidelines
Usage Scenario
After the bfd all-interfaces enable command is used for an OSPF process, BFD sessions are created on all the OSPF interfaces whose neighbor status is Full. You can run the ospf bfd block command on interfaces where BFD is not required to prevent the interfaces from dynamically setting up BFD sessions.
Prerequisites
BFD is enabled on interfaces.
Precautions
The ospf bfd enable command and the ospf bfd block command are mutually exclusive.
ospf cost
Function
The ospf cost command sets the cost of an OSPF on an interface.
The undo ospf cost command restores the default cost for OSPF.
By default, the cost of an interface running OSPF is calculated using the following formula: Interface cost = Bandwidth reference value/Interface bandwidth where, the bandwidth reference value can be changed using the bandwidth-reference command. The default cost of loopback interface is 0.
Parameters
Parameter | Description | Value |
---|---|---|
cost |
Specifies the cost of an OSPF-enabled interface. |
The value is an integer ranging from 1 to 65535. |
Usage Guidelines
Usage Scenario
OSPF can automatically calculate the link cost for an interface based on the interface bandwidth. You can also set the link cost for the interface through ospf cost commands.
Load balancing can be performed among several routes with the same protocol, cost, and destination address. According to the actual networking condition, you can determine whether to perform load balancing by changing the cost of the interface.
Configuration Impact
If no cost is set for an OSPF interface through the ospf cost command, OSPF automatically calculates its cost based on the interface bandwidth. The calculation formula is as follows: Cost of the interface = Bandwidth reference value/Interface bandwidth. The integer of the calculated result is the cost of the interface. If the calculated result is smaller than 1, the cost is 1. Changing the bandwidth reference value can change the cost of an interface.
By default, the bandwidth reference value is 100 Mbit/s divided by the interface bandwidth. With the formula 100000000/Bandwidth, the default costs of the Ethernet (100 Mbit/s) interface is 1.
56 kbit/s Serial port: 1785
64 kbit/s Serial port: 1562
E1 (2.048 Mbit/s): 48
Ethernet (100 Mbit/s): 1
No default cost is configured for trunk interfaces, because a trunk interface has multiple member interfaces that are in constant change.
Precautions
The ospf cost command cannot run on null interfaces.
ospf dr-priority
Function
The ospf dr-priority command sets the priority of the interface that participates in the DR election.
The undo ospf dr-priority command restores the default setting.
By default, the priority is 1.
Parameters
Parameter | Description | Value |
---|---|---|
priority |
Specifies the priority of the interface that participates in the DR or BDR election. The greater the value, the higher the priority. |
The value is an integer ranging from 0 to 255. |
Usage Guidelines
Usage Scenario
The DR priority of an interface determines whether it is qualified to be a DR. The interface with the highest DR priority is elected as the DR. If the DR priority of an interface on a device is 0, the device cannot be elected as a DR or a BDR. On a broadcast or NBMA network, you can set the DR priority of an interface to determine whether it is qualified to be a DR or a BDR.
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
Restarting or shutting down an interface will interrupt the OSPF adjacency between devices. Therefore, perform the operation with caution.
If the DR priority of a device is re-configured, the DR or BDR on the network will not be re-elected. You can re-elect a DR or a BDR by using either of the following methods. This, however, will interrupt the OSPF adjacency between devices. Therefore, use the following methods with caution.
- Restart the OSPF processes on all devices.
- Run the shutdown and then undo shutdown commands on the interfaces where OSPF adjacencies are set up.
In OSPF, the DR priority cannot be configured for null interfaces.
ospf enable
Function
The ospf enable command enables OSPF on an interface.
The undo ospf enable command disables OSPF on an interface.
By default, the interface does not run the OSPF.
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. |
The value is an integer ranging from 1 to 65535. The default value is 1. |
area area-id |
Specifies an area ID. |
The value can be a decimal integer or an IP address. When the value is an integer, the value ranges from 0 to 4294967295. |
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 on an interface, the network configuration takes effect on the interface automatically.
Configuration Impact
The interface will alternate between up and down when the ospf enable command and the network command are run on the interface repeatedly.
Precautions
An interface can be configured with only one OSPF process.
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 by 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 belonging to different VPN instances cannot be added to the same OSPF process.
ospf filter-lsa-out
Function
The ospf filter-lsa-out command configures the specified interface enabled with OSPF to filter outgoing LSAs.
The undo ospf filter-lsa-out command configures a router not to filter outgoing LSAs.
By default, outgoing LSAs are not filtered.
Format
ospf filter-lsa-out { all | { summary [ acl { acl-number | acl-name } ] | ase [ acl { acl-number | acl-name } ] | nssa [ acl { acl-number | acl-name } ] } * }
undo ospf filter-lsa-out
Parameters
Parameter | Description | Value |
---|---|---|
all |
Filters all outgoing LSAs except grace LSAs. |
- |
summary |
Filters outgoing network summary LSAs (Type 3). |
- |
ase |
Filters outgoing AS external LSAs (Type 5). |
- |
nssa |
Filters outgoing NSSA LSAs (Type 7). |
- |
acl acl-number |
Specifies the number of the basic ACL. |
The value is an integer that ranges from 2000 to 2999. |
acl acl-name |
Specifies the name of a Named ACL. |
The value is a string of 1 to 32 case-sensitive characters without spaces. The value must start with a letter (case sensitive). |
Usage Guidelines
Usage Scenario
When multiple links exist between two routers, based on the filtering policy, the ospf filter-lsa-out command configures the local router to filter the outgoing LSAs before sending them along specified links. This can reduce the unnecessary retransmission of LSAs and save bandwidth resources.
Configuration Impact
Filtering the outgoing LSAs on the specified 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.
The command takes effect only on the interfaces on which it is run and must be run on both local and remote interfaces. The LSAs that have been sent are aged in 3600s.
Precautions
When the rule command is used to configure the filtering rules for a named ACL configured using the acl command, 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.
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.
ospf frr block
Function
The ospf frr block, you can block 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.
AR600 series does not support this function.
Usage Guidelines
Usage Scenario
OSPF IP FRR can be disabled using the ospf frr block command on an interface of a specific device that is running important services and resides on an FRR backup link. This setting prevents the device connected to this interface from being a part of a backup link and being burdened after FRR switches traffic to the backup link.
Precautions
Before configuring OSPF IP FRR, you need to 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.
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.
Usage Guidelines
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)
By default, master/slave board switching triggered by abnormal OSPF LSA aging is enabled. To disable master/slave board switching triggered by abnormal OSPF LSA aging, run the ospf maxage-lsa auto-protect disable command.
ospf mib-binding
Function
The ospf mib-binding command binds an OSPF process to SNMP and makes OSPF respond to SNMP requests.
The undo ospf mib-binding command disables the binding.
By default, OSPF processes are not bound to SNMP.
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the OSPF process ID. |
The value is an integer ranging from 1 to 65535. |
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 which OSPF process is processed by the OSPF MIB. That is, you can bind the OSPF MIB to a specified OSPF process.
Prerequisites
An OSPF process has been created using the ospf command in the system view.
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 settings.
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.
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
OSPF does not support configuration on the Null interface.
After the command is configured, the system automatically restarts the OSPF process.
ospf network-type
Function
The ospf network-type command sets the network type of the OSPF interface.
The undo ospf network-type command restores the default network type of the OSPF interface.
By default, the network type of an interface is determined by the physical interface. The network type of Ethernet interface is broadcast, that of the serial interface (encapsulated with PPP or HDLC) is p2p, and that of ATM interface and Frame-relay interface is nbma.
Format
ospf network-type { broadcast | nbma | p2mp | p2p [ peer-ip-ignore ] }
undo ospf network-type
Parameters
Parameter | Description | Value |
---|---|---|
broadcast |
Indicates that the network type of the interface is changed to broadcast. |
- |
nbma |
Indicates that the network type of the interface is changed to NBMA. |
- |
p2mp |
Indicates that the network type of the interface is changed to point-to-multipoint. |
- |
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. |
- |
Usage Guidelines
Usage Scenario
When link layer protocols remain unchanged, you can change network types and configure OSPF features to flexibly build networks.
In the broadcast network, if there is a device that does not support multicast address, you can change the network type of the interface to NBMA.
If the network type of the interface is NBMA, when the interface type is changed to broadcast, the neighboring device is not needed.
The condition for changing an NBMA network to broadcast network is that there should be a direct virtual circuit between any two devices. The network should be a full mesh network. If a network does not meet the preceding conditions, you must change the type of network to point-to-multipoint. In this manner, two indirect devices can communicate with the help of one or two direct and reachable devices. Instead of configuring the neighboring device, you can change the network type of the interface to point-to-multipoint.
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
OSPF does not support the configuration on the Null interface.
When the network type of an interface is NBMA, or the network type of an interface is changed to NBMA manually, you must run the peer command to configure the 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 both ends of the link must be identical. Otherwise, the two interfaces cannot set up the neighbor relationship.
When the network type of one OSPF interface is broadcast and the network type of the other OSPF interface is P2P or P2MP, the two interfaces can still set up the neighbor relationship, but cannot learn the OSPF routing information each other.
ospf p2mp-mask-ignore
Function
The ospf p2mp-mask-ignore command configures the device not to check 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.
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 not to check the network mask in Hello packets. In this manner, the OSPF neighbor relationship can be established.
Prerequisites
Because P2MP is not a link layer protocol, each P2MP network is forcibly changed from a network of another type. A common P2MP network is changed from a non-fully connected Non-Broadcast Multi-Access (NBMA) network through the ospf network-type p2mp command.
ospf router-id auto-recover disable
Function
Using the ospf router-id auto-recover disable command, you can disable automatic recovery that will take effect after router ID conflict is detected.
Using the undo ospf router-id auto-recover disable command, you can enable automatic recovery that will take effect after router ID conflict is detected.
By default, automatic recovery takes effect after router ID conflict occurs.
Usage Guidelines
If router ID conflict occurs in an OSPF area, the system can define a new router ID, preventing route flapping and reducing route calculation operations. Other protocols will not go Down when the CPU usage is controlled.
- 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.
ospf smart-discover
Function
The ospf smart-discover command enables smart-discover on an interface.
The undo ospf smart-discover command disables smart-discover on an interface.
By default, smart-discover is disabled on interfaces.
Usage Guidelines
Usage Scenario
In normal situations, devices periodically send Hello packets through OSPF interfaces. By sending Hello packets, devices set up and maintain neighbor relationships, and elect the DR and BDR on the multi-access network (broadcast or NBMA network). When setting up neighbor relationships or electing the DR and BDR on the multi-access network, interfaces can send Hello packets only when the Hello timer expires. This slows down the establishment of neighbor relationships and election of the DR and BDR.
After smart-discover is configured, when the status of the neighbor relationship changes or the DR and BDR on the multi-access network changes, the device can send Hello packets to its neighbor immediately without waiting for the expiration of the Hello timer.
Procedure
On broadcast and NBMA networks, neighbor relationships can be rapidly set up and a DR and a BDR can be rapidly elected.
- When the neighbor status becomes 2-way for the first time or returns to Init from the 2-way or higher state, the smart-discover-enabled interface sends Hello packets to a neighbor without waiting for the expiration of the Hello timer when detecting that the neighbor status changes.
- When the status of the interface functioning as the DR or BDR on the multi-access network changes, the smart-discover-enabled interface actively sends Hello packets on the network segment and then participates in the DR or BDR election.
The principle of setting up adjacencies rapidly on P2P or P2MP networks is the same as that on broadcast and NBMA networks.
Configuration Impact
The interval for sending Hello packets on an interface is determined by the interval for sending Hello packets set on the interface.
Precautions
The default interval for sending Hello packets varies with the network type.
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.
By default, the detection interval of OSPF neighbor relationship flapping suppression is 60s, the suppression threshold is 10, and the interval for exiting from suppression is 120s.
Format
ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } *
undo ospf suppress-flapping peer { detecting-interval detecting-interval | threshold threshold | resume-interval resume-interval } *
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 from 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. NOTE:
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. |
Usage Guidelines
Usage Scenario
To configure detection parameters for OSPF neighbor relationship flapping suppression on an interface, run the ospf suppress-flapping peer command. However, keeping the default configurations is recommended.
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.
Example
# 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 GE1/0/0.
<Huawei> system-view
[Huawei] interface gigabitethernet 1/0/0
[Huawei-GigabitEthernet1/0/0] ospf suppress-flapping peer detecting-interval 5 threshold 40 resume-interval 20
ospf suppress-flapping peer disable
Function
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.
By default, OSPF neighbor relationship flapping suppression is enabled on all interfaces.
Usage Guidelines
Usage Scenario
By default, OSPF neighbor relationship flapping suppression is enabled on all interfaces in the same OSPF process. To disable the function from one of the interfaces, run the ospf suppress-flapping peer disable command.
Prerequisites
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 suppress-flapping peer hold-down
Function
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.
By default, the Hold-down mode is disabled, and the Hold-max-cost mode is enabled.
Format
ospf suppress-flapping peer hold-down interval
undo ospf suppress-flapping peer hold-down [ interval ]
Parameters
Parameter | Description | Value |
---|---|---|
interval | Specifies the duration of the Hold-down mode. | The value is an integer ranging from 1 to 600, in seconds. The default value is 60. |
Usage Guidelines
Usage Scenario
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. To configure the Hold-down mode and set duration for this mode, run the ospf suppress-flapping peer hold-down interval command.
Prerequisites
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 suppress-flapping peer hold-max-cost disable
Function
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 Hold-max-cost mode is enabled.
Format
ospf suppress-flapping peer hold-max-cost disable
undo ospf suppress-flapping peer hold-max-cost disable
Usage Guidelines
Usage Scenario
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. To configure the Hold-down mode and set duration for this mode, run the ospf suppress-flapping peer hold-down interval command.
Prerequisites
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.
ospf timer dead
Function
The ospf timer dead command sets the dead interval of the OSPF neighbor.
The undo ospf timer dead command restores the default dead interval of the neighbor.
By default, for the interface of P2P and Broadcast, the dead interval for the OSPF neighbors is 40 seconds; for that of NBMA and P2MP, it is 120 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies dead interval of the OSPF neighbors. |
The value is an integer ranging from 1 to 235926000, in seconds. NOTE:
Setting the dead interval of an OSPF neighbor to be longer than 20s is recommended. |
Usage Guidelines
Usage Scenario
The dead interval of OSPF neighbors refers to that within this interval, if no Hello packet is received from the neighbor, the neighbor is considered as invalid. The dead interval on an OSPF-running interface 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
OSPF does not support the configuration on a null interface.
If the dead interval of an OSPF neighbor is shorter than 20s, the session may be closed. Therefore, if dead interval is shorter than 20s, the actual dead interval of an OSPF neighbor is not shorter than 20s.
To speed up OSPF convergence in the case of a link failure, configuring Configuring BFD for OSPF is recommended.
ospf timer hello
Function
The ospf timer hello command sets the interval for sending Hello packets on an interface.
The undo ospf timer hello command restores the default value of the interval.
By default, for the interface of P2P and Broadcast type, the interval for sending Hello packets is 10 seconds; for the interface of NBMA and P2MP type, it is 30 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies the interval for sending the Hello packet on an interface. |
The value is an integer ranging from 1 to 65535, in seconds. Setting hello interval to be longer than or equal to 5s 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 20s. |
- |
Usage Guidelines
Usage Scenario
Hello packets are periodically sent on OSPF interfaces to establish and maintain neighbor relationships. A Hello packet contains information about timers, DRs, BDRs, and known neighbors.
The interval value is added to Hello packets for transmission. The smaller the hello interval is, the faster the changing speed of the network topology is. The cost of routes, however, becomes greater. Ensure that the parameters of this interface and the adjacent routers are consistent.
Precautions
OSPF does not support the configuration on a null interface.
If hello interval is set but a dead interval is not set using the ospf timer dead command, the dead interval of an OSPF neighbor is four times the value of hello interval. If the dead interval of an OSPF neighbor is shorter than 20s, the session may be closed. Therefore, if hello interval is shorter than 5s, the actual dead interval of an OSPF neighbor is not shorter than 20s.
To speed up OSPF convergence in the case of a link failure, configuring Configuring BFD for OSPF is recommended.
ospf timer poll
Function
The ospf timer poll command sets the poll interval for sending Hello packets on NBMA network.
The undo ospf timer poll command restores the default poll interval.
By default, it is 120 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies the poll interval for sending Hello packets. |
The value is an integer ranging from 1 to 3600, in seconds. |
Usage Guidelines
Usage Scenario
On the NBMA network, if a neighbor is invalid, the device periodically sends the Hello packets to the neighbor according to the poll interval set in the ospf timer poll command. The poll interval should be at least 4 times that of the Hello interval.
Precautions
OSPF does not support the configuration on a null interface.
ospf timer retransmit
Function
The ospf timer retransmit command sets the interval for retransmitting LSA on an interface.
The undo ospf timer retransmit command restores the default interval for retransmitting LSA on the interface.
By default, the interval time is 5 seconds.
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies interval for retransmitting LSA on an interface. |
The value is an integer ranging from 1 to 3600, in seconds. |
Usage Guidelines
Usage Scenario
When a device transmits an LSA to its neighbor, it has to wait for the ACK packet from the neighbor. If no ACK packet is received from the neighbor in the LSA retransmission interval, this LSA is retransmitted.
You should not set too short LSA retransmission intervals between adjacent routers. Otherwise, it leads to unnecessary retransmission.
Precautions
OSPF does not support the configuration on a Null interface.
ospf trans-delay
Function
The ospf trans-delay command adds an extension period for LSAs that are transmitted on an interface.
The undo ospf trans-delay command restores the default delay on the interface.
By default, the delay is 1 second.
Parameters
Parameter | Description | Value |
---|---|---|
interval |
Specifies the delay for transmitting LSA on an interface. |
The value is an integer ranging from 1 to 500, in seconds. |
Usage Guidelines
Usage Scenario
LSA ages in LSDB (increase by 1 each second), but LSA does not age during transmission in the network. It is therefore necessary to use this command to set a certain delay before the LSA is transmitted. This configuration is important for a low-speed network.
Precautions
OSPF does not support the configuration on the Null interface.
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 hops [ nonstandard-multicast ] [ vpn-instance vpn-instance-name ]
undo ospf valid-ttl-hops [ hops [ nonstandard-multicast ] ] [ vpn-instance vpn-instance-name ]
Parameters
Parameter | Description | Value |
---|---|---|
hops |
Specifies the TTL value to be checked. |
The value is an integer that ranges from 1 to 255. The default value is 255. |
nonstandard-multicast |
Specifies the GTSM configuration is also valid for multicast packets. When the nonstandard-multicast parameter is configured:
|
- |
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, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
In a network demanding higher security, you can enable GTSM to improve the security of the OSPF network. GTSM defends against attacks by checking the TTL value. If an attacker simulates OSPF unicast packets and keeps sending them to a router, the router receives the packets and directly sends them to the main control board for OSPF processing, without checking the validity of the packets. In this case, the router is busy processing these packets, causing high usage of the CPU. GTSM protects the routers and enhances the system security by checking whether the TTL value in the IP packet header is in a pre-defined range.
The ospf valid-ttl-hops command is used to enable OSPF GTSM. The vpn-instance parameter must be specified in the command if you need to check the TTL value of packets that match the GTSM policy.
For example, if running the ospf valid-ttl-hops command enables OSPF GTSM on both the public network and the private network. If running the ospf valid-ttl-hops 5 vpn-instance vpn1 command, in addition to enabling OSPF GTSM on both the public network and the private network, you can detect the TTL value of OSPF packets in the VPN instance named vpn1, configure the default TTL value for packets unmatched with the GTSM policy for the OSPF packets from other instances of the private network and the public network.
Precautions
- If a VPN instance is specified in the ospf valid-ttl-hops command and the interface is bound to the VPN instance, all the unicast packets sent to this interface are dropped when the set number of TTL hops is smaller than the actual number of hops on the network.
- If a virtual link or sham link is configured, the actual TTL value and the configured TTL value must be the same. That means that the number of virtual links or sham links that pass through the router is calculated. Otherwise, packets sent from neighbors of a virtual link or a sham link will be dropped.
GTSM only checks the TTL values of the packets that match the GTSM policy. If the packets do not match the GTSM policy, you can set the pass parameter or drop parameter in the gtsm default-action command to pass or drop these packets.
- If only a private or public network policy is configured, run the gtsm default-action command to set the default behavior for processing the packets unmatched with the GTSM policy to pass to prevent the OSPF packets of other instances from being discarded.
peer (OSPF)
Function
The peer command sets the IP addresses and the DR priority for the adjacent router on an NBMA network.
The undo peer command cancels the IP address of the adjacent router on an NBMA network.
By default, the IP addresses and the DR priority for the adjacent router on an NBMA network is not set.
Parameters
Parameter | Description | Value |
---|---|---|
ip-address |
Specifies the IP address for the adjacent devices. |
The value is in dotted decimal notation. |
dr-priority priority |
Sets the priority for the adjacent devices to select a DR. |
The value of the priority is an integer that ranges from 0 to 255. By default, it is 1. |
Usage Guidelines
In an NBMA network (such as an X.25 or FR network), the entire network can be fully meshed based on the mapping configuration. That means that there is a virtual link between any two devices. In this case, the network running OSPF can be considered as a broadcast network where a DR or a BDR can be selected. You need, however, manually specify the IP address and the DR priority for the adjacent devices using the peer command, because it is impossible to find the adjacent devices dynamically by broadcasting the Hello packet.
preference (OSPF)
Function
The preference command sets the preference of an OSPF route.
The undo preference command restores the default preference of the OSPF route.
By default, the preference of the OSPF route is 10. When ASE is specified, the default value is 150.
Parameters
Parameter | Description | Value |
---|---|---|
ase | Indicates the preference of the AS external route. | - |
preference | Specifies the preference of the OSPF route. The smaller the preference value, the higher the preference. |
The value of the preference is an integer ranging from 1 to 255. |
route-policy route-policy-name | Specifies the name of the route policy. | The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
Multiple dynamic routing protocols can be run on a router at the same time. In this case, there is a problem of route sharing and selecting among routing protocols. The system sets a default preference for each routing protocol. If different protocols have routes to the same destination, the protocol with the higher preference is selected to forward IP packets. Using this command, you can set the preference of an OSPF route.
- If the apply preference clause is configured for the route-policy,
route preference is determined as follows:
Route matching the route-policy: Its preference is determined by the apply clause.
Route unmatching the route-policy: Its preference is determined by the preference command.
In the following example, the preference of the route matching the route-policy abc is set to 50 and the preference of the route unmatching the route-policy 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 included in the route-policy, the preference of routes is 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 make the router prefer OSPF routes by setting the OSPF route preference.
prefix-priority (OSPF)
Function
The prefix-priority command sets the convergence priority of OSPF routes.
The undo prefix-priority command restores the default convergence priority of OSPF routes.
By default, the convergence priority of public 32-bit host routes is medium, and the convergence of other OSPF routes is low.
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 OSPF routes to high. | - |
medium | Sets the convergence priority of OSPF routes to medium. | - |
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, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Scenario
The prefix-priority command sets the convergence priority of OSPF routes according to the specified IP prefix list name, and 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, which accelerates route convergence.
Prerequisites
An IP prefix list has been created using the ip ip-prefix command in the system view.
Configuration Impact
When an LSA meets multiple priorities, the highest priority takes effect.
With the prefix-priority command, OSPF can calculate and flood LSAs, and synchronize LSDBs according to priorities. This speeds up route convergence. OSPF calculates LSAs in the sequence of intra-area routes, inter-area routes, and AS external routes. This command makes OSPF calculate the three types of routes separately according to the specified route calculation priorities. Convergence priorities are critical, high, medium, and 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, and 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. In the public network, OSPF 32-bit host routes are uniformly identified as medium.
reset gtsm statistics
reset ospf counters
Format
reset ospf [ process-id ] counters [ neighbor [ interface-type interface-number ] [ router-id ] ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Indicates the OSPF process ID. If the parameter is not specified, all OSPF processes are restarted. |
The value is an integer ranging from 1 to 65535. |
neighbor |
The statistics of neighbors for the interface. |
- |
interface-type interface-number |
Specifies the type and the number of the interface. |
- |
router-id |
The Router ID of the neighbor. |
The value is in dotted decimal notation. |
Usage Guidelines
When the router restarts an OSPF process, the neighboring router always reserves invalid LSAs. This occupies the memory of the system. These LSAs are deleted only when they expire, that is, when the LS age field in the LSA reaches 3600 seconds. After the reset ospf is used to restart an OSPF process and only when the router ID is changed, the router generates an LSA in the set time and sets the LS age field to 3600 seconds. After receiving the LSA, other routers delete the LSA immediately from their LSDBs. If a device does not send all the LSAs within the set time, other neighboring routers still store some invalid LSAs.
Clearing OSPF statistics does not affect the normal operation of OSPF services.
Once deleted, statistics cannot be restored. Therefore, use caution when deleting statistics.
reset ospf process
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Indicates the OSPF process ID. If the parameter is not specified, all OSPF processes are restarted. |
The value is an integer ranging from 1 to 65535. |
flush-waiting-timer time |
Specified the time when the LSA is generated. The parameter takes effect only when it is set. |
The value is an integer that ranges from 1 to 40, in seconds. |
graceful-restart |
Indicates that graceful restart is enabled. |
- |
Usage Guidelines
Usage Scenario
The reset ospf process command can be used to clear OSPF information to reset the board.
If OSPF connections are reset, OSPF neighbor relationships will be interrupted and the original information cannot be restored. Exercise caution before running the reset ospf process command.
Configuration Impact
After the reset ospf process command is used to restart OSPF, the following situations may occur:
If the router ID is changed, a new router ID will take affect after the command is run.
Re-elect DR and BDR.
OSPF configuration will not be lost after OSPF restarts.
Precautions
Configuring the flush-waiting-timer parameter when OSPF starts, you can clear invalid LSAs within the set time before LSAs time out.
Whether all invalid LSAs on other routers can be deleted is related to the set time.
When the router restarts an OSPF process, the neighboring router always reserves invalid LSAs. This occupies the memory of the system. These LSAs are deleted only when they expire, that is, when the LS age field in the LSA reaches 3600 seconds. After the reset ospf is used to restart an OSPF process and only when the router ID is changed, the router generates an LSA in the set time and sets the LS age field to 3600 seconds. After receiving the LSA, other routers delete the LSA immediately from their LSDBs. If a device does not send all the LSAs within the set time, other neighboring routers still store some invalid LSAs.
reset ospf redistribution
Parameters
Parameter | Description | Value |
---|---|---|
process-id |
Specifies the ID of an OSPF process. If this parameter is not specified, all OSPF processes are restarted. |
The value is an integer that ranges from 1 to 65535. |
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-type interface-number ] [ notify-peer ]
Parameters
Parameter | Description | Value |
---|---|---|
process-id | Specifies the ID of an OSPF process. | The value is an integer ranging from 1 to 65535. |
interface-type interface-number | Specifies an interface type and number. | - |
notify-peer | Instructs neighbors to exit from OSPF neighbor relationship flapping suppression too. | - |
Usage Guidelines
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.
- 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.
retransmission-limit
Function
The retransmission-limit command enables retransmission limit and set the maximum number of retransmissions.
The undo retransmission-limit command disables retransmission limit.
By default, retransmission limit is disabled.
Parameters
Parameter | Description | Value |
---|---|---|
max-number | Indicates the maximum number of retransmissions. | The value is an integer that ranges from 2 to 255. The default value is 30. |
Usage Guidelines
Usage Scenario
The retransmission-limit command can be used to enable Retransmission Limitation for OSPF (RL-for OSPF) to prevent dead loops caused by repeated transmissions when neighbors cannot receive packets.
Configuration Impact
The OSPF retransmission limit can be used in the following packets:
DD packet
LSU packet
LSR packet
If the three types of packets cannot receive the response packets, enable the retransmission attribute, limit the count of retransmission, and disconnect the neighbor when the retransmission exceeds the specified count.
route-tag
Function
The route-tag command sets the tag value for VPN routes.
The undo route-tag command restores the default setting.
By default, the tag value of a VPN route is calculated based on the AS number of BGP. If BGP is not configured, the default tag value is 0.
Parameters
Parameter | Description | Value |
---|---|---|
tag |
Specifies the tag value of VPN routes. |
The value is an integer in the range from 0 to 4294967295. |
disable |
Forbids the using of the tag to detect loops. |
- |
Usage Guidelines
Usage Scenario
The route-tag command can only be used in VPN scenarios to prevent loops on Type 5 LSAs and Type 7 LSAs when a CE is dual-homed to two PEs.
In a networking where a CE is dual-homed to two PEs, PE1 generates Type 5 LSAs and Type 7 LSAs based on the imported BGP routes, and sends these LSAs to the CE, then to PE2. Because OSPF routes have higher priorities over BGP routes, the former will replace the latter on PE2, causing loops. After the route-tag command is run, if the tag value of the PE and an LSA are the same, the PE will neglect the LSA and a loop is prevented.
By default, the first two bytes of the tag value are fixed as 0xD000, and the last two bytes are the AS number of the local BGP. If a BGP AS number is greater than 65535, the default tag 0 is used. You can use the command to change the tag value in this case.
Configuration Impact
The route tags of a VPN can be configured only and takes effect on the PEs where BGP routes are received and OSPF LSAs are generated.
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.
- If BGP is not configured on the routers at both ends, you are advised to run the route-tag disable command to disable tag check.
The tags set by different commands have different priorities:
- The preference of the tag configured using the import-route command is the highest.
- The preference of the tag configured using the route-tag command is medium.
- The preference of the tag configured using the default tag command is the lowest.
Example
# Set the 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] route-distinguisher 100:1
[Huawei-vpn-instance-huawei-af-ipv4] quit
[Huawei-vpn-instance-huawei] quit
[Huawei] ospf 100 vpn-instance huawei
[Huawei-ospf-100] route-tag 100
rfc1583 compatible
Function
The rfc1583 compatible command converts rules defined in RFC 2328 into rules defined in RFC 1583.
The undo rfc1583 compatible command converts rules defined in RFC 1583 into rules defined in RFC 2328.
By default, OSPF supports the routing rule of RFC 1583.
Usage Guidelines
RFC 2328 and RFC 1583 define different OSPF route selection rules. When enabling OSPF, configure the same route selection rules on all devices in the same OSPF area. For example, an OSPF device supports route selection rules defined in RFC 1583 by default. If the other routers in the same OSPF area support route selection rules defined in RFC 2328, you need to run the undo rfc1583 compatible
sham-hello enable (OSPF)
Function
The sham-hello enable command enables the sham-hello function of OSPF.
The undo sham-hello command disables the sham-hello feature.
By default, the sham-hello feature is disabled.
sham-link (OSPF Area)
Function
The sham-link command configures a sham link or sets the parameter values of a sham link.
The undo sham-link command deletes a sham link or restores the default parameter values of a sham link.
By default, no sham link is configured for OSPF.
Format
sham-link source-ip-address destination-ip-address [ [ simple [ plain plain-text | [ cipher ] cipher-text ] | { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ] | authentication-null | keychain keychain-name ] | smart-discover | cost cost | dead dead-interval | hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval ] *
undo sham-link source-ip-address destination-ip-address [ [ simple | md5 | hmac-md5 | hmac-sha256 | authentication-null | keychain ] | smart-discover | cost | dead | hello | retransmit | trans-delay ] *
Parameters
Parameter | Description | Value |
---|---|---|
source-ip-address |
Specifies the source IP address. |
The value is in dotted decimal notation. |
destination-ip-address |
Specifies the destination IP address. |
The value is in dotted decimal notation. |
smart-discover |
Indicates that Hello packets are sent automatically and immediately. |
- |
simple |
Indicates simple authentication. In simple authentication, the password type is cipher by default. NOTICE:
Simple authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
plain |
Indicates plain authentication. Only plain text can be entered, and only plain text is displayed when the configuration file is viewed. NOTICE:
If plain is selected, the password is saved in the configuration file in plain text. This carries security risks. It is recommended to select cipher to save the password in cipher text. |
- |
plain-text |
Specifies a plain text password. |
|
cipher |
Indicates cipher authentication. Either plain text or cipher text can be entered, and cipher text is displayed when the configuration file is viewed. |
- |
cipher-text |
Specifies a cipher text password. |
|
md5 |
Indicates MD5 authentication. NOTICE:
MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-md5 |
Indicates hmac-md5 authentication. NOTICE:
HMAC-MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-sha256 |
Indicates HMAC-SHA256 authentication. |
- |
key-id |
Specifies the authentication key ID of the interface's cipher authentication. The key ID must be consistent with that of the peer. |
The value is an integer that ranges from 1 to 255. |
authentication-null |
Indicates that no authentication is used. |
- |
keychain |
Indicates keychain authentication. NOTE:
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, OSPF authentication will fail. Currently, only the SM3, hmac-md5 and hmac-sha256 algorithms can be used for OSPF. |
- |
keychain-name |
Specifies the keychain name. |
The value is a string of 1 to 47 case-insensitive characters. Except the question mark (?) and space. However, when double quotation marks (") are used around the string, spaces are allowed in the string. |
cost cost |
Specifies the cost of the sham link. |
The value is an integer that ranges from 1 to 65535. The default value is 1. |
dead dead-interval |
Specifies the dead interval. This value must be equal to dead-interval of the router that sets up a virtual link with the local router, and must be at least four times that of hello-interval. |
The value is an integer that ranges from 1 to 235926000, in seconds. |
hello hello-interval |
Specifies the interval for transmitting Hello packets on an interface. This value must be equal to hello-interval of the router that sets up a virtual link with the local router. |
The value is an integer that ranges from 1 to 65535, in seconds. |
retransmit retransmit-interval |
Specifies the interval for retransmitting the LSA packets on an interface. |
The value is an integer that ranges from 1 to 3600, in seconds. |
trans-delay trans-delay-interval |
Specifies the delay in transmitting LSA packets on an interface. |
The value is an integer that ranges from 1 to 3600, in seconds. |
Usage Guidelines
Usage Scenario
The sham-link command can only be used in VPN scenarios.
This command can create a sham link to allow VPN traffic to be preferentially forwarded through routes within the backbone area. This prevents traffic from the same VPN in the same OSPF area from being forwarded through intra-area OSPF routes.
Before enabling neighbors of a sham link to set up adjacencies quickly, configure the smart-discover parameter to actively send Hello packets immediately.
Configuration Impact
AR611, AR611-S, AR611W-S, AR611W, AR611W-LTE4CN, AR617VW, AR617VW-LTE4EA, AR617VW-LTE4, AR651C, and AR651F-Lite do not support MPLS.
Precautions
The route to the endpoint address of a sham link cannot be advertised to the remote PE using an OSPF process in a private network. Otherwise, two routes to the endpoint address of the sham link exist on the remote PE. One route is learned from the OSPF process and the other is learned using MP-BGP. OSPF routes have higher priorities over BGP routes, so the remote PE select an incorrect OSPF route. As a result, the sham link cannot be created.
silent-interface (OSPF)
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, the interface is permitted to receive or send OSPF packet.
Format
silent-interface { all | interface-type interface-number }
undo silent-interface { all | interface-type [ interface-number ] }
Parameters
Parameter | Description | Value |
---|---|---|
all |
Indicates all interfaces in a specified process. |
- |
interface-type interface-number |
Specifies the interface type and the interface number. |
- |
Usage Guidelines
Usage Scenario
To ensure that OSPF routing information cannot be obtained by the devices of a certain network and the local device does not receive routing update information advertised by other devices, you can run the silent-interface command to disable an interface from receiving and sending OSPF packets.
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.
snmp-agent trap enable feature-name ospf
Function
The snmp-agent trap enable feature-name ospf command enables the trap function for the OSPF module.
The undo snmp-agent trap enable feature-name ospf command disables the trap function for the OSPF module.
By default, the trap function is disabled for the OSPF module.
Format
snmp-agent trap enable feature-name ospf trap-name { ospfifauthfailure | ospfifconfigerror | ospfifrxbadpacket | ospfifstatechange | ospflsdbapproachingoverflow | ospflsdboverflow | ospfmaxagelsa | ospfnbrrestarthelperstatuschange | ospfnbrstatechange | ospfnssatranslatorstatuschange | ospforiginatelsa | ospfrestartstatuschange | ospftxretransmit | ospfvirtifauthfailure | ospfvirtifconfigerror | ospfvirtifrxbadpacket | ospfvirtifstatechange | ospfvirtiftxretransmit | ospfvirtnbrrestarthelperstatuschange | ospfvirtnbrstatechange | hwospfv2intraareadripaddressconflict | hwospfv2intraarearouteridconflict | hwospfv2intraarearouteridconflictrecovered | hwospfv2peerflappingsuppressstatuschange }
undo snmp-agent trap enable feature-name ospf trap-name { ospfifauthfailure | ospfifconfigerror | ospfifrxbadpacket | ospfifstatechange | ospflsdbapproachingoverflow | ospflsdboverflow | ospfmaxagelsa | ospfnbrrestarthelperstatuschange | ospfnbrstatechange | ospfnssatranslatorstatuschange | ospforiginatelsa | ospfrestartstatuschange | ospftxretransmit | ospfvirtifauthfailure | ospfvirtifconfigerror | ospfvirtifrxbadpacket | ospfvirtifstatechange | ospfvirtiftxretransmit | ospfvirtnbrrestarthelperstatuschange | ospfvirtnbrstatechange | hwospfv2intraareadripaddressconflict | hwospfv2intraarearouteridconflict | hwospfv2intraarearouteridconflictrecovered | hwospfv2peerflappingsuppressstatuschange }
Parameters
Parameter | Description | Value |
---|---|---|
trap-name |
Enables the traps of OSPF events of specified types. |
- |
hwospfv2intraareadripaddressconflict |
Enables the traps of the ip addresses conflict of DRs in an intra area. |
By default, this trap is disabled. |
hwospfv2intraarearouteridconflict |
Enables the traps of the router IDs conflict in an intra area. |
By default, this trap is disabled. |
ospfifauthfailure |
Enables the traps of the failure of the interface authentication. |
By default, this trap is disabled. |
ospfifconfigerror |
Enables the traps of errors of the interface configuration. |
By default, this trap is disabled. |
ospfifrxbadpacket |
Enables the traps of received bad packets. |
By default, this trap is disabled. |
ospfifstatechange |
Enables the traps of changes of the interface state. |
By default, this trap is disabled. |
ospflsdbapproachingoverflow |
Enables the traps of LSDB is approaching Overflow. |
By default, this trap is disabled. |
ospflsdboverflow |
Enables the traps of LSDB overflow. |
By default, this trap is disabled. |
ospfmaxagelsa |
Enables the traps of Max Age of LSA. |
By default, this trap is disabled. |
ospfnbrrestarthelperstatuschange |
Enables the traps of changes of the neighbor state. |
By default, this trap is disabled. |
ospfnbrstatechange |
Enables the traps of changes of the state of the helper during GR. |
By default, this trap is disabled. |
ospfnssatranslatorstatuschange |
Enables the traps of the status change of the NSSA router converting Type7 LSAs to Type5 LSAs. |
By default, this trap is disabled. |
ospforiginatelsa |
Enables the traps of LSAs that are locally generated. |
By default, this trap is disabled. |
ospfrestartstatuschange |
Enables the traps of changes of the state of the restarter during GR. |
By default, this trap is disabled. |
ospftxretransmit |
Enables the traps of the receiving and sending of packets on the interface. |
By default, this trap is disabled. |
ospfvirtifauthfailure |
Enables the traps of failure of the virtual interface authentication. |
By default, this trap is disabled. |
ospfvirtifconfigerror |
Enables the traps of error of the virtual interface configuration. |
By default, this trap is disabled. |
ospfvirtifrxbadpacket |
Enables the traps of the bad packet that is received on the virtual interface. |
By default, this trap is disabled. |
ospfvirtifstatechange |
Enables the traps of changes of the virtual interface state. |
By default, this trap is disabled. |
ospfvirtiftxretransmit |
Enables the traps of sending and receiving of packets on the virtual interface. |
By default, this trap is disabled. |
ospfvirtnbrrestarthelperstatuschange |
Enables the traps of changes of the GR helper state of neighboring nodes on the virtual link. |
By default, this trap is disabled. |
ospfvirtnbrstatechange |
Enables the traps of changes of the state for the neighbor of the virtual-link. |
By default, this trap is disabled. |
hwospfv2intraarearouteridconflictrecovered |
The OSPF router ID conflict is resolved. |
By default, this trap is enabled. |
hwOspfv2PeerFlappingSuppressStatusChange |
The status of OSPF neighbor relationship flapping suppression changed. |
By default, this trap is disabled. |
Usage Guidelines
To enable the traps of one or more events, you can specify trap-name.
- The non-excessive traps of OSPF module includes:
- ospfIfStateChange
- ospfVirtIfStateChange
- ospfNbrStateChange
- ospfVirtNbrStateChange
- ospfIfAuthFailure
- ospfVirtIfAuthFailure
- ospfIfRxBadPacket
- ospfVirtIfRxBadPacket
- ospfLsdbOverflow
- ospfLsdbApproachingOverflow
- ospfRestartStatusChange
- ospfNbrRestartHelperStatusChange
- ospfVirtNbrRestartHelperStatusChange
- ospfNssaTranslatorStatusChange
- hwOspfv2IntraAreaRouteridConflict
- hwospfv2intraareadripaddressconflict
- The excessive traps of OSPF module includes:
- ospfIfConfigError
- ospfVirtIfConfigError
- ospfTxRetransmit
- ospfVirtIfTxRetransmit
- ospfOriginateLsa
- ospfMaxAgeLsa
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 interval for the SPF calculation is expressed in milliseconds. The maximum interval for the SPF calculation is 10000 ms, the initial interval is 500 ms, and the Holdtime interval is 1000 ms.
Format
spf-schedule-interval { interval1 | intelligent-timer max-interval start-interval hold-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 ranging 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 is an integer ranging from 1 to 120000, in milliseconds. The default value is 10000. |
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. The default value is 500. |
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. The default value is 1000. |
millisecond interval2 | Specifies the interval for OSPF to perform the SPF calculation. | The value is an integer ranging from 1 to 10000, in milliseconds. |
Usage Guidelines
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. When the OSPF LSDB changes, the shortest path needs to be recalculated. Frequent network changes and continual calculation of the shortest path consume many system resources and affect the efficiency of the devices. You can configure an intelligent timer and set a proper interval for the SPF calculation to prevent excessive device memory and bandwidth resources from being consumed.
In a networking environment, in which the convergence time of routes is required to be shorter, you can set millisecond as the unit of interval to increase the frequency of calculating routes. Route convergence therefore speeds up. In other networking environments, the default value is recommended.
Configuration ImpactAfter this command is configured, the interval for the SPF calculation is as follows:
- The initial interval for the 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×2(n-2).
- When the interval specified by hold-interval×2(n-2) reaches the maximum interval specified by max-interval, OSPF performs SPF calculation at the maximum interval until max-interval expires without flapping or the OSPF process is restarted.
stub (OSPF Area)
Function
The stub command sets an area to the stub area.
The undo stub command cancels the settings.
By default, no area is set to the stub area.
Parameters
Parameter | Description | Value |
---|---|---|
no-summary |
Forbids the ABR to send Summary LSAs to the stub area. |
- |
default-route-advertise |
Enables the ABR to generate default Type 3 LSAs and advertise them to the stub area. |
- |
backbone-peer-ignore |
Prevents the ABR from checking the neighbor status when the ABR generates default Type 3 LSAs and advertises them to the stub area. Specifically, the ABR generates default Type 3 LSAs and advertises them to the stub area as long as an interface that is Up exist in the backbone area. |
- |
Usage Guidelines
There are two configuration commands for stub area: stub and default-cost (OSPF Aera) If you want to configure one area as the stub area, you must configure all devices in the area by the stub command.
The default-cost (OSPF Aera) command takes effect only when it is configured on an ABR. The command is used to specify the cost of the default summary route transmitted by the ABR to the stub area.
On an ABR, you can configure the no-summary of the stub command to prevent Type 3 LSA from entering the stub area that the ABR connects to.
The backbone area cannot be configured as a stub area.
stub-router (OSPF)
Function
The stub-router command configures the stub router.
The undo stub-router command restores the default configuration.
By default, no device is configured as a stub router.
Parameters
Parameter | Description | Value |
---|---|---|
on-startup [ interval ] |
Specifies the interval during which a device acts as a stub router when the device is restarted or faulty.
|
The value is an integer that ranges from 5 to 65535, in seconds. By default, the value is 500 seconds. |
Usage Guidelines
Usage Scenario
After the stub-router command is configured on a device, the device informs other devices not to use this stub router to forward data by increasing the metric (65535) of the links in the LSA that is generated by the device. The metric is not infinite. Thus, the routes to this stub router still exist. The metric of the LSA links that is generated by the stub router is very high.
- If you run the stub-router command on a device without specifying on-startup, the router always functions as a stub device, and the cost of the routes from this device stays at 65535.
- If you run the stub-router on-startup command on a device, the device becomes a stub router after it restarts or a master/slave main control board switchover is performed and stays as a stub device for a period specified by interval. If interval is not specified, the default value (500s) takes effect.
suppress-flapping peer disable (OSPF)
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.
Usage Guidelines
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 LDP and 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.
vlink-peer (OSPF area)
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 for OSPF.
Format
vlink-peer router-id [ dead dead-interval | hello hello-interval | retransmit retransmit-interval | smart-discover | trans-delay trans-delay-interval | [ simple [ plain plain-text | [ cipher ] cipher-text ] | { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ] | authentication-null | keychain keychain-name ] ] *
undo vlink-peer router-id [ dead | hello | retransmit | smart-discover | trans-delay | [ simple | md5 | hmac-md5 | hmac-sha256 | authentication-null | keychain ] ] *
Parameters
Parameter | Description | Value |
---|---|---|
router-id |
Specifies the router ID of virtual link neighbor. |
- |
dead dead-interval |
Specifies the dead interval. This value must be equal to dead-interval of the Router that sets up a virtual link with the interface and must be at least 4 times that of hello-interval. |
The value is an integer that ranges from 1 to 235926000, in seconds. The default value is 40 seconds. |
hello hello-interval |
Specifies the interval for transmitting Hello packets on an interface. This value must be equal to hello-interval value of the Router that sets up a virtual link with the interface. The default value is 10 seconds. |
The value ranges from 1 to 65535 seconds. The default value is 10 seconds. |
retransmit retransmit-interval |
Specifies the interval for retransmitting the LSA packets on an interface. |
The value is an integer that ranges from 1 to 3600, in seconds. The default value is 5 seconds. |
smart-discover |
Automatically sends Hello packets |
- |
trans-delay trans-delay-interval |
Specifies the delay in transmitting LSA packets on an interface. |
The value is an integer that ranges from 1 to 3600, in seconds. The default value is 1 second. |
simple |
Indicates simple authentication. In simple authentication, the password type is cipher by default. NOTICE:
Simple authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
plain |
Indicates plain authentication. Only plain text can be entered, and plain text is displayed when the configuration file is viewed. NOTICE:
If plain is selected, the password is saved in the configuration file in plain text. This carries security risks. You are advised to select cipher to save the password in cipher text. |
- |
plain-text |
Specifies a plain text password. |
|
cipher |
Indicates cipher authentication. Either plain text or cipher text can be entered, and cipher text is displayed when the configuration file is viewed. |
- |
cipher-text |
Specifies a cipher text password. |
|
md5 |
Indicates MD5 authentication. In MD5 authentication, the password type is cipher by default. NOTICE:
MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-md5 |
Indicates HMAC-MD5 authentication. In HMAC-MD5 authentication, the password type is cipher by default. NOTICE:
HMAC-MD5 authentication carries potential risks. HMAC-SHA256 authentication is recommended. |
- |
hmac-sha256 |
Indicates HMAC-SHA256 authentication. In HMAC-SHA256 authentication, the password type is cipher by default. |
- |
key-id |
Specifies the authentication key ID of the interface's cipher authentication. The key ID must be consistent with that of the peer. |
The value is an integer that ranges from 1 to 255. |
authentication-null |
Indicates that no authentication is used. |
- |
keychain |
Indicates keychain authentication. NOTE:
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, OSPF authentication will fail. Currently, only the SM3, hmac-md5 and hmac-sha256 algorithms can be used for OSPF. |
- |
keychain-name |
Specifies the keychain name. |
The value is a string of 1 to 47 case-insensitive characters. Except the question mark (?) and space. However, when double quotation marks (") are used around the string, spaces are allowed in the string. |
Usage Guidelines
Usage Guidelines
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 be directly connected to the backbone area and devices within the backbone area stay connected. However, these requirements may not be met due to various limitations. OSPF virtual links can be configured to solve the problem.
Follow-up Procedure
After virtual links are established, devices provided by different vendors may use different default MTUs. To ensure consistent MTUs on the devices, run the undo ospf mtu-enable command to set the default MTU in DD packets sent by interfaces to 0.
Configuring the MTU in DD packets will cause the neighbor relationship to be re-established.
Precautions
When configuring parameters, pay attention to the following:
- A smaller hello value indicates faster detection of network topology changes and higher network resource usage.
- A too small retransmit value leads to unnecessary retransmission of LSAs. You are advised to set a large retransmit value on a low-speed network.
- The authentication mode of a virtual link must be the same as that in the backbone area.
vpn-instance-capability simple (OSPF)
Function
The vpn-instance-capability simple command directly calculates the route instead of conducting the routing loop detection.
The undo vpn-instance-capability command detects the DN bit to avoid the routing loops.
By default, the routing-loop check is enabled.
Usage Guidelines
Usage Scenario
If OSPF VPN multi-instance is deployed on a Multi-VPN-Instance CE (MCE), routes cannot be calculated based on Type3, Type5, or Type7 LSAs with the DN bit. Therefore, OSPF detects routing loops when calculating routes. In this case, the vpn-instance-capability simple command is used to disable OSPF routing loop detection and enable OSPF to calculate routes based on received LSAs without checking the DN bit and route-tag in the LSAs. The route-tag is restored to the default value 1.
Prerequisites
OSPF VPN multi-instance has been deployed on an MCE using the ospf process-id vpn-instance vpn-instance-name command.
Configuration Impact
If there is no ABR and the vpn-instance-capability simple command is run on an MCE, the MEC cannot become an ABR.
- After the vpn-instance-capability simple command is run in an OSPF process, the OSPF process will not import IBGP routes.
After the vpn-instance-capability simple command is run, OSPF routes that have been imported by BGP do not carry any OSPF domain ID, route tag, or router ID.
By default, when BGP imports an OSPF route, it uses the cost of the OSPF route plus 1 as the MED value. The MED in BGP is similar to the cost in an IGP in terms of functions. After the vpn-instance-capability simple command is run, BGP uses the cost of an OSPF route as the MED when it imports the OSPF route. Therefore, MED values change after the command is run, which may affect the route selection result.
Precautions
The undo vpn-instance-capability command cannot be used to enable OSPF routing loop detection in a scenario without MCEs.
Example
# Disable the OSPF routing-loop check.
<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
- Support for OSPF
- abr-summary (OSPF area)
- area (OSPF)
- asbr-summary
- authentication-mode (OSPF area)
- bandwidth-reference (OSPF)
- bfd all-interfaces (OSPF)
- default (OSPF)
- default-cost (OSPF Aera)
- default-route-advertise (OSPF)
- description (OSPF)
- description (OSPF Area)
- display default-parameter ospf
- display gtsm statistics
- display ospf abr-asbr
- display ospf asbr-summary
- display ospf bfd session
- display ospf brief
- display ospf cumulative
- display ospf error
- display ospf global-statistics
- display ospf graceful-restart
- display ospf interface
- display ospf lsdb
- display ospf migp-routing
- display ospf mesh-group
- display ospf nexthop
- display ospf peer
- display ospf request-queue
- display ospf retrans-queue
- display ospf routing
- display ospf sham-link
- display ospf spf-statistics
- display ospf statistics updated-lsa
- display ospf vlink
- display snmp-agent trap feature-name ospf all
- dn-bit-set
- dn-bit-check
- domain-id (OSPF)
- eca-route-type compatible
- enable log
- filter export (OSPF Area)
- filter import (OSPF Area)
- filter-lsa-out peer
- filter-policy export (OSPF)
- filter-policy import (OSPF)
- flooding-control
- frr (OSPF)
- frr-policy route (OSPF FRR)
- frr-priority static low
- graceful-restart (OSPF)
- graceful-restart helper-role (OSPF)
- gtsm default-action
- gtsm log drop-packet
- import-route (OSPF)
- local-mt filter-policy (OSPF)
- local-mt enable (OSPF)
- loop-free-alternate (OSPF FRR)
- lsa-arrival-interval
- lsa-originate-interval
- lsdb-overflow-limit
- maximum load-balancing (OSPF)
- maximum-routes
- mesh-group enable
- network (OSPF Area)
- nexthop (OSPF)
- nssa (OSPF Area)
- opaque-capability enable
- ospf
- ospf authentication-mode
- ospf bfd
- ospf bfd block
- ospf cost
- ospf dr-priority
- ospf enable
- ospf filter-lsa-out
- ospf frr block
- ospf maxage-lsa auto-protect disable
- ospf mib-binding
- ospf mtu-enable
- ospf network-type
- ospf p2mp-mask-ignore
- ospf router-id auto-recover disable
- ospf smart-discover
- ospf suppress-flapping peer
- ospf suppress-flapping peer disable
- ospf suppress-flapping peer hold-down
- ospf suppress-flapping peer hold-max-cost disable
- ospf timer dead
- ospf timer hello
- ospf timer poll
- ospf timer retransmit
- ospf trans-delay
- ospf valid-ttl-hops
- peer (OSPF)
- preference (OSPF)
- prefix-priority (OSPF)
- reset gtsm statistics
- reset ospf counters
- reset ospf process
- reset ospf redistribution
- reset ospf suppress-flapping peer
- retransmission-limit
- route-tag
- rfc1583 compatible
- sham-hello enable (OSPF)
- sham-link (OSPF Area)
- silent-interface (OSPF)
- snmp-agent trap enable feature-name ospf
- spf-schedule-interval
- stub (OSPF Area)
- stub-router (OSPF)
- suppress-flapping peer disable (OSPF)
- vlink-peer (OSPF area)
- vpn-instance-capability simple (OSPF)