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
MENU
Support Documentation

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).
OSPFV3/2/ospfv3NbrStateChange_active

OSPFV3/2/ospfv3NbrStateChange_active

Message

OSPFV3/2/ospfv3NbrStateChange_active: The status of the non-virtual neighbor has changed. (RouterId=[RouterId], NbrIfIndex=[NbrIfIndex], NbrIfInstId=[NbrIfInstId], NbrRtrId=[NbrRtrId], NbrState=[NbrState], IfName=[IfName], Reason=[Reason], SubReason=[SubReason])

Description

  • The OSPFv3 neighbor relationship changed from full to non-full.
  • After the OSPFv3 neighbor relationship reached full again, services were restored, and the alarm was cleared.
  • Existing neighbor relationships were cleared because processes, areas, or interfaces were deleted.

Parameters

Parameter Name Parameter Meaning

RouterId

Router ID.

NbrIfIndex

Index of the neighboring interface.

NbrIfInstId

Instance ID of the neighboring interface.

NbrRtrId

Router ID of the neighboring router.

NbrState

Neighbor status.

IfName

Indicates the interface name.

Reason

Causes triggering the alarm.

SubReason

Indicates the detailed reason.

Possible Causes

Cause 1: Adjacency holdTimer expired.

Cause 2: Physical interface change.

Cause 3: Protocol reason.

Cause 4: BFD session state change.

Cause 5: Configuration change.

Cause 6: Peer router reason.

Cause 7: Waiting for establishing neighbor.

Procedure

  1. Cause 1: Adjacency holdTimer 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. Then, rectify the link fault to restore OSPFv3 services.
      • If the ping succeeds, go to Step 2.

    2. Collect log messages and contact technical support personnel technical support personnel.
  2. Cause 2: Physical interface change.
    1. Run the display ospfv3 interface command to check the physical status of the interfaces setting up the OSPFv3 neighbor relationship.

      • If the physical status of one interface or both interfaces is Down, check the optical power of the interface and check whether the transmission device works properly. After the interface(s) go(es) Up, check whether the alarm is cleared.
      • If the physical status of one interface or both interfaces is *down, the shutdown command has been run on the interface(s). Then run the undo shutdown command on the interface(s) to clear the alarm.
      • If the physical status of both interfaces is Up, go to Step 2.

    2. Run the display ospfv3 interface command to check the protocol status of the interfaces setting up the OSPFv3 neighbor relationship.

      • If the protocol status of one interface or both interfaces is Down, check whether a correct IP address is configured for the interface. Then configure the IP address correctly to clear the alarm.
      • If the protocol status of both interfaces is Up, go to Step 3.

    3. Collect log messages and contact technical support personnel technical support personnel.
  3. Cause 3: Protocol reason.
    1. Run the display this command in both the interface view and OSPFv3 view of the local device and the remote device to check whether two ends use the same protocol.

      • If two ends use the same protocol, go to Step 2.
      • If two ends use different protocols, correct the configuration on one end to ensure that two ends use the same protocol.

    2. Run the display ospfv3 peer command to view information about the OSPFv3 neighbor relationship.

      • If no neighbor relationship 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. Run the ping command to check whether two link ends are properly connected. The cause for the OSPFv3 neighbor relationship to stay in the Init state is that a fault occurs in packet forwarding and hence packets are discarded. If the alarm persists after the fault in packet forwarding is rectified, go to Step 4.
      • If 2-way is displayed, the ospfv3 dr-priority 0 command has been run on the local interface running OSPFv3. Then, run the ospfv3 dr-priority command to increase the DR priority of the interface to be larger than 0 to clear the alarm.
      • If Exstart is displayed, the device generating this alarm keeps performing DD negotiation but fails to complete DD synchronization. Then go to Step 3.
      • If Loading is displayed, the local device has received illegal LSAs and keeps sending LSA requests. Then run the reset ospfv3 command on two ends to clear the alarm.
        NOTE:

        The OSPFv3 neighbor relationship may be torn down after you run the reset ospfv3 command to reset the OSPFv3 connection. Exercise caution when running this command.

    3. Run the display this command in the interface view and OSPFv3 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: BFD session state change.
    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. Then rectify the link fault to restore OSPFv3 services.
      • 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 ospfv3 peer command to check whether the OSPFv3 neighbor relationship status is Up.

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

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

      • If area configurations on two ends are different, change them to be the same.
      • If area configurations on two ends are the same, go to Step 2.

    2. Run the display this command in the OSPFv3 view to check whether opaque-capability has been enabled in the OSPFv3 processes on two ends.

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

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

      • If OSPFv3 network types configured on the interfaces of two ends are different, change them to be the same.
      • If OSPFv3 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: Peer router reason.
    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. Contact the producer of the non-Huawei device to check its operating status and rectify the fault.
    3. Check whether the remote device or the OSPFv3 process is restarted.

      • If the remote device or the OSPFv3 process is restarted, find the problem cause based on the generated alarm and log messages.
      • If the remote device or the OSPFv3 process is not restarted, go to Step 4.

    4. Collect log messages and contact technical support personnel technical support personnel.
  7. Cause 7: Waiting for establishing neighbor.
    1. Check the two ends are configured with OSPFv3 or check whether the configurations on the two ends are consistent.

      • If the two ends are configured with OSPFv3 and the configurations of the two ends are consistent, go to Step 2.
      • If the remote end is not configured with OSPFv3 or the configurations of the two ends are inconsistent, configure OSPFv3 on the remote end and ensure that the configurations of the two ends are consistent.

    2. Run the ping command to check whether two link ends are properly connected.

      • If the ping fails, check the transmission devices, link status, and interconnected interfaces. Then rectify the link fault to restore OSPFv3 services.
      • If the ping succeeds, go to Step 3.

    3. Collect log messages and contact technical support personnel technical support personnel.
Translation
简体中文
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 169832

Downloads: 110

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next
Enterprise APP

Copyright © 2020 Huawei Technologies Co., Ltd. All rights reserved.