This notification is generated when the system
enters or leaves the Overload state. The number
of times this has been generated and cleared is kept
track of by isisSysStatLSPDbaseOloads.
isisAttemptToExceedMaxSequence
.1.3.6.1.4.1.629.10.10.2.0.10
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.
isisSequenceNumberSkip
.1.3.6.1.4.1.629.10.10.2.0.11
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.
isisCircIndTable
.1.3.6.1.4.1.629.10.10.2.0.12
A notification sent when the value of isisCircOperState for
a circuit changes to operStatusUp, operStatusDown or
operStatusActFailed.
isisExtPassCircuitInd
.1.3.6.1.4.1.629.10.10.2.0.13
A notification sent when the value of isisCircOperState for
a circuit not configured to run the IS-IS protocol (such as
an external, TE-only or passive circuit) changes to
operStatusUp, operStatusDown or operStatusActFailed.
isisOperStateChange
.1.3.6.1.4.1.629.10.10.2.0.14
This notification is generated when the IS-IS system
changes operational state to operStatusUp, operStatusDown or
operStatusActFailed.
isisLspAuthFailure
.1.3.6.1.4.1.629.10.10.2.0.15
An IS-IS instance sends this notification if a received
LSP has failed to authenticate.
isisHelloAuthFailure
.1.3.6.1.4.1.629.10.10.2.0.16
An IS-IS instance sends this notification if a received
Hello has failed to authenticate.
isisAttachedStateChange
.1.3.6.1.4.1.629.10.10.2.0.17
This notification is generated when the Attached state for a
topology changes and the topology is operationally up.
isisDisChange
.1.3.6.1.4.1.629.10.10.2.0.18
An IS-IS instance sends this notification if the DIS changes
at level 1 or level 2.
isisManualAddressDrops
.1.3.6.1.4.1.629.10.10.2.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 isisSysManAddrDropFromAreas.
This notification is edge triggered, and should not
be regenerated until an address that was used in
the previous computation has been dropped.
isisIDLenMismatch
.1.3.6.1.4.1.629.10.10.2.0.3
A notification sent when we receive a PDU
with a different value of the System ID Length.
This notification includes 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 on the same circuit.
isisMaxAreaAddressesMismatch
.1.3.6.1.4.1.629.10.10.2.0.4
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 the same circuit.
isisOwnLSPPurge
.1.3.6.1.4.1.629.10.10.2.0.5
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.
isisAreaMismatch
.1.3.6.1.4.1.629.10.10.2.0.6
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 the same circuit.
isisRejectedAdjacency
.1.3.6.1.4.1.629.10.10.2.0.7
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 circuit.
isisAdjacencyChange
.1.3.6.1.4.1.629.10.10.2.0.8
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.
isisLSPErrorDetected
.1.3.6.1.4.1.629.10.10.2.0.9
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.