OSPF
tmnxOspfAdjBfdSessionSetupFail
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 |
Source stream |
main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: BFD session setup failed with reason $tmnxOspfBfdSessSetupFailReason$ |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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 |
tmnxOspfDynHostnameDuplicate
Property name | Value |
---|---|
Application name |
OSPF |
Event ID | 2061 |
Event name | tmnxOspfDynHostnameDuplicate |
SNMP notification prefix and OID |
TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.61 |
Default severity |
warning |
Source stream | main |
Message format string | Duplicate advertising of $tmnxOspfHostnameName$ |
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
Property name | Value |
---|---|
Application name | OSPF |
Event ID |
2062 |
Event name | tmnxOspfDynHostnameInconsistent |
SNMP notification prefix and OID | TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.62 |
Default severity | warning |
Source stream |
main |
Message format string | Inconsistent advertising of $tmnxOspfHostnameName$ |
Cause | The tmnxOspfDynHostnameInconsistent notification is sent when there are inconsistencies for and advertised hostname. |
Effect | No effect. |
Recovery |
No recovery is necessary. |
tmnxOspfExportLimitReached
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 |
Source stream |
main |
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
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 |
Source stream |
main |
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
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 |
Source stream | main |
Message format string | LCL_RTR_ID $tmnxOspfRouterId$: OSPF disabled. Reason: $tmnxOspfFailureReasonCode$ |
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. |
tmnxOspfFaOperParticipationDown
Property name | Value |
---|---|
Application name |
OSPF |
Event ID | 2063 |
Event name | tmnxOspfFaOperParticipationDown |
SNMP notification prefix and OID |
TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.63 |
Default severity |
warning |
Source stream | main |
Message format string | The oper-participation of $tmnxOspfFlexAlgoId$ in area $tmnxOspfAreaId$ is operationally down due to $tmnxOspfNotifyDescription$. |
Cause | The tmnxOspfFaOperParticipationDown 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. |
tmnxOspfLsdbApproachingOverflow
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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 |
tmnxOspfNgLdpSyncExit
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 |
Source stream | main |
Message format string | IGP-LDP synchronization has stopped for interface $vRtrIfIndex$ because $strReason$. |
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 |
tmnxOspfNgLdpSyncTimerStarted
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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 |
tmnxOspfNgNbrStrictBfdBlocked
Property name | Value |
---|---|
Application name |
OSPF |
Event ID | 2064 |
Event name | tmnxOspfNgNbrStrictBfdBlocked |
SNMP notification prefix and OID |
TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.64 |
Default severity |
warning |
Source stream | main |
Message format string | BFD strict-mode capable neighbor $tmnxOspfNgNbrRtrId$ is blocked |
Cause | The tmnxOspfNgNbrStrictBfdBlocked notification is sent when, with BFD strict-mode enabled, OSPF has received a Hello packet from a BFD strict-mode capable neighbor but will not list that neighbor in the Hello packet sent on that interface while waiting for BFD session setup completion. This should be an edge-triggered notification. We should not send a second notification about Hellos received from or sent to the same source. |
Effect | No effect. |
Recovery |
No recovery is necessary. |
tmnxOspfNssaTranslatorStatusChg
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 |
Source stream |
main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: Reached 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 |
tmnxOspfRejectedAdjacencySet
Property name | Value |
---|---|
Application name |
OSPF |
Event ID | 2059 |
Event name | tmnxOspfRejectedAdjacencySet |
SNMP notification prefix and OID |
TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.59 |
Default severity |
warning |
Source stream | main |
Message format string | Rejected adjacency set $tmnxOspfNotifyDescription$ |
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. |
tmnxOspfRejectedAdjacencySid
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 |
Source stream | main |
Message format string | LCL_RTR_ID $tmnxOspfRouterId$: $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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: Packet failed $tmnxOspfConfigErrorType$ authentication from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$ |
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. |
tmnxOspfShamIfConfigError
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: Conflicting configuration $tmnxOspfConfigErrorType$ from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$ |
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. |
tmnxOspfShamIfRxBadPacket
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: Bad packet, $tmnxOspfBadPacketErrType$, received from sham-link neighbor $tmnxOspfShamIfRemoteNbrAddress$ in $tmnxOspfPacketType$ |
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. |
tmnxOspfShamIfStateChange
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$:State of sham-link interface $tmnxOspfShamIfIndex$ with neighbor $tmnxOspfShamIfRemoteNbrAddress$ changed to $tmnxOspfShamIfState$ |
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. |
tmnxOspfShamNbrRestartHlprStsChg
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 |
Source stream | main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: Helper status for sham-link neighbor $tmnxOspfShamNbrRtrId$ changed to $tmnxOspfShamNbrRestartHelperStatus$ (Helper Age $tmnxOspfShamNbrRestartHelperAge$ Exit Reason $tmnxOspfShamNbrRestartHelperExitRc$) |
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 |
tmnxOspfShamNbrStateChange
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 |
Source stream |
main |
Message format string | LCL_RTR_ID $ospfRouterIdIpAddr$: State of sham-link neighbor $tmnxOspfShamNbrRtrId$ changed to $tmnxOspfShamNbrState$ |
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 |
tmnxOspfSidStatsIndexAlloc
Property name | Value |
---|---|
Application name | OSPF |
Event ID |
2060 |
Event name | tmnxOspfSidStatsIndexAlloc |
SNMP notification prefix and OID | TIMETRA-OSPF-NG-MIB.tmnxOspfNotifications.60 |
Default severity | warning |
Source stream |
main |
Message format string | Possible messages:
|
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. |
tmnxOspfSpfRunsRestarted
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 |
Source stream |
main |
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
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 |
Source stream |
main |
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
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 |
Source stream | main |
Message format string | LCL_RTR_ID $tmnxOspfRouterId$: Bad SRGB label range from router $tmnxOspfNotifSrgbAdvRtrID$ in area $tmnxOspfNotifSrgbAreaId$: startLabel:$tmnxOspfNotifSrgbRangeStartLbl$ maxIdx: $tmnxOspfNotifSrgbRangeMaxIdx$ will be ignored |
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
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 |
Source stream | main |
Message format string | SID label error: SID $tmnxOspfSrPfxSid$, area $tmnxOspfSrPfxAreaId$, algo $tmnxOspfSrPfxSidAlgorithm$, 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
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 |
Source stream | main |
Message format string | Possible messages:
|
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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
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 |
Source stream | main |
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 |
tmnxOspfVirtNbrRestartHlprStsChg
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 |
Source stream | main |
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
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 |
Source stream | main |
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 |