Brian Pawlowski beepy@netapp.com writes:
Anyway, I have a question:
- Has anyone enable NFS/TCP on a NetApp box permanently? If so, why?
(All of the below info only applies to Solaris here.)
Yes. Because when the option was added to the NetApp OS, our Sun clients needed it. I've kept the option because it's never caused any problems (well, until recently). One way that I look at it is that NFS/TCP is tested in our environment, NFS/UDP is not.
(The recent problem is a Solaris bug where Solaris boxes can't reestablish NFS/TCP connections if the TCP route is ever dropped. It only affects Sun-NetApp connections that cross a router. Using a default route or UDP, we couldn't reproduce the problem.)
We considered disabling NFS/TCP because of the above problem, but since we were planning on changing our Suns to use router discovery (creating a default route), it wasn't necessary. Previously, we were running "routed -q" on all Suns (a historical artifact).
Note that we wouldn't have disabled the NetApp option until after all Suns had stopped using it. We would force udp mounting on each Sun client via the udp mount option and then wait a very long time.
Actually, the default route *can* actually be dropped if the router is down for longer than the router discovery protocol timeout, so we're not 100% clear of the problem. Maybe we'll switch to UDP...
- Has any of you customers disabled Version 3 NFS for any reason, if so why?
No.
- Dan