Running Dell IT Assistant to receive the traps, FYI. Previously was running ESX 3.0.2 / VC 2.0.2 with everything working.

-Traps sent by VirtualCenter still work fine, but there is a seemingly undocumented OID prefix change.
Old: .1.3.6.1.4.1.6876.50 (etc)
New: .1.3.6.1.4.1.6876.4.3 (etc)
This change is also not reflected in the MIBs that ship with VirtualCenter (they appear the same and reference the .50 prefix above). I manually entered the new definitions in my SNMP receiver to resolve.

-SNMP on ESX hosts has changed a bit, and at the moment isn't working in my scenario.
As per the documentation, there is now an add'l SNMP engine that can be enabled via the RemoteCLI, designed for 3i use (although also configurable on 3.5 hosts).

For 3.5 hosts, the documentation indicates you can choose to use the Net-SNMP agent that ships with the service console as per usual. Since I use the supported Dell OMI agent (Linux/ESX version) on my 3.5 hosts, I opted to stick with that agent - and have verified all steps were followed, and configurations did not change during the upgrade.

Current behavior is that no traps whatsoever are sent for 'VMWare' events. Note that traps sent by the Dell agent are delivered normally, which helps indicate correct Linux-level SNMP configuration is in place. Again I have verified the VMWare specific traps are not disabled and configs match both the documentation, and my other (working) 3.0.2 host.

So, I'm not sure if this is an issue with the interaction between Dell's agent and ESX, or just a bug in ESX 3.5 when not using the 'new' SNMP agent, or something I haven't thought of. At this point, I have not tested the Remote CLI configured option, since it wants to use the same default port as the Net-SNMP agent and cannot bind. I could change the default port, but prefer to only run one SNMP agent and avoid further firewall configuration.

Anyone noticed the same thing? Ideas? Am I the only one using the ESX specific VMWare traps?

Cheers,
Mike