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.1 isisDatabaseOverload

ISIS-STD_1.3.6.1.2.1.138.0.1 isisDatabaseOverload

Description

ISIS-STD/3/OLOAD:OID [oid] The overload state of IS-IS LSDB changed. (sysLevel=[integer], NotificationSysLevelIndex=[integer], OverLoadState=[integer])

The IS-IS LSDB entered or exited from the overload state.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.1

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SysLevel

IS-IS level:
  • 1: Level-1

  • 2: Level-2

NotificationSysLevelIndex

IS-IS level of a device that sends the trap

OverLoadState

Overload state

Impact on the System

1. If the trap is generated because the IS-IS LSDB entered or exited from the overload state, route selection on the IS-IS neighbor will be affected.

2. If the trap is generated because the memory usage exceeds the upper threshold, the IS-IS LSDB is unreliable.

Possible Causes

Cause 1: The set-overload or undo set-overload command was run in the IS-IS view.

Cause 2: After the set-overload on-startup command was run in the IS-IS view, the router restarted.

Cause 3: Applying for memory resources failed in the case of memory shortage, causing a system crash.

Procedure

  1. Run the display this command in the IS-IS view to check whether the set-overload command has been run in the process.

    • If set-overload command has been run in the process, go to Step 6.

    • If set-overload command has not been run in the process, go to Step 2.

  2. Run the display history-command command in any view to check whether the undo set-overload command has been run in the process.

    • If the undo set-overload command has been run in the process, go to Step 6.

    • If the undo set-overload command has not been run in the process, go to Step 3.

  3. Run the display memory-usage command to check whether the memory usage of the router has reached the upper threshold.

    • If the memory usage has reached the upper threshold, go to Step 4.

    • If the memory usage has not reached the upper threshold, go to Step 5.

  4. Obtain the logs.
  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 144136

Downloads: 42

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