October 6, 2014
Posted by on
Truesec company sends useful newsletters.
One of the latest (Sept 25th, 2014) contains an advice related to SNMP monitoring with SCOM (by Kare):
The right way of Network Monitoring in SCOM 2012R2
Monitoring Network devices in SCOM 2012R2 is plain simple but unfortunately have a kind of bad reputation. Let me try to clear things out.
You do NOT have to install any SNMP features from Microsoft nor start any SNMP trap service.
This is a common misunderstanding, and unfortunately even in a lot of blogs and books around state you should install SNMP = Don’t. Please just create a discovery and then your Microsoft Monitoring Service (Healthservice.exe) begin listening and using port UDP: 161, 162 (bi-dir) and ICMP as well. This work without installing anything else than SCOM 2012 R2.
Monitoring Netapp, HP and Dell with Windows SNMP
In some situations of HW monitoring the Monitor agent/Proxy only works with Microsoft Windows SNMP, then you need to install Microsoft SNMP on the box that communicate with Netapp/HP/Dell. In this case, either dedicate a Management Server to a Resource Pool and let this Pool take care of the HW SNMP or dedicate a “Machine” to act as a proxy. Otherwise, you end up having two SNMP/ICMP interfaces receiving information not exactly knowing who is taking care of what.
So two things to remember – Do not install any SNMP and if monitoring HW that needs Windows SNMP – keep it away from the Management Server or create a dedicated Resource Pool.