NIS plain (not PLUS)

[Bill Short]

Automounting & manual mounting stops working on 11.11 NFS clients when changing NIS Master to 11.11 workstation from 10.20 workstation.

[Theresa Patrie]

Hi All, This is the rest of Bill's post. He tried to attach it, but it didn't work. He is out today so I am finishing his post for him. I hope somebody out there has some ideas. We haven't tried a complete shutdown of the network because we were hoping to do this uptime. Maybe that is not possible??
Thanks, Theresa
----------------------------------------

When we switch over our production domain (2 tries so far) from our old 10.20 NIS Master to our new 11.11 NIS Master, ALL of our 11.11 NFS clients stop automounting/manual mounting NFS servers (except previously instantiated mounts remain intact). The only NIS map source files we copied over to the 11.11 NIS Master before "ypinit -m" were "passwd", "group", and "netgroup". We of course changed the "namesvrs" config files appropriately on old 10.20 and new 11.11 masters and rebooted each and "ypinit -s {11.11_master_name} ALL of our NIS slaves (some 10.20, some 11.11). Because ALL 11.11 NIS clients cease mounting anything new at that point, we have had to back out twice so far by reverting back to the old 10.20 NIS Master, which immediately resumes ALL 11.11 NIS client mounting WITHOUT REBOOTING!!!
All 11.11 boxes including that NIS Master have "nsswitch.conf" set to "files" first for "services", "rpc", "hosts" (small "hosts" stub files on each box, default to DNS next) which means they ALL boot up with this and thus would also get this (and all other 11.11 default shipped NIS map source files) even if they were "leaking" over into NIS for this info. We have set up a dummy test NIS domain modeled after the production domain and collected only 1 single "status=2" automount.log entry (No such file or directory) from an 11.11 NFS client, the mount of which later succeeded, thus NOT exposing anything for us!!! HP phone support can not resolve at this point because they need to get on our machines which is not possible because of our firewall.

Has anyone seen something like this with NIS "plain" (not PLUS)???

[Steve Labar]

I'm not sure if this problem is directly related to switching NIS Master. Where do the directories physically reside that need to be automounted by the client? If they are on the new NIS master, have you exported these directories by listing them in /etc/exports then enabling NFS server on new NIS master and doing an exportfs -a? Also, have you changed your clients' automount files to use the new server ID? If your exported directories are still in original location, have you verified original file server is in new NIS domain maps?

Good Luck.

Steve

[Bill Short]

Steve Labar,
The data servers remain the same in that they are just NIS clients bound to the various slaves (which get "ypinit -s {10.20_or_11.11
NIS Master hostname}") and thus are NOT NIS Master or slaves themselves.

Bill Short

[Shannon Petry]

If all your clients are stopping NFS mounting and automounting when you switch servers, then look at the maps.

Make sure that auto.master is correct and the same on both the new and old server.
ypcat auto.master
ypcat -k auto.master

Did you have custom maps for auto.direct or auto.home?

Make sure that you copy the ypinit script from /var/yp or the Makefile (depending on which one you use) as well as all relavent information.

This could also have to do with the netgroup file.
On both the old and new NIS servers check the maps.
ypcat -k netgroup
ypcat netgroup

Make sure that they match up.

Regards,
Shannon

[Bill Short]

Shannon Petry,
Interesting that the /var/yp/{domainname} dir. has auto.master.dir, auto.master.pag BUT has auto_master.time IN BOTH the
old 10.20 Master & the new 11.11 Master (how confusing switching from "." to "_"!!!). Anyway, we ONLY HAVE one single source file "auto_master" on BOTH the 10.20 (contents "/net -hosts -soft") & the 11.11 (contents "/net -hosts -nosuid,soft") which ARE diff. but the first time we tried the switchover, I had copied that 10.20 sourcefile (as well as ALL others) to the 11.11 Master before initing it and we had the SAME overall automounting failure as the 2nd try in which we ONLY copied the 10.20's passwd, group, netgroup files (ALL others being 11.11 stock-shipped sourcefiles) before initing. Thus I don't think the 11.11 "nosuid" could be the cause? Bill Short

[Theresa Patrie]

We have done some more testing on our situation here and have found that the problem source is our Netapp Filer. Almost all nfs mounts are to the filer and this is where the failure occurs. If I log into the filer and configure it for the new 11i nis master, I can not establish a new nfs mount to it from a nis client. If I immediately configure it back to the original 10.20 nis master, I can immediately establish a new nfs mount to it. I have a call open with Network Appliance support, but thought I would throw it out here as well.
Thanks,
Theresa & Bill

[Adam Harvey_1]

I've just noticed a significant difference in the two NIS mainstays: "/var/yp/ypmake" and "/var/yp/Makefile" between the two versions of HP-UX:
makedbm is called with the '-l' option (force lower-case) for 'netgroup.byhost'.

Maps built on HP-UX 11.23 (or 11.11 as it is works in the same way) with lower-case "netgroup.byhost" cause netgroup controlled exports on HP-UX servers and NetApp filers to refuse NFS mount requests by valid clients.

Having removed the offending '-l' from both files, our NFS "premission denied" issues have been resolved.

Adam Harvey

[NB: Opinions expressed above are not those of my employer]

[Blofeld]

Theresa
You may want to look at the NFS version on the Filers vs the new NIS master.