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


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


Configuration Guide - IP Unicast Routing

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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 Network Types of OSPF Interfaces

Configuring Network Types of OSPF Interfaces


You can configure one of the following network types for an interface as required:
  • P2MP: OSPF does not default any network to a P2MP network regardless of its link layer protocol. Therefore, a P2MP network must be forcibly changed from another network type.

  • NBMA: An NBMA network must be fully meshed. That is, any two switches on an NBMA network must be directly reachable. However, it is not true in most cases. In such a case, you need to forcibly change the network type using commands.

  • Broadcast: To speed up establishment of neighbor relationships, you can change the network type from broadcast to P2P.


  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The OSPF interface view is displayed.

  3. On an Ethernet interface, run undo portswitch

    The interface is switched to Layer 3 mode.

    By default, an Ethernet interface works in Layer 2 mode.

    The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.


    If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

  4. Run ospf network-type { broadcast | nbma | p2mp | p2p [ peer-ip-ignore ] }

    The network type of the OSPF interface is configured.

    By default, the network type of an interface depends on the physical interface. For example, the network type of an Ethernet interface is broadcast.

    Configuring a new network type for an interface will cause the OSPF session on the interface to be reestablished.


    Generally, the network types of OSPF interfaces on both ends of a link must be the same. Otherwise, route calculation errors occur.

  5. Run commit

    The configuration is committed.

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 274552

Downloads: 161

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next