namcd will not start when the server is rebooted

1) When OES server reboots the namcd will not started automatically and needs to start it manually.
2) "id admin" or "id" returns correct information .
3) No error messages in /var/log/message.

The nam.conf was setup as below, in this case :-

server-01:~ # more /etc/nam.conf
base-name=o=org
admin-fdn=cn=namlogin,o=org
preferred-server=100.100.100.100  (Pointing to itself)
num-threads=5
schema=rfc2307
enable-persistent-cache=YES
user-hash-size=211
group-hash-size=211
persistent-cache-refresh-period=28800
persistent-cache-refresh-flag=all
create-home=yes
type-of-authentication=2
certificate-file-type=der
ldap-ssl-port=636
ldap-port=389
support-alias-name=no
support-outside-base-context=yes

Observe the 2nd line "admin-fdn=cn=namlogin,o=org ". In this line it can be seen that the user defined is not admin user. It is eDirectory user. This user did not have admin privilidges.

1) Check "admin-fdn" parameter under nam.conf, verify that the user specified here has LUM enabled
2. To verify the user is  LUM enabled,  from the terminal window run id <username> i.e in this case id namlogin. It came up with the result no such user.
3) Then from iManager, go to Linux User Management, click on "Enable User for Linux".
4. Select the user, LUM enabled group, unix workstation object and click on Finish.
5.  From the server terminal  run  "namconfig -k" and then "namconfig cache_refresh". This will associate the certificate and will restart namcd service.
6. Restart the server namcd should load automatically.