Why is eDirectory listed as not configured after upgrading from OES2sp2 to OES2sp3 or OES11?

The upgrade from OES2sp2 to OES2sp3 occurred without a problem.  After rebooting the server, all was working as expected.  However, when trying to install a new product that relied on eDirectory, like "Novell CIFS", you're prompted that eDirectory is not configured and then walked through configuring eDirectory.

The best solution is to verify that CONFIG_EDIR_REPLICA_SERVER , in /etc/sysconfig/novell/edir2_sp2, is pointing to the IP address of a valid replica holder BEFORE upgrading to OES2SP3 or OES11.  (Note: Section 5.6.1 Prerequisites of the OES11 documentation requires this information to be verified before upgrading).

There was a problem with the OES2sp2 installation such that in the /etc/sysconfig/novell/edir2_sp2 file, the value for
    CONFIG_EDIR_REPLICA_SERVER
was set to "" instead of set to the IP address of a replica holder.

If you have already upgraded to OES2sp3, you can remedy the situation by updating /etc/sysconfig/novell/edir2_sp3 -- ensuring that the following values are set properly.  The can/are broken into 2 categories:

Parameters that will need to be changed
Here is what you will likely see in edir2_sp3.  They should be changed to the values in edir2_sp2:

Parameters that may need to be updates (optional)
Depending on the NMAS methods utilized in the tree, you should insure that the CONFIG_EDIR_NMAS* parameters are the same in edir2_sp3 with edir2_sp2.  Some example parameters & values you may see in the edir2_sp3 are: