Multi-Host Ping MP 3.0

Comments
Social
Related

Comments (17) - Comment RSS

barce59 wrote: on Mar 09, 2010 01:57 AM

Hi Everyone,

First, i'd like to thank you guys for creating this MP :).

My question is, can i configure to have all the monitored IPs into a Group? How? I tried to create a group for these monitors but it seems that it cant be considered (as this is an IP and not device). I want to consolidate all monitored IPs into a single group then assign a specific email subscription for this so that other recipients will not be disturbed incase an IP of such will go down.

Is this possible to do?

Thanks,

Pabs

Permalink | Report Abuse | Edit | Delete

JankoZ wrote: on Apr 07, 2010 03:02 AM

hi, thanks for this.

When I import MP using Opeations Console there are some monitors and rules missing ?!?!

I can see all monitors, rules and tasks in authoring console but not in Operations Console when importing.

??

Permalink | Report Abuse | Edit | Delete

BrettChevy wrote: on Aug 24, 2010 10:12 AM

TWIMC,

I'd also like to thank the authors for putting this together.

Since I haven't seen any responses to posts for over 4 months I don't know if this thread is being monitored any longer. I have a comment in case it is.

To Shailesh's point it would be nice to be able to point this at a text file. I understand that makes it complex because of varying folder locations. The registry key idea makes admins a little nervous and has its limitations.

Shailesh - If you spread the workload over multiple watcher nodes then both of your issues should be resolved. See the pdf doc in the MP for this.

All little criticism aside, this is an excellent solution allowing me to further push IPMon out the door. I can't touch all servers with agents or even agentless monitoring so this is a great workaround.

Permalink | Report Abuse | Edit | Delete

tgoble wrote: on Aug 27, 2010 10:45 AM

Hello everyone!

Also hope folks are still monitoring these posts.

I'm very interested in this MP due to performance Rule overrides available over OpsLogix PING MP!

However, I am curios for an answer to the number of ping targets that can be entered into a single WatcherNode. We have 3000+ network (non Windows) devices we want to monitor for PING response times.

We are thinking of creating custom console tasks (scripts) to perform diagnostic and service stopping actions on Windows PCs when we detect extremely long ms response times over DSL networks when in Dial backup.

While OpsLogix PING MP is nice, it seems more limited and challenging to accomplish monitoring multiple levels of ms response times and thresholds.

We are thinking of either using multiple SCOM monitors or a 3 state monitor for ms response times to trigger console tasks/alerts with custom scripts firing against certain SCOM Agents (Agent IP derived via custom script from ping targets) where the ping target is in Dial backup state. We may simply have to target the actual Windows Computer IP/name with our custom scripts vs. actual SCOM Agents since the tasks will be console based.

None the less or the scripting concerns I may run into, my primary interest is how many Ping Targets can one Ping Watcher support in the registry? I see one post here stating 95 Ping Targets max due to registry limitations. Any update or confirm limit per Ping Watcher?

Any help/comments are truly appreciated.

Thanks,

Terry

Permalink | Report Abuse | Edit | Delete

atiwari wrote: on Sep 08, 2010 02:05 AM

Hi,

I have used this MP in the past worked like a charm. But with our new R2 setup seems like I cannot import the MP. It comes up with the following error:

"SystemCenterForum.org Multi-Host Ping V3 could not be imported.

If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail.

The requested management pack was invalid. See inner exception for details.

Parameter name: managementPack"

The setup is following:

OS: Win 2k8 R2

Ops Mgr R2

Please help?

Regards

Ash

Permalink | Report Abuse | Edit | Delete

Dominique wrote: on Apr 20, 2011 02:07 PM

Hello,

Any limitations in the number of machines to be in the Ping List?When I had between 10 and 20 everything works fine but with 500+ now I could not get it work ... I will review the list but is there any limit?

Thanks,
Dom

Permalink | Report Abuse | Edit | Delete

alexts wrote: on Apr 25, 2011 01:36 PM

thanks!

Permalink | Report Abuse | Edit | Delete

SIDERMAN wrote: on May 22, 2011 06:00 PM

List of Ping Targets empty!!!((

1.Import MP Multi-host ping 3.0

2. Copy reg file to watcher role agent

3. Edit reg file

4. Import reg file to registry

5. Enable proxy on watcher node

6. Restart System Management service on warcher agent

7. Refresh list of tagets on SCOM console

Empty:-(

???

Permalink | Report Abuse | Edit | Delete

Ron wrote: on Oct 26, 2011 05:01 PM

What are the chances of this working in SCOM 2012?

Permalink | Report Abuse | Edit | Delete

Pete Zerger wrote: on Oct 26, 2011 07:19 PM

Should work fine with no changes. See also the Multi-host Ping configuration builder - http://oclashing.wordpress.com/2010/12/18/multi-host-ping-mp-configuration-builder/

Permalink | Report Abuse | Edit | Delete

Add your Comment

Who Viewed

Who Reviewed