I'd like to hear about your experiences running AFS over Fore Systems, Inc.
ATM hardware.
Our cell has three servers (Suns) on ethernet, and I'm trying to get two AFS
clients (also Suns) working exclusively through their ATM interfaces. The
clients are using Fore's sbus cards, attached to an ASX-200 switch. The
ASX-200 connects to an LAX-20, which connects to ethernet.
When the client workstations boot up, everything seems fine at first. I can
log in on either one of the client machines' console, authenticate
successfully, and access files in afs with no trouble--for about 30 to 60
seconds.
After that I get the all too familiar console message about "Lost contact with
server..." I get permission denied messages for whatever file I'm trying to
access. The last ls info is still in the local cache at this point. A quick
ps auxw | grep afsd reveals that afsd has died. Now I've lost it all.
Restarting afsd fails. The kernel module, which was loaded with dkload at boot
time, has apparently "gone south".
I'm still able to ping other hosts with no packet loss and normal round
trip times, telnet works, NFS seems to work. Only AFS seems to exhibit this
problem.
I would be grateful for any advice, pointers, anecdotes, stories, or help you
may have to offer. Obviously, if I can't get this worked out, I can't put my
AFS servers on ATM (which seems to be the eventual goal).
-----------------------------------
Brad Robertson <[EMAIL PROTECTED]>
