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 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
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).
OSPFv3 Troubleshooting

OSPFv3 Troubleshooting

This chapter describes common OSPFv3 faults and provides troubleshooting procedures and troubleshooting cases.

For details about OSPFv3, see the HUAWEI ME60 Feature Description - OSPFv3.

The OSPFv3 Neighbor Relationship Is Down

This section describes how to troubleshoot the fault that the OSPFv3 neighbor relationship is Down.

Common Causes

Common causes are as follows:

  • The BFD is faulty.
  • The remote device is faulty.
  • The CPU usage on the interface board of the faulty device is too high.
  • The link is faulty.
  • The interface is not Up.
  • The IP addresses of the two devices at both ends are on different network segments.
  • The router IDs of the two devices conflict.
  • The area types of the two devices are inconsistent.
  • OSPF parameter configurations of the two devices are inconsistent.
Troubleshooting Flowchart

Figure 4-60 shows the troubleshooting flowchart.

Figure 4-60 Troubleshooting flowchart for the fault that the OSPFv3 neighbor relationship is Down

Troubleshooting Procedure

Context

NOTE:

Commands can be run in one of two modes: immediate validation mode or two-phase validation mode.

  • In immediate validation mode, the configurations take effect immediately after a command is run.
  • In two-phase validation mode, the configurations do not take effect until after the commit command is run.

Unless otherwise specified, this troubleshooting guide defaults to the immediate validation mode.

Save the results of each troubleshooting step. If the fault persists after following this procedure, Huawei will need these results for further troubleshooting.

Procedure

  1. Check that the link between the two devices is normal.

    Run the ping command and the display this interface command in the interface view to check whether the link between the two devices is normal and whether the transmission devices are normal. If the link is normal, go to Step 2.

  2. Check that the CPU usage is within the normal range.

    Run the display cpu-usage command to check whether the CPU usage on the interface board of the faulty device is too high. If the CPU usage is too high, OSPFv3 cannot receive or send protocol packets, which may lead to the neighbor relationship flapping. In this case, troubleshoot the fault of the high CPU usage and disable all unnecessary functions. If the CPU usage is within the normal range, go to Step 3.

  3. Check that the interface status is Up.

    Run the display interface [ interface-type [ interface-number ] ] command to check the physical status of the interface. If the physical status is Down, troubleshoot the interface fault.

    If the physical status of the interface is Up, run the display ospfv3 interface command to check whether the OSPFv3 status of the interface is normal. The status is normal if its value is DR, BDR, DROther, or P2P.

    <HUAWEI> display  ospfv3 interface
    GigabitEthernet1/0/0 is up, line protocol is up
      Interface ID 0x102
      Interface MTU 1500
      IPv6 Prefixes
        FE80::2E0:FFF:FE4E:F101 (Link-Local Address)
        2000::1/64
      Interface Event: 1
      Interface Lsa Count: 1
      Interface Lsa Checksum: 0x9b74
      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 Waiting, 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

    • If the OSPFv3 status of the interface is Down, check whether the number of OSPFv3-capable interfaces in the OSPFv3 process exceeds the upper limit. If the number exceeds the upper limit, disable OSPFv3 on some of the interfaces.

    • If the OSPFv3 status of the interface is DR, BDR, DROther, or P2P, go to Step 4.

  4. Check that the IP addresses of the two devices are on the same network segment.

    Run the display interface interface-type [ interface-number ] command to check the IP addresses of the interfaces on the two devices.

    • If the IP addresses of the two devices are on different network segments, run the ip address command to change either of the IP addresses so that they are on the same network segment.

    • If the IP addresses are on the same network segment, go to Step 5.

  5. Check that the MTUs of interfaces at both ends are consistent.

    If the ospfv3 mtu-ignore command is run on the interfaces at both ends, the MTUs must be consistent. Otherwise, the OSPFv3 neighbor relationship cannot be established.

    • If the MTUs of the two interfaces are inconsistent, run the mtu mtu command in the interface view to change either of the MTUs so that they are consistent.

    • If the MTUs of the two interfaces are consistent, go to Step 6.

  6. Check that there is an interface whose priority is not 0.

    On broadcast and NBMA network segments, at least one interface whose priority is not 0 must exist to ensure that the DR can be elected correctly. Otherwise, the OSPFv3 neighbor relationship can only reach the two-way state.

    Run the display ospfv3 interface command to view the interface priority.

    <HUAWEI> display ospfv3 interface
    GigabitEthernet1/0/0 is up, line protocol is up
      Interface ID 0x102
      Interface MTU 1500
      IPv6 Prefixes
        FE80::2E0:FFF:FE4E:F101 (Link-Local Address)
        2000::1/64
      Interface Event: 1
      Interface Lsa Count: 1
      Interface Lsa Checksum: 0x9b74
      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 Waiting, 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

  7. Check that the OSPFv3 configurations on the two devices are correct.

    1. Check whether the OSPFv3 router IDs of the two devices conflict.

      <HUAWEI> display ospfv3
       Routing Process "OSPFv3 (1)" with ID 0.0.0.0
       SPF Intelligent Timer[millisecs] Max: 10000, Start: 500, Hold: 1000
       For router-LSA and network-LSA:
        LSA Originate Intelligent Timer[millisecs] Max: 5000, Start: 500, Hold: 1000
       For other LSAs:
        LSA Originate Interval 5 seconds
        LSA Arrival Intelligent Timer[millisecs] Max: 1000, Start: 500, Hold: 500 Stub router capability: enabled
       Number of external LSA 0. Checksum Sum 0x0000
       Number of AS-Scoped Unknown LSA 0
       Number of FULL neighbors 0
       Number of Exchange and Loading neighbors 0
       Maximum ASE LS ID 1 and Unused list Count 0
       Number of LSA originated 0
       Number of LSA received 0
       SPF Count          : 0
       Non Refresh LSA    : 0
       Non Full Nbr Count : 0
       Number of areas in this router is 1

      If the OSPFv3 router IDs of the two devices conflict, modify either of the OSPFv3 router IDs so that the both end have the same router ID. If no such conflict exists, proceed with the check.

    2. Check whether the OSPFv3 area configurations on the two devices are consistent.

      <HUAWEI> display ospfv3 interface
      GigabitEthernet1/0/0 is up, line protocol is up
        Interface ID 0x102
        Interface MTU 1500
        IPv6 Prefixes
          FE80::2E0:FFF:FE4E:F101 (Link-Local Address)
          2000::1/64
        Interface Event: 1
        Interface Lsa Count: 1
        Interface Lsa Checksum: 0x9b74
        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 Waiting, 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

    If the fault persists, go to Step 8.

  8. contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs

Relevant Alarms

OSPFv3_1.3.6.1.2.1.191.0.2 ospfv3NbrStateChange

Relevant Logs

None

The OSPFv3 Neighbor Relationship Cannot Enter the Full State

This section describes how to troubleshoot the fault that the OSPFv3 neighbor relationship cannot enter the Full state.

Common Causes

Common causes are as follows:

  • The link is faulty.
  • The configurations of the OSPFv3 neighbor are incorrect.
Troubleshooting Flowchart

Figure 4-61 shows the troubleshooting flowchart.

Figure 4-61 Flowchart for troubleshooting the fault that the OSPFv3 neighbor relationship cannot enter the Full state

Troubleshooting Procedure

Context

NOTE:

Commands can be run in one of two modes: immediate validation mode or two-phase validation mode.

  • In immediate validation mode, the configurations take effect immediately after a command is run.
  • In two-phase validation mode, the configurations do not take effect until after the commit command is run.

Unless otherwise specified, this troubleshooting guide defaults to the immediate validation mode.

Save the results of each troubleshooting step. If the fault persists after following this procedure, Huawei will need these results for further troubleshooting.

Procedure

  1. Troubleshoot the fault based on the status of the OSPFv3 neighbor relationship.

    • The status of the OSPFv3 neighbor relationship is not displayed.

      If the status of the OSPFv3 neighbor relationship is not displayed, see The OSPFv3 Neighbor Relationship Is Down.

    • The neighbor relationship is always in the Init state.

      If the status of the neighbor relationship is always displayed as Init, the remote device cannot receive Hello packets from the local device. In this case, check whether the link or the remote device is faulty.

    • The neighbor relationship is always in the 2-way state.

      If the status of the neighbor relationship is always displayed as 2-way, run the display ospfv3 interface command to check whether the DR priorities of OSPFv3-capable interfaces are 0.

      <HUAWEI> display ospfv3 interface
      GigabitEthernet1/0/0 is up, line protocol is up
      
      Interface ID 518
        IPv6 Prefixes
          FE80::1441:0:E213:1 (Link-Local Address)
          2000:1::1
      
        OSPFv3 Process (1), Area 0.0.0.1, Instance ID 0
          Router ID 2.2.2.2, Network Type POINTOPOINT, Cost: 1562
          Transmit Delay is 1 sec, State Point-To-Point, 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 1, Adjacent neighbor count is 1
      • If the DR priorities of OSPFv3-capable interfaces are 0, the status of the neighbor relationship is normal.
      • If the DR priorities are not 0, go to Step 2.
    • The neighbor relationship is always in the Exstart state.

      If the status of the neighbor relationship is always displayed as Exstart, the devices are exchanging DD packets but fail to synchronize LSDBs, which occurs because excessively long packets cannot be sent or received.

      Run the ping -s 1500 neighbor-address command to ping the neighbor with long packets. If the neighbor fails to be pinged, troubleshoot the link fault.

      If the fault persists, go to Step 2.

    • The neighbor relationship is always in the Exchange state.

      If the status of the neighbor relationship is always displayed as Exchange, the two devices are exchanging DD packets. In this case, check whether the link or the remote device is faulty. If the fault persists, go to Step 2.

    • The neighbor relationship is always in the Loading state.

      Restarting OSPFv3 will cause the re-establishment of all the neighbor relationships in the OSPFv3 process and temporary service interruptions.

      If the neighbor relationship is always in the Loading state, run the reset ospfv3 process-id command to restart the OSPFv3 process.

      If the fault persists, go to Step 2.

  2. contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

OSPFv3_1.3.6.1.2.1.191.0.2 ospfv3NbrStateChange

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 11780

Downloads: 240

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