@Saiyad Rahim well I'm all against running rules/monitors every few seconds, and as an exception I might agree to 1 min. Probably less of an issue in smaller environments than large ones
so you want pings against server with meaningful messages for each, but don't want to do a lot of work...
that's either a lot of rules, effort to setup a template (or install someone else) and deploy for each IP, or cheating...
what do I mean by cheating. Well you can dynamically name a rules alert message, many don't know this. so you could do it all in two rules, and no xml editing or extra tools/management packs
- setup a rule to run a PowerShell script (easiest if community PowerShell management pack is installed) . that script will for instance pull all instance of a group (scom calls, csv,etc), or use parameters to specify whats being pinged, ping it and drop the results, to an event log (easiest way) and make sure key elements are parametrized for extraction or the line is exactly what you want as an alert message
- setup an event log monitor to monitor the event log and use dynamic naming based on the parameters.
ie "Cannot Ping Server %1 from %2"
how does it work. well if you drop the parameter data from the event into the alert, you can reference that in the alert name, as a positional parameter.
ie for our above alert if they were Param [1] and param [2] and alert message:
Test Pings failing
Target Device : $Data/Params/Param[1]$
Source Device : $Data/Params/Param[2]$
or the whole event item... and alert name is %1
$Data[Default='']/EventDescription$
another cheat to make this a HA rule (ie not reliant on management server 'A') is create a management pack for this to be in, add a resource pool to it (will need to edit xml as otherwise you cant target a pool) set the pool to manual, add just the scom servers you want in there, then add the rules against the pool
if this seems all a bit dodgy, in a way it is.