I know I've played around with multihomed dbservers before, but it was long
ago, a different use case, on a different platform, and I had problems
then! :-\
[edit] I just checked rt.central.org and found my ticket. No update in 9
years. <https://rt.central.org/rt/Ticket/Display.html?id=15640>
Anyway, I don't think I'm mis-reading the Admin Guide (but I concede that
what it says may be wrong!)
In any event, the QuickStartUnix guide also says they can be multihomed:
"It is best to maintain a one-to-one mapping between hostnames and IP
addresses on a multihomed database server machine..."
But I know all of the openafs docs are often out of date or downright
wrong, which is why I asked on the list.
As far as you know, is the "it doesn't work" definitive?
Cheers,
Stephen
On Tue, 24 Sep 2013, Jeffrey Altman wrote:
Stephen,
I believe you are misreading the Admin Guide. It indicates that File
Servers can be multi-homed and that they self-register. If you have DB
servers that are multi-homed you need to pick a single network interface
for them to use
If given the choice of interface bonding and multi-homed, choose bonding.
Jeffrey Altman
On 9/24/2013 6:01 PM, [email protected] wrote:
I have two general questions about multihomed AFS servers to pose to list.
- Is there any obvious reason to choose multihoming of a fileserver
rather than link aggregation, assuming both are supported in a given
environment?
- The Admin Guide on docs.openafs.org indicates that multihomed DB
servers work.[1]
Is this true in an environment where both IPs are on the same (campus)
network and they may share the same default route?
Specifically, I'm curious about linux dbservers; clients may contact the
server via IP A but get an answer from IP B, if it is the default
interface. Will the clients care? What if the IP replying isn't in the
client's CellServDB (or DNS) at all? Does the answer change depending on
client version?
[1] <http://docs.openafs.org/AdminGuide/index.html#HDRWQ138.html>
Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info