Home
Monitor and troubleshoot
Documents under this category provide information about monitoring, diagnosing, and troubleshooting router issues.
Log Events Guide
This guide provides information about log events.
ISIS

Monitor and troubleshoot
Documents under this category provide information about monitoring, diagnosing, and troubleshooting router issues.
- Log Events Guide
  This guide provides information about log events.
- OAM and Diagnostics Guide
  This guide describes how to configure features such as service mirroring and Lawful Intercept (LI), and how to use the Operations, Administration, and Maintenance (OAM) and diagnostics tools.
- 7450 and 7750 Troubleshooting Guide
- 7950 Troubleshooting Guide
- Log Events Search Tool
  A searchable HTML list of the SR OS events.

ISIS

tmnxIsisAdjacencyChange

Table 1. tmnxIsisAdjacencyChange properties
Property name	Value
Application name	ISIS
Event ID	2045
Event name	tmnxIsisAdjacencyChange
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.17
Default severity	warning
Message format string	Adjacency status changed to $isisISAdjState$ for interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, LSP-id: $vRtrIsisTrapLSPIDString$
Cause	The tmnxIsisAdjacencyChange notification is sent when an adjacency changes state, entering or leaving state up. The first 6 bytes of the tmnxIsisNotifTrapLSPID are the SystemID of the adjacent IS. The isisISAdjState is the new state of the adjacency.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisAdjBfdSessionSetupFail

Table 2. tmnxIsisAdjBfdSessionSetupFail properties
Property name	Value
Application name	ISIS
Event ID	2062
Event name	tmnxIsisAdjBfdSessionSetupFail
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.34
Default severity	warning
Message format string	BFD session setup failed with reason $tmnxIsisBfdSessSetupFailReason$ for interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, LSP-id: $tmnxIsisNotifTrapLSPIDString$
Cause	The tmnxIsisAdjBfdSessionSetupFail notification is sent when BFD session setup fails. The first 6 bytes of the tmnxIsisNotifTrapLSPID are the SystemID of the adjacent IS.
Effect	The system can not setup the BFD session.
Recovery	Depending on the tmnxIsisBfdSessSetupFailReason, recovery can be possible. Check the BFD configuration to recover.

tmnxIsisAdjRestartStatusChange

Table 3. tmnxIsisAdjRestartStatusChange properties
Property name	Value
Application name	ISIS
Event ID	2047
Event name	tmnxIsisAdjRestartStatusChange
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.19
Default severity	warning
Message format string	Adjacency graceful restart status changed to $tmnxIsisISAdjRestartStatus$ for interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$
Cause	The tmnxIsisAdjRestartStatusChange notification is sent when an adjacency's graceful restart status changes. The tmnxIsisISAdjRestartStatus is the new graceful restart state of the adjacency.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisAreaMismatch

Table 4. tmnxIsisAreaMismatch properties
Property name	Value
Application name	ISIS
Event ID	2040
Event name	tmnxIsisAreaMismatch
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.12
Default severity	warning
Message format string	Area mismatch on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, fragment: $vRtrIsisPDUFragmentString$, LSP size: $tmnxIsisNotifLSPSize$
Cause	The tmnxIsisAreaMismatch notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisAuthFail

Table 5. tmnxIsisAuthFail properties
Property name	Value
Application name	ISIS
Event ID	2038
Event name	tmnxIsisAuthFail
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.10
Default severity	warning
Message format string	Authentication failure on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, fragment: $vRtrIsisPDUFragmentString$
Cause	The tmnxIsisAuthFail notification is sent when we receive a PDU with incorrect 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisAutTypeFail

Table 6. tmnxIsisAutTypeFail properties
Property name	Value
Application name	ISIS
Event ID	2037
Event name	tmnxIsisAutTypeFail
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.9
Default severity	warning
Message format string	Authentication type failure on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, fragment: $vRtrIsisPDUFragmentString$
Cause	The tmnxIsisAutTypeFail notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisCircIdExhausted

Table 7. tmnxIsisCircIdExhausted properties
Property name	Value
Application name	ISIS
Event ID	2046
Event name	tmnxIsisCircIdExhausted
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.18
Default severity	warning
Message format string	Circuit-id space exhausted for level $tmnxIsisNotifSystemLevel$ - interface: $vRtrIfIndex$
Cause	The tmnxIsisCircIdExhausted notification is sent when the specific ISIS level 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.
Effect	In such a case the interface is marked operationally down.
Recovery	When an operationally up interface is deleted, the circid can be reused by any interface which is waiting to receive a unique circid.

tmnxIsisCircMtuTooLow

Table 8. tmnxIsisCircMtuTooLow properties
Property name	Value
Application name	ISIS
Event ID	2064
Event name	tmnxIsisCircMtuTooLow
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.36
Default severity	warning
Message format string	MTU size too low for interface: $vRtrIfIndex$ (level $tmnxIsisNotifSystemLevel$): $tmnxIsisNotifCircMtuSize$ smaller than $tmnxIsisNotifCircMinReqMtuSize$ (min required MTU size to transmit LSP or SNP)
Cause	The tmnxIsisCircMtuTooLow notification is sent when we attempt to a) configure a circuit which cannot propagate an LSP or SNP with max size tmnxIsisLevelLSPBuffSize. b) configure tmnxIsisLevelLSPBuffSize which is bigger than tmnxIsisLevelMaxOperLSPBuffSize. c) configure tmnxIsisSysOrigL1LSPBuffSize or tmnxIsisSysOrigL2LSPBuffSize which is bigger than tmnxIsisLevelMaxOperLSPBuffSize.
Effect	No effect.
Recovery	Increase port-mtu or decrease lsp-mtu.

tmnxIsisCorruptedLSPDetected

Table 9. tmnxIsisCorruptedLSPDetected properties
Property name	Value
Application name	ISIS
Event ID	2031
Event name	tmnxIsisCorruptedLSPDetected
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.3
Default severity	warning
Message format string	Corrupted LSP detected on interface: $vRtrIfIndex$, level: $tmnxIsisNotifSystemLevel$, with LSP-id: $vRtrIsisTrapLSPIDString$.
Cause	The tmnxIsisCorruptedLSPDetected 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.
Effect	LSP is dropped.
Recovery	No recovery is necessary.

tmnxIsisCorruptRemainingLifetime

Table 10. tmnxIsisCorruptRemainingLifetime properties
Property name	Value
Application name	ISIS
Event ID	2066
Event name	tmnxIsisCorruptRemainingLifetime
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.38
Default severity	warning
Message format string	Possible corrupt Remaining Lifetime $tmnxIsisLSPLifetimeRemain$ received on LSP $tmnxIsisLSPIdString$, for level: $tmnxIsisLevel$
Cause	The tmnxIsisCorruptRemainingLifetime notification is sent when an LSP is received with a possible corrupt Remaining Lifetime field. The Remaining Lifetime of a received LSP is considered as possible corrupt based on following algorithm: - The LSP has passed all acceptance tests. - The LSP is newer than the copy in the local LSPDB or no copy present. - The Remaining Lifetime in the received LSP is less than Zero Age Lifetime. - The adjacency to the neighbor from which the LSP is received has been up for a minimum of Zero Age Lifetime.
Effect	It is possible that an LSP is purged prematurely.
Recovery	The ISIS system will try to recover by setting the Remaining Lifetime to the tmnxIsisMinRemainingLspLifetime value.

tmnxIsisDatabaseOverload

Table 11. tmnxIsisDatabaseOverload properties
Property name	Value
Application name	ISIS
Event ID	2029
Event name	tmnxIsisDatabaseOverload
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.1
Default severity	warning
Message format string	Overload (event $tmnxIsisLevelOverloadStatus$, system level: $tmnxIsisNotifSystemLevel$) - Level1State: $isisSysL1State$, Level2State: $isisSysL2State$ $tmnxIsisNotifyDescription$
Cause	The tmnxIsisDatabaseOverload notification is generated when the system enters or leaves the Overload state.
Effect	Database is overloaded.
Recovery	No recovery is necessary unless tmnxIsisNotifyDescription indicates it.

tmnxIsisExportLimitReached

Table 12. tmnxIsisExportLimitReached properties
Property name	Value
Application name	ISIS
Event ID	2050
Event name	tmnxIsisExportLimitReached
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.22
Default severity	major
Message format string	ISIS level $tmnxIsisNotifSystemLevel$ has reached the export-limit $tmnxIsisExportLimit$, additional routes will not be exported into this ISIS level
Cause	The tmnxIsisExportLimitReached notification is sent when the total number of exported routes for the level is equal to the configured limit for exported routes, tmnxIsisExportLimit.
Effect	Additional routes would not be exported into this ISIS level from the route table.
Recovery	Change ISIS export policy.

tmnxIsisExportLimitWarning

Table 13. tmnxIsisExportLimitWarning properties
Property name	Value
Application name	ISIS
Event ID	2051
Event name	tmnxIsisExportLimitWarning
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.23
Default severity	warning
Message format string	ISIS level $tmnxIsisNotifSystemLevel$ has reached $tmnxIsisExportLimitLogPercent$ percent of the export limit $tmnxIsisExportLimit$
Cause	The tmnxIsisExportLimitWarning notification is sent when the total number of exported routes or the level is equal to the configured percent, tmnxIsisExportLimitLogPercent of the export limit, tmnxIsisExportLimit. Additional routes will continue to be exported into this ISIS level from the route table till the export limit is reached.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisFailureDisabled

Table 14. tmnxIsisFailureDisabled properties
Property name	Value
Application name	ISIS
Event ID	2056
Event name	tmnxIsisFailureDisabled
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.28
Default severity	minor
Message format string	ISIS disabled. Reason : $tmnxIsisFailureReasonCode$
Cause	A tmnxIsisFailureDisabled notification is generated when ISIS is operationally brought down. Reason for the failure is indicated by tmnxIsisFailureReasonCode.
Effect	ISIS is now operationally down.
Recovery	ISIS will auto restart.

tmnxIsisFaOperParticipationDown

Table 15. tmnxIsisFaOperParticipationDown properties
Property name	Value
Application name	ISIS
Event ID	2068
Event name	tmnxIsisFaOperParticipationDown
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.40
Default severity	warning
Message format string	The oper-participation of $tmnxIsisFlexAlgoId$ in level $tmnxIsisNotifSystemLevel$ is operationally down due to $tmnxIsisNotifyDescription$.
Cause	The tmnxIsisFaOperParticipationDown 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.

tmnxIsisIDLenMismatch

Table 16. tmnxIsisIDLenMismatch properties
Property name	Value
Application name	ISIS
Event ID	2033
Event name	tmnxIsisIDLenMismatch
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.5
Default severity	warning
Message format string	ISIS-id length mismatch - field length: $tmnxIsisNotifFieldLen$, interface: $vRtrIfIndex$, on fragment: $vRtrIsisPDUFragmentString$
Cause	The tmnxIsisIDLenMismatch notification is sent when we receive a PDU with a different value of the System ID Length. This notification includes the 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisLdpSyncExit

Table 17. tmnxIsisLdpSyncExit properties
Property name	Value
Application name	ISIS
Event ID	2049
Event name	tmnxIsisLdpSyncExit
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.21
Default severity	warning
Message format string	IGP-LDP synchronization has stopped for interface $vRtrIfIndex$ because Exit State $tmnxIsisIfLdpSyncTimerState$
Cause	The tmnxIsisLdpSyncExit notification is sent when IGP-LDP synchronization has stopped. The cause of this event is indicated by tmnxIsisIfLdpSyncTimerState, one of them being expiry of vRtrIfLdpSyncTimer.
Effect	The IGP link metric is restored to normal levels.
Recovery	No recovery is necessary.

tmnxIsisLdpSyncTimerStarted

Table 18. tmnxIsisLdpSyncTimerStarted properties
Property name	Value
Application name	ISIS
Event ID	2048
Event name	tmnxIsisLdpSyncTimerStarted
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.20
Default severity	warning
Message format string	IGP-LDP synchronization timer has started for interface $vRtrIfIndex$.
Cause	The tmnxIsisLdpSyncTimerStarted notification is sent when the vRtrIfLdpSyncTimer is started. The timer is started from the time the LDP session to the neighbor is up over the interface.
Effect	This allows for the label FEC bindings to be exchanged.
Recovery	No recovery is necessary.

tmnxIsisLSPPurge

Table 19. tmnxIsisLSPPurge properties
Property name	Value
Application name	ISIS
Event ID	2060
Event name	tmnxIsisLSPPurge
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.32
Default severity	warning
Message format string	Possible messages: LSP Purge - interface: $vRtrIfIndex$, on level: $tmnxIsisNotifSystemLevel$, LSP: $vRtrIsisTrapLSPIDString$, POI SysId: $tmnxIsisNotifPurgeOriginatorString$ - $tmnxIsisNotifAdditionalInfo$ LSP Purge - interface: $vRtrIfIndex$, on level: $tmnxIsisNotifSystemLevel$, LSP: $vRtrIsisTrapLSPIDString$, POI sysId: $tmnxIsisNotifPurgeOriginatorString$, rcvd sysId: $tmnxIsisNotifPurgeSourceString$ - $tmnxIsisNotifAdditionalInfo$
Cause	The tmnxIsisLSPPurge notification is sent when a LSP is purged. This notification includes the system ID of the originator, or the upstream source of the purge, which may help a network manager to locate the origin of the purge and thus the cause of the purge.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisLSPTooLargeToPropagate

Table 20. tmnxIsisLSPTooLargeToPropagate properties
Property name	Value
Application name	ISIS
Event ID	2042
Event name	tmnxIsisLSPTooLargeToPropagate
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.14
Default severity	warning
Message format string	LSP too large to propagate - LSP size: $tmnxIsisNotifLSPSize$, on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, LSP-id: $vRtrIsisTrapLSPIDString$
Cause	The tmnxIsisLSPTooLargeToPropagate notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisManualAddressDrops

Table 21. tmnxIsisManualAddressDrops properties
Property name	Value
Application name	ISIS
Event ID	2030
Event name	tmnxIsisManualAddressDrops
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.2
Default severity	warning
Message format string	Configured manual area address $isisManAreaAddrString$ being ignored when computing routes
Cause	This notification is generated when one of the manual area addresses assigned to this system is ignored when computing routes. The object isisManAreaAddrExistState 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.
Effect	Assigned manual area address is ignored for computing routes.
Recovery	No recovery is necessary.

tmnxIsisMaxAreaAddrsMismatch

Table 22. tmnxIsisMaxAreaAddrsMismatch properties
Property name	Value
Application name	ISIS
Event ID	2034
Event name	tmnxIsisMaxAreaAddrsMismatch
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.6
Default severity	warning
Message format string	Max area addresses mismatch - max area addresses: $tmnxIsisNotifMaxAreaAddress$, interface: $vRtrIfIndex$, on fragment: $vRtrIsisPDUFragmentString$
Cause	The tmnxIsisMaxAreaAddrsMismatch notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisMaxSeqExceedAttempt

Table 23. tmnxIsisMaxSeqExceedAttempt properties
Property name	Value
Application name	ISIS
Event ID	2032
Event name	tmnxIsisMaxSeqExceedAttempt
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.4
Default severity	warning
Message format string	Protocol disabled due to attempt to exceed the maximum sequence on level: $tmnxIsisNotifSystemLevel$, with LSP-id: $vRtrIsisTrapLSPIDString$. Shutdown for a while and start over.
Cause	The tmnxIsisMaxSeqExceedAttempt notification is generated when the sequence number on an LSP wraps the 32 bit sequence counter, we purge and wait to re-announce this information. Since these should not be generated rapidly, we generate an event each time this happens. A possible cause could be that the same system-id is configured on multiple nodes; when 2 nodes have the same system-id they both keep incrementing its LSP sequence number causing the sequence counter to rollover. While the first 6 bytes of the LSPID are ours, the other two contain useful information.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisOrigLSPBufSizeMismatch

Table 24. tmnxIsisOrigLSPBufSizeMismatch properties
Property name	Value
Application name	ISIS
Event ID	2043
Event name	tmnxIsisOrigLSPBufSizeMismatch
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.15
Default severity	warning
Message format string	Originating LSP buffer size mismatch - LSP size: $tmnxIsisNotifOriginatingBuffSize$, on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, LSP-id: $vRtrIsisTrapLSPIDString$
Cause	The tmnxIsisOrigLSPBufSizeMismatch notification is sent when a Level 1 LSP or Level 2 LSP is received which is larger than the local value for isisSysOrigL1LSPBuffSize or isisSysOrigL2LSPBuffSize 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 isisSysOrigL1LSPBuffSize or isisSysOrigL2LSPBuffSize 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisOwnLSPPurge

Table 25. tmnxIsisOwnLSPPurge properties
Property name	Value
Application name	ISIS
Event ID	2035
Event name	tmnxIsisOwnLSPPurge
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.7
Default severity	warning
Message format string	Own LSP Purge - interface: $vRtrIfIndex$, on level: $tmnxIsisNotifSystemLevel$, LSP: $vRtrIsisTrapLSPIDString$
Cause	The tmnxIsisOwnLSPPurge notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisPfxLimitOverloadWarning

Table 26. tmnxIsisPfxLimitOverloadWarning properties
Property name	Value
Application name	ISIS
Event ID	2061
Event name	tmnxIsisPfxLimitOverloadWarning
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.33
Default severity	warning
Message format string	Overload warning $tmnxIsisNotifAdditionalInfo$
Cause	The tmnxIsisPfxLimitOverloadWarning notification is sent when the number of prefixes in the system reaches the tmnxIsisPrefixLimitThreshold or the tmnxIsisPrefixLimit.
Effect	When tmnxIsisPrefixLimit is not yet reached, but the tmnxIsisPrefixLimitThreshold is reached there is no direct effect; but when the number of prefixes grows the system might go into overload. When the tmnxIsisPrefixLimit is reached and the object tmnxIsisPrefixLimitLogOnly is false, IS-IS will be into overload. There is no direct effect when the object tmnxIsisPrefixLimitLogOnly is true.
Recovery	Increase the IS-IS prefix limit.

tmnxIsisProtoSuppMismatch

Table 27. tmnxIsisProtoSuppMismatch properties
Property name	Value
Application name	ISIS
Event ID	2044
Event name	tmnxIsisProtoSuppMismatch
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.16
Default severity	warning
Message format string	Supported protocol mismatch - supported protocol: $tmnxIsisNotifProtocolsSupported$, on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, LSP-id: $vRtrIsisTrapLSPIDString$
Cause	The tmnxIsisProtoSuppMismatch notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisRejectedAdjacency

Table 28. tmnxIsisRejectedAdjacency properties
Property name	Value
Application name	ISIS
Event ID	2041
Event name	tmnxIsisRejectedAdjacency
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.13
Default severity	warning
Message format string	Rejected adjacency on interface: $vRtrIfIndex$, for level:$tmnxIsisNotifSystemLevel$
Cause	The tmnxIsisRejectedAdjacency notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisRejectedAdjacencySet

Table 29. tmnxIsisRejectedAdjacencySet properties
Property name	Value
Application name	ISIS
Event ID	2065
Event name	tmnxIsisRejectedAdjacencySet
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.37
Default severity	warning
Message format string	Failed adj-set on interface: $tmnxIsisNotifyIfIndex$, for level:$tmnxIsisNotifSystemLevel$, description: $tmnxIsisNotifyDescription$
Cause	The tmnxIsisRejectedAdjacencySet 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.

tmnxIsisRejectedAdjacencySid

Table 30. tmnxIsisRejectedAdjacencySid properties
Property name	Value
Application name	ISIS
Event ID	2059
Event name	tmnxIsisRejectedAdjacencySid
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.31
Default severity	warning
Message format string	Failed SID adjacency on interface: $vRtrIfIndex$, for level:$tmnxIsisNotifSystemLevel$, description: $tmnxIsisNotifyDescription$
Cause	The tmnxIsisRejectedAdjacencySid 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.

tmnxIsisRejectedEndXSid

Table 31. tmnxIsisRejectedEndXSid properties
Property name	Value
Application name	ISIS
Event ID	2069
Event name	tmnxIsisRejectedEndXSid
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.41
Default severity	warning
Message format string	Failed end-x SID on interface: $vRtrIfIndex$, for level:$tmnxIsisNotifSystemLevel$, description: $tmnxIsisNotifyDescription$
Cause	The tmnxIsisRejectedEndXSid notification is sent when we do not establish a SRv6 End-X SID due to a lack of resources. This should be an edge-triggered notification. We should not send a second notification about end-x SID allocation failure for the same adjacency.
Effect	No effect.
Recovery	Whenever an end-x SID is released, the released end-x SID can be reused by any other adjacency which is waiting to receive an end-x SID.

tmnxIsisRejectedPgId

Table 32. tmnxIsisRejectedPgId properties
Property name	Value
Application name	ISIS
Event ID	2070
Event name	tmnxIsisRejectedPgId
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.42
Default severity	warning
Message format string	Failed PGID on interface: $vRtrIfIndex$, for level:$tmnxIsisNotifSystemLevel$, description: $tmnxIsisNotifyDescription$
Cause	The tmnxIsisRejectedPgId notification is sent when we do not establish a SRv6 adjacency PGID due to a lack of resources. This should be an edge-triggered notification. We should not send a second notification about adjacency PGID allocation failure for the same adjacency.
Effect	No effect.
Recovery	Whenever a PGID is released, the released PGID can be reused by any other adjacency which is waiting to receive a PGID.

tmnxIsisRoutesExpLmtDropped

Table 33. tmnxIsisRoutesExpLmtDropped properties
Property name	Value
Application name	ISIS
Event ID	2052
Event name	tmnxIsisRoutesExpLmtDropped
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.24
Default severity	warning
Message format string	The number of redistributed routes into ISIS level $tmnxIsisNotifSystemLevel$ has dropped below the export limit $tmnxIsisExportLimit$
Cause	The tmnxIsisRoutesExpLmtDropped notification is sent when the total number of exported routes from the route table to this ISIS level drops below the configured export limit, tmnxIsisExportLimit.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisSequenceNumberSkip

Table 34. tmnxIsisSequenceNumberSkip properties
Property name	Value
Application name	ISIS
Event ID	2036
Event name	tmnxIsisSequenceNumberSkip
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.8
Default severity	warning
Message format string	Sequence number skipped for LSP: $vRtrIsisTrapLSPIDString$, on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$
Cause	The tmnxIsisSequenceNumberSkip notification is sent when we need to increase the sequence number by more than one. When we receive an LSP without System ID and different contents, we may need to reissue the LSP with a higher sequence number. If two Intermediate Systems are configured with the same System ID, this notification will fire.
Effect	No effect.
Recovery	No recovery is necessary.

tmnxIsisSidError

Table 35. tmnxIsisSidError properties
Property name	Value
Application name	ISIS
Event ID	2057
Event name	tmnxIsisSidError
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.29
Default severity	minor
Message format string	$tmnxIsisNotifyDescription$ SID: $tmnxIsisPrefixSidValue$, level:$tmnxIsisPrefixSidLevel$, mtid: $tmnxIsisRouteMtId$, type:$tmnxIsisPrefixSidType$, flags: $tmnxIsisPrefixSidFlags$, algo:$tmnxIsisPrefixSidAlgorithm$
Cause	This notification is generated when ISIS 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

tmnxIsisSidNotInLabelRange

Table 36. tmnxIsisSidNotInLabelRange properties
Property name	Value
Application name	ISIS
Event ID	2058
Event name	tmnxIsisSidNotInLabelRange
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.30
Default severity	minor
Message format string	SID not in range of router: $tmnxIsisNotifPfxSidSysIDString$, SID:$tmnxIsisPrefixSidValue$, startLabel: $tmnxIsisNotifPfxSidRangeStartLbl$, maxIdx:$tmnxIsisNotifPfxSidRangeMaxIdx$ level: $tmnxIsisPrefixSidLevel$, mtid:$tmnxIsisRouteMtId$, type: $tmnxIsisPrefixSidType$, flags:$tmnxIsisPrefixSidFlags$, algo: $tmnxIsisPrefixSidAlgorithm$
Cause	This notification is generated when ISIS 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.

tmnxIsisSidStatsIndexAlloc

Table 37. tmnxIsisSidStatsIndexAlloc properties
Property name	Value
Application name	ISIS
Event ID	2067
Event name	tmnxIsisSidStatsIndexAlloc
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.39
Default severity	warning
Message format string	Possible messages: Statistics Index Allocation status changed to $tmnxIsisNotifStatsIndexStatus$ for adjacency-set $tmnxIsisSidStatsAdjSet$ Statistics Index Allocation status changed to $tmnxIsisNotifStatsIndexStatus$ for adjacency interface $tmnxIsisSidStatsIfIndex$ Statistics Index Allocation status changed to $tmnxIsisNotifStatsIndexStatus$ for node $tmnxIsisSidStatsPrefix$/$tmnxIsisSidStatsPrefixLength$
Cause	The tmnxIsisSidStatsIndexAlloc 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.

tmnxIsisSrgbBadLabelRange

Table 38. tmnxIsisSrgbBadLabelRange properties
Property name	Value
Application name	ISIS
Event ID	2063
Event name	tmnxIsisSrgbBadLabelRange
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.35
Default severity	warning
Message format string	Bad SRGB label range for advertising router: $tmnxIsisNotifSrgbAdvRtrSysIDString$, startLabel:$tmnxIsisNotifSrgbRangeStartLbl$, maxIdx: $tmnxIsisNotifSrgbRangeMaxIdx$, level:$tmnxIsisNotifSrgbLevel$, mtid: $tmnxIsisNotifSrgbMtId$ $tmnxIsisNotifAdditionalInfo$
Cause	The tmnxIsisSrgbBadLabelRange notification is sent when ISIS receives a bad SRGB label range from a router (for example, overlapping with another label range).
Effect	The configured Segment Routing tunnels will be wrong.
Recovery	Change the label range to recover.

tmnxIsisSrv6LocError

Table 39. tmnxIsisSrv6LocError properties
Property name	Value
Application name	ISIS
Event ID	2071
Event name	tmnxIsisSrv6LocError
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.43
Default severity	warning
Message format string	$tmnxIsisNotifyDescription$, level: $tmnxIsisNotifSystemLevel$, mtid:$tmnxIsisRouteMtId$, algo: $tmnxIsisSrv6SidAlgorithm$
Cause	This notification is generated when ISIS receives an IOM or CPM failure (system exhausted ILM, NHLFE, duplicate SID) while resolving and programming a received SRv6 locator.
Effect	The Segment Routing tunnel corresponding to this locator 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 SRv6 tunnels which previously failed the programming operation

tmnxIsisVersionSkew

Table 40. tmnxIsisVersionSkew properties
Property name	Value
Application name	ISIS
Event ID	2039
Event name	tmnxIsisVersionSkew
SNMP notification prefix and OID	TIMETRA-ISIS-NG-MIB.tmnxIsisNotifications.11
Default severity	warning
Message format string	Protocol version skew - $tmnxIsisNotifProtocolVersion$ on interface: $vRtrIfIndex$, for level: $tmnxIsisNotifSystemLevel$, fragment: $vRtrIsisPDUFragmentString$
Cause	The tmnxIsisVersionSkew notification is 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.
Effect	No effect.
Recovery	No recovery is necessary.

vRtrIsisSpbNbrMultAdjExists

Table 41. vRtrIsisSpbNbrMultAdjExists properties
Property name	Value
Application name	ISIS
Event ID	2025
Event name	vRtrIsisSpbNbrMultAdjExists
SNMP notification prefix and OID	TIMETRA-ISIS-MIB.vRtrIsisNotifications.25
Default severity	warning
Message format string	SPB multiple adjacency exists for neighbor $vRtrIsisNbrSysIdString$ on interface $vRtrIfIndex$ at system level $vRtrIsisSystemLevel$
Cause	A vRtrIsisSpbNbrMultAdjExists notification is sent when IS-IS SPB instance detects a neighbor to which it already has a direct adjacency on another interface.
Effect	During SPF IS-IS SPB instance will have incorrect neighbor information and hence path computations will be incorrect.
Recovery	Check number of links to neighbor to make sure there is only one link.

vRtrIsisSpbNbrMultAdjExistsClear

Table 42. vRtrIsisSpbNbrMultAdjExistsClear properties
Property name	Value
Application name	ISIS
Event ID	2026
Event name	vRtrIsisSpbNbrMultAdjExistsClear
SNMP notification prefix and OID	TIMETRA-ISIS-MIB.vRtrIsisNotifications.26
Default severity	warning
Message format string	SPB multiple adjacency cleared for neighbor $vRtrIsisNbrSysIdString$ on interface $vRtrIfIndex$ at system level $vRtrIsisSystemLevel$
Cause	A vRtrIsisSpbNbrMultAdjExistsClear notification is sent when an IS-IS SPB instance clears the condition raised by vRtrIsisSpbNbrMultAdjExists notification.
Effect	During SPF IS-IS SPB instance will have correct neighbor information and hence path computations will be correct.
Recovery	None required.

vRtrSpbEctFidCfgChg

Table 43. vRtrSpbEctFidCfgChg properties
Property name	Value
Application name	ISIS
Event ID	2027
Event name	vRtrSpbEctFidCfgChg
SNMP notification prefix and OID	TIMETRA-ISIS-MIB.vRtrIsisNotifications.27
Default severity	warning
Message format string	SPB ect-algorithm changed to $vRtrSpbEctFidAlgorithm$ for FID range $vRtrSpbEctFidStart$- $vRtrSpbEctFidEnd$ under $vRtrIsisLevel$
Cause	A vRtrSpbEctFidCfgChg notification is sent when a configuration change is made to vRtrSpbEctFidTable affecting forwarding database identifiers in the range from vRtrSpbEctFidStart to vRtrSpbEctFidEnd.
Effect	There are changes in the vRtrSpbEctFidTable which may be out-of-sync with management application.
Recovery	Management application may need to synchronize with changes in the vRtrSpbEctFidTable.

August 3, 2023