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 OSPF on the NBMA or P2MP Network

Configuring OSPF on the NBMA or P2MP Network

This section describes how to configure OSPF and modify attributes on the NBMA or point-to-multipoint (P2MP) network to flexibly construct the OSPF network.

Applicable Environment

As shown in Table 5-2, OSPF classifies networks into four types based on the types of link layer protocols.
NOTE:
Differentiated OSPF configurations that are applicable to the NBMA network and P2MP network are provided in this section. The OSPF configurations not provided here are applicable to the four types of networks.
Table 5-2 Network types supported by OSPF

Network Type

Characteristic

Default Configuration

Broadcast

On the broadcast network, Hello packets, LSU packets, and LSAck packets are multicasted; DD packets and LSR packets are unicasted.

If the link layer protocol is Ethernet or Fiber Distributed Data Interface (FDDI), OSPF regards the network as a broadcast network by default.

Non-broadcast multiple access (NBMA)

On an NBMA network, Hello packets, DD packets, LSR packets, LSU packets, and LSAck packets are unicasted.

The NBMA network must be fully meshed. Any two NEs on the NBMA network must be directly reachable.

If the link layer protocol is ATM, OSPF regards the network as an NBMA network by default.

Point-to-point (P2P)

On a P2P network, Hello packets, DD packets, LSR packets, LSU packets, and LSAck packets are multicasted.

If the link layer protocol is PPP, or Link Access Procedure Balanced (LAPB), OSPF regards the network as a P2P network by default.

Point-to-multipoint (P2MP)

On a P2MP network, Hello packets are multicasted; DD packets, LSR packets, LSU packets, and LSAck packets are unicasted.

The mask lengths of the NEs on the P2MP network must be the same.

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.

As shown in Table 5-2, OSPF sends packets in different manners on networks of different types. Therefore, the difference between OSPF configurations on the networks lies in the packet sending configurations.

Pre-configuration Tasks

Before configuring session parameters for the OSPF neighbor or adjacency relationship, complete the following tasks:

  • Configuring a link layer protocol

  • Configuring IP addresses for interfaces to ensure that neighboring nodes are reachable at the network layer

  • Configuring Basic OSPF Functions

Configuration Procedures

You can choose one or several configuration tasks (excluding "Checking the Configuration") as required.

Configuring Network Types for OSPF Interfaces

OSPF classifies networks into four types based on the types of link layer protocols. You can configure the network type for an OSPF interface to forcibly change its original network type.

Context

The network types of the interfaces on both ends of a link must be the same; otherwise, the OSPF neighbor relationship cannot be established.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

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

    The network type of the OSPF interface is configured.

    When the network type is configured for an interface, the original network type of the interface is replaced.

    The network type can be configured based on the real world situations.
    • On an interface with the broadcast network type, if a router that does not support the multicast address exists, change the network type of the interface to NBMA.
    • On an interface with the NBMA network type, if the network is fully meshed or any two routers are directly connected, change the network type of the interface to broadcast and do not configure neighboring router information on the interface.
    • On an interface with the NBMA network type, if the network is not fully meshed, change the network type of the interface to P2MP. After that, two indirectly connected routers can communicate through one router that can directly reach both the two routers. After the network type of the interface is changed to P2MP, configuring neighboring router information on the interface is unnecessary.
    • If only two routers run OSPF on the same network segment, changing the network type of the interface to P2P is recommended.

    peer-ip-ignore is used to disable 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.

    NOTE:
    OSPF cannot be configured on a null interface.

  4. Run commit

    The configuration is committed.

Configuring NBMA Network Attributes

To implement OSPF functions, configure NBMA network attributes.

Procedure

  1. (Optional) Set the network type to NBMA.

    The NBMA network must be fully meshed. Any two NEs on the NBMA network must be directly reachable. In most cases, however, this requirement cannot be met. To resolve this problem, run specific commands to forcibly change the network type to NBMA. For details, see Configuring Network Types for OSPF Interfaces.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run ospf network-type nbma

      The network type of the OSPF interface is set to NBMA.

    4. Run commit

      The configuration is committed.

  2. (Optional) Run ospf timer poll interval

    The interval at which Hello packets for polling are sent by an NBMA interface is set.

    On the NBMA network, after the neighbor relationship becomes invalid, the NE sends Hello packets at an interval defined in the polling mechanism.

    The default value is 120, in seconds.

  3. (Optional) Run ospf dr-priority priority

    Sets the priority of an interface that runs for the DR or BDR.

    The priority of an interface determines whether the interface is qualified to be a DR or BDR. The interface with the highest priority is elected as the DR or BDR. If the priority of an interface on a device is 0, the device cannot be elected as a DR or BDR. On a broadcast or an NBMA network, you can set the priority of an interface to control the DR or BDR selection. 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.

  4. (Optional) Run ospf timer wait interval

    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. Configure a neighboring NE on the NBMA network.

    The interface with the network type of NBMA cannot broadcast Hello packets to discover neighboring NEs. Therefore, the IP address of a neighboring NE must be configured on the process and whether the neighboring NE can participate in DR election must be determined on the process.

    1. Run quit

      Exit from the interface view.

    2. Run ospf [ process-id ]

      The OSPF process view is displayed.

    3. Run peer ip-address [ dr-priority priority ]

      A neighboring NE is configured.

    4. Run commit

      The configuration is committed.

  6. Run commit

    The configuration is committed.

Configuring P2MP Network Attributes

To implement OSPF functions, configure P2MP network attributes.

Procedure

  1. Disable OSPF from checking the network mask.

    The OSPF neighbor relationship cannot be established between the devices with different mask lengths on the P2MP network. After OSPF is disabled from checking the network mask, the OSPF neighbor relationship can be properly established.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run ospf network-type p2mp

      The network type of the OSPF interface is configured.

      A P2MP network is forcibly changed from another other type of network. For details, see Configuring Network Types for OSPF Interfaces.

    4. Run ospf p2mp-mask-ignore

      OSPF is disabled from checking the network mask on the P2MP network.

    5. Run commit

      The configuration is committed.

  2. (Optional) Configure the device to filter the LSA packets to be sent.

    When multiple links exist between two devices, you can configure the local device to filter the LSA packets to be sent. This can reduce unnecessary LSA retransmission attempts and save bandwidth resources.

    1. Run system-view

      The system view is displayed.

    2. Run ospf [ process-id ]

      The OSPF process view is displayed.

    3. Based on the basic ACL:

      1. Run 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 } ] } * }

        The local NE is configured to filter the LSA packets to be sent on the P2MP network.

      2. Run quit

        Return to the system view.

      3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

        The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] *

        The rule for the basic ACL is configured.

        When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.

        When a filtering policy of a routing protocol is used to filter routes:
        • If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.

        • If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.

        • If a route has not matched any ACL rules, the route will not be received or advertised by the system.

        • If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.

        • If the ACL referenced by the route-policy does not exist, all routes matching the route-policy will be received or advertised by the system.

        • In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:

          Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.

          Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.

    4. Run commit

      The configuration is committed.

Verifying the Configuration of OSPF on the NBMA or P2MP Network

After OSPF attributes are set on networks of different types, you can check OSPF neighbor and interface information.

Prerequisites

OSPF attributes have been configured on networks of different types.

Procedure

  • Run the display ospf [ process-id ] interface [ all | no-peer | interface-type interface-number ] [ verbose ] command to check information about OSPF interfaces.
  • Run the display ospf [ process-id ] peer command to check information about OSPF neighbors.
  • Run the display ospf brief command to check the interval at which Hello packets are sent on an NBMA network.

Example

Run the display ospf interface command to view the network types and status of OSPF interfaces.

<HUAWEI> display ospf interface
          OSPF Process 1 with Router ID 1.1.1.1
                  
 Area: 0.0.0.0               MPLS TE not enabled
 Interface                IP Address      Type      State    Cost    Pri
 GigabitEthernet0/1/0     192.168.1.1     P2P       P-2-P    1       100

Run the display ospf peer command to view information about OSPF neighbors, including the IP address, interface priority, and the DR or BDR.

<HUAWEI> display ospf peer
          OSPF Process 1 with Router ID 1.1.1.1
                Neighbors

 Area 0.0.0.0 interface 192.168.1.1 ( GE0/3/0 )'s neighbors
 Router ID: 2.2.2.2         Address: 192.168.1.2
   State: Full       Mode:Nbr is  Slave   Priority: 1
   DR: 192.168.1.4   BDR: 192.168.1.3     MTU: 0
   Dead timer due in  32  sec
   Retrans timer interval: 0
   Neighbor is up for
   Authentication Sequence: [ 0 ]

Run the display ospf brief command to view the interval at which Hello packets are sent on an NBMA network.

<HUAWEI> display ospf brief
          OSPF Process 1 with Router ID 9.9.9.9
                  OSPF Protocol Information
RouterID: 9.9.9.9          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 
OSPF Stub Router State Reason: Startup Synchronize
    Router LSA stub links with cost 65535
    Summary LSA with cost 16777214 
    External LSA with cost 16777214 
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 
Intra Route Preference: 50 
Inter Route Preference: 50 
SPF Computation Count: 56 
RFC 1583 Compatible
OSPF is in LSDB overflow status(remain time: 205s)
Retransmission limitation is disabled
Import routes limitation is enabled
  Self ASE LSA count: 8
  Current status: Normal
bfd enabled
BFD Timers: Tx-Interval 10 , Rx-Interval 10 , Multiplier 3 
Area Count: 2   Nssa Area Count: 1 
ExChange/Loading Neighbors: 0

 Area: 0.0.0.0             (MPLS TE not enabled)
 Authtype: None   Area flag: Normal
 SPF scheduled count: 2
 Exchange/Loading neighbors: 0
 Router ID conflict state: Normal

 Interface: 1.1.1.1 (GE0/3/0)
 Cost: 1       State: DR      Type: Broadcast      MTU: 1500
 Priority: 1
 Designated Router: 1.1.1.1
 Backup Designated Router: 0.0.0.0
 Timers: Hello 10, Dead 40, Wait 40, Poll 120, Retransmit 5, Transmit Delay 1

 Area: 0.0.0.1             (MPLS TE not enabled)
 Authtype: None   Area flag: NSSA
 SPF scheduled count: 1
 Exchange/Loading neighbors: 0
 NSSA Translator State: Elected
 Router ID conflict state: Normal
 Import routes limitation is enabled
  Self NSSA LSA count: 2
  Current status: Normal

 Interface: 1.1.1.1 (GE0/2/0)
 Cost: 1       State: P-2-P   Type: P2P      MTU: 1500
 Timers: Hello 10, Dead 40, Wait 40, Poll 120, Retransmit 5, Transmit Delay 1
 Multi-area interface
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 34108

Downloads: 49

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