Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Naming and Directory Services Oracle Solaris 11 Information Library |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. Name Service Switch (Overview)
4. Setting Up Oracle Solaris Active Directory Clients (Tasks)
Part II NIS Setup and Administration
5. Network Information Service (Overview)
6. Setting Up and Configuring NIS (Tasks)
Before You Begin Configuring NIS
NIS and the Service Management Facility
Identify Your NIS Servers and Clients
passwd Files and Namespace Security
How to Prepare Source Files for Conversion
How to Install the NIS Master Server Package
How to Set Up the Master Server
How to Support Multiple NIS Domains on One Master Server
Starting and Stopping NIS Services on an NIS Server
Starting the NIS Service Automatically
How to Enable the NIS Server Services Manually
How to Disable the NIS Server Services
How to Refresh the NIS Server Service
How to Configure an NIS Client in Broadcast Mode
How to Configure an NIS Client Using Specific NIS Servers
Disabling the NIS Client Services
9. Introduction to LDAP Naming Services (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP Naming Service (Reference)
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 the ypinit command to create the slave servers, first make sure that the svc:/network/nis/domain service has been configured.
Note - NIS domain names are case-sensitive, although DNS domain names are not.
Make sure that the network is working properly before you configure an NIS slave server. In particular, make sure that you can use the sshd command to send files from the master NIS server to NIS slaves.
The following procedure explains how to set up a slave server. Repeat this procedure for each machine you want configured as an NIS slave server.
For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.
Add the name and IP address of each of the other NIS servers. Use the following format: IPaddress FQDN-hostname aliases.
For example:
129.0.0.1 master.example.com master 129.0.0.2 slave1.example.com slave1 129.0.0.3 slave2.example.com slave2
Note - You must first configure the new slave server as an NIS client so that it can obtain the NIS maps from the master server for the first time. See Administering NIS Clients for details.
# /usr/sbin/ypinit -c
The ypinit command prompts you for a list of NIS servers. Type the name of the local slave you are working on first, then type the name of the master server, followed by names of the other NIS slave servers in your domain. For the other slave servers, follow the order from the physically closest to the furthest in network terms.
# svcs \*nis\* STATE STIME FMRI online 20:32:56 svc:/network/nis/domain:default online 20:32:56 svc:/network/nis/client:default
If the services are displayed with an online state, then NIS is running. If the service state is disabled, then NIS is not running.
# svcadm restart network/nis/domain # svcadm restart network/nis/client
# svcadm enable network/nis/domain # svcadm enable network/nis/client
# svcs network/nis/server STATE STIME FMRI offline 20:32:56 svc:/network/nis/server:default
# svcadm restart network/nis/server
# svcadm enable network/nis/server
# /usr/sbin/ypinit -s master
where master is the machine name of the existing NIS master server.
The following procedure explains how to start NIS on a slave server.
For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.
# svcadm restart network/nis/domain # svcadm restart network/nis/client # svcadm enable network/nis/server