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

Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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_1.3.6.1.4.1.2011.5.25.147.0.3 hwOspfv3VirtNbrStateChange

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.3 hwOspfv3VirtNbrStateChange

Description

OSPFV3/2/VNBRCHANGE:OID [oid] The status of the virtual neighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VNbrState=[integer], ChgReason=[integer])

The status of the OSPFv3 neighbor on the virtual link changed because the status of the virtual link interface changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.3 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

VirtualNbrRouterId

Indicates the Router ID of the virtual link neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local router. The value is a decimal integer.

VNbrState

Indicates the state of the virtual link neighbor.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

ChgReason

Indicates the reason for change in the state of virtual link neighbor.
  • 1: No Event
  • 2: Received Hello Packet
  • 3: Start
  • 4: Received Two Way
  • 5: Negotiation Done
  • 6: ExchangeDone
  • 7: Received Bad LS Request
  • 8: Loading Done
  • 9: Established Adjacency
  • 10: Mismatch In Seq Number
  • 11: Received One Way
  • 12: NBR Killed
  • 13: Inactivity Timer Expired
  • 14: Link Down

Impact on the System

This trap is generated when the status of the neighbor (a neighbor of a virtual link) changes. If the neighbor changes from a lower status to a higher status, this trap message is informational only, and no action is required. If the neighbor changes from a higher status to a lower status, services may be interrupted.

Possible Causes

1. The status of the interface of the virtual link changed.

2. The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the virtual link interface on the local end or remote end were modified.

3. OSPFv3 was restarted by using the reset ospfv3 command or the active/standby switchover was performed.

4. An error packet was received.

5. The overflow function was configured and the process entered the Overflow state.

6. Routes of the area configured with the virtual link were added or deleted.

7. The ping operation failed, which indicated that an error occurred during packet transmission.

Procedure

  1. Run the display ospfv3 interface and display ipv6 interface brief commands to check whether the physical interface of the virtual link goes Down.

    • If the physical interface is Down, check the link and make the link Up, and then go to Step 2.

    • If the physical interface is Up, go to Step 2.

  2. Run the display ospfv3 peer command to check whether the OSPFv3 neighbor relationship is normal.

    • If the neighbor relationship is abnormal, check whether trap 1.3.6.1.4.1.2011.5.25.147.0.2 exists. If the trap exists, locate the fault according to the trap. If the trap does not exist, go to Step 6.

    • If the neighbor relationship is normal, go to Step 3.

  3. Run the display ospfv3 routing command to check whether the route to the neighbor on the virtual link exists.

    • If the route does not exist, go to Step 5.

    • If the route exists, go to Step 4.

  4. Run the display ospfv3 vlink and display current-configuration configuration ospfv3 commands to check whether the configurations of the two ends are correct.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Adjust the parameters correctly according to the requirements of the networking, and check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 80553

Downloads: 49

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