Are there supposed to be eDir objects representing the _Admin objects for an
OES2 Linux server? I do not see any of them in my tree, yet on the servers
themselves the _ADMIN volume shows as "Active". Running a "novell-nss
status" on each of the servers in question tells me that the NSS admin
volume is running.

I may be barking up the wrong tree, but I am unable to create a DFS
management context on any of my OES2 Linux servers. I have four new
OES2 Linux servers I am going to use (one is a XEN VM). The first attempt
results in the following message selecting "SLC.MHTN" as the context and
"sebek.SLC.MHTN" as the replica site:

"sebek.SLC.MHTN: Could not add the replica site to the new management
context. -601 - eDirectory Error - Object does not exist."

Second attempt using "SLC.MHTN" as the context and "montu.SLC.MHTN" as the
replica site:

"montu.SLC.MHTN: Could not create the new management context. This user does
not have the correct credentials to authenticate to the CIMOM client."

The third attempt using "SLC.MHTN" as the context and "ptah.SLC.MHTN" as the
replica site:

"ptah.SLC.MHTN: Could not create the new management context. This user does
not have the correct credentials to authenticate to the CIMOM client."

There are NSS volumes present and mounted. In looking around I notice that
the "_admin" volumes are not appearing.

If the "_admin volumes need to be in eDir, how do I create them and make
them functional?

I don't understand the "eDirectory Error - Object does not exist." message,
since I selected the server object from within eDir in the first place.
What can I do to resolve this?

Where do I find the correct credentials for the CIMON client?