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.

FILTER

tFilterApplyPathProblem

Table 1. tFilterApplyPathProblem properties
Property name	Value
Application name	FILTER
Event ID	2008
Event name	tFilterApplyPathProblem
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.8
Default severity	minor
Source stream	main
Message format string	Problem in $tFltrPrefixListType$ prefix-list $tFltrPrefixListName$ for apply-path $tFltrApplyPathSource$ $tFltrApplyPathIndex$: $tFilterAlarmDescription$
Cause	Failed to add prefix/prefixes specified by the apply-path rule to the prefix list likely due to insufficient resources.
Effect	Prefix list does not contain all prefixes specified by the apply-path rule.
Recovery	Release resources by removing unnecessary prefixes or specify more specific apply-path rule.

tFilterBgpFlowSpecProblem

Table 2. tFilterBgpFlowSpecProblem properties
Property name	Value
Application name	FILTER
Event ID	2007
Event name	tFilterBgpFlowSpecProblem
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.7
Default severity	minor
Source stream	main
Message format string	N/A
Cause	N/A
Effect	N/A
Recovery	N/A

tFilterEmbeddingOperStateChange

Table 3. tFilterEmbeddingOperStateChange properties
Property name	Value
Application name	FILTER
Event ID	2011
Event name	tFilterEmbeddingOperStateChange
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.11
Default severity	minor
Source stream	main
Message format string	The operational state of the embedded filter ID $tFilterEmbeddedRefEmbeddedFltrId$ in the embedding filter $tFilterEmbeddedRefFilterType$ ID $tFilterEmbeddedRefInsertFltrId$ has changed to $tFilterEmbeddedRefOperState$.
Cause	This notification may be triggered for the following reasons: 1) An attempt to embed an embedded filter into embedding filter was done. 2) An attempt to recover an embedding that is operationally down was done. 3) An attempt to change the admin state of an embedding was done. 4) The operational state of an embedding has changed to inactive due to lack of resources.
Effect	The effect depends on the new state. If the new state is 'active', the embedding of the filter was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the embedded entries were removed. Otherwise the embedding filter was not changed.
Recovery	If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the embedding.

tFilterEmbedFlowspecOperStateChg

Table 4. tFilterEmbedFlowspecOperStateChg properties
Property name	Value
Application name	FILTER
Event ID	2015
Event name	tFilterEmbedFlowspecOperStateChg
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.14
Default severity	minor
Source stream	main
Message format string	The operational state of the embedded FlowSpec rules of virtual router $tFilterEmbedFlowspecRtrId$ in the embedding filter $tFilterEmbedFlowspecFilterType$ ID $tFilterEmbedFlowspecInsertFltrId$ has changed to $tFilterEmbedFlowspecOperState$.
Cause	This notification may be triggered for the following reasons: 1) An attempt to embed a set of flowspec rules into an embedding filter was done. 2) An attempt to recover a flowspec rules embedding that is operationally down was done. 3) An attempt to change the admin state of a flowspec rules embedding was done. 4) The operational state of a flowspec rules embedding has changed to inactive due to lack of resources.
Effect	The effect depends on the new state. If the new state is 'active', the embedding of a set of flowspec rules was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the set of flowspec rules were removed. Otherwise the embedding filter was not changed.
Recovery	If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the flowspec rules embedding.

tFilterEmbedOpenflowOperStateChg

Table 5. tFilterEmbedOpenflowOperStateChg properties
Property name	Value
Application name	FILTER
Event ID	2012
Event name	tFilterEmbedOpenflowOperStateChg
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.12
Default severity	minor
Source stream	main
Message format string	The operational state of the embedded open-flow switch $tFilterEmbedOpenflowOfsName$ in the embedding filter $tFilterEmbedOpenflowFilterType$ ID $tFilterEmbedOpenflowInsertFltrId$ has changed to $tFilterEmbedOpenflowOperState$.
Cause	This notification may be triggered for the following reasons: 1) An attempt to embed an open-flow switch into an embedding filter was done. 2) An attempt to recover an open-flow embedding that is operationally down was done. 3) An attempt to change the admin state of an open-flow embedding was done. 4) The operational state of an open-flow embedding has changed to inactive due to lack of resources.
Effect	The effect depends on the new state. If the new state is 'active', the embedding of an open-flow switch was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the open-flow switch entries were removed. Otherwise the embedding filter was not changed.
Recovery	If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the open-flow embedding.

tFilterOpenflowRequestRejected

Table 6. tFilterOpenflowRequestRejected properties
Property name	Value
Application name	FILTER
Event ID	2013
Event name	tFilterOpenflowRequestRejected
SNMP notification prefix and OID	N/A
Default severity	minor
Source stream	main
Message format string	An error was encountered while handling filter entry $fltrOpenFlowFlowEntryId$ for the open-flow flowTable $fltrOpenFlowFlowTable$. Additional Info: $fltrOpenFlowProblemDescription$.
Cause	N/A
Effect	N/A
Recovery	N/A

tFilterRadSharedFltrAlarmClear

Table 7. tFilterRadSharedFltrAlarmClear properties
Property name	Value
Application name	FILTER
Event ID	2010
Event name	tFilterRadSharedFltrAlarmClear
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.10
Default severity	minor
Source stream	main
Message format string	The number of dynamically allocated Radius Shared Filters based on $tFilterType$ $tFilterId$ has dropped below the threshold of $tFilterThresholdReached$
Cause	The tFilterRadSharedFltrAlarmClear notification is generated when the number of Radius Shared Filters that are dynamically created in the system dropped below to the configured low watermark for the indicated filter.
Effect	The system is working properly, and well within its configured bounds.
Recovery	No recovery is needed.

tFilterRadSharedFltrAlarmRaised

Table 8. tFilterRadSharedFltrAlarmRaised properties
Property name	Value
Application name	FILTER
Event ID	2009
Event name	tFilterRadSharedFltrAlarmRaised
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.9
Default severity	minor
Source stream	main
Message format string	The number of dynamically allocated Radius Shared Filters based on $tFilterType$ $tFilterId$ has exceeded its threshold of $tFilterThresholdReached$
Cause	The tFilterRadSharedFltrAlarmRaised notification is generated when the number of Radius Shared Filters that are dynamically created in the system increases to the configured high watermark for the indicated filter.
Effect	No direct effect, however the system may run out of filter resources.
Recovery	The way in which dynamically filters are used in the system/network may need to be reconsidered.

tFilterRPActiveDestChangeEvent

Table 9. tFilterRPActiveDestChangeEvent properties
Property name	Value
Application name	FILTER
Event ID	2017
Event name	tFilterRPActiveDestChangeEvent
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.16
Default severity	minor
Source stream	main
Message format string	The active destination of redirect policy $tFilterRedirectPolicy$ has changed to $tFilterRPActiveDestAddr$.
Cause	This notification was triggered because active destination of a redirect policy has changed.
Effect	Traffic hitting filter entries with forward redirect-policy set to this redirect policy will be directed toward the new active destination.
Recovery	No recovery action is required.

tFilterSubInsFltrEntryDropped

Table 10. tFilterSubInsFltrEntryDropped properties
Property name	Value
Application name	FILTER
Event ID	2006
Event name	tFilterSubInsFltrEntryDropped
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.6
Default severity	warning
Source stream	main
Message format string	A request to insert a filter-entry in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ has failed - $tFilterAlarmDescription$
Cause	A request to insert a filter entry failed.
Effect	The filter may not be working as intended.
Recovery	Actions may be taken depending on the reason of why the insertion failed.

tFilterSubInsSpaceAlarmCleared

Table 11. tFilterSubInsSpaceAlarmCleared properties
Property name	Value
Application name	FILTER
Event ID	2005
Event name	tFilterSubInsSpaceAlarmCleared
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.5
Default severity	warning
Source stream	main
Message format string	The range of entries reserved in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ has fallen below its configured low watermark level $tFilterThresholdReached$
Cause	A range of entries in the filter has been reserved (via configuration) to be used for inserting entries by the system. If the number of used entries drops below the (configured) low watermark, this notification is sent.
Effect	The system is working properly, and well within its configured bounds.
Recovery	No recovery is needed.

tFilterSubInsSpaceAlarmRaised

Table 12. tFilterSubInsSpaceAlarmRaised properties
Property name	Value
Application name	FILTER
Event ID	2004
Event name	tFilterSubInsSpaceAlarmRaised
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.4
Default severity	warning
Source stream	main
Message format string	The range of entries reserved in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ is filled up to its configured high watermark level $tFilterThresholdReached$
Cause	A range of entries in the filter has been reserved (via configuration) to be used for inserting entries by the system. If the number of used entries reaches the (configured) high watermark, this notification is sent.
Effect	If no more entries are available, no more filter entries will be inserted by the system
Recovery	If needed, more entries can be reserved for inserting entries by the system.

tIPFilterPBRPacketsDrop

Table 13. tIPFilterPBRPacketsDrop properties
Property name	Value
Application name	FILTER
Event ID	2001
Event name	tIPFilterPBRPacketsDrop
SNMP notification prefix and OID	TIMETRA-FILTER-MIB.tFilterNotifications.1
Default severity	warning
Source stream	main
Message format string	Filter $tIPFilterId$ entry $tIPFilterParamsIndex$ PBR packets dropped on interface $tIPFilterParamsForwardNHInterface$ because $tFilterPBRDropReason$.
Cause	The tIPFilterPlcyBasedRoutingPacketsDrop event is generated either when the configuration of a forwarding action refers to an invalid/unconfigured next-hop or if the active interface goes down operationally in the process of active filtering.
Effect	The tIPFilterPlcyBasedRoutingPacketsDrop event is generated either when the configuration of a forwarding action refers to an invalid/unconfigured next-hop or if the active interface goes down operationally in the process of active filtering.
Recovery	No recovery is required.

March 15, 2024