access <-> sdsc ip multicast

[Harry Ammons]

Jay has setup a beacon running on a seperate pc on the same subnet as our AG for
now.
ASAP we will implement a continuous running beacon from sdsc AG.

"Borchers, Robert R" wrote:

> I would hope Jay D at SDSC would have what you need. Bob
>
> -========================================================
> Robert R. Borchers, Director       ACIR Division
> National Science Foundation        4201 Wilson Boulevard
> borchers at NSF.GOV                   Arlington, VA 22230
> Phone: (703) 306-1970              FAX: (703) 306-0632
> Cellular: (703) 627-3749           www.cise.nsf.gov/acir
> -========================================================
>
> -----Original Message-----
> From: Bill Nickless [mailto:nickless at mcs.anl.gov]
> Sent: Friday, July 28, 2000 1:54 PM
> To: Borchers, Robert R
> Cc: 'Bill Nickless'; Nancy Wilkins-Diehr; Tom Coffin; Borchers, Robert
> R; Harry Ammons; Jay Dombrowski; sheddon at SDSC.EDU;
> jsheehan at ncsa.uiuc.edu; dgatchell at nsf.gov; ag-tech at mcs.anl.gov; Zaid
> Albanna
> Subject: RE: access <-> sdsc ip multicast
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> At 01:44 PM 7/28/2000 -0400, Borchers, Robert R wrote:
> >Bill, SDSC can no longer see or hear NSF but they can see and hear ACCESS.
> >They also cannot see my Beacon and their column and row on Beacon Viewer is
> >all reds and yellows. Bob
>
> Bob Olson suggested that the reds/yellows have to do with the possibility
> that Jay Dombrowski's PC (where the SDSC beacon is currently running) may
> be overloaded.  This would cause the problems we are seeing.
>
> I was under the impression that SDSC was going to find someone with
> administrative privileges on their Access Grid node machines.  This would
> let us look at the correct network and the correct machine.  Us network
> types are a little stuck at the moment until that can happen at SDSC.
>
> I would be happy to get the beacon running at SDSC if someone would give me
> access to one of the Linux machines that makes up the cluster.  We
> generally like to see the IP multicast beacons running at a site all the
> time.  We use this to look for problems and solve them before high-pressure
> situations like this.
>
> My SSH public identity is at http://www-fp.mcs.anl.gov/~nickless/sshkey.txt
> for anyone who might wish to give me access to the SDSC Linux
> machines.  Simply add the contents to ~root/.ssh/authorized_keys and I'll
> log right in and fix the beacon up.
> ===
> Bill Nickless    http://www.mcs.anl.gov/people/nickless      +1 630 252 7390
> PGP:0E 0F 16 80 C5 B1 69 52 E1 44 1A A5 0E 1B 74 F7     nickless at mcs.anl.gov
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
>
> iQCVAwUBOYHImawgm7ipJDXBAQHNtgP7Bxhxv/hOZmTu6nPU9HggTyptfC2ZN9KD
> nT2eX3WPjkYCiaeO8d+/wNOb35aFMZ//1AaU/+dskYwrrqXBOqS/LQxtiuPx0MFg
> CNxviU12HY9V2flIDjV1pZsJespwtkIQMFBrwViAqH38u85DoF3lFN4Q8AnBvCnx
> yfEQIL/yHJ8=
> =NqMn
> -----END PGP SIGNATURE-----