Hi

I have a client with a tree with multiple servers in multiple OU's and
multiple partitions.
The remote servers have the ou=common,o=company partition and
individual ou=site_x,ou=state_X,o=company partitions

The remote servers are platespin protected.
The work when the system fail's over

They dont work properly when the systems do a test mode failover.
They fail beacuse they are in isolation.

These servers do not have the root partition or the o=company
partition, only the above 2 partitions, otherwise the subordiante
reference and partition replicas go nuts.

An admin equivalent user is configured in the ou=common,o=company
nam is configured using that user, but I cant get the systems online

LDAP and eDirectory work, but NAM doesn't

what do I need to do to get nam working and hence nss etc??

Suggestions ??

Thanks in advance

Mark

================


in the test environment - namconfig -k worked with the
alternative-ldap-sever-list removed

I tried removing and reinstalling nam with
base-name = ou=TBCH,ou=WA,o=company in the test (isolated) environment

but the install failed


nam.conf (sanatized)

base-name=o=company
admin-fdn=cn=admincommon,ou=common,o=company
preferred-server=192.168.91.250
alternative-ldap-server-list=192.168.21.240,192.168.21.241
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
cache-only=no
persistent-search=no
case-sensitive=no
convert-lowercase=no
workstation-context=ou=TBCH,ou=WA,o=company