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, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

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).
ISIS-STD_1.3.6.1.2.1.138.0.16 isisProtocolsSupportedMismatch

ISIS-STD_1.3.6.1.2.1.138.0.16 isisProtocolsSupportedMismatch

Description

ISIS-STD/2/PROTO_MISMATCH:OID [oid] The protocol of received Protocol TLV is mismatched with local configuration. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduProtocolsSupported=[opaque], PduLspId=[opaque], PduFragment=[opaque])

The type of the protocol supported TLV carried in a received PDU was inconsistent with the locally configured one.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.16

Major

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NotificationSysLevelIndex

IS-IS level of a device that sends the trap

CircIfIndex

Interface index

PduProtocolsSupported

Protocol supported TLV contained in a received PDU

PduLspId

LSP ID

PduFragment

64-byte PDU header

Impact on the System

LSPs cannot be learned and routes cannot be generated.

Possible Causes

The protocol type supported by the source router that generated the LSP was different from that supported by the local router.

Procedure

  1. The type of the protocol supported TLV carried in the received LSP mismatched with the type of the protocol supported by the local device. Check whether the trap is cleared in 10 minutes.

    • If the trap is cleared, go to Step 3.
    • If the trap is not cleared, go to Step 2.

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

Related Information

None

Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 131206

Downloads: 40

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