Operating System - HP-UX
1836373 Members
2270 Online
110100 Solutions
New Discussion

NIS Servers Binding Troubles

 
Peter_17
Frequent Advisor

NIS Servers Binding Troubles

All,

We have a NIS Master Server along with six Slave servers, but when I log into one of the slaves and do a ypwhich, they are mostly bound to themselves. Should they be bound to the master server? Also, if I do a ypwhich on the Master server, it's bound to one of the slaves. In their /etc/rc.config.d/namesvrs files, the appropriate flags are set for each of them. (server/client and slave/client).

Any insight appreciated.


Thanks,

Pete
4 REPLIES 4
Vito Sarducci
Regular Advisor

Re: NIS Servers Binding Troubles

Just one thought, in what sequence did you boot the master and slaves up after configuring the NIS?

I know in the SUN world, you must boot the master NIS Server first otherwise the slaves have no way to validate their configurations?

HTH,

Vito
Lifes too short to stress out, Enjoy every day you have on earth!
Sachin Patel
Honored Contributor

Re: NIS Servers Binding Troubles

Hi Peter,
When ypbind starts at boot time it uses two metod to bind to nis server.
1. Broadcast: it ask in network if any of the nis server is available if someone replys then it binds there.
2. fixed server: ask that server only.

You can change your bind if you are using -ypset options.
#ypset servername (man on ypset for more options)
ypset will not make your system go down so give it a try.

If you want to use ypset option you can define in /etc/rc.config.d/namesvrs
YPBIND_OPTIONS=-ypset

If you want to bind to fixed server all the time then
YPSET_ADDR="ip of server"

I hope this will help.
Sachin

Is photography a hobby or another way to spend $
Patrick Wallek
Honored Contributor

Re: NIS Servers Binding Troubles

There isn't a problem with an NIS slave being bound to itself. That is actually the behavior that I would hope for.

We have an environment much like yours, though not as many slave servers, and the couple of slaves I have checked are bound to themselves. The master is also bound to itself, but I would worry about the master binding to a slave, that shouldn't be a problem either.

As long as all of your NIS maps on your slaves are getting updated regularly and everything is in sync you are OK.
Ravi_8
Honored Contributor

Re: NIS Servers Binding Troubles

Hi,
you might have changed the booting sequence, first the master than the slaves. In our network. all the slaves are binding to master and master binding to itself. all the clients are binding to either slave or master.
But what matters here is whether slaves receiving the modified maps from master or not. since in your case it is happening well, no need to worry.
never give up