CPQ-TRAPS-MIB

Imported Objects

agentSwitchPowerSupplyCurPwrOutput, agentSNTPServer2IPAddr, agentSwitchFanIndex, agentSwitchFanCondition, agentSwitchTempSensorIndex, agentSwitchTempSensorCurrent, agentSwitchTempSensorThreshold, agentSwitchTempSensorCondition, agentSwitchTempSensorTempType, agentSwitchPowerSupplyMaxPwrOutput, agentSNTPServer1IPAddr, agentSwitchPowerSupplyIntakeTemp, agentSwitchPowerSupplyExhaustTemp, agentSwitchPowerSupplyStatus, agentSwitchPowerSupplyInputLineStatus, agentSwitchPowerSupplyCondition, agentSwitchCubeType, agentSwitchCubeSpareName, agentSwitchCubeSparePartNumber, agentBscSwFileStatus, agentBscSwFileLoadType, agentBscSwFile, agentBscSwFileAddrCOMPAQ-AGENT-MIB
compaq-common-mgmtCOMPAQ-ID-REC-MIB
compaqCPQHOST-MIB
cpqRackCommonEnclosureName, cpqRackUid, cpqRackCommonEnclosureSerialNum, cpqRackNetConnectorSerialNum, cpqRackName, cpqRackNetConnectorName, cpqRackNetConnectorLocation, cpqRackNetConnectorFWRev, cpqRackNetConnectorSparePartNumberCPQRACK-MIB
TRAP-TYPERFC-1215
enterprisesRFC1155-SMI
mib-2RFC1213-MIB

Objects

entityMIB .1.3.6.1.2.1.47
entityMIBTraps .1.3.6.1.2.1.47.2
entityMIBTrapPrefix .1.3.6.1.2.1.47.2.0

Notifications/Traps

NameOIDDescription
entConfigChange.1.3.6.1.2.1.47.2.0.0.1
igChange 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.
switchFirmwareTransferred











.1.3.6.1.4.1.232.0.161001
The switch has successfully transferred a firmware image.
switchConfigFileTransferred










.1.3.6.1.4.1.232.0.161002
The switch has successfully transferred a configuration file.
switchTFTPTransferSucceeded










.1.3.6.1.4.1.232.0.161003
The switch has successfully completed a TFTP transfer.
switchTFTPTransferFailed










.1.3.6.1.4.1.232.0.161004
The switch has failed a TFTP transfer.
switchFileInvalid











.1.3.6.1.4.1.232.0.161005
Invalid firmware or configuration image downloaded.
switchFanFailed










.1.3.6.1.4.1.232.0.161006
The switch fan has failed.
switchFanOk










.1.3.6.1.4.1.232.0.161007
The switch fan has returned to normal operation.
switchTempSensorDegraded













.1.3.6.1.4.1.232.0.161008
The switch temperature sensor indicates a high temperature condidtion.
switchTempSensorFailed













.1.3.6.1.4.1.232.0.161009
The switch temperature sensor indicates an over-temperature condition.
switchTempSensorOk













.1.3.6.1.4.1.232.0.161010
The switch temperature sensor indicates temperature has returned to normal.
switchPostSuccess








.1.3.6.1.4.1.232.0.161011
The switch has successfully completed POST.
switchLoginFailure







.1.3.6.1.4.1.232.0.161012
The switch has rejected a login attempt.
switchLocationChange







.1.3.6.1.4.1.232.0.161013
 location has changed.  The new
location is defined in the variables. The 
trap will be sent out on the next boot
switchCubeTypeChange











.1.3.6.1.4.1.232.0.161014
onnection different cube type. 
Customer has changed the cube type since 
the last boot.
switchSNTPServiceUnavailable









.1.3.6.1.4.1.232.0.161015
ver 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.