149 lines
4.2 KiB
C++
149 lines
4.2 KiB
C++
|
|
/* $Id$
|
|
*
|
|
* L O S A L A M O S
|
|
* Los Alamos National Laboratory
|
|
* Los Alamos, New Mexico 87545
|
|
*
|
|
* Copyright, 1986, The Regents of the University of California.
|
|
*
|
|
* Author: Jeff Hill
|
|
*/
|
|
|
|
#include "iocinf.h"
|
|
|
|
tsFreeList < class bhe, 1024 > bhe::freeList;
|
|
|
|
/*
|
|
* update beacon period
|
|
*
|
|
* updates beacon period, and looks for beacon anomalies
|
|
*/
|
|
bool bhe::updateBeaconPeriod (osiTime programBeginTime)
|
|
{
|
|
double currentPeriod;
|
|
bool netChange = false;
|
|
osiTime current = osiTime::getCurrent ();
|
|
|
|
if ( this->timeStamp == osiTime () ) {
|
|
|
|
if ( this->piiu ) {
|
|
this->piiu->beaconAnomalyNotify ();
|
|
}
|
|
|
|
/*
|
|
* this is the 1st beacon seen - the beacon time stamp
|
|
* was not initialized during BHE create because
|
|
* a TCP/IP connection created the beacon.
|
|
* (nothing to do but set the beacon time stamp and return)
|
|
*/
|
|
this->timeStamp = current;
|
|
|
|
return netChange;
|
|
}
|
|
|
|
/*
|
|
* compute the beacon period (if we have seen at least two beacons)
|
|
*/
|
|
currentPeriod = current - this->timeStamp;
|
|
if ( this->averagePeriod < 0.0 ) {
|
|
ca_real totalRunningTime;
|
|
|
|
if ( this->piiu ) {
|
|
this->piiu->beaconAnomalyNotify ();
|
|
}
|
|
|
|
/*
|
|
* this is the 2nd beacon seen. We cant tell about
|
|
* the change in period at this point so we just
|
|
* initialize the average period and return.
|
|
*/
|
|
this->averagePeriod = currentPeriod;
|
|
|
|
/*
|
|
* ignore beacons seen for the first time shortly after
|
|
* init, but do not ignore beacons arriving with a short
|
|
* period because the IOC was rebooted soon after the
|
|
* client starts up.
|
|
*/
|
|
totalRunningTime = this->timeStamp - programBeginTime;
|
|
if ( currentPeriod <= totalRunningTime ) {
|
|
netChange = true;
|
|
}
|
|
}
|
|
else {
|
|
|
|
/*
|
|
* Is this an IOC seen because of a restored
|
|
* network segment?
|
|
*
|
|
* It may be possible to get false triggers here
|
|
* if the client is busy, but this does not cause
|
|
* problems because the echo response will tell us
|
|
* that the server is available
|
|
*/
|
|
if ( currentPeriod >= this->averagePeriod * 1.25 ) {
|
|
|
|
/*
|
|
* trigger on any missing beacon
|
|
* if connected to this server
|
|
*/
|
|
if ( this->piiu ) {
|
|
this->piiu->beaconAnomalyNotify ();
|
|
}
|
|
|
|
if ( currentPeriod >= this->averagePeriod * 3.25 ) {
|
|
/*
|
|
* trigger on any 3 contiguous missing beacons
|
|
* if not connected to this server
|
|
*/
|
|
netChange = true;
|
|
}
|
|
}
|
|
|
|
/*
|
|
* Is this an IOC seen because of an IOC reboot
|
|
* (beacon come at a higher rate just after the
|
|
* IOC reboots). Lower tolarance here because we
|
|
* dont have to worry about lost beacons.
|
|
*
|
|
* It may be possible to get false triggers here
|
|
* if the client is busy, but this does not cause
|
|
* problems because the echo response will tell us
|
|
* that the server is available
|
|
*/
|
|
else if ( currentPeriod <= this->averagePeriod * 0.80 ) {
|
|
if ( this->piiu ) {
|
|
this->piiu->beaconAnomalyNotify ();
|
|
}
|
|
netChange = true;
|
|
}
|
|
else {
|
|
/*
|
|
* update state of health for active virtual circuits
|
|
* if the beacon looks ok
|
|
*/
|
|
if ( this->piiu ) {
|
|
piiu->beaconArrivalNotify (); // reset connection activity watchdog
|
|
}
|
|
}
|
|
|
|
/*
|
|
* update a running average period
|
|
*/
|
|
this->averagePeriod = currentPeriod * 0.125 + this->averagePeriod * 0.875;
|
|
}
|
|
|
|
this->timeStamp = current;
|
|
|
|
return netChange;
|
|
}
|
|
|
|
void bhe::show ( unsigned level ) const
|
|
{
|
|
printf ( "CA beacon hash entry at %p with average period %f\n", this, this->averagePeriod );
|
|
if ( level > 0u ) {
|
|
printf ( "network IO pointer %p, client pointer %p\n", this->piiu, &this->cac );
|
|
}
|
|
}
|