SNMP Traps and suspect OIDs

[iarecuezero]

Greetings,

I'm having an issue getting traps with my NMS from vCenter. First, a little information:

1) vSphere Client: 5.0.0 build: 455964

2) VMware vCenter server: 5.0.0 build 455964

3) ESXi version: HP-ESXi-5.0.0

4) MIB package version: VMware-esx-mibs-1.0.1-368563

I've installed the MIBS per the readme packaged. My NMS is picking up the V2 traps however, it appears that it is receiving an incorrect oid.

Example - vmPoweredOff:

========

Current v2 Trap               : .1.3.6.1.4.1.6876.4.1.0.2

Obsolete v2 Trap            : .1.3.6.1.4.1.6876.0.2

Trap sent by ESX/vCenter (v1): .1.3.6.1.4.1.6876.4.1.

Has anyone run into this issue before? I suspect an issue with vCenter.I don't handle the vmware side of this. Does vCenter need Mibs installed as well? If so which ones and where?

Additionally, the traps configured in the MIBS are all v2 traps but the NMS are picking up are all v1.

Any information would be greatly appreciated.

Thanks,

Chris

[iarecuezero]

Bump.

Noone has seen this issue before?

[iarecuezero]

Does anyone know exactly how the oids are genertated by vcenter and the esxi hosts? I'm still picking up snmp but I belive the both the agent and the manager would need a copy of the mibs. I see that there is a MIBS folder on the vcenter server located at: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\MIBS. The files present in that folder are:

1) VMWARE-PRODUCTS-MIB.mib

2) VMWARE-ROOT-MIB.mib

3) VMWARE-TC-MIB.mib

4) VMWARE-VC-EVENT-MIB.mib

I could not find any mibs on the esxi hosts. Are these somehow embedded in the software? I have not yet tried other trap software to rule out the current snmp manager.

Any help would be greatly appreciated.

Thanks,

Chris