Sun Storage 5210 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 
Sun Storage 5320 NAS Gateway/Cluster System
 
Sun Storage 5320 NAS Appliance
 
Sun Storage 5310 NAS Gateway System
 

GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
 

This document does not cover any configuration details on OpenLDAP and reader are requested to refer to appropriate document on how to configure OpenLDAP.

Enable                Yes
Domain (DN)           cn=manager,dc=mydomain,dc=com
Server                192.15.200.121
Password              **********

Where :

Domain (DN) : This is the distinguished name to bind to the server with. Both binddn and rootbinddn are set to same. Environment variable set with this 
option are "lookup.nssldap.binddn" and "lookup.nssldap.rootbinddn"

Server : IP Address of system where OpenLDAP is installed and configured. Please use the IP address and avoid using hostname. Environment variable set with 
this is option"lookup.nssldap.host"

Password : This is the password used during the bind operation for no root user ID. Both bindpw and rootbindpw are set to the same value. Environment variable 
set with this option are "lookup.nssldap.bindpw" and "lookup.nssldap.rootbindpw"

2. On the Linux host where OpenLDAP is installed start the OpenLDAP in the debug mode. We can start the ldap with following command

/usr/local/libexec/slapd -d <Debug Level>

Where
* /usr/local/libexec is the default installation directory for OpenLDAP. Please check the location where slapd is installed if the default directory is 
changed while installation.
* <Debug Level> is between 0 - 9 with 9 being the highest level.

For most of the issue debug level 4 would be sufficient.

# /usr/local/libexec/slapd -d 4

While starting slapd in debug mode it is started in the foreground and messages are logged to standard error.

NOTE: If you wish to log the messages to a file start the slapd with redirecting the standard error to a file :

# /usr/local/libexec/slapd -d 4 2> /tmp/slapd_logs.out &

"slapd" would start logging the messages the movement NAS head start communication with OpenLDAP server. Out of the messages logged by the host on console, look at the send_ldap_result output as shown below :

==> bdb_bind: dn: cn=manager,dc=mydomain,dc=com
send_ldap_result: err=0 matched="" text=""

If the "err" is not 0, then we are having issues while connecting to the LDAP directory through the binddn (lookup.nssldap.binddn) specified on the NAS head. The err may vary, please use LDAP Error Codes to know the details of the error code.

This solution has no attachment