How to Set Up Multihomed NIS+ Replica Servers

The procedure for setting up a multihomed NIS+ server is the same as setting up a single interface server. The only difference is that there are more interfaces that need to be defined in the hosts database, the /etc/hosts file and NIS+ hosts table.

Prior to the Solaris 10 7/07 release, you also need to define interfaces in the /etc/inet/ipnodes file and ipnodes table.

Once the host information is defined, use the nisclient and nisserver scripts to set up the multihomed NIS+ server.

When setting up a multihomed NIS+ server, the server's primary name must be the same as the nodename for the system. This is a requirement of both Secured RPC and nisclient.

• Secured RPC relies on the nodename to create the netname for authentication.

• nisclient relies on the primary name to create the credential for the client.

If these names are different, Secure RPC authentication will fail to work properly causing NIS+ problems.

This procedure shows how to set up any NIS+ non-root master servers. The following example creates a replica for the root domain. For information about setting up a multihomed root server, see How to Set Up a Multihomed NIS+ Root Master Server.

1. Add the server host information into the hosts file.

   ---

   Note –

   Prior to the Solaris 10 7/07 release, you must also load IPv6 server host information into the client's ipnodes file.

   ---

   For example, for the hostB system with three interfaces:

   192.168.11.y hostB hostB-11 192.168.12.x hostB hostB-12 192.168.14.z hostB hostB-14

2. On the root master server, use either nispopulate or nisaddent to load the new host information into the hosts file.

   ---

   Note –

   Prior to the Solaris 10 7/07 release, you must also load host IPv6 information into the client's ipnodes table.

   ---

   For example:

   hostA# nispopulate -F -d sun.com hosts

   where the example shows sun.com as the NIS+ root domain name. Issue the nispopulate command specifying the name of your NIS+ root domain name.

3. On the root master server, use the nisclient script to create the credential for the new client.

   For example:

   hostA# nisclient -c -d sun.com hostB

   where the example shows sun.com as the root domain name. Issue the nisclient command specifying the name of your root domain name.

4. On the non-root master server, use nisclient to start the new server if it is not already running and initialize the machine as an NIS+ client.

   For example:

   hostB# nisclient -i -d sun.com

   where the example shows sun.com as the root domain name. Issue the nisclient command specifying the name of your root domain name.

5. On the root master server, use nisserver to create a non-root master.

   For example:

   hostA# nisserver -M -d eng.sun.com -h hostB.sun.com.

   where the example shows eng.sun.com as the NIS+ domain name and hostB.sun.com as the fully-qualified hostname for the NIS+ server. Issue the nisserver command specifying the name of your NIS+ domain and the fully-qualified hostname for the NIS+ server.

6. On the root master server, use nisserver to set up a replica server.

   For example:

   hostA# nisserver -R -d sun.com -h hostB.sun.com.

   where the example shows sun.com as the replica server and hostB.sun.com as the fully-qualified hostname for the NIS+ server. Issue the nisserver command specifying the name of your replica server and NIS+ domain.

   After completing the steps for setting up a multihome NIS+ replica server, the remainder of the setup is exactly the same as for a single interface server.