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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 V800R010C10SPC500 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 Basic OSPFv3 Functions

Configuring Basic OSPFv3 Functions

To construct an OSPFv3 network, configure basic OSPFv3 functions first.

Usage Scenario

OSPFv3 functions take effect only after an OSPFv3 process, the router ID, the interface, and the area ID are specified.

OSPFv3 functions can be configured in the interface view, regardless of whether OSPFv3 is enabled. If OSPFv3 is disabled from the interface, OSPFv3 functions configured on this interface are still valid.

Pre-configuration Tasks

Before configuring basic OSPFv3 functions, complete the following tasks:

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

  • Enable IPv6.

Configuration Procedures

Figure 6-1 Flowchart for configuring basic OSPFv3 functions

Enabling OSPFv3

Creating an OSPFv3 process is a prerequisite for configuring OSPFv3 features. By creating an OSPFv3 process, you can specify the router ID for an OSPFv3 process.

Context

OSPFv3 supports multi-process. Multiple OSPFv3 processes running on one Device are differentiated by process IDs. You can set an OSPFv3 process ID when enabling OSPFv3. The process ID is only locally valid and does not affect the packet exchange with other Devices.

In the format of an IPv4 address, a router ID is a 32-bit unsigned integer that uniquely identifies one Device within an AS. The router ID of OSPFv3 must be set. Without a router ID, OSPFv3 cannot run properly.

When configuring the router ID, ensure that the router ID is unique in an AS. When multiple processes are enabled on the same Device, specify a unique router ID for each process.

Configure router IDs during network planning so that OSPFv3 can run properly.

Perform the following steps on the Device that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id] [vpn-instance vpn-instance-name]

    OSPFv3 is enabled, and the OSPFv3 view is displayed.

    The description of an OSPFv3 process helps identify special processes by the description command.

  3. Run router-id router-id

    A router ID is set.

    When configuring the router ID, ensure that the router ID is unique in an AS. You can select the IP address of an interface as the router ID.

    NOTE:

    Each router ID in an OSPFv3 process must be unique. Otherwise, routers cannot establish OSPFv3 neighbor relationships, and the routing information is incorrect.

    If a router ID conflict occurs, perform either of the following operations:

    • Reconfigure a router ID.
    • Run the undo ospfv3 router-id auto-recover disable command to enable the router ID automatic recovery function. After the function is enabled, the system automatically allocates a new router ID.
      NOTE:
      • If the automatic recovery function is enabled and a router ID conflict occurs between indirectly connected routers in one OSPFv3 area, the system replaces the conflicted router ID with a newly calculated one. The automatic recovery function takes effect on both configured and automatically generated router IDs.
      • The system can replace a router ID in a maximum of three attempts in case the router ID conflict persists.

  4. Run commit

    The configuration is committed.

Enabling OSPFv3 on an Interface

For an interface with multiple instances, you need to specify which instance on the interface is enabled in the OSPFv3 process when enabling OSPFv3 on the interface.

Context

After enabling OSPFv3 in the system view, you need to enable OSPFv3 on the interface.

Because an interface may have multiple instances, you need to specify which instance of the interface is enabled in the OSPFv3 process when OSPFv3 is enabled on the interface. If no instance ID is specified, the value defaults to 0. The same instance must be enabled on the interfaces between which the neighbor relationship is set up.

Perform the following steps on the ME device 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. (Optional) Run the ospfv3 network-type { broadcast | nbma | p2mp [ non-broadcast ] | p2p } [ instance instance-id ] command to configure the network type of an interface.

    When an interface supports multi-instance, specify instance-id when enabling OSPFv3 on the interface. If instance-id is not specified, the default value 0 is adopted. In this case, the configured network type of the interface is different from the actual network type. This step is mandatory in such a case.

  4. Run ospfv3 process-id area area-id [ instance instance-id ]

    OSPFv3 is enabled on the interface.

    The area ID can be a decimal integer or in the IPv4 address format, but it is displayed in the IPv4 address format.

  5. Run commit

    The configuration is committed.

Creating an OSPFv3 Area

After an AS is divided into different areas and OSPFv3 interfaces and areas to which these interfaces belong are specified, OSPFv3 can discover and calculate routes in the AS.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run area area-id

    The OSPFv3 area view is displayed.

    The area ID can be a decimal integer or in the IPv4 address format, but it is displayed in the IPv4 address format.

    The description of an OSPFv3 area helps identify special processes by the description command.

  4. Run commit

    The configuration is committed.

(Optional) Configuring the Maximum Number of Packet Retransmission Attempts

When no response to DD packets, Update packets, or Request packets is received, the retransmission mechanism is used and the maximum number of packet retransmission attempts is set to prevent dead loops caused by repeated transmissions.

Context

If no response is received when the maximum number of packet retransmission attempts is reached, the neighbor relationship will be interrupted.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run retransmission-limit [ max-number ]

    The maximum number of OSPFv3 packet retransmission attempts is set.

  4. Run commit

    The configuration is committed.

(Optional) Disabling an Interface from Receiving and Sending OSPFv3 Packets

Context

To prevent OSPFv3 routes from being received by other routers on the network and disable the local router from receiving updated routes, you can disable the local router's interface from receiving and sending OSPFv3 packets. After an interface is disabled from receiving and sending OSPFv3 packets, the interface can still advertise its routes but cannot exchange Hello packets with others. Therefore, no neighbor relationship can be established between the interface and others. This can enhance the networking adaptability of OSPFv3 and reduce system resource consumption.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 process view is displayed.

  3. Run silent-interface interface-type interface-number

    An interface is disabled from receiving and sending OSPFv3 packets.

    NOTE:

    The same interface in different processes can be disabled from sending and receiving OSPFv3 packets, but the silent-interface command is valid only for the OSPFv3 interface in the local process.

  4. Run commit

    The configuration is committed.

Verifying the Basic OSPFv3 Configuration

After configuring basic OSPFv3 functions, verify information about neighbors, interfaces, and the OSPFv3 routing table.

Prerequisites

Basic OSPFv3 functions have been configured.

Procedure

  • Run the display ospfv3 [ process-id ] [ area area-id ] peer [ interface-type interface-number ] [ verbose ] command in any view to view information about OSPFv3 neighbors.
  • Run the display ospfv3 [ process-id ] [ area area-id ] [ interface-type interface-number ] command in any view to view information about an OSPFv3 interface.
  • Run the display ospfv3 [ process-id ] routing command in any view to view information about an OSPFv3 routing table.
  • Run the display ospfv3 [ process-id ] cumulative command in any view to view OSPFv3 statistics.
  • Run the display ospfv3 [ process-id ] error [ lsa | interface interface-type interface-number ] command in any view to view OSPFv3 errors.
  • Run the display ospfv3 [ process-id ] next-hop command in any view to view the OSPFv3 next-hop routing table.
  • Run the display ospfv3 [ process-id ] request-list [ statistics | [ area area-id | peer router-id | interface interface-type interface-number ] * ] command in any view to view the statistics of the request list of OSPFv3.
  • Run the display ospfv3 [ process-id ] retrans-list [ statistics | { area area-id | peer router-id | interface interface-type interface-number } * ] command in any view to view the statistics of the OSPFv3 retransmission list.
  • Run the display ospfv3 [ process-id ] spf-statistics [ verbose ] command in any view to view OSPFv3 route calculation statistics.
  • Run the display ospfv3 [ process-id ] statistics updated-lsa [ originate-router advertising-router-id | history ] command in any view to view the frequent updates of the Link State Advertisements (LSAs) that the Link-state Database (LSDB) receives.
  • Run the display ospfv3 [ process-id ] topology [ area area-id ] [ statistics | verbose ] command in any view to view information about the topology in an OSPFv3 area.

Example

Run the display ospfv3 peer command to view the router ID, interface priority, and interface status on the OSPF neighbor.

<HUAWEI> display ospfv3 peer
OSPFv3 Process (1)
OSPFv3 Area (0.0.0.0)
Neighbor ID     Pri   State           Dead Time   Interface     Instance ID
1.1.1.1           1   Full/ -         00:00:30    GE1/0/0            0

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

<HUAWEI> display ospfv3 interface gigabitethernet 1/0/0
GE1/0/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 routing command, and you can view the destination addresses, link costs, and next hops of OSPFv3 routes. For example:

<HUAWEI> display ospfv3 routing
 Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area
 OSPFv3 Process (1)
   Destination                                Metric
     Nexthop
   2000:1::/64                                 3124
     via FE80::1441:0:E213:1, GigabitEthernet1/0/0
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20677

Downloads: 15

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