TIMETRA-LOG-MIB: View SNMP OID List / Download MIB

This document is the SNMP MIB module to manage and provision the Alcatel-Lucent SROS Logging utility. Copyright 2003-2012 Alcatel-Lucent. All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies Alcatel-Lucent's proprietary intellectual property. Alcatel-Lucent retains all title and ownership in the Specification, including any revisions. Alcatel-Lucent grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel-Lucent products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel-Lucent makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

The compliance statement for revision 4.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 5.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 6.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 6.1 of TIMETRA-LOG-MIB.

The compliance statement for revision 7.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 9.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 7.0 of TIMETRA-LOG-MIB.

The compliance statement for revision 10.0 of TIMETRA-LOG-MIB.

The group of objects supporting management of event logging capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting management of accounting policies capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Log File destinations on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Log Syslog destinations on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Log SNMP notification destinations on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Log Events on Alcatel-Lucent SROS series systems release 2.1.

The group of objects supporting management of Log notifications on Alcatel-Lucent SROS series systems.

The group of notifications supporting the Log feature on Alcatel-Lucent SROS series systems release 3.0.

The group of objects supporting management of event logs on Alcatel-Lucent SROS series systems.

The group of objects supporting management of SNMP SET failure error messages.

The group of objects supporting management of Log Events on Alcatel-Lucent SROS series systems release 5.0.

The group of objects supporting management of Log notifications on Alcatel-Lucentx SROS series systems release 5.0.

The group of notifications supporting the Log feature on Alcatel-Lucent SROS series systems release 5.0.

The group of objects supporting management of Log Syslog destinations on Alcatel-Lucent SROS series systems release 5.0.

The group of objects supporting management of Log SNMP notification destinations on Alcatel-Lucent SROS series systems for release 5.0.

The group of objects supporting management of event logs on Alcatel-Lucent SROS series systems in release 5.0.

The group of objects supporting management of TiMOS logs obsoleted on Alcatel-Lucent SROS series systems in release 5.0.

The group of objects supporting management of Log notifications on Alcatel-Lucent SROS series systems release 6.0.

The group of notifications supporting the Log feature on Alcatel-Lucent SROS series systems release 6.0.

The group of objects added to support SNMP trap destinations in the Alcatel-Lucent SROS series systems release 6.0.

The group of objects supporting management of accounting policies capabilities on Alcatel-Lucent SROS series systems release 6.1.

The group of objects supporting the creation of a custom record inside a accounting policy on Alcatel-Lucent SROS series systems.

The group of objects supporting routing preferences of Log Events on Alcatel-Lucent SROS series systems release 7.0.

The group of objects supporting management of Log notifications on Alcatel-Lucent SROS series systems release 8.0.

The group of notifications supporting the Log feature on Alcatel SROS series systems added in release 9.0.

The group of objects supporting damping of change events on Alcatel-Lucent SROS series systems added in release 8.0r7.

The group of objects extending the application log table on Alcatel-Lucent SROS series systems added in release 9.0.

The group of objects managing exec and rollback revert event history.

The group of accessible-for-notify objects added to Alcatel-Lucent SROS series systems release 10.0.

The group of objects extending the accounting policy table on Alcatel-Lucent SROS series systems.

The group of objects supporting notifications on completion of wait time after cold reboot and route recovery on Alcatel-Lucent SROS series systems release 10.0.

The value of tmnxLogFileDeletedLogId indicates with which event log-id or accounting-policy-id the deleted file was associated. Note the corresponding entry in the tmnxLogIdTable or tmnxLogApTable may no longer exist.

The value of tmnxLogFileDeletedFileId indicates with which event log-id or accounting-policy-id the deleted file was associated. Note that the corresponding entry in the tmnxLogFileIdTable may no longer exist.

The value of tmnxLogFileDeletedLogType indicates whether the deleted file was an 'eventLog' or 'accountingPolicy'.

The value of tmnxLogFileDeletedLocation indicates on which compact flash device the event log or accounting policy file that has been deleted was located.

The value of tmnxLogFileDeletedName indicates the pathname of an event log or accounting policy file that has been deleted because of space contention on a compact flash device.

The value of tmnxLogFileDeletedCreateTime indicates the date and time when the deleted file had been created.

The value of tmnxLogTraceErrorTitle indicates the title string of the trace error event that generated the tmnxLogTraceError notification.

The value of tmnxLogTraceErrorSubject indicates the subject string of the trace error event that generated the tmnxLogTraceError notification. The subject is the entity that originated the event, such as the Slot ID.

The value of tmnxLogTraceErrorMessage indicates the message text string of the trace error event that generated the tmnxLogTraceError notification.

tmnxLogThrottledEventID is used by the tmnxLogEventThrottled notification to indicate the NOTIFICATION-TYPE object identifier of the throttled event.

tmnxLogThrottledEvents is used by the tmnxLogEventThrottled notification to indicate the number of events dropped because of event throttling during the last throttle interval.

tmnxSysLogTargetId is used by the tmnxSysLogTargetProblem notification to indicate the involved TmnxSyslogId.

The value of tmnxSysLogTargetProblemDescr indicates the type of error encountered when trying to deliver events to the destination specified in the TmnxSyslogId.

The value of tmnxLogNotifyApInterval indicates how frequently the statistics are collected and written to their destination.

The value of tmnxStdReplayStartEvent indicates the SNMP notification request ID of the first missed event that was replayed when an SNMP notification target address was readded to the RTM following a period when the target address had been removed. It is used by the tmnxStdEventsReplayed notification.

The value of tmnxStdReplayEndEvent indicates the SNMP notification request ID of the last missed event that was replayed when an SNMP notification target address was readded to the RTM following a period when the target address had been removed. It is used by the tmnxStdEventsReplayed notification.

The maximum number of concurrent active Logs that are allowed. A value of zero (0) for this object implies that there is no limit for the number of concurrent active logs in effect.

Defines the Alcatel-Lucent SROS series Log File ID Table for providing, via SNMP, the capability of defining the characteristics for log and billing files and associating them with a file-id. The actual file is not created until the file-id is used in a log or billing file configuration.

Defines an entry in the tmnxLogFileIdTable. Entries are created and deleted in this table by SNMP sets to tmnxLogFileIdRowStatus.

The index value tmnxLogFileId uniquely identifies a file-id to be used when creating a log or billing file.

This object allows entries to be created and deleted in the tmnxLogFileIdTable. Deletion of an entry in this table will not succeed if it is currently used by any log or billing file.

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

The value of tmnxLogFileIdRolloverTime specifies how often, in minutes, a new log or billing file will be created. If the value of tmnxLogFileIdLogType is not 'rollover', then the value of this object is irrelevant.

The value of tmnxLogFileIdRetainTime specifies the minimum time, in hours, that a file is retained on the media. Once this time period has expired the file is deleted.

The value of tmnxLogFileIdAdminLocation specifies where the log or billing file should be created. The file location should be a compact flash on the primary CPM. When the secondary CPM becomes the primary CPM after a failure, the same log file policies will be activated. Thus it is recommended that the same media is available to both secondary and primary CPMs. If no location is specified, 0, the compact flash cf1: is used to store the log files or cf2: is used to store billing files.

The value of tmnxLogFileIdOperLocation specifies where the log or billing file has been created. The file location should be a compact flash on the primary CPM. When the secondary CPM becomes the primary CPM after a failure, the same log file policies will be activated. Thus it is recommended that the same media is available to both secondary and primary CPMs.

The value of tmnxLogFileIdDescription is a user provided description string for this log file-id entry. It can consist of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of tmnxLogFileIdLogType indicates the type of information that will be written to this file.

The value of tmnxLogFileIdLogId indicates the ID index of the log or accounting policy this file is attached to. A value of zero (0) indicates that this file definition is not currently used by any log or accounting policy.

The value of tmnxLogFileIdPathName is the pathname of the currently opened file used by this file-id entry.

The value of tmnxLogFileIdCreateTime is the time the currently opened file version used by this file-id entry was created.

The value of tmnxLogFileIdBackupLoc specifies where the log or billing file should be created if it cannot be created in the location specified by tmnxLogFileIdAdminLocation. The file location should be a compact flash on the primary CPM. When the secondary CPM becomes the primary CPM after a failure, the same log file policies will be activated. Thus it is recommended that the same media is available to both secondary and primary CPMs. If no backup location is specified, 0, and the log or billing file could not be created in the location specified by tmnxLogFileIdAdminLocation or the file creation at the specified backup location fails, a file create failure trap is issued and the associated log or accounting policy is marked as operationally 'outOfService'.

The Alcatel-Lucent SROS series Log Accounting Policy Table contains an entry for each accounting policy that specifies the characteristics of the accounting records associated with an accounting policy.

Defines an entry in the tmnxLogApTable. Entries in the tmnxLogApTable are created and destroyed via SNMP Set requests to tmnxLogApRowStatus.

The value of tmnxLogApPolicyId uniquely identifies an accounting policy to be used for creating accounting records. A specific accounting policy can be applied to one or more service access points (SAPs). Any changes made to an existing policy is applied immediately to all SAPs where this policy is applied.

This object allows entries to be created and deleted in the tmnxLogApTable. Deletion of an entry in this table will not succeed if it is currently applied to any service access point (SAP).

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

The value of tmnxLogApAdminStatus specifies the desired administrative state for this accounting policy.

The value of tmnxLogApOperStatus indicates the current operational status of this accounting policy.

The value of tmnxLogApInterval determines how frequently the statistics are collected and written to their destination. tmnxLogApInterval will have a default value if the value of tmnxLogApDefaultInterval is set to 'true'. Value of tmnxLogApInterval can be set manually if tmnxLogApDefaultInterval is set to 'false'. An attempt to set this object to a non-default value will fail with an inconsistentValue error if tmnxLogApDefaultInterval has the value 'true' set. If no record is specified, default value for tmnxLogApInterval is 5 minutes. For service and network types of record, default values are 5 minutes and 15 minutes respectively. For SAA only, the minimum value of tmnxLogApInterval is 1 minute. Otherwise the minimum value is 5 minutes.

The value of tmnxLogApDescription is a user provided description string for this accounting policy. It can consist of any printable, seven-bit ASCII characters up to 80 characters in length.

When tmnxLogApDefault has a value of 'true', it indicates that this accounting policy is applied to all service access points (SAPs) that do not have an explicit accounting policy applied. If no accounting policy is associated with a SAP accounting records are produced in accordance with the default policy. Only one accounting policy entry in the tmnxLogApTable can have tmnxLogApDefault set to 'true'. If there is no entry in the tmnxLogApTable with tmnxLogApDefault set to 'true', then the only accounting records collected are those explicitly configured accounting policies.

The value of tmnxLogApRecord indicates the type of predefined accounting record type to be written to the accounting file. When tmnxLogApDefaultInterval has a value of 'false', statistics collection interval of the record type will be ignored. The value 'bsxSubscriberAppGroup (22)' was made obsolete in release 7.0 and replaced by 'custom-record-aa (25).' Enumeration: 'combinedAccessEgress': 57, 'svcIngressOctet': 1, 'kpiKciBearerMgmt': 47, 'combinedSvcInEgOctet': 12, 'saa': 32, 'bsxProtocol': 17, 'combinedNetInfIngress': 54, 'netIngressPkt': 7, 'video': 33, 'kpiKciSystem': 49, 'bsxSubscriberProtocol': 20, 'bsxApplication': 18, 'queueGroupPackets': 27, 'kciBearerMgmt': 41, 'queueGroupOctets': 26, 'combinedNetInEgPkt': 61, 'netEgressOctet': 6, 'completeSubscrIngrEgr': 16, 'bsxAppGroup': 19, 'netInfIngressOct': 52, 'combinedSvcEgress': 59, 'accessEgressPkt': 55, 'kciSystem': 40, 'combinedNetInEgOctet': 11, 'kpiSystem': 34, 'netInfIngressPkt': 53, 'kpiKciPathMgmt': 48, 'combinedNetEgress': 58, 'completeSvcSdpInEg': 15, 'kpiRefPathGroup': 46, 'bsxSubscriberAppGroup': 22, 'combinedLdpLspEgress': 31, 'kpiBearerTraffic': 36, 'combinedQueueGroup': 28, 'svcEgressOctet': 2, 'kpiBearerGroup': 45, 'combinedMplsLspEgress': 30, 'combinedSvcSdpInEg': 14, 'compactSvcInOctet': 9, 'completeKci': 44, 'svcEgressPkt': 4, 'bsxSubscriberApplication': 21, 'kciPathMgmt': 42, 'kpiIom3': 39, 'kpiPathMgmt': 38, 'accessEgressOct': 56, 'combinedMplsLspIngress': 29, 'none': 0, 'completeSvcInEg': 13, 'netEgressPkt': 8, 'customRecordService': 24, 'customRecordSubscriber': 23, 'kpiBearerMgmt': 35, 'svcIngressPkt': 3, 'combinedSvcInEgPkt': 60, 'combinedSvcIngress': 10, 'completeKpi': 43, 'kpiRefPoint': 37, 'netIngressOctet': 5, 'completeKpiKci': 50, 'aaPerformance': 51, 'customRecordAa': 25.

The value of tmnxLogApToFileId is the index to the entry in the tmnxLogFileIdTable that specifies the file characteristics to be used for the destination of the accounting policy records collected by this accounting policy. The file itself is created the first time this accounting policy is applied to a service access point (SAP). tmnxLogApToFileId must be set along with tmnxLogApToFileType to indicate whether the records will be stored in a file or not. When a destination file is specified, the value of the file is specified by tmnxLogApToFileId and the value of tmnxLogApToFileType should be 'fileId'. When the destination file is not specified, the value of tmnxLogApToFileId should be zero and the value of tmnxLogApToFileType should be 'noFile'.

The tmnxLogApPortType variable indicates if this accounting policy's record type is to be associated with a service access port, a network access port, a service destination point, a subscriber or the application-assurance feature. Enumeration: 'subscriber': 4, 'none': 0, 'ldpLspEgr': 10, 'sdp': 3, 'network': 2, 'appAssure': 5, 'mplsLspIngr': 8, 'saa': 7, 'mplsLspEgr': 9, 'networkIf': 13, 'access': 1, 'mobileGateway': 12, 'video': 11, 'accessport': 14, 'qgrp': 6.

When tmnxLogApDefaultInterval has a value of 'true', it indicates that tmnxLogApInterval will have a default value. When tmnxLogApDefaultInterval has a value of 'false', user can set the value of tmnxLogApInterval manually.

The value of tmnxLogApDataLossCount indicates the number of times a tmnxLogAccountingDataLoss trap was raised against this application policy.

The value of tmnxLogApLastDataLossTimeStamp indicates the last time, since system startup that a tmnxLogAccountingDataLoss trap was raised against this application policy.

The value of tmnxLogApToFileType indicates where records of an accounting policy are stored. It should be set along with tmnxLogApToFileId which specifies the destination file index where the accounting records are stored. When the value of tmnxLogApToFileType is 'noFile', it indicates that the accounting records will not to be stored in a file and the value of tmnxLogApToFileId should be set to zero. When the value of tmnxLogApToFileType is 'fileId', it indicates that the accounting records will be stored in a file specified by tmnxLogApToFileId. tmnxLogApOperStatus will transition to 'inService' when the tmnxLogApToFileType is set to 'noFile' or 'fileId'. Enumeration: 'noFile': 1, 'fileId': 0.

The Alcatel-Lucent SROS series Log Identification Table contains an entry for each log that specifies the characteristics of that log associated with a log-id number.

Defines an entry in the tmnxLogIdTable. Entries in the tmnxLogIdTable are created and destroyed via SNMP Set requests to tmnxLogIdRowStatus. Default log entries 99 and 100 are created by the agent.

The value of tmnxLogIdIndex uniquely identifies an event stream log.

This object allows entries to be created and deleted in the tmnxLogIdTable. Deletion of an entry in this table will not succeed if tmnxLogIdOperStatus is not 'outOfService'. tmnxLogIdOperStatus will not transition to 'inService' if tmnxLogIdSource and tmnxLogIdDestination and their associated objects have not been set to valid values.

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

The value of tmnxLogIdAdminStatus indicates the desired administrative state for this log.

The value of tmnxLogIdOperStatus indicates the current operational status of this log.

The value of tmnxLogIdDescription is a user provided description string for this log. It can consist of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of tmnxLogIdFilterId is the index into the tmnxLogFilterTable to the entry the defines a filter to be applied to this log's source event stream to limit the events output to this log's destination. If tmnxLogIdFilterId has a value of 0, then all events in the source log are forwarded to the destination.

The value of tmnxLogIdSource is a bit mask that specifies the log event source stream(s) to be forwarded to the destination specified in tmnxLogIdDestination. Events from more than one source may be forwarded to the log destination. The 'main' event stream consists of all events that are not explicitly directed to any other event stream. The 'security' event stream contains all events that affect attempts to breach system security such as failed login attempts, attempts to access SNMP MIB tables to which the user has not been granted access, or attempts to enter a branch of the CLI for which the user is not authorized. The 'user' activity event stream contains all events that directly affect the configuration or operation of the system. The 'debugTrace' event stream contains all events configured for application or protocol tracing. The 'li' event stream contains all events configured for Lawful Intercept activities. An attempt to set the 'li' event stream will fail with an inconsistentValue error if the requestor does not have access to the 'li' context. An attempt to set the 'li' event stream will fail with an inconsistentValue error if tmnxLogIdDestination has the value 'syslog' or 'file'. Bits: 'security': 1, 'main': 0, 'debugTrace': 3, 'change': 2, 'li': 4.

The value of tmnxLogIdDestination specifies the event log stream destination. Once this object has been set to a value other than the default 'none' it cannot be modified and attempts to reset it to another value will fail with an INCONSISTENT VALUE error. The 'console' destination causes all selected log events to be directed to the system console. If the console is not connected then all entries are dropped. The 'syslog' destination sends all selected log events to the syslog address configured in tmnxSyslogTargetAddress and tmnxSyslogTargetUdpPort in the tmnxSyslogTargetTable row entry pointed to by the value of tmnxLogIdSyslogId. An attempt to set this object ot 'syslog' will fail with an inconsistentValue error if tmnxLogIdSource has the value 'li' set. The 'snmpTraps' destination causes events defined as SNMP traps to be sent to the configured SNMP trap destinations and also to be logged in the NOTIFICATION-LOG-MIB tables. The allocated memory size for the log of transmitted traps is specified in tmnxLogIdMaxMemorySize. The events are logged to memory in a circular fashion. Once the space is full, the oldest entry is replaced with a new entry. The 'file' destination causes all selected log events to be directed to a file on one of the CPM's compact flash discs. Details of the file's configuration are in the tmnxLogFileIdTable entry pointed to by the value of tmnxLogIdFileId. An attempt to set this object ot 'file' will fail with an inconsistentValue error if tmnxLogIdSource has the value 'li' set. The 'memory' destination causes all selected log events to be directed to an in memory storage area. The allocated memory size for the log is specified in tmnxLogIdMaxMemorySize. The events are logged to memory in a circular fashion. Once the space is full, the oldest entry is replaced with a new entry. Enumeration: 'none': 0, 'console': 1, 'snmpTraps': 3, 'syslog': 2, 'file': 4, 'memory': 5.

The value of tmnxLogIdFileId is the index to the entry in the tmnxLogFileIdTable that specifies the file characteristics to be used for the destination of the log events written to this log. tmnxLogIdOperStatus will not transition to 'inService' until a valid value has been set for tmnxLogIdFileId. This object is valid only if tmnxLogIdDestination is set to 'file'.

The value of tmnxLogIdSyslogId is the index into the tmnxSyslogTargetTable for the row entry with the information to format event messages to be sent to a specific syslog collector target. This object is valid only when tmnxLogIdDestination has a value of 'syslog'. If this object has a value of zero (0), then no collector is specified and no messages are sent.

The value of tmnxLogIdMaxMemorySize specifies the amount of memory to allocate for this log. This object is valid only when tmnxLogIdDestination has a value of 'memory' or 'snmpTraps'. If the value tmnxLogIdDestination is neither 'memory' nor 'snmpTraps' a read of this object will return zero (0). Once a memory size has been specified and the log created, any attempt to modify this object will fail with an INCONSISTENT VALUE error.

This object exists for the convenience of the Alcatel-Lucent SROS CLI. When set to 'true' it indicates that the 'CONSOLE' log output should be printed to the Telnet session instead of the CONSOLE device. When a tmnxLogIdEntry is created directly via SNMP, setting this object has no meaning and the 'CONSOLE' log output will always be sent to the CONSOLE device.

The value of tmnxLogIdForwarded is the count of the number of events that have been forwarded to this log's destination. This counter is incremented after an event has been selected by the log filter defined in tmnxLogIdFilterId.

The value of tmnxLogIdDropped is the count of the number of events that have been sent to this logs source(s) and that have not been forwarded to the log destination because they were filtered out by the log filter defined in tmnxLogIdFilterId.

The value of tmnxLogIdTimeFormat specifies the type of timestamp format for events sent to logs where tmnxLogIdDestination has a value of either 'syslog (2)' or 'file (4)'. When tmnxLogIdTimeFormat has a value of 'utc (1)' timestamps are written using the Coordinated Universal Time value. When tmnxLogIdTimeFormat has a value of 'local (2)' timestamps are written in the system's local time. Enumeration: 'utc': 1, 'local': 2.

Information about a particular Log Filter entry. Entries are created by user. Entries are deleted by user. Entry 1001 is created by the agent for default TmnxLogIdIndex 100. There is no StorageType object. Entries have a presumed StorageType of nonVolatile.

The value of tmnxLogFilterId is a unique index that identifies a particular entry in the tmnxLogFilterTable.

Row entries in this table are created and destroyed via SNMP set requests.

The value of tmnxLogFilterDescription is a user provided description string for this log filter. It can consist of any printable, seven-bit ASCII characters up to 80 characters in length.

The action to take for packets that do not match any filter entries. the values default(3), and nat(5) are not allowed.

When tmnxLogFilterInUse has a value of 'true', this filter is attached to a log file configuration. The same tmnxLogFilterEntry can be attached to more than one log file.

A table of all log filter match entries for all log filters.

Information about a particular Log Filter Parameter entry. Every Log Filter can have zero or more Log Filter Parameter match entries. The Log Filter parameter entries are checked in ascending order by their index value, tmnxLogFilterParamsIndex. Upon the first successful match, the specified actions are applied as indicated by the value of tmnxLogFilterParamsAction. No further checking against remaining tmnxLogFilterParamsEntry rows is done. Therefore, entries in this table should be sequenced from most to least explicit match criterion. It is recommended that multiple parameter entries for a log filter should be created with gaps between their index values. This allows a new entry to be inserted into an existing filter policy without needing to renumber the already existing filter parameters entries. A log filter entry in the tmnxLogFilterTable with no entry in the tmnxLogFilterParamsTable to define its match criteria set will match every log event, and the default action specified by tmnxLogFilterDefaultAction will be taken. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

Row Status for this Log filter's parameter entry.

The value of tmnxLogFilterParamsDescription is a user provided description string for this log filter match entry. It can consist of any printable, seven-bit ASCII characters up to 80 characters in length.

the action to take for log events that match this filter entry. the value default(3) is allowed. If tmnxLogFilterParamsAction has the value 'default', the action specified by the value of tmnxLogFilterDefaultAction is applied to events that match this filter entry. The value nat(5) is not allowed.

Matches log events with the specified application name. An application is the software entity the reports the log event and includes IP, MPLS, OSPF, CLI, SERVICES, etc.

The value of tmnxLogFilterParamsApplOperator is the comparison operator to use to determine if the log event matches the value of tmnxLogFilterParamsApplication. The only valid values from TmnxLogFilterOperator are 'off', 'equal', and 'notEqual'.

The value of tmnxLogFilterParamsNumber is the log event number to be matched. Event numbers uniquely identify a certain event within an application but not across applications.

The value of tmnxLogFilterParamsNumberOperator is the comparison operator to use to determine if the log event matches the value of tmnxLogFilterParamsNumber.

The value of tmnxLogFilterParamsSeverity is the log event severity level to be matched.

The value of tmnxLogFilterParamsSeverityOperator is the comparison operator to use to determine if the log event matches the value of tmnxLogFilterParamsSeverity.

The value of tmnxLogFilterParamsSubject is the log event subject string to be matched. The subject is the entity that the event is reported for, such as a port ID.

The value of tmnxLogFilterParamsSubjectOperator is the comparison operator to use to determine if the log event matches the value of tmnxLogFilterParamsSubject. The only valid values of TmnxLogFilterOperator to use for the subject string comparison are 'off', 'equal', and 'notEqual'.

The value of tmnxLogFilterParamsSubjectRegexp specifies the type of string comparison to use to determine if the log event matches the value of tmnxLogFilterParamsSubject. When the value of tmnxLogFilterParamsSubjectRegexp is 'true', the string in tmnxLogFilterParamsSubject is a regular expression string to be matched against the subject string in the log event being filtered. When it has a value of 'false', the string in tmnxLogFilterParamsSubject is matched exactly by the event filter.

The value of tmnxLogFilterParamsRouter is the log event router context name string to be matched.

The value of tmnxLogFilterParamsRouterOperator is the comparison operator to use to determine if the log event matches the value of tmnxLogFilterParamsRouter. The only valid values of TmnxLogFilterOperator to use for the router name string comparison are 'off', 'equal', and 'notEqual'.

The value of tmnxLogFilterParamsRouterRegexp specifies the type of string comparison to use to determine if the log event matches the value of tmnxLogFilterParamsRouter. When the value of tmnxLogFilterParamsRouterRegexp is 'true', the string in tmnxLogFilterParamsRouter is a regular expression string to be matched against the router name string in the log event being filtered. When it has a value of 'false', the string in tmnxLogFilterParamsRouter is matched exactly by the event filter.

A table of all remote syslog collectors that this agent is configured to send syslog messages to.

Information about a particular Syslog Target entry. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

The value of tmnxSyslogTargetIndex is a unique arbitrary identifier for this syslog collector target.

The tmnxSyslogTargetRowStatus object allows for dynamic creation and deletion of row entries in the tmnxSyslogTargetTable as well as the activation and deactivation of these entries. When this object's value is set to 'notInService (2)', no messages will be sent to this target collector and none of its counters will be incremented. Refer to the RowStatus convention for further details on the behavior of this object.

The value of tmnxSyslogTargetDescription is an administratively assigned textual description of this syslog collector target.

The value of tmnxSyslogTargetAddress is the IPv4 address for this syslog message collector target. If the value of this object is '0.0.0.0', then no messages will be sent, nor will any counters be incremented. This object was made obsolete in release 5.0. It is replaced by the InetAddress pair tmnxSyslogTargetAddrType and tmnxSyslogTargetAddr.

The value of tmnxSyslogTargetUdpPort is the UDP port number that is used to send messages to this syslog collector target.

The value of tmnxSyslogTargetFacility is the syslog facility number that will be encoded in messages sent to this syslog collector target.

The value of tmnxSyslogTargetSeverity is the maximum severity level of the messages that SHOULD be forwarded to this syslog collector target. The higher the level, the lower the severity.

The value of tmnxSyslogTargetMessagePrefix is a string of ABNF alphanumeric characters to be prepended as the MSG TAG to the syslog MSG CONTENT string and separated from it with a colon and space, ': '.

The value of tmnxSyslogTargetMessagesDropped is a count of messages not sent to this syslog collector target because the severity level of the message was above tmnxSyslogTargetSeverity; the higher the level, the lower the severity.

The value of tmnxSyslogTargetAddrType specifies the type of host address to be used for the syslog message collector target. This object indicates the type of address stored in the corresponding tmnxSyslogTargetAddr object. Only 'ipv4', 'ipv6', and 'ipv6z' address types are supported.

The value of tmnxSyslogTargetAddr specifies the IP host address to be used for the syslog message collector target. If no address is specified, ''H, then no messages will be sent nor will any counters be incremented. The syslog target address type is determined by the value of the corresponding tmnxSyslogTargetAddrType object.

A table of all applications that generate TiMOS logger events.

Information about a particular application entry. Entries are created by the agent when the system initializes. There is no StorageType object, entries have a presumed StorageType of permanent.

The value of tmnxEventAppIndex is a unique arbitrary identifier for this application event generator.

The value of tmnxEventAppName is the name string that is used in TiMOS log messages as the application that generated the logged event.

A table of all TiMOS events that can be generated.

Information about a particular TiMOS event type entry. Entries are created by the agent when the system initializes. There is no StorageType object, entries have a presumed StorageType of permanent.

The value of tmnxEventID is a unique arbitrary identifier for indexing event type entries within an event generator application as identified by the value of tmnxEventAppIndex.

The value of tmnxEventName is a short name string used to describe this event type.

The value of tmnxEventSeverity indicates the severity level that will be associated with this type of event when it is generated.

The value of tmnxEventControl determines whether or not events of this type will be generated or suppressed. When it has a value of 'true', the event is generated and tmnxEventCounter is incremented. When it has a value of 'false', the event is suppressed and tmnxEventDropCount is incremented.

The value of tmnxEventCounter is the number of times an event of this type has been generated.

The value of tmnxEventDropCount is the number of times and event of this type has been suppressed because tmnxEventControl is set to 'false'. When tmnxEventControl is set to 'true', tmnxEventDropCount indicates the number of events dropped because of logger input queue size overrun or dropped because of throttling when tmnxEventThrottle is set to 'true'.

Setting tmnxEventReset to 'doAction (1)' causes the agent to reset the values of tmnxEventSeverity and tmnxEventControl to the default values for this event type.

The value of tmnxEventThrottle determines whether or not events of this type will be throttled. When it has a value of 'true', the event is throttled at the rate indicated by the value of tmnxEventThrottleLimit and tmnxEventThrottleInterval. When it has a value of 'false', no event throttling is applied.

A table of all remote SNMP trap collectors to which this agent is configured to send SNMP notifications messages. This table was made obsolete in the 5.0 release and is replace with tmnxSnmpTrapDestTable.

Information about a particular SNMP trap destination entry. The first index instance creates and snmp trap group to be associated with the event log with the same value for tmnxLogIdIndex. The second and third indexes specify a remote SNMP trap destination that will be sent SNMP notification messages from the associated event log. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile. This table was made obsolete in the 5.0 release and is replaced with the tmnxSnmpTrapDestTable.

The value of tmnxStgIndex specifies an snmp trap group to be associated with the event log with the same value for tmnxLogIdIndex. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdIndex.

The value of tmnxStgDestAddress is the IPv4 address for this remote snmp notification destination. If the value of this object is '0.0.0.0', then no messages will be sent, nor will any counters be incremented. This object was made obsolete in the 5.0 release. It is replaced by the InetAddressType/InetAddress objects tmnxStdDestAddrType and tmnxStdDestAddr.

The value of tmnxStgDestPort is the UDP port number that is used to send messages to this remote SNMP notification destination. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdDestPort.

The tmnxStgRowStatus object allows for dynamic creation and deletion of row entries in the tmnxSnmpTrapGroupTable as well as the activation and deactivation of these entries. When this object's value is set to 'notInService (2)', no messages will be sent to this snmp trap group and none of its counters will be incremented. Refer to the RowStatus convention for further details on the behavior of this object. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdRowStatus.

The value of tmnxStgDescription is an administratively assigned textual description of this snmp trap destination. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdDescription.

The value of tmnxStgVersion specifies the SNMP version that will be used to format notification messages sent to this snmp trap destination. The values supported by the Alcatel-Lucent SROS series SNMP agent are: 0 for SNMPv1 1 for SNMPv2c 3 for SNMPv3 This object was made obsolete in the 5.0 release. It is replaced by tmnxStdVersion.

The value of tmnxStgNotifyCommunity specifies the SNMPv1 or SNMPv2c community name string or the SNMPv3 security name used when an SNMP notification message is sent to this trap destination. If the value of this object is the empty string, then no messages will be sent nor will any counters be incremented. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdVersion.

The value of tmnxStgSecurityLevel specifies the level of security at which SNMP notification messages will be sent to the SNMP trap destination when tmnxStgVersion has a value of '3' for SNMPv3. This object was made obsolete in the 5.0 release. It is replaced by tmnxStdSecurityLevel.

Setting tmnxEventTest to 'doAction' causes the tmnxTestEvent notification to be generated.

The value of tmnxEventThrottleLimit specifies the number of log events that can be logged within the tmnxEventThrottleInterval for a specific entry in the tmnxEventTable. Once the limit has been reached, any additional events of that type will be dropped, i.e. tmnxEventDropCount will be incremented. At the end of the throttle interval if any events have been dropped a tmnxLogEventThrottled notification will be sent.

The value of tmnxEventThrottleInterval specifies the number of seconds that an event throttling interval lasts.

The value of tmnxSnmpSetErrsMax indicates the maximum number of entries the agent will create in the tmnxSnmpSetErrsTable. Once the table is full the agent will delete the oldest entry in the table in order to add new entries.

A table of recent SNMP SET failures. Only the SET errs from remote SNMP manager requests are saved in this table. Only SET errs detected by the SNMP engine in the test phase consistency check method functions are saved. SET errors that are caught by the preliminary access and ASN.1 decoding phase are not saved. These are errs such as noAccess, notWritable, wrongType, wrongLength and wrongEncoding. Note that notWritable, wrongType, and wrongLength errs may sometimes be generated by the consistency check; in this case they will be saved in this table. SET errs caused by local CLI sessions are not saved. The tmnxSnmpSetErrsTable is intended to provide an aide to Network Management Systems (NMS) developers. When an SNMP SET fails during the consistency checking test phase, this table may provide more detailed failure reason information than the simple SNMP error code value in the SNMP response PDU.

Information about a particular SNMP SET error. The first two index instances identify the SNMP manager who sent the SNMP SET request that failed. The third index specifies the SNMP request-id (sequence number) of the SNMP SET request that failed. Entries are created by the agent. Entries are deleted by the agent. There is no StorageType object, entries have a presumed StorageType of volatile.

The value of tmnxSseAddressType indicates the IP address type of address specified in tmnxSseAddress. 'ipv4' and 'ipv6' are the only address type values supported.

The value of tmnxSseAddress is the IP address of the SNMP manager that sent the SNMP SET request that failed for this error reason.

The value of tmnxSseSnmpPort is the UDP port number of the SNMP manager that sent the SNMP SET request that failed for this error reason.

The value of tmnxSseRequestId indicates the request-id of the SNMP SNMP SET request that failed for this error reason.

The value of tmnxSseVersion indicates the SNMP version of the SNMP SET request that failed. The values supported by the Alcatel-Lucent SROS series SNMP agent are: 0 for SNMPv1 1 for SNMPv2c 3 for SNMPv3

The value of tmnxSseSeverityLevel indicates severity level that is associated with this type SNMP SET error.

The value of tmnxSseModuleId indicates a unique arbitrary identified for the TiMOS application module that generated this SNMP SET error. NOTE: This is NOT the same value used for tmnxEventAppIndex.

The value of tmnxSseModuleName indicates the name string of the TiMOS application module that generated this SNMP SET error. NOTE: This is NOT the same value used for tmnxEventAppName.

The value of tmnxSseErrorCode indicates the error number associated with this SNMP SET error. The error numbers are unique within a tmnxSseModuleId. They are not unique across all modules so both the module name and error number are required to identify a particular error message.

The value of tmnxSseErrorName indicates the error name associated with this SNMP SET error. The error names are unique within a tmnxSseModuleId. They are not unique across all modules so both the module name and error name are required to identify a particular error message.

The value of tmnxSseErrorMsg indicates the fixed error message text associated with this SNMP SET error identified by the values of tmnxSseModuleId and tmnxSseErrorCode.

The value of tmnxSseExtraText indicates the fixed run-time variable message text associated with this SNMP SET error identified by the values of tmnxSseModuleId and tmnxSseErrorCode. If the extra text was truncated to fit into buffer size allowed, the last character will be an asterix (*).

The value of tmnxSseTimestamp indicates the sysUpTime value when this tmnxSnmpSetErrsEntry was created by the agent.

A table of all remote SNMP trap logs to which this agent is configured to send SNMP notifications messages.

Each row entry in the tmnxSnmpTrapLogTable represents additional columns for attributes specific to the Alcatel-Lucent SROS series implementation of SNMP-NOTIFICATION-MIB::snmpNotifyTable.

The value of tmnxSnmpTrapLogDescription is an administratively assigned textual description of this snmp trap log.

A table of all remote SNMP IPv4/v6 trap collectors to which this agent is configured to send SNMP notification messages.

Information about a particular SNMP notification destination entry. The first index instance creates an snmp notification group to be associated with the event log with the same value for tmnxLogIdIndex. The second index specifies an administrative name to identify a specific SNMP notification target. Entries are created by user. Entries are deleted by user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

The value of tmnxStdIndex specifies an snmp notification group to be associated with the event log with the same value for tmnxLogIdIndex.

The value of tmnxStdName specifies the name of an snmp notification destination within the snmp notification group specified by tmnxLogIdIndex.

The tmnxStdRowStatus object allows for dynamic creation and deletion of row entries in the tmnxSnmpTrapDestTable as well as the activation and deactivation of these entries. In order for 'createAndGo' row creation to succeed or status to transition to 'active' a value must be set for tmnxStdNotifyCommunity. In order for 'createAndGo' row creation to succeed or status to transition to 'active' an entry must exist in the SNMP-NOTIFICATION-MIB::snmpNotifyTable with an snmpNotifyName index that is the ASCII string representation of the value of tmnxStdIndex. When this object's value is set to 'notInService (2)', no messages will be sent to this snmp notification collector and none of its counters will be incremented. Refer to the RowStatus convention for further details on the behavior of this object.

The value of tmnxStdRowLastChanged indicates the sysUpTime when the value of a writable object in this row entry was modified.

The value of tmnxStdDestAddrType specifies the type of host address to be used for the remote SNMP notification collector. This object indicates the type of address stored in the corresponding tmnxStdDestAddr object. If the value of this object is 'unknown', then no messages will be sent nor will any counters be incremented. If tmnxStdDestAddrType is not set in the same PDU with tmnxStdDestAddr, the set request will fail with an inconsistentValue error.

The value of tmnxStdDestAddr specifies the IP host address to be used for the remote SNMP notification collector. The SNMP notification collector IP address type is determined by the value of the corresponding tmnxStdDestAddrType object. If the value of this object is empty or all NULLs, then no messages will be sent nor will any counters be incremented. If tmnxStdDestAddrType is not set in the same PDU with tmnxStdDestAddr, the set request will fail with an inconsistentValue error.

The value of tmnxStdDestPort is the UDP port number that is used to send messages to this remote SNMP notification collector.

The value of tmnxStdDescription is an administratively assigned textual description of this SNMP notification collector.

The value of tmnxStdVersion specifies the SNMP version that will be used to format notification messages sent to this SNMP notification collector. The values supported by the Alcatel-Lucent SROS series SNMP agent are: 0 for SNMPv1 1 for SNMPv2c 3 for SNMPv3

The value of tmnxStdNotifyCommunity specifies the SNMPv1 or SNMPv2c community name string or the SNMPv3 security name used when an SNMP notification message is sent to this SNMP notification collector. If the value of this object is the empty string, then no messages will be sent nor will any counters be incremented.

The value of tmnxStdSecurityLevel specifies the level of security at which SNMP notification messages will be sent to the SNMP notification collector when tmnxStdVersion has a value of '3' for SNMPv3.

The value of tmnxStdReplay specifies whether or not to resend notifications that were generated while this notification destination did not have a route installed for it in the route tables.

The value of tmnxStdReplayStart indicates the SNMP notification request ID of the first event that cound not be generated because there is no route to this notification target address. Events will be resent when this notification target address is readded to the route tables, on either an in-band or out-of-band interface. The agent searches backwards in the event log and begins resending events from the oldest event that has a timestamp <= 5 hundredths of a second less than the timestamp of the event with this request ID. Note that if the outage is long and a large number of events are generated in the meantime, it is possible that the log memory storage has wrapped and the event data for this request ID is no longer available. In that case, the oldest event saved in the log will be the first event resent. A value of 0 indicates that there are no missed events waiting to be resent.

The value of tmnxStdReplayLastTime indicates the sysUpTime when missed events were last replayed to this SNMP notification target address. A value of 0 indicates that no missed events have been replayed to this SNMP notification target address.

The maximum number of tmnxSnmpTrapDestTable row entries that can be created for a specific tmnxStdIndex that represents an snmp notification group.

The Alcatel-Lucent SROS series tmnxLogApCustRecordTable augments tmnxLogApTable. The table allows to configure the layout and setting for a custom accounting record associated with this accounting policy.

Defines an entry in the tmnxLogApCustRecordTable. Entries in this table are created and destroyed via SNMP Set requests to the tmnxLogApRowStatus object of the tmnxLogApTable.

The value of tmnxLogApCrLastChanged indicates the sysUpTime when an object in this table was last modified. A Value 0 means that no change was made to this row since the box was last initialized.

The value of tmnxLogApCrSignChangeDelta specifies the delta change (significant change) that is required for the custom record to be written to the xml file.

The value of tmnxLogApCrSignChangeQueue specifies the reference queue to which the significant change defined in tmnxLogApCrSignChangeDelta applies.

The value of tmnxLogApCrSignChangeOCntr specifies the counter-id that will be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies.

The value of tmnxLogApCrSignChangeQICounters specifies the ingress counter Ids in the queue defined by tmnxLogApCrSignChangeQueue to be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies. A non-zero value of this object is only allowed if the object tmnxLogApCrSignChangeQueue has a non-zero value.

The value of tmnxLogApCrSignChangeQECounters specifies the egress counter Ids in the queue defined by tmnxLogApCrSignChangeQueue to be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies. A non-zero value of this object is only allowed if the object tmnxLogApCrSignChangeQueue has a non-zero value.

The value of tmnxLogApCrSignChangeOICounters specifies the ingress counter Ids in the counter-group defined by tmnxLogApCrSignChangeOCntr to be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies. A non-zero value of this object is only allowed if the object tmnxLogApCrSignChangeOCntr has a non-zero value.

The value of tmnxLogApCrSignChangeOECounters specifies the egress counter Ids in the counter-group defined by tmnxLogApCrSignChangeOCntr to be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies. A non-zero value of this object is only allowed if the object tmnxLogApCrSignChangeOCntr has a non-zero value.

The value of tmnxLogApCrSignChangeAACounters specifies the AA (Application assurance) counter Ids to be taken as reference to which the significant change defined in tmnxLogApCrSignChangeDelta applies. A non-zero value of this object is only allowed if both the objects tmnxLogApCrSignChangeOCntr and tmnxLogApCrSignChangeQueue are zero. Also, a non-zero value for this object is only allowed if the object tmnxLogApCrSignChangeDelta is either 0 or 1.

The value of tmnxLogApCrQueueECounters indicates the list of AA (application Assurance) counters that need to be collected in this custom record.

The Alcatel-Lucent SROS series tmnxLogApCustRecordQueueTable allows to create custom record queue information for a given accounting policy. Rows can only be created for existing accounting policies (as defined in tmnxLogApTable).

Defines an entry in the tmnxLogApCustRecordQueueTable. Entries in this table are created and destroyed via SNMP Set requests.

The value of tmnxLogApCrQueueId specifies the queue-id for which counters will be collected in this custom record. The counters that will be collected are defined in tmnxLogApCrQueueICounters and tmnxLogApCrQueueECounters.

Row Status of the entry. This allows creation/deletion of rows in this table.

The value of tmnxLogApCrQueueLastChanged indicates the sysUpTime when an object in this table was last modified. A Value 0 means that no change was made to this row since it was created.

The value of tmnxLogApCrQueueICounters indicates the list of ingress counters that need to be collected in this custom record. At least one of the objects tmnxLogApCrQueueICounters or tmnxLogApCrQueueECounters must have a non-zero value.

The value of tmnxLogApCrQueueECounters indicates the list of egress counters that need to be collected in this custom record. At least one of the objects tmnxLogApCrQueueICounters or tmnxLogApCrQueueECounters must have a non-zero value.

The Alcatel-Lucent SROS series tmnxLogApCrOverrideCntrTable allows to create custom record counter override information for a given accounting policy. Rows can only be created for existing accounting policies (as defined in tmnxLogApTable).

Defines an entry in the tmnxLogApCrOverrideCntrTable. Entries in this table are created and destroyed via SNMP Set requests.

The value of tmnxLogApCrOverrideCntrId specifies the counter group for which counters will be collected in this custom record. The counters that will be collected are defined in tmnxLogApCrOverrideCntrICounters and tmnxLogApCrOverrideCntrECounters.

Row Status of the entry. This allows creation/deletion of rows in this table.

The value of tmnxLogApCrOverrideCntrLastChngd indicates the sysUpTime when an object in this table was last modified. A Value 0 means that no change was made to this row since it was created.

The value of tmnxLogApCrOverrideCntrICounters indicates the list of ingress counters that need to be collected in this custom record. At least one of the objects tmnxLogApCrOverrideCntrICounters or tmnxLogApCrOverrideCntrECounters must have a non-zero value.

The value of tmnxLogApCrOverrideCntrECounters indicates the list of egress counters that need to be collected in this custom record. At least one of the objects tmnxLogApCrOverrideCntrICounters or tmnxLogApCrOverrideCntrECounters must have a non-zero value.

The value of tmnxEventPrimaryRoutePref specifies the primary routing preference for traffic generated for SNMP notifications and syslog messages. A value of 'inband' specifies that the Logging utility will attempt to use the Base routing context to send SNMP notifications and syslog messages to remote destinations. A value of 'outband' specifies that the Logging utility will attempt to use the management routing context to send SNMP notifications and syslog messages to remote destinations. If the remote destination, as specified by tmnxStdDestAddr or tmnxSyslogTargetAddr, is not reachable via the routing context specified by tmnxEventPrimaryRoutePref, the secondary routing preference as specified by tmnxEventSecondaryRoutePref will be attempted. Enumeration: 'outband': 2, 'inband': 1.

The value of tmnxEventSecondaryRoutePref specifies the secondary routing preference for traffic generated for SNMP notifications and syslog messages. The routing context specified by the tmnxEventSecondaryRoutePref will be attempted if the remote destination was not reachable by the primary routing preference, specified by tmnxEventPrimaryRoutePref. The value specified for tmnxEventSecondaryRoutePref must be distinct from the value for tmnxEventPrimaryRoutePref. A value of 'inband' specifies that the Logging utility will attempt to use the Base routing context to send SNMP notifications and syslog messages to remote destinations. A value of 'outband' specifies that the Logging utility will attempt to use the management routing context to send SNMP notifications and syslog messages to remote destinations. A value of 'none' specifies that no attempt will be made to send SNMP notifications and syslog messages to remote destinations. If the remote destination, as specified by tmnxStdDestAddr or tmnxSyslogTargetAddr, is not reachable via the routing contexts specified by tmnxEventPrimaryRoutePref and tmnxEventSecondaryRoutePref, the Log utility will fail to send SNMP notifications and syslog messages to the remote destination. Enumeration: 'none': 3, 'outband': 2, 'inband': 1.

The value of tmnxLogConfigEventsDamped specifies whether or not the module generating tmnxConfigCreate, tmnxConfigDelete, and tmnxConfigModify events applies a damping algorithm. WARNING: While this event damping is original behavior for some modules such as service manager, QoS, and filters it can result in the NMS system database being out of sync because of missed change events. On the other hand, if the damping is disabled, 'false', it may take much longer for a large CLI configuration file to be processed when manually 'execed' after system bootup.

The value of the object tmnxLogExRbkOpTblLastChange indicates the value of sysUpTime at the time of the last modification of a row entry in the tmnxLogExecRollbackOpTable.

The value of the object tmnxLogExRbkOpMaxEntries specifies the maximum number of row entries supported in the tmnxLogExecRollbackOpTable.

The Alcatel-Lucent SROS series tmnxLogExecRollbackOpTable provides a history of up to the last number of 'exec' or rollback revert operations specified by the value of tmnxLogExRbkOpMaxEntries. The tmnxLogExecRollbackOpTable is intended to provide an aide to Network Management Systems (NMS). The 'exec' of a large configuration file via the system's CLI or a large rollback revert operation will generate so many configuration change and other events in a short time that neither the SROS's event logging utility no the NMS can keep up with them. This results in either or both the SROS and NMS dropping events and requires the NMS to perform a costly resynchronization of its management database.

Defines a row entry in the tmnxLogExecRollbackOpTable. Entries in this table are created and deleted by the agent.

The value of tmnxLogExRbkOpIndex is a unique value that indicates an instance of an exec or rollback revert operation. Only the most recent instances are kept in this table. The maximum number of row entries supported in this table is specified by the value of tmnxLogExRbkOpMaxEntries.

The value of tmnxLogExRbkOpLastChanged indicates the sysUpTime when an object in this table was last modified. A Value 0 means that no change was made to this row since it was created.

The value of tmnxLogExRbkOpType indicates the type of operation this row entry represents. Enumeration: 'unknown': 0, 'rollback': 2, 'exec': 1.

The value of tmnxLogExRbkOpStatus indicates the status of this exec or rollback revert operation. Enumeration: 'unknown': 0, 'inProgress': 1, 'success': 2, 'failed': 3.

The value of tmnxLogExRbkOpBegin indicates the sysUpTime when the exec or rollback revert operation began.

The value of tmnxLogExRbkOpEnd indicates the sysUpTime when the exec or rollback revert operation ended. A value of zero (0) means that the operation has not completed.

The value of tmnxLogExRbkOpFile indicates the location and name of the file used for the exec or rollback revert operation.

The value of tmnxLogExRbkOpUser indicates the user who initiated the exec or rollback revert operation.

The value of tmnxLogExRbkOpNumEvents indicates the number of row entries in the associated tmnxLogExecRollbackEventTable for this exec or rollback revert operation. It is updated only when the exec or rollback revert operation ends. A value of zero (0) means that the operation has not completed.

The Alcatel-Lucent SROS series tmnxLogExecRollbackEventTable provides a history of mib tables modified or specific events generated during an exec or rollback revert operation.

Defines a row entry in the tmnxLogExecRollbackEventTable. Each row entry represents either an SNMP table that has been modified or a specific event generated during an exec or rollback revert operation. Entries in this table are created and deleted by the agent.

The value of tmnxLogExRbkEventIndex is a unique value that indicates an instance of an event generated during an exec or rollback revert operation.

The value of tmnxLogExRbkEventOID indicates the object identifier of either a mib table for which a generic change event was generated or the notification object identifier of a specific event notification generated during the the exec or rollback revert operation. The generic change events are tmnxConfigCreate, tmnxConfigDelete, tmnxConfigModify, and tmnxStateChange notifications. For these event types, the value of tmnxLogExRbkEventOID is the object identifier specified by the tmnxNotifyEntryOID varbind. For specific events generated during an exec or rollback revert, the value of this object is the notification object identifier itself. An object identifier will appear only once in this table.

The value of tmnxLogExecRollbackOpIndex is a unique value that indicates a row entry instance of an exec or rollback revert operation in the tmnxLogExecRollbackOpTable. It is included in the 'exec' and rollback revert start and end notifications.

The value of tmnxLogColdStartWaitTime specifies the time delay that must pass before notifying specific CPM applications that a route is available after a cold reboot.

The value of tmnxLogRouteRecoveryWaitTime specifies the time delay that must pass before notifying specific CPM applications after the recovery or change of a route during normal operation.

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.

Generated when an attempt to create a log or billing 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 billing 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.

The tmnxLogTraceError notification is generated when a trace error event is detected.

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 identfied by the tmnxSysLogTargetId.

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.