This module describes an authoritative enterprise-specific Simple
Network Management Protocol (SNMP) Management Information Base (MIB):
For the Birds Of Prey Product Line
Configuration Of Global ISIS Configuration Parameters.
This MIB has been taken from Alcatel 7x50 device ISIS MIB
with minor modifications.
Copyright 2003-2007 Alcatel-Lucent.
ALL RIGHTS RESERVED WORLDWIDE
Reproduction of this document is authorized on the condition that
the foregoing copyright notice is included.
This SNMP MIB module (Specification) embodies Alcatel's
proprietary intellectual property. Alcatel retains
all title and ownership in the Specification, including any
revisions.
Alcatel grants all interested parties a non-exclusive
license to use and distribute an unmodified copy of this
Specification in connection with management of Alcatel
products, and without fee, provided this copyright notice and
license appear on all copies.
This Specification is supplied 'as is', and Alcatel
makes no warranty, either express or implied, as to the use,
operation, condition, or performance of the Specification.
This notification is generated when the system enters or leaves the
Overload state.
vRtrIsisAuthFail
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.10
A notification sent when we receive a PDU with incorrent
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.
vRtrIsisVersionSkew
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.11
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.
vRtrIsisAreaMismatch
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.12
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.
vRtrIsisRejectedAdjacency
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.13
A notification 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.
vRtrIsisLSPTooLargeToPropagate
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.14
A notification 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.
vRtrIsisOrigLSPBufSizeMismatch
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.15
A notification sent when a Level 1 LSP or Level
2 LSP is received which is larger than the local
value for originatingL1LSPBufferSize or
originatingL2LSPBufferSize 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 originatingL1LSPBufferSize or originatingL2LSPBufferSize
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.
vRtrIsisProtoSuppMismatch
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.16
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.
vRtrIsisAdjacencyChange
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.17
A notification sent when an adjacency changes state,
entering or leaving state up. The first 6 bytes of the
vRtrIsisTrapLSPID are the SystemID of the adjacent IS.
The isisISAdjState is the new state of the adjacency.
vRtrIsisCircIdExhausted
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.18
A notification sent when ISIS 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.
In such a case the interface is marked operationally
down. When an operationally up interface is deleted, the
circId can be reused by any interface which is waiting to
receive a unique circId.
vRtrIsisAdjRestartStatusChange
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.19
A notification sent when an adjancency's
graceful restart status changes.
The vRtrIsisISAdjRestartStatus is the new
graceful restart state of the adjacency.
vRtrIsisManualAddressDrops
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.2
This notification is generated when one of the manual areaAddresses
assigned to this system is ignored when computing routes. The object
vRtrIsisManAreaAddrExistState 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.
vRtrIsisCorruptedLSPDetected
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.3
This 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.
vRtrIsisMaxSeqExceedAttempt
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.4
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.
vRtrIsisIDLenMismatch
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.5
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.
vRtrIsisMaxAreaAddrsMismatch
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.6
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.
vRtrIsisOwnLSPPurge
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.7
A notification 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.
vRtrIsisSequenceNumberSkip
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.8
When we recieve 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.
vRtrIsisAutTypeFail
.1.3.6.1.4.1.6486.801.1.2.1.10.14.1.11.0.9
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.