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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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/2/ospfNbrStateChange_active

OSPF/2/ospfNbrStateChange_active

Message

OSPF/2/ospfNbrStateChange_active: The status of the non-virtual neighbor has changed. (RouterId=[RouterId], NbrIpAddress=[NbrIpAddress], NbrAddressLessIndex=[NbrAddressLessIndex], NbrRtrId=[NbrRtrId], NbrState=[NbrState], ProcessId=[ProcessId], AreaId=[AreaId], IfnetIndex=[IfnetIndex], LocalIfIpAddress=[LocalIfIpAddress], IfName=[IfName], VpnName=[VpnName], SubReason=[SubReason], Reason=[NbrStateChangeReason])

Description

OSPF neighbor relationship status changed because the status of the interface where the neighbor resided changed or the local device received error Hello messages.

Parameters

Parameter Name Parameter Meaning

RouterId

Router ID

NbrIpAddress

IP address of the neighbor

NbrAddressLessIndex

Index of the unnumbered interface on the neighbor

NbrRtrId

Router ID of the neighbor

NbrState

State of the neighbor

ProcessId

Process ID

AreaId

Area ID

IfnetIndex

Index of an interface on the local device

LocalIfIpAddress

IP address of the interface on the local device

IfName

Name of the interface on the local device

VpnName

VPN instance name

SubReason

Specific cause of the neighbor status change:

  • 1: No Hello packets were received.
  • 2: Interface parameters were different.
  • 3: The logical interface changed.
  • 4: The physical interface changed.
  • 5: The process was reset.
  • 6: The area was reset.
  • 7: The area capabilities were different.
  • 8: The virtual link was unreachable.
  • 9: The sham link was unreachable.
  • 10: The network was deleted.
  • 11: The neighbor was deleted.
  • 12: The interface was in silent status.
  • 13: The Opaque LSA capability was enabled.
  • 14: The Opaque LSA capability was disabled.
  • 15: The OSPF interface type changed.
  • 16: The BFD session status changed.
  • 17: The number of retransmission times exceeded a specified limit.
  • 18: 1-way Hello packets were received.
  • 19: The local end became a DR Other.
  • 20: The neighbor became a DR Other.
  • 21: An NSSA was configured or deleted.
  • 22: A stub area was configured or deleted.
  • 23: DD packets were invalid.
  • 24: No DD packets were received.
  • 25: The flag bit of DD packets was incorrectly set.
  • 26: The Opaque LSA capability was not enabled, but Type-9, Type-10, and Type-11 LSAs were received.
  • 27: No NSSA was configured, but Type-7 LSAs were received.
  • 28: Unknown LSR packets were received.
  • 29: An NSSA or a stub area was configured, but Type-5 or Type-11 LSAs were received.
  • 30: The received LSR packet carried a nonexistent LSA.
  • 31: The received LSR packet carried an LSA sent by the neighbor.
  • 32: The received LSR packet carried an LSA that was less updated than the corresponding LSA in the local LSDB.
  • 33. The LSDB was overloaded.
  • 34: The criteria used to filter LSAs were changed.
  • 35: The ACL used to filter LSAs were changed.
  • 36: The neighbor was reset.
  • 37. The interface was reset.
  • 38. The interface was deleted.
  • 39. The area was deleted.
  • 40: The system was overloaded.
  • 41: The interface was in the backup status.
  • 42: No router ID was available.
  • 43: The router ID was changed.
  • 44: Component is in Implement stat
  • 45: Seqeunce Number mismatched
  • 46: I Bit Incorrect in DD
  • 47: MS Bit Incorrect in DD
  • 48: Options Incorrect in DD
  • 49: Received MTU mismatched DD Packet
  • 51: OSPF Process Shutdown
  • 52: OSPF Max Nbr In Adj
  • 54: OSPF Gr Master ForceDown
  • 55: DD retrans times upto limit
  • 56: Neighbor state was not full when LSDB overflow
  • 100: Undo OSPF Interface, Undo area

Reason

Causes of the alarm

Possible Causes

Cause 1: The hold timer of the neighbor expired.

Cause 2: The status of physical interfaces changed.

Cause 3: A protocol error occurred.

Cause 4: The BFD session was Down.

Cause 5: OSPF configurations changed.

Cause 6: An error occurred on the neighbor.

Procedure

  1. Cause 1: The hold timer of the neighbor expired.
    1. Run the ping command to check whether two link ends are properly connected.

      • If the ping fails, check the transmission devices, link status, and interfaces to locate the hardware fault and rectify it.
      • If the ping succeeds, go to Step 2.

    2. Collect log messages and contact technical support personnel technical support personnel.
  2. Cause 2: The status of physical interfaces changed.
    1. Run the display ospf interface command to check the physical status of interfaces used to establish the OSPF neighbor relationship.

      • If the physical status is Down, ensure that the optical power of the interfaces and transmission devices are normal.
      • If the physical status is *down because the shutdown command has been run on the interfaces, run the undo shutdown command on the interfaces.
      • If the physical status is Up, go to Step 2.

    2. Run the display ospf interface command to check the protocol status of interfaces used to establish the OSPF neighbor relationship.

      • If the protocol status is Down, ensure that an IP address is correctly configured.
      • If the protocol status is Up, go to Step 3.

    3. Collect log messages and contact technical support personnel technical support personnel.
  3. Cause 3: A protocol error occurred.
    1. Run the display this command in both the interface view and OSPF view of the local and remote devices to check whether the versions of OSPF configured at both ends are the same.

      • If the versions of OSPF configured at both ends are the same, go to Step 2.
      • If the versions of OSPF configured at both ends are different, change the version at either end to be the same as that at the other end.

    2. Run the display ospf peer command to view OSPF neighbor relationship information.

      • If no neighbor information is displayed, the local device does not receive any Hello messages from the remote device or the local device has discarded the received Hello messages. Then go to Step 3.
      • If Init is displayed, the local device has received Hello messages from the remote device, whereas the remote device does not receive any Hello messages from the local device. In this case, a link fault may have occurred, and packets will be discarded. To address this problem, run the ping command to check whether two ends are properly connected. If the alarm persists after the fault is rectified, go to Step 4.
      • If 2-way is displayed, the ospf dr-priority 0 command has been configured on the local interface. In this case, increase the DR priority.
      • If ExStart is displayed, the local device is busy with DD negotiation but fails to complete LSDB synchronization. In this case, go to Step 3.
      • If Loading is displayed, the local device considers received LSAs invalid, discards them, and keeps sending LSA requests. In this case, run the reset ospf process command on two ends.
        NOTE:

        The OSPF adjacency relationship may be torn down after you run the reset ospf process command to reset the OSPF connection. Therefore, exercise caution when running this command.

    3. Run the display this command in the interface view and OSPF view to check whether authentication modes configured on two ends are the same.

      • If authentication modes configured on two ends are the same, go to Step 4.
      • If authentication modes configured on two ends are different, change them to be the same.

    4. Collect log messages and contact technical support personnel technical support personnel.
  4. Cause 4: The BFD session was Down.
    1. Run the ping command to check whether two link ends are properly connected.

      • If the ping fails, the transmission devices, link status, and interfaces to locate the hardware fault and rectify it.
      • If the ping succeeds, go to Step 4.

    2. Run the ping command in the interface view to check whether the link between two ends is configured correctly.

      • If the link is correctly configured, go to Step 3.
      • If the link is incorrectly configured, correct the configuration.

    3. Run the display ospf peer command to check whether OSPF neighbor relationship status is Up.

      • If OSPF neighbor relationship status is Up, go to Step 4.
      • If OSPF neighbor relationship status is Down, go to Step 4.

    4. Collect log messages and contact technical support personnel technical support personnel.
  5. Cause 5: OSPF configurations changed.
    1. Run the display this command in the OSPF view to check whether area configurations on two ends are the same.

      • If area configurations on two ends are different, change the area configuration at either end to be the same as that at the other end.
      • If area configurations on two ends are the same, go to Step 2.

    2. Run the display this command in the OSPF view to check whether the Opaque LSA capability has been enabled in the OSPF processes on two ends.

      • If the Opaque LSA capability has not been enabled in the OSPF process on one end, enable it.
      • If the Opaque LSA capability has been enabled in the OSPF processes on two ends, go to Step 3.

    3. Run the display ospf interface command to check whether OSPF network types configured on the interfaces of two ends are the same.

      • If OSPF network types configured on the interfaces of two ends are different, change them to be the same.
      • If OSPF network types configured on the interfaces of two ends are the same, go to Step 4.

    4. Collect log messages and contact technical support personnel technical support personnel.
  6. Cause 6: An error occurred on the neighbor.
    1. Check whether the remote device is a non-Huawei device.

      • If it is a non-Huawei device, go to Step 2.
      • If it is a Huawei device, go to Step 3.

    2. Ask the manufacturer of the non-Huawei device to check its operating status and rectify the fault.
    3. Check whether the remote device or the OSPF process is restarted.

      • If the remote device or the OSPF process is restarted, locate the problem based on the alarms and logs generated on the remote device.
      • If the remote device or the OSPF process is not restarted, go to Step 4.

    4. Collect log messages and contact technical support personnel technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115242

Downloads: 85

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