ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

Trap Buffer Description

The overload state of IS-IS LSDB changed. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisSysLevelOverloadState=[isisSysLevelOverloadState])

The database entered or exited from the Overload state.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Error
Mnemonic Code	ISIS_DATABASE_OVERLOAD
Trap OID	1.3.6.1.3.37.2.0.1
MIB	ISIS-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
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	-

Trap Buffer Parameters

Parameter	Description
isisSysInstance	ID of an IS-IS process.
isisSysLevelIndex	IS-IS level.
isisSysLevelOverloadState	Overload state.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.3.37.1.1.1.1.1	isisSysInstance	isisSysInstance
1.3.6.1.3.37.1.2.1.1.1	isisSysLevelIndex	isisSysInstance isisSysLevelIndex
1.3.6.1.3.37.1.2.1.1.4	isisSysLevelOverloadState	isisSysInstance isisSysLevelIndex

VB OID

VB Name

VB Index

1.3.6.1.3.37.1.1.1.1.1

isisSysInstance

1.3.6.1.3.37.1.2.1.1.1

isisSysLevelIndex

isisSysInstance

isisSysLevelIndex

1.3.6.1.3.37.1.2.1.1.4

isisSysLevelOverloadState

isisSysInstance

isisSysLevelIndex

Impact on the System

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

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: The IS-IS process entered the Overload state and then exited from it.

Cause 3: Failed to apply for memory 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 or undo set-overload command has been configured in the process.

If so, go to Step 4. This log message is informational only, and no action is required.
If not, go to Step 2.

2. Run the display memory-usage command to check whether the memory usage of the device has reached the threshold.

If so, obtain user logs and go to Step 3.
If not, go to Step 3.

3. Collect log information and configuration information, and then contact technical support personnel.

4. End.