I'm fiddling with getting openafs-1.3 to play nicely, with various grades of success.
For various reasons we have an AFS server that also sits on an internal network, and thus always announces the internal address to the world.
However, openafs 1.3.76 (which is the one I'm pounding on) seems to flag the whole server as down when it can't reach an interface:
# ./fs checkservers
These servers unavailable due to network or server problems: chosan.hpc2n.umu.se.
Console output:
afs: Lost contact with file server 130.239.45.228 in cell hpc2n.umu.se (multi-homed address; other same-host interfaces maybe up)
afs: Lost contact with file server 172.20.1.8 in cell hpc2n.umu.se (all multi-homed ip addresses down for the server)
Make my test machine able to reach the internal interface of the AFS server:
# route add 172.20.1.8 130.239.45.228
# ./fs checkservers
All servers are running.
afs: file server 130.239.45.228 in cell hpc2n.umu.se is back up (multi-homed address; other same-host interfaces may still be down)
afs: file server 172.20.1.8 in cell hpc2n.umu.se is back up (multi-homed address; other same-host interfaces may still be down)
I'm not on the list, so please CC me eventual replies.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [EMAIL PROTECTED]
---------------------------------------------------------------------------
Ultimate office automation: Networked coffee machine.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
