RE: {bb} False ping alarms in V1.13a

[Mark Borghardt <Mark.Borghardt@worldwidefiber.com>]

I am having this problem as well.  Like Steffen, it only seems to be on 1 
machine.  In my case it is an NT box.  My BBDISPLAY is an Ultra5.  vmstat 
doesn't show any signs of stress.

I tried "stressing" the ultra 5 by running crack and it pretty much pins 
the cpu at 100%.  It didn't seem to affect the "false" pings.  During this 
time I also ran ping -s <yellow host> 64 10000.  I lost a total of 11 
packets out of 10000.  Were those 11 the ones that caused the yellow - 
maybe but I doubt it.

I wonder what the problem is?

--
Mark Borghardt
Micronix Computer Consulting

-----Original Message-----
From:	Steffen.Scheibler [SMTP:Steffen.Scheibler@sozvers.at]
Sent:	Thursday, February 24, 2000 11:10 PM
To:	bb@bb4.com; MBorghardt.WFI-VAN_BC_PO.WFI-VAN_BC_DOM@worldwidefiber.com
Subject:	Re: {bb} False ping alarms in V1.13a




Yes I have seen this behaviour too.
I never managed to find out where it came from though and when I moved my
test version of BB to a faster machine it went away - it could be a
performance thing, it could be anything really.

It only happened on one host though. The BBDISPLAY doing the ping was an
x86 P200 running Redhat 5.2 (Apollo) trying to ping a Sun Solaris 2.6
machine. The load avg on the BBDISPLAY was 86, on the Solaris it was 3.

I could find no other connection. Maybe a heavily stressed BBDISPLAY causes
this?





John Lengeling <johnl@microware.com>@bb4.com> on 2000/02/24 20:49:14

Please respond to bb <bb@bb4.com>

Sent by:  owner-bb <owner-bb@bb4.com>


To:   bb <bb@bb4.com>
cc:

Subject:  {bb} False ping alarms in V1.13a


I am getting false ping yellow alerts from one of my machines.  It is an
Axis cdrom server.  I get a yellow alert saying that the ping succeeded
on the second try.  What is weird is that every other pass through
bb-network the alert alternates between green and yellow.  Here is the
connection history from the machine:

DATE                     STATUS SECONDS
Thu Feb 24 13:19:55 2000 GREEN  749
Thu Feb 24 13:08:01 2000 YELLOW 714
Thu Feb 24 12:56:22 2000 GREEN  699
Thu Feb 24 12:44:20 2000 YELLOW 722
Thu Feb 24 12:21:12 2000 GREEN  1388
..
..

BTW: What does the seconds indicate?  Seconds between event change?

I pinged the maching myself for long periods and never lost a packet.  I
modified bb-network.sh to save the tmp/BBPING output so I could look for
a failed attempt. I never found a failed ping attempt for this
machine.   I had the same behavior under v1.08.

Has anyone else seen this type of problem?

johnl
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.



--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.