ALCATEL-IND1-TIMETRA-CHASSIS-MIB: View SNMP OID List / Download MIB

This document is the SNMP MIB module to manage and provision the hardware components of the Alcatel 7x50 device. Copyright 2003-2008 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's proprietary intellectual property. Alcatel retains all title and ownership in the Specification, including any revisions. Alcatel grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

The compliance statement for management of chassis features in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features for the 7710 in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features for the 7710 in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features for the 7710 in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features on the 7750 in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The compliance statement for management of chassis features on the 7450 in the ALCATEL-IND1-TIMETRA-CHASSIS-MIB.

The group of objects supporting chassis hardware notifications on Alcatel 7x50 SR series systems.

The group of notifications supporting the management of chassis hardware made obsolete for revision 2.1 on Alcatel 7x50 SR series systems.

The group of objects supporting management of chassis hardware capabilities on release 3.0 of Alcatel 7x50 SR series systems.

The group of objects supporting management of MDAs on Alcatel 7x50 SR series systems.

The group of objects supporting the allowed types of CPM cards, IOM cards and MDA made obsolete for revision 3.0 on Alcatel 7x50 SR series systems.

The group of objects supporting management of hardware cards on Alcatel 7x50 SR series systems.

The group of objects supporting management of MDAs for release 4.0 on Alcatel 7x50 SR series systems.

The group of notifications supporting the management of chassis hardware for release 4.0 on Alcatel 7x50 SR series systems.

The group of objects supporting management of hardware specific to the Alcatel 7710 SR series systems.

The group of objects supporting management of chassis hardware capabilities on release 5.0 of Alcatel 7x50 SR series systems.

The group of onbsolete objects for managing the chassis hardware capabilities on release 5.0 of Alcatel 7x50 SR series systems.

The group of objects supporting management of CES MDAs for release 6.0 on Alcatel 77x0 SR series systems.

The group of notifications supporting the management of chassis hardware for release 3.0 on Alcatel 7x50 SR series systems.

The group of notifications supporting the management of chassis hardware for release 6.0 on Alcatel 7x50 SR series systems.

The group of objects supporting management of 'Synchronous Equipment Timing' (SETS) when the references are of type 'Building Integrated Timing Supply' (BITS) for release 6.0 on Alcatel 7710 SR series systems.

The group of objects supporting management of Multicast Path Management feature for release 6.0 on Alcatel 7x50 SR series systems.

The group of objects supporting named buffer pools for release 6.0 on Alcatel 7x50 SR series systems.

The group of objects added in 6.0 release to support chassis hardware notifications on Alcatel 7x50 SR series systems.

The number of chassis installed in this system. For the first release of the Alcatel 7x50 series product, there is only 1 chassis per system. A multi-chassis system model is supported to allow for future product expansion.

The value of sysUpTime when the tmnxChassisTable was last changed.

The chassis table has an entry for each chassis in the system.

Each row entry represents a chassis in the system. The agent creates the row for the first chassis in the system, with tmnxChassisIndex = 1, which is auto-discovered by the active CPM card. Additional chassis entries can be created and deleted via SNMP SET operations. Creation requires a SET request containing at least tmnxChassisAdminMode and tmnxChassisRowStatus. Note that the first Alcatel 7x50 series product release does not support multiple chassis, therefore there will not be more than one row entry in this table; attempts to create additional rows in this table will be denied.

The unique value which identifies this chassis in the system. The first release of the product only supports a single chassis in the system.

The row status. The creation or deletion of a chassis entry causes creation or deletion of corresponding entries in the tmnxCardTable with the same tmnxChassisIndex value. Note, the agent will disallow chassis deletion if its entries in the card table have not first been put into the proper state for removal. The row entry for tmnxChassisIndex equal 1 cannot be deleted.

The administrative name assigned this chassis. Setting tmnxChassisName to the empty string, ''H, resets tmnxChassisName to the TiMOS default value.

The type of chassis used in this Alcatel 7x50 system. The value of tmnxChassisType is the tmnxChassisTypeIndex for the entry in the tmnxChassisTypeTable that represents the Alcatel 7x50 SR series chassis model for this system. Chassis types are distinguished by their backplane type.

A user supplied string that indicates the on site location of this chassis. This could used for a Common Language Location Identifier, CLLI, code string if desired. A CLLI code is an 11-character standardized geographic identifier that uniquely identifies the geographic location of places and certain functional categories of equipment unique to the telecommunications industry. All valid CLLI codes are created, updated and maintained in the Central Location Online Entry System (CLONES) database.

A user supplied string that indicates the Global Positioning System (GPS) coordinates for the location of this chassis. N 45 58 23, W 34 56 12 N37 37' 00 latitude, W122 22' 00 longitude N36*39.246' W121*40.121' Two-dimensional GPS positioning offers latitude and longitude information as a four dimensional vector: where Direction is one of the four basic values: N, S, W, E; hours ranges from 0 to 180 (for latitude) and 0 to 90 for longitude, and, finally, minutes and seconds range from 0 to 60. Thus is an example of longitude and is an example of latitude. Four bytes of addressing space (one byte for each of the four dimensions) are necessary to store latitude and four bytes are also sufficient to store longitude. Thus eight bytes total are necessary to address the whole surface of earth with precision down to 0.1 mile! Notice that if we desired precision down to 0.001 mile (1.8 meters) then we would need just five bytes for each component, or ten bytes together for the full address (as military versions provide).

The number of slots in this chassis that are available for plug-in cards. This includes both fabric and IOM cards

The total number of ports currently installed in this chassis. This count does not include the Ethernet ports on the CPM cards that are used for management access.

The total number of power supplies installed in this chassis.

The total number of fan trays installed in this chassis.

The total number of fans installed in this chassis.

The current state of the Critical LED in this chassis.

The current state of the Major LED in this chassis.

The current state of the Minor LED in this chassis.

The base chassis ethernet MAC address. Special purpose MAC addresses used by the system software are constructed as offsets from this base address.

A Common Language Location Identifier (CLLI) code is an 11-character standardized geographic identifier that uniquely identifies the geographic location of places and certain functional categories of equipment unique to the telecommunications industry. If the set on this object specifies a non-null string, the string will automatically be truncated or padded(with spaces) to 11 characters.

Setting this tmnxChassisReboot to 'doAction' causes a soft-reboot of the entire chassis including all the CPM and IOM cards. Note that the reboot action is likely to occur before the SNMP SET response can be transmitted.

Setting this tmnxChassisUpgrade to 'doAction' causes an upgrade of all firmware and a reboot of the entire chassis including all the CPM and IOM cards. CAUTION: This upgrade and reboot may take several minutes to complete. The chassis MUST NOT be reset or powered down, nor cards inserted or removed, during this process. Any of these prohibited actions may cause the cards to be rendered inoperable. tmnxChassisUpgrade and tmnxChassisReboot must be set together in the same SNMP SET request PDU or else the SET request will fail with an inconsistentValue error. Note that the reboot action is likely to occur before the SNMP SET response can be transmitted.

The value of tmnxChassisAdminMode specifies the scaling and feature set for the IOM cards in the chassis. Setting this variable to 'modeA' causes all IOM cards in the chassis to use the scaling and feature sets supported on the iom-20g card type. Setting tmnxChassisAdminMode to 'modeB' corresponds to the scaling and feature sets supported on the iom-20g-b card type. 'modeC' corresponds to the scaling and feature sets supported on the iom2-20g card type. An attempt to change the value of tmnxChassisAdminMode from 'modeA' to 'modeB' (upgrade) or 'modeC' (upgrade) without also setting tmnxChassisModeForce to a value of 'doAction' in the same SNMP SET request, will fail with an inconsistentValue error if there are any IOM cards in the chassis with a value of 'iom-20g' for tmnxCardAssignedType. An attempt to change the value of tmnxChassisAdminMode from 'modeB' to 'modeC' (upgrade) without also setting tmnxChassisModeForce to a value of 'doAction' in the same SNMP SET request, will fail with an inconsistentValue error if there are any IOM cards in the chassis with a value of 'iom-20g-b' for tmnxCardAssignedType. 'modeB' scaling and feature sets cannot be supported on the iom-20g card. 'modeC' scaling feature set cannot be supported on either on the iom-20g or the iom-20g-b.

The value of tmnxChassisOperMode indicates the operational scaling and feature set for the IOM cards in the chassis. Changing the value of tmnxChassisAdminMode from 'modeB' to 'modeA' (downgrade) will result in tmnxChassisAdminMode indicating 'modeA' while tmnxChassisOperMode indicates 'modeB' untill the configuration is saved and the system rebooted, at which point, the actual downgrade will take effect. Changing the value of tmnxChassisAdminMode from 'modeC' to either 'modeB' (downgrade) or 'modeA' (downgrade) will result in tmnxChassisAdminMode indicating 'modeB' or 'modeA' respectively while tmnxChassisOperMode indicates 'modeC' untill the configuration is saved and the system rebooted, at which point, the actual downgrade will take effect. 'modeB' scaling and feature sets cannot be supported on the iom-20g card. 'modeC' scaling feature set cannot be supported on either on the iom-20g or the iom-20g-b.

Setting tmnxChassisModeForce to a value of 'doAction' in the same SNMP SET request where tmnxChassisAdminMode is set to 'modeB' allows the chassis to be upgraded to 'modeB' even if there are IOM cards in the chassis with a value of 'iom-20g' for tmnxCardAssignedType. Setting tmnxChassisModeForce to a value of 'doAction' in the same SNMP SET request where tmnxChassisAdminMode is set to 'modeC' allows the chassis to be upgraded to 'modeC' even if there are IOM cards in the chassis with a value of 'iom2-20g' for tmnxCardAssignedType. An attempt to set tmnxChassisModeForce to 'doAction' without also setting tmnxChassisAdminMode, in the same SNMP SET request will fail with an inconsistentValue error. ----------------------------------------------------------------------- Mode change | Assigned card | Force | Result ----------------------------------------------------------------------- a to b (upgrade) | iom-20g | not-set | error a to b (upgrade) | iom-20g | set | mode b with warnings a to b (upgrade) | iom-20g-b | not-set | mode b a to b (upgrade) | iom-20g-b | set | mode b a to c (upgrade) | iom-20g | not-set | error a to c (upgrade) | iom-20g | set | mode c with warnings a to c (upgrade) | iom2-20g | not-set | mode c a to c (upgrade) | iom2-20g | set | mode c b to c (upgrade) | iom-20g-b | not-set | error b to c (upgrade) | iom-20g-b | set | mode c with warnings b to c (upgrade) | iom2-20g | not-set | mode c b to c (upgrade) | iom2-20g | set | mode c b to a (downgrade)| iom-20g | not-set | mode a on save and reboot b to a (downgrade)| iom-20g | set | mode a on save and reboot b to a (downgrade)| iom-20g-b | not-set | mode a on save and reboot b to a (downgrade)| iom-20g-b | set | mode a on save and reboot c to a (downgrade)| iom-20g | not-set | mode a on save and reboot c to a (downgrade)| iom-20g | set | mode a on save and reboot c to a (downgrade)| iom2-20g | not-set | mode a on save and reboot c to a (downgrade)| iom2-20g | set | mode a on save and reboot c to b (downgrade)| iom-20g-b | not-set | mode b on save and reboot c to b (downgrade)| iom-20g-b | set | mode b on save and reboot c to b (downgrade)| iom2-20g | not-set | mode b on save and reboot c to b (downgrade)| iom2-20g | set | mode b on save and reboot -----------------------------------------------------------------------

The value of tmnxChassisUpdateWaitTime specifies the time to wait before rebooting IOM cards running older software versions following a software upgrade or downgrade activity switchover. This object was obsoleted in release 5.0.

Following a software upgrade or downgrade activity switchover, the value of tmnxChassisUpdateTimeLeft indicates the time remaining before IOM cards or MDAs running older software versions will be rebooted.

The current Over Temperature state of this chassis. stateOk Indicates chassis is below the temperature threshold. stateOverTemp Indicates chassis is above the temperature threshold. Enumeration: 'stateOk': 1, 'stateOverTemp': 2.

This table contains information about fan trays.

Contains information regarding a fan tray.

The unique value which identifies a specific fan tray in the chassis.

Current status of the Fan tray.

The value of tmnxChassisFanSpeed indicates if the fans in this fan tray are running at 'halfSpeed' or 'fullSpeed'. Enumeration: 'unknown': 1, 'halfSpeed': 2, 'fullSpeed': 3.

This table contains information about power supply trays.

Contains information regarding a power supply tray.

The unique identifier index for a power supply tray in the chassis.

If the value of tmnxChassisPowerSupplyACStatus is 'deviceStateOk', the input AC voltage is within range. If the value is 'deviceStateFailed', an AC voltage out of range condition has been detected. A value of 'deviceNotEquipped' indicates that the AC power supply is not present.

If the value of tmnxChassisPowerSupplyDCStatus is 'deviceStateOk', the input DC voltage is within range. If the value is 'deviceStateFailed', an DC voltage out of range condition has been detected. A value of 'deviceNotEquipped' indicates that the DC power supply is not present.

If the value of tmnxChassisPowerSupplyTempStatus is 'deviceStateOk', the current temperature is within acceptable range. If the value is 'deviceStateFailed', a temperature too high condition has been detected.

The temperature threshold for this power supply tray in degrees celsius. When the temperature raises above tmnxChassisPowerSupplyTempThreshold, a 'temperature too high' event will be generated.

The overall status of an equipped power supply. For AC multiple power supplies, this represents the overall status of the first power supply in the tray (or shelf). For any other type, this represents the overall status of the power supply. If tmnxChassisPowerSupply1Status is 'deviceStateOk', then all monitored statuses are 'deviceStateOk'. A value of 'deviceStateFailed' represents a condition where at least one monitored status is in a failed state.

The overall status of an equipped power supply. For AC multiple power supplies, this represents the overall status of the second power supply in the tray (or shelf). For any other type, this field is unused and set to 'deviceNotEquipped'. If tmnxChassisPowerSupply2Status is 'deviceStateOk', then all monitored statuses are 'deviceStateOk'. A value of 'deviceStateFailed' represents a condition where at least one monitored status is in a failed state.

tmnxChassisPowerSupplyAssignedType configures the type of power supply for a platform. Based on the value assigned to this object, various power supply monitoring signals will be interpreted. For example, if a platform is provisioned to use DC power supplies, then the signal that indicates an AC power supply is missing can be ignored. This is required for proper generation of traps and LED management. Enumeration: 'none': 0, 'acSingle': 2, 'dc': 1, 'acMultiple': 3.

If the value of tmnxChassisPowerSupplyInputStatus is 'deviceStateOk', the input voltage of the power supply is within range. If the value is 'deviceStateFailed', an input voltage out of range condition has been detected. A value of 'deviceNotEquipped' indicates that the power supply is not present.

If the value of tmnxChassisPowerSupplyOutputStatus is 'deviceStateOk', the output voltage of the power supply is within range. If the value is 'deviceStateFailed', an output voltage out of range condition has been detected. A value of 'deviceNotEquipped' indicates that the power supply is not present.

The chassis type table has an entry for each Alcatel 7x50 SR series chassis model.

Each row entry represents an Alcatel 7x50 SR series Chassis model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Alcatel 7x50 SR series chassis model.

The administrative name that identifies this type of Alcatel 7x50 SR series chassis model. This name string may be used in CLI commands to specify a particular chassis model type.

A detailed description of this Alcatel 7x50 SR series chassis model.

When tmnxChassisTypeStatus has a value of 'true' it indicates that this chassis model is supported in this revision of the management software. When it has a value of 'false' there is no support.

The value of sysUpTime when the tmnxHwTable was last changed.

The tmnxHwTable has an entry for each managed hardware component in the Alcatel 7x50 SR series system's chassis. Examples of these hardware component types are IOM, Fabric, and CPM cards, MCM and CCM, and MDA modules. Similar information for physical ports is in the tmnxPortObjs.

Each row entry represents an Alcatel 7x50 SR series manufactured hardware component. Entries cannot be created and deleted via SNMP SET operations. When an entry is created in one of the card tables, IOM, CPM, Fabric or MDA, a tmnxHwEntry is created for the common hardware management information for that card in that chassis. When the card is removed from the chassis, its corresponding tmnxHwEntry is deleted. The tmnxHwIndex is bitmapped: | 32 25 | 24 17 | 16 9 | 8 1 | +-------------+-------------+-------------+-------------+ | TmnxHwClass | 00000000 | Slot | number | +-------------+-------------+-------------+-------------+ The Slot field is only used for components on cards in slots. It is zero for all others. The number field starts from 1 and indicates which component. E.g. Power supply 1 or 2.

The value of tmnxHwIndex is a unique index that identifies common management information for Alcatel 7x50 SR series manufactured hardware components within the specified chassis.

The value of tmnxHwID is an object identifier that points to the table and row entry with additional management information specific to this hardware component's class.

The tmnxHwMfgString contains unspecified Alcatel 7x50 SR series manufacturing information and includes the Alcatel vendor information.

The tmnxHwMfgBoardNumber contains the part number information.

The unique Alcatel 7x50 SR series serial number of the hardware component.

The manufacturing date of the hardware component in 'mmddyyyy' ascii format.

The value of tmnxHwClass indicates the general hardware type of this component. If no appropriate enumeration exists for this hardware component then the value 'other (1)' is used. If the agent cannot identify this hardware component then the value 'unknown (2)' is used.

The value of tmnxHwName is the name of the component as assigned by the system software itself and is suitable for use in CLI commands. This may be a text name such as 'console' or a port ID such as '2/2'. If there is no predefined name then a zero length string is returned. Note that the value of tmnxHwName for two component entries will be the same if the CLI does not distinguish between them, e.g. the chassis slot-1 and the card in slot-1.

The value of tmnxHwAlias is the administrative name assigned to this hardware component by the CLI user or network manager. It is saved across re-initializations and reboots of the system.

The value of tmnxHwAssetID is an administratively assigned asset tracking identifier for this hardware component. It is saved across re-initializations and reboots of the system. If no asset tracking information is associated with this hardware component, a zero-length string is returned to an SNMP get request. Some hardware components do not have asset tracking identifiers. Components for which tmnxHwIsFRU has a value of 'false' do not need their own unique asset tracking identifier. In this case, the agent denies write access to this object and returns a zero-length string to an SNMP get request.

The Common Language Equipment Identifier, CLEI, code is a unique 10-character identifier, that is fixed by the manufacturer. It consists of ten alphanumeric characters. The first seven characters present a concise summary of an equipment entity's circuit or transport capabilities, e.g., functional, electrical, bandwidth, etc. CLEI codes for plug-in or portable equipment with the same first seven characters (CLEI-7) are considered bidirectionally interchangeable and group under a G level record. Most licensees plug-in inventories and records are controlled at the group level. The eighth character denotes the reference source used for coding the item, and the last two characters denote manufacturing vintage or version, and other complemental information. A ten-character CLEI code that is developed for a specific piece of equipment is unique within the CLEI code universe and is used in A level records; the code is not assigned to any other equipment piece. Equipment is coded to a first or major application. When the same equipment is usable in another application or system, it is not recorded nor are additional codes developed for that purpose.

The value of tmnxHwIsFRU indicates whether or not this hardware component is a Field Replaceable Unit (FRU) or not. Those components that are permanently contained within a FRU have a value of 'false'.

The value of tmnxHwContainedIn is the tmnxHwIndex value for the row entry of the hardware component that contains this component. A value of zero indicates that this component is not contained in any other component.

The value of tmnxHwParentRelPos indicates the relative position of this hardware component among all its 'sibling' components. A sibling component shares the same instance values for tmnxHwContainedIn and tmnxHwClass objects. If the associated value of tmnxHwContainedIn is zero, then the value -1 is returned.

The desired administrative status of this hardware component. Write access will be denied for those components that do not have administrative status. An attempt to set tmnxHwAdminState to 'operateSwitch (5)' will fail if the hardware component is not part of a redundant pair. Some examples of redundant hardware are the CPM cards and fabric cards. Enumeration: 'outOfService': 3, 'diagnose': 4, 'noop': 1, 'operateSwitch': 5, 'inService': 2.

The actual operational status of this hardware component. unknown (1) Status cannot be determined inService (2) Online - If tmnxHwClass has a value of 'ioModule (8)' or 'cpmModule (9), the card is present, booted, configured, and running. outOfService (3) Ready - The hardware component is OK but is down because tmnxHwAdminState has a value of 'outOfService (3)'. diagnosing (4) Not implemented. failed (5) This hardware component has failed. The value of tmnxHwFailureReason indicates the type of failure. If tmnxHwClass has a value of 'ioModule(8)' or 'cpmModule(9)', there is a card in the slot but it has failed. booting (6) A card is in the transitional startup state. empty (7) There is no card in the slot and it has not been pre-configured. provisioned (8) There is no card in the slot but it has been pre-configured. unprovisioned (9) There is a card in the slot but it is not configured. upgrade (10) Card software version is compatible with and newer than that running on the current active CPM. downgrade (11) Card software version is compatible with and older than that running on the current active CPM. inServiceUpgrade (12) Card is inService and the card software version is compatible with and newer than that running on the current active CPM. This state applies only to a standby CPM card. This enumeration is no longer supported as of release 5.0. inServiceDowngrade (13) Card is inService and the card software is compatible with and older than that running on the current active CPM. This state applies only to a standby CPM card. This enumeration is no longer supported as of release 5.0. resetPending (14) Card is awaiting reset following an upgrade or downgrade activity switch. The card software version is upgrade or downgrade compatible but will be reset in order to update it to match the active CPM software. The value of tmnxChassisUpdateWaitTime indicates the how long the system will wait following an upgrade or downgrade activity switch before it resets IOM cards. This state applies only to IOM cards. This enumeration is no longer supported as of release 5.0. Enumeration: 'outOfService': 3, 'provisioned': 8, 'upgrade': 10, 'resetPending': 14, 'unknown': 1, 'diagnosing': 4, 'inServiceDowngrade': 13, 'inServiceUpgrade': 12, 'failed': 5, 'unprovisioned': 9, 'booting': 6, 'downgrade': 11, 'empty': 7, 'inService': 2.

The value of tmnxHwTempSensor indicates whether or not this hardware component contains a temperature sensor.

The current temperature reading in degrees celsius from this hardware component's temperature sensor. If this component does not contain a temperature sensor, then the value -1 is returned.

The temperature threshold for this hardware component in degrees celsius. When the value of tmnxHwTemperature raises above tmnxHwTempThreshold, a 'temperature too high' event will be generated.

The version number of boot eprom on the card in this slot. If no specific software program is associated with this hardware component then this object will contain a zero length string.

The software product release version number for the software image currently running on this IOM or CPM card. If no specific software program is associated with this hardware component then this object will contain a zero length string.

The date and time the software running on this IOM or CPM card was last rebooted. If this row entry represents a standby CPM card, the date and time indicated is when the standby completed its initial synchronization process and became ready to take over in case the active card fails or a manual switchover command is issued.

The state of the software running on this IOM or CPM card. The tmnxHwSwState object is obsolete. The Alcatel 7x50 platform cannot distinguish software status separate from the hardware status. Instead of using this object, additional operational states have been added to tmnxHwOperState. If no specific software program is associated with this hardware component then this object will contain a zero. Enumeration: 'swInitted': 6, 'unknown': 0, 'hwFailure': 1, 'swDownloading': 4, 'swFailure': 2, 'swRunning': 7, 'hwInitting': 3, 'swInitting': 5.

The value of tmnxHwAlarmState indicates the current alarm state for this hardware component.

The value of tmnxHwLastAlarmEvent is an object identifier whose object name and instance values point to the row entry in the ALARM-MIB that contains the most recent alarm event associated with this hardware component. If the tmnxHwAlarmState has a value of 'alarmCleared', the most recent alarm event will be in the nlmAlarmClearedTable. If it has a value of 'alarmActive', the entry pointed to is in the nlmAlarmActiveTable. If the value of tmnxHwLastAlarmEvent is '0.0', then either there have not been any alarm events associated with this chassis since the system was last booted, or the last alarm event has aged out and its entry is no longer available in the ALARM-MIB tables.

Setting this action variable causes all the active alarms associated with this hardware component to be moved from the ALARM-MIB nlmActiveAlarmTable to the nlmClearedAlarmTable. This action button is primarily meant for use as a code development aid. This object may be removed from the ALCATEL-IND1-TIMETRA-CHASSIS-MIB before product release.

The value of tmnxHwSwImageSource indicates the location in the Boot Options File (BOF) where the software image file was found when the system last rebooted. Enumeration: 'unknown': 0, 'primary': 1, 'tertiary': 3, 'secondary': 2.

tmnxHwMfgDeviations contains a record of changes done by the manufacturing to the hardware or software and which is outside the normal revision control process.

tmnxHwBaseMacAddress contains the base MAC address of the hardware component. It is applicable only if tmnxHwClass is of type 'chassis', 'ioModule', 'cpmModule' or 'mdaModule'.

tmnxHwFailureReason indicates the reason why a hardware component 'failed' as indicated in tmnxHwOperState.

The tmnxHwContainsTable shows the container/containee relationship between entries in the tmnxHwTable. The hardware component containment tree can be constructed from information in the tmnxHwTable, but this table provides the information in a more convenient format for the manager system to use.

Each row entry represents a single container/containee relationship. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxHwIndex for the contained hardware component.

This table contains information about CCM.

Contains information regarding a CCM.

The unique value which identifies a specific CCM instance in the chassis.

Current status of the CCM.

The value of tmnxCcmHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this CCM.

A bit-mask that identifies the CCM type that is physically inserted into this chassis. There will not be more than one bit set at a time in tmnxCcmEquippedType.

The card type table has an entry for each Alcatel 7710 series Chassis Control Module (CCM) model.

Each row entry represents an Alcatel 7710 series CCM model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Alcatel 7710 series CCM model.

The administrative name that identifies this type of Alcatel 7710 series CCM model. This name string may be used in CLI commands to specify a particular card model type.

A detailed description of this Alcatel 7710 series CCM model.

When tmnxCcmTypeStatus has a value of 'true' it indicates that this CCM is supported in this revision of the management software. When it has a value of 'false' there is no support.

The value of sysUpTime when the tmnxCardTable was last changed.

The tmnxCardTable has an entry for each IOM card slot in each chassis in the TMNX system.

Each row entry represents an IOM card slot in a chassis in the system. Entries cannot be created and deleted via SNMP SET operations. When a tmnxChassisEntry is created, a tmnxCardEntry is created for each IOM card slot in that chassis. Before a tmnxChassisEntry can be deleted, each tmnxCardEntry for that chassis must be in the proper state for removal.

The unique value which identifies this IOM slot within a chassis in the system.

A bit-mask that specifies what card types can be physically supported in this IOM slot in this chassis.

A bit-mask that specifies what IOM card types the administrator has designated be allowed to be inserted into this slot. If the slot has not-been pre-provisioned and a card that does not match one of the allowed types is inserted into this slot, a mis-match alarm will be raised. If a specific value has not yet been SET by the manager, tmnxCardAllowedTypes will return the same value to a GET request as tmnxCardSupportedTypes. The object was made obsolete in the 3.0 release.

A bit-mask that identifies the administratively assigned (pre-provisioned) IOM card type that should occupy this slot in this chassis. If tmnxCardAssignedType has a value of 'unassigned', this slot has not yet been pre-provisioned. There must not be more than one bit set at a time in tmnxCardAssignedType.

A bit-mask that identifies the IOM card type that is physically inserted into this slot in this chassis. If the slot has been pre-provisioned, tmnxCardAssignedType is not equal 'unassigned', and the value of tmnxCardEquippedType is not the same as tmnxCardAssignedType, a mis-match alarm will be raised. If the slot has not been pre-provisioned, and the value of tmnxCardEquippedType is not one of the allowed types as specified by tmnxCardAllowedTypes, a mis-match alarm will be raised. There will not be more than one bit set at a time in tmnxCardEquippedType. A value of 0 indicates the IOM card type is not recognized by the software.

The value of tmnxCardHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this IOM card.

The clock source used by the IOM card in this slot.

The number of Media Dependent Adapter (MDA) slots available on this IOM card.

The number of Media Dependent Adapters installed on this IOM card.

Setting this variable to 'doAction' causes the IOM card to execute a soft-reboot.

The value of tmnxCardMemorySize indicates the amount of memory, in mega-bytes, populated on this IOM card.

The value of tmnxCardNamedPoolAdminMode specifies whether or not an IOM is provisioned for the configuration of named pools. If the value of tmnxCardNamedPoolAdminMode is 'inService(2)', the system will change the way default pools are created and allow for the creation of MDA and port level named buffer pools. If the value of tmnxCardNamedPoolAdminMode is 'outOfService(3)', the system will not create per port pools, instead a default network and access pool is created for ingress and egress and is shared by queues on all ports. This object is used in conjunction with tmnxCardNamedPoolOperMode.

The value of tmnxCardNamedPoolOperMode specifies whether or not an IOM provisioned with tmnxCardNamedPoolAdminMode to a value of 'inService(2)' will activly use named pools or not. A value of 'outOfService(3) means that the named pool configurations will not be downloaded to the IOM until after a reset of the IOM is performed. A value of 'inService(2)' means that the named pool configurations are programmed by the IOM. On systems using a separate CPM and IOM combination the value of tmnxCardNamedPoolOperMode and tmnxCardNamedPoolAdminMode will always be in sync due to a mandatory reboot of the IOM. On systems using a combined image (CFM) these values will be out-of-sync until the chassis is rebooted.

The value of sysUpTime when the tmnxCpmCardTable was last changed.

The tmnxCpmCardTable has an entry for each CPM card or module in each chassis in the TMNX system.

Each row entry represents a CPM card or module in a chassis in the system. Entries cannot be created and deleted via SNMP SET operations. When a tmnxChassisEntry is created, a tmnxCpmCardEntry is created for each CPM card or module in that chassis. Before a tmnxChassisEntry can be deleted, each tmnxCpmCardEntry for that chassis must be in the proper state for removal.

The unique value which identifies this slot within a chassis in the system. Depending upon the value of tmnxChassisType, this may represent a fabric slot or a regular card slot. If this CPM module resides on a fabric card, tmnxCpmCardSlotNum has the value the corresponding tmnxFabricSlotNum. If this is a CPM module on a fabric card, tmnxCpmCardSlotNum is the fabric slot number in the chassis where this CPM module is located. Else if this is a CPM card, tmnxCpmCardSlotNum is a regular card slot number.

The unique value which identifies this CPM module within a specific card slot within a chassis in the system.

A bit-mask that specifies what CPM card types can be physically supported in this slot in this chassis.

A bit-mask that specifies what CPM card types the administrator has designated be allowed to be inserted into this slot. If the slot has not-been pre-provisioned and a card that does not match one of the allowed types is inserted into this slot, a mis-match alarm will be raised. If a specific value has not yet been SET by the manager, tmnxCpmCardAllowedTypes will return the same value to a GET request as tmnxCpmCardSupportedTypes. The object was made obsolete in the 3.0 release.

A bit-mask that identifies the administratively assigned (pre-provisioned) CPM card type that should occupy this slot in this chassis. If tmnxCpmCardAssignedType has a value of 'unassigned', this slot has not yet been pre-provisioned. There must not be more than one bit set at a time in tmnxCpmCardAssignedType.

A bit-mask that identifies the CPM card type that is physically inserted into this slot in this chassis. If the slot has been pre-provisioned, tmnxCpmCardAssignedType is not equal 'unassigned', and the value of tmnxCpmCardEquippedType is not the same as tmnxCpmCardAssignedType, a mis-match alarm will be raised. If the slot has not been pre-provisioned, and the value of tmnxCpmCardEquippedType is not one of the allowed types as specified by tmnxCpmCardAllowedTypes, a mis-match alarm will be raised. There will not be more than one bit set at a time in tmnxCpmCardEquippedType.

The value of tmnxCpmCardHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this CPM card or module.

The version number of boot option file (BOF) read by the CPM card in this slot.

The date and time the boot options file (BOF) for this card was last modified. If tmnxCpmCardBootOptionLastModified is more recent than tmnxHwSwLastBoot, the boot options file has been edited since the software was booted and different software images or configuration will likely be used when this card is next rebooted.

The version of the configuration file read when this CPM card was last rebooted.

The version of the index file read when this CPM card was last rebooted.

The date and time the running configuration was last modified. If tmnxCpmCardConfigLastModified is more recent than tmnxHwSwLastBoot, the current configuration may be different than that in the configuration file read upon system initialization.

The date and time the current configuration was last saved. If tmnxCpmCardConfigLastSaved is more recent the value of tmnxHwSwLastBoot, the initial configuration is likely to be different the next time the system is rebooted.

This variable indicates if the CPM card is standalone or part of a pair of redundant cards. If 'redundantDisabled', tmnxHwOperState indicates the specific reason why this redundant CPM card is not available. Note that the 'redudantSplit' option is not implemented. Enumeration: 'singleton': 1, 'redundantActive': 2, 'redundantDisabled': 5, 'redundantSplit': 4, 'redundantStandby': 3, 'redundantSynching': 6.

The clock source used by the CPM card in this slot.

The value of tmnxCpmCardNumCpus indicates the number of CPU chips populated on this CPM module.

The value of tmnxCpmCardCpuType indicates the type of CPU chips populated on this CPM module. Enumeration: 'unknown': 1, 'pentium-pc': 3, 'mips': 2.

The value of tmnxCpmCardMemorySize indicates the amount of memory, in mega-bytes, populated on this CPM module.

Setting this variable to doAction causes the switchover to the redundant CPM card.

Setting this variable to 'doAction' causes the CPM card to execute a soft-reboot.

Setting this variable to 'doAction' causes the Boot Options File (BOF) to be reread and applied.

tmnxCpmCardConfigFileLastBooted indicates the location and name of the configuration file from which the system last rebooted.

tmnxCpmCardConfigFileLastSaved indicates the location and name of the file to which the configuration was last saved.

tmnxCpmCardConfigFileLastBootedHeader contains the header of the configuration file from which the system last rebooted.

tmnxCpmCardIndexFileLastBootedHeader contains the header of the index file from which the system last rebooted.

tmnxCpmCardBootOptionSource indicates the compact flash slot where the Boot Options File (BOF) file was found when the system last rebooted. For example, if the BOF file was found on compact flash slot 1, the value of this variable will be 'cf1:'

The value of tmnxCpmCardConfigSource indicates the location in the Boot Options File(BOF) where the configuration file was found when the system last rebooted. Enumeration: 'unknown': 0, 'primary': 1, 'tertiary': 3, 'secondary': 2.

The date and time the boot options file (BOF) was last saved. If tmnxCpmCardBootOptionLastSaved is more recent than the value of tmnxHwSwLastBoot, the boot options file has been edited since the software was booted and different software images or configuration will likely be used when this card is next rebooted.

The current Master/Slave clocking reference designation. primaryRef Indicates this card is designated as the primary clocking reference in a redundant system. secondaryRef Indicates this card is designated as the secondary clocking reference in a redundant system. notInitialized Indicates the clock is not initialized. Enumeration: 'notInitialized': 3, 'secondaryRef': 2, 'primaryRef': 1.

The value of sysUpTime when the tmnxFabricTable was last changed.

The tmnxFabricTable has an entry for each fabric card slot in each chassis in the TMNX system.

Each row entry represents a fabric card slot in a chassis in the system. Entries cannot be created and deleted via SNMP SET operations. When a tmnxChassisEntry is created, a tmnxFabricEntry is created for each fabric card slot in that chassis. Before a tmnxChassisEntry can be deleted, each tmnxFabricEntry for that chassis must be in the proper state for removal.

The unique value which identifies this fabric slot within a chassis in the system. The CPM cards and IOM cards cannot be physically inserted into the switch fabric card slots. In some models, the CPM is not a separate card, but rather a module on a Fabric card.

The administratively assigned switch fabric card type that should occupy this fabric slot in this chassis.

The switch fabric card type that is physically inserted into this slot in this chassis.

The value of tmnxHwIndex is the index into the tmnxHwTable to locate the row entry that represents the hardware component information for this fabric card.

This table contains information about Flash devices on a CPM card.

Contains information regarding a CPM card's flash unit.

The unique identifier index for a flash device on a CPM card.

Current status of this flash unit on this CPM card.

The serial number for this flash unit on this CPM card.

The firmware revision number for this flash unit on this CPM card.

The model number for this flash unit on this CPM card.

The value of tmnxCpmFlashCapacity indicates the maximum size of this flash unit in 512-byte sectors.

The value of tmnxCpmFlashUsed indicates the amount used, in 512-byte sectors, of this flash unit's total capacity.

The value of tmnxHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this flash unit.

The tmnxMDATable has an entry for each MDA slot in each IOM card in this chassis in the TMNX system.

Each row entry represents a MDA slot in an IOM card in a chassis in the system. Entries cannot be created and deleted via SNMP SET operations. When a tmnxCardEntry has tmnxCardAssignedType or tmnxCardEquippedType equal to an IOM card type that supports MDA slots, a tmnxMDAEntry is created by the agent for each MDA slot on that IOM card. Before a tmnxCardEntry can be deleted, each tmnxMDAEntry for that card must be in the proper state for removal.

The unique value which identifies this MDA slot within a specific IOM card in the system. Rows with a tmnxMDASlotNum value of zero (0) represent the special case of an IOM card without MDA slots but that instead has its ports directly on the IOM card itself. In that case, there should be only that one row entry in the tmnxMDATable for that IOM card.

A bit-mask that specifies what MDA card types can be physically supported in this slot in this chassis.

An integer that specified what MDA card types the administrator has designated be allowed to be inserted into this slot. If the slot has not-been pre-provisioned and a MDA card that does not match one of the allowed types is inserted into this slot, a mis-match alarm will be raised. The object was made obsolete in the 3.0 release.

An integer that indicates the administratively assigned (pre-provisioned) MDA card type that should occupy this slot in this chassis. If tmnxMDAAssignedType has a value of 'unassigned', this slot has not yet been pre-provisioned.

An integer that indicates the MDA card type that is physically inserted into this slot in this chassis. If the slot has been pre-provisioned, tmnxMDAAssignedType is not equal 'unassigned', and the value of tmnxMDAEquippedType is not the same as tmnxMDAAssignedType, a mis-match alarm will be raised. A value of 0 indicates the equipped MDA is not supported by this software release.

The value of tmnxHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this MDA card.

The maximum number of ports that can be equipped on this MDA card.

The value of tmnxMDAEquippedPorts indicates the number of ports equipped on this MDA card.

The transmit timing method which is presently selected and being used by this MDA. tmnxMDATxTimingSelected will be set to 'not-applicable' if this MDA does not use the transmit timing subsystem. Enumeration: 'not-applicable': 5, 'local': 3, 'cpm-card-A': 1, 'cpm-card-B': 2, 'holdover': 4.

Indicates the status of the synchronous equipment timing subsystem. If the tmnxSyncIfTimingRef1Qualified and tmnxSyncIfTimingRef2Qualified are both set to 'not-qualified, then tmnxMDASyncIfTimingStatus is set to 'not-qualified'. If any of the timing references is in use, then tmnxMDASyncIfTimingStatus is set to 'qualified'. tmnxMDASyncIfTimingStatus will be set to 'not-applicable' if this MDA does not use the transmit timing subsystem. Enumeration: 'not-qualified': 2, 'qualified': 1, 'not-applicable': 3.

Specifies the network queue policy being used for this object to define the queueing structure for this object.

tmnxMDACapabilities indicates the capabilities of this MDA. It identifies the type of MDA and the protocols that can run on it. Bits: 'supportsPPP': 3, 'isSonet': 1, 'supportsCEM': 8, 'supportsATM': 5, 'isCMA': 7, 'isTDM': 2, 'isEthernet': 0, 'supportsFR': 4, 'supportscHDLC': 6.

tmnxMDAMinChannelization indicates the minimum size of the channel that can exist on this MDA.

tmnxMDAMaxChannelization indicates the maximum size of the channel that can exist on this MDA.

tmnxMDAMaxChannels is applicable for SONET and TDM MDAs only. It indicates the total number of leaf SONET paths, TDM channels and bundles on the MDA that may be configured to pass traffic.

tmnxMDAChannelsInUse is applicable for SONET and TDM MDAs only. It indicates the total number of leaf SONET paths, TDM channels and bundles on the MDA which are in use. A leaf SONET path or TDM channel which is currently capable of passing traffic is considered to be in use. Also, a SONET path or TDM channel which is channelized and has no subchannels capable of passing traffic is considered to be in use. A SONET path or TDM channel which is channelized and has one or more subchannels capable of passing traffic is not considered to be in use, although the subchannels themselves are considered to be in use. A bundle is considered to be a channel in use as are each of its members since they are TDM channels capable of passing traffic.

When tmnxMDAAssignedType has a value of 'cca' , the value of tmnxMDACcagId specifies the Cross Connect Aggregation Group (CCAG) entry this MDA is provisioned on. If this entry does not represent a 'cca' MDA or is not associated with a CCAG, tmnxMDACcagId has a value of zero.

Setting this variable to 'doAction' causes the MDA to execute a soft-reboot.

The value of tmnxMDAHiBwMcastSource specifies if this MDA should attempt to allocate separate fabric planes to allocate high bandwidth multicast traffic taps. tmnxMDAHiBwMcastGroup must be set in the same SNMP request PDU with tmnxMDAHiBwMcastSource or an 'inconsistentValue' error will be returned.

The value of tmnxMDAHiBwMcastAlarm specifies if a tmnxChassisHiBwMcastAlarm alarm is raised if there are more than one high bandwidth multicast traffic taps sharing a plane.

The value of tmnxMDAHiBwMcastTapCount indicates the number of high bandwidth multicast traffic taps on this MDA.

The value of tmnxMDAHiBwMcastGroup specifies the group of high bandwidth multicast traffic taps to which this tap belongs. A value of '0' specifies that this tap is not a member of any High Bandwidth Multicast group. On an IOM of type 'iom-10g', the value of tmnxMDAHiBwMcastGroup should be the same as the value of tmnxMDAHiBwMcastGroup set on the other MDA residing on the IOM if the tmnxMDAHiBwMcastSource is set to 'true'. Attempt to set to different values will result in an 'inconsistentValue' error. tmnxMDAHiBwMcastGroup must be set in the same SNMP request PDU with tmnxMDAHiBwMcastSource or an 'inconsistentValue' error will be returned.

The value of tmnxMDAClockMode specifies the clock mode of the MDA. notApplicable - The MDA does not support any clock modes or domains. adaptive - The MDA is in 'adaptive' clock mode. This allows adaptive clock domains to be created. differential - The MDA is in 'differential clock mode. This allows differential clock domains to be created. The value of tmnxMDAClockMode can be changed when there are no ports created on the MDA. If there are ports created, a shutdown of the MDA is required in order to change the value. Enumeration: 'notApplicable': 0, 'adaptive': 1, 'differential': 2.

The value of tmnxMDADiffTimestampFreq specifies the differential timestamp frequency of the differential clock on the MDA. The value must be a multiple of 8 KHz. This value can only be changed if the value of tmnxMDAClockMode is 'differential (2)' and there are no ports created on the MDA. If there are ports created, a shutdown of the MDA is required in order to change the value. If the value of tmnxMDAClockMode is 'differential (2) then the default is 103,680 KHz. If the value of tmnxMDAClockMode is not 'differential (2)' then this value is 0 KHz and cannot be changed.

The value of tmnxMDAMcPathMgmtBwPlcyName specifies the multicast policy name configured on the MDA.

The value of tmnxMDAMcPathMgmtPriPathLimit specifies the primary path limit for the MDA.

The value of tmnxMDAMcPathMgmtSecPathLimit specifies the secondary path limit for the MDA.

The value of tmnxMDAMcPathMgmtAncPathLimit specifies the ancillary path limit for the MDA.

The value of tmnxMDAMcPathMgmtAdminState specifies administrative state of this multicast path on the MDA.

The value of tmnxMDAIngNamedPoolPolicy specifies a named pool policy associated with an MDA ingress context. The policy governs the way named pools are created at the MDA level.

The value of tmnxMDAEgrNamedPoolPolicy specifies a named pool policy associated with an MDA egress context. The policy governs the way named pools are created at the MDA level.

The value of tmnxMDAMcPathMgmtPriInUseBw indicates the in use ingress multicast bandwidth for the primary forwarding path.

The value of tmnxMDAMcPathMgmtSecInUseBw indicates the in use ingress multicast bandwidth for the secondary forwarding path.

The value of tmnxMDAMcPathMgmtAncInUseBw indicates the in use ingress multicast bandwidth for the ancillary forwarding path.

The value of tmnxMDAMcPathMgmtBlkHoleInUseBw indicates the bandwidth of the ingress multicast traffic that is being black holed on the MDA.

The card type table has an entry for each Alcatel 7x50 SR series card model.

Each row entry represents an Alcatel 7x50 SR series Card model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Alcatel 7x50 SR series card model.

The administrative name that identifies this type of Alcatel 7x50 SR series card model. This name string may be used in CLI commands to specify a particular card model type.

A detailed description of this Alcatel 7x50 SR series card model.

When tmnxCardTypeStatus has a value of 'true' it indicates that this card model is supported in this revision of the management software. When it has a value of 'false' there is no support.

The MDA type table has an entry for each Alcatel 7x50 SR series MDA card model.

Each row entry represents an Alcatel 7x50 SR series MDA card model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Alcatel 7x50 SR series MDA card model.

The administrative name that identifies this type of Alcatel 7x50 SR series MDA card model. This name string may be used in CLI commands to specify a particular MDA card model type.

A detailed description of this Alcatel 7x50 SR series MDA card model.

When tmnxMdaTypeStatus has a value of 'true' it indicates that this MDA card model is supported in this revision of the management software. When it has a value of 'false' there is no support.

The synchronous interface timing table has an entry for each cpm card in the system.

A row represents the configuration of synchronous equipment timing subsystem (SETS) of the system. Entries cannot be created and deleted via SNMP SET operations. When a tmnxCpmCardEntry is created, a tmnxSyncIfTimingEntry is created. Note that the first Alcatel 7x50 SR series product release does not support configuration of synchronous equipment on the secondary CPM. All SNMP operations with tmnxCpmCardSlotNum of the secondary CPM will be denied. If the value of the reference source port is a valid Port ID then the reference is a port. If the value of the source hardware is a valid non-zero HWIndex then the source is the hardware specified by the HWIndex.

The value of tmnxSyncIfTimingRevert indicates whether the reference source will revert to a higher priority source that has been re-validated or newly validated. The synchronous interface timing subsystem is by default non-revertive ('false').

The value of tmnxSyncIfTimingRefOrder1 indicates the most preferred timing reference source. The synchronous equipment timing subsystem can lock to three different timing reference inputs, reference1, reference2 and bits. The subsystem chooses a reference based on priority.

The value of tmnxSyncIfTimingRefOrder2 indicates the second most preferred timing reference for the synchronous equipment timing subsystem.

The value of tmnxSyncIfTimingRef1SrcPort indicates the source port of the first timing reference. A value of '1e000000'H indicates that there is no source port for this reference.

The value of tmnxSyncIfTimingRef1AdminStatus indicates the administrative status of the first timing reference.

The value of tmnxSyncIfTimingRef1InUse indicates whether the first timing reference is presently being used by the synchronous timing subsystem. If it is in use, tmnxSyncIfTimingFreqOffset indicates the frequency offset for this reference.

The value of tmnxSyncIfTimingRef1Qualified indicates whether the first timing reference is qualified for use by the synchronous timing subsystem. If tmnxSyncIfTimingRef1Qualified is set to 'not-qualified', then the object tmnxSyncIfTimingRef1Alarm gives the reason for disqualification.

The value of tmnxSyncIfTimingRef1Alarm indicates the alarms on the first reference. If any of the bits is set to '1', then the first reference is disqualified by the timing subsystem and the value of tmnxSyncIfTimingRef1Qualified is set to 'not-qualified'. los - loss of signal oof - out of frequency range oopir - out of pull in range

The value of tmnxSyncIfTimingRef2SrcPort indicates the source port of the second timing reference. A value of '1e000000'H indicates that there is no source port for this reference.

The value of tmnxSyncIfTimingRef2AdminStatus indicates the administrative status of the second timing reference.

The value of tmnxSyncIfTimingRef2InUse indicates whether the second timing reference is presently being used by the synchronous timing subsystem.

The value of tmnxSyncIfTimingRef2Qualified indicates whether the second timing reference is qualified for use by the synchronous timing subsystem. If tmnxSyncIfTimingRef2Qualified is 'not-qualified' then the object tmnxSyncIfTimingRef2Alarm gives the reason for disqualification.

The value of tmnxSyncIfTimingRef2Alarm indicates the alarms on the second reference. If any of the bits is set to '1', then the second reference is disqualified by the timing subsystem and the value of tmnxSyncIfTimingRef2Qualified is set to 'not-qualified'. los - loss of signal oof - out of frequency range oopir - out of pull in range

The value of tmnxSyncIfTimingFreqOffset indicates the frequency offset of the current selected timing reference in parts per million (ppm).

The value of tmnxSyncIfTimingStatus indicates the present status of the synchronous timing equipment subsystem (SETS). Enumeration: 'acquiring': 6, 'master-freerun': 2, 'master-holdover': 3, 'not-present': 1, 'master-locked': 4, 'slave': 5.

The value of tmnxSyncIfTimingRefOrder3 is the third most preferred timing reference for the synchronous equipment timing subsystem.

The value of tmnxSyncIfTimingBITSIfType indicates the interface type of the BITS (Building Integrated Timing Supply) timing reference. It also indicates the framing type of the interface.

The value of tmnxSyncIfTimingBITSAdminStatus indicates administrative status of the BITS (Building Integrated Timing Supply) timing reference.

The value of tmnxSyncIfTimingBITSInUse indicates whether the BITS timing reference is presently being used by the synchronous timing subsystem. If it is in use, tmnxSyncIfTimingFreqOffset indicates the frequency offset for this reference.

The value of tmnxSyncIfTimingBITSQualified indicates whether the BITS timing reference is qualified for use by the synchronous timing subsystem. If tmnxSyncIfTimingBITSQualified is 'not-qualified', then the object tmnxSyncIfTimingBITSAlarm gives the reason for disqualification.

The value of tmnxSyncIfTimingBITSAlarm indicates the alarms on the BITS reference. If any of the bits is set to '1', then the BITS reference is disqualified by the timing subsystem and the value of tmnxSyncIfTimingBITSQualified is set to 'not-qualified'.

The value of tmnxSyncIfTimingRef1SrcHw indicates the source HW index of the first timing reference if source is not a port.

The value of tmnxSyncIfTimingRef1BITSIfType indicates the interface type of the first timing reference if the source is BITS. It also indicates the framing type of the interface.

The value of tmnxSyncIfTimingRef2SrcHw indicates the source HW index of the second timing reference if source is not a port.

The value of tmnxSyncIfTimingRef2BITSIfType indicates the interface type of the second timing reference if the source is BITS. It also indicates the framing type of the interface.

The tmnxCcagTable has an entry for each Cross Connect Aggregation Group,CCAG, configured on this system.

Each row entry represents a particular CCAG. Entries are created/deleted by the user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

The value of tmnxCcagId is used to index into the tmnxCcagTable. It uniquely identifies a CCAG entry as configured on this system.

The value of tmnxCcagRowStatus specifies the row status. It allows entries to be created and deleted in the tmnxCcagTable. tmnxCcagRowStatus does not support createAndWait. The status can only be active or notInService.

The value of tmnxCcagLastChanged indicates the time this row was last changed.

The value of tmnxCcagDescription specifies a user provided description string of this CCAG entry.

The value of tmnxCcagAdminStatus specifies the desired state of this CCAG.

The value of tmnxCcagOperStatus indicates the operational state of this CCAG.

The value of tmnxCcagCcaRate specifies the maximum forwarding rate for each CCA member within the CCAG.

The value of tmnxCcagAccessAdaptQos specifies how the CCAG SAP queue and virtual scheduler buffering and rate parameters are adapted over multiple active CCAs. link (1) - The CCAG will create the SAP queues and virtual schedulers on each CCA with the actual parameters specified in the tmnxCcagPathCcTable. distribute (2) - Each CCA will receive a portion of the parameters specified in the tmnxCcagPathCcTable. Enumeration: 'distribute': 2, 'link': 1.

The tmnxCcagPathTable has an entry for each Cross Connect Aggregation Group, CCAG, path configured on this system.

Each row entry represents a particular CCAG Path. Entries are created/deleted by the user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

The value of tmnxCcagPathId is used as the secondary index into the tmnxCcagPathTable. Along with tmnxCcagId, it uniquely identifies a specific path, alpha or beta, on a CCAG. Enumeration: 'alpha': 1, 'beta': 2.

The value of tmnxCcagPathLastChanged indicates the time this row was last changed.

The value of tmnxCcagPathRate specifies the bandwidth rate limitation for this path on each member cross connect adaptor, CCA, in the CCAG.

The value of tmnxCcagPathRateOption specifies whether the rate in tmnxCcagPathRate is defined as an aggregate path rate for all CCAs in the CCAG or as a per CCA path rate.

The value of tmnxCcagPathWeight specifies the scheduling percentage for this path. It is applied to all CCAs in the CCAG membership list for this path.

The tmnxCcagPathCcTable has an entry for each type of Cross Connection on a Cross Connect Aggregation Group Path configured on this system.

Each row entry represents a particular CCAG Path Cross Connect. Entries are created/deleted by the user. There is no StorageType object, entries have a presumed StorageType of nonVolatile.

The value of tmnxCcagPathCcType is used as a third index into the tmnxCcagPathCcTable. Along with tmnxCcagId and tmnxCcagPathId, it uniquely identifies a cross connection type on a specific path in a particular CCAG. The types are: sapsap (1): the cross connection is between two saps, where both services are access. sapnet (2): the cross connection is between a sap and a network service. netsap (3): the cross connection is between a network and a sap service. Enumeration: 'netsap': 3, 'sapsap': 1, 'sapnet': 2.

The value of tmnxCcagPathCcLastChanged indicates the time this row was last changed.

The value of tmnxCcagPathCcEgrPoolResvCbs specifies the percentage of pool size reserved for the committed burst size, CBS. The value '-1' implies that the reserved CBS should be computed as the sum of the CBS requested by the entities using this pool if the application point is 'network'. For 'access' application points the value '-1' means a default of 30%.

The value of tmnxCcagPathCcEgrPoolSlpPlcy specifies the slope policy being used for the egress pool. The Slope policies define the nature of the RED Slopes for the high and the low priority traffic.

The value of tmnxCcagPathCcIngPoolResvCbs specifies the percentage of pool size reserved for the committed burst size, CBS. The value '-1' implies that the reserved CBS should be computed as the sum of the CBS requested by the entities using this pool if the application point is 'network'. For 'access' application points the value '-1' means a default of 30%. tmnxCcagPathCcIngPoolResvCbs does not apply to tmnxCcagPathCcType 'netsap'.

The value of tmnxCcagPathCcIngPoolSlpPlcy specifies the slope policy being used for the ingress pool. The Slope policies define the nature of the RED Slopes for the high and the low priority traffic. tmnxCcagPathCcIngPoolSlpPlcy does not apply to tmnxCcagPathCcType 'netsap'.

The value of tmnxCcagPathCcAcctPolicyId specifies the accounting policy which must be defined prior to associating it with the port. A non-zero value indicates the tmnxLogApPolicyId index identifying the policy entry in the tmnxLogApTable from the TIMETRA-LOG-MIB which is associated with this port. A zero value indicates that there is no accounting policy associated with this port. It is only meaningful when the tmnxCcagPathCcType is 'netsap'.

The value of tmnxCcagPathCcCollectStats specifies whether the collection of accounting and statistical data for the network port is enabled/disabled, 'true'/'false'. When applying accounting policies the data by default will be collected in the appropriate records and written to the designated billing file. When the value is set to false, the statistics are still accumulated by the IOM cards, however, the CPU will not obtain the results and write them to the billing file. If the value of tmnxCcagPathCcType is not 'netsap', the value of this object is meaningless and an attempt to set it will result in an inconsistentValue error.

The value of tmnxCcagPathCcQueuePlcy specifies the network egress queue policy. If the value of tmnxCcagPathCcType is not 'netsap', the value of this object is meaningless and an attempt to set it will result in an inconsistentValue error.

The value of tmnxCcagPathCcMac specifies the MAC address of the virtual LAG that maps to tmnxCcagPathId and tmnxCcagPathCcType. The default value of this object is derived from the chassis MAC address pool.

The value of tmnxCcagPathCcMtu specifies the MTU of the path indexed by tmnxCcagId, tmnxCcagPathId, and tmnxCcagPathCcType. When the value is '0', the real MTU is calculated internally.

The value of tmnxCcagPathCcUserAssignedMac indicates whether the value of tmnxCcagPathCcMac has been explicitly assigned or inherited from tmnxCcagPathCcHwMac, 'true' and 'false', respectively.

The value of tmnxCcagPathCcHwMac is the system assigned MAC address of the virtual LAG that maps to tmnxCcagPathId and tmnxCcagPathCcType. When tmnxCcagPathCcUserAssignedMac is 'false', tmnxCcagPathCcMac inherits its value from this object.

The tmnxMcmTable has an entry for each Mda Carrier module (MCM) on the 7710 system.

Each row entry represents a MCM in a chassis in the 7710 system. Entries in the table cannot be created and deleted via SNMP SET operations. When a tmnxChassisEntry is created, a tmnxMcmEntry is created in the chassis. Before a tmnxChassisEntry can be deleted, each tmnxMcmEntry for the chassis must be in the proper state for removal.

The unique value which identifies this MDA slot within a specific IOM card in the system. Since the MCM occupies two MDA slots in the chassis this value can only be an odd number.

A bit-mask that specifies what MCM types can be physically supported in this chassis.

A bit-mask that identifies the administratively assigned (pre-provisioned) MCM type that should occupy this chassis. If tmnxMcmAssignedType has a value of 'unassigned', this slot has not yet been pre-provisioned. There must not be more than one bit set at a time in tmnxMcmAssignedType.

A bit-mask that identifies the MCM type that is physically inserted into this chassis. If the chassis has been pre-provisioned, tmnxMcmAssignedType is not equal 'unassigned', and the value of tmnxMcmEquippedType is not the same as tmnxMcmAssignedType, a mis-match alarm will be raised. If the chassis has not been pre-provisioned, and the value of tmnxMcmEquippedType is not one of the supported types as specified by tmnxMcmSupportedTypes, a mis-match alarm will be raised. There will not be more than one bit set at a time in tmnxMcmEquippedType.

The value of tmnxMcmHwIndex is the index into the tmnxHwTable for the row entry that represents the hardware component information for this MCM.

The card type table has an entry for each Alcatel 7710 series Mda Carrier Module (MCM) model.

Each row entry represents an Alcatel 7710 series MCM model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Alcatel 7710 series MCM model.

The administrative name that identifies this type of Alcatel 7710 series MCM model. This name string may be used in CLI commands to specify a particular card model type.

A detailed description of this Alcatel 7710 series MCM model.

When tmnxMcmTypeStatus has a value of 'true' it indicates that this MCM is supported in this revision of the management software. When it has a value of 'false' there is no support.

used by tmnx chassis Notifications, the OID indicates the table and entry.

used by tmnx chassis notifications, the OID indicates the table and entry with the equipment model type information.

Used by tmnx chassis and port Notifications, indicates the chassis associated with the alarm.

Used by tmnx chassis and port Notifications, indicates the entry in the tmnxHwTable for the hardware component associated with an alarm.

Used by the tmnxRedSecondaryCPMStatusChange Notification, indicates the status of the secondary CPM. Enumeration: 'fail': 3, 'offline': 2, 'online': 1.

Used by the tmnxChassisNotificationClear trap, the OID identifies the trap which is getting cleared.

Used by tmnx Synchronous interface timing notifications, the value of tmnxSyncIfTimingNotifyAlarm indicates the reason a timing reference alarm has been raised. Enumeration: 'los': 1, 'oof': 2, 'notUsed': 0, 'oopir': 3.

Used by tmnxPeSoftwareVersionMismatch, the value of tmnxChassisNotifyMismatchedVer indicates the software version of the mismatched CPM/IOM card.

Used by tmnxPeSoftwareLoadFailed, the value of tmnxChassisNotifySoftwareLocation contains the location of the software.

Used by tmnxEqCardFailure, the value of tmnxChassisNotifyCardFailureReason contains the reason for card failure.

Used by tmnxEqCardInserted and tmnxEqCardRemoved, the value of tmnxChassisNotifyCardName specifies the name of the affected card.

Who has last initialized the chassis administrative table, who is making all the changes, and who is expected to either commit or re-initialize (ABORT-TRANSACTION). tmnxChassisAdminOwner is advisory only. Before beginning a transaction, read tmnxChassisAdminOwner. if it is empty then proceed with the configuration. Set tmnxChassisAdminOwner after setting tmnxChassisAdminControlApply so that other users will be advised to not make changes to the Admin tables. Agent sets tmnxChassisAdminOwner to empty string after tmnxChassisAdminControlApply is set - either by user initializing or committing, or by agent timing out the uncommitted transactions (tmnxChassisAdminLastSetTimer).

This object controls the use of tmnxChassisAdminTable. when set to initialize(2), the objects in tmnxChassisAdminTable are set to the current Operational values, from the tmnxChassisTable. Any uncommitted changes are lost, so setting this value corresponds to both BEGIN-TRANSACTION and ABORT-TRANSACTION. when set to commit(3) (END-TRANSACTION), all of the objects from tmnxChassisAdminTable are copied to the corresponding tmnxChassisTable table objects. Enumeration: 'initialize': 2, 'commit': 3, 'none': 1.

The time remaining until the agent re-initializes the administrative tables. If tmnxChassisAdminControlApply is not set to commit(3) within tmnxChassisAdminLastSetTimeout centiseconds, the agent will set it to initialize(2) and all uncommitted changes will be lost. This way, uncommitted changes from failed (uncompleted) change sets will eventually be removed, and another transaction can safely begin. this object is reset to tmnxChassisAdminLastSetTimeout after SNMP SET operation to any of the tmnxChassisAdminValue tables.

Timeout for tmnxChassisAdminLastSetTimer. The value zero is not allowed.

Values for the synchronous interface timing for the chassis.

Information about the synchronous interface timing. Entries are created by user. Entries are deleted by user. Note that the first Alcatel 7x50 SR series product release does not support configuration of synchronous timing equipment on the secondary CPM. All SNMP operations with tmnxCpmCardSlotNum of the secondary CPM will be denied. The 7x50 systems supports 3 timing references (reference1, reference2 and bits). The 7710 system only supports 2 timing references (reference1 and reference2). On 7710 system, references can be a source port or a BITS input on a CES CMA. If the value of the reference source port is a valid Port ID then the reference is a source port. If the value of the source hardware is a valid HWIndex of a CES CMA then the source is a BITS on the CES CMA.

The value of tSyncIfTimingAdmRevert specifies whether the reference source will revert to a higher priority source that has been re-validated or newly validated. The synchronous interface timing subsystem is by default non-revertive ('false').

The value of tSyncIfTimingAdmRefOrder1 specifies the most preferred timing reference source. The synchronous equipment timing subsystem can lock to three different timing reference inputs, reference1, reference2 and bits. The subsystem chooses a reference based on priority. tSyncIfTimingAdmRefOrder1 is used to configure the most preferred timing reference.

The value of tSyncIfTimingAdmRefOrder2 specifies the second most preferred timing reference for the synchronous equipment timing subsystem.

The value of tSyncIfTimingAdmRef1SrcPort specifies the source port of the first timing reference. This can only be set to a valid TmnxPortID if the value of tSyncIfTimingAdmRef1SrcHw is 0.

The value of tSyncIfTimingAdmRef1AdminStatus specifies the desired administrative status of the first timing reference.

The value of tSyncIfTimingAdmRef2SrcPort specifies the source port of the second timing reference. This can only be set to a valid TmnxPortID if the value of tSyncIfTimingAdmRef2SrcHw is 0.

The value of tSyncIfTimingAdmRef2AdminStatus specifies the desired administrative status of the second timing reference.

The value of tSyncIfTimingAdmChanged is a bitmask that indicates which objects have been set, but not committed. bit values used here are: 0x0001: tSyncIfTimingAdmRevert 0x0002: tSyncIfTimingAdmRefOrder1 0x0004: tSyncIfTimingAdmRefOrder2 0x0008: tSyncIfTimingAdmRef1SrcPort 0x0010: tSyncIfTimingAdmRef1AdminStatus 0x0020: tSyncIfTimingAdmRef2SrcPort 0x0040: tSyncIfTimingAdmRef2AdminStatus 0x0080: tSyncIfTimingAdmRefOrder3 0x0100: tSyncIfTimingAdmBITSIfType 0x0200: tSyncIfTimingAdmBITSAdminStatus 0x0400: tSyncIfTimingAdmRef1SrcHw 0x0800: tSyncIfTimingAdmRef1BITSIfType 0x1000: tSyncIfTimingAdmRef2SrcHw 0x2000: tSyncIfTimingAdmRef2BITSIfType The agent sets these bits when an object in the row is set. This object is cleared to zero by setting tmnxChassisAdminControlApply to initialize(2) or commit(3).

The value of tSyncIfTimingAdmRefOrder3 indicates the third most preferred timing reference for the synchronous equipment timing subsystem.

The value of tSyncIfTimingAdmBITSIfType specifies the interface type of the BITS (Building Integrated Timing Supply) timing reference.

The value of tSyncIfTimingAdmBITSAdminStatus specifies the desired administrative status of the BITS (Building Integrated Timing Supply) timing reference.

The value of tSyncIfTimingAdmRef1SrcHw specifies the source HW Index of the first timing reference if the source is not a port. This can only be set to a valid HW Index if the value of tSyncIfTimingAdmRef1SrcPort is '1e000000'H.

The value of tSyncIfTimingAdmRef1BITSIfType specifies the interface type of the first timing reference if the source is BITS.

The value of tSyncIfTimingAdmRef2SrcHw specifies the source HW Index of the second timing reference if the source is not a port. This can only be set to a valid HW Index if the value of tSyncIfTimingAdmRef2SrcPort is '1e000000'H.

The value of tSyncIfTimingAdmRef2BITSIfType specifies the interface type of the second timing reference if the source is BITS.

A tmnxHwConfigChange notification is generated when the value of tmnxHwLastChange is updated. It can be used by the NMS to trigger maintenance polls of the hardware configuration information. Only one tmnxHwConfigChange notification event will be generated in a 5 second throttling time period. A notification event is the transmission of a single trap to a list of notification destinations configured in the SNMP-TARGET-MIB. If additional hardware configuration change occurs within the throttling period, the notification events for these changes are suppressed until the throttling period expires. At the end of the throttling period, one notification event is generated if any addition configuration changes occurred within the just completed throttling period and another throttling period is started. The NMS should periodically check the value of tmnxHwConfigChange to detect any missed tmnxHwConfigChange traps. This notification was made obsolete in the 2.1 release. The tmnxHwConfigChange notification has been replaced with the generic change notifications from the TIMETRA-SYSTEM-MIB: tmnxConfigModify, tmnxConfigCreate, tmnxConfigDelete, tmnxStateChange.

Generated when the temperature sensor reading on an equipment object is greater than its configured threshold.

Generated when one of the chassis's power supplies fails.

Generated when one of the chassis's power supplies is inserted.

Generated when one of the chassis's power supplies is removed.

Generated when one of the fans in a fan tray has failed.

Generated when one of the cards in a chassis has failed. The card type may be IOM, Fabric, MDA, MCM, CCM, CPM module, compact flash module, etc. tmnxChassisNotifyCardFailureReason contains the reason for card failure.

Generated when a card is inserted into the chassis. The card type may be IOM, Fabric, MDA, MCM, CCM CPM module, compact flash module, etc.

Generated when a card is removed from the chassis. The card type may be IOM, Fabric, MDA, MCM, CCM, CPM module, compact flash module, etc.

Generated when the wrong type of card is inserted into a slot of the chassis. Even though a card may be physically supported by the slot, it may have been administratively configured to allow only certain card types in a particular slot location. The card type may be IOM, Fabric, MDA, MCM, CPM module, etc.

Generated when a failure is detected for a CPU on an IOM card or CPM module. This notification was made obsolete in the 2.1 release. A cpu failure on a CPM card is detected by the hardware bootup and is indicated by the boot diagnostic display. If there is no working redundant CPM card, the system does not come up. A failure of an IOM card or standby redundant CPM card causes the tmnxEqCardFailure notification to be sent.

Generated when a memory module failure is detected for an IOM card or CPM module. This notification was made obsolete in the 2.1 release. A failure of the memory device is detected by the hardware bootup and is indicated by the boot diagnostic display. If there is no working redundant CPM card, the system does not come up. A failure of the memory device during run-time causes the system to fail and the 'admin tech-support' information to be saved. A failure of an IOM card or standby redundant CPM card causes the tmnxEqCardFailure notification to be sent.

Generated when the backdoor bus has failed. This notification was made obsolete in the 2.1 release.

Generated when a software error has been detected. This notification was made obsolete in the 2.1 release. Many of the other notifications more specifically indicate detection of some type of software error. The 'admin tech-support' information helps developers diagnose a failure of the software in the field.

Generated when the software has abnormally terminated. This notification was made obsolete in the 2.1 release. Many of the other notifications more specifically indicate detection of some type of software error. The 'admin tech-support' information helps developers diagnose a failure of the software in the field.

Generated when there is a mismatch between software versions of the active CPM and standby CPM or the CPM and IOM. tmnxChassisNotifyHwIndex identifies the mismatched CPM/IOM card and tmnxChassisNotifyMismatchedVer will contain the version of the mismatched card. The tmnxHwSoftwareCodeVersion object will contain the expected version.

Generated when there is an out of memory error detected. This notification was made obsolete in the 2.1 release. The tmnxPeOutOfMemory notification has been replaced with the module specific notification from the TIMETRA-SYSTEM-MIB: tmnxModuleMallocFailed.

Generated when a configuration error has been detected. This notification was made obsolete in the 2.1 release. Many other notifications more specifically indicate detection of a configuration error. In most cases the SNMP SET request that tries to make an invalid configuration results in an error response. In some cases the configuration parameters are valid and the SNMP SET request succeeds but the system cannot successfully apply the new parameters. The affected object may then put into an operational 'down' state. A state change notification such as tmnxStateChange or a more specific notification is sent to alert about the problem. For example, an attempt to create an event log with a file-type destination when the specified cflash media is full or not present results in TIMETRA-LOG-MIB notifications tmnxLogSpaceContention, tmnxLogAdminLocFailed, or tmnxLogBackupLocFailed.

Generated when there is a storage capacity problem. This notification was made obsolete in the 2.1 release. The only 'storage' devices on the SR7750 are the cflash drives. Cflash write errors cause a tmnxEqFlashDataLoss notification to be sent. The tmnxEqFlashDiskFull notification is sent when the driver detects that the cflash device is full.

Generated when the CPU cycle usage limit has been exceeded. This notification was made obsolete in the 2.1 release. It does not apply. The SR7750 software architecture does not restrict CPU cycles used by a specific code module.

Generated when the primary CPM fails.

Generated when there is a change in the secondary CPM status. This notification was made obsolete in the 2.1 release. There is no way to administratively enable or disable CPM cards so there is no need for a status change event for administrative state changes. Operational changes detected about the standby CPM card are indicated by more specific notifications such as tmnxEqCardFailure, tmnxEqCardRemoved, tmnxEqCardInserted TIMETRA-SYSTEM-MIB::ssiRedStandbyReady, TIMETRA-SYSTEM-MIB::ssiRedStandbySyncLost, and TIMETRA-SYSTEM-MIB::ssiRedStandbySyncLost.

Generated when the secondary CPM successfully restores the config and state. This notification was made obsolete in the 2.1 release. It does not apply. This event was originally created for an early redundancy mechanism that was never released.

Generated when the secondary CPM fails to restore the config and state. This notification was made obsolete in the 2.1 release. It does not apply. This event was originally created for an early redundancy mechanism that was never released.

A trap indicating the clear of a chassis notification identified by tmnxChassisNotifyOID.

Generated when the synchronous equipment timing subsystem transitions into a holdover state. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when the synchronous equipment timing subsystem transitions out of the holdover state. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when an alarm condition on the first timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when an alarm condition on the first timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when an alarm condition on the second timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when an alarm condition on the second timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

tmnxEqFlashDataLoss is generated when there was an error while data was getting written on to the compact flash. This notification indicates a probable data loss.

tmnxEqFlashDiskFull is generated when there is no space left on the compact flash. No more data can be written to it.

Generated when the CPM fails to load the software from a specified location. tmnxChassisNotifyHwIndex identifies the card for which the software load failed and tmnxChassisNotifySoftwareLocation contains the location from where the software load was attempted.

Generated when there is a mismatch between the CPM and boot loader versions. tmnxChassisNotifyHwIndex identifies the CPM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootloader and tmnxHwSoftwareCodeVersion contains the expected version of the bootloader.

Generated when there is a mismatch between the boot rom versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootrom and tmnxHwSoftwareCodeVersion contains the expected version of the bootrom.

Generated when there is a mismatch between the FPGA versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of FPGA and tmnxHwSoftwareCodeVersion contains the expected version of the FPGA.

Generated when an alarm condition on the BITS timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when an alarm condition on the BITS timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Generated when a card is hot-inserted into the chassis and its firmware is automatically upgraded. The card type may be IOM or CPM module.

The tmnxChassisUpgradeInProgress notification is generated only after a CPM switchover occurs and the new active CPM is running new software, while the IOMs are still running old software. This is the start of the upgrade process. The tmnxChassisUpgradeInProgress notification will continue to be generated every 30 minutes while at least one IOM is still running older software.

The tmnxChassisUpgradeComplete notification is generated to indicate that all the IOMs are running matching software version in reference to the active CPM software version changed as part of the upgrade process.

The tmnxChassisHiBwMcastAlarm notification is generated when a plane is shared by more than one high bandwidth multicast tap.

Generated when a supported MDA is inserted into a slot of an IOM, the MDA is compatible with the currently provisioned MDA, but the current configuration on the MDA's ports is not compatible with the inserted MDA.