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).
OSPF Troubleshooting

OSPF Troubleshooting

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

For details about OSPF, see the Feature Description - OSPF.

The OSPF Neighbor Relationship Is Down

This section describes how to troubleshoot the fault that the OSPF 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 MPU or 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-58 shows the troubleshooting flowchart.

Figure 4-58 Flowchart for troubleshooting the fault that the OSPF neighbor relationship is Down

Troubleshooting Procedure

Context

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check logs to locate the cause.

    Run the display logbuffer size buffersize command to check the log information.

    If the log message is as follows, the neighbor status changes:

    VRPV8 %%01 ospfv2comm/6/NBR_CHANGE(l):CID=[UINT];Neighbor changes event: neighbor status changed. (ProcessId=[UINT], NbrIpAddr=[IPADDR], NbrEvent=[UINT], NbrPreviousState=[UINT], NbrCurrentState=[UINT])

    Check the NbrEvent field, which records the cause of the fault. The possible causes of the fault are as follows:

    • Inactivity (NbrEvent=7)

      An InactivityTimer event occurs on the neighbor, indicating that the OSPF neighbor relationship goes Down because the local device does not receive any Hello packets from its neighbor within the down time. If this is the case, go to Step 2.

    • LLDown (NbrEvent=6)

      An LLDown event of occurs on the neighbor, indicating that the lower-layer protocol notifies the upper layer that the neighbor is unreachable. If this is the case, go to Step 2.

    • 1-Way Received (NbrEvent=4)

      A 1-Way Received event occurs on the neighbor. A 1-Way Hello packet is sent from the remote end to the local end when the OSPF status on the remote end changes to Down. After receiving the packet, the OSPF status on the local end also changes to Down. In this case, check the remote end to rectify any possible fault.

    • Kill Neighbor (NbrEvent=5)

      A Kill Neighbor event occurs, indicating that the interface or BFD session becomes Down. In this case, run the display interface [ interface-type [ interface-number ] ] command to check the interface status and rectify any possible fault.

    If the log message is as follows, the reset ospf process command has been run:

    VRPV8 %%01 ospfv2comm/6/OSPF_RESET(l):VS=%u-CID=[UINT];OSPF process or area reset. (CompCID=[UINT], Parameter=[UINT], ResetReason=[UINT])

    To verify whether this command has been run, check the operation records or log information.

    In other cases, go to Step 9.

  2. 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 3.

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

    Run the display cpu-usage command to check whether the CPU usage on the MPU or interface board of the faulty device is too high. If the CUP usage is too high, OSPF 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 unnecessary functions. If the CPU usage is within the normal range, go to Step 4.

  4. 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 ospf interface command to check whether the OSPF status of the interface is normal. The status is normal if its value is DR, BDR, DROther, or P2P.

    <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
     GigabitEthernet1/0/0     192.168.1.1     P2P       P-2-P    1       100

    • If the OSPF status of the interface is Down, run the display ospf cumulative command to check whether the number of OSPF-capable interfaces in the OSPF process exceeds the upper limit. If the number exceeds the upper limit, disable OSPF on some of the interfaces.

      <HUAWEI> display ospf cumulative
                OSPF Process 1 with Router ID 10.1.1.1
                        
        IO Statistics
        Type             Input     Output
        Hello               26         62
        DB Description       3          2
        Link State Request   1          1
        Link State Update    5          5
        Link-State Ack       3          3
        
        ASE: Disabled
        LSAs originated by this router
        Router            : 1
        Network           : 0
        Summary-Network   : 0
        Summary-ASBR      : 0
        External          : 3
        NSSA              : 0
        Opaque Link scope : 0
        Opaque Area scope : 0
        Opaque AS scope   : 0
      
        LSAs Originated   : 4  
        LSAs Received     : 14
      
         Routing Table:
           Intra Area: 2  Inter Area: 0  ASE: 2
      
        Up Interface Cumulate: 4
        -------------------------------------------------------
         Neighbor cumulative data. (Process 1)
        -------------------------------------------------------
        Down:       0 Init:        0 Attempt:    0 2-Way:    0
        Exstart:    0 Exchange:    0 Loading:    0 Full:     1
        Retransmit Count: 0
      
        Neighbor cumulative data. (Total)
        -------------------------------------------------------
        Down:       0 Init:        0 Attempt:    0 2-Way:    0
        Exstart:    0 Exchange:    0 Loading:    0 Full:     1
        Retransmit Count: 0
    • If the OSPF status of the interface is DR, BDR, DROther, or P2P, go to Step 5.

  5. 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 of the two devices are on the same network segment, go to Step 6.

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

    If the ospf mtu-enable command is run on the interfaces at both ends, the MTUs of the two interfaces must be consistent. Otherwise, the OSPF 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 are consistent, go to Step 7.

  7. 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 OSPF neighbor relationship can only reach the two-way state.

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

    <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
     GigabitEthernet1/0/0     192.168.1.1     P2P       P-2-P    1       100

  8. Check that the OSPF configurations on the two devices are correct.

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

      <HUAWEI> display ospf brief
       OSPF Process 1 with Router ID 6.1.1.1
       
       RouterID: 20.1.1.2          Border Router: AREA AS NSSA
       Multiple VPN instance is not enabled
       Global DS-TE Mode is disabled
       Graceful-restart capability is disabled
       Helper support capability is not configured
       
       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
       SPF computation count       : 2
       RFC 1583 compatible
       Retransmission limitation is disabled 
       Area count                  : 1
       Nssa qrea count             : 0
       ExChange/Loading neighbors  : 0
      
       Area: 0.0.0.0             MPLS TE not enabledMPLS TE  : Disabled
       Authtype: None   Area flag: Normal
       SPF scheduled count: 2
       Exchange/Loading neighbors: 0
       Router ID conflict state: Normal
      
       Interface: 1.1.1.1 (GE3/0/1)
       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

      If so, modify the OSPF router IDs. If not, proceed with the check.

    2. Check whether the OSPF Area ID configurations on the two devices are consistent.

      <HUAWEI> display ospf interface
                OSPF Process 1 with Router ID 1.1.1.1
                        Interfaces
      
       Area: 0.0.0.0          (MPLS TE not enabled)
       Interface          IP Address      Type         State    Cost    Pri
       GigabitEthernet1/0/0           192.168.1.1     Broadcast    BDR      1       1
    3. Check whether other OSPF configurations on the two devices are the consistent.

      Run the display ospf error command every 10s for 5 minutes.

      <HUAWEI> display ospf error
                OSPF Process 1 with Router ID 1.1.1.1
                        OSPF error statistics
      General packet errors:
       0     : IP: received my own packet     0     : Bad packet
       0     : Bad version                  0     : Bad checksum
       0     : Bad area id                   0     : Drop on unnumbered interface
       0     : Bad virtual link               0     : Bad authentication type
       0     : Bad authentication key         0     : Packet too small
       0     : Packet size > ip length         0     : Transmit error
       0     : Interface down                0     : Unknown neighbor
      HELLO packet errors:
       0     : Netmask mismatch              0     : Hello timer mismatch
       0     : Dead timer mismatch           0     : Extern option mismatch
       0     : Router id confusion            0     : Virtual neighbor unknown
       0     : NBMA neighbor unknown          0     : Invalid Source Address
      
      • Check the Bad authentication type field. If the value of this field keeps increasing, the OSPF authentication types of the two devices are different. In this case, set the same authentication type for the two devices.
      • Check the Hello timer mismatch field. If the value of this field keeps increasing, the value of the Hello timers on the two devices are different. In this case, check the interface configurations of the two devices and set the same value for the Hello timers.
      • Check the Dead timer mismatch field. If the value of this field keeps increasing, the value of the dead timers on the two devices are different. In this case, check the interface configurations of the two devices and set the same value for the dead timers.
      • Check the Extern option mismatch field. If the value of this field keeps increasing, the area types of the two devices are different (the area of one device is the common area, and the area of the other device is the stub area or NSSA). In this case, set the same area type for the two devices.

    If the fault persists, go to Step 9.

  9. Contact 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

OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange

Relevant Logs

OSPF/6/NBR_CHANGE

The OSPF Neighbor Relationship Cannot Enter the Full State

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

Common Causes

Common causes are as follows:

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

Figure 4-59 shows the troubleshooting flowchart.

Figure 4-59 Flowchart for troubleshooting the fault that the OSPF 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 OSPF neighbor relationship.

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

      If the status of the OSPF neighbor relationship is not displayed, see The OSPF 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 ospf interface command to check whether the DR priorities of OSPF-capable interfaces are 0.

      <HUAWEI> display ospf interface
                OSPF Process 1 with Router ID 10.1.1.1
                        
       Area: 0.0.0.0               MPLS TE not enabled
       Interface          IP Address      Type         State     Cost    Pri
       GigabitEthernet1/0/0           10.1.1.1       Broadcast    DROther   1       0
      • If the DR priorities of OSPF-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 in the following cases:

      • 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.

      • The OSPF MTUs of the two devices are different.

        If the ospf mtu-enable command is run on the OSPF interfaces, check whether the OSPF MTUs on the two interfaces are the same. If the OSPF MTUs are different, change the MTU at either end to ensure that both ends have the same MTU.

      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 OSPF will cause the re-establishment of all the neighbor relationships in the OSPF process and temporary service interruptions.

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

      If the fault persists, go to Step 2.

  2. Contact 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

OSPF_1.3.6.1.2.1.14.16.2.2 ospfNbrStateChange

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 6317

Downloads: 215

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