"Pete Fiorese 532-4139" <[EMAIL PROTECTED]> writes:
>>Subject: File Servers with Multiple Network Interfaces
>>
>>*** Reply to note of 03/04/93 14:23
>>
>>"Doug Engert" <[EMAIL PROTECTED]> writes:
>>>> ...
>>>> We have two file servers which have multiple network interfaces,
>>>> and thus have multiple IP addresses. AFS referees to the servers
>>>> by name, but appears to store one of the IP numbers in the VLDB
>>>> based on a DNS lookup.
>>>> ...
>>
>> Has there been any follow up on this that I've missed. We're in a
>>situation which causes this to directly affect us. We're about to bring
>>3 fileservers on-line with multiple network interfaces (two building rings).
>>Should all of the volumes be defined on the ring A interface of all
>>fileservers, or should volumes be defined on the same interface as the
>>client? Does it matter? How does it impact performance? Is there an impact
>>to the VLDB for backup? lookup? Thanks for any information...
>>
>>Pete Fiorese
A few weeks ago, I asked if others had seen any problems with AFS
servers which had multiple network interfaces. With some help
>From our AFS rep, we got around the problems. The main problem
comes from the fact that AFS stores the IP number of the server
which has a volume, in the VLDB. Depending on how this volume was
created, it may store anyone of the IP numbers of the server. We
have two ethernets and an FDDI on one of our servers. I am not
sure how we did it, but we did a vos create and got the FDDI
address stored in the VLDB. (Gethostbyname returns a list of
address, and DNS may change the order depending on the location
of the client, server and nameserver.) (These are based on
observation, I don't have source.)
If you then do a command like "backupsys -server ajax" the
backupsys command converts this to an IP number, then searches
the VLDB for volumes which match this IP number. If some volume
was created on ajax, but one of the other addresses was put in
the VLDB, then it will not be selected for backup!!!!
You might want to look at your own situation to see if all your
volumes are being backedup!
We got around this problem, by not using the -server option, on
any of the commands which select volumes for processing based on
their server's IP address. These include backup and backupsys. We
also do a "vos syncvldb" on every server from time to time to get
the VLDB back in sync. just in case.
Transarc still has some work to do in this area. We are living
with the problem. If you have specific problems, contact you AFS
rep.
Douglas E. Engert
Systems Programming
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(708) 252-5444
Internet: [EMAIL PROTECTED]
