NIS SG package

[Elmar P. Kolkman]

We are trying to have the NIS master in a SG package (so it is HA), but it is not really stable. Does anybody have any experience with this? What are the caveats you found? Any do's and dont's?
Thnx in advance.

[melvyn burnard]

NIS has not been *packaged* into a ServiceGuard package. Instead, normal NIS protocols are used to identify a backup server. This is the preferred configuration. There is no need to put NIS into a ServiceGuard package. Instead, use the normal configuration of making a secondary NIS server. This server may be on a ServiceGuard cluster or outside a ServiceGuard cluster.

[Elmar P. Kolkman]

What I need is a HA NIS master. I know I can configure all nodes as slaves, but users want to be able to change passwords, which means I need a master too. We have it working, sort of, but I was interested if someone else has it working and how (s)he has done it, because we have seen some strange behaviour.

[Hemanth Gurunath Basrur]

Hello Elmar,

Refer to the foll. docs for info.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B5140-90012/B5140-90012_top.html&con=/hpux/onlinedocs/B5140-90012/00/00/11-con.html&toc=/hpux/onlinedocs/B5140-90012/00/00/11-toc.html&searchterms=ServiceGuard%7cpackage%7cNIS&queryid=20031104-110930

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B5140-90012/B5140-90012_top.html&con=/hpux/onlinedocs/B5140-90012/00/00/12-con.html&toc=/hpux/onlinedocs/B5140-90012/00/00/12-toc.html&searchterms=ServiceGuard%7cpackage%7cNIS&queryid=20031104-110930

HTH.

Regards,
Hemanth

[Elmar P. Kolkman]

Sorry, but I really mean NIS, not NFS. NFS is working alright.

[Mark Grant]

You can actually have both nodes as masters and slaves of each other.

[Elmar P. Kolkman]

What do you mean ???
Have a node as both master and slave is not supported by NIS, as far as I know. A node is master or is a slave, not both.
A node has to be a client and a master or slave to be able to use NIS though. So do you mean I have to make all nodes (more than two, BTW) master? How do I make sure the passwords are changed on all servers then? Won't the masters complain that there are multiple masters for the same domain?

[Mark Grant]

Elmar. I have seen this done at IBM where all machines (HPUX by the way) were masters and slaves of eache other. The makefile was modified so that the yppush would "make passwd" and send the maps to the other machines. When I first arrived there I thought "This is odd" but it all seemed to work OK. If we actually had NIS set up where I am now I'd give this a try now but sadly I can't.

[Elmar P. Kolkman]

This seems tricky. But I will test it on a test environment I have available for this. Will keep you informed.

[Elmar P. Kolkman]

It seems I've found a solution: I have to restart the slaves on the other cluster nodes and then run an ypset to refresh everything... If I don't run slaves but just clients and a master the ypset would suffice, but that would mean I don't have NIS if the master is down... I'm going to test this more, since it is a simpler solution than setting up the cross-links suggested to me previously, which needed changes to the Makefile...

[Elmar P. Kolkman]

We just proofed a solution: running ypset on all slave nodes after restarting the master has it running again:

ypset $(hostname)

So we will add a script to the package control file to do this for all nodes in the cluster not running the master.

Thnx to all who replied, hope this solution will help others with problems like this too.

Rgds,

Elmar