[OpenAFS] NAT issues.
Jeffrey Hartwigsen
jrhartwigsen@linkp.com
Wed, 26 Apr 2006 16:26:03 -0500
Jeffrey Altman wrote:
>
> I would need to see the output of the file server logs at level 125
> to explain to you exactly what is happening. However, suffice it to
> say that if your NATs do not keep the port mappings open, nothing the
> file server does is going to help.
>
> Jeffrey Altman
>
After resetting the UDP timeouts on both of our NAT boxes to 11 minutes,
things are much improved. We are still experiencing some problems with
timeouts though. (Windows claims "The network path cannot be found" when
trying to access filespace)
What does this line in the Filelog mean?
Wed Apr 26 16:12:12 2006 SAFS_FetchStatus, Fid = 536870918.10604.5870,
Host 192.188.163.112:12096, Id 6
Wed Apr 26 16:12:12 2006 SAFS_FetchStatus, Fid = 536870918.10602.5869,
Host 192.188.163.112:12096, Id 6
Wed Apr 26 16:12:12 2006 SAFS_FetchStatus, Fid = 536870918.10600.5868,
Host 192.188.163.112:12096, Id 6
I had 939 entries like this seemingly from the same client (port number)
within 2 seconds. I'm also still getting some ProbeUuid failures. I can
send the context of those along to if it would be helpful.
Thanks again,
Jeff