ISIS-DRAFT-13-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 defines an experimental portion of the
Management Information Base (MIB) for use with network
management protocols in the Internet community.
        
This document is based on a 1994 IETF draft by Chris Gunner.
This version has been modified to include MIB-II syntax, to
exclude portions of the protocol that are not relevant to IP,
and to add management support for current practice.
    
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-13-MIB
Last revised
Identity
isisMIB
Base OID
1.3.6.1.3.37
Imported Objects
IF-MIB ifName
INET-ADDRESS-MIB InetAddress InetAddressPrefixLength InetAddressType
RFC1213-MIB ifEntry ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 experimental Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC DisplayString RowStatus TestAndIncr TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the huawei 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-13-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ISIS-DRAFT-13-MIB::isisMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ISIS-DRAFT-13-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ISIS-DRAFT-13-MIB::isisMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (230)
.1.3.6.1.3.37
.1.3.6.1.3.37.1
.1.3.6.1.3.37.1.1
.1.3.6.1.3.37.1.1.1
.1.3.6.1.3.37.1.1.1.1
Unsigned32
.1.3.6.1.3.37.1.1.1.1.1
.1.3.6.1.3.37.1.1.1.1.10
.1.3.6.1.3.37.1.1.1.1.11
.1.3.6.1.3.37.1.1.1.1.12
.1.3.6.1.3.37.1.1.1.1.13
.1.3.6.1.3.37.1.1.1.1.14
.1.3.6.1.3.37.1.1.1.1.15
.1.3.6.1.3.37.1.1.1.1.2
Enumeration
.1.3.6.1.3.37.1.1.1.1.3
isisSysID r/w
.1.3.6.1.3.37.1.1.1.1.4
Integer32
.1.3.6.1.3.37.1.1.1.1.5
secondsInteger32
.1.3.6.1.3.37.1.1.1.1.6
.1.3.6.1.3.37.1.1.1.1.7
.1.3.6.1.3.37.1.1.1.1.8
.1.3.6.1.3.37.1.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.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.5.1.5
.1.3.6.1.3.37.1.1.5.1.6
.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.1.7
.1.3.6.1.3.37.1.1.7.1
.1.3.6.1.3.37.1.1.7.1.1
.1.3.6.1.3.37.1.1.7.1.2
.1.3.6.1.3.37.1.1.7.1.3
.1.3.6.1.3.37.1.1.7.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.1.1
.1.3.6.1.3.37.1.10.1.1.10
.1.3.6.1.3.37.1.10.1.1.2
.1.3.6.1.3.37.1.10.1.1.3
.1.3.6.1.3.37.1.10.1.1.4
.1.3.6.1.3.37.1.10.1.1.5
Integer32
.1.3.6.1.3.37.1.10.1.1.6
.1.3.6.1.3.37.1.10.1.1.7
OctetString
.1.3.6.1.3.37.1.10.1.1.8
Enumeration
.1.3.6.1.3.37.1.10.1.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
Enumeration
.1.3.6.1.3.37.1.2.1.1.1
Integer32
.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
.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.1.1
Integer32
.1.3.6.1.3.37.1.3.1.1.1
Enumeration
.1.3.6.1.3.37.1.3.1.1.10
.1.3.6.1.3.37.1.3.1.1.11
.1.3.6.1.3.37.1.3.1.1.12
.1.3.6.1.3.37.1.3.1.1.13
.1.3.6.1.3.37.1.3.1.1.14
.1.3.6.1.3.37.1.3.1.1.15
.1.3.6.1.3.37.1.3.1.1.2
.1.3.6.1.3.37.1.3.1.1.3
.1.3.6.1.3.37.1.3.1.1.4
.1.3.6.1.3.37.1.3.1.1.5
Enumeration
.1.3.6.1.3.37.1.3.1.1.6
.1.3.6.1.3.37.1.3.1.1.7
Enumeration
.1.3.6.1.3.37.1.3.1.1.8
.1.3.6.1.3.37.1.3.1.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
Enumeration
.1.3.6.1.3.37.1.4.1.1.1
millisecondsInteger32
.1.3.6.1.3.37.1.4.1.1.10
millisecondsUnsigned16TC
.1.3.6.1.3.37.1.4.1.1.11
secondsInteger32
.1.3.6.1.3.37.1.4.1.1.12
secondsInteger32
.1.3.6.1.3.37.1.4.1.1.13
secondsInteger32
.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
Integer32
.1.3.6.1.3.37.1.4.1.1.5
.1.3.6.1.3.37.1.4.1.1.6
OctetString
.1.3.6.1.3.37.1.4.1.1.7
Integer32
.1.3.6.1.3.37.1.4.1.1.8
millisecondsInteger32
.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
Enumeration
.1.3.6.1.3.37.1.5.1.1.1
.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
.1.3.6.1.3.37.1.5.1.1.13
.1.3.6.1.3.37.1.5.1.1.2
.1.3.6.1.3.37.1.5.1.1.3
.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
.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
Enumeration
.1.3.6.1.3.37.1.5.3.1.1
Enumeration
.1.3.6.1.3.37.1.5.3.1.2
.1.3.6.1.3.37.1.5.3.1.3
.1.3.6.1.3.37.1.5.3.1.4
.1.3.6.1.3.37.1.5.3.1.5
.1.3.6.1.3.37.1.5.3.1.6
.1.3.6.1.3.37.1.5.3.1.7
.1.3.6.1.3.37.1.5.3.1.8
.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
Integer32
.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
Enumeration
.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
Integer32
.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
Integer32
.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
Integer32
.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
Enumeration
.1.3.6.1.3.37.1.8.1.1.13
.1.3.6.1.3.37.1.8.1.1.2
.1.3.6.1.3.37.1.8.1.1.3
.1.3.6.1.3.37.1.8.1.1.4
.1.3.6.1.3.37.1.8.1.1.5
Enumeration
.1.3.6.1.3.37.1.8.1.1.6
.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
.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.0
.1.3.6.1.3.37.3
.1.3.6.1.3.37.3.1
.1.3.6.1.3.37.3.2
Dependencies (10) 6 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 (18)
Enumeration
on(1)
off(2)
Type used in enabling and disabling a row.
Values match those in RFC 2863.
OctetString range: 7
ID for a circuit.
Integer32 range: 0..63
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 range: 0..4261412864
Full Metric for IP Routes. Traffic Engineering extensions
provide 32 bit metrics.
Enumeration
none(0)
area(1)
domain(2)
Identifies a level.
Integer32 range: 0..127
Integer sub-range for IS-IS priority.
OctetString range: 0..64
A block to contain the header from a PDU.
Integer32 range: 512..16000
Integer sub range for LSP size.
Enumeration
off(1)
on(2)
waiting(3)
overloaded(4)
States of the IS-IS protocol.
OctetString range: 0range: 8
A Link State PDU Identifier.
Enumeration
narrow(1)
wide(2)
both(3)
Do we use 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
Enumeration
iso8473(129)
ipV6(142)
ip(204)
virtual-access(255)
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
A system ID.
Unsigned32 range: 0..65535
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
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
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.3.1.1
The collection of objects used to describe in IS-IS Circuit.
.1.3.6.1.3.37.3.1.2
The collections of objects used to manage an IS-IS Adjacency.
.1.3.6.1.3.37.3.1.3
The objects used to record notification parameters.
.1.3.6.1.3.37.3.1.4
The collections of notifications sent by an IS.
.1.3.6.1.3.37.3.1.5
The collections of objects used to count protocol PDUs.
.1.3.6.1.3.37.3.1.6
The collections of objects used to manage the
reachable NSAP prefixes.
.1.3.6.1.3.37.3.1.7
The collections of objects used to manage configured
IP addresses.
.1.3.6.1.3.37.3.1.8
The collections of objects used to observe the LSP
Data Base.
.1.3.6.1.3.37.3.1.9
Compliance Statements (2)

OID .1.3.6.1.3.37.3.2.1
The compliance statement for agents that support
the IS-IS MIB
Required groups

OID .1.3.6.1.3.37.3.2.2
The compliance statement for agents that support
the IS-IS MIB
Required groups
Notifications / Traps (17)
NameOIDDescription
.1.3.6.1.3.37.2.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 recorded
by isisSysStatLSPDbaseOloads.
.1.3.6.1.3.37.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.
.1.3.6.1.3.37.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.
This decision is up to the agent to make, and may
be based on the circuit or on some MAC level
information.
.1.3.6.1.3.37.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.
This decision is up to the agent to make, and may
be based on the circuit or on some MAC level
information.
.1.3.6.1.3.37.2.0.13
A notification sent when we receive a Hello
PDU from an IS, but do not establish an
adjacency for some reason.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from the same source.
.1.3.6.1.3.37.2.0.14
A notification sent when we attempt to propagate
an LSP which is larger than the dataLinkBlockSize
for the circuit.
This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from the same source.
.1.3.6.1.3.37.2.0.15
A notification sent when a Level 1 LSP or Level
2 LSP is received which is larger than the local
value for isisOriginatingBufferSize, or when an
LSP is received containing the isisOriginatingBufferSize
option and the value in the PDU option field does
not match the local value for isisOriginatingBufferSize.
We pass up the size from the option field or the
size of the LSP that exceeds our configuration.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from the same source.
.1.3.6.1.3.37.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from the same source.
.1.3.6.1.3.37.2.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.2.0.2
This notification is generated when one of the
manual areaAddresses assigned to this system is
ignored when computing routes. The object
isisManAreaAddrExistState describes the area that
has been dropped.

The number of times this event has been generated
is counted by isisSysManAddrDropFromAreas.

This notification is edge triggered, and should not
be regenerated until an address that was used in
the previous computation has been dropped.
.1.3.6.1.3.37.2.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.2.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.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.
This decision is up to the agent to make, and may
be based on the circuit or on some MAC level
information.
.1.3.6.1.3.37.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.
.1.3.6.1.3.37.2.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.2.0.8
When we receive an LSP with out 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.2.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.

This should be an edge-triggered notification.
We should not send a second notification about
PDUs received from what seem to be the same source.