CPQ-TRAPS-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CPQ-TRAPS-MIB.
19
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
19 total| Object Name |
|---|
switchFirmwareTransferredThe switch has successfully transferred a firmware image. TRAP-TYPE .1.3.6.1.4.1.232.0.161001 |
switchConfigFileTransferredThe switch has successfully transferred a configuration file. TRAP-TYPE .1.3.6.1.4.1.232.0.161002 |
switchTFTPTransferSucceededThe switch has successfully completed a TFTP transfer. TRAP-TYPE .1.3.6.1.4.1.232.0.161003 |
switchTFTPTransferFailedThe switch has failed a TFTP transfer. TRAP-TYPE .1.3.6.1.4.1.232.0.161004 |
switchFileInvalidInvalid firmware or configuration image downloaded. TRAP-TYPE .1.3.6.1.4.1.232.0.161005 |
switchFanFailedThe switch fan has failed. TRAP-TYPE .1.3.6.1.4.1.232.0.161006 |
switchFanOkThe switch fan has returned to normal operation. TRAP-TYPE .1.3.6.1.4.1.232.0.161007 |
switchTempSensorDegradedThe switch temperature sensor indicates a high temperature condidtion. TRAP-TYPE .1.3.6.1.4.1.232.0.161008 |
switchTempSensorFailedThe switch temperature sensor indicates an over-temperature condition. TRAP-TYPE .1.3.6.1.4.1.232.0.161009 |
switchTempSensorOkThe switch temperature sensor indicates temperature has returned to normal. TRAP-TYPE .1.3.6.1.4.1.232.0.161010 |
switchPostSuccessThe switch has successfully completed POST. TRAP-TYPE .1.3.6.1.4.1.232.0.161011 |
switchLoginFailureThe switch has rejected a login attempt. TRAP-TYPE .1.3.6.1.4.1.232.0.161012 |
switchLocationChangeThe switch location has changed. The new
location is defined in the variables. The
trap will be sent out on the next boot TRAP-TYPE .1.3.6.1.4.1.232.0.161013 |
switchCubeTypeChangeTrap for connection different cube type.
Customer has changed the cube type since
the last boot. TRAP-TYPE .1.3.6.1.4.1.232.0.161014 |
switchSNTPServiceUnavailableA SNTP Server was configured, but no SNTP servers were found.
This trap is sent once if SNTP is enabled, a SNTP server
is configured, and a SNTP server could not be contacted for
10 minutes from the start time. The start time will be defined
as when both SNTP was enabled and a SNTP server was configured
or when a SNTP server was contacted successfully. TRAP-TYPE .1.3.6.1.4.1.232.0.161015 |
entityMIB OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.47 |
entityMIBTraps OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.47.2 |
entityMIBTrapPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.47.2.0 |
entConfigChangeAn entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling period
is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss. TRAP-TYPE .1.3.6.1.4.1.3727.20.20.3.1.47.2.0.0.1 |