BBNET is ... well, a BB'ism. Hobbit completely ignores it, as well as
the BBPAGER and BBDISPLAY entries in bb-hosts.
But you're right - setting up server B to run network tests is the way
to go. See my other response.
Regards,
Henrik
On Wed, May 16, 2007 at 01:15:45PM -0400, Galen Johnson wrote:
Would making that a BBNET server do it?
=G=
-----Original Message-----
From: Kern, Thomas [mailto:user-f1ebafb19faf@xymon.invalid] Sent: Wednesday, May 16, 2007 1:04 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Ping question
I don't know if the hobbit client itself can do that, but I think it would be easy enough to write a custom test script to be run at Client-B and report the status of Client-B/ProdServer connectivity to the real hobbit server via the old STATUS message functionality.
/Thomas Kern
/XXX-XXX-XXXX
-----Original Message-----
From: Jeff Newman [mailto:user-e96740e73ca8@xymon.invalid]
Sent: Wednesday, May 16, 2007 12:52 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Ping question
Hi,
I have 1 hobbit server that successfully monitors all of my servers.
(with all of the problems everyone mails about, just had to say that > up front heh)
But yes, I do have a question :-)
Hobbit server A monitors client B. Client B has a a private connection > to a network that nobody else can be on except for it. Client B talks > to some production server over that network. Today, that production > server went down. Now I have been asked to do the following:
I need to be able to ping monitor the production server. I can ping > the production server from Client B. Hobbit server A can ping client > B, but not the prod. server (as only client B has that ability)
So in other words "Hobbit - I want you to ping prod server through > client B" - the other way would be "Client B - I want you to ping > prod. server and report the status to Hobbit"
Help! :-)
Thanks,
Jeff
--
Henrik Storner