|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: Naming and Directory Services Oracle Solaris 11 Information Library|
Make sure that the system is set up as a working traditional NIS server before running the inityp2l script to enable N2L mode.
Configure the LDAP directory server on your system.
Oracle Directory Server Enterprise Edition and compatible versions of directory servers offered by Oracle, are supported with the NIS-to-LDAP migration tools. If you use Oracle Directory Server Enterprise Edition, configure the server by using the idsconfig command before you set up the N2L service. For more information about idsconfig, see Chapter 11, Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks) and the idsconfig(1M) man page.
Other (third-party) LDAP servers might work with the N2L service, but they are not supported by Oracle. If you are using an LDAP server other than the Oracle Directory Server Enterprise Edition or compatible Oracle servers, you must manually configure the server to support RFC 2307bis, RFC 4876, or their successors' schemas before you set up the N2L service.
Use files before dns for the config/host property.
Ensure that the addresses of the N2L master server and the LDAP server are present in the hosts file on the N2L master server.
An alternative solution is to list the LDAP server address, not its host name, in ypserv. This means that the LDAP server address is listed in another place, so changing the address of either the LDAP server or the N2L master server requires additional file modifications.