[CAUSE] The tmnxIsisDatabaseOverload notification is generated when
the system enters or leaves the Overload state.
          
[EFFECT] Database is overloaded.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisAuthFail notification is 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisVersionSkew notification is 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisAreaMismatch notification is 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisRejectedAdjacency notification is sent when we
receive a Hello PDU from an IS, but do not establish an adjacency due
to a lack of resources.
          
This should be an edge-triggered notification. We should not send a
second notification about PDUs received from the same source.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisLSPTooLargeToPropagate notification is sent when
we attempt to propagate an LSP which is larger than the
dataLinkBlockSize for a circuit.
          
This should be an edge-triggered notification. We should not send a
second notification about PDUs received from the same source.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisOrigLSPBufSizeMismatch notification is sent when
a Level 1 LSP or Level 2 LSP is received which is larger than
the local value for tmnxIsisLevelLSPBuffSize or
tmnxIsisSysOrigL1LSPBuffSize or tmnxIsisSysOrigL2LSPBuffSize
respectively, or when a Level 1 LSP or Level2 LSP is received
containing the originatingLSPBufferSize option and the value in
the PDU option field does not match the local value
for tmnxIsisLevelLSPBuffSize or tmnxIsisSysOrigL1LSPBuffSize or
tmnxIsisSysOrigL2LSPBuffSize respectively.  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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisProtoSuppMismatch notification is 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisAdjacencyChange notification is sent when an
adjacency changes state, entering or leaving state up.
          
The first 6 bytes of the tmnxIsisNotifTrapLSPID are the SystemID of
the adjacent IS.
          
The isisISAdjState is the new state of the adjacency.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisCircIdExhausted notification is sent when the
specific ISIS level cannot be started on a LAN interface as a unique
circid could not be assigned due to the exhaustion of the circid
space.
          
This could happen only on the broadcast interfaces.
          
[EFFECT] In such a case the interface is marked operationally down.
          
[RECOVERY] When an operationally up interface is deleted, the circid
can be reused by any interface which is waiting to receive a unique
circid.

[CAUSE] The tmnxIsisAdjRestartStatusChange notification is sent when
an adjacency's graceful restart status changes.
          
The tmnxIsisISAdjRestartStatus is the new graceful restart state of
the adjacency.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] This notification is generated when one of the manual area
addresses assigned to this system is ignored when computing routes.
The object isisManAreaAddrExistState describes the area that has been
dropped.
          
This notification is edge triggered, and should not be regenerated
until an address that was used in the previous computation has been
dropped.
          
[EFFECT] Assigned manual area address is ignored for computing routes.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisLdpSyncTimerStarted notification is sent when the
vRtrIfLdpSyncTimer is started.
          
The timer is started from the time the LDP session to the neighbor is
up over the interface.
          
[EFFECT] This allows for the label FEC bindings to be exchanged.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisLdpSyncExit notification is sent when IGP-LDP
synchronization has stopped.
          
The cause of this event is indicated by tmnxIsisIfLdpSyncTimerState,
one of them being expiry of vRtrIfLdpSyncTimer.
          
[EFFECT] The IGP link metric is restored to normal levels.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisExportLimitReached notification is sent when the
total number of exported routes for the level is equal to the
configured limit for exported routes, tmnxIsisExportLimit.
          
[EFFECT] Additional routes would not be exported into this ISIS level
from the route table.
          
[RECOVERY] Change ISIS export policy.

[CAUSE] The tmnxIsisExportLimitWarning notification is sent when the
total number of exported routes or the level is equal to the
configured percent, tmnxIsisExportLimitLogPercent of the export limit,
tmnxIsisExportLimit.
          
Additional routes will continue to be exported into this ISIS level
from the route table till the export limit is reached.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisRoutesExpLmtDropped notification is sent when the
total number of exported routes from the route table to this ISIS
level drops below the configured export limit, tmnxIsisExportLimit.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] A tmnxIsisFailureDisabled notification is generated when ISIS
is operationally brought down. Reason for the failure is indicated by
tmnxIsisFailureReasonCode.
          
[EFFECT] ISIS is now operationally down.
          
[RECOVERY] ISIS will auto restart.

[CAUSE] This notification is generated when ISIS receives an IOM or
CPM failure (system exhausted ILM, NHLFE, duplicate SID) while
resolving and programming a received prefix SID.
          
[EFFECT] The Segment Routing tunnel corresponding to this SID will not
be programmed.
          
[RECOVERY] In case of system exhaustion, the IGP instance goes into
overload. The operator must manually clear the IGP overload condition
after freeing resources. IGP will attempt to program at the next SPF
all tunnels which previously failed the programming operation

[CAUSE] The tmnxIsisCorruptedLSPDetected notification is generated
when we find that and LSP that was stored in memory has become
corrupted.
          
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.
          
[EFFECT] LSP is dropped.
          
[RECOVERY] No recovery is necessary.

[CAUSE] This notification is generated when ISIS receives a SID which
is not within the label range of the nhop router.
          
[EFFECT] The Segment Routing tunnel corresponding to this SID will not
be programmed.
          
[RECOVERY] Increase the label range or change the SID index to be
within the current label range.

[CAUSE] The tmnxIsisRejectedAdjacencySid notification is sent when we
do not establish an adjacency SID due to a lack of resources.
          
This should be an edge-triggered notification. We should not send a
second notification about adjacency SID allocation failure for the
same adjacency.
          
[EFFECT] No effect.
          
[RECOVERY] When an operationally up interface is deleted, the ADJ-SID
can be reused by any interface which is waiting to receive an ADJ-SID.

[CAUSE] The tmnxIsisLSPPurge notification is sent when a LSP is
purged.
          
This notification includes the system ID of the originator, or the
upstream source of the purge, which may help a network manager to
locate the origin of the purge and thus the cause of the purge.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisPfxLimitOverloadWarning notification is sent when
the number of prefixes in the system reaches the
tmnxIsisPrefixLimitThreshold or the tmnxIsisPrefixLimit.
          
[EFFECT] When tmnxIsisPrefixLimit is not yet reached, but the
tmnxIsisPrefixLimitThreshold is reached there is no direct effect; but
when the number of prefixes grows the system might go into overload.
When the tmnxIsisPrefixLimit is reached and the object
tmnxIsisPrefixLimitLogOnly is false, IS-IS will be in overload. There
is no direct effect when the object tmnxIsisPrefixLimitLogOnly is
true.
          
[RECOVERY] Increase the IS-IS prefix limit.

[CAUSE] The tmnxIsisAdjBfdSessionSetupFail notification is sent when
BFD session setup fails.
          
The first 6 bytes of the tmnxIsisNotifTrapLSPID are the SystemID of
the adjacent IS.
          
[EFFECT] The system can not setup the BFD session.
          
[RECOVERY] Depending on the tmnxIsisBfdSessSetupFailReason, recovery
can be possible. Check the BFD configuration to recover.

[CAUSE] The tmnxIsisSrgbBadLabelRange notification is sent when ISIS
receives a bad SRGB label range from a router (for example,
overlapping with another label range).
          
[EFFECT] The configured Segment Routing tunnels will be wrong.
          
[RECOVERY] Change the label range to recover.

[CAUSE] The tmnxIsisCircMtuTooLow notification is sent when we attempt
to a) configure a circuit which cannot propagate an LSP or SNP with
max size tmnxIsisLevelLSPBuffSize. b) configure
tmnxIsisLevelLSPBuffSize which is bigger than
tmnxIsisLevelMaxOperLSPBuffSize. c) configure
tmnxIsisSysOrigL1LSPBuffSize or tmnxIsisSysOrigL2LSPBuffSize which is
bigger than tmnxIsisLevelMaxOperLSPBuffSize.
          
[EFFECT] No effect.
          
[RECOVERY] Increase port-mtu or decrease lsp-mtu.

[CAUSE] The tmnxIsisRejectedAdjacencySet notification is sent when an
adjacency can not be assigned to an adjacency-set because it does not
terminate on the same neighbor node as the other adjacencies.
          
This notification each time the adjacency-set is programmed.
          
[EFFECT] Adjacency-set nhops will not include this adjacency.
          
[RECOVERY] Remove the interface from the adjacency-set or change the
adjacency-set type to non parallel.

[CAUSE] The tmnxIsisCorruptRemainingLifetime notification is sent when
an LSP is received with a possible corrupt Remaining Lifetime field.
          
The Remaining Lifetime of a received LSP is considered as possible
corrupt based on following algorithm:
          
- The LSP has passed all acceptance tests.
- The LSP is newer than the copy in the local LSPDB or no copy present.
- The Remaining Lifetime in the received LSP is less than Zero Age Lifetime.
- The adjacency to the neighbor from which the LSP is received has been up
  for a minimum of Zero Age Lifetime.
          
[EFFECT] It is possible that an LSP is purged prematurely.
          
[RECOVERY] The ISIS system will try to recover by setting the
Remaining Lifetime to the tmnxIsisLspMinRemainingLifetime value.

[CAUSE] The tmnxIsisSidStatsIndexAlloc notification is sent when the
system is not able to allocate a statistic index to at least one SID.
This indication is sent once, i.e. if the system retries to allocate a
stat index but fails no new notification is sent. Conversely, in case
the system resolves the situation and allocates stat indices to all
needed SIDs a notification is sent to indicate that stat allocation is
in nominal state.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisMaxSeqExceedAttempt notification is generated when
the sequence number on an LSP wraps the 32 bit sequence counter, we
purge and wait to re-announce this information. Since these should not
be generated rapidly, we generate an event each time this happens.
          
A possible cause could be that the same system-id is configured on
multiple nodes; when 2 nodes have the same system-id they both keep
incrementing its LSP sequence number causing the sequence counter to
rollover.
          
While the first 6 bytes of the LSPID are ours, the other two contain
useful information.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisFaOperParticipationDown notification is
sent when the Flexible Algorithm Participation is operationally down.
This notification occurs each time when:
a) there are no Flexible Algorithm Definitions(FADs) present for
   the Flexible Algorithm.
b) the FAD chosen for Flex-Algo calculation has unsupported
   parameters like unsupported:
   1. Metric-Type
   2. Calculation-Type
   3. Constraint
   4. Fad-Flags
   5. Sub-Tlv
          
[EFFECT] The node will cease to participate in that Flexible
Algorithm,  and won't advertise its participation in SR-algo sub-TLV.
          
[RECOVERY] The operator may make sure if at least one FAD is present
for that Flexible Algorithm, and in case of unsupported FAD, correct
the FAD parameters to send supported values from remote side.

[CAUSE] The tmnxIsisIDLenMismatch notification is sent when we receive
a PDU with a different value of the System ID Length.
          
This notification includes the 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisMaxAreaAddrsMismatch notification is 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.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

[CAUSE] The tmnxIsisOwnLSPPurge notification is sent when we receive a
PDU with our SystemID and zero age.
          
This notification includes the circuit Index if available, which may
help a network manager identify the source of the confusion.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.