ISIS-DRAFT-25-MIB

Monitored by Observium
        This document describes a management information base for
the IS-IS Routing protocol, as described in ISO 10589,
when it is used to construct routing tables for IP
networks, as described in RFC 1195.
        
This document is based on a 1994 IETF draft by Chris
Gunner.  This version has been modified to include
current syntax, to exclude portions of the protocol that
are not relevant to IP, and to add management support for
current practice.
        
Copyright (C) The Internet Society (2005).  This version
of this MIB module is part of RFC 0DDD;  see the RFC
itself for full legal notices.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Routing
Explore Observium network monitoring
Source file
ISIS-DRAFT-25-MIB
Last revised
Identity
isisMIB
Base OID
1.3.6.1.3.37
Imported Objects
DIFFSERV-MIB IndexInteger IndexIntegerNextFree
IF-MIB InterfaceIndex
INET-ADDRESS-MIB InetAddress InetAddressPrefixLength InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 experimental MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the extreme MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ISIS-DRAFT-25-MIB' -M '/opt/observium/mibs/extreme:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ISIS-DRAFT-25-MIB::isisMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ISIS-DRAFT-25-MIB' -M '/opt/observium/mibs/extreme:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ISIS-DRAFT-25-MIB::isisMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (227)
.1.3.6.1.3.37
.1.3.6.1.3.37.0
.1.3.6.1.3.37.1
.1.3.6.1.3.37.1.1
.1.3.6.1.3.37.1.1.1
Enumeration
.1.3.6.1.3.37.1.1.1.1
.1.3.6.1.3.37.1.1.1.10
.1.3.6.1.3.37.1.1.1.11
Bits
.1.3.6.1.3.37.1.1.1.12
.1.3.6.1.3.37.1.1.1.13
.1.3.6.1.3.37.1.1.1.2
isisSysID r/w
.1.3.6.1.3.37.1.1.1.3
Unsigned32
.1.3.6.1.3.37.1.1.1.4
secondsUnsigned32
.1.3.6.1.3.37.1.1.1.5
.1.3.6.1.3.37.1.1.1.6
.1.3.6.1.3.37.1.1.1.7
.1.3.6.1.3.37.1.1.1.8
.1.3.6.1.3.37.1.1.1.9
.1.3.6.1.3.37.1.1.2
.1.3.6.1.3.37.1.1.2.1
.1.3.6.1.3.37.1.1.2.1.1
.1.3.6.1.3.37.1.1.2.1.2
.1.3.6.1.3.37.1.1.3
.1.3.6.1.3.37.1.1.3.1
.1.3.6.1.3.37.1.1.3.1.1
.1.3.6.1.3.37.1.1.4
.1.3.6.1.3.37.1.1.4.1
.1.3.6.1.3.37.1.1.4.1.1
.1.3.6.1.3.37.1.1.4.1.2
.1.3.6.1.3.37.1.1.4.1.3
.1.3.6.1.3.37.1.1.4.1.4
.1.3.6.1.3.37.1.1.4.1.5
.1.3.6.1.3.37.1.1.4.1.6
.1.3.6.1.3.37.1.1.5
.1.3.6.1.3.37.1.1.5.1
.1.3.6.1.3.37.1.1.5.1.1
.1.3.6.1.3.37.1.1.5.1.2
.1.3.6.1.3.37.1.1.5.1.3
.1.3.6.1.3.37.1.1.5.1.4
.1.3.6.1.3.37.1.1.6
.1.3.6.1.3.37.1.1.6.1
.1.3.6.1.3.37.1.1.6.1.1
.1.3.6.1.3.37.1.1.6.1.2
.1.3.6.1.3.37.1.1.6.1.3
.1.3.6.1.3.37.1.1.6.1.4
.1.3.6.1.3.37.1.10
.1.3.6.1.3.37.1.10.1
.1.3.6.1.3.37.1.10.1.1
.1.3.6.1.3.37.1.10.1.10
OctetString
.1.3.6.1.3.37.1.10.1.11
Enumeration
.1.3.6.1.3.37.1.10.1.12
.1.3.6.1.3.37.1.10.1.13
Unsigned32
.1.3.6.1.3.37.1.10.1.14
.1.3.6.1.3.37.1.10.1.15
Unsigned32
.1.3.6.1.3.37.1.10.1.2
.1.3.6.1.3.37.1.10.1.3
.1.3.6.1.3.37.1.10.1.4
.1.3.6.1.3.37.1.10.1.5
.1.3.6.1.3.37.1.10.1.6
.1.3.6.1.3.37.1.10.1.7
Unsigned32
.1.3.6.1.3.37.1.10.1.8
.1.3.6.1.3.37.1.10.1.9
.1.3.6.1.3.37.1.2
.1.3.6.1.3.37.1.2.1
.1.3.6.1.3.37.1.2.1.1
.1.3.6.1.3.37.1.2.1.1.1
.1.3.6.1.3.37.1.2.1.1.2
.1.3.6.1.3.37.1.2.1.1.3
.1.3.6.1.3.37.1.2.1.1.4
.1.3.6.1.3.37.1.2.1.1.5
Seconds until clearing manually set Overload BitSNMPv2-SMIUnsigned32
.1.3.6.1.3.37.1.2.1.1.6
.1.3.6.1.3.37.1.2.1.1.7
.1.3.6.1.3.37.1.2.1.1.8
.1.3.6.1.3.37.1.2.1.1.9
.1.3.6.1.3.37.1.3
.1.3.6.1.3.37.1.3.1
.1.3.6.1.3.37.1.3.2
.1.3.6.1.3.37.1.3.2.1
.1.3.6.1.3.37.1.3.2.1.1
.1.3.6.1.3.37.1.3.2.1.10
.1.3.6.1.3.37.1.3.2.1.11
.1.3.6.1.3.37.1.3.2.1.12
.1.3.6.1.3.37.1.3.2.1.13
.1.3.6.1.3.37.1.3.2.1.14
.1.3.6.1.3.37.1.3.2.1.2
.1.3.6.1.3.37.1.3.2.1.3
.1.3.6.1.3.37.1.3.2.1.4
Enumeration
.1.3.6.1.3.37.1.3.2.1.5
.1.3.6.1.3.37.1.3.2.1.6
.1.3.6.1.3.37.1.3.2.1.7
.1.3.6.1.3.37.1.3.2.1.8
Enumeration
.1.3.6.1.3.37.1.3.2.1.9
.1.3.6.1.3.37.1.4
.1.3.6.1.3.37.1.4.1
.1.3.6.1.3.37.1.4.1.1
.1.3.6.1.3.37.1.4.1.1.1
millisecondsUnsigned32
.1.3.6.1.3.37.1.4.1.1.10
millisecondsIsisUnsigned16TC
.1.3.6.1.3.37.1.4.1.1.11
secondsUnsigned32
.1.3.6.1.3.37.1.4.1.1.12
secondsUnsigned32
.1.3.6.1.3.37.1.4.1.1.13
secondsUnsigned32
.1.3.6.1.3.37.1.4.1.1.14
.1.3.6.1.3.37.1.4.1.1.2
.1.3.6.1.3.37.1.4.1.1.3
.1.3.6.1.3.37.1.4.1.1.4
Unsigned32
.1.3.6.1.3.37.1.4.1.1.5
.1.3.6.1.3.37.1.4.1.1.6
.1.3.6.1.3.37.1.4.1.1.7
Unsigned32
.1.3.6.1.3.37.1.4.1.1.8
millisecondsUnsigned32
.1.3.6.1.3.37.1.4.1.1.9
.1.3.6.1.3.37.1.5
.1.3.6.1.3.37.1.5.1
.1.3.6.1.3.37.1.5.1.1
.1.3.6.1.3.37.1.5.1.1.1
Number of frames with ID length mismatchesSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.1.1.10
.1.3.6.1.3.37.1.5.1.1.11
.1.3.6.1.3.37.1.5.1.1.12
Number of frames with errors that we have receivedSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.1.1.13
Number of corrupted in-memory framesSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.1.1.2
Number of frames with authentication type mismatchesSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.1.1.3
Number of frames with authentication key failuresSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.1.1.4
.1.3.6.1.3.37.1.5.1.1.5
.1.3.6.1.3.37.1.5.1.1.6
.1.3.6.1.3.37.1.5.1.1.7
.1.3.6.1.3.37.1.5.1.1.8
.1.3.6.1.3.37.1.5.1.1.9
.1.3.6.1.3.37.1.5.2
.1.3.6.1.3.37.1.5.2.1
Enumeration
.1.3.6.1.3.37.1.5.2.1.1
.1.3.6.1.3.37.1.5.2.1.10
.1.3.6.1.3.37.1.5.2.1.2
.1.3.6.1.3.37.1.5.2.1.3
.1.3.6.1.3.37.1.5.2.1.4
.1.3.6.1.3.37.1.5.2.1.5
Number of frames with ID field length mismatchSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.2.1.6
.1.3.6.1.3.37.1.5.2.1.7
.1.3.6.1.3.37.1.5.2.1.8
.1.3.6.1.3.37.1.5.2.1.9
.1.3.6.1.3.37.1.5.3
.1.3.6.1.3.37.1.5.3.1
.1.3.6.1.3.37.1.5.3.1.1
Enumeration
.1.3.6.1.3.37.1.5.3.1.2
Number of IS-IS Hellos frames seen in this direction at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.3
Number of ES-IS frames seen in this direction at this level.SNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.4
Number of ES Hello frames seen in this direction at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.5
Number of IS-IS LSP frames seen in this direction at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.6
Number of IS-IS CSNP frames seen in this direction at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.7
Number of IS-IS PSNP frames seen in this direction at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.8
Number of unknown IS-IS frames seen at this levelSNMPv2-SMICounter32
.1.3.6.1.3.37.1.5.3.1.9
.1.3.6.1.3.37.1.6
.1.3.6.1.3.37.1.6.1
.1.3.6.1.3.37.1.6.1.1
Unsigned32
.1.3.6.1.3.37.1.6.1.1.1
.1.3.6.1.3.37.1.6.1.1.10
.1.3.6.1.3.37.1.6.1.1.11
Enumeration
.1.3.6.1.3.37.1.6.1.1.2
Enumeration
.1.3.6.1.3.37.1.6.1.1.3
.1.3.6.1.3.37.1.6.1.1.4
Enumeration
.1.3.6.1.3.37.1.6.1.1.5
.1.3.6.1.3.37.1.6.1.1.6
.1.3.6.1.3.37.1.6.1.1.7
.1.3.6.1.3.37.1.6.1.1.8
.1.3.6.1.3.37.1.6.1.1.9
.1.3.6.1.3.37.1.6.2
.1.3.6.1.3.37.1.6.2.1
Unsigned32
.1.3.6.1.3.37.1.6.2.1.1
.1.3.6.1.3.37.1.6.2.1.2
.1.3.6.1.3.37.1.6.3
.1.3.6.1.3.37.1.6.3.1
Unsigned32
.1.3.6.1.3.37.1.6.3.1.1
.1.3.6.1.3.37.1.6.3.1.2
.1.3.6.1.3.37.1.6.3.1.3
.1.3.6.1.3.37.1.6.4
.1.3.6.1.3.37.1.6.4.1
.1.3.6.1.3.37.1.6.4.1.1
.1.3.6.1.3.37.1.7
.1.3.6.1.3.37.1.7.1
.1.3.6.1.3.37.1.7.1.1
Unsigned32
.1.3.6.1.3.37.1.7.1.1.1
.1.3.6.1.3.37.1.7.1.1.10
Enumeration
.1.3.6.1.3.37.1.7.1.1.11
.1.3.6.1.3.37.1.7.1.1.2
.1.3.6.1.3.37.1.7.1.1.3
.1.3.6.1.3.37.1.7.1.1.4
Enumeration
.1.3.6.1.3.37.1.7.1.1.5
.1.3.6.1.3.37.1.7.1.1.6
.1.3.6.1.3.37.1.7.1.1.7
.1.3.6.1.3.37.1.7.1.1.8
.1.3.6.1.3.37.1.7.1.1.9
.1.3.6.1.3.37.1.8
.1.3.6.1.3.37.1.8.1
.1.3.6.1.3.37.1.8.1.1
.1.3.6.1.3.37.1.8.1.1.1
.1.3.6.1.3.37.1.8.1.1.10
.1.3.6.1.3.37.1.8.1.1.11
.1.3.6.1.3.37.1.8.1.1.12
.1.3.6.1.3.37.1.8.1.1.13
Enumeration
.1.3.6.1.3.37.1.8.1.1.14
.1.3.6.1.3.37.1.8.1.1.2
.1.3.6.1.3.37.1.8.1.1.3
Unsigned32
.1.3.6.1.3.37.1.8.1.1.4
.1.3.6.1.3.37.1.8.1.1.5
.1.3.6.1.3.37.1.8.1.1.6
Enumeration
.1.3.6.1.3.37.1.8.1.1.7
.1.3.6.1.3.37.1.8.1.1.8
.1.3.6.1.3.37.1.8.1.1.9
.1.3.6.1.3.37.1.9
.1.3.6.1.3.37.1.9.1
.1.3.6.1.3.37.1.9.1.1
.1.3.6.1.3.37.1.9.1.1.1
.1.3.6.1.3.37.1.9.1.1.2
.1.3.6.1.3.37.1.9.1.1.3
.1.3.6.1.3.37.1.9.1.1.4
.1.3.6.1.3.37.1.9.1.1.5
.1.3.6.1.3.37.1.9.1.1.6
.1.3.6.1.3.37.1.9.1.1.7
.1.3.6.1.3.37.1.9.1.1.8
.1.3.6.1.3.37.1.9.2
.1.3.6.1.3.37.1.9.2.1
Unsigned32
.1.3.6.1.3.37.1.9.2.1.1
.1.3.6.1.3.37.1.9.2.1.2
.1.3.6.1.3.37.1.9.2.1.3
.1.3.6.1.3.37.1.9.2.1.4
.1.3.6.1.3.37.1.9.2.1.5
OctetString
.1.3.6.1.3.37.1.9.2.1.6
.1.3.6.1.3.37.2
.1.3.6.1.3.37.2.1
.1.3.6.1.3.37.2.2
Dependencies (11) 7 direct · 4 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (19)
Enumeration
on(1)
off(2)
Type used in enabling and disabling a row.
OctetString range: 0range: 7
ID for a circuit.
Unsigned32 range: 0..63
Display format: d
Integer sub-range for default metric for single hop.
ISO 10589 provides for 4 types of metric. Only the
'default' metric is used in practice.
Unsigned32
Display format: d
Full Metric for IP Routes. Traffic Engineering extensions
provide 32 bit metrics.
Enumeration
area(1)
domain(2)
Identifies a level.
Unsigned32 range: 0..127
Display format: d
Integer sub-range for IS-IS priority.
Unsigned32 range: 512..16000
Display format: d
Integer sub range for maximum LSP size.
Enumeration
level1(1)
level2(2)
level1and2(3)
Identifies one or more levels.
Enumeration
off(1)
on(2)
waiting(3)
overloaded(4)
States of the IS-IS protocol.
OctetString range: 8
The 8 byte Link State PDU (LSP) ID,
consisting of the 6 byte SystemID of the
originating IS, a one byte PseudoNode ID
which is 0 unless the LSP represents the
topology of a LAN, and one byte LSP
fragment number that are issued in sequence,
starting with 0. Non zero PseudoNode IDs
need to be unique to the IS, but need not
match the IfIndex.
Enumeration
narrow(1)
wide(2)
both(3)
Do we use RFC 1195 style metrics or wide metrics?
Enumeration
internal(1)
external(2)
Is this an Internal or External Metric?
OctetString range: 0..20
OSI Network Service Address, e.g. NSAP, SNPA, or Network
Entity Title
OctetString range: 0..64
A block to contain the header from a PDU.
Enumeration
iso8473(129)
ipV6(142)
ip(204)
Types of network protocol supported by Integrated IS-IS.
The values for ISO8473 and IP are those registered for
these protocols in ISO TR9577.
OctetString range: 6
The ID for an Intermediate System. This should
be unique within a network, and is included
in all PDUs originated by an Intermediate System.
The protocol does not place any meanings upon
the bits, other than using ordering to break
ties in electing a Designated IS on a LAN.
Unsigned32 range: 0..65535
Display format: d
An Unsigned32 further restricted to 16 Bits. Note that
the ASN.1 BER encoding may still require 24 Bits for
some values.
Unsigned32 range: 0..255
Display format: d
An Unsigned32 further restricted to 8 Bits. Note that
the ASN.1 BER encoding may still require 16 Bits for
some values.
Unsigned32 range: 0..16777215
Display format: d
Wide Metric for IS Neighbors. ISO 10589 provides a
6 bit metric. Traffic Engineering extensions provide
24 bit metrics.
Conformance Groups (9)
The collections of objects used to manage an
IS-IS router.
.1.3.6.1.3.37.2.2.1
The collection of objects used to describe in
IS-IS Circuit.
.1.3.6.1.3.37.2.2.2
The collections of objects used to manage an
IS-IS Adjacency.
.1.3.6.1.3.37.2.2.3
The objects used to record notification parameters.
.1.3.6.1.3.37.2.2.4
The collections of notifications sent by an IS.
.1.3.6.1.3.37.2.2.5
The collections of objects used to count protocol PDUs.
.1.3.6.1.3.37.2.2.6
The collections of objects used to manage the
reachable NSAP prefixes.
.1.3.6.1.3.37.2.2.7
The collections of objects used to manage configured
IP addresses.
.1.3.6.1.3.37.2.2.8
The collections of objects used to observe the LSP
Data Base.
.1.3.6.1.3.37.2.2.9
Compliance Statements (3)

OID .1.3.6.1.3.37.2.1.1
The compliance statement for agents that support
the IS-IS MIB.

There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements.
Those requirements, and similar requirements for
related objects, are expressed below in
pseudo-OBJECT clause form in this description:

-- OBJECT isisSummAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
--
-- DESCRIPTION
-- The MIB requires support for IPv4 Summary
-- Addresses, and anticipates the support of
-- IPv6 addresses.
--
--
-- OBJECT isisRedistributeAddrType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
--
-- DESCRIPTION
-- The MIB requires support for IPv4
-- Redistribution Addresses, and anticipates
-- the support of IPv6 addresses.
Required groups

OID .1.3.6.1.3.37.2.1.2
The compliance statement for agents that fully
support the IS-IS MIB.

There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements.
Those requirements, and similar requirements for
related objects, are expressed below in
pseudo-OBJECT clause form in this description:

-- OBJECT isisSummAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
--
-- DESCRIPTION
-- The MIB requires support for IPv4 Summary
-- Addresses, and anticipates the support of
-- IPv6 addresses.
--
--
-- OBJECT isisRedistributeAddrType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
--
-- DESCRIPTION
-- The MIB requires support for IPv4
-- Redistribution Addresses, and anticipates
-- the support of IPv6 addresses.
Required groups

OID .1.3.6.1.3.37.2.1.3
When this MIB is implemented without support for
read-create (i.e. in read-only mode), the implementation
can claim read-only compliance. Such a device can then
be monitored but can not be configured with this MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
isisSysLevelType readonly
Write access is not required.
isisSysID readonly
Write access is not required.
isisSysMaxPathSplits readonly
Write access is not required.
isisSysMaxLSPGenInt readonly
Write access is not required.
isisSysPollESHelloRate readonly
Write access is not required.
isisSysWaitTime readonly
Write access is not required.
isisSysAdminState readonly
Write access is not required.
isisSysL2toL1Leaking readonly
Write access is not required.
isisSysMaxAge readonly
Write access is not required.
isisManAreaAddrExistState readonly
Write access is not required.
isisSysLevelOrigLSPBuffSize readonly
Write access is not required.
isisSysLevelMinLSPGenInt readonly
Write access is not required.
isisSysLevelSetOverload readonly
Write access is not required.
isisSysLevelSetOverloadUntil readonly
Write access is not required.
isisSysLevelMetricStyle readonly
Write access is not required.
isisSysLevelSPFConsiders readonly
Write access is not required.
isisSysLevelTEEnabled readonly
Write access is not required.
isisSysReceiveLSPBufferSize readonly
Write access is not required.
isisSummAddrExistState readonly
Write access is not required.
isisSummAddrMetric readonly
Write access is not required.
isisSummAddrFullMetric readonly
Write access is not required.
isisRedistributeAddrExistState readonly
Write access is not required.
isisCircAdminState readonly
Write access is not required.
isisCircExistState readonly
Write access is not required.
isisCircType readonly
Write access is not required.
isisCircExtDomain readonly
Write access is not required.
isisCircLevelType readonly
Write access is not required.
isisCircPassiveCircuit readonly
Write access is not required.
isisCircMeshGroupEnabled readonly
Write access is not required.
isisCircMeshGroup readonly
Write access is not required.
isisCircSmallHellos readonly
Write access is not required.
isisCircExtendedCircID readonly
Write access is not required.
isisCircIfIndex readonly
Write access is not required.
isisCirc3WayEnabled readonly
Write access is not required.
isisCircLevelMetric readonly
Write access is not required.
isisCircLevelWideMetric readonly
Write access is not required.
isisCircLevelISPriority readonly
Write access is not required.
isisCircLevelHelloMultiplier readonly
Write access is not required.
isisCircLevelHelloTimer readonly
Write access is not required.
isisCircLevelDRHelloTimer readonly
Write access is not required.
isisCircLevelLSPThrottle readonly
Write access is not required.
isisCircLevelMinLSPRetransInt readonly
Write access is not required.
isisCircLevelCSNPInterval readonly
Write access is not required.
isisCircLevelPartSNPInterval readonly
Write access is not required.
Notifications / Traps (18)
NameOIDDescription
.1.3.6.1.3.37.0.1
This notification is generated when the system
enters or leaves the Overload state. The number
of times this has be generated and cleared is kept
track of by isisSysStatLSPDbaseOloads.
.1.3.6.1.3.37.0.10
A notification sent when we receive a PDU
with incorrect authentication information
field. This notification includes the header
of the packet, which may help a network manager
identify the source of the confusion.

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.
.1.3.6.1.3.37.0.11
A notification sent when we receive a Hello
PDU from an IS running a different version
of the protocol. This notification includes
the header of the packet, which may help a
network manager identify the source of the
confusion.

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.
.1.3.6.1.3.37.0.12
A notification sent when we receive a Hello
PDU from an IS which does not share any
area address. This notification includes
the header of the packet, which may help a
network manager identify the source of the
confusion.

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.
.1.3.6.1.3.37.0.13
A notification sent when we receive a Hello
PDU from an IS, but do not establish an
adjacency for some reason.

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.
.1.3.6.1.3.37.0.14
A notification sent when we attempt to propagate
an LSP which is larger than the dataLinkBlockSize
for the circuit.

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.
.1.3.6.1.3.37.0.15
A notification sent when a Level 1 LSP or Level
2 LSP is received which is larger than the local
value for isisSysLevelOrigLSPBuffSize, or when an
LSP is received containing the supported Buffer Size
option and the value in the PDU option field does
not match the local value for isisSysLevelOrigLSPBuffSize.
We pass up the size from the option field and the
size of the LSP when one of them exceeds our configuration.

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.
.1.3.6.1.3.37.0.16
A notification sent when a non-pseudonode
segment 0 LSP is received that has no matching
protocols supported.
This may be because the system does not generate
the field, or because there are no common elements.
The list of protocols supported should be included
in the notification: it may be empty if the TLV
is not supported, or if the TLV is empty.

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.
.1.3.6.1.3.37.0.17
A notification sent when an adjacency changes
state, entering or leaving state up.
The first 6 bytes of the isisPduLspId are the
SystemID of the adjacent IS.
The isisAdjState is the new state of the adjacency.
.1.3.6.1.3.37.0.18
This notification is generated when we receive
an LSP with a parse error. The isisCircIfIndex
holds in index of the circuit on which the PDU
arrived. The isisPduFragment holds start of the LSP,
and the isisErrorOffset points to the problem.

If the problem is a malformed TLV, isisErrorOffset
points to start of the TLV and isisErrorTLVType
holds the value of the type.

If the problem is with the LSP header, isisErrorOffset
points to the suspicious byte.
The number of such LSPs is accumulated in
isisSysStatLSPErrors.
.1.3.6.1.3.37.0.2
This notification is generated when one of the
manual areaAddresses assigned to this system is
ignored when computing routes. The object
isisNotificationAreaAddress describes the area that
has been dropped.

The number of times this event has been generated
is counted by 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.
.1.3.6.1.3.37.0.3
This notification is generated when we find that
an LSP that was stored in memory has become
corrupted. The number of times this has been
generated is counted by isisSysCorrLSPs.

We forward an LSP ID. We may have independent
knowledge of the ID, but in some implementations
there is a chance that the ID itself will be
corrupted.
.1.3.6.1.3.37.0.4
When the sequence number on an LSP we generate
wraps the 32 bit sequence counter, we purge and
wait to re-announce this information. This
notification describes that event. Since these
should not be generated rapidly, we generate
an event each time this happens.

While the first 6 bytes of the LSPID are ours,
the other two contain useful information.
.1.3.6.1.3.37.0.5
A notification sent when we receive a PDU
with a different value of the System ID Length.
This notification includes the an index to identify
the circuit where we saw the PDU and the header of
the PDU which may help a network manager identify
the source of the confusion.

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.
.1.3.6.1.3.37.0.6
A notification sent when we receive a PDU
with a different value of the Maximum Area
Addresses. This notification includes the
header of the packet, which may help a
network manager identify the source of the
confusion.

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.
.1.3.6.1.3.37.0.7
A notification sent when we receive a PDU
with our systemID and zero age. This
notification includes the circuit Index
and router ID from the LSP, if available,
which may help a network manager
identify the source of the confusion.
.1.3.6.1.3.37.0.8
When we receive an LSP with our System ID
and different contents, we may need to reissue
the LSP with a higher sequence number.

We send this notification if we need to increase
the sequence number by more than one. If two
Intermediate Systems are configured with the same
System ID, this notification will fire.
.1.3.6.1.3.37.0.9
A notification sent when we receive a PDU
with the wrong authentication type field.
This notification includes the header of the
packet, which may help a network manager
identify the source of the confusion.

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.