CPQ-TRAPS-MIB: View SNMP OID List / Download MIB

VENDOR: EUROSINET


 Home MIB: CPQ-TRAPS-MIB
Download as:   
SNMPv2-CONF, CPQHOST-MIB, COMPAQ-ID-REC-MIB, COMPAQ-AGENT-MIB, SNMPv2-SMI, CPQRACK-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
                 entConfigChange 1.3.6.1.2.1.47.2.00.1
An 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.
           switchFirmwareTransferred 1.3.6.1.4.1.2320.161001
The switch has successfully transferred a firmware image.
           switchConfigFileTransferred 1.3.6.1.4.1.2320.161002
The switch has successfully transferred a configuration file.
           switchTFTPTransferSucceeded 1.3.6.1.4.1.2320.161003
The switch has successfully completed a TFTP transfer.
           switchTFTPTransferFailed 1.3.6.1.4.1.2320.161004
The switch has failed a TFTP transfer.
           switchFileInvalid 1.3.6.1.4.1.2320.161005
Invalid firmware or configuration image downloaded.
           switchFanFailed 1.3.6.1.4.1.2320.161006
The switch fan has failed.
           switchFanOk 1.3.6.1.4.1.2320.161007
The switch fan has returned to normal operation.
           switchTempSensorDegraded 1.3.6.1.4.1.2320.161008
The switch temperature sensor indicates a high temperature condidtion.
           switchTempSensorFailed 1.3.6.1.4.1.2320.161009
The switch temperature sensor indicates an over-temperature condition.
           switchTempSensorOk 1.3.6.1.4.1.2320.161010
The switch temperature sensor indicates temperature has returned to normal.
           switchPostSuccess 1.3.6.1.4.1.2320.161011
The switch has successfully completed POST.
           switchLoginFailure 1.3.6.1.4.1.2320.161012
The switch has rejected a login attempt.
           switchLocationChange 1.3.6.1.4.1.2320.161013
The switch 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.2320.161014
Trap for connection different cube type. Customer has changed the cube type since the last boot.
           switchSNTPServiceUnavailable 1.3.6.1.4.1.2320.161015
A 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.