Toasters-
A rather interesting update for everyone on the problem I posted yesterday with an 880c and FAS960c clusters that refused to bind to a Solaris 8 NIS server.
Just to help us isolate the problem between OS and NIS, we initialized a Solaris 2.6 system, as a NIS slave to the Solaris 8 NIS server that we couldn't get the filers to bind to. Surprisingly, the FAS960c bound with no problems to the Solaris 2.6 NIS slave. To us, this rules out a configuration issue with the NIS domain itself and focuses the problem back to an apparent Solaris 8 NIS/DataONTAP incompatibility.
I was somewhat surprised that no one replied that they are using Solaris 8 NIS with DataONTAP. I have updated the tech support case I have opened with both Sun and NetApp and I'll keep the list informed as the solution moves along.
Thanks, Brent Killion
On Fri, Jan 31, 2003 at 04:10:21PM -0700, Brent.Killion@pinnaclewest.com wrote:
I was somewhat surprised that no one replied that they are using Solaris 8 NIS with DataONTAP. I have updated the tech support case I have opened with both Sun and NetApp and I'll keep the list informed as the solution moves along.
Well, some of us were busy :)
I have all of my filters bound to Solaris 8 NIS servers, masters and slaves, without hiccup or issue.
Perhaps it is an issue with patch revisions...
Brent Killion writes:
Just to help us isolate the problem between OS and NIS, we initialized a Solaris 2.6 system, as a NIS slave to the Solaris 8 NIS server that we couldn't get the filers to bind to. Surprisingly, the FAS960c bound with no problems to the Solaris 2.6 NIS slave. To us, this rules out a configuration issue with the NIS domain itself and focuses the problem back to an apparent Solaris 8 NIS/DataONTAP incompatibility.
I was somewhat surprised that no one replied that they are using Solaris 8 NIS with DataONTAP. I have updated the tech support case I have opened with both Sun and NetApp and I'll keep the list informed as the solution moves along.
We are using Solaris 8 for our NIS slaves. Our filers are running 6.2.1R2D2 (F760, F840, F880, no clustering).
We have the NIS patch 110511 installed on our slaves, in versions ranging from 01 to 05. I don't think we've seen any NIS trouble with our configuration.
quentin.fennessy@amd.com (Quentin Fennessy) writes: [...]
We are using Solaris 8 for our NIS slaves. Our filers are running 6.2.1R2D2 (F760, F840, F880, no clustering).
We have the NIS patch 110511 installed on our slaves, in versions ranging from 01 to 05. I don't think we've seen any NIS trouble with our configuration.
Ummm... patch 110511 is for rpc.nisd, i.e. NIS+. Are you running NIS+ in NIS(YP)-compatibility mode (i.e. -Y option on nisd)? I imagine this might well be less filer-friendly than running straight NIS (ypserv).
On the other hand, if you are running straight NIS(YP), the ypserv patch sequence in Solaris 8 is 109328 (-03 is current).
Chris Thompson Email: cet1@cam.ac.uk
Chris Thompson writes:
quentin.fennessy@amd.com (Quentin Fennessy) writes: [...]
We are using Solaris 8 for our NIS slaves. Our filers are running 6.2.1R2D2 (F760, F840, F880, no clustering).
We have the NIS patch 110511 installed on our slaves, in versions ranging from 01 to 05. I don't think we've seen any NIS trouble with our configuration.
Ummm... patch 110511 is for rpc.nisd, i.e. NIS+. Are you running NIS+ in NIS(YP)-compatibility mode (i.e. -Y option on nisd)? I imagine this might well be less filer-friendly than running straight NIS (ypserv).
No, we're not using NIS+ atall.
On the other hand, if you are running straight NIS(YP), the ypserv patch sequence in Solaris 8 is 109328 (-03 is current).
Oops. Thanks, Chris. We have the nisd patch installed, but you are correct -- the important patch is 109328. We are running some slaves at -02 and some at -03 with no problems.
Just to add to the experience, we have been using filers and Solaris 2.6 and 8 NIS+ in YP compatibility mode for years with no problems on filers.
The only issue we found is with the netgroup implementation in NIS+, so we use local files.
/Brian/ IT System Admin Cisco Systems
-
Brent.Killion＠pinnaclewest.com -
Brian Long -
Chris Thompson -
Mike Horwath -
Quentin Fennessy