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

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).
ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

Description

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

The database entered or exited from the Overload state.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.1

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

overLoadState

Indicates the LSDB Overload state:
  • 1: off

  • 2: on

  • 3: waiting

  • 4: overloaded

Impact on the System

1. If the trap is triggered by the change of the LSDB Overload state, route selection of the neighbor will be affected.

2. If the trap is triggered by memory failure, it indicates that the IS-IS database is unauthentic.

Possible Causes

1. The set-overload or undo set-overload command is run in the IS-IS view.

2. Memory application failed because memory was insufficient. As a result, the system of the switch may crash.

Procedure

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

    • If so, this trap message is informational only, and no action is required. Go to Step 6.

    • If not, 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 the memory usage of the switch. Check whether the memory usage reaches the threshold.

    • If so, go to Step 4.

    • If not, 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-21

Document ID: EDOC1000142054

Views: 182173

Downloads: 44

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