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

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2 hwOspfv3NbrStateChange

Description

OSPFV3/2/NBRCHANGE:OID [oid] The status of the non-virtual neighbor has changed. (IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge], RouterId=[gauge], NbrState=[integer], IfName=[octet], ChgReason=[integer])

The status of the OSPFv3 neighbor changed. A possible cause is that the status of the interface where the neighbor resided changed or the contents of the received Hello packets changed.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface. The value is a decimal integer.

IfName

Indicates the name of the interface.

InstanceId

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

NbrRouterId

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

RouterId

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

NbrState

Indicates the state of the 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 an OSPFv3 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 (not a neighbor of a virtual link) changes. This trap indicates that the status of the neighbor 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 where the neighbor resided changed.
  2. The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the interfaces on the local end or remote end were modified.
  3. OSPF was restarted by using the reset ospfv3 command or the active/standby switchover was performed.
  4. The ping operation failed, which indicated that an error occurred during packet transmission.

Procedure

  1. Run the display ipv6 interface and display ospfv3 peer commands to check the status of the interface where the neighbor resides.

    • 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. Check whether packets are correctly forwarded and ping the IP address of the remote interface.

    • If the ping fails, go to Step 5.

    • If the ping succeeds, go to Step 3.

  3. Run the display ipv6 interface command to check whether the interface where the OSPFv3 neighbor resides is in the Up state.

    • If the interface is in the Down state, go to Step 5.

    • If the interface is in the Up state, go to Step 4.

  4. Run the display ospfv3 interface command to check whether the configurations of the two ends are correct.

    • If so, go to Step 6.

    • If not, go to Step 5.

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

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 74242

Downloads: 47

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