Monitor and troubleshoot
Documents under this category provide information about monitoring the 7705 SAR routers and diagnosing and troubleshooting router issues.
- OAM Guide
  This guide describes how to use the Operations, Administration and Management (OAM) and diagnostic tools provided by the 7705 SAR, including how to configure mirroring.
- Log Events Guide
  This guide provides information about the log events for the 7705 SAR.

OSPF

tmnxOspfAdjBfdSessionSetupFail

Table 1. tmnxOspfAdjBfdSessionSetupFail properties
Property name	Value
Application name	OSPF
Event ID	2057
Event name	tmnxOspfAdjBfdSessionSetupFail
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.57
Default severity	warning
Message format string	BFD session setup failed with reason $tmnxOspfBfdSessSetupFailReason$ for Router $tmnxOspfRouterId$
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.

tmnxOspfAreaMaxAgeLsa

Table 2. tmnxOspfAreaMaxAgeLsa properties
Property name	Value
Application name	OSPF
Event ID	2013
Event name	tmnxOspfAreaMaxAgeLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.13
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Max aged LSA $ospfLsdbLsid$ type $ospfLsdbType$ area $ospfLsdbAreaId$ advertising router $ospfLsdbRtrId$
Cause	One of the LSA in the router's link-state database has reached its maximum age.
Effect	N/A
Recovery	N/A

tmnxOspfAreaOriginateLsa

Table 3. tmnxOspfAreaOriginateLsa properties
Property name	Value
Application name	OSPF
Event ID	2012
Event name	tmnxOspfAreaOriginateLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.12
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Originated LSA $ospfLsdbLsid$ type $ospfLsdbType$ area $ospfLsdbAreaId$ advertising router $ospfLsdbRtrId$
Cause	A new LSA has been originated by this router. This event is not generated for simple refreshes of LSAs (which happens every 30 minutes), but instead is generated when an LSA is (re)originated due to a topology change. Additionally, this event does not include LSAs that are being flushed because they have reached their maximum age.
Effect	N/A
Recovery	N/A

tmnxOspfAsMaxAgeLsa

Table 4. tmnxOspfAsMaxAgeLsa properties
Property name	Value
Application name	OSPF
Event ID	2026
Event name	tmnxOspfAsMaxAgeLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.26
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Max aged LSA $ospfLsdbLsid$ type $ospfLsdbType$ advertising router $ospfLsdbRtrId$
Cause	One of the LSAs in the router's link-state database has reached its maximum age limit.
Effect	N/A
Recovery	N/A

tmnxOspfAsOriginateLsa

Table 5. tmnxOspfAsOriginateLsa properties
Property name	Value
Application name	OSPF
Event ID	2025
Event name	tmnxOspfAsOriginateLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.25
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Originated LSA $ospfLsdbLsid$ type $ospfLsdbType$ advertising router $ospfLsdbRtrId$
Cause	A new LSA has been originated by this router. This trap is not generated for simple refreshes of LSAs (which happens every 30 minutes), but instead will only be generated when an LSA is (re)originated due to a topology change. Additionally, this trap does not include LSAs that are being flushed because they have reached their maximum age limit.
Effect	N/A
Recovery	N/A

tmnxOspfExportLimitReached

Table 6. tmnxOspfExportLimitReached properties
Property name	Value
Application name	OSPF
Event ID	2039
Event name	tmnxOspfExportLimitReached
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.39
Default severity	major
Message format string	OSPF has reached the export-limit $tmnxOspfExportLimit$, additional routes will not be exported into OSPF
Cause	OSPF has exported maximum allowed export routes. It will not export any more routes unless the export policy and export limit is changed.
Effect	OSPF will not export any more routes.
Recovery	Change OSPF export policy.

tmnxOspfExportLimitWarning

Table 7. tmnxOspfExportLimitWarning properties
Property name	Value
Application name	OSPF
Event ID	2040
Event name	tmnxOspfExportLimitWarning
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.40
Default severity	warning
Message format string	OSPF has reached $tmnxOspfExportLimitLogPercent$ percent of the export limit $tmnxOspfExportLimit$
Cause	The number of routes exported by OSPF has reached the warning percent of the configured export limit. OSPF will continue to export routes till the limit is reached.
Effect	N/A
Recovery	N/A

tmnxOspfFailureDisabled

Table 8. tmnxOspfFailureDisabled properties
Property name	Value
Application name	OSPF
Event ID	2038
Event name	tmnxOspfFailureDisabled
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.38
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: OSPF disabled. Reason: $tmnxOspfFailureReasonCode$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfLsdbApproachingOverflow

Table 9. tmnxOspfLsdbApproachingOverflow properties
Property name	Value
Application name	OSPF
Event ID	2015
Event name	tmnxOspfLsdbApproachingOverflow
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.15
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Number of external LSAs has exceed 90% of the configured limit ( $tmnxOspfExtLsdbLimit$)
Cause	The number of external LSAs in the router's link-state database has exceeded ninety percent of the configured limit.
Effect	N/A
Recovery	N/A

tmnxOspfLsdbOverflow

Table 10. tmnxOspfLsdbOverflow properties
Property name	Value
Application name	OSPF
Event ID	2014
Event name	tmnxOspfLsdbOverflow
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.14
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Number of external LSAs has exceeded the configured limit ( $tmnxOspfExtLsdbLimit$)
Cause	The number of external LSAs in the router's link-state database has exceeded the configured limit.
Effect	N/A
Recovery	N/A

tmnxOspfNgIfAuthFailure

Table 11. tmnxOspfNgIfAuthFailure properties
Property name	Value
Application name	OSPF
Event ID	2044
Event name	tmnxOspfNgIfAuthFailure
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.44
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Packet failed $tmnxOspfConfigErrorType$ authentication on interface $ospfIfIpAddress$ from $tmnxOspfPacketSrcAddress$ in $tmnxOspfPacketType$
Cause	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.
Effect	N/A
Recovery	N/A

tmnxOspfNgIfConfigError

Table 12. tmnxOspfNgIfConfigError properties
Property name	Value
Application name	OSPF
Event ID	2043
Event name	tmnxOspfNgIfConfigError
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.43
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Conflicting configuration $tmnxOspfConfigErrorType$ on interface $ospfIfIpAddress$ from $tmnxOspfPacketSrcAddress$ in $tmnxOspfPacketType$
Cause	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 trap only if it prevents an adjacency from forming.
Effect	N/A
Recovery	N/A

tmnxOspfNgIfRxBadPacket

Table 13. tmnxOspfNgIfRxBadPacket properties
Property name	Value
Application name	OSPF
Event ID	2045
Event name	tmnxOspfNgIfRxBadPacket
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.45
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Bad packet, $tmnxOspfBadPacketErrType$, received on interface $ospfIfIpAddress$ from $tmnxOspfPacketSrcAddress$ in $tmnxOspfPacketType$
Cause	An OSPF packet has been received on a non-virtual interface that cannot be parsed.
Effect	N/A
Recovery	N/A

tmnxOspfNgIfStateChange

Table 14. tmnxOspfNgIfStateChange properties
Property name	Value
Application name	OSPF
Event ID	2047
Event name	tmnxOspfNgIfStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.47
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Interface $tmnxOspfIfIpName$ state changed to $tmnxOspfNgIfState$ (event $tmnxOspfIfEvent$)
Cause	There has been a change in the state of a non-virtual OSPF interface. This event is 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).
Effect	N/A
Recovery	N/A

tmnxOspfNgIfTxRetransmit

Table 15. tmnxOspfNgIfTxRetransmit properties
Property name	Value
Application name	OSPF
Event ID	2046
Event name	tmnxOspfNgIfTxRetransmit
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.46
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Retransmit to neighbor $ospfNbrRtrId$ on interface $ospfIfIpAddress$
Cause	An OSPF packet has been retransmitted on a non-virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
Effect	N/A
Recovery	N/A

tmnxOspfNgLdpSyncExit

Table 16. tmnxOspfNgLdpSyncExit properties
Property name	Value
Application name	OSPF
Event ID	2052
Event name	tmnxOspfNgLdpSyncExit
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.52
Default severity	warning
Message format string	IGP-LDP synchronization has stopped for interface $vRtrIfIndex$ because $strReason$.
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfNgLdpSyncTimerStarted

Table 17. tmnxOspfNgLdpSyncTimerStarted properties
Property name	Value
Application name	OSPF
Event ID	2051
Event name	tmnxOspfNgLdpSyncTimerStarted
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.51
Default severity	warning
Message format string	IGP-LDP synchronization timer has started for interface $vRtrIfIndex$.
Cause	The OSPF interface LDP synchronization timer state has started. The timer was started from the time the LDP session to the neighbor became up over the interface. This is to allow for the label FEC bindings to be exchanged.
Effect	N/A
Recovery	N/A

tmnxOspfNgLinkMaxAgeLsa

Table 18. tmnxOspfNgLinkMaxAgeLsa properties
Property name	Value
Application name	OSPF
Event ID	2050
Event name	tmnxOspfNgLinkMaxAgeLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.50
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Max aged LSA $ospfLsdbLsid$ type $ospfLsdbType$ ifIndex $ospfLinkIfIdx$ ifInstId $ospfLinkIfInstId$ advertising router $ospfLsdbRtrId$
Cause	One of the LSAs in the router's link-state database has reached its maximum age limit.
Effect	N/A
Recovery	N/A

tmnxOspfNgLinkOriginateLsa

Table 19. tmnxOspfNgLinkOriginateLsa properties
Property name	Value
Application name	OSPF
Event ID	2049
Event name	tmnxOspfNgLinkOriginateLsa
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.49
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Originated LSA $ospfLsdbLsid$ type $ospfLsdbType$ ifIndex $ospfLinkIfIdx$ ifInstId $ospfLinkIfInstId$ advertising router $ospfLsdbRtrId$
Cause	A new LSA has been originated by this router. This event is not generated for simple refreshes of LSAs (which happens every 30 minutes), but instead is only generated when an LSA is (re)originated due to a topology change. Additionally, this event does not include LSAs that are being flushed because they have reached their maximum age limit.
Effect	N/A
Recovery	N/A

tmnxOspfNgNbrRestartHlprStsChg

Table 20. tmnxOspfNgNbrRestartHlprStsChg properties
Property name	Value
Application name	OSPF
Event ID	2048
Event name	tmnxOspfNgNbrRestartHlprStsChg
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.48
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Helper status for neighbor $ospfNbrIpAddr$ router $ospfNbrRtrId$ changed to $tmnxOspfNgNbrRestartHelperStatus$ (Helper Age $tmnxOspfNgNbrRestartHelperAge$ Exit Reason $tmnxOspfNgNbrRestartHelperExitRc$)
Cause	There has been a change in the graceful restart helper state for the neighbor. This event is generated when the neighbor restart helper status transitions for a neighbor.
Effect	N/A
Recovery	N/A

tmnxOspfNgNbrStateChange

Table 21. tmnxOspfNgNbrStateChange properties
Property name	Value
Application name	OSPF
Event ID	2042
Event name	tmnxOspfNgNbrStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.42
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Neighbor $ospfNbrRtrId$ on $ospfNbrIpAddr$ router state changed to $tmnxOspfNgNbrState$ (event $ospfNbrEvent$)
Cause	There has been a change in the state of a non-virtual OSPF neighbor. This event is 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 event is generated by the designated router. A designated router transitioning to Down is indicated by the value of ospfNgIfStateChange.
Effect	N/A
Recovery	N/A

tmnxOspfNssaTranslatorStatusChg

Table 22. tmnxOspfNssaTranslatorStatusChg properties
Property name	Value
Application name	OSPF
Event ID	2017
Event name	tmnxOspfNssaTranslatorStatusChg
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.17
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: NSSA translator state in area $ospfAreaId$ changed to $tmnxOspfAreaNssaTranslatorState$
Cause	There has been a change in the router's ability to translate OSPF type-7 LSAs into OSPF type-5 LSAs. This event is generated when the Translator Status transitions from or to any defined status on a per area basis.
Effect	N/A
Recovery	N/A

tmnxOspfOverloadEntered

Table 23. tmnxOspfOverloadEntered properties
Property name	Value
Application name	OSPF
Event ID	2023
Event name	tmnxOspfOverloadEntered
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.23
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Overload entered (event $tmnxOspfLastOverloadEnterCode$) $tmnxOspfNotifyDescription$
Cause	OSPF entered the overload state. vRtrOspfLastOverloadEnterCode holds the condition which caused OSPF to get into overload.
Effect	N/A
Recovery	N/A

tmnxOspfOverloadExited

Table 24. tmnxOspfOverloadExited properties
Property name	Value
Application name	OSPF
Event ID	2024
Event name	tmnxOspfOverloadExited
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.24
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Overload exited (event $tmnxOspfLastOverloadExitCode$)
Cause	OSPF entered the overload state. vRtrOspfLastOverloadExitCode holds the condition which caused OSPF to get out of overload.
Effect	N/A
Recovery	N/A

tmnxOspfOverloadWarning

Table 25. tmnxOspfOverloadWarning properties
Property name	Value
Application name	OSPF
Event ID	2055
Event name	tmnxOspfOverloadWarning
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.55
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Reached 80 percent overload limit (event $tmnxOspfLastOverloadEnterCode$) $tmnxOspfNotifyDescription$
Cause	A tmnxOspfOverloadWarning trap is sent out when OSPF reaches 80 percent of overload limit. tmnxOspfLastOverloadEnterCode holds the condition which caused OSPF to approach this limit.
Effect	N/A
Recovery	N/A

tmnxOspfRejectedAdjacencySid

Table 26. tmnxOspfRejectedAdjacencySid properties
Property name	Value
Application name	OSPF
Event ID	2056
Event name	tmnxOspfRejectedAdjacencySid
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.56
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Rejected adjacency SID $tmnxOspfNotifyDescription$
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.

tmnxOspfRestartStatusChange

Table 27. tmnxOspfRestartStatusChange properties
Property name	Value
Application name	OSPF
Event ID	2018
Event name	tmnxOspfRestartStatusChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.18
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Restart status changed to $tmnxOspfRestartStatus$ (Restart Interval $tmnxOspfRestartInterval$ Exit Reason $tmnxOspfRestartExitRc$)
Cause	There has been a change in the graceful restart state for the router. This event is generated when the router restart status changes.
Effect	N/A
Recovery	N/A

tmnxOspfRoutesExpLmtDropped

Table 28. tmnxOspfRoutesExpLmtDropped properties
Property name	Value
Application name	OSPF
Event ID	2041
Event name	tmnxOspfRoutesExpLmtDropped
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.41
Default severity	warning
Message format string	The number of redistributed routes into OSPF has dropped below the export limit $tmnxOspfExportLimit$
Cause	Number of exported routes is dropped below the configured export limit.
Effect	N/A
Recovery	N/A

tmnxOspfShamIfAuthFailure

Table 29. tmnxOspfShamIfAuthFailure properties
Property name	Value
Application name	OSPF
Event ID	2034
Event name	tmnxOspfShamIfAuthFailure
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.34
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Packet failed $tmnxOspfConfigErrorType$ authentication from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamIfConfigError

Table 30. tmnxOspfShamIfConfigError properties
Property name	Value
Application name	OSPF
Event ID	2033
Event name	tmnxOspfShamIfConfigError
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.33
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Conflicting configuration $tmnxOspfConfigErrorType$ from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamIfRxBadPacket

Table 31. tmnxOspfShamIfRxBadPacket properties
Property name	Value
Application name	OSPF
Event ID	2035
Event name	tmnxOspfShamIfRxBadPacket
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.35
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Bad packet, $tmnxOspfBadPacketErrType$, received from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamIfStateChange

Table 32. tmnxOspfShamIfStateChange properties
Property name	Value
Application name	OSPF
Event ID	2031
Event name	tmnxOspfShamIfStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.31
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$:State of sham-link interface $tmnxOspfShamIfIndex$ with neighbor $tmnxOspfShamIfRemoteNbrAddress$ changed to $tmnxOspfShamIfState$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamIfTxRetransmit

Table 33. tmnxOspfShamIfTxRetransmit properties
Property name	Value
Application name	OSPF
Event ID	2036
Event name	tmnxOspfShamIfTxRetransmit
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.36
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Retransmit to sham-link interface $tmnxOspfShamNbrIfIndex$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamNbrRestartHlprStsChg

Table 34. tmnxOspfShamNbrRestartHlprStsChg properties
Property name	Value
Application name	OSPF
Event ID	2037
Event name	tmnxOspfShamNbrRestartHlprStsChg
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.37
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Helper status for sham-link neighbor $tmnxOspfShamNbrRtrId$ changed to $tmnxOspfShamNbrRestartHelperStatus$ (Helper Age $tmnxOspfShamNbrRestartHelperAge$ Exit Reason $tmnxOspfShamNbrRestartHelperExitRc$)
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfShamNbrStateChange

Table 35. tmnxOspfShamNbrStateChange properties
Property name	Value
Application name	OSPF
Event ID	2032
Event name	tmnxOspfShamNbrStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.32
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: State of sham-link neighbor $tmnxOspfShamNbrRtrId$ changed to $tmnxOspfShamNbrState$
Cause	N/A
Effect	N/A
Recovery	N/A

tmnxOspfSpfRunsRestarted

Table 36. tmnxOspfSpfRunsRestarted properties
Property name	Value
Application name	OSPF
Event ID	2022
Event name	tmnxOspfSpfRunsRestarted
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.22
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: SPF runs resumed - memory resources available
Cause	There are sufficient memory resources on the system to start running the SPF to completion.
Effect	OSPF will resume running the SPFs as required.
Recovery	N/A

tmnxOspfSpfRunsStopped

Table 37. tmnxOspfSpfRunsStopped properties
Property name	Value
Application name	OSPF
Event ID	2021
Event name	tmnxOspfSpfRunsStopped
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.21
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: SPF runs stopped - insufficient memory resources
Cause	There are insufficient memory resources on the system to run the SPF to completion.
Effect	OSPF stops running SPFs until enough memory resources become available.
Recovery	Free some memory resources.

tmnxOspfSrgbBadLabelRange

Table 38. tmnxOspfSrgbBadLabelRange properties
Property name	Value
Application name	OSPF
Event ID	2058
Event name	tmnxOspfSrgbBadLabelRange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.58
Default severity	warning
Message format string	Bad SRGB label range for advertising router: $tmnxOspfNotifSrgbAdvRtrID$, startLabel:$tmnxOspfNotifSrgbRangeStartLbl$, maxIdx: $tmnxOspfNotifSrgbRangeMaxIdx$, area:$tmnxOspfNotifSrgbAreaId$
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.

tmnxOspfSrSidError

Table 39. tmnxOspfSrSidError properties
Property name	Value
Application name	OSPF
Event ID	2053
Event name	tmnxOspfSrSidError
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.53
Default severity	minor
Message format string	Received SID label already in use for other prefix, reason: $tmnxOspfNotifyDescription$
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

Table 40. tmnxOspfSrSidNotInLabelRange properties
Property name	Value
Application name	OSPF
Event ID	2054
Event name	tmnxOspfSrSidNotInLabelRange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.54
Default severity	minor
Message format string	Receivd SID not in range $tmnxOspfNotifPfxSidRangeStartLbl$(+$tmnxOspfNotifPfxSidRangeMaxIdx$)of NH-router $tmnxOspfNotifPfxNhAdvRtr$
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.

tmnxOspfVirtIfAuthFailure

Table 41. tmnxOspfVirtIfAuthFailure properties
Property name	Value
Application name	OSPF
Event ID	2007
Event name	tmnxOspfVirtIfAuthFailure
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.7
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Packet failed $tmnxOspfConfigErrorType$ authentication from virtual neighbor $ospfVirtIfNeighbor$ area $ospfVirtIfAreaId$ in $tmnxOspfPacketType$
Cause	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.
Effect	N/A
Recovery	N/A

tmnxOspfVirtIfConfigError

Table 42. tmnxOspfVirtIfConfigError properties
Property name	Value
Application name	OSPF
Event ID	2005
Event name	tmnxOspfVirtIfConfigError
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.5
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Conflicting configuration $tmnxOspfConfigErrorType$ from virtual neighbor $ospfVirtIfNeighbor$ area $ospfVirtIfAreaId$ in $tmnxOspfPacketType$
Cause	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 generate an event only if it prevents an adjacency from forming.
Effect	N/A
Recovery	N/A

tmnxOspfVirtIfRxBadPacket

Table 43. tmnxOspfVirtIfRxBadPacket properties
Property name	Value
Application name	OSPF
Event ID	2009
Event name	tmnxOspfVirtIfRxBadPacket
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.9
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Bad packet, $tmnxOspfBadPacketErrType$ received from virtual neighbor $ospfVirtIfNeighbor$ area $ospfVirtIfAreaId$ in $tmnxOspfPacketType$
Cause	An OSPF packet that cannot be parsed has been received on a virtual interface.
Effect	N/A
Recovery	N/A

tmnxOspfVirtIfStateChange

Table 44. tmnxOspfVirtIfStateChange properties
Property name	Value
Application name	OSPF
Event ID	2001
Event name	tmnxOspfVirtIfStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.1
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Virtual interface $ospfVirtIfNeighbor$ in transit-area $ospfVirtIfAreaId$ state changed to $tmnxOspfVirtIfState$ (event $ospfVirtIfEvent$)
Cause	There has been a change in the state of an OSPF virtual interface. This event is 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	N/A
Recovery	N/A

tmnxOspfVirtIfTxRetransmit

Table 45. tmnxOspfVirtIfTxRetransmit properties
Property name	Value
Application name	OSPF
Event ID	2011
Event name	tmnxOspfVirtIfTxRetransmit
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.11
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Retransmit to virtual interface $ospfVirtIfNeighbor$ in transit-area $ospfVirtIfAreaId$
Cause	An OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
Effect	N/A
Recovery	N/A

tmnxOspfVirtNbrRestartHlprStsChg

Table 46. tmnxOspfVirtNbrRestartHlprStsChg properties
Property name	Value
Application name	OSPF
Event ID	2020
Event name	tmnxOspfVirtNbrRestartHlprStsChg
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.20
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Helper status for Virtual neighbor $ospfVirtNbrRtrId$ in transit-area $ospfVirtNbrArea$ changed to $tmnxOspfVirtNbrRestartHelperStatus$ (Helper Age $tmnxOspfVirtNbrRestartHelperAge$ Exit Reason $tmnxOspfVirtNbrRestartHelperExitRc$)
Cause	There has been a change in the graceful restart helper state for the virtual neighbor. This event is generated when the virtual neighbor restart helper status transitions for a virtual neighbor.
Effect	N/A
Recovery	N/A

tmnxOspfVirtNbrStateChange

Table 47. tmnxOspfVirtNbrStateChange properties
Property name	Value
Application name	OSPF
Event ID	2003
Event name	tmnxOspfVirtNbrStateChange
SNMP notification prefix and OID	TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.3
Default severity	warning
Message format string	LCL_RTR_ID $ospfRouterIdIpAddr$: Virtual neighbor $ospfVirtNbrRtrId$ in transit-area $ospfVirtNbrArea$ state changed to $tmnxOspfVirtNbrState$ (event $ospfVirtNbrEvent$)
Cause	There has been a change in the state of an OSPF virtual neighbor. This event is 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	N/A
Recovery	N/A

October 25, 2023