Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

VMware traps not recognized

Description

The event definitions in VMWare.events.xml do not always (ever?) match actual traps sent by VMware products.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Attachments

5

Lucidchart Diagrams

Activity

Show:

Seth Leger January 9, 2012 at 3:35 PM

I've added these VMware MIB conversions to the eventconf. Marking as fixed.

commits:
ce6a3daeb362b2d27ffe6407a800c17992ce9d4b
437a167566786c4cb712a9310176437acccdbe3d
222973192c0acc0b220d6624236e3e940f4ca124

Steve Hillier January 6, 2012 at 9:39 AM

I just finished deploying the attached configurations on 1.9.93.

For the most part, they work, however some extra steps are needed to actually enable SNMP on ESXi 4.1. I used vMA to enable the SNMP agents on the ESXi hypervisors.

It seems the amount of data exposed by the SNMP agent is indeed much less in this release of ESXi. For that reason, some of the data cannot be collected. I'm sure older hosts with the full SC will expose this data.

+1 for 1.10 release.

Seth Leger August 25, 2011 at 2:07 PM

This seems like it needs to be added to the 1.10 release candidate branch.

bofh.jr June 10, 2011 at 12:21 PM

alarm-data corrections

bofh.jr June 8, 2011 at 6:40 PM

I created an event file for each mib source file.

The file VMWare.obsolete.events.xml contains the same events as in the actual /etc/events/VMWare.events.xml.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 21, 2008 at 1:51 PM
Updated January 27, 2017 at 4:25 PM
Resolved January 9, 2012 at 3:35 PM