ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge

Trap Buffer Description

ISIS received a self-originated LSP with the age being 0. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspId=[isisPduLspId], isisPduRemoteRouterID=[isisPduRemoteRouterID], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received an LSP with a system ID identical to that on the local device. The lifetime of this LSP was 0.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Critical
Mnemonic Code	ISIS_OWN_LSP_PURGE
Trap OID	1.3.6.1.3.37.2.0.7
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.
isisCircIndex	Circuit IfIndex of an interface.
isisCircIfIndex	Circuit IfIndex of an interface.
isisPduLspId	LSP ID.
isisPduRemoteRouterID	ID of the remote router.
ifIndex	IfIndex of an interface.
IfName	Interface name.

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.3.1.1.2	isisCircIfIndex	isisSysInstance isisCircIndex
1.3.6.1.3.37.1.10.1.1.1	isisPduLspId	isisSysInstance
1.3.6.1.3.37.1.10.1.1.10	isisPduRemoteRouterID	isisSysInstance
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

1. If the trap is triggered by the restart of the local device, services will not be affected.

2. If the trap is generated frequently, IS-IS routes are affected and packets may not be forwarded.

Possible Causes

Cause 1: LSPs were not refreshed in time on the local device. Purge packets were generated and then flooded to the local device after these LSPs aged.

Cause 2: After a fault occurred during the packet transmission, packets were changed and purge packets were generated.

Cause 3: After the local device restarted, it received an LSP with a system ID identical to the one on the local device. In addition, the lifetime of the LSP was 0.

Procedure

1. Check whether the local device restarted.

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

2. Check whether IS-IS authentication configuration is changed on the device.

If so, go to Step 4. In this case, this log message is informational only, and no action is required.
If not, go to Step 3.

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

4. End.