Solaris Naming Setup and Configuration Guide

NIS+ Configuration Overview

Using the configuration scripts is the recommended method of setting up and configuring an NIS+ namespace. Using these scripts is easier than to trying to set up an NIS+ namespace with the NIS+ command set, as described in the subsequent chapters of this Part.

(See the nisserver, nispopulate, and nisclient man pages for complete descriptions of the scripts. See the glossary in Solaris Naming Administration Guide for definitions of terms and acronyms you do not recognize.)

You should not use the small sample NIS+ namespace referred to in this tutorial manual as a basis for your actual NIS+ namespace. You should destroy the sample namespace after you finish exploring it, instead of adding on to it. It is better to begin again and carefully plan your NIS+ hierarchy before you create your actual namespace.

Table 4-1 summarizes the recommended generic configuration procedure. The left column lists the major configuration activities, such as configuring the root domain or creating a client. The text in the middle describes the activities. The third column lists which script or NIS+ commands accomplish each step.

Table 4-1 Recommended NIS+ Configuration Procedure Overview



Script/NIS+ Commands 

Plan your new NIS+ namespace 

Plan your new NIS+ namespace. See NIS+ Transition Guide for a full discussion of planning requirements and steps. (If you are just following the NIS+ tutorial in a test-bed network, this step has been done for you.)


Prepare your existing namespace 

In order for the scripts to work best, your current namespace (if any) must be properly prepared. See "Preparing the Existing Namespace" and the NIS+ Transition Guide for a description of necessary preparations. (If you are just following the NIS+ tutorial in a test-bed network, this step has been done for you.)


Configure the Diffie-Hellman key length 

If you intend to use DES authentication, consider using Diffie-Hellman keys longer than the 192-bit default. The extended key length must be the same on all machines in the domain. Specify the desired key length before running the respective initialization scripts. 


Configure root Domain 

Create the root domain. Configure and initialize the root master server. Create the root domain admin group. 


Populate tables 

Populate the NIS+ tables of the root domain from text files or NIS maps. Create credentials for root domain clients. Create administrator credentials. 




Configure root domain clients 

Configure the client machines. (Some of them will subsequently be converted into servers.) Initialize users as NIS+ clients. 


Enable servers 

Enable some clients of the root domain to become servers. Some servers will later become root replicas; others will support lower-level domains. 


Configure root replicas 

Designate one or more of the servers you just configured as replicas of the root domain. 



Configure non-root domains 

Create a new domain. Designate a previously enabled server as its master. Create its admin group and admin credentials. 



Populate tables 

Create credentials for clients of the new domain. Populate the NIS+ tables of the new domain from text files or NIS maps. 


Configure non-root domain clients 

Configure the clients of the new domain. (Some may subsequently be converted into servers for lower-level domains.) Initialize users as NIS+ clients. 


The NIS+ scripts enable to you to skip most of the individual procedures included in the above activities.