JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Working With Naming and Directory Services in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

Part I About Naming and Directory Services

1.  Naming and Directory Services (Overview)

2.  Name Service Switch (Overview)

3.  Managing DNS (Tasks)

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)

7.  Administering NIS (Tasks)

8.  NIS Troubleshooting

Part III LDAP Naming 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)

15.  Transitioning From NIS to LDAP (Tasks)

NIS-to-LDAP Service Overview

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

Supported Standard Mappings

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

Examples of Custom Maps

NIS-to-LDAP Best Practices With Oracle Directory Server Enterprise Edition

Creating Virtual List View Indexes With Oracle Directory Server Enterprise Edition

VLVs for Standard Maps

VLVs for Custom and Nonstandard Maps

Avoiding Server Timeouts With Oracle Directory Server Enterprise Edition

Avoiding Buffer Overruns With Oracle Directory Server Enterprise Edition

NIS-to-LDAP Restrictions

NIS-to-LDAP Troubleshooting

Common LDAP Error Messages

NIS-to-LDAP Issues

Debugging the NISLDAPmapping File

N2L Server Timeout Issue

N2L Lock File Issue

N2L Deadlock Issue

Reverting to NIS

How to Revert to Maps Based on Old Source Files

How to Revert to Maps Based on Current DIT Contents

Glossary

Index

Reverting to NIS

A site that has transitioned from NIS to LDAP using the N2L service is expected to gradually replace all NIS clients with 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.


How to Revert to Maps Based on Old Source Files

  1. Become an administrator.

    For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

  2. Stop the NIS daemons.
    # svcadm disable network/nis/server:default
  3. Disable N2L.

    This command backs up and moves the N2L mapping file.

    # mv /var/yp/NISLDAPmapping backup_filename
  4. Set the NOPUSH environment variable so the new maps are not pushed by ypmake.
    # NOPUSH=1
  5. Make a new set of NIS maps that are based on the old sources.
    # cd /var/yp
    # make
  6. (Optional) Remove N2L versions of the NIS maps.
    # rm /var/yp/domainname/LDAP_*
  7. Start the DNS and the NIS service.
    # svcadm enable network/dns/client:default
    # svcadm enable network/nis/server:default

How to Revert to Maps Based on Current DIT Contents

Back up the old NIS source files before performing this procedure.

  1. Become an administrator.

    For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

  2. Stop the NIS daemons.
    # svcadm disable network/nis/server:default
  3. Update the maps from the DIT.
    # ypserv -r

    Wait for ypserv to exit.

  4. Disable N2L.

    This command backs up and moves the N2L mapping file.

    # mv /var/yp/NISLDAPmapping backup_filename
  5. Regenerate the NIS source files.
    # ypmap2src
  6. Manually check that regenerated NIS source files have the correct content and structure.
  7. Move the regenerated NIS source files to the appropriate directories.
  8. (Optional) Remove the N2L versions of the mapping files.
    # rm /var/yp/domainname/LDAP_*
  9. Start the DNS and NIS service.
    # svcadm enable network/dns/client:default
    # svcadm enable network/nis/server:default