LOGGER
STARTED
Property name | Value |
---|---|
Application name | LOGGER |
Event ID |
2001 |
Event name | STARTED |
SNMP notification prefix and OID | N/A |
Default severity |
minor |
Source stream | main |
Message format string | Event collector $taskName$ started |
Cause | An event log collector process was started. |
Effect |
Application events will be collected, filtered, and distributed, as configured. |
Recovery | No recovery; not applicable. |
tmnxClear
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2010 |
Event name | tmnxClear |
SNMP notification prefix and OID |
TIMETRA-CLEAR-MIB.tmnxClearNotifications.1 |
Default severity |
indeterminate |
Source stream | main |
Message format string | Clear function $tmnxClearName$ has been run with parameters: $tmnxClearParams$. The completion result is: $tmnxClearResult$. Additional error text, if any, is: $tmnxClearErrorText$ |
Cause | The tmnxClear notification is generated to report the results of the clear function that was run as a result of setting tmnxClearAction to 'doAction'. |
Effect | If successful, the managed object was cleared. |
Recovery | If failed, check that the managed object exists or that the clear function parameters are correct. |
tmnxLogAccountingDataLoss
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2014 |
Event name | tmnxLogAccountingDataLoss |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.10 |
Default severity |
major |
Source stream | main |
Message format string |
Accounting data loss occurred for $subject$. |
Cause |
An accounting file was still being written to when the next collection interval ended. |
Effect | A tmnxLogAccountingDataLoss notification is generated when an accounting file is still being written to when the next collection interval ends. The collection of statistics for the past interval is immediately stopped and collection is started for the next interval. There are missing records in the file for this past interval. |
Recovery | N/A |
tmnxLogAdminLocFailed
Property name | Value |
---|---|
Application name | LOGGER |
Event ID |
2006 |
Event name | tmnxLogAdminLocFailed |
SNMP notification prefix and OID | TIMETRA-LOG-MIB.tmnxLogNotifications.2 |
Default severity | major |
Source stream |
main |
Message format string | Possible messages:
|
Cause | Generated when the specified admin cflash is not available. Indicates that an alternative backup location, if specified, will be used. |
Effect | N/A |
Recovery | N/A |
tmnxLogBackupLocFailed
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2007 |
Event name | tmnxLogBackupLocFailed |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.3 |
Default severity |
major |
Source stream | main |
Message format string |
Compact flash backup location cf$tmnxLogFileIdBackupLoc$ is not available for $subject$ .File destination creation failed |
Cause | Generated when the specified backup cflash is not available. |
Effect | No log or billing file was created on either the admin or backup cflash. |
Recovery | N/A |
tmnxLogEventOverrun
Property name | Value |
---|---|
Application name | LOGGER |
Event ID |
2017 |
Event name | tmnxLogEventOverrun |
SNMP notification prefix and OID | TIMETRA-LOG-MIB.tmnxLogNotifications.12 |
Default severity | major |
Source stream |
main |
Message format string | $tmnxLogThrottledEvents$ $tmnxLogThrottledEventID$ events were dropped because of logger input queue overrun. |
Cause | A tmnxLogEventOverrun notification is generated at the end of the overrun throttling interval when one or more events of the type specified by tmnxLogThrottledEventID were dropped because the logger input stream's input queue limit was exceeded. The overrun throttling interval begins when the input queue limit is first exceeded and ends when the number of events in the input queue has dropped below an internal low watermark. At that point a tmnxLogEventOverrun notification is generated for each event type that had one or more events dropped because of the input queue overrun. The number of dropped events is specified by tmnxLogThrottledEvents. |
Effect | Logger events have been dropped and were not sent to any log destination. tmnxEventDropCount has been incremented for each event dropped because of input queue overrun. |
Recovery | The specific event information of dropped events cannot be recovered. The frequency of input queue overruns can be lessened by configuring as few event logs as possible, especially those going to remote destinations such as file, syslog and snmp notification logs |
tmnxLogEventThrottled
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2012 |
Event name | tmnxLogEventThrottled |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.8 |
Default severity |
major |
Source stream | main |
Message format string |
$tmnxLogThrottledEvents$ $tmnxLogThrottledEventID$ events were dropped in the last event throttling interval. |
Cause | A tmnxLogEventThrottled notification is generated at the end of the throttling interval when one or more events are dropped because the throttling limit was reached for that interval. |
Effect | N/A |
Recovery | N/A |
tmnxLogFileDeleted
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2009 |
Event name | tmnxLogFileDeleted |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.5 |
Default severity |
minor |
Source stream | main |
Message format string |
Log file $tmnxLogFileDeletedName$ on compact flash cf$tmnxLogFileDeletedLocation$ has been deleted |
Cause | Generated when a closed event log or accounting policy file has been deleted as part of the space contention cleanup. |
Effect | N/A |
Recovery | N/A |
tmnxLogFileRollover
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2008 |
Event name | tmnxLogFileRollover |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.4 |
Default severity |
major |
Source stream | main |
Message format string |
Log file $tmnxLogFileIdPathName$ on compact flash cf$tmnxLogFileIdOperLocation$ has been rolled over |
Cause | Generated when an event log or accounting policy file's rollover time has expired. |
Effect | The file located as indicated by the value of tmnxLogFileIdOperLocation is closed and a new file is created as specified by tmnxLogFileIdAdminLocation and tmnxLogFileIdBackupLoc. |
Recovery | No recovery is necessary. |
tmnxLogOnlyEventOverrun
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2018 |
Event name | tmnxLogOnlyEventOverrun |
SNMP notification prefix and OID |
N/A |
Default severity | major |
Source stream | main |
Message format string |
$tmnxLogOnlyOverrunEvents$ $tmnxLogOnlyOverrunEventName$ log-only (L) events were dropped because the logger input queue was overrun. |
Cause | A tmnxLogOnlyEventOverrun notification is generated at the end of the overrun throttling interval when one or more log-only events of the type specified by tmnxLogOnlyOverrunEventName were dropped because the logger input stream's input queue limit was exceeded. The overrun throttling interval begins when the input queue limit is first exceeded and ends when the number of events in the input queue has dropped below an internal low watermark. At that point a tmnxLogOnlyEventOverrun notification is generated for each log-only event type that had one or more events dropped because of the input queue overrun. The number of dropped events is specified by tmnxLogOnlyOverrunEvents. |
Effect | Logger events have been dropped and were not sent to any log destination. tmnxEventDropCount has been incremented for each event dropped because of input queue overrun. |
Recovery | The specific event information of dropped events cannot be recovered. The frequency of input queue overruns can be lessened by configuring as few event logs as possible, especially those going to remote destinations such as file, syslog and snmp notification logs |
tmnxLogOnlyEventThrottled
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2016 |
Event name | tmnxLogOnlyEventThrottled |
SNMP notification prefix and OID |
N/A |
Default severity | major |
Source stream | main |
Message format string |
$tmnxLogOnlyThrottledEvents$ $tmnxLogOnlyThrottledEventName$ log-only (L) events were dropped in the last event throttling interval. |
Cause | One or more log-only events were dropped because the throttling limit was reached for that interval. |
Effect | A tmnxLogOnlyEventThrottled event is generated at the end of the throttling interval when one or more log-only events are dropped because the throttling limit was reached for that interval. |
Recovery | N/A |
tmnxLogSpaceContention
Property name | Value |
---|---|
Application name | LOGGER |
Event ID |
2005 |
Event name | tmnxLogSpaceContention |
SNMP notification prefix and OID | TIMETRA-LOG-MIB.tmnxLogNotifications.1 |
Default severity | major |
Source stream |
main |
Message format string | Space contention occurred on compact flash cf $cFlashId$ during I/O for $subject$. |
Cause | Generated when space contention occurs on the compact flash where a log or billing file creation is being attempted. Space contention exists if: Insufficient space is available on the compact flash to create a file of the same size as the file being rolled over. The first file of this type is being created and less than 10% of the total compact flash space is available. A write operation on a log or billing file is denied due to lack of space. |
Effect | N/A |
Recovery | N/A |
tmnxLogTraceError
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2002 |
Event name | tmnxLogTraceError |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.7 |
Default severity |
critical |
Source stream | main |
Message format string | $tmnxLogTraceErrorTitle$: $tmnxLogTraceErrorMessage$ |
Cause | The tmnxLogTraceError notification is generated when a critical level trace error has been detected by the software. There are multiple triggers for such a trace error. |
Effect | Effect varies depending on the specific trigger. |
Recovery | Contact Nokia Support. |
tmnxStdEventsReplayed
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2015 |
Event name | tmnxStdEventsReplayed |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.11 |
Default severity |
major |
Source stream | main |
Message format string |
Events $tmnxStdReplayStartEvent$ to $tmnxStdReplayEndEvent$ from $subject$ have been resent to SNMP notification target address $tmnxStdDestAddr$. The first event with no route to the target address was $tmnxStdReplayStart$. |
Cause | An SNMP trap target address was added to the route table following a period when a route to that address was not available. |
Effect | A tmnxStdEventsReplayed notification is generated when an SNMP trap target address is added to the RTM (tmnxVRtrID) following a period when the address had been removed. The value of tmnxStdReplayStartEvent is the SNMP notification request ID of the first event that was replayed. The value of tmnxStdReplayEndEvent is the SNMP notification request ID of the last missed event that was replayed. The value of tmnxStdReplayStart is the request ID of the first event for which there was no route to the trap target address. |
Recovery | N/A |
tmnxSysLogTargetProblem
Property name | Value |
---|---|
Application name | LOGGER |
Event ID |
2013 |
Event name | tmnxSysLogTargetProblem |
SNMP notification prefix and OID | TIMETRA-LOG-MIB.tmnxLogNotifications.9 |
Default severity | major |
Source stream |
main |
Message format string | Problem encountered when trying to reach the destination specified in syslog $tmnxSysLogTargetId$ : $tmnxSysLogTargetProblemDescr$. |
Cause |
An event could not be delivered to the destination specified for the syslog. |
Effect | A tmnxSysLogTargetProblem notification is generated when a problem is encountered when trying to deliver data to the syslog destination identified by the tmnxSysLogTargetId. |
Recovery | N/A |
tmnxTestEvent
Property name | Value |
---|---|
Application name |
LOGGER |
Event ID | 2011 |
Event name | tmnxTestEvent |
SNMP notification prefix and OID |
TIMETRA-LOG-MIB.tmnxLogNotifications.6 |
Default severity |
indeterminate |
Source stream | main |
Message format string | Test event has been generated with system object identifier $sysObjectID$ System description: $sysDescr$ |
Cause |
The tmnxTestEvent notification is generated when the object tmnxEventTest is set to a value of 'doAction' or the tools>perform>log>test-event CLI command has been entered. This event can be used to test that remote log destinations such as syslog and snmp trap destinations are configured correctly. |
Effect | A tmnxTestEvent is generated. |
Recovery |
If the test event is not received by the log destination, verify that syslog and snmp trap destinations are configured correctly and that the interface link between the system and the remote receiver is up. |