We have been using NIS+ on a Solaris 2.6 environment for 5 years and NIS+ on a separate environment for over a year with no issues at all. (Both in compatibility mode)

We regard to the NIS Group update issue it is probably a line in the group file that is over 1024 characters in length. We have this happen regularly and the effect is that people have access problems usually via CIFS. We have to "manage" the entry to less than 1024 characters and the group update works OK. This will eventually cause us a problem as there is only so much slack in the one entry that we can take out. There is no way that we can split the group as it is used to manage access to a third party product. One to watch for... :)

Ray Griffith

-----Original Message----- From: Clawson, Simon [mailto:simon_clawson@mentorg.com] Sent: 21 February 2003 09:44 To: 'Brent.Killion@pinnaclewest.com'; toasters@mathworks.com Subject: RE: DataONTAP and Solaris 8 NIS Update

Hi,

We have been using a Solaris 8 NIS Slave, and a Solaris 2.6 NIS Master for over a year now. We have no major hassles, though I do see a message in the syslog on the filer -

Fri Feb 21 00:00:55 GMT [nis_grp_updater:warning]: NIS group map has invalid entry in line 7. Continuing to build Local NIS Group Cache. Fri Feb 21 00:00:55 GMT [nis_grp_updater:warning]: NIS group map has invalid entry in line 27. Continuing to build Local NIS Group Cache.

Which I guess is due to some spurious entry in the group file. I will eventually sort this out (maybe even today) but apart from that there seems to be no NIS issues at all. FYI, I just did a ypwhich on the filer and it binds to the Solaris 8 slave. Recently we had NT PDC issues, and the only way onto the filer was by NFS mounted shares, so it seems to be as robust as ever.

Simon

-----Original Message----- From: Brent.Killion@pinnaclewest.com [mailto:Brent.Killion@pinnaclewest.com] Sent: 31 January 2003 23:10 To: toasters@mathworks.com Subject: DataONTAP and Solaris 8 NIS Update

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