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
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)
NIS-to-LDAP Tools and the Service Management Facility
NIS-to-LDAP Audience Assumptions
When Not to Use the NIS-to-LDAP Service
Effects of the NIS-to-LDAP Service on Users
NIS-to-LDAP Transition Terminology
NIS-to-LDAP Commands, Files, and Maps
Transitioning From NIS to LDAP (Task Map)
Prerequisites for the NIS-to-LDAP Transition
Setting Up the NIS-to-LDAP Service
How to Set Up the N2L Service With Standard Mappings
How to Set Up the N2L Service With Custom or Nonstandard Mappings
Example 2-Implementing a Custom Map
NIS-to-LDAP Best Practices With Sun Java System Directory Server
Creating Virtual List View Indexes With Sun Java System Directory Server
VLVs for Custom and Nonstandard Maps
Avoiding Server Timeouts With Sun Java System Directory Server
Avoiding Buffer Overruns With Sun Java System Directory Server
Debugging the NISLDAPmapping File
Part V Active Directory Naming Service
A site that has transitioned from NIS to LDAP using the N2L service is expected to gradually replace all NIS clients with Solaris LDAP naming services clients. Support for NIS clients eventually becomes redundant. However, if required, the N2L service provides two ways to return to traditional NIS, as explained in the next two procedures.
Tip - Traditional NIS ignores the N2L versions of the NIS maps if those maps are present. After reverting to NIS, if you leave the N2L versions of the maps on the server, the N2L maps do not cause problems. Therefore, it might be useful to keep the N2L maps in case you later decide to re-enable N2L. However, the maps do take up disk space.
For more information , see How to Obtain Administrative Rights in System Administration Guide: Security Services.
# svcadm disable network/nis/server:default
This command backs up and moves the N2L mapping file.
# mv /var/yp/NISLDAPmapping backup_filename
# NOPUSH=1
# cd /var/yp # make
# rm /var/yp/domainname/LDAP_*
# svcadm enable network/nis/server:default
Back up the old NIS source files before performing this procedure.
For more information, see How to Obtain Administrative Rights in System Administration Guide: Security Services.
# svcadm disable network/nis/server:default
# ypserv -r
Wait for ypserv to exit.
This command backs up and moves the N2L mapping file.
# mv /var/yp/NISLDAPmapping backup_filename
# ypmap2src
# rm /var/yp/domainname/LDAP_*
# svcadm enable network/nis/server:default