1.5 Upgrading eDirectory

IMPORTANT:Ensure that supported version of SSP is installed on eDirectory 873 SPx before upgrading to eDirectory 8.8 SP6.

  • For eDirectory 873 SP9, ensure that SSP 203 is installed.

  • For eDirectory 873 SP10, ensure that SSP 206 is installed.

NOTE:ndsconfig upgrade is used to upgrade the necessary configuration of the individual components such as HTTP, LDAP, SNMP, SAS, and NMAS. eDirectory database is upgraded to a new format if eDirectory versions prior to eDirectory 8.8 SP1 are upgraded to eDirectory 8.8 SP6.

1.5.1 Server Health Checks

With eDirectory 8.8, when you upgrade eDirectory, a server health check is conducted by default to ensure that the server is safe for the upgrade:

Based on the results obtained from the health checks, the upgrade will either continue or exit as follows:

  • If all the health checks are successful, the upgrade will continue.

  • If there are minor errors, the upgrade will prompt you to continue or exit.

  • If there are critical errors, the upgrade will exit.

See Section B.0, eDirectory Health Checks for a list of minor and critical error conditions.

Skipping Server Health Checks

To skip server health checks, use nds-install -j or ndsconfig upgrade -j.

For more information, see Section B.0, eDirectory Health Checks.

1.5.2 Upgrading on Linux Servers Other Than OES

If you have eDirectory 8.5.x or 8.6.x, you have to first upgrade to eDirectory 8.7.x and then upgrade to eDirectory 8.8.

To upgrade to eDirectory 8.8, use nds-install utility. this utility is located in the Setup directory of the downloaded file for Linux platform. Enter the following command from Setup directory:

./nds-install

After the upgrade to eDirectory 8.8, the default location of the configuration files, data files, and log files are changed to /etc/opt/novell/eDirectory/conf, /var/opt/novell/eDirectory/data, and /var/opt/novell/eDirectory/log respectively.

The new directory /var/opt/novell/eDirectory/data uses a symbolic link to the /var/nds directory.

The old configuration file /etc/nds.conf is migrated to /etc/opt/novell/eDirectory/conf directory. The old configuration file /etc/nds.conf and the old log files under /var/nds are retained for reference.

NOTE:Run "ndsconfig upgrade" after nds-install, if upgrade of the DIB fails and nds-install asks to do so.

NOTE:Health check fails due to time sync. To resolve this issue, perform a time sync between the instances. You can ignore this warning message during upgrade.

1.5.3 Unattended Upgrade of eDirectory on Unix

On UNIX platform , eDirectory provides switches and options along with the install script and configuration utility that facilitates the unattended upgrade. The following sections discuss various steps for unattended eDirectory upgrade on UNIX:

  1. Perform the health check of eDirectory:

    Health check of all the root instances planned for upgrade is manually done by using ndscheck utility.

    1. export LD_LIBRARY_PATH, SHLIB_PATH and LIBPATH to the <untarred location of eDirectory>/eDirectory/setup/utils

    2. Run ndscheck using one of the below commands:

      <untarred location of eDirectory>/eDirectory/setup/utils/ndscheck -a <user name> -w passwd --config-file <nds.conf with absolute path> 
      

      Passing the password through environment variable: <untarred location of 88SP6>/eDirectory/setup/utils/ndscheck -a <user name> -w env:<environment variable> --config-file <nds.conf with absolute path>

      Passing the password through file: <untarred location of 88SP6>/eDirectory/setup/utils/ndscheck -a <user name> -w file:<filname> --config-file <nds.conf with absolute path>

      Any one of the above can be used in the automated script for the health check. For example:

      /Builds/eDirectory/utils/ndscheck -a admin.novell -w n 
      /Builds/eDirectory/utils/ndscheck -a admin.novell -w env:ADM_PASWD 
      /Builds/eDirectory/utils/ndscheck -a admin.novell -w file:adm_paswd 
      
  2. Upgrade the eDirectory 8.8 packages:

    1. Run nds-install script to upgrade the packages as below:

      nds-install -u  -i -j  
      
  3. Update the following environment variables :

    PATH=/opt/novell/eDirectory/bin:/opt/novell/eDirectory/sbin:$PATH 
    LD_LIBRARY_PATH=/opt/novell/eDirectory/lib:/opt/novell/eDirectory/lib/nds-modules:/opt/novell/lib:$LD_LIBRARY_PATH 
    MANPATH=/opt/novell/man:/opt/novell/eDirectory/man:$MANPATH 
    TEXTDOMAINDIR=/opt/novell/eDirectory/share/locale
    
  4. Upgrade eDirectory by using the ndsconfig utility for all the root instances by using the following commands:

    ndsconfig upgrade -a <user name> -w passwd -c --config-file <nds.conf with absolute path> 
    

    Passing the password through environment variable: ndsconfig upgrade -a <user name> -w env:<environment variable> -c --config-file <nds.conf with absolute path>

    Passing the password through file: ndsconfig upgrade -a <user name> -w file:<filename with absolute/relative path> -c --config-file <nds.conf with absolute path>

    Any of the above can be used in the automated script for the eDirectory upgrade. For example:

    ndsconfig upgrade -a admin.novell -w n -c -–config-file /etc/opt/novell/eDirectory/conf/nds.conf 
    
    ndsconfig upgrade -a admin.novell -w env:ADM_PASWD -c --config-file /etc/opt/novell/eDirectory/conf/nds.conf 
    
    ndsconfig upgrade -a admin.novell -w file:/Builds/88SP6/adm_paswd -c --config-file /etc/opt/novell/eDirectory/conf/nds.conf
    

1.5.4 Upgrading eDirectory on Existing OES

For more information on upgrading eDirectory on existing OES, refer to the OES Linux Installation Guide.

1.5.5 Upgrading eDirectory During OES 1.0 to OES 2.0 Upgrade

eDirectory should be upgraded when OES upgrades from OES 1.0 to OES 2.0. For more information on OES upgrade, refer to OES Linux Installation Guide.

Perform the following checks before upgrading the OES or eDirectory server:

  • eDirectory Health Check

    Ensure that eDirectory health status is normal using the procedures specified in Section B.0, eDirectory Health Checks. You can use the applicable tools for verification:

    • Use iMonitor for eDirectory version prior to 8.8, see Using Novell iMonitor 2.4 from Novell eDirectory 8.8 Administration Guide.

    • Use ndscheck utility for eDirectory version 8.8 or later, see General Utilities from Novell eDirectory 8.8 Administration Guide.

  • Disk Space Check

    For eDirectory version prior to 8.8 SP1, ensure disk space available on the file system that holds the DIB atleast equals the DIB size. For example, if the DIB size is 100 MB, the available disk space should not be less than 100 MB.

If the eDirectory health status is not normal or an error is detected, refer to the Section B.5, Log Files.

1.5.6 Upgrading the Tarball Deployment of eDirectory 8.8

If you want to upgrade the Tarball deployment from eDirectory 8.8 to eDirectory 8.8 SP6, perform the following steps:

  1. Download the tarball build.

  2. Take backup of the following configuration files:

    • $NDSHOME/eDirectory/etc/opt/novell/eDirectory/conf/ndsimon.conf

    • $NDSHOME/eDirectory/etc/opt/novell/eDirectory/conf/ice.conf

    • $NDSHOME/eDirectory/etc/opt/novell/eDirectory/conf/ndsimonhealth.conf

    • $NDSHOME/eDirectory/etc/opt/novell/eDirectory/conf/ndssnmp/ndssnmp.cfg

    • $NDSHOME is the location where eDirectory is installed.

  3. For upgrade of eDirectory versions lower than 8.8 SP1, do the following:

    • Perform disk space check using ndscheck -D --config-file conf_file_path

    • Create an empty file upgradeDIB under the DIB location of each server instance.

      The list of instances can be obtained using the ndsmanage utility.

  4. Run pre upgrade health check for the all instances using ndscheck and check the ndscheck.log file for any errors before proceeding with the upgrade.

  5. Stop all instances using ndsmanage.

  6. Untar the tarball in the same location ($NDSHOME) where eDirectory is installed. By untaring the tarball in the same location, you are overwriting the binaries and libraries.

  7. Upgrade the following packages if necessary.

    Platform

    Command

    Packages

    Linux 32-bit

    • rpm -Uvh <rpm name>

    • novell-NOVLsubag-8.8.6-1.i586.rpm

    • novell-NDSslp-8.8.2-1.i386.rpm

    • nici-2.7.0-0.01.i386.rpm

    • novell-NDSslp-8.8-1.i386.rpm

    Linux 64-bit

     

    • novell-NOVLsubag-8.8.6-1.x86_64.rpm

    • nici64-2.7.6-0.01.x86_64.rpm

      NOTE:For more information on installing 32 and 64-bit NICI, refer to the Installing NICI.

    Solaris 32-bit

    • Remove the older version using "pkgrm <pkg name>

    • Install new version using "pkgadd -d <pkg name>"

    • NOVLsubag.pkg

    • NOVLniu0.pkg

    • NDSslp.pkg

    Solaris 64-bit

     

    • NOVLsubagx.pkg

    • NOVLniu64.pkg

    AIX

    • installp -acgXd <pkg name with full path> <pkg name> all

    • NDS.NOVLsubag.8.8.6.0

    • NOVLniu0.2.7.6.0

    • NDS.NDSslp.8.8.2.0

  8. Restore the configuration files.

  9. Run the $NDSHOME/eDirectory/opt/novell/eDirectory/bin/ndspath for setting all environment variables.

  10. Run ndsconfig upgrade -j for all instances. While running ndsconfig upgrade follow the order in which the master replica is the first and followed by Read/Write and others.

1.5.7 Upgrading Multiple Instances

This section contains the following information:

Root User has Multiple Instances

If you run nds-install after upgrading the package, it prompts you to upgrade the DIB files of all the eDirectory server instances, which might take a long time to complete. If you wish to perform the DIB upgrade parallely, you can do it manually (Refer to the eDirectory Readme). If you select to upgrade the DIB for all the active instances one by one, it runs the ndsconfig upgrade command for all the instances one by one. In case of larger DIBs, you can select No and run ndsconfig upgrade parallely in separate shells, which can reduce the upgrade time of each instance.

Non Root User's Instances

If you have non root user's instances which are using root user's binaries, before doing the package upgrade you need to run “ndscheck” for such instances and make sure that their health is proper by referring the ndscheck.log file. If you run nds-install, it stops all the instances including the non root user's instances. After doing the package upgrade, the nds-install command does not call ndsconfig upgrade for non root user's instances. You need to manually run ndsconfig upgrade for all non root user's instances to start these instances.

Order of Upgrade

While running ndsconfig upgrade, it is recommended to follow the order in which master replica comes first and then Read/Write or other replicas.

1.5.8 Disk Space Check on Upgrading to eDirectory 8.8 SP6

When eDirectory server is upgraded from previous versions to eDirectory 8.8 SP6, the disk space check for the DIB upgrade would be performed. The free disk space necessary in the file system, where the DIB resides would be equal to that of the DIB size. The messages of the disk space check would be updated in the ndscheck.log located in the instance's specific log directory. For default instance, /var/opt/novell/eDirectory/log/ndscheck.log.

NOTE:The disk space check is required only during the DIB upgrade process. For more information, refer to Section 6.0, Upgrade Requirements of eDirectory 8.8.