We upgraded to AFS 3.4a on Monday on our Sun 4.1.3 servers and things
appear to be going OK. On Wednesday when we were doing full backups, the
network appeared to be very sluggish. This was tracked down to heave
traffic between two of our servers.
Two of our servers have both an FDDI and an ethernet connection. They
are on the same FDDI ring, and on the same ethernet cable. One of them
has the tape drive. In the past, the ethernet was not really used and
the backup data went over the FDDI. Since 3.4a it appears that some, if
not all, of the traffic for the backups is going over the ethernet
instead!
The fs getserverprefs -n on one of the servers shows:
146.139.254.1 10038
146.137.72.2 0
146.137.64.2 5007
146.137.72.12 0
146.137.64.12 20004
146.137.72.12 20004
i.e. the FDDI addresses (72) show 0. I assume that this is saying, don't use
them. Can I set them to non-zero values?
The ethernet address (146.137.64.xx) are less then the FDDI address
(146.137.72.xx) and so during the conversion, I assume the lower
146.137.64.xx address were chosen it be placed in the VLDB. I assume
this means that older pre-3.4 clients will be using the ethernet
access to the servers as well, as they should not know how to use
multihomed servers!
Can I do a "vos changeaddr" on the server to use the FDDI address as the
primary address? (I know the manual says it does not work, but the
"vos help changeaddr" still says how to do it.)
Is there a program to edit the /usr/afs/local/sysid file so as to
favor the FDDI addresses? (I appears to end with a count of addresses,
and the IP numbers.)
If we turn off the ethernet port, (or add another port) does the sysid
file get updated?
Since during the conversion, some process looked at all the interfaces
which were up at the time, it would have been nice if it also looked
at the metrics set on the interface and produced a list sorted by
performance.
(You might like to know that we have been running these AFS servers
with two interfaces for years, as both file servers and database
servers. This was carefully done, by not registering the ethernet
interface in DNS, and by using static host tables on the servers
themselves, so they would only know about a single interface on the
other servers. That appears to continue to work with 3.4a as well
despite all the warnings.)
Douglas E. Engert
Systems Programming
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(708) 252-5444
Internet: [EMAIL PROTECTED]
