Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) Oracle Solaris 11 Express 11/10 |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. The Name Service Switch (Overview)
Part II DNS Setup and Administration
3. DNS Setup and Administration (Reference)
Part III NIS Setup and Administration
4. Network Information Service (NIS) (Overview)
5. Setting Up and Configuring NIS Service
Before You Begin Configuring NIS
NIS and the Service Management Facility
Identify Your NIS Servers and Clients
Passwd Files and Namespace Security
Preparing Source Files for Conversion to NIS Maps
How to Prepare Source Files for Conversion
Setting Up the Master Server With ypinit
How to Set Up the Master Server Using ypinit
Master Supporting Multiple NIS Domains
Starting and Stopping NIS Service on the Master Server
Starting NIS Service Automatically
Starting and Stopping NIS From the Command Line
Part IV LDAP Naming Services Setup and Administration
8. Introduction to LDAP Naming Services (Overview/Reference)
9. LDAP Basic Components and Concepts (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Sun Java System Directory Server With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP General Reference (Reference)
15. Transitioning From NIS to LDAP (Overview/Tasks)
Part V Active Directory Naming Service
Your network can have one or more slave servers. Having slave servers ensures the continuity of NIS services when the master server is not available.
Before actually running ypinit to create the slave servers, you should run the domainname command on each NIS slave to make sure the domain name is consistent with the master server.
Note - Domain names are case-sensitive.
Make sure that the network is working properly before you configure an NIS slave server. In particular, check to be sure you can use rcp to send files from the master NIS server to NIS slaves.
The following procedure shows how to set up a slave server.
For more information, see How to Obtain Administrative Rights in System Administration Guide: Security Services.
Note - You must first configure the new slave server as an NIS client so that it can get the NIS maps from the master for the first time. See Setting Up NIS Clients for details.
# /usr/sbin/ypinit -c
The ypinit command prompts you for a list of NIS servers. Enter the name of the local slave you are working on first, then the master server, followed by the other NIS slave servers in your domain in order from the physically closest to the furthest in network terms.
# svcs network/nis/client STATE STIME FMRI online 20:32:56 svc:/network/nis/client:default
If svc:/network/nis/client is displayed with an online state, then NIS is running. If the service state is disabled, then NIS is not running.
# svcadm restart network/nis/client
# svcadm enable network/nis/client
# /usr/lib/netsvc/yp/ypstop
# /usr/lib/netsvc/yp/ypstart
# /usr/sbin/ypinit -s master
Where master is the machine name of the existing NIS master server.
Repeat the procedures described in this section for each machine you want configured as an NIS slave server.
The following procedure shows how to start NIS on a slave server.
For more information, see How to Obtain Administrative Rights in System Administration Guide: Security Services.
# svcadm disable network/nis/client # svcadm enable network/nis/server