We are trying to monitor vCenter for alerts generated by our ESXi hosts. When they generate an alert condition we can have vCenter send a notification trap. The plan is to then alert on those traps with System Center. The problem we are running into is we cant add the vCenter server as an SNMP device. It keeps getting filtered out. This apparently is by design http://technet.microsoft.com/en-us/library/hh212935.aspx Note Windows computers running SNMP are filtered out of discovery results if: The device type is Host and the vendor is Microsoft The sysDescription field contains Microsoft The sysOid starts with .1.3.6.1.4.1.311.1.1.3.1 The sysOid contains 1.3.6.1.4.1.199.1.1.3.11 Can anyone think of anyway around this. Our current solution is to build out a Linux SNMP device to accept the trap and then forward it on, but it seems like there should be a better way.

Direct monitoring of ESX hosts by SCOM is not so practical. The 'approved' method is to deploy v.Center and SCVMM, connect SCVMM to v.Center, then connect SCVMM to SCOM. This provides good visibility of ESX host health in SCOM such as CPU, memory, disk, network, and free space in ESX storage. Of course there are third party ESX management packs available, a popular one is from Veeam: http://www.veeam.com/vmware-microsoft-esx-monitoring.html? I found this blog post on the topic, it might help you: http://www.system-center.me/opsmgr/monitor-vmware-esx-with-scom-vcenter-for-free/John Joyner MVP-SC-CDM

Direct monitoring of ESX hosts by SCOM is not so practical. The 'approved' method is to deploy v.Center and SCVMM, connect SCVMM to v.Center, then connect SCVMM to SCOM. This provides good visibility of ESX host health in SCOM such as CPU, memory, disk, network, and free space in ESX storage. Of course there are third party ESX management packs available, a popular one is from Veeam: http://www.veeam.com/vmware-microsoft-esx-monitoring.html? I found this blog post on the topic, it might help you: http://www.system-center.me/opsmgr/monitor-vmware-esx-with-scom-vcenter-for-free/John Joyner MVP-SC-CDM

"Direct monitoring of ESX hosts by SCOM is not so practical" You are correct, that is why we are monitoring vCenter. It already correlates all the warnings using its built in tools. We are in the process of deploying the tools you mentioned, but it will take several months to get done. The management pack for Veeam is over $25,000 so thats a non starter. I have also read the blog you mentioned. Our biggest problem is that you cant add a Windows server as an SNMP device.