Novell EDIRECTORY 8.8 SP3 User manual

Novell®
www.novell.com
novdocx (en) 11 July 2008
AUTHORIZED DOCUMENTATION
Novell eDirectory 8.8 Installation Guide
eDirectory TM
8.8 SP3
July 31, 2008
Installation Guide

novdocx (en) 11 July 2008
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no
responsibility for your failure to obtain any necessary export approvals.
Copyright © 2003-2006 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent
applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get
updates, see www.novell.com/documentation.

novdocx (en) 11 July 2008
Novell Trademarks
Client32 is a trademark of Novell, Inc.
eDirectory is a trademark of Novell, Inc.
NetWare is a registered trademark of Novell, Inc., in the United States and other countries.
NetWare Core Protocol and NCP are trademarks of Novell, Inc.
NMAS is a trademark of Novell, Inc.
Novell is a registered trademark of Novell, Inc., in the United States and other countries.
Novell Client is a trademark of Novell, Inc.
Novell Directory Services and NDS are registered trademarks of Novell, Inc., in the United States and other
countries.
Ximiam is a registerd trademark of Novell, Inc., in the United States and other countries.
ZENworks is a registered trademark of Novell, Inc., in the United States and other countries.
Third-Party Materials
All third-party trademarks are the property of their respective owners.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://
www.openssl.org).

novdocx (en) 11 July 2008

Contents 5
Contents
novdocx (en) 11 July 2008
About This Book 9
1 Installing or Upgrading Novell eDirectory on NetWare 11
1.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Forcing the Backlink Process to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Updating the eDirectory Schema for NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6 Disk Space Check on Upgrading to eDirectory SP3 or later . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.7 Installing or Upgrading Novell eDirectory on NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.7.1 Installing or Upgrading Novell eDirectory 8.8 on NetWare . . . . . . . . . . . . . . . . . . . . 15
1.7.2 Server Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7.3 Installing NMAS Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7.4 Installing NMAS Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7.5 Installing into a Tree with Dotted Name Containers . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.7.6 Unattended Upgrade to eDirectory 8.8 SP3 on Netware. . . . . . . . . . . . . . . . . . . . . . 17
1.7.7 Remote Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Installing or Upgrading Novell eDirectory on Windows 23
2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4 Forcing the Backlink Process to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5 Updating the eDirectory Schema for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.6 Disk Space Check on Upgrading to eDirectory SP3 or later . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.7 Installing Novell eDirectory on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.7.1 Installing or Updating Novell eDirectory 8.8 on Windows 2000 or Server 2003 . . . . 27
2.7.2 Server Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.7.3 Communicating with eDirectory through LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.7.4 Installing NMAS Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.7.5 Installing NMAS Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.7.6 Installing into a Tree with Dotted Name Containers . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.7.7 Unattended Install and Upgrade to eDirectory 8.8 SP3 on Windows . . . . . . . . . . . . 34
3 Installing or Upgrading Novell eDirectory on Linux 45
3.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4 Forcing the Backlink Process to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5 Upgrading eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.5.1 Server Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.5.2 Upgrading on Linux Servers Other Than OES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.5.3 Upgrading Through ZENworks Linux Management on OES Linux SP3 . . . . . . . . . . 50
3.5.4 Upgrading eDirectory During OES 1.0 to OES 2.0 Upgrade . . . . . . . . . . . . . . . . . . . 54
3.5.5 Upgrading the Tarball Deployment of eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . . 55
3.5.6 Upgrading Multiple Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.5.7 Disk Space Check on Upgrading to eDirectory SP3 or later . . . . . . . . . . . . . . . . . . . 56

6Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
3.6 Installing eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.6.1 Using SLP with eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.6.2 Installing NICI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.6.3 Using the nds-install Utility to Install eDirectory Components . . . . . . . . . . . . . . . . . . 60
3.6.4 Installing Through ZENworks Linux Management on OES Linux SP3 . . . . . . . . . . . 63
3.6.5 Nonroot User Installing eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.6.6 Using the ndsconfig Utility to Add or Remove the eDirectory Replica Server . . . . . . 70
3.6.7 Using ndsconfig to Configure Multiple Instances of eDirectory 8.8 . . . . . . . . . . . . . . 74
3.6.8 Using ndsconfig to Install a Linux Server into a Tree with Dotted Name Containers. 80
3.6.9 Using the nmasinst Utility to Configure NMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.6.10 Nonroot user SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4 Installing or Upgrading Novell eDirectory on Solaris 83
4.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.4 Forcing the Backlink Process to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.5 Upgrading eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5.1 Upgrading Multiple Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5.2 Upgrading the Tarball Deployment of eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . . 86
4.6 Installing eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.6.1 Server Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6.2 Using SLP with eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6.3 Installing NICI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.6.4 Using the Nds-install Utility to Install eDirectory Components . . . . . . . . . . . . . . . . . . 89
4.6.5 Nonroot User Installing eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.6.6 Using the Ndsconfig Utility to Add or Remove the eDirectory Replica Server . . . . . . 94
4.6.7 Using ndsconfig to Configure Multiple Instances of eDirectory 8.8 . . . . . . . . . . . . . . 96
4.6.8 Using Ndsconfig to Install a Solaris Server into a Tree with Dotted Name Containers .
96
4.6.9 Using the Nmasinst Utility to Configure NMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.6.10 Nonroot user SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5 Installing or Upgrading Novell eDirectory on AIX 99
5.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.4 Forcing the Backlink Process to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.5 Upgrading eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.5.1 Upgrading Multiple Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.5.2 Upgrading the Tarball Deployment of eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . 102
5.6 Installing eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.6.1 Server Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.6.2 Using SLP with eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.6.3 Installing NICI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.6.4 Using the Nds-install Utility to Install eDirectory Components . . . . . . . . . . . . . . . . . 105
5.6.5 Nonroot User Installing eDirectory 8.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.6 Using the Ndsconfig Utility to Add or Remove the eDirectory Replica Server . . . . . 109
5.6.7 Using ndsconfig to Configure Multiple Instances of eDirectory 8.8 . . . . . . . . . . . . . 111
5.6.8 Using Ndsconfig to Install an AIX Server into a Tree with Dotted Name Containers 111
5.6.9 Using the Nmasinst Utility to Configure NMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.6.10 nonroot user SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Contents 7
novdocx (en) 11 July 2008
6 Relocating the DIB 115
6.1 Linux and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.2 NetWare and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
7 Upgrade Requirements of eDirectory 8.8 117
7.1 Reference Changes in 8.8 SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.2 Upgrade Process in 8.8 SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.3 Performing a Dry Run before Upgrading eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
7.3.1 Common Problems Encountered during the Upgrade Process . . . . . . . . . . . . . . . . 121
8 Configuring Novell eDirectory on Linux, Solaris, or AIX Systems 123
8.1 Configuration Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.1.1 The ndsconfig Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.1.2 Using the ldapconfig Utility to Configure the LDAP Server and LDAP Group Objects .
123
8.1.3 Using the nmasinst Utility to Configure Novell Modular Authentication Service . . . 124
8.2 Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.3 Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9 Migrating to eDirectory 8.8 SP3 131
9.1 Migrating to eDirectory 8.8 SP3 While Upgrading the Operating System . . . . . . . . . . . . . . . 131
9.2 Migrating to eDirectory 8.8 SP3 Without Upgrading the Operating System. . . . . . . . . . . . . . 133
10 Uninstalling Novell eDirectory 135
10.1 Uninstalling eDirectory on NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
10.1.1 Reinstalling eDirectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
10.2 Uninstalling eDirectory on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.2.1 Uninstalling eDirectory, ConsoleOne, and SLP DA . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.2.2 Unattended Uninstallation of eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.2.3 Uninstalling NICI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
10.2.4 Uninstalling Microsoft Visual C++ 2005 Runtime Libraries . . . . . . . . . . . . . . . . . . . 139
10.3 Uninstalling eDirectory on Linux, Solaris, or AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
A Linux, Solaris, and AIX Packages for Novell eDirectory 141
B eDirectory Health Checks 145
B.1 Need for Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
B.2 Performing Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
B.2.1 With the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
B.2.2 As a Standalone Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
B.3 Types of Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
B.3.1 Basic Server Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
B.3.2 Partitions and Replica Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
B.4 Categorization of Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
B.4.1 Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
B.4.2 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
B.4.3 Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
B.5 Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

8Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
C Configuring OpenSLP for eDirectory 151
C.1 Service Location Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
C.2 SLP Fundamentals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
C.2.1 Novell Service Location Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
C.2.2 User Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
C.2.3 Service Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
C.3 Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

About This Book 9
novdocx (en) 11 July 2008
About This Book
This Installation Guide describes how to install Novell®eDirectoryTM 8.8. It is intended for network
administrators, and contains the following sections:
Chapter 1, “Installing or Upgrading Novell eDirectory on NetWare,” on page 11
Chapter 2, “Installing or Upgrading Novell eDirectory on Windows,” on page 23
Chapter 3, “Installing or Upgrading Novell eDirectory on Linux,” on page 45
Chapter 4, “Installing or Upgrading Novell eDirectory on Solaris,” on page 83
Chapter 5, “Installing or Upgrading Novell eDirectory on AIX,” on page 99
Chapter 6, “Relocating the DIB,” on page 115
Chapter 7, “Upgrade Requirements of eDirectory 8.8,” on page 117
Chapter 8, “Configuring Novell eDirectory on Linux, Solaris, or AIX Systems,” on page 123
Chapter 10, “Uninstalling Novell eDirectory,” on page 135
Appendix A, “Linux, Solaris, and AIX Packages for Novell eDirectory,” on page 141
Appendix B, “eDirectory Health Checks,” on page 145
Appendix C, “Configuring OpenSLP for eDirectory,” on page 151
Audience
The guide is intended for network administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the Novell eDirectory 8.8 Installation Guide, see the Novell
eDirectory 8.8 Documentation (http://www.novell.com/documentation/edir88/index.html) Web site.
Additional Documentation
For documentation on managing and administering eDirectory, see the Novell eDirectory 8.8
Administration Guide (http://www.novell.com/documentation/edir88/index.html).
Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
within a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.

10 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* and UNIX*, should use forward slashes as required by your software.

Installing or Upgrading Novell eDirectory on NetWare
1
11
novdocx (en) 11 July 2008
1
Installing or Upgrading Novell
eDirectory on NetWare
Use the following information to install or upgrade Novell®eDirectoryTM 8.8 on a NetWare®server:
Section 1.1, “System Requirements,” on page 11
Section 1.2, “Prerequisites,” on page 11
Section 1.3, “Hardware Requirements,” on page 12
Section 1.4, “Forcing the Backlink Process to Run,” on page 13
Section 1.5, “Updating the eDirectory Schema for NetWare,” on page 13
Section 1.6, “Disk Space Check on Upgrading to eDirectory SP3 or later,” on page 14
Section 1.7, “Installing or Upgrading Novell eDirectory on NetWare,” on page 14
1.1 System Requirements
The system requirements to upgrade to eDirectory 8.8 SP 3 are,
NetWare version 6.5 SP7 or later
Administrative rights to the eDirectory tree to enable you to modify the schema.
1.2 Prerequisites
IMPORTANT: Check the currently installed Novell and Third Party applications to determine if
eDirectory 8.8 is supported before upgrading your existing eDirectory environment. You can find
out the current status for Novell products in the TID - What Novell products are supported with
Novell eDirectory 8.8? (http://support.novell.com/cgi-bin/search/searchtid.cgi?10099872.htm) It is
also highly recommended to backup eDirectory prior to any upgrades.
If you are installing into an eDirectory tree that has NetWare and Windows servers, each
NetWare server must be running:
NetWare 5.1 with Support Pack 8 (http://support.novell.com/filefinder/9331/index.html)
or later
NetWare 6.0 with Support Pack 5 (http://support.novell.com/filefinder/13659/index.html)
or later
NetWare 6.5 with Support Pack 3 (http://support.novell.com/filefinder/18197/index.html)
or later
Each Windows server must be running eDirectory 8.7.3 or later.
(Conditional) 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 and ConsoleOne, must
have NICI 2.7 installed on it.

12 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
When you upgrade your Certificate Authority (CA) server to eDirectory 8.8, the key size will
not change; it will 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.
(Conditional) If you are upgrading a NetWare server as a nonadministrator user, ensure that you
have met the following prerequisites:
A NetWare server in the eDirectory 8.8 tree installed as the tree admin
Ensure that you have the following rights:
Supervisor rights to the container the server is being installed into.
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.
As a nonadministrator user, you can only upgrade a NetWare server.
(Conditional) If you are installing a secondary server into an existing tree as a nonadministrator
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 admin of the tree before adding
the secondary using container admin.
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.
1.3 Hardware Requirements
Hardware requirements depend on the specific implementation of eDirectory.
For example, a base installation of eDirectory with the standard schema requires about 74 MB of
disk space for every 50,000 users. However, if you add a new set of attributes or completely fill in
every existing attribute, the object size grows. These additions affect the disk space, processor, and
memory needed.
Two factors increase performance: more cache memory and faster processors.
For best results, cache as much of the DIB Set as the hardware allows.
eDirectory scales well on a single processor. However, Novell eDirectory 8.7 took advantage of
multiple processors. Adding processors improves performance in some areas—for example, logins
and having multiple threads active on multiple processors. eDirectory itself is not processor
intensive, but it is I/O intensive.
The following table illustrates typical system requirements for eDirectory for NetWare:
Objects Processor Memory Hard Disk
100,000 Pentium* III 450-700 MHz (single) 384 MB 144 MB
1 million Pentium III 450-700 MHz (dual) 2 GB 1.5 GB

Installing or Upgrading Novell eDirectory on NetWare 13
novdocx (en) 11 July 2008
Requirements for processors might be greater than the table indicates, depending upon additional
services available on the computer as well as the number of authentications, reads, and writes that
the computer is handling. Processes such as encryption and indexing can be processor intensive.
Of course, faster processors improve performance. Additional memory also improves performance
because eDirectory can then cache more of the directory into memory.
1.4 Forcing the Backlink Process to Run
Because the internal eDirectory identifiers change when upgrading to Novell 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, we recommend that you force the backlink to run by issuing the
following commands from the server console. Running the backlink process is especially important
on servers that do not contain a replica.
1At the server console, enter set dstrace=on.
2Enter set dstrace=+blink.
3Enter set dstrace=*b.
4When the process is complete, enter set dstrace=off.
1.5 Updating the eDirectory Schema for NetWare
When upgrading a NetWare server to eDirectory 8.8, you might need to update the eDirectory
schema by running DSRepair on the server that has the master replica of the root partition.
IMPORTANT: If the master replica of the root partition resides on a Windows server, follow the
instructions in Section 2.5, “Updating the eDirectory Schema for Windows,” on page 26.
To update the schema:
1Copy the appropriate dsrepair.nlm file from the product CD (or downloaded and
expanded file) to the sys:\system directory of the server that contains the master replica of
the Tree partition.
2At the server console of the master replica of the root partition, load dsrepair.nlm.
3Select Advanced Options Menu > Global Schema Operations.
4Enter the Administrator's name (for example, Admin.VMP) and password.
10 million Pentium III 450-700 MHz (2 to 4) 2+ GB 15 GB
Objects Processor Memory Hard Disk

14 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
NOTE: In eDirectory 8.8 and later, you can have case sensitive passwords for all the utilities.
Refer to Novell eDirectory 8.8 What's New Guide (http://www.novell.com/documentation/
edir88/index.html) for more information.
5Select Post NetWare 5 Schema Update > Yes.
dsrepair.nlm updates the schema and posts the results to the dsrepair.log file.
Ignore errors associated with adding object classes. dsrepair.nlm is simply applying the
Post NetWare 5 Schema Update changes to each object.
6Copy the appropriate patch version of dsrepair.nlm to each NetWare server in the
eDirectory tree.
Use the table in Step 1 as a reference. Having a correct version on each server ensures that the
schema needed for eDirectory is properly maintained when dsrepair.nlm is run in the
future.
If you use an earlier version of dsrepair.nlm and select Rebuild Operational Schema,
schema enhancements made by the Post NetWare 5 Schema Update will be lost. To resolve lost
schema enhancements, run dsrepair.nlm according to the following table.
This action resynchronizes the schema from the root of the tree.
7Close dsrepair.nlm before installing eDirectory on the server.
If dsrepair.nlm is loaded, the server might not restart.
1.6 Disk Space Check on Upgrading to
eDirectory SP3 or later
When eDirectory server is upgraded from previous versions to eDirectory 8.8 SP3 or later, 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 sys:\system\dscheck.log.
NOTE: The disk space check is required only during the DIB upgrade process. For more
information, refer to Chapter 7, “Upgrade Requirements of eDirectory 8.8,” on page 117.
1.7 Installing or Upgrading Novell eDirectory on
NetWare
This section contains the following information:
“Installing or Upgrading Novell eDirectory 8.8 on NetWare” on page 15
If You Are Running dsrepair.nlm From
Here Then
A server that holds a writable replica of the
root partition
Reapply the Post NetWare 5 Schema Update to
your eDirectory tree.
From any other server Select Advanced Options > Global Schema
Operations > Request Schema from Tree.

Installing or Upgrading Novell eDirectory on NetWare 15
novdocx (en) 11 July 2008
“Server Health Checks” on page 16
“Installing NMAS Server Software” on page 16
“Installing NMAS Client Software” on page 16
“Installing into a Tree with Dotted Name Containers” on page 17
“Unattended Upgrade to eDirectory 8.8 SP3 on Netware” on page 17
“Remote Installation or Upgrade” on page 21
NOTE: Unattended Upgrade feature is supported only for SP3 release.
1.7.1 Installing or Upgrading Novell eDirectory 8.8 on NetWare
1At the server console, enter nwconfig.nlm.
2Select Product Options > Install a Product Not Listed.
3Press F3 and specify the path to the NW directory where the installation program can find the
nds8.ips file.
If you downloaded eDirectory from the Web, enter the path to the NW directory you
extracted from the downloaded file (for example, sys:\edir\nw).
If you are installing from a CD, mount the CD as a volume and enter volume_name:NW
(for example, edir_88:NW).
For information on mounting a CD as a volume, see “CD-ROMs as Logical Volumes”
(http://www.novell.com/documentation/lg/nw6p/nss_enu/data/htxx7fd6.html) in the
Novell Storage Services Administration Guide.
4Follow the on-screen prompts concerning license agreements, the Readme file, and tips.
5Enter the administrator's login name (for example, Admin.VMP) and password.
IMPORTANT: This window might close before you enter this information. If it does, toggle
(Alt+Esc) to the screen and enter the information. Otherwise, the installation will not be
complete.
NOTE: In eDirectory 8.8 and later, you can have case sensitive passwords for all the utilities.
Refer to Novell eDirectory 8.8 What's New Guide (http://www.novell.com/documentation/
edir88/index.html) for more information.
6In the LDAP Configuration screen, specify which LDAP ports to use, then click Next.
For more information, see “Communicating with eDirectory through LDAP” on page 29.
7Select the NMASTM login method you want to install, then click Next.
See “Installing NMAS Server Software” on page 16 and “Installing NMAS Client Software”
on page 16 for more information.
8Click Finish to start the eDirectory installation.
9To complete the installation, remove any diskettes or CDs when prompted, then click Yes to
restart the server.

16 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
1.7.2 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 147
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 145 for a list of minor and critical error
conditions.
Skipping Server Health Checks
To skip server health checks, enter No when you are prompted to perform the health check.
For more information, see Appendix B, “eDirectory Health Checks,” on page 145.
1.7.3 Installing NMAS Server Software
Novell Modular Authentication ServiceTM (NMAS) server components are installed automatically
when you run the eDirectory installation program. You will need to select the login methods you
want to install.
Select the login methods that you want to install into eDirectory by checking the appropriate check
boxes. When you select a login method, a description of the component appears in the Description
box. For more information on login methods, see “Managing Login and Post-Login Methods and
Sequences” (http://www.novell.com/documentation/lg/nmas23/admin/data/a53vj9a.html) in the
Novell Modular Authentication Service Administration Guide.
Click Select All if you want to install all the login methods into eDirectory. Click Clear All if you
want to clear all selections.
The NDS login method is installed by default.
1.7.4 Installing NMAS Client Software
The NMAS client software must be installed on each client workstation where you want to use the
NMAS login methods.
1At a Windows client workstation, insert the Novell eDirectory 8.8 CD.
2From the NMAS directory, run nmasinstall.exe.
3Select the NMAS Client Components checkbox.
Optionally, you can select the NICI checkbox if you want to install this component.
4Click OK and follow the on-screen instructions.
5Reboot the client workstation after the installation completes.

Installing or Upgrading Novell eDirectory on NetWare 17
novdocx (en) 11 July 2008
1.7.5 Installing into a Tree with Dotted Name Containers
You can install a NetWare server into an eDirectory tree that has containers with dots in the names
(for example, O=novell.com or C=u.s.a). Using containers with dotted names requires that those
dots be escaped with the backslash character. To escape a dot, simply put a backslash in front of any
dot in a container name. For example:
O=novell\.com
You cannot start a name with a dot. For example, you cannot create a container named “.novell”
because it starts with a dot (‘.’).
IMPORTANT: If your tree has containers with dotted names, you must escape those names when
logging into utilities such as iMonitor, iManager, and DHost iConsole. For example, if your tree has
“novell.com” as the name of the O, enter username.novell\.com in the Username field when logging
in to iMonitor (see Figure 1-1).
Figure 1-1 iMonitor Login Screen
1.7.6 Unattended Upgrade to eDirectory 8.8 SP3 on Netware
The SPK for eDirectory 8.8 upgrade is provided with the Netware installation package. SPK has to
be inserted into the ConsoleOne “Server Software Packages” snap-in for customizing into local
environments. Once the Server Software Package ConsoleOne snap-in is installed, you can insert
this SPK in the ConsoleOne.
NOTE: Pre upgrade health check is not run during unattended upgrade, ensure you run dscheck.nlm
manually before starting the upgrade.
To perform this,
1Import the applicable SPK into ConsoleOne.
2To do this, right click on the Server Software Packages name space and select Insert New
Package (see Figure 1-2).

18 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
Figure 1-2 Adding the package into ConsoleOne
An SPK has components and properties. To see the components, click on the SPK's expand
box. The properties include a description, requirements, and variables. The Support Pack SPKs
use variables, which is the only place where each site will need to make specific modifications.
All of the SPK's components may use the SPK's variables. To see the variables, right click on
the SPK and select Properties (see Figure 1-3).
Figure 1-3 Editing the package properties
3Click on the Va ri ab le s tab to make the site-specific changes needed by the installation process
(see Figure 1-4).

Installing or Upgrading Novell eDirectory on NetWare 19
novdocx (en) 11 July 2008
Figure 1-4 Modifying the package variables
Edit and change the values of the two variables “user_id” and “pwd”.
user_id
administrator name that the install program will use to extend the tree.
pwd
password for the above username
These are the only two fields that need to be edited. Leave the values of rest of the variables as
defined.
WARNING: The installation source folders will be partially removed for security reasons. You
need to copy the installation source again in case you restart the installation on failures, e.g,
Disk Space unavailability errors.
Adding Upgrade Source to the SPK
The automated upgrade for eDirectory on Netware for ZFS environment is delivered as SPK along
with the source. The compiled CPK is not provided since the user is expected to provide values for
the variables containing administrator credentials. This SPK needs to be compiled to a CPK in the
customer site after providing values to these variables.
As mentioned earlier, the source is delivered along with the SPK and the source has to be attached to
the SPK before compiling the CPK. Steps for attaching the source to the SPK is given below:
1Copy the source to the local machine and name the folder as “eDir88”. There are references to
this folder name inside the SPK and hence please use this suggested name.
2Right click on the “Copying files” component and select Properties and browse to the Copy
File Tab.
3Remove the file set (if given as a sample) by right clicking on the file group and choosing
Remove. Choose “Add File” by right clicking on the File Group as given below:

20 Novell eDirectory 8.8 Installation Guide
novdocx (en) 11 July 2008
Figure 1-5 Adding the source to the SPK
4Then select the “eDir88” folder that contains the source files that are delivered along with the
SPK as given below:
Figure 1-6 Selecting the upgrade source
Fully Automated Standalone Upgrade
Once the above changes are performed, compile the SPK to make a CPK using the right-click menu
option in the main component to compile (see Figure 1-7).