This MP contains a Resource Pool dedicated for these devices. You can look at the rule configurations to better understand this method, to start creating your own rules. A rule that will filter a specific payload in the trap, such as data in a specific Varbind. A rule to alert on ANY trap sent to the device that comes from a specific OID.ģ. A rule to alert on ANY trap sent from the device.Ģ. I have included three different rule examples:ġ. The Base64 Community string is described here: I have included the one for “public” in my example.Īnd let you generate alerts when traps are sent to the SCOM Management server that hosts these objects: We require a DeviceName, IP Address, and Community String (base64) at a minimum: You may change these as you wish, but you have to change the discovery script as well if you do. For my example I include the device name, IP, Base64 SNMP Community String, a description, and the Owner. My example CSV is very basic – you can add or remove fields you want to discover. You can override this for Interval, SyncTime, Timeout, and the CSV path you want to discover from: Then – there is a discovery that discovers against the CSV file and creates our instances: They just create the pool and load the relationship so the pool will host our devices. There is a datasource for the Resource Pool, and a Discovery for that as well, but those aren’t important here. Our class definitions look like the following: Therefore – even if you don’t need this functionality – this will be a very good MP example, of discovering objects from a CSV, and having those objects hosted by a resource pool and load balanced by resource pool members! Rules, to alert on all traps, specific traps from a specific OID, and specific traps where a SNMP varbind contains specific data
A discovery, which is a PowerShell script to discover our network devices.Ĥ. A Class that will define our SNMP network device and any properties.ģ. A new Resource Pool, that will host our network devices and load balance them.Ģ. The idea is to create a management pack with the following:ġ.
This post will be based on the work of Tatiana Golovina here: along with feedback from Michael Bullwinkle. This article will demonstrate how we can create a new class for our network devices, discover them from a simple CSV text file, and then monitor them for SNMP traps. If we have challenges getting a network device to discover in SCOM, we can’t generate an alert or collect the trap. This can be a big problem for customers, as they often have network devices that only sent traps, but are not query-able via SNMP GET requests. One of the challenges I have heard many times with SCOM – is that we must discover a network device, in order to monitor or receive SNMP traps from that device. I have written on SNMP monitoring in SCOM a few times:
0 kommentar(er)
