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

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms 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_1. hwOspfv3IfConfigError

OSPFV3_1. hwOspfv3IfConfigError


OSPFV3/2/IFCFGERR:OID [oid] The configuration of the non-virtual interface is incorrect. (IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], PacketSrcAdd=[octet], ErrorType=[integer], PacketType=[integer])

This trap is generated on a non-virtual-link interface when the local end refused to establish the adjacency relationship with the remote end. This trap indicated that the configurations of the interfaces on which the neighbor relationship is to be established were inconsistent. A possible cause is that the values of the Hello timer, dead timer, poll timer were not consistent on the two interfaces or the two interfaces were not in the same area.


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 switch. The value is a decimal integer.


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


Indicates the address of the source node that sends the packet.


Indicates the type of the error.
  • 1: badVersion
  • 2: areaMismatch
  • 3: unknownNbmaNbr
  • 4: unknownVirtualNbr
  • 5: helloIntervalMismatch
  • 6: deadIntervalMismatch
  • 7: optionMismatch
  • 8: mtuMismatch
  • 9: duplicateRouterId
  • 10: noError


Indicates the type of the packet.
  • 1: Hello
  • 2: DD(Data base Description) packet
  • 3: LS Request
  • 4: LS Update
  • 5: LS Acknowledgement
  • 6: NULL packet

Impact on the System

This trap is generated when an interface receives a packet indicating parameters are incorrectly configured. Such configuration errors generally occur during the deployment test or cutover. You can rectify the fault by modifying the parameters on the two ends to be consistent, and services will not be affected.

Possible Causes

1. Parameters manually configured on the two interfaces were inconsistent.

2. The routing protocol on the link layer changed.


  1. Run the display ospfv3 interface command to check whether the configurations of the two ends are consistent.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Perform the following operations according to the networking:

    • If it is allowed to modify the configurations of the two ends to be consistent, go to Step 4.

    • If it is not allowed to modify the configurations of the two ends to be consistent, go to Step 3.

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

Related Information


Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 184255

Downloads: 44

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