ISIS-MIB is a standard MIB implemented based on RFC4444. Use this MIB to define MIB variables on managed devices according to associated IS-IS configuration at the CLI.

Root object

iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1).isisMIB(138)

Scalar objects

isisSysVersion (1.3.6.1.2.1.138.1.1.1.1)

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysVersion (1.3.6.1.2.1.138.1.1.1.1)	read-only	INTEGER	unknown(0), one(1)	IS-IS version number.	The value is fixed at one(1).

(1.3.6.1.2.1.138.1.1.1.2)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysLevelType

(1.3.6.1.2.1.138.1.1.1.2)

read-write

IsisLevel

level1(1),

level2(2),

level1and2(3)

IS level.

Supports only the read operation.

isisSysID (1.3.6.1.2.1.138.1.1.1.3)

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysID (1.3.6.1.2.1.138.1.1.1.3)	read-write	IsisSystemID	OCTET STRING (6)	System ID	Supports only the read operation.

isisSysMaxPathSplits (1.3.6.1.2.1.138.1.1.1.4)

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysMaxPathSplits (1.3.6.1.2.1.138.1.1.1.4)	read-write	Unsigned32	Unsigned32(1..32)	Maximum number of ECMP routes supported by IS-IS.	The value range and default value vary by device model. The object can be modified whether the value of isisSysAdminState is on(1).

isisSysMaxLSPGenInt (1.3.6.1.2.1.138.1.1.1.5)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysMaxLSPGenInt (1.3.6.1.2.1.138.1.1.1.5)

read-write

Unsigned32

Unsigned32(1..65235)

Maximum LSP generation interval supported by IS-IS.

This value must be smaller than isisSysMaxAge.

This value must be greater than any isisSysLevelMinLSPGenInt value (not implemented yet).

This value must be at least 300 seconds shorter than isisSysMaxAge (not implemented yet).

isisSysPollESHelloRate (1.3.6.1.2.1.138.1.1.1.6)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysPollESHelloRate (1.3.6.1.2.1.138.1.1.1.6)

read-write

IsisUnsigned16TC

Unsigned32(1..65535)

Maximum ES solicitation interval in ISH PDUs.

Supports only the read operation.

The value is fixed at 50.

isisSysWaitTime (1.3.6.1.2.1.138.1.1.1.7)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysWaitTime (1.3.6.1.2.1.138.1.1.1.7)

read-write

IsisUnsigned16TC

Unsigned32(1..65535)

Maximum time to wait for the IS to come up.

Supports only the read operation.

The value is fixed at 60.

isisSysAdminState (1.3.6.1.2.1.138.1.1.1.8)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysAdminState (1.3.6.1.2.1.138.1.1.1.8)

read-write

IsisAdminState

INTEGER {

on(1),

off(2)

}

Administrative state of the IS.

Supports only the read operation.

isisSysL2toL1Leaking (1.3.6.1.2.1.138.1.1.1.9)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysL2toL1Leaking (1.3.6.1.2.1.138.1.1.1.9)

read-write

TruthValue

true(1),

false(2)

Whether route leaking from Level-2 to Level-1 is allowed.

As per the MIB.

isisSysMaxAge (1.3.6.1.2.1.138.1.1.1.10)

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysMaxAge (1.3.6.1.2.1.138.1.1.1.10)	read-write	IsisUnsigned16TC	Unsigned32(350..65535)	LSP maximum age. The value must be 300 seconds longer than the maximum LSP generation interval.	The value must be larger than isisSysMaxLSPGenInt, and at least 300 seconds longer than isisSysMaxLSPGenInt.

isisSysReceiveLSPBufferSize(1.3.6.1.2.1.138.1.1.1.11)

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysReceiveLSPBufferSize(1.3.6.1.2.1.138.1.1.1.11)	read-write	IsisUnsigned16TC	Unsigned32(1492..16000)	LSP receiving buffer size.	Default: 1497.

isisSysProtSupported (1.3.6.1.2.1.138.1.1.1.12)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysProtSupported (1.3.6.1.2.1.138.1.1.1.12)

read-only

BITS

iso8473 (0), ipv4 (1), ipv6 (2)

Supported protocol type.

Supports only ipv4(1) and ipv6(2).

The return value is ipv6(2) when both IPv4 and IPv6 are supported.

isisSysNotificationEnable (1.3.6.1.2.1.138.1.1.1.13)

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisSysNotificationEnable (1.3.6.1.2.1.138.1.1.1.13)

read-write

TruthValue

true(1),

false(2)

Whether IS-IS SNMP notifications is enabled.

As per the MIB.

Tabular objects

isisManAreaAddrTable

About this table

This table contains information about manually configured area addresses.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table index is isisManAreaAddr.

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisManAreaAddr (1.3.6.1.2.1.138.1.1.2.1.1)

not-accessible

IsisOSINSAddress

OCTET STRING (0..20)

Manually configured area address.

As per the MIB.

isisManAreaAddrExistState (1.3.6.1.2.1.138.1.1.2.1.2)

read-create

RowStatus

active(1)

State of the manually configured area address.

Supports only the read operation.

Supports only active(1).

isisAreaAddrTable

About this table

This table contains information about reachable Level-1 area addresses.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table index is isisAreaAddr.

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisAreaAddr

(1.3.6.1.2.1.138.1.1.3.1.1)

read-only

IsisOSINSAddress

OCTET STRING (0..20)

Reachable Level-1 area address

A value is returned only when the value of isisSysLevelType is level1and2(3).

isisSummAddrTable

About this table

This table contains information about summarized addresses.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisSummAddressType, isisSummAddress, and isisSummAddrPrefixLen.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSummAddressType (1.3.6.1.2.1.138.1.1.4.1.1)	not-accessible	InetAddressType	INTEGER{ unknown(0), ipv4(1), ipv6(2), dns(16) }	Summary address type.	As per the MIB.
isisSummAddress (1.3.6.1.2.1.138.1.1.4.1.2)	not-accessible	InetAddress	OCTET STRING(0..255)	Summary address.	As per the MIB.
isisSummAddrPrefixLen (1.3.6.1.2.1.138.1.1.4.1.3)	not-accessible	InetAddressPrefixLength	Unsigned32(0..2040)	Prefix length of the summary address.	As per the MIB.
isisSummAddrExistState (1.3.6.1.2.1.138.1.1.4.1.4)	read-create	RowStatus	active(1)	State of the summary address.	Supports only the read operation. Support only active(1).
isisSummAddrMetric (1.3.6.1.2.1.138.1.1.4.1.5)	read-create	IsisDefaultMetric	Unsigned32(0..63)	Metric of the summary address.	Supports only the read operation. Default: 20.
isisSummAddrFullMetric (1.3.6.1.2.1.138.1.1.4.1.6)	read-create	IsisFullMetric	Unsigned32	Total metric (internal metric plus external metric) of the summary address.	Supports only the read operation. Default: 20.

isisRedistributeAddrTable

About this table

This table contains information about route leaking from Level-2 to Level-1.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisRedistributeAddrType, isisRedistributeAddrAddress, and isisRedistributeAddrPrefixLen.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisRedistributeAddrType (1.3.6.1.2.1.138.1.1.5.1.1)	not-accessible	InetAddressType	INTEGER{ unknown(0), ipv4(1), ipv6(2), dns(16) }	Redistributed address type.	As per the MIB.
isisRedistributeAddrAddress (1.3.6.1.2.1.138.1.1.5.1.2)	not-accessible	InetAddress	OCTET STRING(0..255)	Redistributed address.	As per the MIB.
isisRedistributeAddrPrefixLen (1.3.6.1.2.1.138.1.1.5.1.3)	not-accessible	InetAddressPrefixLength	Unsigned32(0..2040)	Prefix length of the redistributed address.	As per the MIB.
isisRedistributeAddrExistState (1.3.6.1.2.1.138.1.1.5.1.4)	read-create	RowStatus	active(1)	State of the redistributed address.	Supports only the read operation. Supports only active(1).

isisRouterTable

About this table

This table contains information about mappings between host names and system IDs.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisRouterSysID and isisRouterLevel.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisRouterSysID (1.3.6.1.2.1.138.1.1.6.1.1)	not-accessible	IsisSystemID	OCTET STRING (6)	System ID.	As per the MIB.
isisRouterLevel (1.3.6.1.2.1.138.1.1.6.1.2)	not-accessible	IsisISLevel	level1(1), level2(2), level1and2(3)	IS level.	As per the MIB.
isisRouterHostName (1.3.6.1.2.1.138.1.1.6.1.3)	read-only	SnmpAdminString	OCTET STRING (0..255)	Host name of the IS.	As per the MIB.
isisRouterID (1.3.6.1.2.1.138.1.1.6.1.4)	read-only	Unsigned32	Standard MIB values.	Router ID of the IS.	As per the MIB.

isisSysLevelTable

About this table

This table contains information about the specified IS level.

Support for operations

Create：Not supported

Edit/Modify：Supported

Delete：Not supported

Read：Supported

Columns

The table index is isisSysLevelIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysLevelIndex (1.3.6.1.2.1.138.1.2.1.1.1)	not-accessible	IsisISLevel	INTEGER{ area(1), domain(2) }	IS level.	As per the MIB.
isisSysLevelOrigLSPBuffSize (1.3.6.1.2.1.138.1.2.1.1.2)	read-write	IsisLSPBuffSize	Unsigned32(512..16000)	Maximum LSP size that can be generated by the specified IS level.	Default: 1497. The value must be smaller than isisSysReceiveLSPBufferSize. The object is modifiable whether the value of isisSysAdminState is on(1).
isisSysLevelMinLSPGenInt (1.3.6.1.2.1.138.1.2.1.1.3)	read-write	IsisUnsigned16TC	Unsigned32(1..65535)	Minimum LSP generation interval of the specified IS level.	Value range: 1 to 120. Default: 1. The return value is an integer. When the intelligent timer is configured, if the value is smaller than 1, the return value is 1.
isisSysLevelState (1.3.6.1.2.1.138.1.2.1.1.4)	read-only	IsisLevelState	off (1) on (2) waiting (3) overloaded(4)	Overload status of the specified IS level.	Supports only off(1), on(2), and overloaded(4).
isisSysLevelSetOverload (1.3.6.1.2.1.138.1.2.1.1.5)	read-write	TruthValue	true(1), false(2)	Whether the overload status is set for the specified IS level.	As per the MIB.
isisSysLevelSetOverloadUntil (1.3.6.1.2.1.138.1.2.1.1.6)	read-write	Unsigned32	Standard MIB values.	Most recent time when the specified IS level exits the overload status.	If the object is a non-zero value, the overload bit is set for this level when the isisSysAdminState variable enters "on" state (when the IS is not implemented yet).
isisSysLevelMetricStyle (1.3.6.1.2.1.138.1.2.1.1.7)	read-write	IsisMetricStyle	INTEGER{ narrow(1), wide(2), both(3) }	Cost style of the specified IS level.	As per the MIB.
isisSysLevelSPFConsiders (1.3.6.1.2.1.138.1.2.1.1.8)	read-write	IsisMetricStyle	INTEGER{ narrow(1), wide(2), both(3) }	Cost style used by the specified IS level during SPF calculation.	Supports only the read operation.
isisSysLevelTEEnabled (1.3.6.1.2.1.138.1.2.1.1.9)	read-write	TruthValue	true(1), false(2)	Whether TE is enabled for the specified IS level.	As per the MIB.

isisCirc

About this table

This table contains interface index information.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

This table has no indexes.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisNextCircIndex (1.3.6.1.2.1.138.1.3.1)	read-only	IndexIntegerNextFree	Unsigned32(0..4294967295)	Available interface index of the system.	As per the MIB.

isisCircTable

About this table

This table contains IS-IS interface information.

Support for operations

Create：Not supported

Edit/Modify：Supported

Delete：Not supported

Read：Supported

Columns

The table index is isisCircIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisCircIndex (1.3.6.1.2.1.138.1.3.2.1.1)	not-accessible	IndexInteger	Unsigned32(1..4294967295)	Interface index.	As per the MIB.
isisCircIfIndex (1.3.6.1.2.1.138.1.3.2.1.2)	read-create	InterfaceIndex	Integer32(1..2147483647)	Ifnet index of the interface.	Supports only the read operation.
isisCircAdminState (1.3.6.1.2.1.138.1.3.2.1.3)	read-create	IsisAdminState	INTEGER { on(1), off(2) }	Administrative state of the interface.	Supports only the read operation.
isisCircExistState (1.3.6.1.2.1.138.1.3.2.1.4)	read-create	RowStatus	active(1)	State of the interface.	Supports only the read operation. Supports only active(1).
isisCircType (1.3.6.1.2.1.138.1.3.2.1.5)	read-create	INTEGER	broadcast(1), ptToPt(2), staticIn(3), staticOut(4), dA(5)	Type of the interface.	Supports only the read operation. Supports only broadcast(1) and ptToPt(2). This value is broadcast(1) on a broadcast link, and is ptToPt (2) on other types of links.
isisCircExtDomain (1.3.6.1.2.1.138.1.3.2.1.6)	read-create	TruthValue	true(1), false(2)	Domain attribute of the interface.	Supports only the read operation. The value is fixed at false(2).
isisCircLevelType (1.3.6.1.2.1.138.1.3.2.1.7)	read-create	IsisLevel	level1(1), level2(2), level1and2(3)	Level of the interface.	Supports only the read and write operations.
isisCircPassiveCircuit (1.3.6.1.2.1.138.1.3.2.1.8)	read-create	TruthValue	true(1), false(2)	Whether the interface is disabled from advertising routes.	Supports only the read and write operations.
isisCircMeshGroupEnabled (1.3.6.1.2.1.138.1.3.2.1.9)	read-create	INTEGER	inactive(1), blocked(2), set(3)	Mesh group setting for the interface.	Supports only the read operation.
isisCircMeshGroup (1.3.6.1.2.1.138.1.3.2.1.10)	read-create	Unsigned32	Standard MIB values.	Mesh group number.	Supports only the read operation.
isisCircSmallHellos (1.3.6.1.2.1.138.1.3.2.1.11)	read-create	TruthValue	true(1), false(2)	Whether sending small hello packets is enabled.	Supports only the read and write operations.
isisCircLastUpTime (1.3.6.1.2.1.138.1.3.2.1.12)	read-only	TimeStamp	TimeTicks	Most recent up time of the interface.	As per the MIB.
isisCirc3WayEnabled (1.3.6.1.2.1.138.1.3.2.1.13)	read-create	TruthValue	true(1), false(2)	Whether three-way handshake is enabled.	Supports only the read operation.
isisCircExtendedCircID (1.3.6.1.2.1.138.1.3.2.1.14)	read-create	Unsigned32	Standard MIB values.	Unique interface ID during the three-way handshake process.	Supports only the read operation.

isisCircLevelTable

About this table

This table contains information about an interface of the specified circuit level.

Support for operations

Create：Not supported

Edit/Modify：Supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex and isisCircLevelIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisCircLevelIndex (1.3.6.1.2.1.138.1.4.1.1.1)	not-accessible	IsisISLevel	INTEGER{ area(1), domain(2) }	Circuit level of the interface.	As per the MIB.
isisCircLevelMetric (1.3.6.1.2.1.138.1.4.1.1.2)	read-write	IsisDefaultMetric	Unsigned32(0..63)	Internal cost of the interface of the specified circuit level.	Value range: 1 to 63.
isisCircLevelWideMetric (1.3.6.1.2.1.138.1.4.1.1.3)	read-write	IsisWideMetric	Unsigned32(0..16777215)	Total cost of the interface of the specified circuit level.	Value range: 1 to 16777215.
isisCircLevelISPriority (1.3.6.1.2.1.138.1.4.1.1.4)	read-write	IsisISPriority	Unsigned32(0..127)	DIS priority for the interface of the specified circuit level.	As per the MIB.
isisCircLevelIDOctet (1.3.6.1.2.1.138.1.4.1.1.5)	read-only	Unsigned32	Unsigned32(0..255)	Circuit ID of the interface (DIS).	As per the MIB.
isisCircLevelID (1.3.6.1.2.1.138.1.4.1.1.6)	read-only	IsisCircuitID	OCTET STRING(0\|7)	Unique circuit ID assigned to the interface.	The value is the isisSysID. For a P2P circuit, the value is isisCircLevelIDOctet that is one byte long. For a broadcast circuit, the value is a zero-length eight-byte string.
isisCircLevelDesIS (1.3.6.1.2.1.138.1.4.1.1.7)	read-only	IsisCircuitID	OCTET STRING(0\|7)	LAN ID for the DIS on the interface of the specified circuit level.	As per the MIB.
isisCircLevelHelloMultiplier (1.3.6.1.2.1.138.1.4.1.1.8)	read-write	Unsigned32	Unsigned32(2..100)	IS-IS hello multiplier.	Value range: 3 to 100. Default: 3.
isisCircLevelHelloTimer (1.3.6.1.2.1.138.1.4.1.1.9)	read-write	Unsigned32	Unsigned32(10..600000)	Hello packet sending interval.	Value range: 1000 to 255000. Default: 10000. When the value is divided by 1000, the decimal number will be ignored.
isisCircLevelDRHelloTimer (1.3.6.1.2.1.138.1.4.1.1.10)	read-write	Unsigned32	Unsigned32(10..120000)	Hello packet sending interval on the DIS.	Supports only the read operation. Value range: 1000 to 85000. Default: 3000. When the value is divided by 1000, the decimal number will be ignored.
isisCircLevelLSPThrottle (1.3.6.1.2.1.138.1.4.1.1.11)	read-write	IsisUnsigned16TC	Unsigned32(1..65535)	Minimum LSP sending interval.	Value range: 1 to 1000. Default: 33.
isisCircLevelMinLSPRetransInt (1.3.6.1.2.1.138.1.4.1.1.12)	read-write	Unsigned32	Unsigned32(1..300)	Minimum LSP retransmission interval	As per the MIB.
isisCircLevelCSNPInterval (1.3.6.1.2.1.138.1.4.1.1.13)	read-write	Unsigned32	Unsigned32(1..600)	Minimum CSNP sending interval	As per the MIB.
isisCircLevelPartSNPInterval (1.3.6.1.2.1.138.1.4.1.1.14)	read-write	Unsigned32	Unsigned32(1..120)	Minimum PSNP sending interval	Supports only the read operation. The value is fixed at 2.

isisSystemCounterTable

About this table

This table contains statistics information about the specified IS level.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table index is isisSysStatLevel.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisSysStatLevel (1.3.6.1.2.1.138.1.5.1.1.1)	not-accessible	IsisISLevel	INTEGER{ area(1), domain(2) }	IS level.	As per the MIB.
isisSysStatCorrLSPs (1.3.6.1.2.1.138.1.5.1.1.2)	read-only	Counter32	INTEGER(0..4294967295)	Number of error LSPs.	The value is fixed at 0.
isisSysStatAuthTypeFails (1.3.6.1.2.1.138.1.5.1.1.3)	read-only	Counter32	INTEGER(0..4294967295)	Number of authentication type errors.	As per the MIB.
isisSysStatAuthFails (1.3.6.1.2.1.138.1.5.1.1.4)	read-only	Counter32	INTEGER(0..4294967295)	Number of authentication failures.	As per the MIB.
isisSysStatLSPDbaseOloads (1.3.6.1.2.1.138.1.5.1.1.5)	read-only	Counter32	INTEGER(0..4294967295)	Number of LSDB overload times.	As per the MIB.
isisSysStatManAddrDropFromAreas (1.3.6.1.2.1.138.1.5.1.1.6)	read-only	Counter32	INTEGER(0..4294967295)	Number of times the manually configured area address is deleted from the local area.	As per the MIB.
isisSysStatAttmptToExMaxSeqNums (1.3.6.1.2.1.138.1.5.1.1.7)	read-only	Counter32	INTEGER(0..4294967295)	Number of times the LSP sequence number exceeds the maximum sequence number.	As per the MIB.
isisSysStatSeqNumSkips (1.3.6.1.2.1.138.1.5.1.1.8)	read-only	Counter32	INTEGER(0..4294967295)	Number of times the LSP sequence number is not continuous.	As per the MIB.
isisSysStatOwnLSPPurges (1.3.6.1.2.1.138.1.5.1.1.9)	read-only	Counter32	INTEGER(0..4294967295)	Number of times the system generates LSPs with a lifetime of 0.	As per the MIB.
isisSysStatIDFieldLenMismatches (1.3.6.1.2.1.138.1.5.1.1.10)	read-only	Counter32	INTEGER(0..4294967295)	Number of times the system receives LSPs with ID length changes.	As per the MIB.
isisSysStatPartChanges (1.3.6.1.2.1.138.1.5.1.1.11)	read-only	Counter32	INTEGER(0..4294967295)	Number of area address mismatches.	As per the MIB.
isisSysStatSPFRuns (1.3.6.1.2.1.138.1.5.1.1.12)	read-only	Counter32	INTEGER(0..4294967295)	Number of area split events.	As per the MIB.
isisSysStatLSPErrors (1.3.6.1.2.1.138.1.5.1.1.13)	read-only	Counter32	INTEGER(0..4294967295)	Number of SPF calculation events.	As per the MIB.

isisCircuitCounterTable

About this table

This table contains statistics information about interfaces of the specified circuit level.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex and isisCircuitType.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisCircuitType (1.3.6.1.2.1.138.1.5.2.1.1)	not-accessible	INTEGER	lanlevel1(1), lanlevel2(2), p2pcircuit(3)	Interface type.	As per the MIB.
isisCircAdjChanges (1.3.6.1.2.1.138.1.5.2.1.2)	read-only	Counter32	INTEGER(0..4294967295)	Neighbor change information.	As per the MIB.
isisCircNumAdj (1.3.6.1.2.1.138.1.5.2.1.3)	read-only	Unsigned32	Standard MIB values.	Number of neighbor changes.	As per the MIB.
isisCircInitFails (1.3.6.1.2.1.138.1.5.2.1.4)	read-only	Counter32	INTEGER(0..4294967295)	Number of interface initialization failures.	The value is fixed at 0.
isisCircRejAdjs (1.3.6.1.2.1.138.1.5.2.1.5)	read-only	Counter32	INTEGER(0..4294967295)	Number of adjacency creation failures.	As per the MIB.
isisCircIDFieldLenMismatches (1.3.6.1.2.1.138.1.5.2.1.6)	read-only	Counter32	INTEGER(0..4294967295)	Number of ID length changes in received IS-IS packets.	As per the MIB.
isisCircMaxAreaAddrMismatches (1.3.6.1.2.1.138.1.5.2.1.7)	read-only	Counter32	INTEGER(0..4294967295)	Number of area address mismatches.	As per the MIB.
isisCircAuthTypeFails (1.3.6.1.2.1.138.1.5.2.1.8)	read-only	Counter32	INTEGER(0..4294967295)	Number of authentication type errors.	As per the MIB.
isisCircAuthFails (1.3.6.1.2.1.138.1.5.2.1.9)	read-only	Counter32	INTEGER(0..4294967295)	Number of authentication errors of the same authentication type.	As per the MIB.
isisCircLANDesISChanges (1.3.6.1.2.1.138.1.5.2.1.10)	read-only	Counter32	INTEGER(0..4294967295)	Number of DIS changes.	As per the MIB.

isisPacketCounterTable

About this table

This table contains statistics information about received and sent IS-IS packets for the specified IS level.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex, isisPacketCountLevel, and isisPacketCountDirection.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisPacketCountLevel (1.3.6.1.2.1.138.1.5.3.1.1)	not-accessible	IsisISLevel	INTEGER{ area(1), domain(2) }	IS level.	As per the MIB.
isisPacketCountDirection (1.3.6.1.2.1.138.1.5.3.1.2)	not-accessible	INTEGER	sending(1), receiving(2)	Packet direction (sending or receiving).	As per the MIB.
isisPacketCountIIHello (1.3.6.1.2.1.138.1.5.3.1.3)	read-only	Counter32	INTEGER(0..4294967295)	Number of IS-IS packets received or sent.	As per the MIB.
isisPacketCountISHello (1.3.6.1.2.1.138.1.5.3.1.4)	read-only	Counter32	INTEGER(0..4294967295)	Number of hello packets received or sent.	The value is fixed at 0.
isisPacketCountESHello (1.3.6.1.2.1.138.1.5.3.1.5)	read-only	Counter32	INTEGER(0..4294967295)	Number of ES packets received or sent.	The value is fixed at 0.
isisPacketCountLSP (1.3.6.1.2.1.138.1.5.3.1.6)	read-only	Counter32	INTEGER(0..4294967295)	Number of LSPs received or sent.	As per the MIB.
isisPacketCountCSNP (1.3.6.1.2.1.138.1.5.3.1.7)	read-only	Counter32	INTEGER(0..4294967295)	Number of CSNPs received or sent.	As per the MIB.
isisPacketCountPSNP (1.3.6.1.2.1.138.1.5.3.1.8)	read-only	Counter32	INTEGER(0..4294967295)	Number of PSNPs received or sent.	As per the MIB.
isisPacketCountUnknown (1.3.6.1.2.1.138.1.5.3.1.9)	read-only	Counter32	INTEGER(0..4294967295)	Number of unknown IS-IS packets.	As per the MIB.

isisISAdjTable

About this table

This table contains neighbor information about the specified interface.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex and isisISAdjIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisISAdjIndex (1.3.6.1.2.1.138.1.6.1.1.1)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	Neighbor index.	As per the MIB.
isisISAdjState (1.3.6.1.2.1.138.1.6.1.1.2)	read-only	INTEGER	down (1), initializing (2), up (3), failed(4)	Neighbor state.	Supports only down(1), initializing(2), and up(3).
isisISAdj3WayState (1.3.6.1.2.1.138.1.6.1.1.3)	read-only	INTEGER	up (0), initializing (1), down (2), failed (3)	Neighbor state.	As per the MIB.
isisISAdjNeighSNPAAddress (1.3.6.1.2.1.138.1.6.1.1.4)	read-only	IsisOSINSAddress	OCTET STRING (0..20)	SNPA address of the neighbor.	As per the MIB.
isisISAdjNeighSysType (1.3.6.1.2.1.138.1.6.1.1.5)	read-only	INTEGER	l1IntermediateSystem(1), l2IntermediateSystem(2), l1L2IntermediateSystem(3), unknown(4)	System type of the neighbor.	Supports only l1IntermediateSystem(1), l2IntermediateSystem(2), and l1L2IntermediateSystem(3).
isisISAdjNeighSysID (1.3.6.1.2.1.138.1.6.1.1.6)	read-only	IsisSystemID	OCTET STRING (6)	System ID of the neighbor.	As per the MIB.
isisISAdjNbrExtendedCircID (1.3.6.1.2.1.138.1.6.1.1.7)	read-only	Unsigned32	Standard MIB values.	Circuit ID of the neighbor learned through three-way handshake.	As per the MIB.
isisISAdjUsage (1.3.6.1.2.1.138.1.6.1.1.8)	read-only	IsisLevel	level1(1), level2(2), level1and2(3)	IS level.	As per the MIB.
isisISAdjHoldTimer (1.3.6.1.2.1.138.1.6.1.1.9)	read-only	IsisUnsigned16TC	Unsigned32(1..65535)	Neighbor hold timer.	As per the MIB.
isisISAdjNeighPriority (1.3.6.1.2.1.138.1.6.1.1.10)	read-only	IsisISPriority	Unsigned32(0..127)	Neighbor priority.	As per the MIB.
isisISAdjLastUpTime (1.3.6.1.2.1.138.1.6.1.1.11)	read-only	TimeStamp	TimeTicks	Most recent neighbor up time.	As per the MIB.

isisISAdjAreaAddrTable

About this table

This table contains neighbor area information about the specified interface.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex, isisISAdjIndex, and isisISAdjAreaAddrIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisISAdjAreaAddrIndex (1.3.6.1.2.1.138.1.6.2.1.1)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	Neighbor area address index.	As per the MIB.
isisISAdjAreaAddress (1.3.6.1.2.1.138.1.6.2.1.2)	read-only	IsisOSINSAddress	OCTET STRING (0..20)	Neighbor area address.	As per the MIB.

isisISAdjIPAddrTable

About this table

This table contains IP address information in the hello packets from the specified neighbor of an interface.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex, isisISAdjIndex, and isisISAdjIPAddrIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisISAdjIPAddrIndex (1.3.6.1.2.1.138.1.6.3.1.1)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	Reachable IP address index of the neighbor.	As per the MIB.
isisISAdjIPAddrType (1.3.6.1.2.1.138.1.6.3.1.2)	read-only	InetAddressType	ipv4(1), ipv6(2)	Reachable IP address type of the neighbor.	Supports only ipv4(1) and ipv6(2). The local IS supports ipv6(2) only when it supports IPv6 functions.
isisISAdjIPAddrAddress (1.3.6.1.2.1.138.1.6.3.1.3)	read-only	InetAddress	OCTET STRING(0..255)	Reachable IP address of the neighbor.	As per the MIB.

isisISAdjProtSuppTable

About this table

This table contains protocol information supported by the specified neighbor of an interface.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisCircIndex, isisISAdjIndex, and isisISAdjProtSuppProtocol.

Object (OID)

Access

Syntax

Value range

Description

Implementation

isisISAdjProtSuppProtocol (1.3.6.1.2.1.138.1.6.4.1.1)

read-only

IsisSupportedProtocol

INTEGER{

iso8473(129),

ipV6(142),

ip(204)

}

Protocol type supported by the neighbor.

As per the MIB.

isisRATable

About this table

This table contains reachable NSAP address or address prefix information.

Support for operations

Create：Supported

Edit/Modify：Supported

Delete：Supported

Read：Supported

Columns

The table indexes are isisCircIndex and isisRAIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisRAIndex (1.3.6.1.2.1.138.1.7.1.1.1)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	Reachable address index.	As per the MIB.
isisRAExistState (1.3.6.1.2.1.138.1.7.1.1.2)	read-create	RowStatus	active(1)	Reachable address state.	The value is fixed at active(1).
isisRAAdminState (1.3.6.1.2.1.138.1.7.1.1.3)	read-create	IsisAdminState	INTEGER { on(1), off(2) }	Administrative state of the reachable address.	Default: on(1).
isisRAAddrPrefix (1.3.6.1.2.1.138.1.7.1.1.4)	read-create	IsisOSINSAddress	OCTET STRING (0..20)	Address prefix.	As per the MIB.
isisRAMapType (1.3.6.1.2.1.138.1.7.1.1.5)	read-create	INTEGER	none (1), explicit (2), extractIDI (3), extractDSP (4)	Address mapping type.	Default: none(1).
isisRAMetric (1.3.6.1.2.1.138.1.7.1.1.6)	read-create	IsisDefaultMetric	Unsigned32(0..63)	Metric value of the reachable address.	As per the MIB.
isisRAMetricType (1.3.6.1.2.1.138.1.7.1.1.7)	read-create	IsisMetricType	INTEGER{ internal(1), external(2) }	Metric type of the reachable address.	As per the MIB.
isisRASNPAAddress (1.3.6.1.2.1.138.1.7.1.1.8)	read-create	IsisOSINSAddress	OCTET STRING (0..20)	Reachable SNPA address.	As per the MIB.
isisRASNPAMask (1.3.6.1.2.1.138.1.7.1.1.9)	read-create	IsisOSINSAddress	OCTET STRING (0..20)	Subnet mask of the reachable SNPA address.	As per the MIB.
isisRASNPAPrefix (1.3.6.1.2.1.138.1.7.1.1.10)	read-create	IsisOSINSAddress	OCTET STRING (0..20)	Prefix of the reachable SNPA address.	As per the MIB.
isisRAType (1.3.6.1.2.1.138.1.7.1.1.11)	read-create	INTEGER	manual (1), automatic (2)	Reachable address type.	As per the MIB.

isisIPRATable

About this table

This table contains reachable IP address information.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisSysLevelIndex, isisIPRADestType, isisIPRADest, isisIPRADestPrefixLen, and isisIPRANextHopIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisIPRADestType (1.3.6.1.2.1.138.1.8.1.1.1)	not-accessible	InetAddressType	INTEGER{ unknown(0), ipv4(1), ipv6(2), dns(16) }	Reachable IP address type (manual/automatic).	As per the MIB.
isisIPRADest (1.3.6.1.2.1.138.1.8.1.1.2)	not-accessible	InetAddress	OCTET STRING(0..255)	Reachable IP address.	As per the MIB.
isisIPRADestPrefixLen (1.3.6.1.2.1.138.1.8.1.1.3)	not-accessible	InetAddressPrefixLength	Unsigned32(0..2040)	Prefix length of the reachable IP address.	As per the MIB.
isisIPRANextHopIndex (1.3.6.1.2.1.138.1.8.1.1.4)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	Next hop index of the reachable IP address.	As per the MIB.
isisIPRANextHopType (1.3.6.1.2.1.138.1.8.1.1.5)	read-create	InetAddressType	ipv4(1), ipv6(2)	Reachable next hop IP address type.	Supports only the read operation. Supports only ipv4(1) and ipv6(2).
isisIPRANextHop (1.3.6.1.2.1.138.1.8.1.1.6)	read-create	InetAddress	OCTET STRING(0..255)	Reachable next hop IP address.	Supports only the read operation.
isisIPRAType (1.3.6.1.2.1.138.1.8.1.1.7)	read-create	INTEGER	manual (1), automatic (2)	Reachable IP address type.	Supports only the read operation. The value is fixed at automatic(2).
isisIPRAExistState (1.3.6.1.2.1.138.1.8.1.1.8)	read-create	RowStatus	active(1)	Reachable IP address state.	Supports only the read operation. The value is fixed at active(1).
isisIPRAAdminState (1.3.6.1.2.1.138.1.8.1.1.9)	read-create	IsisAdminState	INTEGER { on(1), off(2) }	Administrative state of the reachable IP address.	Supports only the read operation. The value is fixed at on(1).
isisIPRAMetric (1.3.6.1.2.1.138.1.8.1.1.10)	read-create	IsisDefaultMetric	Unsigned32(0..63)	Internal metric value of the reachable IP address.	Supports only the read operation. Default: 0.
isisIPRAMetricType (1.3.6.1.2.1.138.1.8.1.1.11)	read-create	IsisMetricType	INTEGER{ internal(1), external(2) }	Metric type of the reachable IP address.	Supports only the read operation.
isisIPRAFullMetric (1.3.6.1.2.1.138.1.8.1.1.12)	read-create	IsisFullMetric	Unsigned32	Total metric value of the reachable IP address.	Supports only the read operation. Default: 0.
isisIPRASNPAAddress (1.3.6.1.2.1.138.1.8.1.1.13)	read-create	IsisOSINSAddress	OCTET STRING (0..20)	Reachable SNPA address.	Supports only the read operation. The value is always a zero-length string of eight bytes.
isisIPRASourceType (1.3.6.1.2.1.138.1.8.1.1.14)	read-only	INTEGER	static (1), direct (2), ospfv2 (3), ospfv3 (4), isis(5), rip(6), igrp(7), eigrp(8), bgp(9), other(10)	Route source (protocol that discovered the route).	Supports only static(1), direct(2), ospfv2(3), ospfv3(4), isis(5), rip(6), and bgp(9).

isisLSPSummaryTable

About this table

This table contains LSP summary information.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisLSPLevel and isisLSPID.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisLSPLevel (1.3.6.1.2.1.138.1.9.1.1.1)	not-accessible	IsisISLevel	INTEGER{ area(1), domain(2) }	LSP level.	As per the MIB.
isisLSPID (1.3.6.1.2.1.138.1.9.1.1.2)	not-accessible	IsisLinkStatePDUID	OCTET STRING (8)	LSP ID.	As per the MIB.
isisLSPSeq (1.3.6.1.2.1.138.1.9.1.1.3)	read-only	Unsigned32	Standard MIB values.	LSP sequence number.	As per the MIB.
isisLSPZeroLife (1.3.6.1.2.1.138.1.9.1.1.4)	read-only	TruthValue	true(1), false(2)	Whether the LSP is to be cleared (whether the remaining lifetime is 0).	As per the MIB.
isisLSPChecksum (1.3.6.1.2.1.138.1.9.1.1.5)	read-only	IsisUnsigned16TC	Unsigned32(1..65535)	LSP checksum.	As per the MIB.
isisLSPLifetimeRemain (1.3.6.1.2.1.138.1.9.1.1.6)	read-only	IsisUnsigned16TC	Unsigned32(1..65535)	Remaining lifetime of the LSP.	As per the MIB.
isisLSPPDULength (1.3.6.1.2.1.138.1.9.1.1.7)	read-only	IsisUnsigned16TC	Unsigned32(1..65535)	LSP packet length.	As per the MIB.
isisLSPAttributes (1.3.6.1.2.1.138.1.9.1.1.8)	read-only	IsisUnsigned8TC	Unsigned32(0..255)	ATT bit of the LSP.	As per the MIB.

isisLSPTLVTable

About this table

This table contains LSP TLV information.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Supported

Columns

The table indexes are isisLSPLevel, isisLSPID, and isisLSPTLVIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisLSPTLVIndex (1.3.6.1.2.1.138.1.9.2.1.1)	not-accessible	Unsigned32	Unsigned32(1..4294967295)	TLV index in the LSP.	As per the MIB.
isisLSPTLVSeq (1.3.6.1.2.1.138.1.9.2.1.2)	read-only	Unsigned32	Standard MIB values.	LSP sequence number.	As per the MIB.
isisLSPTLVChecksum (1.3.6.1.2.1.138.1.9.2.1.3)	read-only	IsisUnsigned16TC	Unsigned32(1..65535)	LSP TLV checksum.	As per the MIB.
isisLSPTLVType (1.3.6.1.2.1.138.1.9.2.1.4)	read-only	IsisUnsigned8TC	Unsigned32(0..255)	LSP TLV type.	As per the MIB.
isisLSPTLVLen (1.3.6.1.2.1.138.1.9.2.1.5)	read-only	IsisUnsigned8TC	Unsigned32(0..255)	LSP TLV length.	As per the MIB.
isisLSPTLVValue (1.3.6.1.2.1.138.1.9.2.1.6)	read-only	OCTET STRING	OCTET STRING (0..255)	LSP TLV value.	As per the MIB.

isisNotificationEntry

About this table

This table contains SNMP notifications information.

Support for operations

Create：Not supported

Edit/Modify：Not supported

Delete：Not supported

Read：Not supported

Columns

The table indexes are isisLSPLevel, isisLSPID, and isisLSPTLVIndex.

Object (OID)	Access	Syntax	Value range	Description	Implementation
isisNotificationSysLevelIndex (1.3.6.1.2.1.138.1.10.1.1)	accessible-for-notify	IsisLevel	level1(1), level2(2), level1and2(3)	IS level.	As per the MIB.
isisNotificationCircIfIndex (1.3.6.1.2.1.138.1.10.1.2)	accessible-for-notify	Unsigned32	Unsigned32(1..2147483647)	Interface index.	As per the MIB.
isisPduLspId (1.3.6.1.2.1.138.1.10.1.3)	accessible-for-notify	IsisLinkStatePDUID	OCTET STRING (8)	String that uniquely identifies a link state PDU.	As per the MIB.
isisPduFragment (1.3.6.1.2.1.138.1.10.1.4)	accessible-for-notify	IsisPDUHeader	OCTET STRING(0..64)	First 64 bytes in the PDU that triggers the notification.	As per the MIB.
isisPduFieldLen (1.3.6.1.2.1.138.1.10.1.5)	accessible-for-notify	IsisUnsigned8TC	Unsigned32(0..255)	System ID length in the received PDU.	As per the MIB.
isisPduMaxAreaAddress (1.3.6.1.2.1.138.1.10.1.6)	accessible-for-notify	IsisUnsigned8TC	Unsigned32(0..255)	Maximum address in the received PDU.	As per the MIB.
isisPduProtocolVersion (1.3.6.1.2.1.138.1.10.1.7)	accessible-for-notify	IsisUnsigned8TC	Unsigned32(0..255)	Protocol version in the received PDU.	As per the MIB.
isisPduLspSize (1.3.6.1.2.1.138.1.10.1.8)	accessible-for-notify	Unsigned32	Unsigned32(0..2147483647)	Size of the LSP that is too large to be forwarded.	As per the MIB.
isisPduOriginatingBufferSize (1.3.6.1.2.1.138.1.10.1.9)	accessible-for-notify	IsisUnsigned16TC	Unsigned32(0..16000)	Peer isisSysOrigLSPBuffSize value in the TLV.	As per the MIB.
isisPduBufferSize (1.3.6.1.2.1.138.1.10.1.10)	accessible-for-notify	IsisUnsigned16TC	Unsigned32(0..16000)	Maximum received LSP size.	As per the MIB.
isisPduProtocolsSupported (1.3.6.1.2.1.138.1.10.1.11)	accessible-for-notify	OCTET STRING	OCTET STRING (0..255)	Protocol list supported by the neighbor.	As per the MIB.
isisAdjState (1.3.6.1.2.1.138.1.10.1.12)	accessible-for-notify	INTEGER	down (1), initializing (2), up (3), failed(4)	Adjacency state.	As per the MIB.
isisErrorOffset (1.3.6.1.2.1.138.1.10.1.13)	accessible-for-notify	Unsigned32	Standard MIB values.	Offset of the error TLV.	As per the MIB.
isisErrorTLVType (1.3.6.1.2.1.138.1.10.1.14)	accessible-for-notify	Unsigned32	Unsigned32(0..255)	Type of the error TLV.	As per the MIB.
isisNotificationAreaAddress (1.3.6.1.2.1.138.1.10.1.15)	accessible-for-notify	IsisOSINSAddress	OCTET STRING (0..20)	Area address of the notification.	As per the MIB.

Notifications

isisDatabaseOverload

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.1	LSDB overload state changes.	Informational	Informational	N/A (N/A)	ON

Notification triggers

This notification is generated when the system enters or exits the overload status after one of the following events occurs:

Event 1: You configure the set-overload command or the undo set-overload command in IS-IS view.

Event 2: Memory application fails.

The number of times for generating and clearing this notification is recorded in isisSysStatLSPDbaseOloads.

System impact

If event 1 is the cause of this notification, route selection of IS-IS neighbors will be affected.

If event 2 is the cause of this notification, the IS-IS database is untrustable.

Status control

CLI: Use the snmp-agent trap enable isis lsdboverload-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable isis lsdboverload-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.2.1.1.4 (isisSysLevelState)	Overload state of the IS level.	isisSysLevelIndex	IsisLevelState	off (1), on (2), waiting (3), overloaded(4)

Recommended action

To resolve this issue:

1.Use the display this command in IS-IS view to identify whether the set-overload command is configured for the current IS-IS process:

- If the set-overload command is configured, no action is required.

- If the set-overload command is not configured, proceed to step 2.

2.Use the display history-command command in IS-IS view to identify whether the undo set-overload command is configured for the current IS-IS process:

- If the undo set-overload command is configured, no action is required.

- If the undo set-overload command is not configured, proceed to step 3.

3.Use the display memory command to view the memory usage on the device.

- If the device has high memory usage, proceed to step 4.

- If the device does not have high memory usage, proceed to step 5.

4.View log information on the device to determine the cause of high memory usage.

5.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisManualAddressDrops

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.2	This notification is generated for invalid area addresses.	Informational	Warning	N/A (N/A)	ON

Notification triggers

When IS-IS leaks Level-1 area addresses to the Level-2 area on a Level-1-2 device, the number of Level-2 area addresses might exceed three. In this situation, IS-IS keeps only the lowest three addresses as Level-2 area addresses. As a result, some local Level-2 area addresses might be discarded.

This notification might be generated when the Level-2 area has more than three area addresses after IS-IS leaks Level-1 area addresses to the Level-2 area on a Level-1-2 device.

The number of times for generating this notification is recorded in isisSysStatManAddrDropFromAreas.

The agent must throttle the generation of consecutive isisManualAddressDrops notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

Some local Level-2 area addresses might be discarded.

Status control

CLI: Use the snmp-agent trap enable isis manual-address-drop command.

OFF

CLI: Use the undo snmp-agent trap enable isis manual-address-drop command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.15 (isisNotificationAreaAddress)	Manually configured area addresses that have been dropped.	N/A	IsisOSINSAddress	OCTET STRING (0..20)

Recommended action

To resolve the issue:

1.Use the display isis lsdb level-1 verbose command to view detailed Level-1 LSDB information. View the Area address field in the command output. This field records the total number of Level-1 area addresses.

- If the total number of Level-1 area addresses is greater than 3, proceed to step 2.

- If the total number of Level-1 area addresses is less than 3, proceed to step 4.

2.Use the display isis lsdb level-2 verbose command to identify whether the Level-1 area addresses are the same as the Level-2 area addresses:

- If they are exactly the same, proceed to step 4.

- If some of them are different, proceed to step 3.

3.Use the undo network-entity command to reduce the number of invalid or unused area addresses, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 4.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisCorruptedLSPDetected

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.3	LSP errors.	Informational	Informational	N/A (N/A)	ON

Notification triggers

This notification is generated when an LSP stored in the memory is damaged. This issue might occur when a memory occurs and an LSP is changed within an LSP refresh interval.

The number of times for generating this notification is recorded in isisSysCorrLSPs.

System impact

If an LSP check failure occurs, the current IS-IS process will restart and the corresponding services will be interrupted.

Status control

CLI: Use the snmp-agent trap enable isis lsp-corrupt command.

OFF

CLI: Use the undo snmp-agent trap enable isis lsp-corrupt command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)

Recommended action

To resolve the issue:

1.Use the display memory command to view the value of the FreeRatio field. This field records the free memory ratio on the device.

- If the value is less than 80%, proceed to step 2.

- If the value is greater than 80%, proceed to step 3.

2.Use the reset isis all command to restart the current IS-IS process, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisAttemptToExceedMaxSequence

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.4	Attempts to exceed the maximum LSP sequence number	Informational	Informational	N/A (N/A)	ON

Notification triggers

This notification is generated when the sequence number of an LSP reaches or exceeds the maximum value, 65535. This issue might occur when the sequence number of an LSP generated by the local device reaches the maximum value, 0xFFFFFFFF.

The first six bytes of an LSP ID contain system ID information, and the remaining two bytes contain valid information.

System impact

When this notification is generated for an LSP three times in a row, IS-IS stops running temporarily to wait for the LSP to expire on other devices. By default, IS-IS stops running for 20 minutes, which is the maximum LSP age. After the LSP expires and is deleted from other devices, IS-IS continues to generate LSPs with sequence number starting from 1. As a result, some IS-IS routes will be deleted and incorrect traffic forwarding will occur.

Status control

CLI: Use the snmp-agent trap enable isis max-seq-exceeded command.

OFF

CLI: Use the undo snmp-agent trap enable isis max-seq-exceeded command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)

Recommended action

If the notification is cleared automatically, no action is required.

If the notification remains, perform the following tasks:

1.Wait for the LSP with sequence number 0xFFFFFFFF to expire. When IS-IS continues LSP generation, use the display isis lsdb local command multiple times to view the Seq Num field. This field displays the sequence number of an LSP generated by the local device.

- If the speed of LSP sequence number increment matches the LSP refresh interval, no action is required.

- If the LSP sequence number increases at a fast pace, proceed to step 2.

2.Identify whether the local device uses the same system ID or vSystem ID as another device in the routing domain:

- If yes, proceed to step 3.

- If no, proceed to step 4.

3.Perform the following tasks to clear the notification:

Enter the IS-IS view of the local device or the device that uses the same system ID or vSystem ID as the local device.

Use the undo network-entity command or the undo virtual-system command to remove the conflicting system ID or vSystem ID.

Use the network-entity command or the virtual-system command to specify a different system ID or vSystem ID.

Identify whether the notification is cleared:

If the notification is cleared, the troubleshooting is complete.

If the notification is not cleared, proceed to step 4.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisIDLenMismatch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.5	System ID length mismatches.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the device receives a PDU with different system ID length. This issue occurs when one of the following conditions exists:

The local device and the source device of the PDU support different system ID length values.

The value of the System ID Length field is changed.

This notification includes the index of the link through which the PDU is received and packet header information, which might help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisIDLenMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

Route flapping might occur.

If this notification is generated due to a device communication error, the local device and the source device of the PDU cannot establish a neighbor relationship or cannot learn routes from each other.

Status control

CLI: Use the snmp-agent trap enable isis id-length-mismatch command.

OFF

CLI: Use the undo snmp-agent trap enable isis id-length-mismatch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.5 (isisPduFieldLen)	System ID length in the received PDU.	N/A	IsisUnsigned8TC	Unsigned32 (0..255)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.Check the IS-IS PDU format defined by ISO 10589, find the pdu-fragment field in the notification, and then identify whether the system ID length of the source device is neither 0 nor 6:

- If the system ID length of the source device is neither 0 nor 6, proceed to step 2.

- If the system ID length of the source device is 0 or 6, proceed to step 3.

The method to find the system ID varies by IS-IS PDU type as follows:

- For hello PDUs, the value for the fifth byte of the pdu-fragment field is 0f, 10, or 11. The System ID portion in the pdu-fragment field is the consecutive 6 bytes from the tenth byte to the fifteenth byte.

- For LSPs, the value for the fifth byte of the pdu-fragment field is 12 or 14. The System ID portion in the pdu-fragment field is the consecutive 6 bytes from the thirteenth byte to the eighteenth byte.

- For SNPs, the value for the fifth byte of the pdu-fragment field is 18, 19, 1A, or 1B. The System ID portion in the pdu-fragment field is the consecutive 6 bytes from the eleventh byte to the sixteenth byte.

2.Change the system ID length of the source device to 6, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisMaxAreaAddressesMismatch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.6	Maximum area address mismatches.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the device receives a PDU with MaxAreaAddresses value mismatch. The MaxAreaAddresses field of a PDU records the maximum number of area addresses supported by the source device. This issue occurs when one of the following conditions exists:

The local device and the source device of the PDU support different quantities of area addresses.

The value of the MaxAreaAddresses field is changed.

This notification includes packet header information, which might help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisMaxAreaAddressesMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

Route flapping might occur and the CPU usage of the device will rise.

If this notification is generated due to a device communication error, the local device and the source device of the PDU cannot establish a neighbor relationship and therefore cannot learn routes from each other.

Status control

CLI: Use the snmp-agent trap enable isis maxarea-mismatch command.

OFF

CLI: Use the undo snmp-agent trap enable isis maxarea-mismatch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.6 (isisPduMaxAreaAddress)	Maximum address in the received PDU.	N/A	IsisUnsigned8TC	Unsigned32 (0..255)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.Check the IS-IS packet format defined by ISO 10589, and then find the system ID of the source device in the pdu-fragment field of the notification.

The method to find the system ID varies by IS-IS PDU type as follows:

2.Identify whether the value of the pdu-max-area field in the notification is neither 0 nor 3:

- If the system ID length of the source device is neither 0 nor 3, proceed to step 3.

- If the system ID length of the source device is 0 or 3, proceed to step 4.

3.Change the maximum number of area addresses supported by the source device to 3, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 4.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisOwnLSPPurge

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.7	Attempts to remove the local LSP.	Informational	Informational	N/A (N/A)	ON

Notification triggers

This notification is generated when the device receives a PDU with the local system ID and a lifetime value of 0. This issue occurs when one of the following conditions exists:

The local device does not refresh its LSPs timely. After these LSPs expire, LSP purge packets are generated and are flooded to the local device.

The PDU is rewritten due to a transmission error, which triggers LSP purging.

After the local device restarts, it receives an LSP with the local system ID and a lifetime value of 0.

This notification includes the link index and router ID, which may help a network manager identify the source of the PDU.

System impact

If this notification occurs after the device restarts, you can ignore this notification.

If this notification occurs frequently, IS-IS routing will be interrupted and packet forwarding might fail.

Status control

CLI: Use the snmp-agent trap enable isis own-lsp-purge command.

OFF

CLI: Use the undo snmp-agent trap enable isis own-lsp-purge command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)

Recommended action

To resolve the issue:

1.Identify whether the local device restarted:

- If the local device restarted, no action is required.

- If the local device did not restart, proceed to step 2.

2.Identify whether an IS-IS authentication configuration change occurred on non-local devices. Such a change leads to the generation of LSP purge packets and triggers this notification.

- If an IS-IS authentication configuration change occurred on non-local devices, no action is required.

- If no IS-IS authentication configuration change occurred on non-local devices, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisSequenceNumberSkip

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.8	LSP sequence number duplications.	Informational	Informational	N/A (N/A)	ON

Notification triggers

When an IS-IS process on the local device receives a PDU with the local system ID and different content, the system might redeploy the LSP by using a greater sequence number. This notification is generated when the sequence number increases by a value greater than 1. This issue occurs when one of the following conditions exists:

After an IS-IS process restarts, it generates LSPs whose sequence numbers increase from 1. The IS-IS process then receives a neighbor LSP with the local system ID and a greater sequence number.

LSP updates occur frequently, because the local device uses the same system ID as another device.

When two ISs has the same system ID, a large number of such notifications will be generated.

System impact

If this notification occurs after the device restarts, you can ignore this notification.

If this notification occurs due to incorrect system ID configuration, route flapping might occur frequently.

Status control

CLI: Use the snmp-agent trap enable isis skip-sequence-number command.

OFF

CLI: Use the undo snmp-agent trap enable isis skip-sequence-number command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)

Recommended action

To resolve this issue:

1.Use the display history-command command in IS-IS view to identify whether the reset isis all command was configured to restart the current IS-IS process:

- If the reset isis all command is configured, no action is required.

- If the reset isis all command is not configured, proceed to step 2.

2.Use the display isis lsdb command multiple times to identify whether the value for the Seq Num field increases at a fast pace. This field displays the sequence number of an LSP generated by the local device.

- If the value for the Seq Num field increases at a fast pace, the real LSP refresh interval is shorter than the LSP refresh interval specified with the timer lsp-refresh command. In this situation, proceed to step 3.

- If the value for the Seq Num field increases at a normal pace, proceed to step 5.

3.Identify whether the local device uses the same system ID or vSystem ID as another device on the network:

- If yes, proceed to step 4.

- If no, proceed to step 5.

4.Perform the following tasks to clear the notification:

Enter the IS-IS view of the local device or the device that uses the same system ID or vSystem ID as the local device.

Use the undo network-entity command or the undo virtual-system command to remove the conflicting system ID or vSystem ID.

Use the network-entity command or the virtual-system command to specify a different system ID or vSystem ID.

Identify whether the notification is cleared:

If the notification is cleared, the troubleshooting is complete.

If the notification is not cleared, proceed to step 5.

5.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisAuthenticationTypeFailure

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.9	Authentication type errors.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the following conditions exist:

An authentication mode is configured for the IS-IS process on the local device.

The IS-IS process receives one of the following PDUs:

LSP, CSNP, PSNP, or hello PDU that does not contain any authentication.

This issue occurs when the local device is configured with an IS-IS authentication mode and the source device of the PDU does not have any IS-IS authentication configuration. You can configure IS-IS authentication on an interface or IS-IS process.

Packet with authentication type mismatch.

This issue occurs when the local device and the source device of the PDU use different IS-IS authentication modes. You can configure IS-IS authentication on an interface or IS-IS process. For example, the authentication type is MD5 for the local device and is Simple for the source device of the PDU.

This notification includes packet header information, which may help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisAuthenticationTypeFailure notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

If this notification occurs due to a hello PDU authentication failure, the local device and the source device of the PDU cannot establish a neighbor relationship.

If this notification occurs due to an LSP or SNP authentication failure, the local device and the source device of the PDU can establish a neighbor relationship, but they cannot synchronize LSDB information.

Status control

CLI: Use the snmp-agent trap enable isis authentication-type command.

OFF

CLI: Use the undo snmp-agent trap enable isis authentication-type command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve this issue:

1.View the following fields in the notification:

sysInstance—This field displays the ID of the IS-IS process that received the incorrect PDU.

sysLevel—This field displays the IS level of the received PDU.

IfName—This field displays the interface that received the incorrect PDU. You can find this field according to the IS-IS PDU format defined by ISO 10589.

PduFrag—This field displays the PDU type and the system ID of the source device.

If the PDU type is hello, proceed to steps 2 and 3.

If the PDU type is LSP or SNP, proceed to step 5.

The method to find the system ID varies by IS-IS PDU type as follows:

2.Use the display isis peer command on the source device to view the interface that sent the PDU.

3.In the view of the interface that sent the PDU, use the display this command on the source device to identify whether the interface is configured with an IS-IS authentication mode. Then, compare the authentication mode with that of the local interface that received the PDU.

- If the two authentication modes are different, proceed to step 4.

- If the two authentication modes are the same, the troubleshooting is complete.

4.In the view of the interface that sent the PDU, use the isis authentication-mode command to change its authentication mode. This operation ensures that the interface and the local interface can use the same authentication mode and the same authentication key.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 7.

5.Use the display current-configuration configuration isis command on the source device to identify whether the IS-IS process is configured with an area or routing domain authentication mode. Then, compare the authentication mode with that of the local device.

- If the source device and the local device use the same authentication mode and the same authentication key, the troubleshooting is complete.

- If the source device and the local device use different authentication modes, proceed to step 6.

6.In the IS-IS view of the source device, use the area-authentication-mode command or the domain-authentication-mode command to change its area or routing domain authentication mode. This operation ensures that the source device and the local device can use the same area or routing domain authentication mode and the same authentication key.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 7.

7.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisAuthenticationFailure

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.10	Authentication failures.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the IS-IS process on the local device is configured with an authentication mode and receives an LSP, CSNP, PSNP, or hello PDU that meet the following requirements:

The PDU and the local IS-IS process use the same authentication mode.

The PDU and the local IS-IS process use different authentication keys.

This issue occurs when the local device and the source device of the PDU use the same authentication mode but different authentication keys. You can configure IS-IS authentication on an interface or IS-IS process.

This notification includes packet header information, which may help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisAuthenticationFailure notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

If this notification occurs due to a hello PDU authentication failure, the local device and the source device of the PDU cannot establish a neighbor relationship.

Status control

CLI: Use the snmp-agent trap enable isis authentication command.

OFF

CLI: Use the undo snmp-agent trap enable isis authentication command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.View the following fields in the notification:

sysInstance—This field displays the ID of the IS-IS process that received the incorrect PDU.

sysLevel—This field displays the IS level of the received PDU.

IfName—This field displays the interface that received the incorrect PDU. You can find this field according to the IS-IS PDU format defined by ISO 10589.

PduFrag—This field displays the PDU type and the system ID of the source device.

If the PDU type is hello, proceed to step 2.

If the PDU type is LSP or SNP, proceed to step 4.

The method to find the system ID varies by IS-IS PDU type as follows:

2.Use the display isis peer command on the source device to view the interface that sent the PDU.

In the view of the interface that sent the PDU, use the display this command on the source device to identify the authentication mode of the interface.

3.In the view of the source interface or the local interface, use the isis authentication-mode command to change its authentication mode. This operation ensures that the two interfaces can use the same authentication mode and the same authentication key.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 6.

4.Use the display current-configuration configuration isis command on the source device to identify whether the IS-IS process is configured with an area or routing domain authentication mode.

5.In the IS-IS view of the source device or the local device, use the area-authentication-mode command or the domain-authentication-mode command to change its authentication mode and authentication key. This operation ensures that the two devices can use the same area or routing domain authentication mode and the same authentication key.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 6.

6.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisVersionSkew

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.11	Hello packet version mismatches.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device receives a hello PDU with IS-IS version number mismatch. This issue occurs when one of the following conditions exists:

The local device and the source device of the hello PDU support different IS-IS versions.

The IS-IS version number of the PDU is changed during transmission.

This notification includes packet header information, which may help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisVersionSkew notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

If this notification is generated because the IS-IS version number of the PDU was changed, route flapping might occur and the CPU usage of the device will rise.

Status control

CLI: Use the snmp-agent trap enable isis version-skew command.

OFF

CLI: Use the undo snmp-agent trap enable isis version-skew command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.7 (isisPduProtocolVersion)	Protocol version in the received PDU.	N/A	IsisUnsigned8TC	Unsigned32 (0..255)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve this issue:

1.Check the IS-IS PDU format defined by ISO 10589, and then find the system ID of the source device in the pdu-fragment field of the notification.

The method to find the system ID varies by IS-IS PDU type as follows:

2.Identify whether the value of the version field in the notification is 1 on the source device:

- If the value of the version field is 1, proceed to step 5.

- If the value of the version field is not 1, proceed to step 3.

3.Identify whether you can edit the IS-IS version number of the source device:

- If the IS-IS version number of the source device is editable, proceed to step 4.

- If the IS-IS version number of the source device is not editable, proceed to step 5.

4.Change the IS-IS version number of the source device to that of the local device, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 5.

5.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisAreaMismatch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.12	Area address mismatches.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device receives a hello PDU with area address mismatch. This issue occurs when one of the following conditions exists:

An area address configuration error exists.

The area addresses of the hello PDU is changed during transmission.

This notification includes packet header information, which may help a network manager identify the source of the PDU.

The agent must throttle the generation of consecutive isisAreaMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

Route flapping might occur and the CPU usage of the device will rise.

If this notification is generated due to an area address configuration error, the local device and the source device of the PDU cannot establish a neighbor relationship and therefore cannot learn routes from each other.

Status control

CLI: Use the snmp-agent trap enable isis area-mismatch command.

OFF

CLI: Use the undo snmp-agent trap enable isis area-mismatch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.Check the IS-IS PDU format defined by ISO 10589, and then find the system ID of the source device in the pdu-fragment field of the notification.

The method to find the system ID varies by IS-IS PDU type as follows:

2.In the IS-IS view of the source device, use the display this command to identify whether the source device and the local device use the same area addresses:

- If the source device and the local device use the same area addresses, proceed to step 4.

- If the source device and the local device do not use the same area addresses, proceed to step 3.

3.In the IS-IS view of the source device, use the network-entity command to change its area addresses. This operation ensures that the source device and the local device can use the same area addresses.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 4.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisRejectedAdjacency

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.13	Adjacency creation failures.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device cannot establish a neighbor relationship with a remote device upon receiving a hello PDU from that remote device.

The agent must throttle the generation of consecutive isisRejectedAdjacency notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

The local device cannot establish a neighbor relationship with the source device of the hello PDU.

Status control

CLI: Use the snmp-agent trap enable isis rejected-adjacency command.

OFF

CLI: Use the undo snmp-agent trap enable isis rejected-adjacency command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.View the IfName field of the notification to determine the interface that received the hello PDU.

- If the network type of the interface is broadcast, proceed to steps 2 and 3.

- If the network type of the interface is P2P, proceed to step 7.

2.Check the IS-IS PDU format defined by ISO 10589, and then find the system ID of the source device in the pdu-fragment field of the notification. The System ID portion in the pdu-fragment field is the consecutive 6 bytes from the tenth byte to the fifteenth byte.

3.Use the display this command in the interface view and the IS-IS view of the source device to view its IS-IS level and circuit level.

Use the display this command in the interface view and the IS-IS view of the local device to view its IS-IS level and circuit level.

Identify whether the source device and the local device use the same IS-IS level and circuit level.

- If they use the same IS-IS level and circuit level, proceed to step 4.

- If they do not use the same IS-IS level and circuit level, proceed to step 7.

4.Use the isis circuit-level command in the interface view of the source device or the local device to change its IS-IS level and circuit level, so the two devices can use the same IS-IS level and circuit level.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 5.

5.Use the display ip interface command to identify the IP address of the source interface and that of the local interface are in the same network segment. The local interface refers to the interface that received the hello PDU on the local device and the source interface refers to the interface that sent the hello PDU on the source device.

- If the two interface addresses are in the same network segment, proceed to step 8.

- If the two interface addresses are in different network segments, proceed to step 6.

6.Use the ip address command in the interface view of the source device or the local device to specify a new interface address. This operation ensures that the IP address of the source interface and that of the local interface can be in the same network segment.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 8.

7.Identify whether the source device and the local device use the same Level-1 area addresses.

- If they use the same Level-1 area addresses, proceed to step 10.

- If they do not use the same Level-1 area addresses, proceed to step 8.

8.Use the network-entity command in the IS-IS view of the source device to change its Level-1 area addresses, so the source device and the local device can use the same Level-1 area addresses. Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 9.

9.Use the display current-configuration command to identify whether the source device uses the same system ID or vSystem ID as the local device:

- If yes, proceed to step 10.

- If no, proceed to step 12.

10.Use the network-entity command or the virtual-system command to specify a different system ID or vSystem ID for the source device or the local device. This operation ensures that the two devices use different system IDs or vSystem IDs.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 11.

11.Use the display this command in the interface view of the local interface and the source interface to identify whether the two interfaces use the same IS-IS authentication mode:

- If they use the same IS-IS authentication mode, proceed to step 13.

- If they do not use the same IS-IS authentication mode, proceed to step 12.

12.Use the isis authentication-mode command on the local interface or the source interface to change its authentication mode and authentication key. This operation ensures that the two interfaces use the same IS-IS authentication configuration. Alternatively, you can use the undo isis authentication-mode command on both the local interface and the source interface to remove their IS-IS authentication configurations.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 13.

13.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisLSPTooLargeToPropagate

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.14	Propagation failures caused by oversized LSPs.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device attempts to propagate a PDU larger than the link MTU. This issue might occur when the device forwards an LSP larger than the MTU of the output interface.

The agent must throttle the generation of consecutive isisLSPTooLargeToPropagate notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

LSP loss occurs.

Status control

CLI: Use the snmp-agent trap enable isis lsp-size-exceeded command.

OFF

CLI: Use the undo snmp-agent trap enable isis lsp-size-exceeded command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.8 (isisPduLspSize)	Size of the LSP that is too large to be forwarded.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)

Recommended action

To resolve the issue:

1.Use the display ip interface interface-type interface-number command to view the value of the The Maximum Transmit Unit field. This field displays the MTU of an interface.

2.Use the display current-configuration configuration isis command in the current IS-IS process to view the configuration of the lsp-length originate command. If the lsp-length originate command is not configured for the IS-IS process, the maximum LSP length equals the default value, 1497 bytes.

- If the maximum LSP length is greater than the interface MTU, proceed to step 3.

- If the maximum LSP length is less than the interface MTU, proceed to step 4.

3.Use the lsp-length originate command in IS-IS view to change the maximum LSP length to a value less than the interface MTU. Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 4.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisOrigLSPBuffSizeMismatch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.15	Buffer size mismatches of IS-IS packets.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device receives an LSP (Level-1 or Level-2) that is larger than the local isisSysLevelOrigLSPBuffSize value or has a Buffer Size value not matching the local isisSysLevelOrigLSPBuffSize value. This issue might occur when the device receives an LSP larger than the size of the local buffer for received LSPs.

The agent must throttle the generation of consecutive isisOrigLSPBuffSizeMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

The local device cannot learn routes from the received LSP, which affects traffic forwarding.

Status control

CLI: Use the snmp-agent trap enable isis buffsize-mismatch command.

OFF

CLI: Use the undo snmp-agent trap enable isis buffsize-mismatch command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)
1.3.6.1.2.1.138.1.10.1.9 (isisPduOriginatingBufferSize)	Peer isisSysOrigLSPBuffSize value in the TLV.	N/A	IsisUnsigned16TC	Unsigned32 (0..16000)
1.3.6.1.2.1.138.1.10.1.10 (isisPduBufferSize)	Maximum received LSP size.	N/A	IsisUnsigned16TC	Unsigned32 (0..16000)

Recommended action

To resolve the issue:

1.Use the display current-configuration configuration isis command in the IS-IS process of the local device to view the configuration of the lsp-length receive command. If the lsp-length receive command is not configured for the IS-IS process, the maximum length of received LSPs equals the default value, 1497 bytes.

2.Use the LSP ID in the lsp-id field of the notification to find the source device of the received LSP.

Then, use the display current-configuration configuration isis command in the IS-IS process of the source device to view the configuration of the lsp-length originate command. If the lsp-length originate command is not configured for the IS-IS process, the maximum length of generated LSPs equals the default value, 1497 bytes.

3.Identify whether the maximum length of received LSPs is less than that of generated LSPs:

- If the maximum length of received LSPs is less than that of generated LSPs, proceed to step 4.

- If the maximum length of received LSPs is greater than that of generated LSPs, proceed to step 7.

4.Choose one of the following operations as needed:

- If the buffer size for LSPs received on the local device equals the default value, proceed to step 5.

- If the maximum length of received LSPs on the source device equals the default value, proceed to step 6.

5.Use the lsp-length originate command in the IS-IS process of the source device to change the maximum length of generated LSPs. This operation ensures that the maximum length of LSPs generated by the source device is not greater than the buffer size for LSPs received on the local device.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 7.

6.Use the lsp-length receive command in the IS-IS process of the local device to change the maximum length of received LSPs. This operation ensures that the maximum length of LSPs received on the local device is not less than the maximum length of LSPs generated by the source device.

Then, identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 7.

7.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisProtocolsSupportedMismatch

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.16	Supported-protocol mismatches.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device receives an LSP that carries a TLV (type value: 0x81) and the TLV supports different protocols from the local device. This issue might occur when the local device and the source device of the LSP support different protocols.

The agent must throttle the generation of consecutive isisProtocolsSupportedMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.

System impact

The local device cannot learn routes from the received LSP.

Status control

CLI: Use the snmp-agent trap enable isis protocol-support command.

OFF

CLI: Use the undo snmp-agent trap enable isis protocol-support command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.11 (isisPduProtocolsSupported)	Protocol list supported by the neighbor.	N/A	OCTET STRING	OCTET STRING (0..255)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)

Recommended action

To resolve the issue:

1.Wait for 10 minutes after you receive the notification, and then identify whether the notification is cleared:

- If the notification is cleared, the troubleshooting is complete.

- If the notification is not cleared, proceed to step 2.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisAdjacencyChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.17	IS-IS adjacency status changes.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when a neighbor enters or exits UP state. This issue occurs when one of the following conditions exists:

An IS-IS adjacency goes up or goes down.

An IS-IS configuration error exists.

The system is so busy that an IS-IS neighbor relationship flaps.

The state of an IS-IS neighbor relationship changes due to link failure.

The isisAdjState variable represents the most recent state of the neighbor.

System impact

IS-IS might recalculate routes, which causes route flapping and traffic flapping.

Status control

CLI: Use the snmp-agent trap enable isis adjacency-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable isis adjacency-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)
1.3.6.1.2.1.138.1.10.1.12 (isisAdjState)	Adjacency state.	isisCircIndex, isisISAdjIndex	INTEGER	down (1), initializing (2), up (3), failed(4)
1.3.6.1.2.1.31.1.1.1.1 (ifName)	Interface name.	ifIndex	DisplayString	OCTET STRING(0..255)

Recommended action

To resolve the issue:

1.Check the IS-IS PDU format defined by ISO 10589, obtain the system ID of the source device from the LspID field of the notification, and then identify whether the neighbor states of the source device and the local device are as configured.

- If yes, proceed to step 12.

- If no, proceed to step 2.

2.Download the user log of the source device, and then find the cause of the neighbor state change.

- If the neighbor state change occurs because of an interface down event, proceed to step 3.

- If the neighbor state change is not caused by an interface down event, proceed to step 10.

3.Find information about the local interface, check its state, and make sure both the local interface and the source interface are up. The local interface refers to the interface that received the LSP on the local device and the source interface refers to the interface that sent the LSP on the source device.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 4.

4.View the system IDs of the source device and the local device, and make sure their system IDs are configured correctly.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 5.

5.View the IS level of the IS-IS process on the source device and the IS level of the IS-IS process on the local device. Make sure the two IS levels are the same.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 6.

6.View the area IDs of the source device and the local device, and make sure their area IDs are the same.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 7.

7.View the IP addresses of the source interface and the local interface, and make sure their addresses are in the same network segment.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 8.

8.Identify whether the source device and the local device has IS-IS authentication configuration, and make sure they use the same IS-IS authentication mode and authentication key.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 9.

9.Identify whether the source device and the local device can receive and send hello packets, and make sure they can receive and send hello packets.

Then, identify whether the neighbor states of the source device and the local device are as configured.

- If yes, the troubleshooting is complete.

- If no, proceed to step 10.

10.Use the display cpu-usage command to identify whether the CPU usage remained 100% during a period.

- If yes, proceed to step 11.

- If no, proceed to step 12.

11.Use the isis timer hello command in interface view to prolong the interval for sending hello packets. This operation slows down network failure detection and route convergence.

- If yes, the troubleshooting is complete.

- If no, proceed to step 12.

12.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

isisLSPErrorDetected

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.138.0.18	LSP packet parse failures.	Informational	Warning	N/A (N/A)	ON

Notification triggers

This notification is generated when the local device fails to parse a received LSP. This issue occurs when one of the following conditions exists:

The LSP carries a malformed TLV.

The LSP has a header error.

The LSP is of unknown type.

The checksum of the LSP is 0.

A checksum error occurs.

isisCircIfIndex records the index of the link that received the PDU. isisPduFragment records the starting bytes of the PDU. isisErrorOffset indicates the problem.

System impact

The local device cannot learn routes from the received LSP.

Status control

CLI: Use the snmp-agent trap enable isis lsp-parse-error command.

OFF

CLI: Use the undo snmp-agent trap enable isis lsp-parse-error command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.138.1.10.1.1 (isisNotificationSysLevelIndex)	IS level index.	N/A	IsisLevel	level1(1), level2(2), level1and2(3)
1.3.6.1.2.1.138.1.10.1.3 (isisPduLspId)	String that uniquely identifies a link state PDU.	N/A	IsisLinkStatePDUID	OCTET STRING (8)
1.3.6.1.2.1.138.1.10.1.2 (isisNotificationCircIfIndex)	Interface index.	N/A	Unsigned32	Unsigned32(1..2147483647)
1.3.6.1.2.1.138.1.10.1.4 (isisPduFragment)	First 64 bytes in the PDU that triggers the notification.	N/A	IsisPDUHeader	OCTET STRING (0..64)
1.3.6.1.2.1.138.1.10.1.13 (isisErrorOffset)	Offset of the error TLV.	N/A	Unsigned32	Standard MIB values.
1.3.6.1.2.1.138.1.10.1.14 (isisErrorTLVType)	Type of the error TLV.	N/A	Unsigned32	Unsigned32(0..255)

Recommended action

To resolve the issue:

1.Use the display isis packet command to view IS-IS packet statistics, determine the cause of the LSP error, and then correct the corresponding configurations accordingly.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

09-Layer 3 - IP Routing

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

About this table

Support for operations

Columns

Basic information

Notification triggers

System impact

Status control

Object

Recommended action

Basic information

Notification triggers

System impact

Status control

Object

Recommended action

Basic information

Notification triggers

System impact

Status control