OpenManage Essentials MIB Import Utility

Systems Management - Wiki

Dell - Internal Use - Confidential

Why do I want to use this tool?

OpenManage Essentials provides support for formatting hardware alerts (i.e., SNMP traps) for
most Dell enterprise hardware. If you want to monitor non-Dell devices, you can use the
OpenManage Essentials MIB Import Utility to define new alerts for OpenManage Essentials.
Dell - Internal Use - Confidential

Defining alerts enables OpenManage Essentials to monitor a wider range of hardware and to set
up email and forwarding rules for these devices. The MIB Import Utility is an optional tool that
is only required if you want to add support for formatting alerts received from third-party
devices.
The details:
Dell OpenManage Essentials MIB Import Utility enables you to extract trap definitions from
SMIv1 or SMIv2 management information base (MIB) files. The extracted traps can be viewed
and edited before importing them to OpenManage Essentials. This tool also enables you to
manually define and manage traps. Using the imported and manually-managed trap definitions,
OpenManage Essentials classifies the incoming trap from a specific device as expected.
If you want to monitor (classify incoming SNMP traps) a SNMP supported device that is not
currently supported by OpenManage Essentials, use MIB Import Utility to import or manually
define that devices SNMP trap definitions for OpenManage Essentials.
Please review the readme file after you install this tool. The readme also provides a list of some
of
the MIBs that have been tested using this tool. Feel free to post updates on the DTC/OME
forum including MIBs that you have imported using this tool. Your posts would be of help to the
community.
Understandably, all MIBs are different and not all MIBs adhere to the specifications. This tool
tries to accommodate these differences, but if you notice any issues with a MIB you are trying to
import, post a question on the OpenManage Essentials forum.
Ensure the following before using this utility:

The remote device supports SNMP (v1/v2) protocol.

SNMP services on the remote device are working fine and trap destination
point to
the OME system.

You have the device specific SNMP MIB files (main MIB and its reference
MIBs).

Validate these specific MIB(s) using a standard MIB compiler tool.

Getting HP servers on Dell OME - Which MIB to use

I recently set up Dell OME at my new company and have it running reliably and reporting
regularly with Support Assist.

Dell - Internal Use - Confidential

I've been using the product for years but haven't played around with importing MIBs. This
company has a few HP Proliants that I'd like to get monitored without having to resort to setting
up Insight Manager.
But I'm having some problems with getting the HP server recognized-- I don't get anything other
than it being classified as "unknown" with a like health status.

I've downloaded the latest 9.3 MIBs update pack from HP, and have imported them into OME.
I've set the SNMP traps and everything on the HP server-- so what am I missing?
Yes, I've already been to
en.community.dell.com/.../3570.openmanage-essentials-mib-import-utility.aspx
have downloaded and read the guide and but nothing is clearly stated as to how to do this.
Is there a particular MIB I need to import? The guide mentions CPQ-IDA.MIB and CPQHOST.MIB in the screenshots from the guide... but still, it's a no-go!
Thanks for your assistance!
--

Dell - Internal Use - Confidential

Hi Matthew and thanks for your well written post.

I suspect you are doing everything ok.
The MIB import tool only provides the ability to properly format the traps from 3rd party MIBs.
It does not provide a way to add 3rd party device support to OME. That is the difference.
Table 1 in the whitepaper shows what the benefits are to importing the MIB and how the traps
will then be formatted in OME.
But you won't see it show up classified in the device tree with health etc. So one can say that
importing the MIB provides 'second' class support in OME (formatted alerts), but not "first class"
(device tree, health, etc.).
What some folks do is create a custom group on the tree and include the HP servers by virtue of
a special ip range or some other criteria. This will at least group them for you.
Hope that helps,
Rob
OME 1.0.1 will provide for health reporting on Dell hardware only.
So the health icon on the device tree and in the device health pie chart will only work for Dell
hardware.
But....we _can_ import MIBS from other devices like HP, IBM, etc. This will allow you to get
formatted SNMP traps in the OME event console. And you can set up email or forwarding rules
to help process these alerts.
--

@ HoosierCAB Many thanks, any feedback would be great!

@ Dell-Manoj P The "HP-SWITCH-BASIC-CONFIG-MIB" is included in the MIBs from HP,
as mentioned the Dell utility doesnt seem to parse them correctly.
The download link for the MIBs is:
https://h10145.www1.hp.com/Downloads/DownloadSoftware.aspx?
SoftwareReleaseUId=9474&ProductNumber=J8697A&lang=en&cc=us&prodSeriesId=1827663
&SerialNumber=&PurchaseDate=
But as you can see from the screenshots, only two are ever imported.

Dell - Internal Use - Confidential

--

Hi,
I looked at the MIB and it looks to be having only 2 trap definitions (I searched for
"NOTIFICATION-TYPE" in the MIB). Hope I am not looking at different file.
Please note that, "OBJECT-TYPE" are attributes and not trap definitions. MIBImport utility
imports only trap definitions.
Regards,
==

Dell - Internal Use - Confidential

My company is a small subcontractor for a much larger company. I'm looking for a way to
remotely manage all the laptops, desktops, and servers we have on the parent company's domain.
I am the only IT guy for my company, and unfortunately I am not a domain admin for the larger
company. Since we are in the process of replacing our old HP laptops with nice new Dell laptops,
I poked around and found OpenManage Essentials.
I played with OpenManage as time permitted today. It has all the fields for all the information I
want (asset tag, installed ram, warranty info, etc), however none of that information gets
collected when adding our legacy HP laptops and some of the aging ProLiant servers. Its
apparent that even though I specify WMI discovery and give administrative credentials, WMI is
not used to get the information.
Will OpenManage work with non-Dell equipment? Did I add the HP's in the wrong way? Is there
a way to manually edit the discovered computers so that the fields aren't all blank? If
OpenManage won't fill my needs, is anyone aware of a similar product?
--

Hi Tim,
Thanks for the post and glad to know that you are evaluating OpenManage Essentials (OME).
OME is primarily designed to support Dell devices like Dell Servers, storage, networking
devices, clients (workstation/laptops) and support features like inventory, event monitoring,
health monitoring, system update, configuration base-line and bare metal deployment, etc. (Refer

Dell OpenManage Essentials Version 2.1 Support Matrix for details).

However, you can do event monitoring for non-dell devices by using MIB Import utility and
importing the required MIB files for the devices (Refer Dell OpenManage Essentials MIB
Import Utility - Monitoring HP Servers for details).
For discovering ProLiant Servers, you can try discovering the same via IPMI protocol and see if
it helps you with the desired inventory information you are looking for (Refer Managing
Devices via IPMI in OpenManage Essentials - section "Using IPMI to manage HP iLO and
IBM IMM").
Let us know if you have any further queries as you use OME :).
Thanks,
Vijay
==
how to "move" all hardwares monitored to new OME server/environment

Dell - Internal Use - Confidential

Hi OME support,
I recently setup a new OME monitoring server with OME v2.1 installed, how do I proceed to
batch "transfer" all the hardwares currently monitored by my current OME server to this new
OME server ?
Hi,
If you have the db back up of older OME, then you can use that db back up while installing new
OME and that should get you all the older servers monitored by new OME. After installation of
new OME, there is no way to transfer the monitored hardware. The user guide lists out steps on
how to backup the OME db. Hope this helps.
==

Hi, thanks for the query.

Monitoring of non-Dell hardware is not supported in OME. Hardware inventory details and
health cannot be recorded. However, you can enable receipt of formatted traps from such targets
by importing respective MIBs into OME using MIB Import utility.
Hope this helps!
==

MIBs and OIDs for HP servers

This question has been Answered.

licensing@nlc.com.au Dec 28, 2010 9:49 PM

Hey guys, just wondering which MIBs/OIDs are used to monitor HP server hardware. I want to
set up traps for specific hardware failure (RAM and disk array in particular).
Thanks in advance.
Gran
Hi Grant,
I'm not sure about SNMP Traps, but normally the following OIDs are used with the Custom
SNMP Monitor to monitor various items:
For Compaq/HP Servers:
Dell - Internal Use - Confidential

1.3.6.1.4.1.232.6.1.3.0 - System status

1.3.6.1.4.1.232.3.2.2.1.10.6 - Raid status

1.3.6.1.4.1.232.3.2.2.2.1.5 - RAID accelerator status

1.3.6.1.4.1.232.3.2.5.1.1.37 - Drive condition

1.3.6.1.4.1.232.6.2.6.7.1.6 - Fan speed

1.3.6.1.4.1.232.6.2.6.4 - Fan status

1.3.6.1.4.1.232.6.2.14.4 - Memory status

1.3.6.1.4.1.232.6.2.9.3.1.4 - PSU status.

1.3.6.1.4.1.232.6.2.6.1 - Overall thermal status

For Dell System:

1.3.6.1.4.1.674.10892.1.200.10.1.4.1 - SystemStateChassisStatus

1.3.6.1.4.1.674.10893.1.20.110.13.0 - AgentGlobalSystemStatus

1.3.6.1.4.1.674.10893.1.1.130.4.1.4 - Disk State

1.3.6.1.4.1.674.10893.1.20.130.4.1.4 - ArrayDiskState

1.3.6.1.4.1.674.10893.1.1.130.1.1.5 - Controller State

1.3.6.1.4.1.674.10893.1.1.2 - Array Manager Global Status

Hope this helps.

Chris Foley
==

I want to download DL 380p Gen8 Mib

From the events i've seen you need the cpqhost and hphealth mibs. There are no specific gen8
mibs just server mibs.
Summary

Dell - Internal Use - Confidential

Device Type

HP Proliant Servers

Object Identifier

Mibs

CPQHLTH-MIB

CPQIDA-MIB

CPQFCA-MIB

CPQIDA-MIB

CPQNIC-MIB

CPQHOST MIB

Inherits Compaq Server properties

Dell - Internal Use - Confidential

What to Monitor
HP Proliant Servers are preferred by administrators in datacenters and growing small and
medium enterprises as it addresses the power and space constraint needs. It has a few variants
including the BladeSystem.
The hardware health of the HP Proliant systems depends on the performance of the
temperature sensors, the fan status and speed, the proper functioning of the power module,
other than the usual suspects i.e., memory, processor and disk. In addition to these hardware
health monitors, these systems provide an handle to monitor other metrics specific to the
system status that include AMP (Advanced Memory Protection), Drive Array status, Network
interface status etc.

Temperature: The server temperature must be maintained within the operating range.
An increased temperature may result in server shutdown which means a downtime!
HP Proliant systems can have many temperature sensors. Monitoring the temperature
and the temperature thresholds are a proactive way of keeping a check on the
temperature. You can also monitor the system generated logs as an added measure.
The fan adjusts its speed to bring down the temperature which warrants monitoring the
fan speed and status too.

Fan: As mentioned above, the fan cools the server when there is an increase in the
temperature. Some systems have fans with variable speed that allows it to adjust the
speed according to the server temperature. Improper functioning of the fan can lead to
the temperature overshooting the threshold and in the absence of a redundant cooling
fan, it can cause server shutdown.

Power: The HP Proliant servers that come with a fault-tolerant power supply
architecture have the load distributed equally. In the event of a supply failure,
uninterrupted supply is made available using the backup power. Monitoring the power
supply status, the state of power redundancy, the used power capacity etc reflect the
health of the power module.

Advanced Memory Protection and Memory Monitoring: Besides the regular resource
utilization monitors, these systems have what is called the 'AMP- Advanced Memory
Protection or the resilient memory subsystem that aids increased fault tolerance,
ensuring high availability of services hosted on these servers.. It comprises features
such as online spare memory, mirrored memory, hot replace etc. An overall health
status monitoring of this module helps administrators take informed decisions.

CPU Monitoring: The status of the processor, the utilization of CPU, the CPU speed
etc are some of the metrics that need monitoring to avert degradation of server health
because of a poor performance of this resource

Dell - Internal Use - Confidential

Monitor

SNMP OID

CPU Monitors

Details
TOP ^
"This is the current
temperature sensor reading in
degrees
celsius.

Temperature

.1.3.6.1.4.1.232.6.2.6.8.1.4

If this value cannot be

determined by software, then a
value
of -1 will be returned."

This specifies the speed of the

fan. This value will be set
if the fan type is tachOutput."
Fan speed

CPU speed

.1.3.6.1.4.1.232.6.2.6.7.1.6

.1.3.6.1.4.1.232.1.2.2.1.1.4

Resource Utilizaton

CPU Utilization

.1.3.6.1.2.1.25.3.3.1.2

Memory Utilization

.1.3.6.1.2.1.25.5.1.1.2

Disk Utilization

1.3.6.1.2.1.25.2.3.1.6

It returns one of these results

on query: other ( 1 ) , normal (
2 ) , high ( 3 )
This is the internal speed in
megahertz of this processor.
Zero is returned if this value is
not available.
The utilization of system
resources are monitored if
HostResource Mib is
implemented on the system.
The host physical and paging
memory can be monitored by
querying the relevant OIDs
from CPQHOST MIB.

This system supports

redundant power supply for
efficiency and high
availability. Monitoring this
variable gives the condition or
Dell - Internal Use - Confidential

Dell - Internal Use - Confidential