Okay, just if you are testing connectivity from HostA to HostB it has to
route *through* HostA and as HostA isn't a router, using the route tag only
tests from Hobbit to HostB or HostA, not from Host to Host.
I don't know enough about bbnet to comment on that aspect though. Script
will work (shell, perl, ...) if all else fails. You could use bb (through
client) to send results or bbsend.pl.
'Nobody goes there anymore. It's too crowded.' --Yogi Berra
On Thu, Aug 28, 2008 at 10:01 AM, michael nemeth <user-609d3fab5b2d@xymon.invalid>wrote:
Ive unix and linux system but script is a script.
Is this because it is a cluster or something?
No I think it because the network team makes changes but tell no one AND
the attitude "well it works for Windoze boxes" .
But it may and I believe can be due too other network problems, like too
much traffic.
Probable what I'll is a script . Now ,I don't think that a route actually
need to be network hardware; at least I've routed though servers before in
one card out another.
I was thinking of something like hobbit server
xxx.xxx.xxx Hostb # route:router1,Hosta route2,router3
Or setting up a bbnet on Hosta
Or as you say a script.
Looking to see If others have handed this problem through hobbit before I
did something or if some would say ; "Yes use route or bbnet would be better
choice or something else ."!
Geoff Hallford wrote:
So, you need to know when HostA can't ping HostB? Is this because it is a
cluster or something?
I would suggest a simple vbscript on HostA and HostB that pings the other
and puts the results (green or red) in a file. Then just pass that to BBWin
or use bbsend.exe as an alternative to Hobbit. You could call the new status
column something like 'cluster' or 'interconnect' ... whatever.
I don't think that route or anything will work for this, as these are not
routers are they?
On Thu, Aug 28, 2008 at 6:02 AM, michael nemeth <user-609d3fab5b2d@xymon.invalid>wrote:
No one has any input? Going to start working this issue myself soon.
michael nemeth wrote:
The Network problem IS exactly what I want to detect! Ward, Martin wrote:
Michael,
What exactly are you after? If the problem is that HostA cannot ping
HostB all the time then this points to a networking issue: Firewall?
Dodgy network cable? Too much traffic and too short a time-out?
If your Hobbit server can ping both hosts then it's doing its job and
there are no problems, with Hobbit at least...
|\/|artin
-----Original Message-----
From: michael nemeth [mailto:user-609d3fab5b2d@xymon.invalid] Sent: 14 August
2008 16:40
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Secondary ping?
Heres the problem my hobbit server can ping HostA and HostB but
SOMETIMES HostA and HostB
cannot ping each other . Besides a client side script, anyone think of
a way to do this and take advantage of
hobbit functionality. BBNET? route ? something else?
*************************************************************************************
The message is intended for the named addressee only and may not be
disclosed to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and
may also be subject to legal privilege. If you are not the named addressee
and/or have received this message in error, please advise us by e-mailing
user-61c7f445d564@xymon.invalid and delete the message and any attachments without
retaining any copies.
Internet communications are not secure and COLT does not accept
responsibility for this message, its contents nor responsibility for any
viruses.
No contracts can be created or varied on behalf of COLT
Telecommunications, its subsidiaries or affiliates ("COLT") and any other
party by email Communications unless expressly agreed in writing with such
other party. Please note that incoming emails will be automatically scanned
to eliminate potential viruses and unsolicited promotional emails. For more
information refer to www.colt.net or contact us on +44(0)20 7390 3900.