[OpenAFS] Multihomed issues
Mon, 17 Jan 2011 22:13:14 -0500
On Mon, Jan 17, 2011 at 9:49 PM, Jaap Winius <firstname.lastname@example.org> wrote:
> Quoting Russ Allbery <email@example.com>:
>> Hm, I would have thought that would be enough. =A0If you have NetInfo, t=
>> should be all you need. =A0What directory did you create that file in?
>>> I did mean /etc/openafs/server/CellServDB, but, like the original
>>> server, this new (second) server is both a file server and a VLDB
>> I don't understand how anything would have ended up there without you
>> explicitly adding it. =A0Hm. =A0Oh, the openafs-client postinst will add=
>> the IP addresses for the VLDB servers you give. =A0Do you have the priva=
>> IP addresses in DNS? =A0If so, that's where it came from.
> Yes, each AFS server can see one of its private IP addresses in DNS. I
> suspected that might be influencing the matter.
>> Yeah, sorry, I should have warned like Darrick did. =A0vos remsite was t=
>> command you wanted. =A0vos delentry nukes the whole entry, so it nuked y=
>> root.cell VLDB entry.
> I'll try to remember that.
> In the mean time, things are not working as well as I thought. When I nex=
> attempted to use vos addsite to create some RO copies of the user and
> service volumes on the second server, it didn't work. I ran these command=
> on the second server and it ended up telling the system to use its privat=
> IP address (192.168.26.10) as the target.
> This is frustrating. These private IP addresses keep showing up in the VL=
> The first AFS server has had both NetInfo and NetRestrict files (in the d=
> mentioned above) for a while, yet I can't stop it's private IP addresses
> from being used either.
> If this is all because of DNS, what should I do? Both AFS servers also ru=
> Bind9 with split views -- internal and external. Each AFS server sees an
> internal view that includes its private IP address.
then some systems *need* the internal address to be able to reach
things. remember volume releases *also* require RPCs to go from the
master site to slaves. if a system
can only reach another by it's internal address, again, fix the real
problem. the real problem is not the internal address appearing. it's
that *only* the internal address is appearing.
did you read what i sent? you may, and probably do, need both
addresses to appear in the VLDB. the key is *both*. setting NetInfo
correctly will fix this.
> Perhaps I should simply associate each server's internal address with a
> different name. That way, the current names of the servers will only be
> associated with their public IP addresses -- both internally and external=
> If DNS is causing these problems, I think this will fix it.
> I'll let you know how things work out.
> OpenAFS-info mailing list