Thanks for your post. There are some new traps introduced with ESXi 5.0 and we'll have the future versions of OME pick these up and format/interprete these.

Ok thanks

Hope it will be a release soon

Any news on this? Have been looking around the net but still no release...

Very nice,

looking forward to it.

OME next version is slated to release during Q3/Q4 this year.

We are also looking at releasing MIB import tool for OME which allows importing of external MIBs so that the traps can be formatted. This tool will be releasing soon.

i still get these with v1.1.  You can change the snmp settings on the esxi hosts to send hardware only events which stops them from being sent out.

Is there any progress on this?

I am also seeing these alerts from ESXi 5.0

Thanks Andy,

Yeah it looks look these are still not defined in OME 1.1.  As you mentioned, folks will change the settings to not send the heartbeat alerts from ESXi.

Thx,

Rob

Can you provide details on how to not send the heartbeat alerts from ESXi?

TIA

Link to ESXi user guide: en.community.dell.com/.../20224619.aspx

Other option is to ignore these alerts in OME:

1.3.6.1.4.1.6876.4.90 is a “vmwCimOmHeartbeat” SNMP trap (EOID: .1.3.6.1.4.1.6876.4.90 , Specific TrapID: 401)  defined in the VMWARE-CIMOM-MIB.MIB.

How can I ignore/discard the VMWare (ESXi) heartbeat SNMP trap in OME ?

You need to parse and import this trap(alert) definition from VMWARE-CIMOM-MIB.MIB using OME’s MIBImport tool. Once imported, define a ignore alert action in OME: Manage ->Alerts->New Alert Ignore Action.

   OR

   If you have already received this alert In OME console, navigate to Manage -> Alerts

   Select “Alerts Logs -> All Alerts” in the left pane.

   Right click on the unknown alert and chose “Ignore -> Ignore on All Devices”.

You can download MIBs from the VMWare website for the latest ESXi version: communities.vmware.com/.../VMware-esx-mibs-1.0.1-368563.zip

As per ESXi user guide, you can filter out SNMP alerts on ESXi systems following these steps:

Configure the SNMP Agent to Filter Traps

You can configure the ESXi embedded SNMP agent to filter out traps if you don't want your SNMP

management software to receive those traps.

Prerequisites

SNMP configuration for ESXi requires the vSphere Command-Line Interface. See Getting Started with vSphere

Command-Line Interfaces.

Procedure

1 From the vSphere CLI,

vicfg-snmp.pl --server hostname --username username --password password -n oid_list

oid_list is a list of OIDs for the traps to filter, separated by commas. This list replaces any OIDs that were previously specificed using this command.

For example, to filter out coldStart (OID 1.3.6.1.4.1.6876.4.1.1.0) and warmStart (OID

1.3.6.1.4.1.6876.4.1.1.1) traps, type

vicfg-snmp.pl --server hostname --username username --password password -n

1.3.6.1.4.1.6876.4.1.1.0,1.3.6.1.4.1.6876.4.1.1.1 .

2 (Optional) If the SNMP agent is not enabled, enable it by typing

vicfg-snmp.pl --server hostname --username username --password password --enable.

The traps identified by the specified OIDs are filtered out of the output of the SNMP agent, and are not sent to SNMP management software.

What to do next

To clear all trap filters,

typevicfg-snmp.pl --server hostname --username username --password password -n reset.