Configure OSPFv3 Network Optimization

Configuration Condition

Before configuring OSPFv3 network optimization, ensure that:

• The IPv6 forwarding function is enabled.
• The OSPFv3 protocol is enabled.

Configure the Keep-alive Time of an OSPFv3 Neighbor

OSPFv3 Hello packets are used to set up neighbor relations and keep the relations alive. The default transmission interval of Hello packets is determined by the network type. For broadcast networks and P2P networks, the default transmission interval of Hello packets is 10s. For P2MP networks and NBMA networks, the default transmission interval of Hello packets is 30s.

Neighbor dead time is used to determine the validity of a neighbor. By default, the neighbor dead time is four times the Hello interval. If an OSPFv3 device fails to receive Hello packets from a neighbor after the neighbor dead time times out, the OSPFv3 device regards the neighbor as invalid, and then it deletes the neighbor in an active manner.

Table 8-23 Configure the keep-alive time of an OSPFv3 neighbor

• ---

  The Hello interval and neighbor dead time of OSPFv3 neighbors must be the same; otherwise, they cannot set up neighbor relations.
• When you modify the Hello interval, if the current neighbor dead time is four times of the Hello interval, the neighbor dead time is automatically modified to be still four times of the new Hello interval. If the current neighbor dead time is not four times of the Hello interval, the neighbor dead time keeps unchanged.
• If you modify the neighbor dead time, the Hello interval is not affected.

  ---

Configure an OSPFv3 Passive Interface

The dynamic routing protocol adopts a passive interface to effectively decrease the network bandwidth consumed by the routing protocol. After an OSPFv3 passive interface is configured, you can use the enable command of the interface to advertise the routes of the directly connected network segment in which the interface is located, but the receiving and transmitting of OSPFv3 packets are damped on the interface.

Table 8-24 Configure an OSPFv3 passive interface

Configure an OSPFv3 Demand Circuit

On P2P and P2MP links, to decrease the line cost, you can configure an OSPFv3 demand circuit to suppress periodical transmitting of Hello packets and periodical update of LSA packets. This function is mainly applied on charged links such as ISDN, SVC, and X.25.

Table 8-25 Configure an OSPFv3 demand circuit

Configure the Priority of an OSPFv3 Interface

Interface priorities are mainly used in election of Designated Router (DR), and Backup Designated Router (BDR) in broadcast networks and NBMA networks. The value range is 0-255. The larger the value is, the higher the priority is. The default value is 1.

The DR and BDR are selected from all devices in a network segment based on interface priorities and Router IDs through Hello packets. The rules are as follows:

• First, the device whose interface has the highest priority is elected as the DR, and the device whose interface has the second highest priority is elected as the BDR. The device whose interface has the priority 0 does not participate in the election.
• If the interface priorities of two devices are the same, the device with the largest Router ID is elected as the DR, and the device with the second largest Router ID is elected as the BDR.
• If the DR fails, the BDR becomes the DR immediately, and a new BDR is elected.

Table 8-26 Configure the priority of an OSPFv3 interface

• ---

  Interface priorities affect only an election process. If the DR and BDR have already been elected, modification of interface priorities does not affect the election result; instead, it affects the next election of DR or BDR. Therefore, the DR may not have the interface with the highest priority, and the BDR may not have the interface with the second highest priority.

  ---

Configure the OSPFv3 Interface to Ignore MTU

When adjacent OSPF devices exchange DD packets, MTUs are checked by default. If the MTUs are different, the devices cannot form a neighbor relation. If you have configured OSPFv3 to ignore interface MTU check, even if MTUs are different, they can set up a neighbor relation.

Table 8-27 Configure an OSPFv3 interface to ignore MTU

Configure the LSA Transmit Delay of an OSPFv3 Interface

LSA transmit delay refers to the time it takes for an LSA to flood to other devices. The device that sends the LSA adds the interface transmit delay to the LSA aging time. By default, once the flooding LSA passes a device, the aging time is increased by 1. You can configure the LSA transmit delay according to the network conditions. The value range is 1-840. LSA transmit delay is usually configured on low-speed links.

Table 8-28 Configure the LSA transmit delay of an OSPFv3 interface

Configure OSPFv3 LSA Retransmission

To ensure the reliability of data exchange, OSPFv3 adopts the acknowledgement mechanism. If an LSA floods on a device interface, the LSA is added into the retransmission list of the neighbor. If no acknowledgement message is received from the neighbor after the retransmission time times out, the LSA is retransmitted until an acknowledgement message is received.

Table 8-29 Configure OSPFv3 LSA retransmission

Configure OSPFv3 SPF Calculation Time

If the OSPFv3 network topology changes, routes need to be re-calculated. When the network continues to change, frequent route calculation occupies a lot of system resources. You can adjust the SPF calculation time parameters to prevent frequent network changes from consuming too many system resources.

Table 8-30 Configure OSPFv3 SPF calculation time

• ---

  The parameter delay-time indicates the initial calculation delay, hold-time indicates the suppression time, and max-time indicates the maximum waiting time between two SPF calculations. If network changes are not frequent, you can shorten the continuous route calculation interval to delay-time. If network changes are frequent, you can adjust the parameters, increase the suppression time to hold-time×2n-2 (n is the number of route calculation trigger times), extend the waiting time based on the configured hold-time increment and the maximum value must not exceed max-time.

  ---