This document is the SNMP MIB module to manage and provision OSPF
protocol for the Nokia SROS device.
Copyright 2003-2018 Nokia. All rights reserved.
Reproduction of this document is authorized on the condition that
the foregoing copyright notice is included.
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property. Nokia retains
all title and ownership in the Specification, including any
revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied 'as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
A tmnxOspfVirtIfStateChange notification is generated when there has
been a change in the state of an OSPF virtual interface.
This notification should be generated when the interface state
regresses (e.g., goes from Point-to-Point to Down) or progresses to a
terminal state (i.e., Point-to-Point).
tmnxOspfIfTxRetransmit
.1.3.6.1.4.1.6527.3.1.3.36.0.10
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgIfTxRetransmit.
tmnxOspfVirtIfTxRetransmit
.1.3.6.1.4.1.6527.3.1.3.36.0.11
A tmnxOspfVirtIfTxRetransmit notification is generated when an OSPF
packet has been retransmitted on a virtual interface.
tmnxOspfAreaOriginateLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.12
A tmnxOspfAreaOriginateLsa notification is generated when a new
LSA has been originated by this router. This notification should
not be invoked for simple refreshes of LSAs (which happens every
30 minutes), but instead will only be invoked when an LSA is
(re)originated due to a topology change. Additionally, this
notification does not include LSAs that are being flushed because
they have reached 'MaxAge'.
tmnxOspfAreaMaxAgeLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.13
A tmnxOspfAreaMaxAgeLsa notification is generated when one of the area
scope LSAs in the router's link-state database has aged to 'MaxAge'.
tmnxOspfLsdbOverflow
.1.3.6.1.4.1.6527.3.1.3.36.0.14
A tmnxOspfLsdbOverflow notification is generated when the number of
LSAs in the router's link-state database has exceeded limit indicated
by tmnxOspfExtLsdbLimit.
tmnxOspfLsdbApproachingOverflow
.1.3.6.1.4.1.6527.3.1.3.36.0.15
A tmnxOspfLsdbApproachingOverflow notification is generated when the
number of LSAs in the router's link-state database has exceeded ninety
percent of the value indicated by tmnxOspfExtLsdbLimit.
tmnxOspfIfStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.16
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgIfStateChange.
tmnxOspfNssaTranslatorStatusChg
.1.3.6.1.4.1.6527.3.1.3.36.0.17
A tmnxOspfNssaTranslatorStatusChg notification is generated
when there has been a change in the router's ability to translate
OSPF type-7 LSAs into OSPF type-5 LSAs. This notification should be
generated when the Translator Status transitions from or to any
defined status on a per area basis.
tmnxOspfRestartStatusChange
.1.3.6.1.4.1.6527.3.1.3.36.0.18
A tmnxOspfRestartStatusChange notification is generated when
there has been a change in the graceful restart state for the
router. This notification should be generated when the router
restart status changes.
tmnxOspfNbrRestartHlprStsChg
.1.3.6.1.4.1.6527.3.1.3.36.0.19
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgNbrRestartHlprStsChg.
tmnxOspfNbrStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.2
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgNbrStateChange.
tmnxOspfVirtNbrRestartHlprStsChg
.1.3.6.1.4.1.6527.3.1.3.36.0.20
An tmnxOspfVirtNbrRestartHlprStsChg notification is
generated when there has been a change in the graceful restart
helper state for the virtual neighbor. This notification should
be generated when the virtual neighbor restart helper status
transitions for a virtual neighbor.
tmnxOspfSpfRunsStopped
.1.3.6.1.4.1.6527.3.1.3.36.0.21
A tmnxOspfSpfRunsStopped trap signifies that there are insufficient
memory resources on the system to run the SPF to completion.
Consequently, OSPF will stop running SPFs until enough memory
resources become available.
tmnxOspfSpfRunsRestarted
.1.3.6.1.4.1.6527.3.1.3.36.0.22
A tmnxOspfSpfRunsRestarted trap signifies that there are sufficient
memory resources on the system to start running the SPF to completion.
Consequently, OSPF will resume running the SPFs as required.
tmnxOspfOverloadEntered
.1.3.6.1.4.1.6527.3.1.3.36.0.23
A tmnxOspfOverloadEntered trap is sent out when OSPF enters the
overload state. tmnxOspfLastOverloadEnterCode holds the condition
which caused OSPF to get into overload
tmnxOspfOverloadExited
.1.3.6.1.4.1.6527.3.1.3.36.0.24
A tmnxOspfOverloadExited trap is sent out when OSPF exits the overload
state. tmnxOspfLastOverloadExitCode holds the condition which caused
OSPF to get out of overload
tmnxOspfAsOriginateLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.25
A tmnxOspfAsOriginateLsa notification is generated when a new
LSA has been originated by this router. This notification should
not be invoked for simple refreshes of LSAs (which happens every
30 minutes), but instead will only be invoked when an LSA is
(re)originated due to a topology change. Additionally, this
notification does not include LSAs that are being flushed because
they have reached 'MaxAge'.
tmnxOspfAsMaxAgeLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.26
A tmnxOspfAsMaxAgeLsa notification is generated when one of the
autonomous system scope LSAs in the router's link-state database has
aged to 'MaxAge'.
tmnxOspfLinkOriginateLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.27
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgLinkOriginateLsa.
tmnxOspfLinkMaxAgeLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.28
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgLinkMaxAgeLsa.
tmnxOspfLdpSyncTimerStarted
.1.3.6.1.4.1.6527.3.1.3.36.0.29
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgLdpSyncTimerStarted.
tmnxOspfVirtNbrStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.3
A tmnxOspfVirtNbrStateChange notification is generated when there has
been a change in the state of an OSPF virtual neighbor. This
notification should be generated when the neighbor state regresses
(e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a
terminal state (e.g., Full).
tmnxOspfLdpSyncExit
.1.3.6.1.4.1.6527.3.1.3.36.0.30
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgLdpSyncExit.
tmnxOspfShamIfStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.31
[CAUSE] A tmnxOspfShamIfStateChange notification is generated when
there has been a change in the state of an OSPF sham link.
This notification should be generated when the interface state
regresses (e.g., goes from Point-to-Point to Down) or progresses to a
terminal state (i.e., Point-to-Point). [EFFECT] The state of an OSPF
sham link changed. [RECOVERY] Investigate why the state changed if it
was not intentional.
tmnxOspfShamNbrStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.32
[CAUSE] A tmnxOspfShamNbrStateChange notification is generated when
there has been a change in the state of an OSPF sham link neighbor.
This notification should be generated when the neighbor state
regresses (e.g., goes from Attempt or Full to 1-Way or Down) or
progresses to a terminal state (e.g., Full). [EFFECT] There has been a
change in the state of an OSPF sham link neighbor. [RECOVERY] N/A
tmnxOspfShamIfConfigError
.1.3.6.1.4.1.6527.3.1.3.36.0.33
[CAUSE] A tmnxOspfShamIfConfigError notification is generated when a
packet has been received on a sham link from a router whose
configuration parameters conflict with this router's configuration
parameters. Note that the event 'optionMismatch' should cause a
notification only if it prevents an adjacency from forming.
[EFFECT] No OSPF adjacency is formed.
[RECOVERY] Correct conflicting OSPF configuration parameters.
tmnxOspfShamIfAuthFailure
.1.3.6.1.4.1.6527.3.1.3.36.0.34
[CAUSE] A tmnxOspfShamIfAuthFailure notification is generated when a
packet has been received on a sham link from a router whose
authentication key or authentication type conflicts with this router's
authentication key or authentication type. [EFFECT] The packet is
discarded. [RECOVERY] Correct authentication configuration in this
router or in the other router.
tmnxOspfShamIfRxBadPacket
.1.3.6.1.4.1.6527.3.1.3.36.0.35
[CAUSE] A tmnxOspfShamIfRxBadPacket notification is generated when an
OSPF packet that cannot be parsed has been received on a sham link.
[EFFECT] The OSPF packet is dropped. [RECOVERY] Resolve root cause why
packet could not be parsed by OSPF. The necessary action depends on
tmnxOspfBadPacketErrType.
tmnxOspfShamIfTxRetransmit
.1.3.6.1.4.1.6527.3.1.3.36.0.36
[CAUSE] A tmnxOspfShamIfTxRetransmit notification is generated when an
OSPF packet has been retransmitted on a sham link. [EFFECT] The OSPF
packet is retransmitted on a sham link. [RECOVERY] N/A
tmnxOspfShamNbrRestartHlprStsChg
.1.3.6.1.4.1.6527.3.1.3.36.0.37
[CAUSE] An tmnxOspfShamNbrRestartHlprStsChg notification is
generated when there has been a change in the graceful restart
helper state for the sham link neighbor. This notification should
be generated when the sham link neighbor restart helper status
transitions for a sham link neighbor.
[EFFECT] Notifies a change in the graceful restart helper state for
the sham link neighbor.
[RECOVERY] N/A
tmnxOspfFailureDisabled
.1.3.6.1.4.1.6527.3.1.3.36.0.38
[CAUSE] A tmnxOspfFailureDisabled notification is generated when OSPF
is operationally brought down due to an operational problem. Reason
for the failure is indicated by tmnxOspfFailureReasonCode. [EFFECT]
OSPF is going in shutdown. [RECOVERY] After 30 seconds, OSPF will
autonomously start up. If the operational problem is still there then
it will shutdown again.
tmnxOspfExportLimitReached
.1.3.6.1.4.1.6527.3.1.3.36.0.39
A tmnxOspfExportLimitReached notification is generated when the
configured value of exported routes, tmnxOspfExportLimit is reached.
Additional routes would not be exported into OSPF or OSPF3 from the
route table.
tmnxOspfIfConfigError
.1.3.6.1.4.1.6527.3.1.3.36.0.4
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgIfConfigError.
tmnxOspfExportLimitWarning
.1.3.6.1.4.1.6527.3.1.3.36.0.40
A tmnxOspfExportLimitWarning notification is generated when the number
of exported routes is equal to the configured percent,
tmnxOspfExportLimitLogPercent of the export limit,
tmnxOspfExportLimit. Additional routes will continue to be exported
into OSPF or OSPF3 from the route table till the export limit is
reached.
tmnxOspfRoutesExpLmtDropped
.1.3.6.1.4.1.6527.3.1.3.36.0.41
A tmnxOspfRoutesExpLmtDropped notification is generated when the
number of exported routes drops below the export limit,
tmnxOspfExportLimit.
tmnxOspfNgNbrStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.42
A tmnxOspfNgNbrStateChange notification is generated when there has
been a change in the state of a non-virtual OSPF neighbor. This
notification should be generated when the neighbor state regresses
(e.g., goes from Attempt or Full to 1-Way or Down) or progresses
to a terminal state (e.g., 2-Way or Full). When a neighbor
transitions from or to Full on non-broadcast multi-access and
broadcast networks, the notification should be generated by the
designated router. A designated router transitioning to Down will
be noted by the tmnxOspfNgIfStateChange notification.
tmnxOspfNgIfConfigError
.1.3.6.1.4.1.6527.3.1.3.36.0.43
A tmnxOspfNgIfConfigError notification is generated when a packet has
been received on a non-virtual interface from a router whose
configuration parameters conflict with this router's configuration
parameters. Note that the event 'optionMismatch' should cause a
notification only if it prevents an adjacency from forming.
tmnxOspfNgIfAuthFailure
.1.3.6.1.4.1.6527.3.1.3.36.0.44
A tmnxOspfNgIfAuthFailure notification is generated when a packet has
been received on a non-virtual interface from a router whose
authentication key or authentication type conflicts with this router's
authentication key or authentication type.
tmnxOspfNgIfRxBadPacket
.1.3.6.1.4.1.6527.3.1.3.36.0.45
A tmnxOspfNgIfRxBadPacket notification is generated when an OSPF
packet that cannot be parsed has been received on a non-virtual
interface.
tmnxOspfNgIfTxRetransmit
.1.3.6.1.4.1.6527.3.1.3.36.0.46
A tmnxOspfNgIfTxRetransmit notification is generated when an OSPF
packet has been retransmitted on a non-virtual interface.
tmnxOspfNgIfStateChange
.1.3.6.1.4.1.6527.3.1.3.36.0.47
A tmnxOspfNgIfStateChange notification is generated when there
has been a change in the state of a non-virtual OSPF interface.
This notification should be generated when the interface state
regresses (e.g., goes from Dr to Down) or progresses to a terminal
state (i.e., Point-to-Point, DR Other, Dr, or Backup).
tmnxOspfNgNbrRestartHlprStsChg
.1.3.6.1.4.1.6527.3.1.3.36.0.48
A tmnxOspfNgNbrRestartHlprStsChg notification is generated
when there has been a change in the graceful restart helper state
for the neighbor. This notification should be generated when the
neighbor restart helper status transitions for a neighbor.
tmnxOspfNgLinkOriginateLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.49
A tmnxOspfNgLinkOriginateLsa notification is generated when a new
LSA has been originated by this router. This notification should
not be invoked for simple refreshes of LSAs (which happens every
30 minutes), but instead will only be invoked when an LSA is
(re)originated due to a topology change. Additionally, this
notification does not include LSAs that are being flushed because
they have reached 'MaxAge'.
tmnxOspfVirtIfConfigError
.1.3.6.1.4.1.6527.3.1.3.36.0.5
A tmnxOspfVirtIfConfigError notification is generated when a
packet has been received on a virtual interface from a router whose
configuration parameters conflict with this router's configuration
parameters. Note that the event 'optionMismatch' should cause a
notification only if it prevents an adjacency from forming.
tmnxOspfNgLinkMaxAgeLsa
.1.3.6.1.4.1.6527.3.1.3.36.0.50
A tmnxOspfNgLinkMaxAgeLsa notification is generated when one of the
LSAs in the router's link-state database has aged to 'MaxAge'.
tmnxOspfNgLdpSyncTimerStarted
.1.3.6.1.4.1.6527.3.1.3.36.0.51
A notification sent when the tmnxOspfNgIfLdpSyncTimerState is started.
The timer is started from the time the LDP session to the neighbor is
up over the interface. This is to allow for the label FEC bindings to
be exchanged.
tmnxOspfNgLdpSyncExit
.1.3.6.1.4.1.6527.3.1.3.36.0.52
[CAUSE] When IGP-LDP synchronization is configured on an interface
then the interface is initially announced with maximum metric in the
router LSA. This notification is sent when IGP-LDP synchronization
finishes, that is when tmnxOspfNgIfLdpSyncTimerState changes to a
state higher than timerActive. [EFFECT] The IGP link metric is
restored to normal level. [RECOVERY] N/A
tmnxOspfSrSidError
.1.3.6.1.4.1.6527.3.1.3.36.0.53
[CAUSE] This notification is generated when OSPF 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.
tmnxOspfSrSidNotInLabelRange
.1.3.6.1.4.1.6527.3.1.3.36.0.54
[CAUSE] This notification is generated when OSPF 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.
tmnxOspfOverloadWarning
.1.3.6.1.4.1.6527.3.1.3.36.0.55
A tmnxOspfOverloadWarning trap is sent out when OSPF reaches
tmnxOspfAdvRtrLsaLimitWarning percent or tmnxOspfAdvRtrLsaLimit.
tmnxOspfLastOverloadEnterCode holds the condition which caused OSPF to
approach the limit.
tmnxOspfRejectedAdjacencySid
.1.3.6.1.4.1.6527.3.1.3.36.0.56
[CAUSE] The tmnxOspfRejectedAdjacencySid notification is sent when we
do not establish an adjacency SID or adjacency PGID 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. We should not send a second notification about
adjacency PGID allocation failure for the same adjacency.
[EFFECT] No effect.
[RECOVERY] Whenever an ADJ-SID is released, the released ADJ-SID can
be reused by any other adjacency which is waiting to receive an
ADJ-SID. Whenever a PGID is released, the released PGID can be reused
by any other adjacency which is waiting to receive a PGID.
tmnxOspfAdjBfdSessionSetupFail
.1.3.6.1.4.1.6527.3.1.3.36.0.57
[CAUSE] The tmnxOspfAdjBfdSessionSetupFail notification is sent when
BFD session setup fails.
[EFFECT] The system can not setup the BFD session.
[RECOVERY] Depending on the tmnxOspfBfdSessSetupFailReason, recovery
can be possible. Check the BFD configuration to recover.
tmnxOspfSrgbBadLabelRange
.1.3.6.1.4.1.6527.3.1.3.36.0.58
[CAUSE] The tmnxOspfSrgbBadLabelRange notification is sent when OSPF
receives a bad SRGB label range from a router (e.g. overlapping with
another label range.
[EFFECT] The configured Segment Routing tunnels will be wrong.
[RECOVERY] Change the label range to recover.
tmnxOspfRejectedAdjacencySet
.1.3.6.1.4.1.6527.3.1.3.36.0.59
[CAUSE] The tmnxOspfRejectedAdjacencySet 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.
tmnxOspfIfAuthFailure
.1.3.6.1.4.1.6527.3.1.3.36.0.6
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgIfAuthFailure.
tmnxOspfSidStatsIndexAlloc
.1.3.6.1.4.1.6527.3.1.3.36.0.60
[CAUSE] The tmnxOspfSidStatsIndexAlloc 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.
tmnxOspfDynHostnameDuplicate
.1.3.6.1.4.1.6527.3.1.3.36.0.61
[CAUSE] The tmnxOspfDynHostnameDuplicate notification is sent when
another system advertises the same hostname as the local router.
[EFFECT] No effect.
[RECOVERY] No recovery is necessary.
tmnxOspfDynHostnameInconsistent
.1.3.6.1.4.1.6527.3.1.3.36.0.62
[CAUSE] The tmnxOspfDynHostnameInconsistent notification is sent when
there are inconsistencies for and advertised hostname.
[EFFECT] No effect.
[RECOVERY] No recovery is necessary.
tmnxOspfVirtIfAuthFailure
.1.3.6.1.4.1.6527.3.1.3.36.0.7
A tmnxOspfVirtIfAuthFailure notification is generated when a packet
has been received on a virtual interface from a router whose
authentication key or authentication type conflicts with this router's
authentication key or authentication type.
tmnxOspfIfRxBadPacket
.1.3.6.1.4.1.6527.3.1.3.36.0.8
This notification is obsoleted in release 9.0. It is replaced with
tmnxOspfNgIfRxBadPacket.
tmnxOspfVirtIfRxBadPacket
.1.3.6.1.4.1.6527.3.1.3.36.0.9
A tmnxOspfVirtIfRxBadPacket notification is generated when an OSPF
packet that cannot be parsed has been received on a virtual interface.
TmnxOspfAreaIdTc
timetraOspfNgMIBModule 
tmnxOspfGeneralEntries 
tmnxOspfLinkLsdbTable 
tmnxOspfLinkLsdbEntry 
tmnxOspfLinkLsdbIfIndex 
tmnxOspfVirtIfStateChange