Hi Cheryl,
I would also advise to go to 5.3.5R2. If you still have an issue after upgrade, I would like to look at netgroups entry for one of the clients in question along with autosupports, /etc/resolv.conf, /etc/nsswitch.conf, etc.
Please email the info directly to me at that point.
Thank you.
Regards, Jagan
From cruddace@feather.llnl.gov Thu May 25 17:32:29 2000 Date: Thu, 25 May 2000 17:23:02 -0700 (PDT) From: Cheryl Cruddace cruddace@feather.llnl.gov Subject: Re: NIS problem with netgroup file To: jagan@netapp.com Cc: toasters@mathworks.com MIME-Version: 1.0 Content-MD5: +YTS6ZN6Oo0B/5xulEuLqA==
Jagan Bearelly wrote:
I am assuming you are using DNS. There should be case sensitive FQDN entry that matches the "nslookup" output for a given client and please see that dns.domainname is set with the same case sensitive value because "ypmatch" on NIS server is case sensitive.
I am using DNS, I am not sure what you mean by case sensitive FQDN or do you mean case insensitive? All combos of case seem to work when I do an nslookup, i.e. feather, Feather, FEATHER...and none of this mattered for the first 1-1/2 years so why now? The dns.domain is set also.
Also, ONTAP version 5.3.4R3 doesn't have a fix for netgroup related issue (19922 netgroup lookups can fail with fully qualified domain name). This fix is available in 5.3.5, 5.3.5R1 and 5.3.5R2 which are the latest releases.
Thanks for the info. However, I went to the NOW site and the Data ONTAP Release Advisor (a really neat tool I just found) said to go to 5.3.5r2. So, is this not only the latest but also stable since stable is mucho importante. I am running off to conquer new worlds in another week and I can't get an unlisted number and hide since I will only be four trailers away from where I am now. And, I don't want to leave a bunch of limping filers as my legacy now do I???
Cheryl