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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

icating the clear of a chassis notification
identified by tmnxChassisNotifyOID.

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

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

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

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 one of the chassis's power supplies fails.

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

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

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

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

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.

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.

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.

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.

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

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 one of the chassis's power supplies is inserted.

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

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

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

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

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.

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

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

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.

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

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