NetIQ edirectory 8.8 SP8 Installation Guide

Transcription

1 NetIQ edirectory 8.8 SP8 Installation Guide December

2 Legal Notice THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non-dod acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement NetIQ Corporation and its affiliates. All Rights Reserved. For information about NetIQ trademarks, see

3 Contents About this Book and the Library 7 About NetIQ Corporation 9 1 Install and Upgrade Features Multiple Package Formats for Installing edirectory 8.8 SP Installing edirectory 8.8 in a Custom Location Specifying a Custom Location for Application Files Specifying a Custom Location for Data Files Specifying a Custom Location for Configuration Files Non-root Install Standards Compliance FHS Compliance LSB Compliance Server Health Checks Need for Health Checks What Makes a Server Healthy? Performing Health Checks Types of Health Checks Categorization of Health Log Files SecretStore Integration with edirectory edirectory Instrumentation Installation For More Information Installing or Upgrading NetIQ edirectory on Linux System Requirements Prerequisites Hardware Requirements Forcing the Backlink Process to Run Upgrading edirectory Server Health Checks Upgrading on Linux Servers Other Than OES Unattended Upgrade of edirectory on Linux Upgrading edirectory on Existing OES Upgrading the Tarball Deployment of edirectory Upgrading Multiple Instances Installing edirectory Using SLP with edirectory Using the nds-install Utility to Install edirectory Components Installing edirectory 8.8 as a Non-root User Using the ndsconfig Utility to Add or Remove the edirectory Replica Server Using ndsconfig to Configure Multiple Instances of edirectory Using ndsconfig to Install a Linux Server into a Tree with Dotted Name Containers Using the nmasinst Utility to Configure NMAS Non-root user SNMP configuration Installing or Upgrading NetIQ edirectory on Windows System Requirements Contents 3

4 3.2 Prerequisites Hardware Requirements Forcing the Backlink Process to Run Disk Space Check on Upgrading to edirectory SP8 or later Installing NetIQ edirectory on Windows Installing or Updating NetIQ edirectory 8.8 on a Windows Server Server Health Checks Communicating with edirectory through LDAP Installing NMAS Server Software Installing NMAS Client Software Installing into a Tree with Dotted Name Containers Unattended Install and Configure to edirectory 8.8 SP8 on Windows Installing edirectory on Linux and Windows with IPv6 Addresses Configuring edirectory on Linux with IPv Creating a New edirectory Tree Adding a Server to an Existing edirectory Tree Enabling IPv6 Addresses on Existing or Upgraded edirectory Servers Adding LDAP URLS for IPV6 on the LDAP Server Object Installing or Upgrading edirectory on Windows with IPv Enabling IPv6 While Installing or Upgrading edirectory Enabling IPv6 for Existing Servers Accessing imonitor Relocating the DIB Linux Windows Upgrade Requirements of edirectory Reference Changes in 8.8 SP1 or Later Versions Upgrade Process in 8.8 SP Performing a Dry Run before Upgrading edirectory Common Problems Encountered during the Upgrade Process Configuring NetIQ edirectory on Linux Configuration Utilities The ndsconfig Utility Using LDAP Tools to Configure the LDAP Server and LDAP Group Objects Using the nmasinst Utility to Configure NetIQ Modular Authentication Service Customizing edirectory Configuration Parameters Security Considerations Migrating to edirectory 8.8 SP Migrating to edirectory 8.8 SP8 While Upgrading the Operating System Migrating to edirectory 8.8 SP8 Without Upgrading the Operating System Migrating edirectory from NetWare to OES 2 Linux Planning Your Migration System Requirements NetIQ edirectory 8.8 SP8 Installation Guide

5 9.1.2 Prerequisites Supported Platforms Considerations Migration Tools Migration Procedure After the Migration Deploying edirectory on High Availability Clusters Clustering edirectory Services on Linux Prerequisites Installing and Configuring edirectory Configuring SNMP Server in Clustered Linux Environments Clustering edirectory Services on Windows Prerequisites Installing and Configuring edirectory Configuring SNMP Server in Clustered Windows Environments Troubleshooting Clustered Environments Repairing or Upgrading edirectory on Clustered Nodes Creating Windows Registry Keys Configuration Utility Options Uninstalling NetIQ edirectory Uninstalling edirectory on Windows Uninstalling edirectory Unattended Uninstallation of edirectory Uninstalling NICI Uninstalling Microsoft Visual C and Visual C Runtime Libraries Uninstalling edirectory on Linux Unattended Uninstallation of edirectory on Linux Caveats for Uninstalling edirectory A Linux Packages for NetIQ edirectory 113 B edirectory Health Checks 117 B.1 Need for Health Checks B.2 Performing Health Checks B.2.1 With the Upgrade B.2.2 As a Standalone Utility B.3 Types of Health Checks B.3.1 Basic Server Health B.3.2 Partitions and Replica Health B.4 Categorization of Health B.4.1 Normal B.4.2 Warning B.4.3 Critical B.5 Log Files C Configuring OpenSLP for edirectory 121 C.1 Service Location Protocol C.2 SLP Fundamentals C.2.1 NetIQ Service Location Providers C.2.2 User Agents Contents 5

6 C.2.3 Service Agents C.3 Configuration Parameters NetIQ edirectory 8.8 SP8 Installation Guide

7 About this Book and the Library The Installation Guide describes how to install edirectory 8.8. It is intended for network administrators. For the most recent version of the NetIQ edirectory 8.8 SP8 Installation Guide, see the NetIQ edirectory 8.8 online documentation ( Web site. Intended Audience The guide is intended for network administrators. Other Information in the Library The library provides the following information resources: XDASv2 Administration Guide Describes how to configure and use XDASv2 to audit edirectory and NetIQ Identity Manager. Administration Guide Describes how to manage and configure edirectory. What s New Guide Describes the new features of edirectory. Troubleshooting Guide Describes how to resolve edirectory issues. Tuning Guide for Linux Platforms Describes how to analyze and tune edirectory on Linux platforms to yield superior performance in all deployments. These guides are available at the NetIQ edirectory 8.8 documentation Web site ( For information about the edirectory management utility, see the NetIQ imanager 2.7 Administration Guide ( About this Book and the Library 7

8 8 NetIQ edirectory 8.8 SP8 Installation Guide

9 About NetIQ Corporation We are a global, enterprise software company, with a focus on the three persistent challenges in your environment: Change, complexity and risk and how we can help you control them. Our Viewpoint Adapting to change and managing complexity and risk are nothing new In fact, of all the challenges you face, these are perhaps the most prominent variables that deny you the control you need to securely measure, monitor, and manage your physical, virtual, and cloud computing environments. Enabling critical business services, better and faster We believe that providing as much control as possible to IT organizations is the only way to enable timelier and cost effective delivery of services. Persistent pressures like change and complexity will only continue to increase as organizations continue to change and the technologies needed to manage them become inherently more complex. Our Philosophy Selling intelligent solutions, not just software In order to provide reliable control, we first make sure we understand the real-world scenarios in which IT organizations like yours operate day in and day out. That's the only way we can develop practical, intelligent IT solutions that successfully yield proven, measurable results. And that's so much more rewarding than simply selling software. Driving your success is our passion We place your success at the heart of how we do business. From product inception to deployment, we understand that you need IT solutions that work well and integrate seamlessly with your existing investments; you need ongoing support and training post-deployment; and you need someone that is truly easy to work with for a change. Ultimately, when you succeed, we all succeed. Our Solutions Identity & Access Governance Access Management Security Management Systems & Application Management Workload Management Service Management About NetIQ Corporation 9

10 Contacting Sales Support For questions about products, pricing, and capabilities, contact your local partner. If you cannot contact your partner, contact our Sales Support team. Worldwide: United States and Canada: Web Site: Contacting Technical Support For specific product issues, contact our Technical Support team. Worldwide: North and South America: Europe, Middle East, and Africa: +353 (0) Web Site: Contacting Documentation Support Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, click Add Comment at the bottom of any page in the HTML versions of the documentation posted at You can also Documentation- We value your input and look forward to hearing from you. Contacting the Online User Community Qmunity, the NetIQ online community, is a collaborative network connecting you to your peers and NetIQ experts. By providing more immediate information, useful links to helpful resources, and access to NetIQ experts, Qmunity helps ensure you are mastering the knowledge you need to realize the full potential of IT investments upon which you rely. For more information, visit community.netiq.com. 10 NetIQ edirectory 8.8 SP8 Installation Guide

11 1 1Install and Upgrade Features This chapter discusses the features of NetIQ edirectory 8.8 installation and upgrade. The following table lists the new features and specifies the platforms they are supported on. Feature Linux Windows Multiple package formats for installing edirectory 8.8 Custom location install for application files Custom location install for data files Custom location install for configuration files Non-root install Improved support for installations on high availability clusters FHS compliance LSB compliance Server health checks SecretStore integration edirectory Instrumentation Installation This chapter includes the following information: Section 1.1, Multiple Package Formats for Installing edirectory 8.8 SP 8, on page 11 Section 1.2, Installing edirectory 8.8 in a Custom Location, on page 12 Section 1.3, Non-root Install, on page 14 Section 1.4, Standards Compliance, on page 14 Section 1.5, Server Health Checks, on page 15 Section 1.6, SecretStore Integration with edirectory, on page 19 Section 1.7, edirectory Instrumentation Installation, on page 20 Section 1.8, For More Information, on page Multiple Package Formats for Installing edirectory 8.8 SP 8 On Linux, you have an option to choose from various file formats while installing edirectory 8.8 on your host. The file formats are listed in the table below. Install and Upgrade Features 11

12 Type of User and Installation Location Linux Root user Default location Custom location RPM Tarball Non-root user Custom location Tarball For more information on installing using tarballs, refer to Section 2.5.5, Upgrading the Tarball Deployment of edirectory 8.8, on page Installing edirectory 8.8 in a Custom Location edirectory 8.8 gives you the flexibility to install the application, data, and configuration files in a location of your choice. One of the scenarios for installing edirectory 8.8 in a custom location is when you already have an earlier version of edirectory installed on your host and you want to test edirectory 8.8 before upgrading to it. This way, you can have your existing edirectory setup undisturbed and also test this new version. You can then decide whether you want to retain your existing version or want to upgrade to edirectory 8.8. NOTE: SLP and the SNMP subagent are installed in the default locations. This section explains how to install the various files in a custom location: Section 1.2.1, Specifying a Custom Location for Application Files, on page 12 Section 1.2.2, Specifying a Custom Location for Data Files, on page 13 Section 1.2.3, Specifying a Custom Location for Configuration Files, on page Specifying a Custom Location for Application Files While installing edirectory, you can install your application files in a location of your choice. Linux To install edirectory 8.8 in a custom location, you can use the tarball installation file and untar edirectory 8.8 in a location of your choice. Windows You were able to specify a custom location for the application files during the installation Wizard even prior to edirectory NetIQ edirectory 8.8 SP8 Installation Guide

13 1.2.2 Specifying a Custom Location for Data Files While configuring edirectory, you can save the data files in a location of your choice. The data files include the data, dib, and log directories. Linux To configure the data files in a custom location, you can use either the -d or -D option of the ndsconfig utility. Option Description -d custom_location Creates the DIB (the edirectory database) directory in the path mentioned. NOTE: This option was present prior to edirectory 8.8 also. -D custom_location Creates the data (contains data such as the pids and socket IDs), dib, and log directories in the path mentioned. Windows On Windows you would be prompted to enter the DIB path during the installation. Enter a path of your choice Specifying a Custom Location for Configuration Files While configuring edirectory, you can select the path where you want to save your configuration files. Linux To configure the nds.conf configuration file to a different location, use the --config-file option of the ndsconfig utility. To install the other configuration files (such as modules.conf, ndsimon.conf, and ice.conf) to a different location, do the following: 1 Copy all the configuration files to the new location. 2 Set the new location by entering the following: ndsconfig set n4u.nds.configdir custom_location Windows You cannot specify a custom location for the configuration files on Windows. Install and Upgrade Features 13

14 1.3 Non-root Install edirectory 8.8 and higher supports installation and configuration of edirectory servers by a non-root user. Earlier versions of edirectory could be installed and configured only by a root user with only a single instance of edirectory running on a host. With edirectory 8.8 or higher, any non-root user can use a tarball build to install edirectory. There can be multiple instances of edirectory binary installs by the same or different users. However, even for non-root user installs, the system-level services such as the Novell International Cryptographic Infrastructure (NICI), SNMP and SLP can be installed only with the root privileges. NICI is a mandatory component, and SNMP and SLP are optional components for edirectory functionality. Also, with a package install, only a single instance can be installed by the root user. After the install, a non-root user can configure edirectory server instances using his or her individual tarball installation, or by using a binary installation. This means that there can be multiple instances of edirectory servers running on a single host because any user, either root or non-root, can configure different edirectory server instances on a single host by using either a package or tarball installation. For more details on the Multiple Instances feature, see Section 2.5.6, Upgrading Multiple Instances, on page 28. Non-root installation and configuration is applicable to Linux platforms only. For more information on non-root installation and configuration, see Section 2.6.3, Installing edirectory 8.8 as a Non-root User, on page Standards Compliance edirectory 8.8 is compliant with the following standards: Section 1.4.1, FHS Compliance, on page 14 Section 1.4.2, LSB Compliance, on page FHS Compliance To avoid file conflicts with other product application files, edirectory 8.8 follows the Filesystem Hierarchy Standard (FHS). This feature is available only on Linux. edirectory follows this directory structure only if you have chosen to install it in the default location. If you have chosen a custom location, the directory structure would be custom_location/default_path. For example, if you choose to install in the edir88 directory, the same directory structure would be followed in the edir88 directory, like the man pages would be installed in the /edir88/opt/novell/ man directory. The following table lists the change in the directory structure: Types of Files Stored in the Directory Executable binaries and static shell scripts Executable binaries for root use Static or dynamic library binaries Configuration files Read/Write, run-time dynamic data like the DIB Directory Name and Path /opt/novell/edirectory/bin /opt/novell/edirectory/sbin /opt/novell/edirectory/lib /etc/opt/novell/edirectory/conf /var/opt/novell/edirectory/data 14 NetIQ edirectory 8.8 SP8 Installation Guide

15 Types of Files Stored in the Directory Log files Linux man pages Directory Name and Path /var/opt/novell/edirectory/log /opt/novell/man Export Environmental Variables With the FHS implementation in edirectory 8.8, you need to update the path environmental variables and export them. This creates the following problems: You need to remember all the paths exported, so that whenever you open a shell, you need to export these paths and start using the utilities. When you want to use more than one set of binary, you have to open more than one shell or have to unset and set the paths to the different set of binaries frequently. To resolve the above issue, you can use the /opt/novell/edirectory/bin/ndspath script as follows: Prefix the ndspath script to the utility and run the utility you want as follows: custom_location/opt/novell/edirectory/bin/ndspath utility_name_with_parameters Export the paths in the current shell as follows:. custom_location/opt/novell/edirectory/bin/ndspath After entering the above command, run the utilities as you would normally do. Call the script in your profile, bashrc, or similar scripts. Therefore, whenever you log in or open a new shell, you can start using the utilities directly LSB Compliance edirectory 8.8 is now Linux Standard Base (LSB) compliant. LSB also recommends FHS compliance. All the edirectory packages in Linux are prefixed with novell. For example, NDSserv is now novell- NDSserv. 1.5 Server Health Checks NetIQ edirectory includes server health checks that help you determine whether your server health is safe before upgrading. The server health checks run by default with every upgrade and occur before the actual package upgrade. However, you can also run the diagnostic tool ndscheck to do the health checks. For more information about performing routine health check procedures, see Maintaining NetIQ edirectory in the NetIQ edirectory 8.8 SP8 Administration Guide ( documentation/edir88/edir88/data/bookinfo.html) Install and Upgrade Features 15

16 1.5.1 Need for Health Checks In earlier releases of edirectory, the upgrade did not check the health of the server before proceeding with the upgrade. If the heath was unstable, the upgrade operation would fail and edirectory would be in an inconsistent state. In some cases, you probably could not roll back to the pre-upgrade settings. This new health check tool resolves this, letting you to ensure that your server is ready to upgrade What Makes a Server Healthy? The server health check utility performs certain health checks to ensure that the tree is healthy. The tree is declared healthy when all these health checks are completed successfully Performing Health Checks You can perform server health checks in two ways: With the Upgrade on page 16 As a Standalone Utility on page 16 NOTE: You need administrative rights to run the health check utility. The minimal right that can be set to run the utility is the Public right. However, with the Public right some of the NetWare Core Protocol (NCP) objects and partition information are not available. With the Upgrade The health checks are run by default every time you upgrade edirectory. Linux Every time you upgrade, the health checks are run by default before the actual upgrade operation starts. To skip the default health checks, you can use the -j option with the nds-install utility. Windows The server health checks happen as part of the installation wizard. You can enable or disable the health checks when prompted to do so. As a Standalone Utility You can run the server health checks as a standalone utility any time you want. The following table explains the health check utilities. 16 NetIQ edirectory 8.8 SP8 Installation Guide

17 Table 1-1 Health Check Utilities Platform Linux Utility Name ndscheck Syntax: ndscheck -h hostname:port -a admin_fdn -F logfile_path --config-file configuration_file_name_and_path NOTE: You can specify either -h or --config-file, but not both options. Windows ndscheck Types of Health Checks When you upgrade or run the ndscheck utility, the following types of health checks are done: Basic Server Health Partitions and Replica Health If you run the ndscheck utility, the results from the health checks are displayed on the screen and logged in to ndscheck.log. For more information on log files, refer to Section 1.5.6, Log Files, on page 18. If the health checks are done as part of the upgrade, then after the health checks, based on the criticality of the error, either you are prompted to continue the upgrade process or the process is aborted. The details of the errors are described in Section 1.5.5, Categorization of Health, on page 18. Basic Server Health This is the first stage of the health check.the health check utility checks for the following: 1. The edirectory service is up. The DIB is open and able to read some basic tree information such as the tree name. 2. The server is listening on the respective port numbers. For LDAP, it gets the TCP and the SSL port numbers and checks if the server is listening on these ports. Similarly, it gets the HTTP and HTTP secure port numbers and checks if the server is listening on these ports. Partitions and Replica Health After checking the basic server health, the next step is to check the partitions and replica health as follows: 1. Checks the health of the replicas of the locally held partitions. Install and Upgrade Features 17

18 2. Reads the replica ring of each and every partition held by the server and checks whether all servers in the replica ring are up and all the replicas are in the ON state. 3. Checks the time synchronization of all the servers in the replica ring. This shows the time difference between the servers Categorization of Health Based on the errors found while checking the health of a server, there can be the three categories of health. The status of the health checks is logged in to a log file. For more information, refer to Section 1.5.6, Log Files, on page 18. The three categories of health Normal, Warning, and Critical. Normal The server health is normal when all the health checks were successful. The upgrade proceeds without interruption. Warning The server health is in the warning category when minor errors are found while checking the health. If the health check is run as part of the upgrade, you are prompted to either abort or continue. Warnings normally occur in the following scenarios: 1. Server not listening on LDAP and HTTP ports, either normal or secure or both. 2. Unable to contact any of the nonmaster servers in the replica ring. 3. Servers in the replica ring are not in sync. Critical The server health is critical when critical errors were found while checking the health. If the health check is run as part of the upgrade, the upgrade operation is aborted. The critical state normally occurs in the following cases: 1. Unable to read or open the DIB. The DIB might be locked or corrupt. 2. Unable to contact all the servers in the replica ring. 3. Locally held partitions are busy. 4. Replica is not in the ON state Log Files Every server health check operation, whether it is run with the upgrade or as a standalone utility, maintains the status of the health in a log file. The content of the log file is similar to the messages displayed on the screen when the checks are happening. 18 NetIQ edirectory 8.8 SP8 Installation Guide

19 The health check log file contains the following: Status of the health checks (normal, warning, or critical). URLs to the NetIQ support site. The following table gives you the locations for the log file on the various platforms: Table 1-2 Health Check Log File Locations Platform Log File Name Log File Location Linux ndscheck.log Depends on the location you specified with the ndscheck -F utility. If you did not use the -F option, the location of the ndscheck.log file is determined by the other options you used at the ndscheck command line as follows: Windows ndscheck.log install_directory 1. If you used the -h option, the ndscheck.log file is saved in the user s home directory. 2. If you used the --config-file option, the ndscheck.log file is saved in the server instance s log directory. You can also select an instance from the multiple instances list. 1.6 SecretStore Integration with edirectory edirectory 8.8 gives you an option to configure Novell SecretStore 3.4 during edirectory configuration. Prior to edirectory 8.8, you had to manually install SecretStore. SecretStore is a simple and secure password management solution. It enables you to use a single authentication to edirectory to access most Linux, Windows, Web, and mainframe applications. After you've authenticated to edirectory, SecretStore-enabled applications store and retrieve the appropriate login credentials. When you use SecretStore, you eliminate the need to remember or synchronize all the multiple passwords required for accessing password-protected applications, Web sites, and mainframes. To configure SecretStore 3.4 along with edirectory, you can do the following: Linux: Use the ndsconfig add -m ss parameter. Here, ss denotes SecretStore and is an optional parameter. If you do not mention the module name, all the modules are installed. If you do not want to configure SecretStore, you can pass the no_ss value to this option by specifying -m no_ss. Windows: While installing edirectory, there is an option to specify whether to configure the SecretStore module. By default, this option is selected. Install and Upgrade Features 19

20 For more information on the SecretStore usage, refer to the Novell SecretStore 3.4 Administration Guide ( 1.7 edirectory Instrumentation Installation Earlier edirectory Instrumentation was a part of Novell Audit. From edirectory 8.8 SP3 version onwards, edirectory Instrumentation must be installed separately. For detailed information on installing, configuring, and uninstalling edirectory Instrumentation, see Auditing edirectory Events in the NetIQ edirectory 8.8 SP8 Administration Guide ( For More Information For more information on any of the features discussed in this chapter, see the following documentation: NetIQ edirectory 8.8 SP8 Administration Guide On Linux: nds-install, ndsconfig, and ndscheck man pages 20 NetIQ edirectory 8.8 SP8 Installation Guide

21 2 2Installing or Upgrading NetIQ edirectory on Linux Use the following information to install or upgrade NetIQ edirectory 8.8 on a Linux server: Section 2.1, System Requirements, on page 21 Section 2.2, Prerequisites, on page 22 Section 2.3, Hardware Requirements, on page 24 Section 2.4, Forcing the Backlink Process to Run, on page 24 Section 2.5, Upgrading edirectory, on page 24 Section 2.6, Installing edirectory, on page System Requirements You must install edirectory on one of the following 64-bit platforms. SLES 11 SP1, SP2, and SP3 SLES 10 SP4 SLES 12 RHEL 5.10, 5.9, 5.8, and 5.7 RHEL 6.5, 6.4, 6.3, and 6.2 RHEL 7 You can run these operating systems in a virtual mode on the following hypervisors: VMware ESXi Xen (on SLES 10, SLES 11, and their Support Packs) NOTE: edirectory 8.8 SP8 is supported on SLES 10 XEN virtualization service that runs the SLES 10 guest OS. The following updates are available at the Novell Update Web site ( update.novell.com): SUSE-Linux-Enterprise-Server-X86_ SLES10-Updates For registering and updating SUSE Linux Enterprise 10, refer to Registering SUSE Linux Enterprise with the NetIQ Customer Center ( After installing the latest update, ensure that the minimum patch level of the installed update is 3.0.2_ Windows Server 2008 R2 Virtualization with Hyper-V KVM Hypervisor (on RHEL 6.4) To determine the version of SUSE Linux you are running, see the /etc/suse-release file. Installing or Upgrading NetIQ edirectory on Linux 21

22 Ensure that the latest glibc patches are applied from Red Hat Errata ( on Red Hat systems. The minimum required version of the glibc library is version 2.4. edirectory also requires the following: A minimum of 1 GB RAM for edirectory 300 MB of disk space for the edirectory server 150 MB of disk space for every 50,000 users 2.2 Prerequisites IMPORTANT: Check the currently installed NetIQ and Third Party applications to determine if those products are supported on edirectory 8.8 before upgrading your existing edirectory environment. The prerequisites for other NetIQ products can be found on the NetIQ Documentation site ( We also recommend you back up an edirectory instance before performing any upgrades on that instance. (Conditional) Novell International Cryptographic Infrastructure (NICI) 2.7 and edirectory 8.8 support key sizes up to 4096 bits. If you want to use a 4 KB key size, every server must be upgraded to edirectory 8.8. In addition, every workstation using the management utilities, for example, imanager must have NICI 2.7 installed on it. When you upgrade your Certificate Authority (CA) server to edirectory 8.8, the key size will not change but will still be 2 KB. The only way to create a 4 KB key size is recreate the CA on an edirectory 8.8 server. In addition, you would have to change the default from 2 KB to 4 KB for the key size, during the CA creation. When you install edirectory, the nds-install utility automatically installs NICI. For more information about installing edirectory, see Section 2.6.2, Using the nds-install Utility to Install edirectory Components, on page 30. However, if you need to install only NICI, and not edirectory itself, on a workstation that has the management utilities installed, you must install NICI manually. For more information about manually installing NICI, see Installing NICI on page 33. Service Location Protocol (SLP) installed and configured With edirectory 8.8, SLP does not get installed as part of the edirectory installation. Only a root user can install SLP. For more information on installing SLP, refer to Using SLP with edirectory on page 29. The Linux host enabled for multicast routing To check if the host is enabled for multicast routing, enter the following command: /bin/netstat -nr The following entry should be present in the routing table: If the entry is not present, log in as root and enter the following command to enable multicast routing: route add -net netmask dev interface The interface could be a value such as eth0, hme0, hme1, or hme2, depending on the NIC that is installed and used. 22 NetIQ edirectory 8.8 SP8 Installation Guide

23 For more information on multicast and broadcast routes, refer to the OpenSLP Web site ( Network server time synchronized Use Network Time Protocol's (NTP) ntp to synchronize time across all network servers. (Conditional) If you are installing a secondary server, all the replicas in the partition that you install the product on should be in the On state. (Conditional) If you are installing a secondary server into an existing tree as a non-administrator user, create a container and then partition it. Ensure that you have the following rights: Supervisor rights to this partition. All Attributes rights: read, compare, and write rights over the W0.KAP.Security object. Entry rights: browse rights over Security container object. All Attributes rights: read and compare rights over Security container object. (Conditional) If you are installing a secondary server into an existing tree as a non-administrator user, ensure that at least one of the servers in the tree has the same or higher edirectory version as that of the secondary being added as container admin. In case the secondary being added is of later version, then the schema needs to be extended by the administrator of the tree before adding the secondary using container admin. While configuring edirectory, you must enable SLP services and a NetWare Core Protocol (NCP) port (the default is 524) in the firewall to allow the secondary server addition. Additionally, you can enable the following service ports based on your requirements: LDAP clear text LDAP secured HTTP clear text HTTP secured In case, if you have enabled user-defined ports, you must mention these ports while configuring edirectory. NOTE: This step is required only if you have SLP configured in your system. Do not set the user-defined ports to 8008 and 8010 while upgrading edirectory 8.8 SP2 or later versions to 8.8 SP8. If the ports are set to 8008 or 8010, ndsconfig assumes that the server is a pre-edirectory 8.8x server and automatically resets them to 8028 and 8030 respectively. During edirectory upgrade, if SecretStore has not already been configured with the previous versions, or you do not want to configure SecretStore, use the -m no_ss option with the ndsinstall utility. Configuring Static IP Address Static IP address must be configured on the server for the edirectory to perform efficiently. Configuring edirectory on the servers with DHCP address can lead to unpredictable results. Installing or Upgrading NetIQ edirectory on Linux 23

24 2.3 Hardware Requirements Hardware requirements depend on the specific implementation of edirectory. Two factors increase performance: more cache memory and faster processors. For best results, cache as much of the Directory Information Base (DIB) Set as the hardware allows. edirectory scales well on a single processor. However, NetIQ edirectory 8.8 takes advantage of multiple processors. Adding processors improves performance in some areas for example, logins and having multiple threads active on multiple processors also improves performance. edirectory itself is not processor intensive, but it is I/O intensive. The following table illustrates typical system requirements for edirectory for Linux: Objects Memory Hard Disk 100, GB 300 MB 1 million 4 GB 1.5 GB 10 million 4+ GB 15 GB 2.4 Forcing the Backlink Process to Run Because the internal edirectory identifiers change when upgrading to NetIQ edirectory, the backlink process must update backlinked objects for them to be consistent. Backlinks keep track of external references to objects on other servers. For each external reference on a server, the backlink process ensures that the real object exists in the correct location and verifies all backlink attributes on the master of the replica. The backlink process occurs two hours after the database is open, and then every 780 minutes (13 hours). The interval is configurable from 2 minutes to 10,080 minutes (7 days). After migrating to edirectory, start the DSTrace process by issuing the ndstrace -l>log& command, which runs the process at the background. This allows you to properly analyze the results of the backlinker process, which takes 4 to 10 minutes. Then force the backlink process to run by issuing the ndstrace -c 'set ndstrace=*b' command from the DSTrace OS command prompt. Review the results of the log file created in the first step. Then you can unload the DSTrace process by issuing the ndstrace -u command. Running the backlink process is especially important on servers that do not contain a replica. 2.5 Upgrading edirectory When upgrading edirectory, you can use one of the following upgrade paths: Upgrade from an existing 32-bit version to a new 32-bit version Upgrade from an existing 32-bit version to a new 64-bit version Upgrade from an existing 64-bit version to a new 64-bit version NOTE: There are no special steps to upgrade from a 32-bit version of edirectory to a 64-bit version of edirectory. You can follow the same procedure as you would to upgrade from a 32-bit version to a new 32-bit version. 24 NetIQ edirectory 8.8 SP8 Installation Guide

25 The following sections provide information to help you upgrade your existing edirectory installation to the current version. Section 2.5.1, Server Health Checks, on page 25 Section 2.5.2, Upgrading on Linux Servers Other Than OES, on page 25 Section 2.5.3, Unattended Upgrade of edirectory on Linux, on page 26 Section 2.5.4, Upgrading edirectory on Existing OES, on page 27 Section 2.5.5, Upgrading the Tarball Deployment of edirectory 8.8, on page 27 Section 2.5.6, Upgrading Multiple Instances, on page 28 NOTE: The ndsconfig upgrade command is used to upgrade the necessary configuration of the individual components such as HTTP, LDAP, SNMP, SAS, and NetIQ Modular Authentication Service (NMAS) 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: Section B.3.2, Partitions and Replica Health, on page 119 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 Appendix B, edirectory Health Checks, on page 117 for a list of minor and critical error conditions. Skipping Server Health Checks To skip server health checks, run nds-install -j or ndsconfig upgrade -j from the installation folder. For more information, see Appendix B, edirectory Health Checks, on page Upgrading on Linux Servers Other Than OES edirectory upgrade is supported from edirectory 8.8 SP2 onwards. If you have edirectory 8.8 SP2 or later versions installed, you can directly upgrade to edirectory 8.8 SP8. To upgrade, use the nds-install utility. This utility is located in the Setup directory of the downloaded file for Linux platform. Enter the following command from the 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. Installing or Upgrading NetIQ edirectory on Linux 25

26 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 the 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 Unattended Upgrade of edirectory on Linux On Linux, 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 Linux: 1 Perform the health check of edirectory: Health check of all the root instances planned for upgrade is manually done by using ndscheck utility. 1a export LD_LIBRARY_PATH to the <untarred location of edirectory>/edirectory/ setup/utils 1b 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 88SP8>/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 88SP8>/eDirectory/ setup/utils/ndscheck -a <user name> -w file:<filename> --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: 2a Run the 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/ndsmodules:/opt/novell/lib:$LD_LIBRARY_PATH MANPATH=/opt/novell/man:/opt/novell/eDirectory/man:$MANPATH TEXTDOMAINDIR=/opt/novell/eDirectory/share/locale 26 NetIQ edirectory 8.8 SP8 Installation Guide