Monitor and troubleshoot
Documents under this category provide information about monitoring, diagnosing, and troubleshooting router issues.
- 7450 and 7750 Troubleshooting Guide
- 7950 Troubleshooting Guide
- Log Events Guide
  This guide provides information about log events.
- Log Events Search Tool
  A searchable HTML list of the SR OS 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.

RIP_NG

tmnxRipNgAuthFailure

Table 1. tmnxRipNgAuthFailure properties
Property name	Value
Application name	RIP_NG
Event ID	2003
Event name	tmnxRipNgAuthFailure
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.2
Default severity	minor
Source stream	main
Message format string	Authentication type failure on $tmnxRipNgInstVersion$ packet received from peer $tmnxRipNgPeerAddress$ on interface $tmnxRipNgPeerIfIndex$
Cause	A tmnxRipNgAuthFailure trap is generated when the authentication key in a received RIPv2 packet conflicts with the authentication key configured for this router.
Effect	N/A
Recovery	N/A

tmnxRipNgAuthTypeMismatch

Table 2. tmnxRipNgAuthTypeMismatch properties
Property name	Value
Application name	RIP_NG
Event ID	2002
Event name	tmnxRipNgAuthTypeMismatch
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.1
Default severity	minor
Source stream	main
Message format string	Authentication type mismatch on $tmnxRipNgInstVersion$ packet received from peer $tmnxRipNgPeerAddress$ on interface $tmnxRipNgPeerIfIndex$
Cause	A tmnxRipNgAuthTypeMismatch trap is generated when the authentication type field in a received RIPv2 packet conflicts with the authentication type configured for this router.
Effect	N/A
Recovery	N/A

tmnxRipNgIfUcastAddrNotUsed

Table 3. tmnxRipNgIfUcastAddrNotUsed properties
Property name	Value
Application name	RIP_NG
Event ID	2009
Event name	tmnxRipNgIfUcastAddrNotUsed
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.8
Default severity	minor
Source stream	main
Message format string	$tmnxRipNgInstVersion$ neighbor $vRtrIfIndex$ has unicast addresses configured while send mode is not set to 'unicast'
Cause	A tmnxRipNgIfUcastAddrNotUsed notification is generated when a neighbor has one or more unicast-addresses configured but it's send mode is not set to 'unicast'.
Effect	N/A
Recovery	N/A

tmnxRipNgInstExpLmtReached

Table 4. tmnxRipNgInstExpLmtReached properties
Property name	Value
Application name	RIP_NG
Event ID	2006
Event name	tmnxRipNgInstExpLmtReached
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.5
Default severity	minor
Source stream	main
Message format string	$tmnxRipNgInstVersion$ instance has reached the export limit $tmnxRipNgInstExportLimit$, additional routes will not be exported into the instance
Cause	A tmnxRipNgInstExpLmtReached notification is generated when the configured value of exported routes, tmnxRipNgInstExportLimit is reached. Additional routes would not be exported into RIP/RIP-NG from the route table.
Effect	N/A
Recovery	N/A

tmnxRipNgInstExpLmtWarning

Table 5. tmnxRipNgInstExpLmtWarning properties
Property name	Value
Application name	RIP_NG
Event ID	2007
Event name	tmnxRipNgInstExpLmtWarning
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.6
Default severity	minor
Source stream	main
Message format string	$tmnxRipNgInstVersion$ instance has reached $tmnxRipNgInstExpLmtLogPct$ percent of the export limit $tmnxRipNgInstExportLimit$
Cause	A tmnxRipNgInstExpLmtWarning notification is generated when the number of exported routes is equal to the configured percent, tmnxRipNgInstExpLmtLogPct of the export limit, tmnxRipNgInstExportLimit. Additional routes will continue to be exported into RIP/RIP-NG from the route table till the export limit is reached.
Effect	N/A
Recovery	N/A

tmnxRipNgInstRestarted

Table 6. tmnxRipNgInstRestarted properties
Property name	Value
Application name	RIP_NG
Event ID	2005
Event name	tmnxRipNgInstRestarted
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.4
Default severity	minor
Source stream	main
Message format string	$tmnxRipNgInstVersion$ instance restarted
Cause	When a RIP/RIP-NG protocol instance runs out of resources, the instance will shut down and then attempt to restart within 30 seconds. A tmnxRipNgInstRestarted trap is generated when the RIP instance has restarted.
Effect	N/A
Recovery	N/A

tmnxRipNgInstRtsExpLmtDropped

Table 7. tmnxRipNgInstRtsExpLmtDropped properties
Property name	Value
Application name	RIP_NG
Event ID	2008
Event name	tmnxRipNgInstRtsExpLmtDropped
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.7
Default severity	minor
Source stream	main
Message format string	The number of redistributed routes into the $tmnxRipNgInstVersion$ instance has dropped below the export limit $tmnxRipNgInstExportLimit$
Cause	A tmnxRipNgInstRtsExpLmtDropped notification is generated when the number of exported routes drops below the export limit, tmnxRipNgInstExportLimit.
Effect	N/A
Recovery	N/A

tmnxRipNgInstShuttingDown

Table 8. tmnxRipNgInstShuttingDown properties
Property name	Value
Application name	RIP_NG
Event ID	2004
Event name	tmnxRipNgInstShuttingDown
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.3
Default severity	minor
Source stream	main
Message format string	$tmnxRipNgInstVersion$ instance is being operationally 'shutdown' because $tmnxRipNgNotifyReason$
Cause	A tmnxRipNgInstShuttingDown trap is generated when the RIP/RIP-NG instance shuts down on its own accord when the protocol runs out of resources such as memory. The instance will attempt to restart within 30 seconds of shutting down.
Effect	N/A
Recovery	N/A

tmnxRipNgPacketDiscarded

Table 9. tmnxRipNgPacketDiscarded properties
Property name	Value
Application name	RIP_NG
Event ID	2001
Event name	tmnxRipNgPacketDiscarded
SNMP notification prefix and OID	N/A
Default severity	minor
Source stream	main
Message format string	Discarded $tmnxRipNgInstVersion$ packet received from $tmnxRipNgNotifySrcAddr$ on interface $vRtrIfIndex$ because $tmnxRipNgNotifyReason$
Cause	The following checks are performed on an incoming RIP packet - valid RIP version - valid source address and port - valid destination address and port - valid routes etc. If a packet fails any of these checks it must be discarded, and the event is logged.
Effect	N/A
Recovery	N/A

tmnxRipNgPeerBfdDown

Table 10. tmnxRipNgPeerBfdDown properties
Property name	Value
Application name	RIP_NG
Event ID	2010
Event name	tmnxRipNgPeerBfdDown
SNMP notification prefix and OID	TIMETRA-RIP-NG-MIB.tmnxRipNgNotifications.9
Default severity	warning
Source stream	main
Message format string	$tmnxRipNgInstVersion$ peer $tmnxRipNgPeerAddress$ on interface $tmnxRipNgPeerIfIndex$ went down due to a BFD session failure
Cause	A peer is presumed down because of a BFD session failure.
Effect	All routes learned from the peer will be removed from the routing table.
Recovery	N/A

October 31, 2023