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

This document is the System SNMP MIB module for the Alcatel-Lucent SROS device. The System MIB module defines SNMP objects to manage and provision system features. 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 management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for currently active (booted) BOF capabilities on Alcatel-Lucent SROS series systems.

The compliance statement for management of general system capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting management of RADIUS servers on Alcatel-Lucent SROS series systems.

The group of objects supporting management of TACACS+ servers on Alcatel-Lucent SROS series systems.

The group of objects supporting management of the Boot Options File (BOF) on Alcatel-Lucent SROS series systems.

The group of objects supporting management of boot-up configuration and synchronization of active and standby systems on Alcatel-Lucent SROS series systems.

The group of objects supporting management of general system capabilities on Alcatel-Lucent SROS series systems, 3.0 Release.

The group of objects in TIMETRA-SYSTEM-MIB which are obsoleted.

The group of objects supporting management of persistency accross system reboot on Alcatel-Lucent SROS series systems.

The group of objects supporting management of time on Alcatel-Lucent SROS series systems, 4.0 Release.

The group of objects supporting notifications for general system capabilities on Alcatel-Lucent SROS series systems.

The group of notifications supporting the general system capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting notifications for general system capabilities on Alcatel-Lucent SROS series systems.

The group of notifications supporting the general system capabilities on Alcatel-Lucent SROS series systems.

The group of notification objects in TIMETRA-SYSTEM-MIB which are obsoleted.

The group of objects supporting management of TACACS+ servers on Alcatel-Lucent SROS series systems.

The group of objects supporting management of RADIUS servers on Alcatel-Lucent SROS series systems.

The group of objects in TIMETRA-SYSTEM-MIB which are obsoleted.

The group of objects supporting management of persistency accross system reboot on Alcatel-Lucent SROS series systems.

The group of objects supporting ipv6 management interface on Alcatel-Lucent SROS series systems.

The group of objects supporting management of persistency accross system reboot on Alcatel-Lucent SROS series systems.

The group of objects supporting management of the Boot Options File (BOF) on Alcatel-Lucent SROS series systems.

The group of notifications supporting the general system capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Lawful Intercept configuration on Alcatel-Lucent SROS series systems.

The group of objects added in 6.0 release to support system notifications.

The group of objects supporting management of general system capabilities on Alcatel-Lucent SROS series systems added in 7.0 Release.

The group of objects supporting management of ICMP vendor specific enhancement capabilities on Alcatel-Lucent SROS series systems.

The group of objects supporting management of boot-up configuration and synchronization of active and standby systems on Alcatel-Lucent SROS series systems.

The group of objects supporting management of login control on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Ethernet Info on Alcatel-Lucent SROS series systems.

The group of objects supporting management of persistency accross system reboot on Alcatel-Lucent SROS series systems release 9.0.

The group of objects supporting management of login control on Alcatel-Lucent SROS series systems.

The group of objects supporting management of Lawful Intercept configuration on Alcatel-Lucent SROS series systems.

The group of notifications supporting the general system capabilities added in release 9.0 of SROS.

The group of objects supporting management of the Rollback Files on Alcatel-Lucent SROS series systems.

The group of objects supporting management of login control on Alcatel-Lucent SROS series systems, added in release 9.0.

The group of objects, added in release 7.0, used for monitoring system CPU utilization on Alcatel SROS series systems.

The group of objects supporting management of the synchronization of certificate Files on Alcatel-Lucent SROS series systems.

The group of objects giving the value of the currently active (booted) Boot Options File (BOF) parameters on Alcatel-Lucent SROS series systems.

The group of objects supporting management of the Rollback Rescue file on Alcatel-Lucent SROS series systems.

The group of notifications supporting the general system capabilities added in release 10.0 of SROS.

The group of accessible-for-notify objects supporting notifications on Alcatel-Lucent SROS series systems added in SROS release 10.0.

The group of notifications supporting the general system capabilities added in Alcatel-Lucent SROS series systems.

The group of accessible-for-notify objects supporting notifications on Alcatel-Lucent SROS series systems added in SROS.

The value of sgiCpuUsage indicates the current CPU utilization for the system.

The value of sgiMemoryUsed indicates the total pre-allocated pool memory currently in use on the system. If the value is greater than the maximum value reportable by this object then this object reports its maximum value (4,294,967,295) and sgiKbMemoryUsed must be used to determine the total pre-allocated pool memory.

The value of sgiMemoryAvailable indicates the amount of free memory in the overall system that is not allocated to memory pools, but is available in case a memory pool needs to grow.

The value of sgiMemoryPoolAllocated indicates the total memory currently allocated in memory-pools on the system. This memory may or may not be currently in use, but is pre-allocated should the software need to use it. If the value is greater than the maximum value reportable by this object then this object reports its maximum value (4,294,967,295) and sgiKbMemoryPoolAllocated must be used to determine the total memory allocated in memory-pools.

The value of sgiSwMajorVersion indicates the major version number of the software running on the active CPM card.

The value of sgiSwMinorVersion indicates the minor version number of the software running on the active CPM card.

The value of sgiSwVersionModifier indicates additional information about the version of software running on the active CPM card.

The value of sgiSnmpInGetBulks indicates the total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.

The value of sgiKbMemoryUsed indicates the total pre-allocated pool memory, in kilobytes, currently in use on the system.

The value of sgiKbMemoryAvailable indicates the amount of free memory, in kilobytes, in the overall system that is not allocated to memory pools, but is available in case a memory pool needs to grow.

The value of sgiKbMemoryPoolAllocated indicates the total memory, in kilobytes, currently allocated in memory-pools on the system. This memory may or may not be currently in use, but is pre-allocated should the software need to use it.

tmnxSysCpuMonTable consists of the system level CPU monitoring statistics.

tmnxSysCpuMonEntry contains the system level CPU monitoring statistics over a specified sample-time.

The value of tmnxSysCpuMonSampleTime specifies the sample-time used to calculate the utilization results for the row.

The value of tmnxSysCpuMonCpuIdle indicates the overall percentage of CPU idleness over the specified sample-time.

The value of tmnxSysCpuMonBusyCoreUtil indicates the utilization percentage of the busiest processor core over the specified sample-time. On single core CPUs, this is the overall system utilization percentage over the specified sample-time.

The value of tmnxSysCpuMonBusyGroupName indicates the name of the group that is running at the highest capacity utilization. Capacity utilization is the CPU utilization relative to the maximum CPU resources available to that group. A group is a set of related applications, services, tasks or protocol handlers that consumes some part of the system CPU resources. The capacity utilization of the busiest group is indicated by tmnxSysCpuMonBusyGroupUtil.

The value of tmnxSysCpuMonBusyGroupUtil indicates the capacity utilization of the group that is running at the highest capacity utilization. Capacity utilization is the CPU utilization relative to the maximum CPU resources available to that group. A group is a set of related applications, services, tasks or protocol handlers that consumes some part of the system CPU resources. The name of the busiest group is indicated by tmnxSysCpuMonBusyGroupName.

The current date and time (in UTC) maintained in this managed system.

The time zone that is active in this managed system.

The number of hours by which the time zone represented by stiActiveZone offsets from UTC (Coordinated Universal Time).

The number of minutes (in addition to the hours offset defined by stiHoursOffset) by which the time zone represented by stiActiveZone offsets from UTC (Coordinated Universal Time). This value is used when the time zone does not have an offset that is an integral number of hours. If the hour offset is defined as '12', the minute offset cannot be anything other than zero.

stiZoneType will be 'system' if the zone defined by stiActiveZone is a system-defined zone. It will be 'user' if the zone has been defined by the user. Enumeration: 'system': 1, 'user': 2.

The stiSummerZoneTable has an entry for each summer time zone information.

Each row entry contains information about a summer time zone. This information can be used to either override the default summer (or daylight savings) time information for a system-defined time zone or define the summer time information for a user-defined time zone.

The name for a summer time zone. This name must be unique amongst the table entries. The summer time zone name should comprise only of uppercase letters A-Z and digits 0-9.

The row status used to create and delete rows in this table.

The starting date and time when the summer time will take effect. This object was made obsolete in the 4.0 release.

The date and time when summer time will end. This object was made obsolete in the 4.0 release.

The number of minutes that will be added to the time when summer time takes effect. The same number of minutes will be subtracted from the time when the summer time ends.

The starting day of the week when the summer time will take effect. Enumeration: 'monday': 1, 'tuesday': 2, 'friday': 5, 'wednesday': 3, 'thursday': 4, 'sunday': 0, 'saturday': 6.

The starting week of the month when the summer time will take effect. Enumeration: 'second': 1, 'last': 4, 'fourth': 3, 'third': 2, 'first': 0.

The starting month of the year when the summer time will take effect. Enumeration: 'february': 1, 'october': 9, 'march': 2, 'august': 7, 'september': 8, 'may': 4, 'january': 0, 'june': 5, 'april': 3, 'december': 11, 'july': 6, 'november': 10.

The hour at which the summer time will take effect.

The number of minutes after the hours defined by stiSummerZoneStartHour when the summer time will take effect.

The day of the week when the summer time setting will end. Enumeration: 'monday': 1, 'tuesday': 2, 'friday': 5, 'wednesday': 3, 'thursday': 4, 'sunday': 0, 'saturday': 6.

The week of the month when the summer time setting will end. Enumeration: 'second': 1, 'last': 4, 'fourth': 3, 'third': 2, 'first': 0.

The month of the year when the summer time setting will end. Enumeration: 'february': 1, 'october': 9, 'march': 2, 'august': 7, 'september': 8, 'may': 4, 'january': 0, 'june': 5, 'april': 3, 'december': 11, 'july': 6, 'november': 10.

The hour at which the summer time will stop taking effect.

The number of minutes after the hours defined by stiSummerZoneEndHour when the summer time will stop taking effect.

The mode for Simple Network Time Protocol (SNTP). 'Unicast' indicates that broadcast client is disabled. A value of 'broadcast' indicates that SNTP is listening to SNTP/NTP broadcast messages on interfaces with broadcast client enabled. Enumeration: 'unicast': 1, 'broadcast': 2.

The sntpServerEntry has an entry for each SNTP server for SNTP unicast client mode. SNTP can only receive the time from one of these SNTP servers. The table can have upto a maximum of 3 entries.

Each row entry contains information about an SNTP server.

The IP address of the SNTP server.

The row status used to create and delete rows in this table.

The SNTP Version supported by this server.

The preference value for this SNTP server. When more then one time-server is configured it may be desirable that one server have preference over others. The value of sntpServerPreference for that server will be set to preferred(2). Only one server in the table can be a preferred server Enumeration: 'preferred': 2, 'normal': 1.

The frequency at which this server is queried.

The desired administrative state for SNTP. Enumeration: 'outOfService': 3, 'noop': 1, 'inService': 2.

The value of sntpOperStatus indicates the current operational status of SNTP.

Setting this action variable to 'doAction' causes the current running configuration information to be saved to the location specified by ssiSaveConfigDest. If no location is specified by ssiSaveConfigDest, the primary configuration file pointed to in the boot options file (bof) will be backed up and a new primary configuration file will be created with the current running configuration information. If ssiSaveConfigDetail has a value of 'true', default configuration values will be included in the saved configuration information. A corresponding persistent SNMP index file is created regardless of the setting of the persistence switch in the bof.

The value of ssiSyncMode specifies the type of synchronization operation to perform between the primary and secondary CPMs after a change has been made to the configuration files or the boot environment information contained in the boot options file (bof).

The value of ssiSyncForce specifies the type of synchronization operation to perform when an SNMP set is made to this object. 'config' synchronizes only configuration files. 'bootEnv' synchronizes all files required to boot the system. The result of a read operation on this object is always 'none'.

The value of ssiSyncStatus indicates the results of the last synchronization operation between the primary and secondary CPMs. Enumeration: 'configFail': 3, 'unknown': 0, 'configOnly': 1, 'bootEnvFail': 4, 'bootEnvInProgress': 6, 'bootEnv': 2, 'configInProgress': 5.

The value of ssiSyncConfigLastTime is the timestamp of the last successful synchronization of the configuration files.

The value of ssiSyncBootEnvLastTime is the timestamp of the last successful synchronization of the boot environment files.

The value of ssiConfigMaxBackupRevisions is the maximum number of backup revisions maintained for a configuration file. This value also applies to the number of revisions maintained for the BOF file.

The value of ssiSaveConfigResult represents the result of the last ssiSaveConfig action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

Setting ssiSaveBof action variable to 'doAction' causes the existing BOF to be backed up and a new BOF file to be created with the current boot options information.

The value of ssiSaveBofResult represents the result of the last ssiSaveBof action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of ssiSaveConfigDest specifies the destination filepath or file-URL where the current running configuration information will be saved when ssiSaveConfig is set to 'doAction'. If ssiSaveConfigDest is set to the empty string, ''H, the primary configuration file pointed to in the boot options file (bof) will be backed up and a new primary configuration file will be created with the current running configuration information. A corresponding persistent SNMP index file is created regardless of the setting of the persistence switch in the bof.

When ssiSaveConfigDetail has a value of 'true', the default configuration values will also be included in the current running configuration information that will be saved when ssiSaveConfig is set to 'doAction'. When ssiSaveConfigDetail has a value of 'false', only non-default configuration values are saved.

The value of ssiRedFailoverTime is the timestamp when the last redundancy failover occurred causing a switchover from active to standby CPM. If there is no redundant CPM card in this system or no failover has occurred since the system last booted, ssiRedFailoverTime will always return 0.

The value of ssiRedFailoverReason is a text string giving an explanation of the cause of the last redundancy failover. If no failover has occurred, the empty string, ''H, will be returned.

The value of ssiSyncRollbackLastTime is the timestamp of the last successful synchronization of the rollback files.

The value of ssiSyncRollbackMode specifies the type of synchronization operation to perform between the primary and secondary CPMs after a change has been made to the rollback files.

The value of ssiSyncRollbackForce specifies the type of synchronization operation to perform when an SNMP set is made to this object. 'rollbackSingle' synchronizes only the rollback file that recently changed. 'rollbackAll' synchronizes all rollback files. The result of a read operation on this object is always 'none'.

The value of ssiSyncRollbackStatus indicates the results of the last rollback synchronization operation between the primary and secondary CPMs. Enumeration: 'unknown': 0, 'rollbackSuccess': 3, 'rollbackFail': 1, 'rollbackInProgress': 2.

The value of ssiSyncCertLastTime is the timestamp of the last successful synchronization of the certificate files.

The value of ssiSyncCertMode specifies whether to synchronize certificate files between the primary and secondary CPMs.

The value of ssiSyncCertForce specifies to perform action to synchronize certificate files between the primary and secondary CPMs when an SNMP set is made to this object. The value of ssiSyncCertForce will always be returned as 'notApplicable'.

The value of ssiSyncCertStatus indicates the results of the last certificate synchronization operation between the primary and secondary CPMs. Enumeration: 'fail': 1, 'unknown': 0, 'inProgress': 2, 'success': 3.

The value of sbiConfigStatus indicates the result of the last attempt to execute the configuration file upon reboot of the system. configRead (1) - The configuration file is being read. configOK (2) - The configuration file was successfully executed. defaultBooted (3) - There was no configuration file and the system booted using a minimal default configuration. bootConfigFailed (4) - An error occurred while the configuration file was being executed. The system configuration is incomplete. bootRestoreFailed (5) - An error occurred while the restoration was being performed. The system configuration is incomplete. Enumeration: 'configRead': 1, 'configOK': 2, 'bootConfigFailed': 4, 'bootRestoreFailed': 5, 'defaultBooted': 3.

The value of sbiPersistStatus indicates the result of the last attempt to rebuild the SNMP persistent index database upon reboot of the system. persistOK (1) - The persistent index database was successfully created. Persistent SNMP managed objects were recreated with the same SNMP indexes they had prior to the system reboot. noPersistFile (2) - There was no persistent index file with the same pathname as the configuration file. persistMismatch (3) -The headers in the persistent index file and the configuration file with the same name do not match. persistIndexFailure (4) - An error occurred while creating the persistent index database. persistDisabled (5) - The system was administratively reconfigured without maintaining persistent SNMP index values because sbiPersistIndex has a value of 'false'. If sbiConfigStatus has a value of 'configOK' and sbiPersistStatus has any value other than 'persistOK', the system was reconfigured without maintaining persistent SNMP index values. Unless sbiPersistIndex has a value of 'false', sbiSnmpdOperStatus returns 'disabled' and the SNMP daemon will not receive SNMP requests until sbiSnmpdAdminStatus variable has been set to 'inService'. Enumeration: 'persistIndexFailure': 4, 'persistMismatch': 3, 'noPersistFile': 2, 'persistDisabled': 5, 'persistOK': 1.

When sbiPersistIndex has a value of 'true', the SNMP persistent index database was rebuilt when the system was rebooted. If there was an error during the processing of the configuration file the system may have been reconfigured without persistent SNMP indexes and the SNMP daemon will be suspended until it is manually enabled by setting sbiSnmpdAdminStatus to 'inService. When sbiPersistIndex has a value of 'false' the system was reconfigured without maintaining persistent SNMP index values and the SNMP daemon was enabled.

The value of sbiSnmpdAdminStatus is the desired administrative state for the SNMP daemon. When sbiSnmpdAdminStatus is set to 'inService' the SNMP daemon will begin receiving SNMP requests from external SNMP managers. When sbiSnmpdAdminStatus is set to 'outOfService' the SNMP daemon is suspended and will no longer receive SNMP requests from external SNMP managers.

When sbiSnmpdOperStatus has a value of 'inService', the SNMP daemon will receive SNMP requests from external SNMP managers. When sbiSnmpdOperStatus has a value of 'outOfService', the SNMP daemon is suspended and will not receive SNMP requests from external SNMP managers.

The value of sbiSnmpdMaxPktSize indicates the maximum length in octets of an SNMP message which the SNMP daemon can send or receive and process.

The value of sbiSnmpdPortNum indicates the UDP port to send and receive SNMP messages.

The value of sbiBootConfigOKScript specifies the location and name of the CLI script file executed following successful completion of the boot-up configuration file execution. I.e. sbiPersistStatus has a value of 'configOK'. When this object has the empty string value, ''H, no CLI script file is executed.

The value of sbiConfigOKScriptStatus indicates the results of executing the CLI script file specified in sbiBootConfigOKScript. Enumeration: 'fail': 2, 'notRun': 0, 'success': 1.

The value of sbiBootConfigFailScript specifies the location and name of the CLI script file executed following failure of the boot-up configuration file execution. I.e. sbiPersistStatus has a value other than 'configOK'. When this object has the empty string value, ''H, no CLI script file is executed.

The value of sbiConfigFailScriptStatus indicates the results of executing the CLI script file specified in sbiBootConfigFailScript. Enumeration: 'fail': 2, 'notRun': 0, 'success': 1.

The value of sbiRedSwitchoverScript specifies the location and name of the CLI script file executed following a redundancy switchover from the previously active CPM card. A switchover can happen because of a fatal failure or by manual action. This CLI script file can contain commands for environment settings, debug and mirroring settings, and other commands not maintained by the configuration redundancy. When this object has the empty string value, ''H, no CLI script file is executed.

The value of sbiRedSwitchoverScriptStatus indicates the results of executing the CLI script file specified in sbiRedSwitchoverScript. Enumeration: 'fail': 2, 'notRun': 0, 'success': 1.

The radiusOperStatus will have a value of 'up' if any one of the RADIUS servers in the radiusServerTable has the radiusServerOperStatus value of 'up'. It will have a value of 'down' if all the RADIUS servers in the radiusServerTable have the radiusServerOperStatus value of 'down'. Enumeration: 'down': 2, 'up': 1.

The radiusServerEntry has an entry for each RADIUS server. The table can have up to a maximum of 5 entries.

Each row entry contains information about a RADIUS server.

The unique value which identifies a specific radius server.

The IP address of the RADIUS server. This object was made obsolete in the 5.0 release.

Current status of the RADIUS server. Enumeration: 'down': 2, 'up': 1.

The value of radiusServerInetAddressType indicates the address type of radiusServerInetAddress address. The value of radiusServerInetAddressType can be either of InetAddressType - 'ipv4' or InetAddressType - 'ipv6' or InetAddressType - 'ipv6z'.

The value of radiusServerInetAddress indicates the address of the Radius server.

tmnxNotifyRow is used by the configuration modify, create and delete traps. tmnxNotifyRow specifies the OID of the MIB table entry that was changed.

tmnxNotifyRowAdminState is used by the state change notification to specify the administrative state of the MIB table entry reported in the notification.

tmnxNotifyRowOperState is used by the state change notification to specify the operational state of the MIB table entry reported in the notification.

tmnxMemoryModule is used by the module malloc failed notification to specify the memory module for which the trap is generated.

tmnxModuleMallocSize is used by the module malloc failed notification to specify the memory size (in bytes) requested in the failed malloc call.

tmnxDroppedTrapID is used by the trap dropped notification to specify the NOTIFICATION-TYPE object identifier of the dropped trap.

tmnxTrapDroppedReasonCode is used by the trap dropped notification to specify the reason for which a trap is dropped. Enumeration: 'frequencyExceeded': 1.

tmnxTrapDroppedEntryID is used by the trap dropped notification to specify the table entry associated with the dropped trap.

tmnxNotifyEntryOID is used by the configuration modify, create and delete traps. tmnxNotifyEntryOID specifies the OID of the MIB table that was changed.

tmnxSnmpdErrorMsg is used by the tmnxSnmpdError notification to indicate the type of SNMP daemon error detected.

tmnxPersistencyClient is used by the persistencyClosedAlarmRaised, persistencyClosedAlarmCleared, persistencyFileSysThresRaised and persistencyFileSysThresCleared notification to indicate the affected persistent application.

tmnxPersistencyFileLocator is used by the persistencyClosedAlarmRaised, persistencyClosedAlarmCleared, persistencyFileSysThresRaised and persistencyFileSysThresCleared notification to indicate the affected file used to store persistence data.

tmnxPersistencyNotifyMsg is used by the persistencyClosedAlarmRaised persistencyClosedAlarmCleared, persistencyEventReport, persistencyFileSysThresRaised and persistencyFileSysThresCleared notification to provide additional information related to the event that occurred.

tmnxPersistenceAffectedCpm is used by the persistencyClosedAlarmRaised, persistencyClosedAlarmCleared, persistencyFileSysThresRaised and persistencyFileSysThresCleared notification to indicate the affected CPM.

tmnxSysTimeSetBy is used by tmnxSysTimeSetBy notification to indicate who set the time. Enumeration: 'ntp': 1, 'manually': 4, 'snmp': 3, 'rtc': 5, 'sntp': 2.

tmnxFtpFailureMsg is used by tmnxFtpClientFailure notification to indicate FTP error.

tmnxFtpFailureDestAddressType is used by tmnxFtpClientFailure notification to indicate the IP address type of the remote host.

The value of tmnxFtpFailureDestAddress indicates the IP address of the remote host to which an ftp operation is being attempted on. The value of tmnxFtpFailureDestAddress is used by tmnxFtpClientFailure notification.

tmnxNotifyObjectName is used by the configuration modify, create, delete and state change traps. tmnxNotifyObjectName specifies the human readable name of the OID instance of the MIB table entry that was changed.

tmnxSyncFailureReason is used by the ssiSyncConfigFailed, ssiSyncBootEnvFailed, and ssiSyncRollbackFailed traps to specify the reason for synchronization failure.

The value of tmnxSysExecScript specifies the location and name of the CLI command script file executed by a SROS CLI 'exec' command. It is used by the tmnxSysExecStarted and tmnxSysExecFinished notifications.

The value of tmnxSysExecResult indicates the results of executing the CLI script file specified in tmnxSysExecScript. It is used by the tmnxSysExecFinished notification. Enumeration: 'fail': 2, 'none': 0, 'success': 1.

tmnxSysRollbackFileType is used by tmnxSysRollbackStarted, tmnxSysRollbackSaveStarted, tmnxSysRollbackDeleteStarted, tmnxSysRollbackStatusChange, tmnxSysRollbackSaveStatusChange, and tmnxSysRollbackFileDeleteStatus notifications to indicate the type of file involved in a rollback operation. Enumeration: 'rollback': 1, 'rescue': 2.

tmnxSysFileErrorType is used by tmnxSysNvsysFileError notification to indicate the type of file error occurred. Enumeration: 'read': 1, 'write': 2.

The maximum number of concurrent inbound FTP sessions permitted.

The value of slcTelnetInboundMaxSessions specifies the maximum number of concurrent inbound telnet sessions permitted.

The value of slcTelnetOutboundMaxSessions specifies the maximum number of concurrent outbound telnet sessions permitted.

The message to be displayed prior to the login prompt of an inbound FTP or telnet session.

If the value of slcPreLoginMessageInclName is set to 'TRUE', the slcPreLoginMessage which is displayed prior to the login prompt will contain the system name.

The message-of-the-day text will be displayed when the user successfully authenticates himself for an inbound FTP, telnet or console session. If slcMessageOfTheDayType is set to 'URL', then slcMessageOfTheDay should be of the form: 'url-prefix:source-url'.

The type of slcMessageOfTheDay. If the value of slcMessageOfTheDayType is set to 'motd-type-none', then message of the day will not be displayed. If it is set to 'motd-type-url', then the message is fetched from the URL. Enumeration: 'motd-type-url': 1, 'motd-type-text': 2, 'motd-type-none': 0.

If the value of slcLoginBanner is set to 'true', the login banner containing Alcatel-Lucent copyright and version information is displayed prior to the login prompt. If the value is set to 'false', the login banner is not displayed.

The value of slcLoginExponentialBackOff specifies if exponential-backoff of the login prompt is enabled. Exponential-backoff is used to deter dictionary attacks. A value of 'true' specifies that exponential-backoff is enabled, while a value of 'false' indicates that exponential-backoff is disabled.

The value of slcTelnetGracefulShutdown specifies if graceful shutdown is enabled. A value of 'true' specifies that telnet sessions are closed gracefully by using a TCP FIN/ACK handshake. A value of 'false' indicates that telnet sessions are disconnected by sending a RST (reset) TCP packet.

The value of slcSSHGracefulShutdown specifies if graceful shutdown is enabled. A value of 'true' specifies that SSH sessions are closed gracefully by using a TCP FIN/ACK handshake. A value of 'false' indicates that SSH sessions are disconnected by sending a RST (reset) TCP packet.

The value of slcTelnetMinTTLValue specifies the minimum TTL value for an incoming packet. This object can only be set if the value of tmnxCpmPerPeerQueuing is 'true (1)'. This value is applied after restarting the Telnet server. If slcTelnetMinTTLValue is set to zero (0), the TTL Security feature is disabled.

The value of slcSSHMinTTLValue specifies the minimum TTL value for an incoming packet. This object can only be set if the value of tmnxCpmPerPeerQueuing is 'true (1)'. This value is applied after restarting the SSH server. If slcSSHMinTTLValue is set to zero (0), the TTL Security feature is disabled.

The value of slcSSHInboundMaxSessions specifies the maximum number of concurrent inbound SSH sessions permitted.

The value of slcSSHOutboundMaxSessions specifies the maximum number of concurrent outbound SSH sessions permitted.

sysLACPSystemPriority is the Link Aggregation Control Protocol (LACP) system priority which is combined with the system MAC address to make up a unique system ID that is used by LACP in communications with LACP peer systems on Link Aggregation (LAG) ports.

The tacplusOperStatus will have a value of 'up' if any one of the TACACS+ servers in the tacplusServerTable has the tacplusServerOperStatus value of 'up'. It will have a value of 'down' if all the TACACS+ servers in the tacplusServerTable have the tacplusServerOperStatus value of 'down'. Enumeration: 'down': 2, 'up': 1.

The tacplusServerEntry has an entry for each TACACS+ server. The table can have up to a maximum of 5 entries.

Each row entry contains information about a TACACS+ server.

The unique value which identifies a specific TACACS+ server.

The IP address of the TACACS+ server. This object was made obsolete in the 5.0 release.

Current status of the TACACS+ server. Enumeration: 'down': 2, 'up': 1.

The value of tacPlusServerInetAddressType indicates the address type of tacPlusServerInetAddress address. The value of tacPlusServerInetAddressType can be either of InetAddressType - 'ipv4' or InetAddressType - 'ipv6' or InetAddressType - 'ipv6z'.

The value of tacPlusServerInetAddress indicates the address of the Tacplus server.

The value of sbiActiveIpAddr specifies the IP address of the ethernet port on the active CPM.

The value of sbiActiveIpMask specifies the mask length of the subnet associated with the IP address of the ethernet port on the active CPM.

The value of sbiStandbyIpAddr specifies the IP address of the ethernet port on the standby CPM.

The value of sbiStandbyIpMask specifies the mask length of the subnet associated with the IP address of the ethernet port on the standby CPM.

The value of sbiPrimaryImage specifies the primary location of the directory that contains the runtime image files.

The value of sbiSecondaryImage specifies the secondary location of the directory that contains the runtime image files.

The value of sbiTertiaryImage specifies the tertiary location of the directory that contains the runtime image files.

The value of sbiPrimaryConfigFile specifies the location and name of the primary configuration file.

The value of sbiSecondaryConfigFile specifies the location and name of the secondary configuration file.

The value of sbiTertiaryConfigFile specifies the location and name of the tertiary configuration file.

The value of sbiPersist specifies whether or not the system will preserve SNMP indexes between reboots. When set to 'true', persistent indexing is enabled.

The value of sbiConsoleSpeed specifies the baud rate of the console port.

The value of sbiAutoNegotiate determines whether or not the speed and duplex parameters will be automatically negotiated on the CPM ethernet port. When set to 'true', auto-negotiation is enabled.

The value of sbiSpeed specifies the speed of the CPM ethernet port. This value is ignored if auto-negotiation is enabled.

The value of sbiDuplex specifies the duplex mode for the CPM ethernet port. This value is ignored if auto-negotiation is enabled. Enumeration: 'full': 1, 'half': 2.

The value of sbiPrimaryDns specifies the IP address of the primary DNS server to use for DNS name resolution.

The value of sbiSecondaryDns specifies the IP address of the secondary DNS server to use for DNS name resolution.

The value of sbiTertiaryDns specifies the IP address of the tertiary DNS server to use for DNS name resolution.

The value of sbiDnsDomain specifies the domain name to use when performing DNS address resolution.

The value of sbiWait specifies the number of seconds the system pauses at the start of the boot process. This pause allows the operator to interrupt the system initialization at the console and manually override the parameters in the BOF.

The sbiStaticRouteTable contains an entry for each static route configured for the CPM ethernet port. These static routes are only used to route traffic generated by the CPM ethernet port. The table can have upto a maximum of 10 entries.

Each row entry contains information about a static route configured for the CPM ethernet port. Entries in this table can be created and deleted via SNMP SET operations to sbiStaticRouteRowStatus.

The value of sbiStaticRouteDest specifies the destination IP address of this static route.

The value of sbiStaticRouteMask specifies the length of the subnet mask associated with the destination IP address of this static route.

The value of sbiStaticRouteNextHop specifies the IP address of the next hop for this static route. This IP address should be in the same subnet as the ethernet port on the active CPM. The value of sbiStaticRouteNextHop must be set to a valid IP address for the row creation to succeed.

sbiStaticRouteRowStatus controls the creation and deletion of rows in the table. To create a row in this table, set the row status to createAndGo(4)'. The value of sbiStaticRouteNextHop must also be set to a valid IP address for the row creation to succeed. To delete a row in this table, set the row status to delete(6).

The value of sbiActiveIPv6Addr specifies the IPv6 address of the ethernet port on the active CPM.

The value of sbiActiveIPv6PfxLen specifies the prefix length of the subnet associated with the sbiActiveIPv6Addr address of the ethernet port on the active CPM.

The value of sbiStandbyIPv6Addr specifies the IPv6 address of the ethernet port on the standby CPM.

The value of sbiStandbyIPv6PfxLen specifies the prefix length of the subnet associated with the sbiStandbyIPv6Addr address of the ethernet port on the active CPM.

The value of sbiPrimaryDnsIPv6Addr specifies the IPv6 address of the primary DNS server to use for DNS name resolution.

The value of sbiSecondaryDnsIPv6Addr specifies the IPv6 address of the secondary DNS server to use for DNS name resolution.

The value of sbiTertiaryDnsIPv6Addr specifies the IPv6 address of the tertiary DNS server to use for DNS name resolution.

The sbiStaticRouteIPv6Table contains an entry for each static IPv6 route configured for the CPM ethernet port. These static routes are only used to route traffic generated by the CPM ethernet port. The table can have upto a maximum of 10 entries.

Each row entry contains information about a static IPv6 route configured for the CPM ethernet port. Entries in this table can be created and deleted via SNMP SET operations to sbiStaticRouteIPv6RowStatus.

The value of sbiStaticRouteIPv6Dest specifies the destination IPv6 address of this static route.

The value of sbiStaticRouteIPv6PfxLen specifies the prefix length of sbiStaticRouteIPv6Dest, the destination IPv6 address of this static route.

The value of sbiStaticRouteIPv6NextHop specifies the IPv6 address of the next hop for this static route. This IPv6 address should be in the same subnet as the ethernet port on the active CPM. The value of sbiStaticRouteIPv6NextHop must be set to a valid IPv6 address for the row creation to succeed.

sbiStaticRouteIPv6RowStatus controls the creation and deletion of rows in the table. To create a row in this table, set the row status to createAndGo(4)'. The value of sbiStaticRouteIPv6NextHop must also be set to a valid IPv6 address for the row creation to succeed. To delete a row in this table, set the row status to delete(6).

The value of sbiLiSeparate specifies whether or not a non-LI user has access to Lawful Intercept (LI) information. When sbiLiSeparate has a value of 'true', a user who does not have the TMETRA-SECURITY-MIB:: tmnxUserAccess 'li' bit set will not be allowed to access CLI or SNMP objects in the 'li' context. A change to the value of this object does not take affect until the system is rebooted.

The value of sbiLiLocalSave specifies whether or not Lawful Intercept (LI) configuration is allowed to be save to a local file. A change to the value of this object does not take affect until the system is rebooted.

The value of spiDhcpL2PersistenceFileLocation specifies the flash device on a CPM card where the data for handling DHCP Layer2 persistency is stored. The value 0 indicates that no flash device is specified. This object was made obsolete in the 5.0 release.

The value of the object spiDhcpL2PersistenceDescription specifies a user provided description related to DHCP Layer-2 persistency. It consists of any printable, seven-bit ASCII characters up to 80 characters in length. This object was made obsolete in the 5.0 release.

The value of spiDhcpL3PersistenceFileLocation specifies the flash device on a CPM card where the data for handling DHCP Layer3 persistency is stored. The value 0 indicates that no flash device is specified. This object was made obsolete in the 5.0 release.

The value of the object spiDhcpL3PersistenceDescription specifies a user provided description related to DHCP Layer-3 persistency. It consists of any printable, seven-bit ASCII characters up to 80 characters in length. This object was made obsolete in the 5.0 release.

The value of spiSubMgmtPersistenceFileLocation specifies the flash device on a CPM card where the data for handling subscriber management persistency is stored. The value 0 indicates that no flash device is specified.

The value of the object spiSubMgmtPersistenceDescription specifies a user provided description related to subscriber management persistency. It consists of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of spiDhcpSrvPersistenceFileLoc specifies the flash device on a CPM card where the data for handling the local DHCP server persistency is stored. The value 0 indicates that no flash device is specified.

The value of the object spiDhcpSrvPersistenceDescr specifies a user provided description related to the local DHCP server persistency. It consists of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of spiNatFwdPersistenceFileLoc specifies the flash device on a CPM card where the data for handling the NAT (Network Address Translation) port forwarding persistence is stored. The value 0 indicates that no flash device is specified.

The value of the object spiNatFwdPersistenceDescr specifies a user provided description related to the NAT port forwarding persistence. It consists of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of spiAAPersistenceFileLoc specifies the flash device on a CPM card where the data for handling the AA (Application Assurance) persistence is stored. The value 0 indicates that no flash device is specified.

The value of the object spiAAPersistenceDescr specifies a user provided description related to the AA (Application Assurance) persistence. It consists of any printable, seven-bit ASCII characters up to 80 characters in length.

The value of sliConfigStatus indicates the results of restoring the Lawful Intercept (LI) configuration at boot-up time. Enumeration: 'fail': 2, 'notRun': 0, 'success': 1.

The value of sliSaveConfig indicates a desired action. Setting this action variable to 'doAction' causes the current Lawful Intercept (LI) running configuration information, to be saved to a file called li.cfg in the same location as the BOF file. If the li.cfg file already exists, it will be renamed and a new file is created with the current running configuration. An attempt to set this object to 'doAction' when the booted value of sbiLiLocalSave is 'false' will result in an 'inconsistentValue' error. Default configuration values will be included in the saved configuration information.

The value of sliSaveConfigResult represents the result of the last sliSaveConfig action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of sliConfigLastModified indicates the date and time the Lawful Intercept (LI) running configuration was last modified. If sliConfigLastModified is more recent than TIMETRA-CHASSIS-MIB:: tmnxHwSwLastBoot, the current configuration may be different than that in the configuration file read upon system initialization.

The value of sliConfigLastSaved indicates the date and time the current Lawful Intercept (LI) configuration was last saved. If sliConfigLastSaved is more recent than the value of TIMETRA-CHASSIS-MIB::tmnxHwSwLastBoot, the initial configuration is likely to be different the next time the system is rebooted.

The of sliFilterLock specifies who can modify the Lawful Intercept (LI) filters. The value: 'locked': no users can modify the LI filters 'unlockedForLiUsers': only users with LI privileges can modify the LI filters 'unlockedForAll': all users can modify the LI filters. Enumeration: 'locked': 0, 'unlockedForLiUsers': 1, 'unlockedForAll': 2.

The value of sysDNSInfoLastChanged is the timestamp of the last configuration changes to any of the DNS global settings.

The value of sysDNSAddressResolvePref specifies how the DNS client will request for address resolution. ipv4-only: The DNS client will only try to resolve a domain name into an ipv4 address. ipv6-first: the DNS client will first try to relsove the domain name in to ipv6 address. If no ipv6 address is available it will try to resolve the domain name into an ipv4 address. Enumeration: 'ipv6First': 2, 'ipv4Only': 1.

The value of sysIcmpVSEnhancement specifies if vendor specific extensions to ICMP is enabled or not.

The value of sysNewQinqUntaggedSap controls the forwarding of packets on a QinQ X.0 access SAP. When sysNewQinqUntaggedSap is set to true, the SAP will only accept: - frames with a single tag matching the SAP's outer tag or, - frames with double tag where the outer tag matches the SAP's outer tag and inner tag is set to 0. When sysNewQinqUntaggedSap is set to false, forwarding of packets remains unchanged.

The value of tmnxSysRollbackIndex indicates a specific rollback checkpoint file to which a rollback action can be taken. The value of the tmnxSysRollbackIndex corresponds to a rollback checkpoint file with suffix .rb.index. The maximum checkpoint file that can be specified is determined by the rollback location as specified by tmnxSysRollbackLocation. If the location is on a compact flash, then the maximum value of tmnxSysRollbackIndex can be tmnxSysRollbackMaxLocalFiles minus 1. If the location is a remote ftp location, then the maximum value of tmnxSysRollbackIndex can be tmnxSysRollbackMaxRemoteFiles minus 1. This index is SET along with another action object, including tmnxSysRollbackStart to initiate a rollback revert of a file and tmnxSysRollbackFileDelete to delete a rollback file. An SNMP GET request on this object should return the last SET value.

The value of tmnxSysRollbackStart indicates whether to revert the rollback file specified by tmnxSysRollbackIndex. When SET to the value of 'doAction' the system will revert the rollback file specified by tmnxSysRollbackIndex. This variable must be set along with tmnxSysRollbackIndex to indicate the specific rollback file to revert. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackResult indicates the result of the last tmnxSysRollbackStart action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed interrupted (5) The action was interrupted Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3, 'interrupted': 5.

The value of tmnxSysRollbackSave indicates whether to save the existing configuration in a rollback checkpoint file. When SET to the value of 'doAction' the system will save the configuration in a new rollback checkpoint file, with suffix '.rb'. Previously saved rollback files with the same name will increment the filename suffix by 1 upto a maximum of 9. For example, file.rb is moved to file.rb.1. The higher the number, the older the file is. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackSaveResult indicates the result of the last tmnxSysRollbackSave action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of tmnxSysRollbackLocation specifies the destination filepath or file-URL where the current running configuration information will be saved when tmnxSysRollbackSave is set to 'doAction'. If the value of tmnxSysRollbackLocation is an empty string the system will attempt to store the file in the best available location locally, for example compact flash 1 or 2 if either is present.

The value of tmnxSysRollbackRevertIndex indicates the last rollback checkpoint file reverted on the system.

The value of tmnxSysRollbackRevertEndTime indicates the timestamp the last rollback revert on the system is completed.

The value of tmnxSysRollbackSavedTime indicates the timestamp the last rollback save on the system is completed.

The value of tmnxSysRollbackRevertStartTime indicates the timestamp the last rollback file reverted on the system is initiated.

The value of tmnxSysRollbackRevertUserName indicates the name of a system user who initiates the last rollback revert.

The value of tmnxSysRollbackRevertFilename specifies the filepath or file-URL of the last reverted rollback file.

The value of the object tmnxSysRollbackSaveComment specifies a user provided comment related to the rollback checkpoint file about to be saved. It consists of any printable, seven-bit ASCII characters up to 255 characters in length.

The value of tmnxSysRollbackFileDelete specifies whether to delete the rollback file specified by tmnxSysRollbackIndex. When SET to the value of 'doAction' the system will delete the rollback file specified by tmnxSysRollbackIndex. This variable must be set along with tmnxSysRollbackIndex to specify the specific rollback file to delete. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackFileDeleteResult indicates the result of the last tmnxSysRollbackFileDelete action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of tmnxSysRollbackAbortRevert indicates whether to abort the rollback revert that's currently in progress. When SET to the value of 'doAction' the system will abort the active rollback revert. This will leave the system in an unknown state, so it should be used with care. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackRescueLocation specifies the destination file path or file-URL where the rollback rescue configuration file will be saved. If the value of tmnxSysRollbackRescueLocation is an empty string the system will attempt to store the file in the best available location locally, for example compact flash 1 or 2 if either is present.

The value of tmnxSysRollbackRescueRevert indicates whether to revert the rollback rescue file located in tmnxSysRollbackRescueLocation. When SET to the value of 'doAction' the system will revert the rollback rescue file. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackRescueSave indicates whether to save the existing configuration in the rollback rescue file located in tmnxSysRollbackRescueLocation. When SET to the value of 'doAction' the system will save the configuration to the rollback rescue file. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackRescueDelete specifies whether to delete the rollback rescue file located in tmnxSysRollbackRescueLocation. When SET to the value of 'doAction' the system will delete the rollback rescue file. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackRescueSaveRes indicates the result of the last tmnxSysRollbackRescueSave action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of tmnxSysRollbackRescueRevertRes indicates the result of the last tmnxSysRollbackRescueRevert action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed interrupted (5) The action was interrupted Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3, 'interrupted': 5.

The value of tmnxSysRollbackRescueDeleteRes indicates the result of the last tmnxSysRollbackRescueDelete action. none(1) None of the following apply inProgress(2) The action is still in progress success(3) The action completed successfully failed(4) The action failed Enumeration: 'failed': 4, 'none': 1, 'inProgress': 2, 'success': 3.

The value of tmnxSysRollbackRescueSavedTime indicates the timestamp the last rollback rescue save on the system is completed.

The value of tmnxSysRollbackRescueRevStTime indicates the timestamp the last rescue rollback file reverted on the system is initiated.

The value of tmnxSysRollbackRescueRevEdTime indicates the timestamp the last rollback rescue revert on the system is completed.

The value of tmnxSysRollbackRescueRevUser indicates the name of a system user who initiates the last rollback rescue revert.

The value of the object tmnxSysRollbackRescueSaveComment specifies a user provided comment related to the rollback rescue file about to be saved. It consists of any printable, seven-bit ASCII characters up to 255 characters in length.

The value of tmnxSysRollbackRescueAbortRevert indicates whether to abort the rescue revert that's currently in progress. When SET to the value of 'doAction' the system will abort the active rollback revert. This will leave the system in an unknown state, so it should be used with care. An SNMP GET request on this object should return 'notApplicable'.

The value of tmnxSysRollbackRescueFileExists indicates whether a rollback rescue file specified by tmnxSysRollbackRescueLocation and suffix '.rc' is present. A value of 'true' indicates the file is present and a value of 'false' indicates the file is not present.

The value of tmnxSysRollbackMaxLocalFiles indicates the maximum number of rollback checkpoint files that can be saved locally on the compact flash.

The value of tmnxSysRollbackMaxRemoteFiles indicates the maximum number of rollback checkpoint files that can be saved at a remote ftp location.

The value of tmnxSysRollbackTableLastChanged indicates the timestamp of the last configuration changes to any of the rows in tmnxSysRollbackFileTable.

The table tmnxSysRollbackFileTable contains information pertaining to an entry for each rollback checkpoint file. If the configured rollback location as specified by tmnxSysRollbackLocation is on compact flash, this table can have upto a maximum of tmnxSysRollbackMaxLocalFiles. If the configured rollback location as specified by tmnxSysRollbackLocation is a remote ftp location, this table can have upto a maximum of tmnxSysRollbackMaxRemoteFiles.

Each row entry contains information about a rollback checkpoint file.

The value of tmnxSysRollbackFileIndex specifies the index of the rollback checkpoint file.

The value of tmnxSysRollbackFileCreationTime indicates the timestamp of the creation time of this row in tmnxSysRollbackFileTable.

The value of the object tmnxSysRollbackFileComment specifies a user provided comment related to a rollback checkpoint file. It consists of any printable, seven-bit ASCII characters up to 255 characters in length.

The value of tmnxSysRollbackFileUserName indicates the name of a system user who saves this rollback file.

The value of tmnxSysRollbackFileVersion indicates the version number of the software running on the system when the rollback file is saved.

This object gives the currently active (booted) value of li-separate. This value specifies whether or not a non-LI user has access to Lawful Intercept (LI) information. When sbbiLiSeparate has a value of 'true', a user who does not have the TMETRA-SECURITY-MIB:: tmnxUserAccess 'li' bit set will not be allowed to access CLI or SNMP objects in the 'li' context.

This object gives the currently active (booted) value of li-local-save. This value specifies whether or not Lawful Intercept (LI) configuration is allowed to be save to a local file.

The date and time changed event is generated when the time on the system is modified either by explicit setting or automatic update in case of SNTP.

The save config succeeded event is generated when the saving of configuration finishes without errors.

The save config failed event is generated when the saving of configuration is stopped due to errors.

The sbiBootConfig notification is generated upon completion of the configuration phase following a system reboot.

The sbiBootSnmpd notification is generated upon completion of the SNMP daemon initialization following a system reboot. Some system configuration and initialization errors may result in the SNMP daemon being suspended.

The radiusServerOperStatusChange notification is generated when the operational status of a RADIUS server has transitioned either from 'up' to 'down' or from 'down' to 'up'. This object was made obsolete in the 5.0 release.

The radiusOperStatusChange notification is generated when the radiusOperStatus has transitioned either from 'up' to 'down' or from 'down' to 'up'

A tmnxConfigModify notification is generated when a configuration attribute associated with a row entry in a MIB table is modified. It can be used by the NMS to trigger maintenance polls of the configuration information.

A tmnxConfigCreate notification is generated when a new row entry is created in one of the MIB tables. It can be used by the NMS to trigger maintenance polls of the configuration information.

A tmnxConfigDelete notification is generated when an existing row entry in one of the MIB tables is deleted. It can be used by the NMS to trigger maintenance polls of the configuration information.

A tmnxStateChange notification is generated when there is a change in either the administrative or operational state of a MIB table entry.

A tmnxModuleMallocFailed notification is generated when a request to allocate memory from a particular module fails because the memory module is short on memory and cannot support the size that was requested.

A tmnxTrapDropped notification is generated when a trap is dropped for the reason specified by the reason code. The tmnxTrapDroppedEntryID identifies the table entry associated with the dropped trap.

The ssiSyncConfigOK event is generated when the synchronization of configuration files between the primary and secondary CPMs finishes without errors.

The ssiSyncConfigFailed event is generated when the synchronization of configuration files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state reason for failure.

The ssiSyncBootEnvOK event is generated when the synchronization of boot environment files between the primary and secondary CPMs finishes without errors.

The ssiSyncBootEnvFailed event is generated when the synchronization of boot environment files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state reason for failure.

The sntpTimeDiffExceedsThreshold event is generated when the time differential between the system and the SNTP server is more than 10 seconds. In this case the system clock is not automatically adjusted.

The tacplusServerOperStatusChange notification is generated when the operational status of a TACACS+ server has transitioned either from 'up' to 'down' or from 'down' to 'up'. This object was made obsolete in the 5.0 release.

The tacplusOperStatusChange notification is generated when the tacplusOperStatus has transitioned either from 'up' to 'down' or from 'down' to 'up'

The tmnxSnmpdError notification is generated when the SNMP daemon detects an error condition.

The tmnxSsiMismatch notification is generated by a system with redundant CPM cards after the processing of the bootup configuration has completed when ssiSyncMode has a value of 'none' and sbiPersist has a value of 'true'. This can result in SNMP indexes having different values following a system failover.

The tmnxSnmpdStateChange notification is generated whenever there is a change in either the administrative or operational state of the SNMP agent.

The ssiRedStandbySyncing notification is generated when synchronization of redundancy information onto the standby CPM is started. tmnxChassisNotifyHwIndex identifies the standby CPM.

The ssiRedStandbyReady notification is generated when the synchronization of redundancy information onto the standby CPM has completed. The standby CPM is now ready to take over control of the system if the active CPM fails or a manual switchover command is issued. tmnxChassisNotifyHwIndex identifies the standby CPM.

The ssiRedStandbySyncLost notification is generated when the active CPM looses communication with the standby CPM. tmnxChassisNotifyHwIndex identifies the lost standby CPM.

The ssiRedSwitchover notification is generated when the standby CPM detects that the active CPM has failed and the standby prepares to take over as the new active CPM. tmnxChassisNotifyHwIndex identifies the new active CPM.

The ssiRedCpmActive notification is generated following a redundancy switchover when the new active CPM has completed its audit and is ready to accept management commands via CLI or SNMP SET requests. tmnxChassisNotifyHwIndex identifies the new active CPM.

The ssiRedSingleCpm notification is generated by a system with a chassis with two CPM slots when the active CPM cannot detect a standby CPM in the chassis. When the operating state of TIMETRA-CHASSIS-MIB::tmnxCpmCardRedundant for the active CPM card transitions to a value of 'singleton (1)', this notification is generated. tmnxChassisNotifyHwIndex identifies the singleton CPM. When the active CPM later detects a standby CPM in the chassis, the ssiRedStandbySyncing event will be generated followed by a ssiRedStandbyReady event to indicate clearing of the CPM singleton state. The value of tmnxCpmCardRedundant will then transition to 'redundantActive (2)'.

The persistencyClosedAlarmRaised notification is generated when the system is unable to store persistency data (e.g. because the device is inaccessible, or full).

The persistencyClosedAlarmCleared notification is generated when the output device used to store the persistence data is available for use again.

The tmnxSntpOperChange notification is generated whenever there is a change in the operational state of SNTP.

The tmnxSysTimeSet notification is generated whenever system time is set by NTP, SNTP, SNMP, Real Time Clock(RTC) or if it was set manually.

The tmnxFtpClientFailure notification is generated when a file transfer operation initiated by the FTP client fails.

The tacplusInetSrvrOperStatusChange notification is generated when the operational status of a TACACS+ server has transitioned either from 'up' to 'down' or from 'down' to 'up'.

The radiusInetServerOperStatusChange notification is generated when the operational status of a Radius server has transitioned either from 'up' to 'down' or from 'down' to 'up'.

The persistencyEventReport notification is generated when a client-specific persistence event occurs (e.g. the start and completion of a recover action after system startup).

The sbiBootConfigFailFileError notification is generated when sbiBootConfigFailScript file cannot be accessed.

The sbiBootConfigOKFileError notification is generated when sbiBootConfigOKScript file cannot be accessed.

The sbiBootLiConfig notification is generated upon completion of the Lawful Intercept (LI) configuration phase following a system reboot. This notification is generated periodically, about once an hour. This event is generated only from the LI context.

The persistenceRestoreProblem notification is generated when an an error is detected while processing a persistence record.

[CAUSE] The tmnxSysRollbackStarted notification is generated when the user initiates a revert of the rollback checkpoint file specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. The value of tmnxLogExecRollbackOpIndex indicates the row entry in the TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this rollback revert operation. [EFFECT] The specified file is executed and system configuration may change. [RECOVERY] There is no recovery required for this notification.

[CAUSE] The tmnxSysRollbackStatusChange notification is generated upon the completion of a rollback revert as specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. The value of tmnxLogExecRollbackOpIndex indicates the row entry in the TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this rollback revert operation. [EFFECT] The result is indicated by the value of tmnxSysRollbackResult. [RECOVERY] When the value of tmnxSysRollbackResult is none, inProgress or success no recovery is required. When the value is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by reverting back to a known good checkpoint. The user may reboot the system with the bof pointing to a saved configuration file.

[CAUSE] The tmnxSysRollbackSaveStatusChange notification is generated upon the completion of a rollback save as specified by tmnxSysRollbackFileType. [EFFECT] The result is indicated by value of tmnxSysRollbackSaveResult. [RECOVERY] When the value of tmnxSysRollbackSaveResult is none, inProgress or success no recovery is required. When the value is is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by attempting the rollback save again.

[CAUSE] The tmnxSysRollbackFileDeleteStatus notification is generated upon the completion of a rollback file delete as specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. [EFFECT] The result is indicated by the value of tmnxSysRollbackFileDeleteResult. [RECOVERY] When the value of tmnxSysRollbackFileDeleteResult is none, inProgress or success no recovery is required. When the value is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by deleting the file again.

[CAUSE] The ssiSyncRollbackOK event is generated when the synchronization of rollback files between the primary and secondary CPMs finishes without errors. [EFFECT] Rollback files are synchronized. [RECOVERY] No recovery is necessary.

[CAUSE] The ssiSyncRollbackFailed event is generated when the synchronization of rollback files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state the reason for the failure. [EFFECT] Rollback files are not synchronized. [RECOVERY] The user should try to determine the cause of the failure and can attempt synchronizing the files again.

[CAUSE] The ssiSyncCertOK event is generated when the synchronization of certificate files between the primary and secondary CPMs finishes without errors. [EFFECT] Certificate files are synchronized. [RECOVERY] No recovery is necessary.

[CAUSE] The ssiSyncCertFailed event is generated when the synchronization of certificate files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state the reason for the failure. [EFFECT] Certificate files are not synchronized. [RECOVERY] The user should try to determine the cause of the failure and can attempt synchronizing the files again.

The persistencyFileSysThresRaised notification is generated when the filesystem reaches 90 percent occupation.

The persistencyFileSysThresCleared notification is generated when the filesystem drops below 90 percent occupation.

[CAUSE] The tmnxSysExecStarted notification is generated when the user initiates a CLI 'exec' operation to process a file of SROS CLI commands. The value of tmnxSysExecScript indicates the command file. The value of tmnxLogExecRollbackOpIndex indicates the row entry in TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this CLI 'exec' operation. [EFFECT] The specified CLI configuration file is executed and the system configuration may have changed. [RECOVERY] There is no recovery required for this notification.

[CAUSE] The tmnxSysExecFinished notification is generated upon the completion of the execution of a CLI command file indicated by the value of tmnxSysExecScript. The value of tmnxLogExecRollbackOpIndex indicates the row entry in TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this CLI 'exec' operation. [EFFECT] The success or failure result is indicated by the value of tmnxSysExecResult. [RECOVERY] When the value of tmnxSysExecResult is 'none' or 'success', no recovery is required. When the value is 'fail', the system may be left in an inconsistent state and the user should try to determine the reason for the failure. The user can attempt a recovery by manually entering CLI commands to reverse the failed configuration. The user can attempt a recovery by performing a rollback revert to a known good checkpoint. The user can attempt a recovery by rebooting the system with the bof pointing to a saved configuration file.

[CAUSE] The tmnxSysRollbackSaveStarted notification is generated when the user initiates a rollback save as specified by tmnxSysRollbackFileType. [EFFECT] The specified configuration file is saved. [RECOVERY] There is no recovery required for this notification.

[CAUSE] The tmnxSysRollbackDeleteStarted notification is generated when the user initiates a rollback delete as specified by by tmnxSysRollbackIndex and tmnxSysRollbackFileType. [EFFECT] The specified configuration file is deleted. [RECOVERY] There is no recovery required for this notification.

[CAUSE] The tmnxSysNvsysFileError notification is generated when there is a failure in accessing the nvsys file as specified by tmnxSysFileErrorType. [EFFECT] The specified nvsys file operation is unsuccessful. [RECOVERY] The user should investigate why the failure occurred. A failure can indicate a problem with the compact flash.