The IS-IS MIB feature introduces network management support for the IS-IS routing protocol through the use of IS-IS MIB table entries, MIB objects and MIB trap notification objects that comprise the Cisco private MIB CISCO-IETF-ISIS-MIB.my. New CLI has been added to enable SNMP notifications for IS-IS MIB objects. Notifications are provided for errors and other significant event information for the IS-IS network.

For more information on how to configure IS-IS MIB to receive the SNMP notifications, refer to the How to Enable IS-IS MIB.

The ciiManAreaAddrEntry table contains the set of area addresses manually configured for the IS. The ciiManAreaAddrEntry table defines the following MIB objects:

• ciiManAreaAddr

• ciiManAreaAddrExistState

The ciiAreaAddrEntry table groups sets of relevant area addresses reported in all Level 1 link-state packets (LSPs) that were generated or received by an IS from other ISs that are reachable through Level 1 routing.

Each entry contains one area address per LSP. The ciiAreaAddrEntry table defines the following MIB object:

• ciiAreaAddr

The ciiSysProtSuppEntry table contains a manually configured set of protocols supported by the IS. The supported protocol types are IPv4, IPv6, and ISO8473. The ciiSysProtSuppEntry table defines the following MIB objects:

• ciiSysProtSuppProtocol

• ciiSysProtSuppExistState

The ciiSummAddrEntry table contains a set of manually configured summary addresses used to form summarized IP TLVs originated by an ISS. This table is useful to combine and modify IP reachability announcements, and also controls leaking of L1 routes into L2. The ciiSummAddrEntry table defines the following MIB objects:

• ciiSummAddressType

• ciiSummAddress

• ciiSummAddrPrefixLen

• ciiSummAddrExistState

• ciiSummAddrMetric

• ciiSummAddrFullMetric

The ciiRedistributeAddrEntry table provides the criteria to decide if a route should be leaked from L2 to L1. When Domain Wide Prefix leaking is enabled (represented by ciiSysL2toL1Leaking), addresses that match the summary mask in the table are announced at L1 by routers. The Cisco MIB implementation also allows retrieval of routes for masked entries based on configured access lists or route maps. The ciiRedistributeAddrEntry table defines the following MIB objects:

• ciiRedistributeAddrType

• ciiRedistributeAddrAddress

• ciiRedistributeAddrPrefixLen

• ciiRedistributeAddrExistState

The ciiRouterEntry table has one entry for every peer and it tracks the hostnames and Router IDs associated with that peer. The ciiRouterEntry table defines the following MIB objects.

• ciiRouterSysID

• ciiRouterLevel

• ciiRouterHostName

• ciiRouterID

Note	The IS-IS MIB defines the ciiRouterLevel object to be the level of the IS. The Cisco implementation interprets the ciiRouterLevel object to be the level of the link-state packet (LSP) in which the hostname (ciiRouterHostName) and router ID (ciiRouterID) were received.

The ciiSysLevelEntry table captures level-specific information about the IS. This information includes parameters that control how LSPs are generated, metrics for SPF computation and the decision of whether to perform traffic engineering at this level.

The ciiSysLevelEntry table defines the following MIB objects:

• ciiSysLevelIndex

• ciiSysLevelOrigLSPBuffSize

• ciiSysLevelMinLSPGenInt

• ciiSysLevelOverloadState

• ciiSysLevelSetOverload

• ciiSysLevelSetOverloadUntil

• ciiSysLevelMetricStyle

• ciiSysLevelSPFConsiders

• ciiSysLevelTEEnabled

Note

For the ciiSysLevelOverloadState MIB object, the Cisco MIB follows the correct interpretation of IS state transition per the future IETF draft MIB revisions. The draft-ietf-isis-wg-16.txt did not follow the ISO 10589:2002 definition correctly. Per the ISO 10589:2002 definition, the waiting state is defined for low memory resource condition and the overloaded state is enabled by the administrator. Moreover, the Cisco implementation does not support a transition to a waiting state on low memory.

The ciiCircEntry table contains circuit-specific information about each broadcast or point-to-point interface used in this IS-IS. Each entry is associated with a corresponding interface, based on the circuit type (broadcast or point-to-point interfaces). In other words, only interfaces that are configured as broadcast or point-to-point can be polled. The Cisco implementation of the IS-IS MIB does not support the following circuit types: staticIn, staticOut, dA (dynamically assigned). The ciiCircEntry table defines the following MIB objects:

• ciiCircIndex

• ciiCircIfIndex

• ciiCircIfSubIndex

• ciiCircAdminState

• ciiCircExistState

• ciiCircType

• ciiCircExtDomain

• ciiCircLevel

• ciiCircPassiveCircuit

• ciiCircMeshGroupEnabled

• ciiCircMeshGroup

• ciiCircSmallHellos

• ciiCircLastUpTime

• ciiCirc3WayEnabled

• ciiCircExtendedCircID

Note	The ciiCircExtDomain MIB table object is not implemented because externalDomain linkage is not supported by Cisco IOS software.

The ciiNextCircIndex object, which is defined outside ciiCircTable, is used to assign a unique index value to the ciiCircIndex through a SET operation. The Cisco MIB implementation does not implement this object because the SET ability currently is not supported, and ciiCircIndex is determined uniquely through data from configured interfaces.

The ciiCircLevelEntry table contains level-specific information about IS-IS circuits. The ciiCircLevelEntry table contains the following MIB objects:

• ciiCircLevelIndex

• ciiCircLevelMetric

• ciiCircLevelWideMetric

• ciiCircLevelISPriority

• ciiCircLevelIDOctet

• ciiCircLevelID

• ciiCircLevelDesIS

• ciiCircLevelHelloMultiplier

• ciiCircLevelHelloTimer

• ciiCircLevelDRHelloTimer

• ciiCircLevelLSPThrottle

• ciiCircLevelMinLSPRetransInt

• ciiCircLevelCSNPInterval

• ciiCircLevelPartSNPInterval

The ciiSystemCounterEntry table has a sequence of entries used to track system-wide events using counters. The ciiSystemCounterEntry table defines the following MIB objects:

• ciiSysStatLevel

• ciiSysStatCorrLSPs

• ciiSysStatAuthTypeFails

• ciiSysStatAuthFails

• ciiSysStatLSPDbaseOloads

• ciiSysStatManAddrDropFromAreas

• ciiSysStatAttmptToExMaxSeqNums

• ciiSysStatSeqNumSkips

• ciiSysStatOwnLSPPurges

• ciiSysStatIDFieldLenMismatches

• ciiSysStatPartChanges

• ciiSysStatSPFRuns

• ciiSysStatLSPErrors

Note	The ciiSysStatPartChanges object is not implemented because the ability to detect partition changes currently is not supported by Cisco IOS software.

The ciiCircuitCounterEntry table is used to track system-wide events specific to a circuit and level. The ciiCircuitCounterEntry table defines the following MIB objects:

• ciiCircuitType

• ciiCircAdjChanges

• ciiCircNumAdj

• ciiCircInitFails

• ciiCircRejAdjs

• ciiCircIDFieldLenMismatches

• ciiCircMaxAreaAddrMismatches

• ciiCircAuthTypeFails

• ciiCircAuthFails

• ciiCircLANDesISChanges

Note	The ciiCircInitFails MIB object does not return any data because circuit initialization failures are not tracked by Cisco IOS software.

The ciiPacketCounterEntry table tracks the number of IS-IS packets sent and received over a circuit at one level. At any time, the traffic flow along one direction is recorded. All objects defined in this table are Counter objects. The ciiPacketCounterEntry table defines the following MIB objects:

• ciiPacketCountLevel

• ciiPacketCountDirection

• ciiPacketCountIIHellos

• ciiPacketCountISHellos

• ciiPacketCountESHellos

• ciiPacketCountLSPs

• ciiPacketCountCSNPs

• ciiPacketCountPSNPs

• ciiPacketCountUnknowns

Note	The ciiPacketCountISHellos MIB object tracks the number of end system-Intermediate system (ES-IS) hellos only at system granularity and not at per-level or per-circuit.

• The ciiPacketCountESHellos MIB objects tracks the number of end-system (ES) hellos only at system granularity and not at per-level or per-circuit.

• The ciiPacketCountUnknowns MIB object can track only unknown packet types that are received, not those that are sent in any given level.

The ciiISAdjEntry table has one entry associated with every adjacency to an IS (in other words, a table of adjacencies).

However, this object cannot be used to track multiple adjacencies in a LAN, with each adjacency corresponding to a level. Thus the best priority level is selected among the configured objects.

The ciiISAdjEntry table defines the following MIB objects:

• ciiISAdjChanges

• ciiISAdjIndex

• ciiISAdjState

• ciiISAdj3WayState

• ciiISAdjNeighSNPAAddress

• ciiISAdjNeighSysType

• ciiISAdjNeighSysID

• ciiISAdjNbrExtendedCircID

• ciiISAdjUsage

• ciiISAdjHoldTimer

• ciiIsAdjNeighPriority

• ciiISAdjLastUpTime

Note	The ciiISAdjChanges MIB object gathers information based on the best priority level that is selected among the configured objects, per the restriction against the software support of multiple adjacencies in a LAN for the ciiISAdjEntry table.

• The ciiISAdjNeighPriority MIB object gathers information based on the best priority level that is selected among the configured objects, per the restriction against the software support of multiple adjacencies in a LAN for the ciiISAdjEntry table.

The ciiISAdjAreaAddrEntry table contains entries for the sets of area addresses of neighboring ISs as reported in received IS-IS Hello protocol data units (PDU)s. The ciiISAdjAreaAddrEntry table defines the following MIB objects:

• ciiISAdjAreaAddrIndex

• ciiISAdjAreaAddress

The ciiISAdjIPAddrEntry table contains entries that are formed by a set of IP addresses of neighboring ISs as reported in received Hello PDUs. The ciiISAdjIPAddrEntry table defines the following MIB objects:

• ciiISAdjIPAddrIndex

• ciiISAdjIPAddrType

• ciiISAdjIPAddrAddress

The ciiISAdjProtSuppEntry table contains information about the protocols supported by neighboring ISs as reported in received Hello PDUs. The ciiISAdjProtSuppEntry table defines the following MIB object:

• ciiISAdjProtSuppProtocol

The ciiRAEntry table records information about a reachable NSAP or address prefix that is manually configured or learned dynamically.

The ciiRAEntry table defines the following MIB objects:

• ciiRAIndex

• ciiRAExistState

• ciiRAAdminState

• ciiRAAddrPrefix

• ciiRAMapType

• ciiRAMetric

• ciiRAMetricType

• ciiRASNPAAddress

• ciiRASNPAMask

• ciiRASNPAPrefix

• ciiRAType

Note	The ciiRAMapType MIB Object supports only implicit (null) and explicit mapping types. The extractIDI and extractDSP types are not supported.

• Because the ciiRAMapType MIB Object does not support the extractIDI and extractDSP mapping types, the ciiraSNPAPrefix and ciiRASNPAMask MIB objects will hold no data, as they depend on the unsupported mapping types. The ciiRAMapType and ciiRASNPAMask MIB objects are not implemented.

• The ciiRAType MIB object does not support the manual creation of IP reachability addresses.

Each entry in the ciiIPRAEntry table records information about one IP reachable address manually configured on the IS or learned from another protocol. The ciiIPRAEntry table defines the following MIB objects:

• ciiIPRADestType

• ciiIPRADest

• ciiIPRADestPrefixLen

• ciiIPRANextHopIndex

• ciiIPRANextHopType

• ciiIPRANextHop

• ciiIPRAType

• ciiIPRAExistState

• ciiIPRAAdminState

• ciiIPRAMetric

• ciiIPRAMetricType

• ciiIPRAFullMetric

• ciiIPRASNPAAddress

• ciiIPRASourceType

Note	The ciiIpRAType MIB object does not support manually created IP reachability addresses.

The ciiLSPSummaryEntry table (LSP Summary Table) provides LSP summary information.

The ciiLSPSummaryEntry table defines the following MIB objects:

• ciiLSPLevel

• ciiLSPID

• ciiLSPSeq

• ciiLSPZeroLife

• ciiLSPChecksum

• ciiLSPLifetimeRemain

• ciiLSPPDULength

• ciiLSPAttributes

The ciiLSPTLVEntry table provides a complete record of all LSPs as a sequence of {Type, Length, Value} tuples. The ciiLSPTLVEntry table defines the following MIB objects:

• ciiLSPTLVIndex

• ciiLSPTLVSeq

• ciiLSPTLVChecksum

• ciiLSPTLVType

• ciiLSPTLVLen

• ciiLSPTLVValue

Fields that are required for notifications are recorded in the ciiNotificationEntry table. The ciiNotificationEntry table is not meant for query since the MAX-ACCESS clause of the MIB objects is "accessible-for-notify." The information for notifications will be directly provided at the time of event generation. The following MIB objects are used only in trap notifications where their value is determined and directly based on input parameters for the IS-IS trap generation process.

• ciiPduLspId

• ciiPduFragment

• ciiPduFieldLen

• ciiPduMaxAreaAddress

• ciiPduProtocolVersion

• ciiPduLspSize

• ciiPduOriginatingBufferSize

• ciiPduProtocolsSupported

• ciiAdjState

• ciiErrorOffset

• ciiErrorTLVType

• ciiNotifManualAddress

• ciiNotifIsLevelIndex

Note

The MIB objects ciiNotifManualAddress and ciiNotifIsLevelIndex were added separately and are not defined in draft-ietf-isis-wg-mib-16.txt. These have been provided as a replacement for ciiManAreaAddr and ciiSysLevelIndex respectively to be used only in trap notifications. They have a MAX-ACCESS clause of "accessible-for-notify."

• IS-IS MIB for Generic System-Wide Errors
• IS-IS MIB for LSP-Specific Errors
• MIB Support for IS-IS Hello PDU-Specific Errors
• MIB Support for IS-IS Transition State Changes

IS-IS MIB for LSP-Specific Errors

The following MIB trap objects are for LSP-specific errors that can occur in the IS-IS network:

• ciiCorruptedLSPDetected--When an LSP stored in memory is corrupted, the ciiCorruptedLSPDetected trap is generated.

• ciiAttemptToExceedMaxSequence--The ciiAttemptToExceedMaxSequence trap is generated each time a sequence number on a generated LSP wraps around the 32-bit sequence counter, forcing it to be purged and hence waiting for its reannouncement.

• ciiOwnLSPPurge--The ciiOwnLSPPurge trap is generated when a LSP is received from a circuit with your systemID and zero age.

• ciiSequenceNumberSkip--When an LSP is received without a SystemID or differing contents, the ciiSequenceNumberSkip trap is generated in order to increment the sequence number by 1.

• ciiAuthenticationTypeFailure--When an LSP is received from a circuit filled with a wrong authentication type field, the ciiAuthenticationTypeFailure notification is generated. This is an edge-triggered notification.

• ciiLSPTooLargeToPropagate--When an attempt is made to send an LSP over the circuit with a size greater than dataLinkBlockSize (link-specific parameter for maximum size of a data packet), the ciiLSPTooLargeToPropagate trap is generated indicating that the LSP could not be propagated. This is an edge-triggered notification and will be generated only once for all PDUs received on the same circuit.

Note	Cisco IOS software does not support the condition that leads to this event. Therefore, this trap will not be generated.

• ciiOrigLSPBuffSizeMismatch--When an L1 or L2 LSP that has been received from a circuit has a size larger than the local value of ciiOriginatingBufferSize, or when an LSP has been received with the ciiOriginatingBufferSize option and there is a mismatch between local ciiOriginatingBufferSize and value of the PDU option field, this notification is generated. This is an edge-triggered notification and will be generated only once.

Note	The originating buffer size TLV that is used to advertise this condition is not currently supported in Cisco IOS software and sufficient information to determine which condition caused the trap is not available. Therefore, this trap will not be generated.

• ciiProtocolsSupportedMismatch--The ciiProtocolsSupportedMismatch trap is generated when a non-pseudonode segment 0 LSP is received that does not have any matching protocols supported. This is an edge-triggered notification.

Note	Cisco IOS software does not provide checks in the IS-IS implementation for detecting matching protocols in the case of received PDUs. The generation of the ciiProtocolsSupportedMismatch trap does not indicate a mismatch in protocols supported as specified in the protocol field of the received PDU.

• ciiLSPErrorDetected--The ciiLSPErrorDetected trap is generated to indicate that an LSP with a parse error has been received.

• Configuring the Router to Send SNMP Notifications for IS-IS to a Host
• Enabling All IS-IS Traps
• Enabling IS-IS Error Traps
• Enabling IS-IS State-Change Traps
• Verifying IS-IS MIB Traps on the Router

Router> enable

Router# show running-config

Router# configure terminal

Router(config)# snmp-server host 172.16.1.1 traps version 3 mycommunitystring isis

Router(config)# end

Router> enable
Router# configure terminal
Router(config)# snmp-server host 172.31.1.1 traps version 3 mycommunity string isis

Router> enable

Router# configure terminal

Router(config)# snmp-server enable traps isis

Router(config)# no snmp-server enable traps isis state-change database-overload

Router(config)# exit

Router# show running-config | include traps

Router> enable
Router# configure terminal
Router(config)# snmp-server enable traps isis

Router> enable

Router# configure terminal

Router(config)# snmp-server enable traps isis errors lsp

Router(config)# end

Router> enable
Router# configure terminal
Router(config)# snmp-server enable traps isis errors authentication

Router> enable

Router# configure terminal

Router(config)# snmp-server enable traps isis state-change

Router(config)# end

Router> enable
Router# configure terminal
Router(config)# snmp-server enable traps isis state-change adjacency

Router> enable

Router# show running-config | include traps