[OpenAFS] Re: Server disk operations speed

Andrew Deason adeason@sinenomine.net
Tue, 9 Apr 2013 18:39:32 -0500

On Tue, 9 Apr 2013 23:36:15 +0300 (EEST)
"Jukka Tuominen" <jukka.tuominen@finndesign.fi> wrote:

> Does it sound resonable to prefer DNS names over external IP's, and
> external IP's over local IP's? The rationale there would be to prefer
> dynamic over static definitions, and IP's that the clients can see
> over local IP's that may not be accessible always? (external meaning
> WAN and internal LAN IP's). I've started with whatever worked, and
> later on moved towards what I just described.

I'm not quite sure if you're asking what you as a person should do, or
if you're asking what the code does.

If you mean what IPs you should be specifying in various places, you
should put in the 'public' IPs that are always reachable by everyone.
That means put that in CellServDB and probably the fileserver NetInfo.
If you put a 'private' IP in there, then clients accessing from
elsewhere may also see that IP, and obviously they won't be able to
connect. We don't really do "split-horizon"-style setups, since everyone
gets the same list of IPs for fileservers.

> If you just want to see where the traffic is
> > going, capture some net traffic. All AFS traffic for a client
> > interacting with a server should happen on ports 7000-7003 UDP. If
> > we're contacting an IP that is one of the local host's interfaces,
> > it's up to the underlying OS where the packets physically go.
> OK, I'll try to figure out how to do that. Wireshark is my guess to
> start with.

Yes, tcpdump or wireshark are the usual tools. wireshark is/can be
graphical and probably more intuitive if you haven't used similar tools

Andrew Deason