Client B has to be on the same network as the production server, or it's getting through a firewall/router somewhere. This is what I imagine it has to look like:
Either:
Hobbit1 ---- Router1 ---- ClientB --- Router2 --- Prod Server
-OR-
Hobbit1 ---- Router1 ---- ClientB \---- Prod Server
In either scenario, you can either get ClientB to report to Hobbit the Status (port 1984, it's well documented, etc), or you can adjust your routers to forward the packets back and forth.
Your choice, really. I'd prefer to go the direct route and just modify the network rules to allow ICMP from Hobbit1 to the Prod Server.
Tod Hansmann Network Engineer
-----Original Message----- From: Jeff Newman [mailto:jeffnewman75 at gmail.com] Sent: Wednesday, May 16, 2007 10:52 AM To: hobbit at hswn.dk 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
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk