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


To have a better experience, please upgrade your IE browser.


Alarm Handling

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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

OSPFV3_1. hwOspfv3IfStateChange


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

The status of the OSPFv3 non-virtual-link interface changed.


Alarm ID Alarm Severity Alarm Type Major processingErrorAlarm(4)


Name Meaning


Indicates the MIB object ID of the alarm.


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


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


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


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


Indicates the name of the interface.


Indicates the reason for change in the state of an OSPFv3 interface.
  • 1: No Event
  • 2: Interface Up
  • 3: Wait Timer Expired
  • 4: Backup Seen Occurred
  • 5: Neighbor Change Event Occurred
  • 6: Loop Ind
  • 7: Unloop Ind
  • 8: Interface Down

Impact on the System

This trap is generated when the status of a common interface changes. This trap may affect the neighbor status. If the interface goes Down, the neighbor relationship will be interrupted.

Possible Causes

1. The physical interface went Up or Down.

2. The OSPFv3 neighbor relationship was being established.


  1. Run the display rm interface and display ipv6 interface brief commands to check whether the interface is Down.

    • If the physical interface is Down, check the link. Then check whether the trap is cleared.
      • If so, go to Step 4.

      • If not, go to Step 2.

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

  2. Run the display ospfv3 interface command to check whether the current interface is Up.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information


Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 131679

Downloads: 20

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