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 Attributes on Different Types of Networks

Configuring OSPFv3 Attributes on Different Types of Networks

By setting network types for OSPFv3 interfaces and adjusting OSPFv3 attributes, you can build OSPFv3 networks flexibly.

Usage Scenario

Based on the types of link layer protocols, OSPFv3 classifies networks into the following types:
  • P2MP: Because P2MP is not a link layer protocol, each P2MP network is changed from a network of another type.
  • NBMA: If the link layer protocol is X.25, OSPFv3 defaults the network type to NBMA.
  • Broadcast: If the link layer protocol is GigabitEthernet or FDDI, OSPFv3 defaults the network type to broadcast.
  • P2P: If the link layer protocol is PPP, or LAPB, OSPFv3 defaults the network type to P2P.

You can change network types and configure OSPFv3 attributes to flexibly build networks without changing link layer protocols.

Pre-configuration Tasks

Before configuring OSPFv3 attributes on different types of networks, 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

Figure 6-2 Flowchart for configuring OSPFv3 attributes on different types of networks

Configuring the Network Type for an OSPFv3 Interface

OSPFv3 classifies networks into broadcast, P2P, P2MP, and NBMA networks based on link layer protocols. By configuring network types for interfaces, you can change the network types of interfaces.

Context

By default, the network type of an interface depends on the physical interface. The network type of an Ethernet interface is broadcast, the network type of a serial interface is p2p.

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 network-type { broadcast | nbma | p2mp [ non-broadcast ] | p2p } [ instance instance-id ]

    The network type is configured for the OSPFv3 interface.

    NOTE:

    The network types of two OSPFv3 interfaces at both ends of a link must be identical. Otherwise, the OSPFv3 neighbor relationship cannot be established.

  4. Run commit

    The configuration is committed.

(Optional) Setting the DR Priority for the OSPFv3 Broadcast or NBMA Interface

You can specify the Designated Router (DR) priority for each interface on a broadcast or a non-broadcast multiple access (NBMA) network for DR/Backup Designated Router (BDR) election on the network.

Context

When configuring broadcast networks or NBMA networks, you can specify the DR priority for each interface for DR/BDR election on the network. The greater the value, the higher the priority.

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 dr-priority priority [ instance instance-id ]

    The DR priority of the OSPFv3 interface is set.

  4. (Optional) Run ospfv3 timer wait interval [ instance instance-id ]

    The wait timer on an OSPFv3 interface is set.

    If no Backup Seen event is received within the interval, the designated router (DR) election starts. Setting a proper value for the wait timer can slow down changes of the DR and the backup designated router (BDR) on the network, reducing network flapping. When setting the wait timer, note the following points:

    • The wait timer takes effect only on broadcast and NBMA interfaces.
    • The value of the wait timer cannot be greater than the value of the dead timer.

  5. Run commit

    The configuration is committed.

Follow-up Procedure

Changing the priority leads to a DR/BDR re-election and interrupts the OSPFv3 adjacency between NEs. Therefore, changing the priority is not recommended.

Reconfiguring the DR priority for an interface does not change the DR or BDR on the network. To reelect a DR or BDR, perform either of the following operations.

  • Restart the OSPFv3 processes on all the NEs.

  • Run the shutdown and then undo shutdown commands on the interfaces where neighbor relationships are established.

(Optional) Setting the Polling Interval at Which Hello Packets Are Sent on an NBMA Network

On an NBMA network, a device sends Hello packets to a neighbor that is Down at a polling interval.

Context

Perform the following steps on the NE running OSPFv3.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The OSPFv3 interface view is displayed.

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

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

    The parameter poll interval specifies the polling interval at which Hello packets are sent.

  4. Run commit

    The configuration is committed.

(Optional) Disabling MTU Check on DD Packets

After you prevent an interface from checking the Maximum Transmission Unit (MTU) field in received Database Description (DD) packets, the device can receive packets with the MTU field as 0.

Context

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 mtu-ignore [ instance instance-id ]

    The MTU check on DD packets is disabled.

    After the command is used, the interface does not check the MTU field of received DD packets.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of OSPFv3 Attributes in Different Types of Networks

After configuring attributes of OSPFv3 interfaces on different types of networks, verify information about OSPFv3 interfaces.

Prerequisites

OSPFv3 interface attributes on different types of networks have been configured.

Procedure

  1. Run the display ospfv3 [ process-id ] interface [ no-peer | area area-id ] [ interface-type interface-number ] command in any view to view information about an OSPFv3 interface.

Example

Run the display ospfv3 interface command to view the network types of OSPFv3 interfaces.

<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
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 34913

Downloads: 51

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