No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - IP Routing
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring OSPFv3 Fast Convergence

Configuring OSPFv3 Fast Convergence

By adjusting OSPFv3 timers, you can implement OSPF fast network convergence.

Pre-configuration Tasks

Before configuring OSPFv3 fast convergence, complete the following tasks:

  • Configure a link layer protocol.

  • Configure IPv6 addresses for interfaces to ensure that neighboring nodes are reachable at the network layer.

  • Configure basic OSPFv3 functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Setting the Interval at Which Hello Packets Are Sent

You can adjust the value of the Hello timer to change the speed of OSPFv3 neighbor relationship establishment and the network convergence speed.

Context

Hello packets are periodically sent to the neighbor NE to detect and maintain the neighbor relationship and to elect the DR and the BDR. Based on standard protocols, the Hello timer values of neighbors must be the same. The value of the Hello timer is inversely proportional to the route convergence speed and network load.

Perform the following steps on the NE that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run ospfv3 timer hello interval [ conservative ] [ instance instance-id ]

    The interval at which Hello packets are sent is set on the interface.

    If the conservative parameter is specified in the command, the conservative mode is configured for the dead timer. If the conservative mode is configured, the value configured for the dead timer using the ospfv3 timer dead command takes effect even when the value is less than 10s.

    To speed up OSPFv3 convergence in the case of a link failure, configuring BFD For OSPFv3 is recommended. If the remote end does not support BFD for OSPFv3 or you do not want to configure BFD for OSPFv3, specify conservative when you run the ospfv3 timer hello command. If the conservative mode is configured, the value configured for the dead timer using the ospfv3 timer dead command takes effect even when the value is less than 10s; if the value configured for the dead timer is greater than 10s, services may be affected.

    NOTE:
    The interval must be longer than the time a device takes to perform a master/slave main control board switchover. If the timer is set to less than the switchover time, a protocol intermittent interruption occurs during a switchover. The default timer value is recommended.

  4. Run commit

    The configuration is committed.

Setting the Dead Time of the Neighbor Relationship

If a device does not receive a Hello packet from its neighbor within the dead interval, the device considers the neighbor Down.

Context

Perform the following steps on the OSPFv3 router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run ospfv3 timer dead interval [ instance instance-id ]

    The dead interval is set for the neighbor relationship.

    By default, the dead time of the neighbor relationship on the same interface is four times the interval at which Hello packets are sent.

    NOTE:

    If the dead interval of an OSPFv3 neighbor is shorter than 10s, the session may be closed. Therefore, if dead interval is shorter than 10s, the actual dead interval of an OSPFv3 neighbor is not shorter than 10s. If the conservative mode is configured using the ospfv3 timer hello command, the configured dead timer takes effect even when its value is less than 10s.

  4. Run commit

    The configuration is committed.

Configuring OSPFv3 Sham Hello

With OSPFv3 sham hello, device can exchange Hello and LSU and LSAck packets to maintain OSPFv3 neighbor relationships, which strengthens the neighbor detection mechanism.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 process view is displayed.

  3. Run sham-hello enable

    OSPFv3 sham hello is enabled.

  4. Run commit

    The configuration is committed.

Setting the Interval at Which LSAs Are Updated

You can set the interval at which LSAs are updated based on network connections and router resources.

Context

On a stable network that requires fast route convergence, intelligent-timer needs to be specified in the lsa-originate-interval command to enable an intelligent timer to update OSPFv3 LSAs so that topology changes or route changes can be immediately advertised to the network through LSAs, which speeding up route convergence. This prevents too many network bandwidth and device resources from being consumed due to network connection changes or frequent route flapping.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 process view is displayed.

  3. Run lsa-originate-interval { 0 | intelligent-timer max-interval start-interval hold-interval [ other-type interval ] | other-type interval [ intelligent-timer max-interval start-interval hold-interval ] }

    An intelligent timer is enabled to update OSPFv3 LSAs.

    By default, the intelligent timer is enabled; the maximum interval at which LSAs are updated is 5000 ms, the initial interval is 500 ms, and the holding interval is 1000 ms.

  4. (Optional) Run lsa-originate-interval suppress-flapping suppress-interval [ threshold count ]

    The suppression period that takes effect when the OSPFv3 LSAs to be sent flap is configured.

    If no flapping occurs among the OSPFv3 LSAs to be sent, the configuration of the lsa-originate-interval command prevents the device from frequently sending LSAs. If the OSPFv3 LSAs to be sent flap, the configuration of the lsa-originate-interval suppress-flapping command minimizes the impact of the flapping on services. The larger value of the two intervals specified in the commands is used as the suppression period.

  5. Run commit

    The configuration is committed.

Setting the Interval at Which LSAs Are Received

You can set the interval at which LSAs are received based on network connections and router resources.

Context

To prevent excessive network resource consumption due to frequent network changes, you can run the lsa-arrival-interval command to configure an interval at which OSPFv3 LSAs are received.

On a stable network that requires fast route convergence, you can change the interval at which OSPFv3 LSAs are received to 0s. In this manner, the device can fast respond to topology or route changes, which speeds up route convergence.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 process view is displayed.

  3. Run lsa-arrival-interval { interval | intelligent-timer max-interval start-interval hold-interval }

    The interval at which LSAs are received is configured.

    By default, an intelligent timer is enabled. The maximum interval at which OSPFv3 LSAs are received is 10000 ms, the initial interval is 500 ms, and the Holdtime interval is 500 ms.

  4. (Optional) Run lsa-arrival-interval suppress-flapping suppress-interval [ threshold count ]

    The suppression period that takes effect when received OSPFv3 LSAs flap is configured.

    If no flapping occurs among received OSPFv3 LSAs, the configuration of the lsa-arrival-interval command prevents the device from frequently receiving LSAs. If received OSPFv3 LSAs flap, the configuration of the lsa-arrival-interval suppress-flapping command minimizes the impact of the flapping on services. The larger value of the two intervals specified in the commands is used as the suppression period.

  5. Run commit

    The configuration is committed.

Disabling OSPFv3 LSA Aging Management

By default, the OSPFv3 LSA aging management function is enabled. To disable this function, perform this task.

Context

If an exception occurs in the age field of LSAs, LSAs may be aged unexpectedly, causing LSA flapping or a route calculation error. For example, if the abnormal aging time is 2500s and the actual aging time is 500s, LSAs are aged prematurely. To address this problem, OSPFv3 LSA aging management is enabled by default. If the aging time in a received LSA is greater than 1800s, OSPFv3 considers the LSA abnormal and changes the aging time to 1700s until the aging time values of all LSAs in the area become the same. In this case, routes can be calculated correctly.

By default, the OSPFv3 LSA aging management function is enabled. To disable this function, run the lsa-age refresh disable command.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run lsa-age refresh disable

    OSPFv3 LSA aging management is disabled.

  3. Run commit

    The configuration is committed.

Verifying the Configuration of OSPFv3 Fast Convergence

After configuring OSPFv3 fast convergence, verify brief information about OSPFv3.

Prerequisites

OSPFv3 fast convergence has been configured.

Procedure

  • Run the display ospfv3 [ process-id ] interface [ area area-id ] [ interface-type interface-number ] command in any view to view information about an OSPFv3 interface.
  • Run the display ospfv3 [ process-id ] command to check brief OSPFv3 information.

Example

Run the display ospfv3 interface command to view detailed information about OSPFv3 timers.

<HUAWEI> display ospfv3 interface
GE0/1/0 is up, line protocol is up
  Interface ID 0x102
  IPv6 Prefixes
    FE80::2E0:FFF:FE4E:F101 (Link-Local Address)
    2000::1/64
  OSPFv3 Process (1), Area 0.0.0.1, Instance ID 0
    Router ID 1.1.1.1, Network Type BROADCAST, Cost: 1
    Transmit Delay is 1 sec, State Full, Priority 1
    No designated router on this link
    No backup designated router on this link
    Timer interval configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:02
    Neighbor Count is 0, Adjacent neighbor count is 0

Run the display ospfv3 command to view brief information about OSPFv3 timers.

<HUAWEI> display ospfv3
 Routing Process "OSPFv3 (1)" with ID 0.0.0.0
 Route Tag: 0
 Multi-VPN-Instance is not enabled
 SPF Intelligent Timer[millisecs] Max: 10000, Start: 500, Hold: 1000
 For router-LSA and network-LSA:
  LSA Originate Intelligent Timer[millisecs] Max: 5000, Start: 500, Hold: 1000
 For other LSAs:
  LSA Originate Interval 5 seconds
  LSA Arrival Intelligent Timer[millisecs] Max: 1000, Start: 500, Hold: 500
 Default ASE parameters: Metric: 1 Tag: 1 Type: 2
 Number of AS-External LSA 0. AS-External LSA's Checksum Sum 0x0
 Number of AS-Scoped Unknown LSA 0. AS-Scoped Unknown LSA's Checksum Sum 0x0
 Number of FULL neighbors 0
 Number of Exchange and Loading neighbors 0
 Maximum ASE LS ID 1 and Unused list Count 0
 Number of LSA originated 0
 Number of LSA received 0
 SPF Count          : 0
 Non Refresh LSA    : 0
 Non Full Nbr Count : 0
 Number of areas in this router is 1
 Authentication : HMAC-SHA256
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 35422

Downloads: 51

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next