Generated when space contention occurs on the compact flash where
a log or accounting 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 accounting file is denied due to
     lack of space.

A tmnxLogAccountingDataLoss notification is generated
when an accounting file is still being written to
when the next 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.

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.

[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.

Generated when an attempt to create a log or accounting file at the
location specified by tmnxLogFileIdAdminLocation has failed. Indicates
that the backup location, if specified, will be used.

Generated when an attempt to create a log or accounting file at the
location specified by tmnxLogFileIdBackupLoc has failed.

Generated when an event log or accounting policy file's
rollover time has expired.  The file located as indicated
by the value of tmnxLogFileIdOperLocation is closed and a new
file is created as specified by tmnxLogFileIdAdminLocation
and tmnxLogFileIdBackupLoc.

Generated when a closed event log or accounting policy file has been
deleted as part of the space contention cleanup.

The tmnxTestEvent notification is generated when the object
tmnxEventTest is set to a value of 'doAction'.  This event can
be used to test that remote log destinations such as syslog and
snmp trap destinations are configured correctly.

[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.

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.

A tmnxSysLogTargetProblem notification is generated when a problem is
encountered when trying to deliver data to the syslog destination
identified by the tmnxSysLogTargetId.