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

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

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.3.6.1.2.1.191.0.4 ifconfigerror

OSPFV3_1.3.6.1.2.1.191.0.4 ifconfigerror

Description

A packet is received on the non-virtual interface from a router whose configuration conflicts with the local configuration. (RouterId=[RouterId], IfIndex=[IfIndex], IfInstId=[IfInstId], IfState=[IfState], PacketSrc=[PacketSrc], ConfigErrorType=[ConfigErrorType], PacketType=[PacketType])

This alarm indicates that the configurations of interfaces used to establish a neighbor relationship are inconsistent. Possible causes are that the Hello, Dead, or Poll timer configurations on both ends were inconsistent or the interface configurations on both ends were not performed in the same area.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

ifconfigerror

Trap OID

1.3.6.1.2.1.191.0.4

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

RouterId

Indicates the router ID.

IfnetIndex

Indicates the interface index.

NbrIfInstId

Indicates the ID of a neighbor interface.

NbrRtrId

Indicates the ID of a neighbor router.

NbrState

Indicates the neighbor status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: ExStart
  • 6: Exchange
  • 7: Loading
  • 8: Full

SubReason

Indicates detailed reasons.

Reason

Possible causes of the neighbor status change are as follows:

  • 1: adjacencyHoldTimerExpired. The value indicates that the timer of the neighbor switch times out.
  • 2: physicalInterfaceChange. The value indicates that the physical interface status of the switch changes.
  • 3: ospfProtocolReason. The value indicates that an OSPF protocol error occurs.
  • 4: bfdSessionStateChange. The value indicates that a BFD session is torn down.
  • 5: configureChange. The value indicates that OSPF configurations change.
  • 6: peerRouterReason. The value indicates that the neighbor switch does not function properly.
  • 100: alarmCleared. The value indicates that the service is restored or the neighbor switch is deleted and the alarm is cleared.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.191.1.1.1

ospfv3RouterId

N/A

1.3.6.1.2.1.191.1.7.1.12

ospfv3IfState

ospfv3IfIndex;

ospfv3IfInstId;

1.3.6.1.2.1.191.1.14.3

ospfv3PacketSrc

N/A

1.3.6.1.2.1.191.1.14.2

ospfv3PacketType

N/A

1.3.6.1.2.1.191.1.14.1

ospfv3ConfigErrorType

N/A

Impact on the System

This trap message is generated after an interface receives a message indicating that parameters are incorrectly configured. Such configuration errors generally occur during the deployment test or service cutover. You can adjust the parameters correctly to rectify the fault, and services will not be affected.

Possible Causes

Cause 1: Interface configurations on both ends of the link were inconsistent.

Cause 2: The link protocol changed.

Procedure

  1. Use the display ospfv3 interface command to check whether the interface configurations on both ends of the link are consistent.

    • If they are consistent, go to Step 3.
    • If they are inconsistent, go to Step 2.

  2. Perform the following operations based on the networking condition:

    • If the configurations on both ends can be changed to be consistent, set the same Hello timer value, Dead timer value, and Poll timer value on both ends. Then check whether the alarm is cleared.
      • If the alarm is cleared, go to Step 4.
      • If the alarm persists, go to Step 3.
    • If the configurations on both ends of the link cannot be changed to be consistent, go to Step 3.

  3. Collect the alarm information, log information, and configuration information, and then contact technical support personnel technical support personnel.
  4. End.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 196012

Downloads: 115

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