Over the past few months, for various reasons, our F630 has lost it's connection to our NIS slave. Pretty well every time this happens the filer decides not to serve either NFS or CIFS clients(usually CIFS). The only way to get the machine to serve data again is to run ypset and have it bind to a new NIS slave or(as a last resort) reboot the filer and have it automatically discover another slave. Shouldn't the filer bind itself to a new NIS slave after some timeout period without any intervention?
We're currently running DOT 5.3.1 but have seen the problem on several 5.2 versions.
Does anyone have any recommendations or are we stuck with less stable NIS client?
-Sean
Sean Hinchey wrote:
Does anyone have any recommendations or are we stuck with less stable NIS client?
-Sean
After battling this same problem for months i finally put some hooks into my makefile.nis that copies the files locally to all our filers and turned off NIS. You are correct, Netapp's are not good NIS clients.
Graham
-
Graham C. Knight -
Sean Hinchey