ted LSP Detected Notification is generated when
a corrupted Link State PDU is detected in memory.
hwIsisMaxAreaAddrMismatch
.1.3.6.1.4.1.2011.5.25.24.4.10
when a PDU is received from Wrong/different
area not recognised by this system
hwIsisManualAddressDroppedFromArea
.1.3.6.1.4.1.2011.5.25.24.4.11
Address Dropped From Area Notification is generated
when one of the manualAreaAddresses (specified on this system) is
ignored when computing partitionAreaAddresses or areaAddresses
because there are more than MaximumAreaAddresses distinct
Area Addresses. The hwIsisTrapDroppedAreaAddr argument
is set to the ignored Area Address. It is generated once for
each Area Address in manualAreaAddresses which is dropped.
The occurance of this event is counted by the
isisSysManAddrDropFromAreas counter.
hwIsisAttemptToExceedMaximumSequenceNumber
.1.3.6.1.4.1.2011.5.25.24.4.12
t To Exceed Maximum Sequence Number Notification is
generated when an attempt is made to increment the sequence
number of an LSP beyond the maximum sequence number.
Following the generation of this event the operation of the
Routeing state machine shall be disabled for atleast
(MaxAge + ZeroAgeLifetime) seconds. The occurance of this
event is counted by the isisSysAttmptToExMaxSeqNums
counter.
hwIsisSequenceNumberSkip
.1.3.6.1.4.1.2011.5.25.24.4.13
ce Number Skipped Notification is generated when the
sequence number of an LSP is incremented by more than one. The
occurance of this event is counted by the isisSysSeqNumSkips
counter.
hwIsisOwnLSPPurge
.1.3.6.1.4.1.2011.5.25.24.4.14
P Purged Notification is generated when a zero aged copy
of a system's own LSP is received from some other system. This
represents an erroneous attempt to purge the local system's LSP.
The occurance of this event is counted by the isisSysOwnLSPPurges
counter.
hwIsisCircuitChange
.1.3.6.1.4.1.2011.5.25.24.4.15
t Change Notification is generated when the state of
the Circuit changes from On to Off or from Off to On. The relative
order of events relating to the same Circuit must be preserved.
hwIsisAdjacencyStateChange
.1.3.6.1.4.1.2011.5.25.24.4.16
ncy State Change Notification is generated when the state
of an Adjacency on the Circuit changes from Up to Down or Down to
Up. For these purposes the states Up and Up/dormant are considered
to be Up, and any other state is considered to be Down. The occurance
of this event is counted by the isisCircAdjChanges counter.
hwIsisInitializationFailure
.1.3.6.1.4.1.2011.5.25.24.4.17
lisation Failure Notification is
generated when an attempt to initialise with an adjacent system fails
as a result of either Version Skew or Area Mismatch. In the case of
Version Skew, the Adjacent system argument is not present. The
occurance of this event is counted by the isisCircInitFails counter.
hwIsisRejectedAdjacency
.1.3.6.1.4.1.2011.5.25.24.4.18
ed Adjacency Notification is generated when an attempt
to create a new adjacency is rejected, because of a lack of resources. The occurance of this event is counted by the isisCircRejAdjs counter.
hwIsisLanL1DesignatedIntermediateSystemChange
.1.3.6.1.4.1.2011.5.25.24.4.19
Designated Intermediate System Change Notification
is generated when the local system either elects itself or resigns as
being the LAN L1 Designated Intermediate System on this
circuit. The relative order of these events must be
preserved. The occurance of this event is counted by
the isisCircLANL1DesISChanges counter.
hwIsisCorruptedLSPReceived
.1.3.6.1.4.1.2011.5.25.24.4.2
ted LSP Received Notification is generated when
a corrupted Link State PDU is Received. The occurance of
this event is counted by the isisSysCorrLSPscounter.
hwIsisLanL2DesignatedIntermediateSystemChange
.1.3.6.1.4.1.2011.5.25.24.4.20
Designated Intermediate System Change Notification
is generated when the local system either elects itself or resigns as
being the LAN L2 Designated Intermediate System on this
circuit. The relative order of these events must be
preserved. The occurance of this event is counted by
the isisCircLANL2DesISChanges counter.
hwIsisLSPL1DatabaseOverload
.1.3.6.1.4.1.2011.5.25.24.4.3
Database Overload Notification is generated when the
l1State of the system changes between On and Waiting or Waiting
and On. The isisSysL1State argument is set to indicate the
resulting state, and in the case of Waiting the isisSysID is
set to indicate the source of the LSP which precipitated the
overload. The occurance of this event is counted by the
isisSysLSPL1DbaseOloads counter.
hwIsisLSPL2DatabaseOverload
.1.3.6.1.4.1.2011.5.25.24.4.4
Database Overload Notification is generated when the
l2State of the system changes between On and Waiting or Waiting and
On. The isisSysL2State argument is set to indicate the
resulting state, and in the case of Waiting the isisSysID is set to
indicate the source of the LSP which precipitated the overload.
The occurance of this event is counted by the
isisSysLSPL2DbaseOloads counter.
hwIsisAuthenticationFailure
.1.3.6.1.4.1.2011.5.25.24.4.5
when a PDU is received with an incorrect
Authentication information field
hwIsisWrongSysType
.1.3.6.1.4.1.2011.5.25.24.4.6
when a Adjacency Request for Wrong/unsupported
adjacency type is made.
hwIsisVersionSkew
.1.3.6.1.4.1.2011.5.25.24.4.7
Generated when a PDU of Wrong/different version is received
hwIsisIDFieldLengthMismatch
.1.3.6.1.4.1.2011.5.25.24.4.8
IDFieldLengthMismatch Notification is generated when a PDU is
received with a different value for ID field length to that of the
receiving Intermediate system. The occurance of this
event is counted by the isisSysIDFieldLenMismatches.
hwIsisAreaMismatch
.1.3.6.1.4.1.2011.5.25.24.4.9
when a PDU is received from Wrong/different
area not recognised by this system