Skip navigation
1893 Views 2 Replies Latest reply: Aug 16, 2012 7:15 PM by James Stewart RSS
James Stewart Rank: Green Belt 91 posts since
Dec 1, 2010
Currently Being Moderated

Aug 16, 2012 2:54 AM

VMWare ESX Trap Vars not Mapping Correctly

Hello all,

 

I've got the VMWare ESX MIBS loaded and all seems ok when I browse them in Zenoss. Here are the traps:

 

vpxdAlarm1.3.6.1.4.1.6876.4.3.0.201notification
vpxdAlarmInfo1.3.6.1.4.1.6876.4.3.0.203notification
vpxdDiagnostic1.3.6.1.4.1.6876.4.3.0.202notification

 

and here are some OID mappings:

 

vmwVpxdHostName1.3.6.1.4.1.6876.4.3.302scalar
vmwVpxdNewStatus1.3.6.1.4.1.6876.4.3.305scalar
vmwVpxdObjValue1.3.6.1.4.1.6876.4.3.306scalar
vmwVpxdOldStatus1.3.6.1.4.1.6876.4.3.304scalar
vmwVpxdTargetObj1.3.6.1.4.1.6876.4.3.307scalar
vmwVpxdTargetObjType1.3.6.1.4.1.6876.4.3.308scalar
vmwVpxdTrapType1.3.6.1.4.1.6876.4.3.301scalar
vmwVpxdVMName1.3.6.1.4.1.6876.4.3.303scalar

 

However, when I receive traps from my ESX(4) host, the resulting event has a message field "snmp trap enterprises.6876.4.3.203" (note the missing '0' which is causing the trap not to be mapped).

 

Furthermore, the trap vars have the opposite problem, e.g:

 

enterprises.6876.4.3.306.0Test Host Memory - Metric Usage = 70%
enterprises.6876.4.3.305.0Yellow

 

(notice the extra '0', causing the traps not to be mapped).

 

Does anyone know why this might be? I've tried it on 3.1.x and 3.2.1 and the result is the same.

 

Thanks,

 

James

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points