NIS issue with ypwhich

[Andrew Kaplan]

Hi there --

We have a ServiceGuard cluster with several packages and NIS configured such that one server is the Master, and the other is the Slave.

When I do a ypwhich on the Master, the Master server hostname is the ouput that I see onscreen. However, when I do the same on the Slave, the name of one of the packages is what is seen as opposed to the hostname of the Master.

How can I correct this so that the hostname of the Master is the onscreen output on the Slave? Thanks.

[Jeff_Traigle · Accepted solution]

If you run ypbind on the client with the -ypset option, you can use the ypset command to change the binding.

[Steven Schweda]

Actual commands used with their actual output
might be clearer than this description.

> How can I correct this [...]

What info would you like?

"ypwhich -m"?

[Andrew Kaplan]

I tried using the -ypset option, but that does not seem to have worked. Just so we are on the same page: what is the full syntax to use?

[Jeff_Traigle]

You'd run ypbind like:

ypbind -ypset

(You can set the option with YPBIND_OPTIONS in /etc/rc.config.d/namesvrs for use at startup.)

To change the binding from the server:

ypset -h client server

[Dave Olker]

What operating system are your NIS systems running?

Dave

[Andrew Kaplan]

Hi there --

The operating system for both servers is HPUX 11i v1.

[Dave Olker]

Hi Andrew,

11i v1 and newer systems offer a preferred method of configuring a system to contact specific NIS servers - "ypinit -c". When you use this command it prompts you for a list of NIS servers in the order you want the client to bind to them. These systems can be on remote subnets, local subnets, etc.

In my opinion this is a far superior solution to using ypset or reverting to the normal UDP broadcasting mechanism, which is probably how you're getting bound to a package alias IP address.

Regards,

Dave

[Andrew Kaplan]

Hi there --

I ran the ypinit command with the following syntax:
ypinit -s cosmos1

I had the procedure continue on non-fatal errors, and allowed for the existing directory to be overwritten.

There were several errors concerning the ethers.byaddr, ethers.byname, netmasks.byaddr, and bootparams files. I know the two ethers files can be safely ignored, but I am concerned about the latter two files.

I had also had two follow questions:
1. /etc/hosts file on the slave server does not match that of which is on the master. Can I simply copy the file that is on the master to the slave, or is there a better method?

2. /etc/passwd file on the slave server does not match that of which is on the master. Is that by design, or should the two be the same? Thanks.

[Dave Olker]

Hang on, you're getting into completely different topics here. You're original thread topic was "how can I get my NIS system to bind to a specific server". That's what the "ypinit -c" comes in.

Now you're talking about setting up an NIS Slave and how to distribute maps. Is there another problem you're trying to solve or is this somehow related to the original thread topic?

Dave

[Andrew Kaplan]

Oops...Sorry about that. I'll put those in another thread. Thanks for the help in any event.