compiling and customizing snmp mibs with hpe simh20628. · compiling and customizing snmp mibs with...
Post on 18-Apr-2019
456 Views
Preview:
TRANSCRIPT
Technical Proposal
Compiling and customizing SNMP MIBs with HPE SIM DivisionV 1.0
February 2017
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 2
Table of contents
Introduction ................................................................................................................................................ 3
Windows ................................................................................................................................................ 3
HP-UX and Linux ................................................................................................................................... 3
MIB management tools ............................................................................................................................. 4
mcompile ................................................................................................................................................ 4
mxmib .................................................................................................................................................... 6
mxmib MIB keyword customization 7
--#TYPE 7
--#SEVERITY 7
--#ENABLE 8
--#CATEGORY 8
--#MSG_FORMATTER 9
Example 10
SNMP Trap Settings page ................................................................................................................... 11
Troubleshooting MIB compilation issues ................................................................................................ 13
Troubleshooting mcompile ................................................................................................................... 13
Troubleshooting mxmib ....................................................................................................................... 13
Finding Dependent MIBs ..................................................................................................................... 13
Appendix ................................................................................................................................................. 15
Out-of-the-box MIB support in HPE SIM ............................................................................................. 15
Virtual Connect MIBs ........................................................................................................................... 19
Virtual Connect MIB Loading order 19
Virtual Connect Traps/Notifications 20
OneView Server Enablement and Health MIBs ................................................................................... 22
OneView Server Enablement and Health Traps/Notifications 22
OneView Server Enablement and Health MIB Loading order 23
iLO 4 MIBs ........................................................................................................................................... 23
iLO 4 Traps/Notifications 23
iLO 4 MIB Loading order 26
Onboard Administrator MIBs ............................................................................................................... 28
Onboard Administrator Traps/Notifications 28
Onboard Administrator MIB Loading order 29
Rack and Power Infrastructure MIBs ................................................................................................... 29
Rack and Power Infrastructure: Traps/Notifications 29
Rack and Power Infrastructure MIB Loading order 30
MIBs Trap Info ......................................................................................................................................... 31
For more information ............................................................................................................................. 465
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 3
Introduction HPE Systems Insight Manager (HPE SIM) provides the capability of managing systems through SNMP and by receiving incoming SNMP trap events. This paper discusses the tools provided by HPE SIM to integrate third-party (non-HPE) SNMP v1/v2 MIBs into HPE SIM and to provide support for processing and displaying traps from other systems. This paper also discusses the MIB syntax extensions supported by HPE SIM that provide additional value in customizing specific trap information. Finally, this paper discusses the set of MIBs included with HPE SIM to provide out-of-the-box support for many HPE systems.
Integration of third-party MIBs is a topic for advanced users of HPE SIM. This paper assumes that the reader already has familiarity with SNMP-based management and MIBs in particular. Most vendors tend to loosely follow industry standards for the development of MIBs and MIB compilers. Therefore, it is often the case that MIBs require some changes and customization on the part of the end-user to properly integrate the MIBs with a management application such as HPE SIM.
Note that this paper frequently references directories and tool locations throughout the HPE SIM directory structure. This directory structure varies depending upon your installation choices and on the operating system under which you have installed HPE SIM. Typical installation paths are as follows:
Windows
C:\Program Files\HP\Systems Insight Manager\ as the installation directory
C:\Program Files\HP\Systems Insight Manager\mibs for all MIB and CFG files
C:\Program Files\HP\Systems Insight Manager\lbin for mcompile
C:\Program Files\HP\Systems Insight Manager\bin for mxmib
HP-UX and Linux
/opt/mx as the installation directory
/opt/mx/mibs for all MIB and CFG files
/opt/mx/bin for mcompile and mxmib
Note Compiling MIBs into HPE SIM only enables the console to receive SNMP traps from systems. This does NOT extend the data collection mechanism to collect data points from the compiled MIBs into the database. This type of functionality is currently not available in HPE SIM.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 4
MIB management tools HPE SIM provides three tools for use with MIB integration and trap customization. You register MIBs with HPE SIM using two command-line tools. These tools are only accessible to the administrator or root user of the operating system. They are:
mcompile
mxmib
In addition, HPE SIM provides a GUI tool to display and edit the trap settings for MIBs already compiled using the command-line tools listed above. This tool is the SNMP Trap Settings page.
The remainder of this section discusses each of the tools provided and elaborates on their specific usage.
mcompile
The mcompile tool verifies the syntax of all MIBs to be loaded into the system. mcompile resolves all MIB dependencies and, where necessary, converts SNMP v2 MIBs into v1 format for loading into the HPE SIM database. mcompile is located in the \lbin directory and should be run from the \mibs directory. mcompile looks for all MIB files in the \mibs directory by default so any MIB that you intend to register should be copied to the \mibs directory. While mcompile does provide some capability to specify a different directory to search for MIBs, as a best practice HPE strongly recommends you place all MIBs in the \mibs directory.
Usage for mcompile is as follows:
mcompile [-d ]
Typical usage is mcompile test.mib where test.mib is the target MIB you want to register with HPE SIM.
Use of the -d switch is not necessary when you have copied all MIBs, including dependency MIBs, to the \mibs directory and execute mcompile from the \mibs directory. The
-d switch specifies which directory contains the MIB files to be compiled into HPE SIM. The directory path must be specified as relative to the full path or relative to the directory.
As output, mcompile produces a CFG file and save it to the \mibs directory. This file has the same name as the source MIB except it has the .cfg suffix. In the typical usage mentioned above, the resulting output file would be test.cfg. Running mcompile several times against the same source MIB produces multiple revisions of the CFG with the latest version retaining the .cfg extension. CFG files are stripped-down versions of the original source MIBs where all comments have been removed, all imports from other MIBs have been resolved and substituted as needed, and the compiler has converted v2 syntax to v1 where appropriate.
Also note when compiling MIBs with dependencies, the dependent MIB must be located in the same directory as the target MIB and must follow a certain naming convention, typically MIBMODULE.MIB. An example follows using excerpts from the CPQFCA MIB:
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 5
CPQFCA-MIB DEFINITIONS ::= BEGIN
IMPORTS
compaq
FROM CPQHOST-MIB
enterprises
FROM RFC1155-SMI
DisplayString
FROM RFC1213-MIB OBJECT-TYPE
FROM RFC-1212 TRAP-TYPE
FROM RFC-1215
cpqSsChassisName
FROM CPQSTSYS-MIB
mcompile searched for compaq by opening the file CPQHOST.MIB and mcompile looks for cpqSsChassisName in CPQSTSYS.MIB. The other imports are resolved automatically when mcompile runs from the \mibs directory. HPE provides versions of the RFC 1212, 1213, and 1215 MIBs for automatic import during compilation. mcompile automatically resolves and imports internally from RFC1155.
Another example of imports during compilation comes from the BLADETYPE2-TRAP.MIB used by the HP ProLiant BL p-Class GbE2 Interconnect Switch:
BLADETYPE2-TRAP-MIB DEFINITIONS:= BEGIN
IMPORTS
TRAP-TYPE
FROM RFC-1215
sysName
FROM RFC1213-MIB
hpSwitchBladeType2-Mgmt
FROM HP-SWITCH-PL-MIB
agSlotNumber
FROM BLADETYPE2-SWITCH-MIB
ipCurCfgGwIndex
FROM BLADETYPE2-NETWORK-MIB
In this example, TRAP-TYPE and sysName are readily resolved as in the example above. hpSwitchBladeType2-Mgmt is resolved by mcompile checking HP-SWITCH-PL.MIB. agSlotNumber is resolved from BLADETYPE2-SWITCH.MIB and ipCurCfgGwIndex is resolved from BLADETYPE2-NETWORK.MIB.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 6
To illustrate further how imports are resolvedthe following procedure is how mcompile would attempt to resolve the import for hpSwitchBladeType2-Mgmt:
1. Search for a file named HP-SWITCH-PL-MIB.mib (module name, uppercase).
2. Search for a file named HP-SWITCH-PL.mib (module name without -MIB,
uppercase).
3. Search for hp-switch-pl.mib (convert name to lowercase for case sensitivity in
Linux/HP-UX).
4. Search for hp-switch-pl-mib.mib (convert name to lowercase for case sensitivity
in Linux/HP- UX).
5. Report an error indicating that the imported MIB could not be found.
A major consideration when importing MIBs is locating variables from other third-party MIBs. In many cases, MIBs are named to match module names. However, in some circumstances it might be necessary to rename MIB files to match the module names prior to compilation. For example, some vendors might provide MIB files with different extensions such as .my. In this case, before using mcompile, the mibfile.my file must be renamed to mibfile.mib.
mxmib
The mxmib tools registers MIBs into the HPE SIM database by using their corresponding CFG files. This tool has the capability to list all registered MIBs, to display a list of traps contained in each individually registered MIB, and to unregister MIBs that you or the system have previously registered.
Important: While it is possible to unregister MIBs currently registered in the HPE SIM database, HPE strongly advises you do not unregister any files that have been registered by default. Doing so can impair HPE SIMs ability to correctly process traps from other HPE systems on the network.
If you unregister a MIB from HPE SIM, the corresponding received events in HPE SIM are automatically deleted.
mxmib expects to find all files located in the \mibs directory. Usage for mxmib is as follows:
mxmib -a
mxmib -f
mxmib l
mxmib -t
mxmib -d
The switches work as follows:
-a registers a new CFG, , or replaces the data of a previously registered MIB.
-f reads and processes a list of CFGs from a file, , to
register with HPE SIM. This file must reside in the \mibs directory and the full CFG filename must be
listed on individual lines. Each line in the file is processed as it would be by running the mxmib a command
individually on each individual MIB file.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 7
-l lists all the MIBs registered in HPE SIM. Supplying no arguments to mxmib defaults to running
mxmib l.
-t lists the traps in the specified MIB .
-d unregisters a MIB, , from the HPE SIM database.
The initial command to register the file uses the .cfg extension, but all subsequent commands refer to the file by its .mib extension.
Important: mxmib is order sensitive. While the command allows you to compile MIBs whose dependencies have not been compiled, for optimal results, HPE recommends that you register MIBs with HPE SIM in order of dependency. If you do not compile MIBs in order of dependency, HPE SIM might not properly resolve varbind data for incoming traps from MIB X when a varbind has been imported from MIB Y that was not registered prior to registering MIB X. MIB dependencies are typically identified at the top of MIB files in the IMPORTS section ad are discussed in the mcompile section. Note that failing to compile imported MIBs properly does not block reception of traps; it only limits the data captured for some traps.
mxmib MIB keyword customization
After using mcompile to parse and validate the source MIB, you can customize the resulting CFG file for support in HPE SIM. Specifically, there are special keywords that can be defined on a per-trap basis. At the conclusion of this section, there is a full example. The keywords and their usage are as follows.
--#TYPE
The TYPE keyword provides a way to add a short description of the trap to HPE SIM. This short description can be used when sending a paging message. This enhances the ability to transmit information without being verbose. This keyword does not provide any functional purpose; however, it does represent the primary display string for the trap when it is displayed in HPE SIM. Note that while the TYPE field does not need to be unique, but HPE recommends that the combination of TYPE and CATEGORY fields form a unique pair so that this event can be effectively searched for using the Event by Category/Type search criteria.
--#SEVERITY
The SEVERITY keyword can be used to alter the severity of a trap. The vendor who created the MIB might have decided that the trap, under most circumstances, only warrants a severity level of informational. However, you might need to escalate the traps severity based on operational importance. Therefore, this keyword overrides default severity. The allowable severity levels are shown below. Many vendors have different severities specified in their MIBs such as Normal, Warning, Degraded, Broken, and so on. These severities must be changed in the base MIB or CFG to one that matches HPE SIM. For example, Degraded can be mapped to Minor or Major, depending on the degradation. Editing the MIB or CFG and doing a search/replace on the severities is the easiest way to tweak the MIB. HPE SIM also provides a GUI to change the SEVERITY after MIB compilation.
INFORMATIONALEvents of this type require no attention. They are provided as useful information.
MINOREvents of this type indicate a warning condition that can escalate into a more serious problem.
MAJOREvents of this type indicate an impending failure.
CRITICALEvents of this type indicate a failure and signal the need for immediate attention.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 8
--#ENABLE
The ENABLE flag can be set to TRUE or FALSE and can effectively enable or disable a trap from being processed by HPE SIM. The usage for the keyword is either TRUE to indicate that that trap should be processed or FALSE to indicate that this trap should not be processed. By default, this keyword is TRUE and should only be explicitly overwritten on an exception basis.
--#CATEGORY
This provides a categorization of the trap for ease of viewing and use in forming HPE SIM lists. You can use predefined categories or, if none of these fit your need, you can create a category befitting your circumstances. The HPE SIM SNMP Trap Settings page provides a GUI to change the CATEGORY after MIB compilation. The predefined categories in HPE SIM are shown below.
APPLICATION
ARCserve Events
CommandView Events
Common Cluster Events
Cpqdscs
Data Protector Events
General Backup
Giga Switch Events
HP Open View Internet Services Events
HP OVSAM Events
HP Service Events
HP StorageWorks HSV Controller Events
HP StorageWorks SAN Switch Events
HP-UX EMS Events
Integrity Server Events
NetServer Events
PATROL Events
PowerDevice
ProLiant Application Events
ProLiant BL p-Class GbE Interconnect Switch Events
ProLiant BL p-Class GbE2 Interconnect Switch Events
ProLiant Cluster Events
ProLiant Miscellaneous Events
ProLiant NIC Events
ProLiant Operating System Events
ProLiant Rack Events
ProLiant Remote Management Events
ProLiant Storage Events
ProLiant System and Environmental Events
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 9
ProLiant Threshold Events
SAN Appliance Events
Server Net Events
ServiceGuard Events
STORAGE
SWCC Events
SYSTEM AND ENVIRONMENTAL
Tandem EMS Events
TruCluster Events
Unassigned
Unisys Configuration Agent Events
UNKNOWN
WYSE Events
ZESA
ZHRM
--#MSG_FORMATTER
This keyword has a number of HPE SIM specific commands. These commands are parsed and executed when a paging or e-mail Automatic Action on Event rule is created and exercised within HPE SIM. You might view these commands as a paging or e-mail command language. The general layout of each command contains an operand and descriptive text associated with the operand. The descriptive text must be delimited by a # pair. If the parser within HPE SIM does not recognize a command, it will disregard that command without providing any additional feedback.
Important: Changing the MSG_FORMATTER string is only recommended for extremely advanced users. Always back up any files that are modified so that they can easily be restored. Also, for HP ProLiant traps, HPE has already generated intelligent messages that are registered by default with HPE SIM. Referring to the following tables, the V keyword represents varbind information specific to individual traps. Numerically, all V definitions match the varbinds as they appear in the trap.
$VnV#Some text# Includes value for varbind and descriptive text (in this case, Some text)
Label will reflect the value selected. This will vary on a trap-to-trap basis.
$VnD#Some text# Includes the varbind description that is only available within HPE SIM
Label will reflect the valve selected. This will vary on a trap-to-trap basis.
In addition, a special keyword can be used to form varbind data into text sentences.
$Hdr#Some text# Used to add text or formatting to headers Text that could be added to add clarity to output data.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 10
Also, if the beginning keyword in the trap definition file is a $!, that tells the HPE SIM parser to disregard the global settings and to use only the trap definition file keywords. See example below.
Example
cpqDa5PhyDrvStatusChange TRAP-TYPE
ENTERPRISE compaq
VARIABLES { sysName, cpqHoTrapFlags, cpqDaPhyDrvStatus,
cpqDaPhyDrvCntlrIndex, cpqDaPhyDrvBusNumber,
cpqDaPhyDrvBay, cpqDaPhyDrvModel, cpqDaPhyDrvFWRev,
cpqDaPhyDrvSerialNum, cpqDaPhyDrvFailureCode }
DESCRIPTION Physical Drive Status Change. This trap signifies that the agent
has detected a change in the status of a Drive Array physical drive. The variable
cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If
the physical drive status is failed(3) or predictiveFailure(4), replace the
drive.
--#TYPE Physical Drive Status Change
--#SUMMARY Physical Drive Status is now %d.
--#ARGUMENTS {2}
--#SEVERITY CRITICAL
--#TIMEINDEX 99
--#MSG_FORMATTER $V1V#Computer: # $V3V#Drive Status: # $V9V#Serial
Number: #
::= 3029
The e-mail or pager output would appear as:
Event Notice ID: 3029
Computer: CRONUS
Drive Status: FAILED
Serial Number: WS7000134715
Event Description: Physical Drive Status Change. This trap signifies that the
agent has detected a change in the status of a Drive Array physical drive. The
variable cpaDaPhyDrvStatus indicates the current physical drive status. User
Action: If the physical drive status is failed(3) or predictiveFailure(4), replace
the drive.
Event Time: 01/09/2003 15:46: PM
Note that Event Notice ID, Event Description and Event Time are inserted by HPE SIM into all event notifications and that Computer (V1, sysName), Drive Status (V3, cpqDaPhyDrvStatus) and Serial Number (V9, cpaDaPhySerialNum) are customized to this specific trap.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 11
Using the preceding example and adding the $!:
--#MSG_FORMATTER $! $V1V#System Name: # $V3V#Drive Status: # $V9V#Serial Number:
#
The e-mail or pager output would be:
System Name: CRONUS Drive Status: FAILED
Serial Number: WS7000134715
Using the $Hdr keyword in conjunction with $! to further customize the display could be as follows:
--#MSG_FORMATTER $! $Hdr#The # $V1V#system # $Hdr#had the following # $V3V#Drive
Status:# $Hdr#. The system Serial Number # $V9V#is # $Hdr#.#
The e-mail or pager output would be:
The system Cronus had the following Drive Status: failed. The system Serial Number
is WS7000134715.
Important: For the TYPE, CATEGORY, and MSG_FORMATTER keywords described above, the value for these keywords must be encapsulated in quotes, such as xxx for the mxmib to successfully register the MIB in question. Other keywords such as SEVERITY and ENABLE do not require quoted values.
SNMP Trap Settings page The SNMP Trap Settings graphical page has the capability to modify the attributes of any trap that has been registered with the HPE SIM database. The attributes that are available for modification include the short and long descriptions, severity, category, and the trap enable/disable flag. Use the interface on this page to first select the registered MIB containing the trap in which you are interested, and then select the specific trap you wish to modify.
Fields can be modified as follows:
The Description field is the long description stating the nature of the trap. The Description field is used on the Event detail page and can be included in paging and e-mail notifications. This field corresponds to the DESCRIPTION keyword in the CFG files.
The Type field is the short description and is used as the display string when viewing a list of events. The Type can also be used as part of a paging or e-mail notification. Type fields have been custom-created for all of the HP ProLiant hardware events. However, for many other MIBs they have not been customized. Tailoring this field to present a clear message is crucial to presenting meaningful Event data in HPE SIM. This field corresponds to the #TYPE keyword in the CFG files.
The Severity field can be set to CRITICAL, MAJOR, MINOR, or INFORMATIONAL. The default is INFORMATIONAL when no other severity has been set by the base MIB. Many vendors have different severities specified in their MIBs such as Normal, Warning, Degraded, Broken, etc. These severities need to be changed in the base MIB or CFG to one that matches HPE SIM. For example, Degraded can be mapped to Minor or Major, depending on the degradation. Editing the MIB or CFG and doing a search/replace on the severities is the easiest way to tweak the MIB. This field corresponds to the #SEVERITY keyword in the CFG files.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 12
The Category field is used to logically group similar events for display purposes in HPE SIM. These groups are shown when you create event lists and when configuring Automatic Event Handling.
This is extremely helpful when wanting to group specific networking, storage, and other traps to be easily found in the user interface. This field corresponds to the #CATEGORY keyword in the CFG files.
The Enable/Disable field can be toggled to support or suppress events on a per-trap basis. HPE recommends that all traps remain Enabled and are only disabled when they are well-understood and can be ignored without any impact. By disabling a specific trap, you are telling HPE SIM to ignore that trap once received. If a trap is disabled, then the trap is dropped and not logged in the database. This field corresponds to the #ENABLE keyword in the CFG files.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 13
Troubleshooting MIB compilation issues
Important: Most MIB compilation issues are caused by syntactical errors in the source MIB from the original hardware vendor. Due to the vast number of MIBs available, HPE is able to only test and certify the set of MIBs that ship by default with HPE SIM. Other MIBs might need to be edited to compile with HPE SIM.
Troubleshooting mcompile
If the MIB file being compiled includes IMPORTS from other MIBs, the imported MIB files should also be located in the same directory as the MIB file being compiled.
Comment lines in MIB files start with -- and end with a new line or the next occurrence of --. Beware of MIBs with -- characters across the entire line. These lines are intended to be comments. However, extra dashes have cancelled the first set of -- characters. As a general rule, for comment lines, only use -- to denote the comment. No further -- are allowed on that line.
For example:
-- xyz comments out xyz
However
-- -- xyz effectively uncomments xyz
mcompile expects the END keyword at the end of a module on a line by itself. Be sure there is a new line in the MIB file after the END keyword.
mcompile does not allow redefinition of standard data types. If the MIB file being compiled contains such redefinitions, they must be commented out before running mcompile.
Troubleshooting mxmib
For the CLI to list a MIB file as registered, the MIB file must reside in the MIBs directory and have the same name as the MIB file that was registered.
mxmib -a relies on file.cfg being in the MIBs directory.
Re-registering a previously registered MIB can be slow. HPE recommends un-registering first and then re-registering.
Finding Dependent MIBs
At the command prompt, change directory to HPE SIM installation folder -> mibs
Execute the command: mcompile mibname.mib
This will display all the dependent MIBs while compiling and user can recognize all the dependent MIBs. For Ex: As shown below, MIB bladetype2-network.mib has the following dependent MIBs.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 14
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 15
Appendix
Out-of-the-box MIB support in HPE SIM
The following table represents the key MIBs that ship with HPE SIM. Those MIBs that are marked as preloaded are registered as part of every HPE SIM installation. The remaining MIBs are in the MIB directory for you to compile, if necessary, for managing those types of systems in your environment.
MIB name Supports HPE SIM
asmib.mib ARC Serve X
atmf.mib ATM device X
avsnmpv1.mib Availant Manager X
bkupexec.mib General Backup X
bladetype2-network.mib HP ProLiant BL p-Class GbE2 Interconnect
Switch
X
bladetype2-physical.mib HP ProLiant BL p-Class GbE2 Interconnect
Switch
X
bladetype2-switch.mib HP ProLiant BL p-Class GbE2 Interconnect
Switch
X
bladetype2-trap.mib Proliant BL P-class GbE2 Interconnect Switch X
bladetype4-switch.mib hpSwitchProliant X
bridge.mib Cisco bridge X
cisco-cdp.mib cisco products X
cisco-cluster.mib cisco products X
cisco-config-copy.mib cisco products X
cisco-config-man.mib cisco products X
cisco-entity-fru-control.mib cisco products X
cisco-entity-vendortype-oid.mib cisco products X
cisco-envmon.mib cisco products X
cisco-flash.mib cisco products X
cisco-ftp-client.mib cisco products X
cisco-igmp-filter.mib cisco products X
cisco-image.mib cisco products X
cisco-ip-stat.mib cisco products X
cisco-l2l3-interface-config.mib cisco products X
cisco-lag.mib cisco products X
cisco-mac-notification.mib cisco products X
cisco-memory-pool.mib cisco products X
cisco-pae.mib cisco products X
cisco-pagp.mib cisco products X
cisco-ping.mib cisco products X
cisco-port-security-mib.mib cisco products X
cisco-process.mib cisco products X
cisco-products.mib cisco products X
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 16
MIB name Supports HPE SIM
cisco-rttmon.mib cisco products X
cisco-stack-mib.mib cisco products X
cisco-stackmaker.mib cisco products X
cisco-stp-extensions.mib cisco products X
cisco-syslog.mib cisco products X
cisco-tc.mib cisco products X
cisco-tcp.mib cisco products X
cisco-udldp.mib cisco products X
cisco-vlan-iftable-relationship.mib cisco products X
cisco-vlan-membership.mib cisco products X
cisco-vtp.mib cisco products X
compaq-agent.mib HP Rack and Enclosure X
compaq-id-rec.mib HP ProLiantBLpClassGbE series Product X
cpq-traps.mib HP Proliant BL P-class GbE Interconnect Switch X
cpq54nn.mib Giga Switch X
cpqclus.mib HP Proliant Cluster X
cpqcmc.mib HP Proliant remote management X
cpqcr.mib HP Proliant Cluster X
cpqdsccs.mib Cpqdsccs X
cpqfca.mib HP Proliant Storage X
cpqgen.mib HP Proliant Miscellaneous X
cpqhlth.mib HP Proliant System and Environmental X
cpqhost.mib HP Proliant Application X
cpqhsv110v3.mib HP StorageWorks HSV Controller X
cpqida.mib HP Proliant Storage X
cpqide.mib HP Proliant Storage X
cpqidrec.mib HP proLiant BL pClass GbE Device X
cpqn5226a.mib Giga Switch X
cpqnic.mib HP Proliant NIC X
cpqpower.mib Power Device X
cpqrack.mib HP ProLiant Rack X
cpqrecov.mib HP Proliant Cluster X
cpqrpm.mib HP Proliant UPS X
cpqsanapp.mib SAN Appliance X
cpqsanevent.mib SAN Appliance X
cpqscsi.mib HP Proliant Storage X
cpqservice.mib HP Service X
cpqsinfo.mib HP Proliant System and Environmental X
cpqsm2.mib HP Proliant remote management X
cpqsrvmn.mib HP Proliant System and Environmental X
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 17
MIB name Supports HPE SIM
cpqstdeq.mib HP Proliant System and Environmental X
cpqstsys.mib HP Proliant Storage X
cpqswcc.mib HP StorageWorks Command Console X
cpqthrsh.mib HP Proliant threshold X
cpqups.mib HP Proliant UPS X
cpqwinos.mib HP Proliant Operating System X
dataprotector.mib Data protector X
dlghwinf.mib Dialogic Hardware X
ems.mib HP-UX EMS X
emsmibax.mib Tandem EMS X
fa-mib40.mib HP StorageWorks SAN Switch X
fddi-smt73.mib FDDI subsystems X
fe-mib.mib Fibre Channel Fabric Element X
gbe2c-1-10g-l2l3.mib hpProLiant-GbE2c-1-10G-InterconnectSwitch X
gbe2c-10g-l2l3.mib hpProLiant-GbE2c-10G-InterconnectSwitch X
h22agent.mib HP StorageWorks Command Console X
hp-mccluster.mib HP Serviceguard X
hp-switch-pl.mib HP Blade Network switch X
hpeccmib.mib NetServer X
hpipf02trap.mib HP Integrity Server X
hpipftrap.mib HP Integrity Server X
hpn.mib NetServer X
hpnetctz.mib CommandView X
hpnr.mib NetServer X
hpov-nnm.mib HPOV X
hpovsam.mib HP OVSAM X
hpovsam_im.mib HP STORAGE X
hpprfmib.mib HP Netserver X
hpsgcluster.mib HP ServiceGuard X
hpswa.mib HP Netserver X
hptat.mib HP Netserver X
hs_agent.mib SWCC X
lsf001.mib LSF product X
msa2000traps.mib MSA2000 Array(HPMSA) X
nsadimm.mib HP Netserver X
nsaevent.mib HP Netserver X
nsainfo.mib HP Netserver X
nsapci.mib HP Netserver X
nsascsi.mib HP Netserver X
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 18
MIB name Supports HPE SIM
nsavolcp.mib HP Netserver X
old-cisco-chassis.mib cisco products X
old-cisco-flash.mib cisco products X
old-cisco-interfaces.mib cisco products X
old-cisco-ip.mib cisco products X
old-cisco-sys.mib cisco products X
old-cisco-tcp.mib cisco products X
old-cisco-ts.mib cisco products X
ovis-v2.mib HP Open View Internet Services X
pcisnet.mib ServerNet X
pfc.mib PATROL X
rfc1213.mib RFC MIB X
rfc1215.mib RFC MIB X
rfc1514.mib RFC MIB X
rmon-mib.mib RFC MIB X
smsagent.mib Unisys Configuration Agent X
svrclu.mib Common Cluster X
switch.mib ServerNet X
symtrap.mib Integrity Server X
truclu.mib TruCluster X
ucd-snmp-mib.mib Numerical Management X
v5_0ficon.mib FICON in Fabos X
v5_1ha.mib Brocade Communications Systems X
v5_3sw.mib Fibre Channel Switch X
wbt3mib.mib WYSE Events X
xp1024trapmib.mib Hitachi RAID450 SNMP Agent X
zesa.mib ZESA X
zhrm.mib ZHRM X
zsmp.mib Tandem's Subsystem Control Facility (SCF): X
ztmx.mib Tandem SNMP Trap Multiplexer X
ztsa.mib Tandem TCP/IP Subagent X
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 19
Virtual Connect MIBs
A managed device has a set of objects that can be queried, such as a status, state, or statistical information. Each object queried is identified by an OID. MIBs are databases of OIDs and their descriptions. MIBs are used by the management station to translate trap information sent by an SNMP agent about an OID.
The following table provides a list of MIBs supported by VC Enet and FC modules.
MIB File Name MIB Module Name Comments
if-mib.mib IF-MIB Information on interfaces (links, ports etc)
bridge.mib BRIDGE-MIB Information on bridges
snmpv2-mib.mib SNMPv2-MIB Contains system related information (sysObjectID,
sysDescr, sysName.)
cpqsinfo.mib CPQSINFO-MIB Compaq System Information cpqhost.mib CPQHOST-MIB Compaq Host MIB cpqrack.mib CPQRACK-MIB Compaq Rack MIB RFC1213-MIB.txt RFC1213-MIB RFC 1213 Network Mgmt IP-MIB.txt IP-MIB RFC 4293 IP-MIB fa-mib40.mib FCMGMT-MIB Fibre Alliance MIB (FC Mgmt Integ) fe-mib.mib FIBRE-CHANNEL-FE-MIB RFC 2837 Fabric Element MIB
lldp-mib.mib LLDP-MIB IEEE LLDP MIB (LLDP-MIB) lldp-v2-mib.mib LLDP-V2-MIB IEEE LLDPv2 MIB (LLDPv2-MIB)
ieee8023-lag.mib IEEE8023-LAG-MIB IEEE8023 LAG MIB (LAG-MIB)
Virtual Connect MIB Loading order
Following MIBs (file) must be loaded in the MIB Browser before loading Virtual Connect specific MIBs.
Common MIBs:
SNMPv2-SMI.mib
SNMPv2-TC.mib
snmp-framework-mib.mib
rfc1155-smi.mib
rfc-1212.mib
rfc-1213.mib
rfc-1215.mib
TRANSPORT-ADDRESS-MIB.mib
if-mib.mib
SNMPv2-CONF.mib
Product Specific and Depended MIBs:
Load all the common MIBs and then load dependent MIBs:
MIB File MIB Module Name Dependent MIBs
hpvcmodule-mib.mib HPVCMODULE-MIB
vc-domain-mib.mib HPVC-MIB
vc-qos-mib.mib HPVCQOS-MIB hpvcmodule-mib.mib
https://github.com/hardaker/net-snmp/blob/master/mibs/RFC1213-MIB.txthttps://github.com/hardaker/net-snmp/blob/master/mibs/IP-MIB.txt
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 20
Virtual Connect MIB details are below:
hpvcmodule-mib.mib The VC Module MIB is a VC-specific MIB that describes the state of a specific VC module. In addition to unique VC module attributes, it defines traps for reporting alerts on port statistics, such as throughput, errors, and discards.
vc-domain-mib.mib The VC Domain MIB combines domain-wide attributes with traps for state changes in VC managed objects.
vc-qos-mib.mib This MIB module describes QoS specific MIB objects present in the Virtual Connect Module.
Virtual Connect Traps/Notifications
Trap / Notification Name MIB Module Name Trap Description / Comments
cpqHoSWRunningStatusChangeTrap CPQHOST-MIB This trap notifies the user that the running
software has changed status, configuration
status, or redundancy mode.
cpqHoSWRunningStatusChange CPQHOST-MIB Notifies the user that the running software has
changed status, configuration status, or
redundancy mode.
connUnitStatusChange FCMGMT-MIB The overall status of the connectivity unit has
changed. Recommended severity level (for
filtering): alert
connUnitDeletedTrap FCMGMT-MIB A connUnit has been deleted from this agent.
Recommended severity level (for filtering):
warning
connUnitEventTrap FCMGMT-MIB An event has been generated by the
connectivity unit. Recommended severity level
(for filtering): info
connUnitSensorStatusChange FCMGMT-MIB The overall status of the connectivity unit has
changed. Recommended severity level (for
filtering): alert
connUnitPortStatusChange FCMGMT-MIB The overall status of the connectivity unit has
changed. Recommended severity level (for
filtering): alert
linkDown IF-MIB A linkDown trap signifies that the SNMP entity,
acting in an agent role, has detected that the
ifOperStatus object for one of its
communication links is about to enter the
down state from some other state (but not
from the notPresent state). This other state is
indicated by the included value of
ifOperStatus.
linkup IF-MIB A linkUp trap signifies that the SNMP entity,
acting in an agent role, has detected that the
ifOperStatus object for one of its
communication links left the down state and
transitioned into some other state (but not into
the notPresent state). This other state is
indicated by the included value of
ifOperStatus.
authenticationFailure SNMPv2-MIB An authenticationFailure trap signifies that the
sending protocol entity is the addressee of a
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 21
Trap / Notification Name MIB Module Name Trap Description / Comments
protocol message that is not properly
authenticated.
coldStart SNMPv2-MIB A coldStart trap signifies that the sending
protocol entity is reinitializing itself such that
the agent``s configuration or the protocol
entity implementation may be altered.
authenticationFailure SNMPv2-MIB An authenticationFailure trap signifies that the
sending protocol entity is the addressee of a
protocol message that is not properly
authenticated.
vcDomainManagedStatusChanged HPVC-MIB The managed status of Domain has changed
vcDomainStackingLinkRedundancyS
tatusChange
HPVC-MIB The stacking link connection redundancy
status has changed.
VcDomainModuleRole HPVC-MIB The virtual connect manager role of module
has changed.
vcCheckpointTimeout HPVC-MIB The checkpoint valid status remained false for
more than five minutes.
vcCheckpointCompleted HPVC-MIB A checkpoint operation has completed
following a checkpoint timeout trap. The
checkpoint valid status is true again. This trap
is not sent on every checkpoint completion,
but only on a checkpoint completion after a
vcCheckpointTimeout trap has been sent.
vcEnclosureManagedStateChanged HPVC-MIB The managed status of Enclosure has
changed
vcEnetNetworkManagedStatusChanged HPVC-MIB The managed status of Network has changed
vcFcFabricManagedStatusChanged HPVC-MIB The managed status of Fabric has changed
vcModuleManagedStatusChanged HPVC-MIB The managed status of Module has changed
vcProfileManagedStatusChanged HPVC-MIB The managed status of Profile has changed
vcPhysicalServerManagedStatusChan
ged3
HPVC-MIB The managed status of Physical Server has
changed
vcTesttrap HPVC-MIB A test trap for verifying trap configuration.
vcModPortInputUtilizationUp HPVCMODULE-
MIB
The input line utilization on a port has
exceeded its high-water mark for longer than
30 seconds. Port is the index of the affected
port in ifTable.
vcModPortInputUtilizationDown HPVCMODULE-
MIB
The input line utilization on a port has dropped
below its low-water mark for longer than 30
seconds. Port is the index of the affected port
in ifTable.
vcModPortOutputUtilizationUp HPVCMODULE-
MIB
The output line utilization on a port has
exceeded its high-water mark for longer than
30 seconds. Port is the index of the affected
port in ifTable.
vcModPortOutputUtilizationDown HPVCMODULE-
MIB
The output line utilization on a port has
dropped below its low-water mark for longer
than 30 seconds. Port is the index of the
affected port in ifTable.
vcModPortInputErrorsUp HPVCMODULE-
MIB
The input error count on a port has exceeded
its high-water mark for longer than the error
averaging period. Port is the index of the
affected port in ifTable.
vcModPortInputErrorsDown HPVCMODULE-
MIB
The input error count on a port has dropped
below its low-water mark for longer than the
error averaging period. Port is the index of the
affected port in ifTable.
vcModPortOutputErrorsUp HPVCMODULE-
MIB
The output error count on a port has exceeded
its high-water mark for longer than the
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 22
Trap / Notification Name MIB Module Name Trap Description / Comments
threshold averaging period. Port is the index
of the affected port in ifTable.
vcModPortOutputErrorsDown HPVCMODULE-
MIB
The output error count on a port has dropped
below its low-water mark for longer than 30
seconds. Port is the index of the affected port
in ifTable.
vcModPortBpduLoopDetected HPVCMODULE-
MIB
A network loop condition is detected on this
port. If the loop condition is detected on a
Flex10 port, the trap data indicates the
physical port associated with the Flex10 port.
If multiple Flex10 ports on a physical port
detect a loop condition, a separate trap is sent
for each occurrence of the loop condition.
vcModPortBpduLoopCleared HPVCMODULE-
MIB
A network loop condition is cleared on this
port. The trap data indicates the physical port
associated with a Flex10 port.
For Flex10 ports, this trap is sent only after all
Flex10 ports on a physical port are cleared
from a loop condition.
vcModPortProtectionConditionDetected HPVCMODULE-
MIB
A port protection condition is detected on this
port. If the new port protection status is a
value other than OK, the port may be disabled
to protect the VC module from further service
degradation. Administrative action is required
to recover the port from this condition.
vcModPortProtectionConditionCleared HPVCMODULE-
MIB
The port is recovered from port protection
condition to normal operational state.
vcModuleDomainRoleChange
HPVCMODULE-
MIB
The VCM role of the VC module has changed.
vcSwitchMemParityErrorEvent
HPVCMODULE-
MIB
The switch hardware has detected a parity
error. The parity error is automatically
corrected.
OneView Server Enablement and Health MIBs
MIB File Name MIB Module Name Comments
cpqoneView CPQOneView-MIB This mib file is used by Customers to
interpret SNMP traps forwarded from
OneView.
OneView Server Enablement and Health Traps/Notifications
Trap/Notification name MIB Module Name Comments
cpqOneViewCriticalAlert(179001) CPQOneView-MIB These four traps are defined (179001-179004)
in order to forward alerts from OneView as
traps. These alerts are generated from both
SNMP traps and RIS events received in
Oneview.
cpqOneViewWarningAlert(179002) CPQOneView-MIB
cpqOneViewOkAlert(179003) CPQOneView-MIB
cpqOneViewUnknownAlert(179004) CPQOneView-MIB
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 23
OneView Server Enablement and Health MIB Loading order
Following MIBs (file) must be loaded in the MIB Browser before loading OneView Server Enablement and Health specific MIBs.
Common MIBs: Below is the list of all the common MIBs in the order of loading:
RFC-1212
RFC1155-SMI
RFC1213-MIB
RFC-1215
Product Specific and Depended MIBs:
MIB File MIB Module Name Dependent MIBs
cpqoneview CPQOneView-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1215
CPQHOST-MIBRFC1155-SMI
RFC1213-MIB
RFC-1215
CPQHOST-MIB
iLO 4 MIBs
MIB File Name MIB Module Name Comments
cpqida.mib CPQIDA-MIB Handling the Drive Array
cpqhost.mib CPQHOST-MIB Handling server's host System details
cpqhlth.mib CPQHLTH-MIB Handling server health system
cpqsm2.mib CPQSM2-MIB Handling the Remote Insight/Integrated Lights-Out
cpqide.mib CPQIDE-MIB Handling the IDE sub system
cpqscsi.mib CPQSCSI-MIB Handling the SCSI system
cpqnic.mib CPQNIC-MIB Handling the system NIC
cpqstsys.mib CPQSTSYS-MIB Handling storage systems
cpqstdeq.mib CPQSTDEQ-MIB Handling server standard equipment
cpqfca.mib CPQFCA-MIB Handling Fibre Channel Array
iLO 4 Traps/Notifications
Trap/Notification name MIB Module Name Comments
Cold Start Trap 0 SNMPv2-
MIB
SNMP has been initialized, the system has
completed POST, or AMS has started.
Authentication Failure Trap 4 SNMPv2-
MIB
SNMP has detected an authentication failure.
cpqSeCpuStatusChange 1006 cpqstdeq An uncorrectable machine check exception has
been detected in a processor.
cpqSeUSBStorageDeviceReadErrorOccurred
1010
cpqstdeq A read error occurred on an attached USB storage
device.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 24
Trap/Notification name MIB Module Name Comments
cpqSeUSBStorageDeviceWriteErrorOccurred 1011 cpqstdeq A write error occurred on an attached USB storage
device.
cpqSeUSBStorageDeviceRedundancyLost
1012
cpqstdeq USB storage device redundancy was lost.
cpqSeUSBStorageDeviceRedundancyRestored 1013 cpqstdeq USB storage device redundancy was restored.
cpqSeUSBStorageDeviceSyncFailed 1014 cpqstdeq The sync operation to restore USB storage device
redundancy failed.
cpqSePCIeDiskTemperatureFailed 1015 cpqstdeq Temperature of the disk has crossed the upper
critical threshold
cpqSePCIeDiskTemperatureOk 1016 cpqstdeq The temperature of the disk has been set to ok
cpqSePCIeDiskConditionChange 1017 cpqstdeq PCIe Disk Status Change
PCIe Disk Wear Status Change
cpqSePCIeDiskWearStatusChange 1018 cpqstdeq PCIe Disk Wear Status Change
cpqSePciDeviceAddedOrPoweredOn 1019 cpqstdeq A PCI device has been added or powered on
cpqSePciDeviceRemovedOrPoweredOff 1020 cpqstdeq A PCI device has been removed or powered off
cpqDa6CntlrStatusChange 3033 cpqida A change has been detected in the status of the
Smart Array controller.
cpqDa6LogDrvStatusChange 3034 cpqida A change has been detected in the status of a Smart
Array logical drive.
cpqDa6AccelStatusChange 3038 cpqida A change has been detected in the status of a Smart
Array cache module.
cpqDa6AccelBadDataTrap 3039 cpqida The Smart Array cache module has lost backup
power.
cpqDa6AccelBatteryFailed 3040 cpqida The Smart Array cache module backup power has
failed.
cpqDa7PhyDrvStatusChange 3046 cpqida A change has been detected in the status of a Smart
Array physical drive.
cpqDa7SpareStatusChange 3047 cpqida A change has been detected in the status of a Smart
Array spare drive.
cpqDaPhyDrvSSDWearStatusChange 3049 cpqida A change has been detected in the SSD wear status
of a Smart Array physical drive.
cpqHe3ThermalConfirmation 6026 cpqhlth The server was shut down due to a thermal
anomaly and is now operational.
cpqHe3PostError 6027 cpqhlth One or more POST errors have occurred.
cpqHe3FltTolPowerRedundancyLost 6032 cpqhlth The fault-tolerant power supplies have lost
redundancy for the specified chassis.
cpqHe3FltTolPowerSupplyInserted 6033 cpqhlth A fault-tolerant power supply has been inserted.
cpqHe3FltTolPowerSupplyRemoved 6034 cpqhlth A fault-tolerant power supply has been removed.
cpqHe3FltTolFanDegraded 6035 cpqhlth The fault-tolerant fan condition has been set to
Degraded.
cpqHe3FltTolFanFailed 6036 cpqhlth The fault-tolerant fan condition has been set to
Failed.
cpqHe3FltTolFanRedundancyLost 6037 cpqhlth The fault-tolerant fans have lost redundancy.
cpqHe3FltTolFanInserted 6038 cpqhlth A fault-tolerant fan has been inserted.
cpqHe3FltTolFanRemoved 6039 cpqhlth A fault-tolerant fan has been removed.
cpqHe3TemperatureDegraded 6041 cpqhlth The temperature status has been set to Degraded,
and the temperature is outside the normal operating
range. Depending on the system configuration, this
system might be shut down.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 25
Trap/Notification name MIB Module Name Comments
cpqHe3TemperatureOk 6042 cpqhlth The temperature status has been set to OK.
cpqHe4FltTolPowerSupplyOk 6048 cpqhlth The fault-tolerant power supply condition has been
reset to OK.
cpqHe4FltTolPowerSupplyDegraded 6049 cpqhlth The fault-tolerant power supply condition has been
set to Degraded.
cpqHe4FltTolPowerSupplyFailed 6050 cpqhlth The fault-tolerant power supply condition has been
set to Failed.
cpqHeResilientMemMirroredMemoryEngaged 6051 cpqhlth The Advanced Memory Protection subsystem has
detected a memory fault. Mirrored Memory has
been activated.
cpqHe3FltTolPowerRedundancyRestore 6054 cpqhlth The fault-tolerant power supplies have returned to a
redundant state.
cpqHe3FltTolFanRedundancyRestored 6055 cpqhlth The fault-tolerant fans have returned to a redundant
state.
cpqHe5CorrMemReplaceMemModule 6064 cpqhlth Memory errors have been corrected. Replace the
memory module.
cpqHe4FltTolPowerSupplyACpowerloss 6069 cpqhlth The fault-tolerant power supply in the specified chassis
and bay reported AC power loss.
cpqHeSysBatteryFailed 6070 cpqhlth The HPE Smart Storage Battery has failed.
cpqHeSysBatteryRemoved 6071 cpqhlth The HPE Smart Storage Battery has been removed.
cpqHeSysPwrAllocationNotOptimized 6072 cpqhlth iLO could not determine the power requirements.
The server power allocation is not optimized.
cpqHeSysPwrOnDenied 6073 cpqhlth The server could not power on because the
hardware cannot be identified.
cpqHePowerFailureError 6074 cpqhlth A device power failure has been detected.
cpqHeInterlockFailureError 6075 cpqhlth A device is missing or improperly seated on the
system board.
cpqSs6FanStatusChange 8029 cpqstsys The storage enclosure fan status changed.
cpqSs6TempStatusChange 8030 cpqstsys The storage enclosure temperature status changed.
cpqSs6PwrSupplyStatusChange 8031 cpqstsys The storage enclosure power status changed.
cpqSsConnectionStatusChange 8032 cpqstsys The storage enclosure status changed.
cpqSm2ServerReset 9001 cpqsm2 The server power has been reset.
cpqSm2UnauthorizedLoginAttempts 9003 cpqsm2 The maximum unauthorized login attempt threshold
has been exceeded.
cpqSm2SelfTestError 9005 cpqsm2 iLO 4 has detected a self test error.
cpqSm2SecurityOverrideEngaged 9012 cpqsm2 iLO 4 has detected that the security override jumper
has been toggled to the engaged position.
cpqSm2SecurityOverrideDisengaged 9013 cpqsm2 iLO 4 has detected that the security override jumper
has been toggled to the disengaged position.
cpqSm2ServerPowerOn 9017 cpqsm2 The server has been powered on.
cpqSm2ServerPowerOff 9018 cpqsm2 The server has been powered off.
cpqSm2ServerPowerOnFailure 9019 cpqsm2 A request was made to power on the server, but the
server could not be powered on because of a failure
condition.
cpqSm2IrsCommFailure 9020 cpqsm2 Communication with Insight Remote Support or Insight
Online has failed.
cpqHo2GenericTrap 11003 cpqhost Generic trap. Verifies that the SNMP configuration,
client SNMP console, and network are operating
correctly. You can use the iLO web interface to
generate this alert to verify receipt of the alert on the
SNMP console.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 26
Trap/Notification name MIB Module Name Comments
cpqHo2PowerThresholdTrap 11018 cpqhost A power threshold has been exceeded.
cpqHoMibHealthStatusArrayChangeTrap
11020
cpqhost A change in the health status of the server has
occurred.
cpqSasPhyDrvStatusChange 5022 cpqscsi AMS detected a change in the status of an SAS or
SATA physical drive.
cpqSasPhyDrvSSDWearStatusChange 5026 cpqscsi AMS detected a change in the Solid State Disk
Wear Status
cpqIdeAtaDiskStatusChange 14004 cpqide AMS detected a change in the status of an ATA disk
drive.
cpqFca3HostCntlrStatusChange 16028 cpqfca AMS detected a change in the status of a Fibre
Channel host controller.
cpqNic3ConnectivityRestored 18011 cpqnic Indicate that connectivity was restored to a logical network
adapter.
cpqNic3ConnectivityLost 18012 cpqnic AMS detected that the status of a logical network
adapter changed to Failed.
cpqNic3RedundancyIncreased 18013 cpqnic AMS detected that a previously failed physical
adapter in a connected logical adapter group
returned to the OK status.
cpqNic3RedundancyReduced 18014 cpqnic AMS detected that a physical adapter in a logical
adapter group changed to Failed status, but at least
one physical adapter remains in OK status.
iLO 4 MIB Loading order
Following MIBs (file) must be loaded in the MIB Browser before loading iLO 4 specific MIBs.
Common MIBs:
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
RFC1213-MIB
Product Specific and Depended MIBs:
MIB File MIB Module Name Dependent MIBs
cpqida.mib CPQIDA-MIB RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
RFC1213-MIB
CPQHOST-MIB
cpqhost.mib CPQHOST-MIB RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
RFC1213-MIB
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 27
cpqhlth.mib CPQHLTH-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
CPQSINFO-MIB
cpqsm2.mib CPQSM2-MIB RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
CPQHOST-MIB
CPQSINFO-MIB
cpqide.mib CPQIDE-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
cpqscsi.mib CPQSCSI-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
cpqnic.mib CPQNIC-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
CPQSINFO-MIB
CPQSTDEQ-MIB
cpqstsys.mib CPQSTSYS-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
cpqstdeq.mib CPQSTDEQ-MIB CPQHOST-MIB
RFC1155-SMI
SNMPv2-SMI
RFC1213-MIB
RFC-1212
RFC-1215
cpqfca.mib CPQFCA-MIB CPQHOST-MIB
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
CPQSTSYS-MIB
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 28
Onboard Administrator MIBs
MIB File Name MIB Module Name Comments
cpqrack.mib CPQRACK-MIB Handling Rack Information
cpqhost.mib CPQHOST-MIB Handling server's host system details
Onboard Administrator Traps/Notifications
Trap/Notification name MIB Module Name Comments
cpqRackNameChanged CPQRACK-MIB Rack Name has changed
cpqRackEnclosureNameChanged CPQRACK-MIB Enclosure Name has changed
cpqRackEnclosureRemoved CPQRACK-MIB Linked Enclosure removal detected
cpqRackEnclosureInserted CPQRACK-MIB Linked Enclosure insertion detected
cpqRackEnclosureFanFailed CPQRACK-MIB Enclosure fan has failed
cpqRackEnclosureFanDegraded CPQRACK-MIB Enclosure fan is degraded
cpqRackEnclosureFanOk
cpqRackEnclosureFanOk
CPQRACK-MIB Enclosure fan is OK
cpqRackEnclosureFanRemoved CPQRACK-MIB Enclosure fan is removed
cpqRackEnclosureFanInserted CPQRACK-MIB Enclosure fan is inserted
cpqRackPowerSupplyFailed CPQRACK-MIB Enclosure power supply has failed
cpqRackPowerSupplyDegraded CPQRACK-MIB Enclosure power supply is degraded
cpqRackPowerSupplyOk CPQRACK-MIB Enclosure power supply is OK
cpqRackPowerSupplyRemoved CPQRACK-MIB Enclosure power supply is removed
cpqRackPowerSupplyInserted CPQRACK-MIB Enclosure power supply is inserted
cpqRackPowerSubsystemNotRedundant CPQRACK-MIB Enclosure power subsystem is not redundant
cpqRackPowerSubsystemLineVoltageProblem CPQRACK-MIB Enclosure power subsystem line voltage
problem
cpqRackPowerSubsystemOverloadCondition CPQRACK-MIB Enclosure power subsystem overload
condition
cpqRackServerBladeRemoved CPQRACK-MIB Blade removed (replaced by 22050 in OA
v1.30)
cpqRackServerBladeInserted CPQRACK-MIB Blade inserted (replaced by 22051 in OA
v1.30)
cpqRackEnclosureManagerDegraded CPQRACK-MIB Onboard Administrator degraded
cpqRackEnclosureManagerOk CPQRACK-MIB Onboard Administrator OK
cpqRackEnclosureManagerRemoved CPQRACK-MIB Onboard Administrator removed
cpqRackEnclosureManagerInserted CPQRACK-MIB Onboard Administrator inserted
cpqRackManagerPrimaryRole CPQRACK-MIB Onboard Administrator is Active
cpqRackServerBladeEKeyingFailed CPQRACK-MIB Blade eKeying config failed
cpqRackNetConnectorRemoved CPQRACK-MIB Interconnect removed
cpqRackNetConnectorInserted CPQRACK-MIB Interconnect inserted
cpqRackNetConnectorFailed CPQRACK-MIB Interconnect failed
cpqRackNetConnectorDegraded CPQRACK-MIB Interconnect degraded
cpqRackNetConnectorOk CPQRACK-MIB Interconnect OK
cpqRackServerBladeToLowPower CPQRACK-MIB Blade requested too low power
cpqRackServerBladeRemoved2 CPQRACK-MIB Blade removed2
cpqRackServerBladeInserted2 CPQRACK-MIB Blade inserted2
cpqRackEnclosureManagerLinkDown CPQRACK-MIB Standby Onboard Administrator network link
down
cpqRackEnclosureManagerLinkUp CPQRACK-MIB Standby Onboard Administrator network link
up
cpqRackErsCommFailure CPQRACK-MIB Onboard Administrator to remote support
communication failure
cpqRackPowerSubsystemOverloadConditionR
epaired
CPQRACK-MIB Enclosure power subsystem overload
condition was repaired
cpqHo2GenericTrap CPQHOST-MIB Test Trap
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 29
Onboard Administrator MIB Loading order
Following MIBs (file) must be loaded in the MIB Browser before loading Onboard Administrator specific MIBs.
Common MIBs:
RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
Product Specific and Depended MIBs:
MIB File MIB Module Name Dependent MIBs
cpqrack.mib CPQRACK-MIB RFC1213-MIB
RFC-1212
RFC-1215
CPQHOST-MIB
cpqhost.mib CPQHOST-MIB RFC1155-SMI
RFC1213-MIB
RFC-1212
RFC-1215
Rack and Power Infrastructure MIBs
MIB File Name MIB Module Name Comments
CPQPOWER.MIB CPQPOWER-MIB UPS, PDU, Power Mgnt Module
Rack and Power Infrastructure: Traps/Notifications
Trap/Notification name MIB Module Name Comments
Critical CPQPOWER-MIB
Warning CPQPOWER-MIB
Informative CPQPOWER-MIB
Test Trap CPQPOWER-MIB
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 30
Rack and Power Infrastructure MIB Loading order
Following MIBs (file) must be loaded in the MIB Browser before loading CPQPOWER.MIB specific MIBs.
Common MIBs:
RFC1213-MIB
RFC1155-SMI
RFC1215
RFC1212
CPQHOST-MIB
Product Specific and Depended MIBs:
MIB File MIB Module Name Dependent MIBs
CPQHOST.MIB CPQHOST-MIB UPS, PDU, Power Mgnt Module
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 31
MIBs Trap Info
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_340.
mib
CPQHSV340V1
1-MIB
sCellEventTrap-0c-63 Severity: Normal -- informational in nature. The
members of the specified Source Data Replication
Group have not been presented to the host because
the remote Storage System is not accessible and the
failsafe on link-down/power-up state is enabled:
Suspend\Resume Source Data Replication Group to
override this behavior, which will present the
members.
Ashcroft_HSV_340.
mib
CPQHSV340V1
1-MIB
sCellEventTrap-0c-85 Severity: Normal -- informational in nature. The
Source Virtual Disk in group Data Replication Group
has cleared its rw_bitmap.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-1 Object Already Exists
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-10 Invalid Loop Configuration
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-100 Login required - password changed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1000
Logical Disk Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10001
Storage Object Broker Ready
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10004
The storage system object could not be found.
Refresh of the view is required.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10006
SOB Memory Allocation Failure
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1001
Storage system is FULL **critical**
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10010
Your initialized system must have at least one disk
group
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10011
Cannot talk to all available controllers
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10012
Command rejected - Folder is not empty
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10013
Command rejected - Vdisk(s), Container(s) or a data
replication log are contained in this disk group
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10014
Command rejected - Vdisk(s) are presented to this
host
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10015
Command rejected - This Vdisk has a sharing
relationship with another object
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10017
Command rejected - Number of disk groups will
exceed the maximum allowable number
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10018
Cannot access the password file
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10019
Enterprise Login - Complete
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1002
Disk group capacity reached Critical level.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10020
Command rejected - Disks in the group would go
below the minimum required number.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10021
Rediscovery of controllers - Complete
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 32
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10022
Unable to establish communication with controller,
check all connections.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10023
Disk Group Data Lost Error Resolution Sequence 3 -
Disk group resolved to normal
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10024
Disk Group Data Lost Error Resolution Sequence 1 -
Failed Vdisks marked for deletion
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10025
Disk Group Data Lost Error Resolution Sequence 2 -
Failed Vdisks deletion in progress
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10026
Disk Group Data Lost Error Resolution Sequence 3 -
Disk group deleted
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10027
Creating the Vdisk would exceed the maximum
allowable Vdisk count
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10028
Volume insufficient resources
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10029
Process mutex is locked
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1003
Controller Cache Battery Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10030
Invalid URL request type
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10031
Invalid URL object type
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10035
The snapshot/Snapclone license cannot be validated.
Either the license key has not been entered, or there
is a system communication failure.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10036
A data replication license cannot be validated. Either
the license key has not been entered, or there is a
system communication failure.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10037
Object name should not be empty or exceed its
maximum length
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10038
Object comments exceeds maximum length
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10039
Vdisk does not meet the requirements to be part of a
DR group.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1004
Controller Cache Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10040
The array selected as the Destination for the DR
group is invalid. Either it has a DR relationship with
another array or it is not the same array that the
source array presently has a DR relationship with.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10041
Cannot group the specified disk device because the
disk is already in a disk group.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10042
Cannot ungroup the specified disk device because the
disk is not grouped.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10043
Object ID provided, or object type, is invalid for the
requested operation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10044
Specified remote disk group does not exist.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10047
The maximum number of iSCSI Controllers per array
has been reached.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 33
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10048
The iSCSI Host object cannot be deleted.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10049
Error received from the iSCSI Controller. See log file
for details.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1005
Controller Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10050
All presentations to the iSCSI host must be removed
first.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10051
All iSCSI presentations must be removed first.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10052
Configuration Error - This iSCSI controller cannot
communicate with the selected storage cell.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10053
No iSCSI Controller found.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10054
A reboot of your iSCSI Controllers is required in order
for the parameter changes to take effect.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10055
The specified iSCSI host os type is not supported.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10056
Adding an iSCSI controller requires the automatic
creation of an iSCSI host object but the maximum
number of host objects has been exceeded.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10057
Multiple iSCSI controllers are configured however one
or more are currently not available. All configured
iSCSI controllers must be functional in order to
continue with this operation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10058
This multi-attach (snap) item will not be processed
because it exceeds the maximum allowable
attach/snap count.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10059
Command Rejected - At least one snap item should
be specified in the multi-attach (snap) operation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1006
Controller FC Port Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10060
All snap items in the multi-attach operation failed.
Please check individual snap items result code for
details.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10061
Mirror Clone must be detached before deleting.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10062
Asynchronous DR Group mode cannot be created
between specified systems.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10063
iSCSI host initiator not found with discovered iSCSI
controllers.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10064
Adding an iSCSI host requires valid iSCSI node name.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10065
Selected iSCSI initiator node already associated with
Host.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10066
iSCSI Host creation failed. Maximum number of iSCSI
hosts reached.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10067
Operation not allowed on selected host.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 34
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10068
This multi-mirror operation will not be processed
because it exceeds the maximum mirror item-count.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10069
Command Rejected - At least one mirror item should
be specified in the multi-mirror command.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1007
Physical Device Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10070
All mirror items in the multi-mirror command failed.
Please check individual mirror items result code for
details.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10071
There is no operation type specified for this command.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10072
Could not verify the completion of this operation due
to could not locate the mirrorclone.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10073
Mirrorclone is fractured
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10074
Mirrorclone is detached
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10075
Failed Vdisk has a Mirror Clone relationship. Retry
after detaching the Mirror Clones attached to failed
vdisks.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10076
Maximum Number of allowed iSCSI Host
Presentations reached.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10077
Discovered iSCSI Controller already exist.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10078
Not a supported configuration. Both HP Storage
Works MPX200 controllers should belong to same
Chassis/Enclosure.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10079
Not a supported configuration. HP Storage Works
MPX200 cannot be discovered with this array.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1008
Physical Store Condition Change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10080
Not a supported configuration. HP Storage Works
MPX200 controller host port specified does not exist.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10081
Unable to process command at this time. Check all
connections as iSCSI controller fibre channel ports are
unavailable.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10082
Invalid iSCSI controller configuration file extension.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10083
Saving iSCSI Controller configuration process have
been failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10084
Selected iSCSI host cannot be added to iscsi
controller to proceed with this presentation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10085
Operation failed. iSCSI controller code load file cannot
open/read.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10086
iSCSI Controller code load process have been failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10087
Invalid iSCSI controller code load file extension.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 35
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10088
Not a supported configuration. Discovery of HP
Storage Works MPX200 controller with Direct
connects Fibre Channel attachment mode not
allowed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10089
Discovered iSCSI Controller not found with selected
array.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1009
Host condition change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10093
Mirrorclone inversion is successful
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10094
Virtual Disk Migration Failed
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10095
Operation failed. iSCSI Controller event logs cannot
retrieve.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10096
Save iSCSI Controller event logs process have been
failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10097
Clear iSCSI Controller event logs process have been
failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10098
Failed to retrieve licensing information of iSCSI
controller.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10099
Error. Add iSCSI Controller license operation failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-101 Numerous login attempts have been detected that
uses an incorrect password. Please update your
systems password in the Storage System Access
menu.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1010
Storage system time has been set
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10100
Error. iSCSI Controller license feature keys already
presented.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10101
Not a supported operation. FCoE Host creation not
allowed with currently discovered iSCSI controller.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10102
Selected FCoE initiator node already associated with
Host.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10103
Invalid FCoE initiator node name format.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10104
Adding an FCoE host requires valid FCoE port
worldwide name.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10105
FCoE Host creation failed. Maximum number of FCoE
hosts reached.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10106
An iSCSI host presentation has been found.
Unpresent this Vdisk and represent to the FCoE host
first, then add the iSCSI host presentation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10107
Selected FCoE host cannot be added to iscsi
controller to proceed with this presentation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10108
The virtual disk operation has failed. Please make
sure that FC targets and FCoE portal connections are
online.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10109
Maximum Number of allowed FCoE Host
Presentations reached.
Compiling and customizing SNMP MIBs with HPE SIM Technical proposal
Page 36
MIB File Name MIB Module
Name
Trap / Notification
Name
Trap Description / Comments
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1011
Volume Condition change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10110
All presentations to the FCoE host must be removed
first.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10111
The FCoE Host object cannot be deleted.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10112
All FCoE presentations must be removed first.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10113
Operation failed. Failed to retrieve iSCSI Controller
slot information.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10114
FCoE host initiator not found with discovered FCoE
controllers.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10115
Unexpected mirror clone condition after mirror
operation.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10116
iSCSI controller pairing operation has been failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10117
iSCSI controller pairing not available.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10118
iSCSI controller remove pairing operation has been
failed.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1012
Volume insufficient_resources condition change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10121
Successfully enabled Enhanced Connectivity option
for the discovered iSCSI Controllers.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
10122
Enabling Enhanced Connectivity option for the
discovered iSCSI Controllers has been unsuccessful.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1013
Volume Quorum Disk change
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1014
The state of an object in the system has changed.
View adjacent events for more detail.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1015
Disk group capacity returned to below Critical level.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1016
Disk group capacity reached Warning level.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1017
Disk group capacity returned to below Warning level.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1018
Vdisk reached Allocation alarm level.
Ashcroft_HSV_360.
mib
CPQHSV360V1
1-MIB
mngmtAgentTrap-
1019
Vdisk returned to below Allocation alarm level.
Ashcroft_HSV_360.
top related