ISIS-D13-MIB: View SNMP OID List / Download MIB

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.

The object describes system wide attributes.

The set of instance of the Integrated IS-IS protocol existing on the system.

Each row defines information specific to a single instance of the IS-IS protocol existing on the system.

The unique identifier of the Integrated IS-IS instance to which this row corresponds. This object follows the index behavior.

The version number of the IS-IS protocol which this instance implements.

The type of this instance of the Integrated IS-IS protocol. This object follows the replaceOnlyWhileDisabled behavior. Enumeration: 'level1IS': 1, 'level2IS': 2, 'level1L2IS': 3.

The ID for this instance of the Integrated IS-IS protocol. This value is appended to each of the area addresses to form the Network Entity Titles. The derivation of a value for this object is implementation-specific. Some implementations may automatically assign values and not permit an SNMP write, while others may require the value to be set manually.

Maximum number of paths with equal routing metric value which it is permitted to split between. This object follows the replaceOnlyWhileDisabled behavior.

Maximum interval, in seconds, between generated LSPs by this instance of the protocol. This object follows the resettingTimer behavior. Should be at least 300 seconds less than isisD13SysMaxAge.

The value, in seconds, to be used for the suggested ES configuration timer in ISH PDUs when soliciting the ES configuration.

Number of seconds to delay in waiting state before entering on state. This object follows the resettingTimer behavior.

The administrative state of this instance of the Integrated IS-IS protocol. Setting this object to the value 'on' when its current value is 'off' enables operation of this instance of the Integrated IS-IS protocol.

If true, causes IS-IS to generate a log message when an IS-IS adjacency changes state (up or down).

This object is used to assign values to isisD13CircIndex as described in 'Textual Conventions for SNMPv2'. The network manager reads this object, and then writes the value back as the isisD13CircIndex in a SET that creates a new instance of isisD13CircEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the object is incremented, and the new isisD13Circuit is created according to the manager's directions.

If true, allow the router to leak L2 routes into L1.

Value to place in RemainingLifeTime field of the LSPs we generate. This is should be at least 300 seconds greater than isisD13SysMaxLSPGenInt.

Size of the largest Buffer we are designed or configured to store. This should be at least as big as the maximum isisD13SysOrigLSPBuffSize supported by the system. If resources allow, we will store and flood LSPs larger than isisD13SysReceiveLSPBufferSize, as this can help avoid problems in networks with different values for isisD13SysOrigLSPBuffSize.

The state of the IS-IS router. Turning this to state 'destroy' forces the router to forget all the current configuration. Setting the state to 'notInService' stops protocol processing, but retains the configuration.

The set of manual area addresses configured on this Intermediate System.

Each entry contains one area address manually configured on this system

A manually configured area address for this system. This object follows the index behavior. Note: an index for the entry {1, {49.0001} active} in this table would be the ordered pair (1, (0x03 0x49 0x00 0x01)), as the length of an Octet string is part of the OID.

The state of the isisD13ManAreaAddrEntry. This object follows the Row Status behavior. If the isisD13SysAdminState for this instance of the IS-IS protocol is 'on', and an attempt is made to set this object to the value 'destroy' or 'notInService' when this is the only isisD13ManAreaAddrEntry in state 'active' for this instance of the IS-IS protocol should return inconsistentValue.

The union of the sets of area addresses reported in all Level 1 LSPs with segment number zero received by this instance of the protocol from Intermediate Systems which are reachable via Level 1 routing.

Each entry contains one area address reported in a Level 1 LSP received by this instance of the IS-IS protocol.

An area address reported in a Level 1 LSP received by this instance of the IS-IS protocol.

This table contains the manually configured set of protocols supported by each instance of the Integrated IS-IS protocol.

Each entry contains one protocol supported by an instance of the Integrated IS-IS protocol.

One supported protocol. This object follows the index behavior.

The state of the isisD13SysProtSuppEntry. This object follows the RowStatus behavior.

The set of IP summary addresses to use in forming summary TLVs originated by this Intermediate System. An administrator may use a summary address to combine and modify IP Reachability announcements. If the Intermediate system can reach any subset of the summary address, the summary address will be announced instead, at the configured metric.

Each entry contains one IP summary address.

The Type of IP address for this summary address. This object follows the index behavior.

The IP Address value for this summary address. This object follows the index behavior.

The Length of the IP NetMask for this summary address.

The existence state of this summary address. This object follows the row status behavior.

The metric value to announce this summary address with in LSPs generated by this system.

The wide metric value to announce this summary address with in LSPs generated by this system.

This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when isisD13SysL2toL1Leaking is enabled. Routes that fall into the ranges specified are announced as is, without being summarized. Routes that do not match a summary mask are not announced.

Each entry contains one IP summary address to manage leaking L2 addresses into L1.

The Type of IP address for this summary address. This object follows the index behavior.

The IP Address value for this summary address. This object follows the index behavior.

The Length of the IP NetMask for this summary address.

The existence state of this summary address. This object follows the row status behavior.

The set of hostnames and router ID.

Each entry tracks information about one peer at one level.

The System ID of the Router Peer.

The level of this Intermediate System.

The hostname listed in LSP, or NULL if none.

The Router ID of the Peer found in LSP, or NULL if none.

This object describes attributes associated with the domain or with the area.

Level specific information about the System.

Describe variables defined for Area or Domain.

The level that this entry describes. Enumeration: 'level2IS': 2, 'level1IS': 1.

The maximum size of LSPs and SNPs originated by this instance of the protocol at this level. This object follows the replaceOnlyWhileDisabled behavior.

Minimum interval, in seconds, between successive generation of LSPs with the same LSPID at this level by this instance of the protocol. This object follows the resettingTimer behavior.

The Overload state of the database at this level. The value 'overloaded' indicates a database that is low on an essential resource, such as memory. The administrator may indirectly force the state to 'waiting' when the router is initializing by setting the object isisD13SysLevelSetOverload. If the state is waiting or overloaded, we originate LSPs with the Overload bit set.

Administratively set the overload bit for the level. The overload bit will continue to be set if the implementation runs out of memory, independent of this variable

If set, the overload bit should be set, and cleared after sysUpTime exceeds this value.

Which style of Metric do we generate in our LSPs at this level? This object follows the replaceOnlyWhileDisabled behavior.

Which style of Metric do we consider in our SPF computation at this level?

Do we do Traffic Engineering at this level?

This object describes attributes associated with one Circuit

The table of circuits used by each instance of Integrated IS-IS on this system.

An isisD13CircEntry exists for each circuit used by Integrated IS-IS on this system.

The identifier of this circuit, unique within the instance of the IS-IS protocol. This object follows the index behavior. This is for SNMP Indexing purposes only and need not have any relation to any protocol value.

The value of ifIndex for the interface to which this circuit corresponds. This object cannot be modified after creation

A specifier for the part of the interface ifIndex to which this circuit corresponds, such as a DLCI or VPI/VCI. This object cannot be modified after creation

The administrative state of the circuit. This object follows the AdminState behavior.

The existence state of this circuit. This object follows the Row Status behavior. Setting the state to 'notInService' halts the generation and processing of IS-IS protocol PDUs on this circuit. Setting the state to destroy will also erase any configuration associated with the circuit.

The type of the circuit. This object follows the replaceOnlyWhileDisabled behavior. The type specified must be compatible with the type of the interface defined by the value of isisD13CircIfIndex. Enumeration: 'broadcast': 1, 'staticOut': 4, 'staticIn': 3, 'ptToPt': 2, 'dA': 5.

If true, suppress normal transmission of and interpretation of Intra-domain IS-IS PDUs on this circuit.

Indicates which type of packets will be sent and accepted on this circuit. The values used will be modified by the settings of isisD13SysType. This object follows the replaceOnlyWhileDisabled behavior. Enumeration: 'level1': 1, 'level2': 2, 'level1L2': 3.

Should we include this interface in LSPs, even if it is not running the IS-IS Protocol?

Is this port a member of a mesh group, or blocked? Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group. Enumeration: 'inactive': 1, 'set': 3, 'blocked': 2.

Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group. If isisD13CircMeshGroupEnabled is inactive or blocked, this value is ignored.

Can we send unpadded hellos on LAN circuits? False means LAN Hellos must be padded. Implementations should allow the administrator to read this value. An implementation need not be able to support unpadded hellos to be conformant.

If the circuit is enabled, the value of sysUpTime when isisD13CircAdminState most recently entered the state on. If the circuit is not on, the value of sysUpTime when the circuit last entered state on, 0 if the circuit has never been on.

Is this circuit enabled to run 3Way handshake?

A unique value to be used as the extended circuit ID in 3Way handshake.

This object describes attributes associated with area or domain relevant within a Circuit.

Level specific information about circuits used by IS-IS

An isisD13CircLevelEntry exists for each level on each circuit used by Integrated IS-IS on this system.

The level that this entry describes. Enumeration: 'level2IS': 2, 'level1IS': 1.

The metric value of this circuit for this level.

The wide metric value of this circuit for this level.

The priority for becoming LAN Designated Intermediate System at this level.

A one byte identifier that can be used in protocol packets to identify a circuit. Values of isisD13CircLevelIDOctet do not need to be unique. They are only required to differ on LANs where the Intermediate System is the Designated Intermediate System.

The ID of the circuit allocated during initialization. If no value has been negotiated (either because the adjacency is to an End System, or because initialization has not yet successfully completed), this object has the value which would be proposed for this circuit (i.e. the concatenation of the local system ID and the one byte isisD13CircLevelIDOctet for this circuit.

The ID of the LAN Designated Intermediate System on this circuit at this level. If, for any reason, this system is not partaking in the relevant Designated Intermediate System election process, then the value returned is the zero length OCTET STRING.

This value is multiplied by the corresponding HelloTimer and the result in seconds (rounded up) is used as the holding time in transmitted hellos, to be used by receivers of hello packets from this IS

Maximum period, in milliseconds, between IIH PDUs on multiaccess networks at this level for LANs. The value at level 1 is used as the period between Hellos on L1L2 point to point circuits. Setting this value at level 2 on an L1L2 point to point circuit will result in an error of InconsistentValue. This object follows the resettingTimer behavior.

Period, in milliseconds, between Hello PDUs on multiaccess networks when this IS is the Designated Intermediate System. This object follows the resettingTimer behavior.

Minimal interval of time, in milliseconds, between transmissions of LSPs on an interface at this level.

Minimum interval, in seconds, between re-transmission of an LSP at this level. This object follows the resettingTimer behavior. Note that isisD13CircLevelLSPThrottle controls how fast we send back to back LSPs. This variable controls how fast we re-send the same LSP.

Interval of time, in seconds, between periodic transmission of a complete set of CSNPs on multiaccess networks if this router is the designated router at this level.

Minimum interval in seconds between sending Partial Sequence Number PDUs at this level. This object follows the resettingTimer behavior.

This object collects system and circuit counters

System wide counters for one instance of the IS-IS protocol on the system.

System-wide IS-IS counters.

The level that this entry describes. Enumeration: 'level2IS': 2, 'level1IS': 1.

Number of corrupted in-memory LSPs detected. LSPs received from the wire with a bad checksum are silently dropped and not counted.

The number of authentication type mismatches recognized by this instance of the protocol.

The number of authentication failures recognized by this instance of the protocol.

Number of times the LSP database has become overloaded.

Number of times a manual address has been dropped from the area.

Number of times the IS has attempted to exceed the maximum sequence number.

Number of times a sequence number skip has occurred.

Number of times a zero-aged copy of the system's own LSP is received from some other node.

Number of times a PDU is received with a different value for ID field length to that of the receiving system.

Number of times a PDU is received with a different value for MaximumAreaAddresses from that of the receiving system.

Partition changes

Number of times we ran SPF at this level.

Circuit specific counters for one instance of the IS-IS protocol on the system.

An isisD13CircCountEntry exists for each circuit used by Integrated IS-IS on this system.

What type of circuit saw these counts? The point to point Hello PDU includes both L1 and L2, and ISs form a single adjacency on point to point links. Thus we combine counts on point to point links into one group. Enumeration: 'lanlevel2': 2, 'lanlevel1': 1, 'p2pcircuit': 3.

The number of times an adjacency state change has occurred on this circuit.

The number of adjacencies on this circuit.

The number of times initialization of this circuit has failed.

The number of times an adjacency has been rejected on this circuit.

The number of times an IS-IS control PDU with an ID field length different to that for this system has been received.

The number of times an IS-IS control PDU with a max area address field different to that for this system has been received.

The number of times an IS-IS control PDU with an auth type field different to that for this system has been received.

The number of times an IS-IS control PDU with the correct auth type has failed to pass authentication validation.

The number of times the Designated IS has changed on this circuit at this level. If the circuit is point to point, this count is zero.

Information about IS-IS protocol traffic at one level on one circuit in one direction

Information about IS-IS protocol traffic at one level on one circuit in one direction

The level at which these PDU counts have been collected. Enumeration: 'level1': 1, 'level2': 2.

Were we sending or receiving these PDUs? Enumeration: 'sending': 1, 'receiving': 2.

The number of IS-IS Hello PDUs seen in this direction at this level. Point-to-Point IIH PDUs are counted at Level 1 if the value of their Circuit Type field is 1, and are counted at Level 2 otherwise.

The number of ES-IS Hello PDUs seen in this direction. ISH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.

The number of ES Hello PDUs seen in this direction. ESH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.

The number of IS-IS LSPs seen in this direction at this level.

The number of IS-IS CSNPs seen in this direction at this level.

The number of IS-IS PSNPs seen in this direction at this level.

The number of unknown IS-IS PDUs seen at this level.

This object describes attributes associated with an adjacent Protocol Peer.

The table of adjacencies to Intermediate Systems.

Each entry corresponds to one adjacency to an Intermediate System on this system.

A unique value identifying the IS adjacency from all other such adjacencies on this circuit. This value is assigned by the system when the adjacency is created automatically.

The state of the adjacency Enumeration: 'down': 1, 'failed': 4, 'up': 3, 'initializing': 2.

The 3Way state of the adjacency. These are picked to match the historical on-the-wire representation of the 3Way state, and are not intended to match isisD13ISAdjState. Enumeration: 'down': 2, 'failed': 3, 'up': 0, 'initializing': 1.

The SNPA address of the neighboring system.

The type of the neighboring system. Enumeration: 'l1IntermediateSystem': 1, 'l1L2IntermediateSystem': 3, 'l2IntermediateSystem': 2, 'unknown': 4.

The system ID of the neighboring Intermediate System.

The 4 byte Extended Circuit ID learned from the Neighbor during 3-way handshake, or 0.

How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at level 1, and level2 for the adjacency between peers at level 2. Enumeration: 'level1': 1, 'level2': 2, 'level1and2': 3.

The holding time in seconds for this adjacency. This value is based on received IIH PDUs and the elapsed time since receipt.

Priority of the neighboring Intermediate System for becoming the Designated Intermediate System.

If the isisD13ISAdjState is in state 'up', the value of sysUpTime when the adjacency most recently entered the state 'up', or 0 if it has never been in state 'up'.

This table contains the set of Area Addresses of neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one Area Address reported by a neighboring Intermediate System in its IIH PDUs.

An index for the areas associated with one neighbor. This provides a simpler way to walk the table.

One Area Address as reported in IIH PDUs received from the neighbor.

This table contains the set of IP Addresses of neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one IP Address reported by a neighboring Intermediate System in its IIH PDUs.

An index to this table which identifies the IP addresss to which this entry belongs.

The type of one IP Address as reported in IIH PDUs received from the neighbor.

One IP Address as reported in IIH PDUs received from the neighbor.

This table contains the set of protocols supported by neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one protocol supported by a neighboring Intermediate System as reported in its IIH PDUs.

One supported protocol as reported in IIH PDUs received from the neighbor.

This object describes attributes associated with a configured address

The table of Reachable Addresses to NSAPs or Address Prefixes.

Each entry defines a Reachable Address to a NSAP or Address Prefix.

The identifier for this isisD13RAEntry. This value must be unique amongst all Reachable Addresses on the same parent Circuit. This object follows the index and ManualOrAutomatic behaviors.

The existence state of this Reachable Address. This object follows the ManualOrAutomatic behaviors.

The administrative state of the Reachable Address. This object follows the AdminState and ManualOrAutomatic behaviors.

The destination of this Reachable Address. This is an Address Prefix. This object follows the replaceOnlyWhileDisabled and ManualOrAutomatic behaviors.

The type of mapping to be employed to ascertain the SNPA Address which should be used in forwarding PDUs for this Reachable Address prefix. This object follows the ManualOrAutomatic behavior. The following values of mapping type are defined: none: The mapping is null because the neighbor SNPA is implicit by nature of the subnetwork (e.g. a point-to-point linkage). explicit: The subnetwork addresses in the object isisD13RASNPAAddress is to be used. extractIDI: The SNPA is embedded in the IDI of the destination NSAP Address. The mapping algorithm extracts the SNPA to be used according to the format and encoding rules of ISO8473/Add2. This SNPA extraction algorithm can be used in conjunction with Reachable Address prefixes from the X.121, F.69, E.163 and E.164 addressing subdomains. extractDSP: All, or a suffix, of the SNPA is embedded in the DSP of the destination address. This SNPA extraction algorithm extracts the embedded subnetwork addressing information by performing a logical AND of the isisD13RASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the isisD13RASNPAPrefix object value to form the next hop subnetwork addressing information. Enumeration: 'none': 1, 'explicit': 2, 'extractDSP': 4, 'extractIDI': 3.

The metric value for reaching the specified prefix over this circuit. This object follows the ManualOrAutomatic behavior.

Indicates whether the metric is internal or external. This object follows the ManualOrAutomatic behavior.

The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches the address prefix of the Reachable Address. This object follows the ManualOrAutomatic behavior.

A bit mask with 1 bits indicating the positions in the effective destination address from which embedded SNPA information is to be extracted. For the extraction the first octet of the isisD13RASNPAMask object value is aligned with the first octet (AFI) of the NSAP Address. If the isisD13RASNPAMask object value and NSAP Address are of different lengths, the shorter of the two is logically padded with zeros before performing the extraction. This object follows the ManualOrAutomatic behavior.

A fixed SNPA prefix for use when the isisD13RAMapType is extractDSP. The SNPA Address to use is formed by concatenating the fixed SNPA prefix with a variable SNPA part that is extracted from the effective destination address. For Reachable Address prefixes in which the entire SNPA is embedded in the DSP the SNPA Prefix shall be null. This object follows the ManualOrAutomatic behavior.

The type of Reachable address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of routing information from another routing protocol (eg. IDRP). Enumeration: 'manual': 1, 'automatic': 2.

This object describes attributes associated with IP routes learned by configuration or through another protocol.

The table of IP Reachable Addresses to networks, subnetworks or hosts either manually configured or learned from another protocol.

Each entry defines an IP Reachable Address to a network, subnetwork or host.

The type of this IP Reachable Address. This object follows the ManualOrAutomatic behavior.

The destination of this IP Reachable Address. This is either a network address, subnetwork address or host address. This object follows the ManualOrAutomatic behavior.

The length of the IP Netmask for Reachability Address. This object follows the ManualOrAutomatic behavior.

The type of the IP next hop address.

The IP next hop to this destination.

The type of this IP Reachable Address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of routing information from another routing protocol. This object follows the ManualOrAutomatic behavior. Enumeration: 'manual': 1, 'automatic': 2.

The state of this IP Reachable Address. This object follows the ExistenceState and ManualOrAutomatic behaviors.

The administrative state of the IP Reachable Address. This object follows the AdminState and ManualOrAutomatic behaviors.

The metric value for reaching the specified destination over this circuit. This object follows the ManualOrAutomatic behavior.

Indicates whether the metric is internal or external. This object follows the ManualOrAutomatic behavior.

The wide metric value for reaching the specified destination over this circuit. This object follows the ManualOrAutomatic behavior.

The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches this IP Reachable Address. This object follows the ManualOrAutomatic behavior.

The origin of this route. Enumeration: 'isisD13': 5, 'igrp': 7, 'direct': 2, 'rip': 6, 'ospfv3': 4, 'bgp': 9, 'eigrp': 8, 'other': 10, 'static': 1, 'ospfv2': 3.

This object describes the collection of Link State PDUs known to the system.

The table of LSP Headers.

Each entry describes an LSP current stored in the system.

At which level does this LSP appear?

The 8 byte LSP ID, consisting of the SystemID, Circuit ID, and Fragment Number.

The sequence number for this LSP.

Is this LSP being purged by this System?

The 16 bit Fletcher Checksum.

The remaining lifetime in seconds for this LSP.

The length of this LSP.

Flags carried by the LSP.

The contents of each LSP.

Each entry describes an LSP current stored in the system.

The index of this TLV in the LSP. The first TLV has index 1 and the Nth TLV has an index of N.

The sequence number for this LSP.

The 16 bit Fletcher Checksum.

The Type of this TLV.

The length of this TLV.

The value of this TLV.

Objects included in Notifications.

Objects seen in the most recent notification this instance of the IS-IS protocol.

Each entry defines variables relevant to notifications for one instance of the IS-IS protocol.

An Octet String that uniquely identifies a Link State PDU.

Holds up to the first 64 bytes of a PDU that triggered the notification.

Holds the System ID length reported in PDU we received.

Holds the Max Area Addresses reported in a PDU we received.

Holds the Protocol version reported in PDU we received.

Holds the size of LSP we received that is too big to forward.

Holds the size of isisD13SysOrigLSPBuffSize advertised by peer in TLV.

The list of protocols supported by an adjacent system. This may be empty.

The current state of an adjacency. Enumeration: 'down': 1, 'failed': 4, 'up': 3, 'initializing': 2.

The Router ID of a remote system. If not known, we set this to 0.

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 isisD13SysStatLSPDbaseOloads.

This notification is generated when one of the manual areaAddresses assigned to this system is ignored when computing routes. The object isisD13ManAreaAddrExistState describes the area that has been dropped. The number of times this event has been generated is counted by isisD13SysManAddrDropFromAreas. This notification is edge triggered, and should not be regenerated until an address that was used in the previous computation has been dropped.

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 isisD13SysCorrLSPs. 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

A notification sent when a Level 1 LSP or Level 2 LSP is received which is larger than the local value for isisD13OriginatingBufferSize, or when an LSP is received containing the isisD13OriginatingBufferSize option and the value in the PDU option field does not match the local value for isisD13OriginatingBufferSize. 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.

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.

A notification sent when an adjacency changes state, entering or leaving state up. The first 6 bytes of the isisD13PduLspId are the SystemID of the adjacent IS. The isisD13AdjState is the new state of the adjacency.

The collections of objects used to manage an IS-IS router.

The collection of objects used to describe in IS-IS Circuit.

The collections of objects used to manage an IS-IS Adjacency.

The objects used to record notification parameters.

The collections of notifications sent by an IS.

The collections of objects used to count protocol PDUs.

The collections of objects used to manage the reachable NSAP prefixes.

The collections of objects used to manage configured IP addresses.

The collections of objects used to observe the LSP Data Base.

The compliance statement for agents that support the IS-IS MIB

The compliance statement for agents that support the IS-IS MIB