Novell OES 11 SP2, Open Enterprise Server 11 SP2 Installation Manual
Installation Guide
Open Enterprise Server 11 SP2
January 2014
www.novell.com/documentation
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. See the Novell International Trade
Services Web page (http://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 © 2005–2014 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.
1800 South Novell Place
Provo, UT 84606
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see the
Novell Documentation Web page (http://www.novell.com/documentation/oes11/).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/
tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Contents
About This Guide 9
1 What’s New or Changed in the OES Install 11
1.1 What’s New (OES 11 SP2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 What’s New or Changed in OES 11 SP1 Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.3 What’s New or Changed in OES 11 Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Preparing to Install OES 11 SP2 13
2.1 Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Meeting All Server Software and Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1 Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.2 Server Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 NetIQ eDirectory Rights Needed for Installing OES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2.3.1 Rights to Install the First OES Server in a Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2 Rights to Install the First Three Servers in an eDirectory Tree . . . . . . . . . . . . . . . . . . . . . . 15
2.3.3 Rights to Install the First Three Servers in any eDirectory Partition . . . . . . . . . . . . . . . . . . 15
2.4 Installing and Configuring OES as a Subcontainer Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.1 Rights Required for Subcontainer Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.2 Providing Required Rights to the Subcontainer Administrator for Installing and
Managing Samba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.4.3 Starting a New Installation as a Subcontainer Administrator . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4.4 Adding/Configuring OES Services as a Different Administrator . . . . . . . . . . . . . . . . . . . . . 20
2.5 Preparing eDirectory for OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5.1 If Your Directory Tree Is Earlier than eDirectory 8.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5.2 If Your LDAP Server Is Running NetWare 6.5 SP2 or Earlier . . . . . . . . . . . . . . . . . . . . . . . 21
2.5.3 If Your Tree Has Ever Contained an OES 1 Linux Server with LUM and NSS
Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.5.4 Extending the Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.6 Deciding What Patterns to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7 Obtaining OES 11 SP2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.8 Preparing Physical Media for a New Server Installation or an Upgrade . . . . . . . . . . . . . . . . . . . . . . 35
2.9 Setting Up a Network Installation Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9.1 SUSE Linux as a Network Installation Source Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9.2 NetWare as a Network Installation Source Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.9.3 Windows as a Network Installation Source Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.10 Always Install OES as an Add-On Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.11 Install Only One Server at a Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.12 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3 Installing OES 11 SP2 as a New Installation 43
3.1 Linux Software RAIDs Are Not Cluster Aware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2 Linux Software RAIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3 Starting the OES 11 SP2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.1 Installing from Physical Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.2 Installing from a Network Source with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.3 Installing from a Network Source without DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.4 Specifying the Installation Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Contents 3
3.5 Specifying the Add-On Product Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.6 Setting Up the Clock and Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.7 Specifying the Installation Settings for the SLES Base and OES Installation . . . . . . . . . . . . . . . . . . 48
3.7.1 Setting Up Disk Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.7.2 Customizing the Software Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.7.3 Accepting the Installation Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
3.8 Specifying Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.8.1 Specifying the Password for the System Administrator “root” . . . . . . . . . . . . . . . . . . . . . . . 55
3.8.2 Specifying the Hostname and Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.8.3 Specifying Network Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.8.4 Testing the Connection to the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.8.5 Specifying Novell Customer Center Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . 59
3.8.6 Updating the Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
3.8.7 Specifying Service Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.8.8 Typical and Custom OES Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.8.9 Specifying LDAP Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.8.10 Specifying eDirectory Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.8.11 Configuring OES Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.8.12 Configuration Guidelines for OES Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.9 Finishing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.10 Verifying That the Installation Was Successful. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.11 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4 Installing or Configuring OES 11 SP2 on an Existing Server 109
4.1 Before You Install OES Services on an Existing Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.1.1 Always Use YaST to Install and Initially Configure OES Services. . . . . . . . . . . . . . . . . . . 109
4.1.2 Don’t Install OES While Running the Xen Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.1.3 If You Want OES to Use a Local eDirectory Database on the Server . . . . . . . . . . . . . . . . 110
4.2 Adding/Configuring OES Services on an Existing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.3 Adding/Configuring OES Services on a Server That Another Administrator Installed . . . . . . . . . . . 114
4.4 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5 Upgrading to OES 11 SP2 115
5.1 Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.2 Planning for the Upgrade to OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2.1 Be Sure to Check the Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2.2 Always Upgrade SLES and OES at the Same Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2.3 Understanding the Implications for Other Products Currently Installed on the Server. . . . 116
5.3 Meeting the Upgrade Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.3.1 Securing Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.3.2 Ensuring That There Is Adequate Storage Space on the Root Partition . . . . . . . . . . . . . . 117
5.3.3 Preparing the Server You Are Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.3.4 Checking the Server’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.3.5 Checking the Server’s DNS Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.3.6 Ensuring That the Server Has a Server Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.3.7 Changing the Mount Options Before an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.3.8 Preparing an Installation Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.4 Upgrading to OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.4.1 For Servers with EVMS and LVM on the System Device . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.4.2 To Upgrade Using a Network Installation Source with DHCP (Offline) . . . . . . . . . . . . . . . 123
5.4.3 Upgrading Using a Network Installation Source without DHCP (Offline). . . . . . . . . . . . . . 124
5.4.4 Using Physical Media to Upgrade (Offline) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.4.5 Selecting the Installation Mode Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.4.6 Specifying the Partition to Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.4.7 Specifying the Add-On Product Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 129
5.4.8 Verifying and Customizing the Update Options in Installation Settings . . . . . . . . . . . . . . . 129
4 OES 11 SP2: Installation Guide
5.4.9 Accepting the Installation Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.4.10 Specifying Configuration Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.5 Finishing the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.6 Using AutoYaST for an OES 11 SP2 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.6.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.6.2 Remastering the Integrated ISO without the add_on_products.xml . . . . . . . . . . . . . . . . . 145
5.6.3 Creating an Answer File to Provide the eDirectory and DSfW Passwords . . . . . . . . . . . . 145
5.6.4 Upgrading an OES 2 (64-bit), OES 11 or OES 11 SP1 Server to OES 11 SP2. . . . . . . . . 146
5.6.5 Upgrading an OES 2 (64-bit), OES 11 or OES 11 SP1 XEN Guest Server to OES 11
SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.6.6 Troubleshooting an AutoYaST Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.7 Channel Upgrade from OES 11 SP1 to OES 11 SP2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.7.1 Channel Upgrade from OES 11 SP1 to OES 11 SP2 Via Wagon . . . . . . . . . . . . . . . . . . . 149
5.7.2 Channel Upgrade from OES 11 SP1 to OES 11 SP2 Using Zypper . . . . . . . . . . . . . . . . . 152
5.7.3 Upgrading OES 11 SP1 to OES 11 SP2 Using SMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.7.4 Rolling Back the Server in the Middle of a Wagon-based Channel Upgrade . . . . . . . . . . 154
5.8 Using SUSE Manager to Upgrade from OES 11 SP1 to OES 11 SP2. . . . . . . . . . . . . . . . . . . . . . . 154
5.9 Verifying That the Upgrade Was Successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.10 Moving to Common Proxy Users After an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.11 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
6 Completing OES Installation or Upgrade Tasks 159
6.1 Determining Which Services Need Additional Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
6.2 Rebooting the Server after Installing NSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
6.3 Restarting Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
6.4 Launching and Configuring Firefox for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
6.5 Implementing Digital Certificates in an OES Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
6.5.1 Configuring the Digital Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
6.5.2 Reconfiguring Services after Importing the Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
7 Updating (Patching) an OES 11 SP2 Server 165
7.1 Overview of Updating (Patching) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
7.1.1 The Patch Process Briefly Explained. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
7.1.2 Update Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7.2 Preparing the Server for Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
7.3 Registering the Server in the Novell Customer Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
7.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
7.3.2 Registering the Server in the Novell Customer Center Using the Command Line . . . . . . 168
7.3.3 Registering the Server in the Novell Customer Center Using the GUI . . . . . . . . . . . . . . . 169
7.4 Updating the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.4.1 Updating the Server Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7.5 Verifying That Your Repository Subscriptions Are Up-to-Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
7.6 Frequently Asked Questions about Updating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
7.6.1 Do I apply all the patches in the catalogs? How do I know which patches to apply? . . . . 172
7.7 Patching From Behind a Proxy Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
7.8 GUI Based Patching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
7.9 Using SUSE Manager to Patch an OES Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
7.9.1 Setting Up SUSE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
7.9.2 Patching an OES 11 or Later Server Using SUSE Manager . . . . . . . . . . . . . . . . . . . . . . . 176
7.10 Quick Path Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
7.10.1 Do Not Use zypper up without the -t Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
7.10.2 Command Line Quick Path for Updating OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
7.11 Installing the Latest iManager NPMs After Applying OES Patches . . . . . . . . . . . . . . . . . . . . . . . . . 179
7.12 Restarting the OES Instance of Tomcat After Applying a Tomcat Update . . . . . . . . . . . . . . . . . . . . 179
Contents 5
8 Using AutoYaST to Install and Configure Multiple OES Servers 181
8.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
8.2 Setting Up a Control File with OES Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
8.2.1 Fixing an Automatically Created Control File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
8.2.2 Using the AutoInstallation Module to Create the Control File . . . . . . . . . . . . . . . . . . . . . . 183
8.3 Setting Up an Installation Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
8.4 Cloning an OES Server Post OES Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 188
8.4.1 Generating the autoinst.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
8.4.2 Using the autoinst.xml to Reinstall an OES Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
9 Installing OES as a VM Host Server 191
9.1 Installing the KVM Hypervisor and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
9.2 Installing the Xen Hypervisor and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
9.3 Upgrading an OES 2 Xen VM Host Server to OES 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
9.4 Setting Up Bridging After the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10 Installing, Upgrading, or Updating OES on a VM 195
10.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10.1.1 OES 11 SP2 VM Host Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.2 Novell Storage Services Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.3 Setup Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.3 Preparing the Installation Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.3.1 Downloading the Installation Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.3.2 Preparing the Installation Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.4 Installing an OES 11 SP2 VM Guest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.4.1 Specifying Options for Creating an OES 11 SP2 VM Guest . . . . . . . . . . . . . . . . . . . . . . . 198
10.4.2 Specifying the Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.4.3 Specifying the Add-On Product Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.4.4 Completing the OES 11 SP2 VM Guest Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.5 Upgrading an OES 2 VM Guest to OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.5.1 Before You Start the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.5.2 Starting the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.6 Managing a Virtual Machine Running OES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.7 Setting Up an OES 11 SP2 VM Guest to Use Novell Storage Services (NSS) . . . . . . . . . . . . . . . . 202
11 Installing and Managing NetWare on a Xen-based VM 205
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11.2 Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.1 OES Registration Is Required for Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.2 Supported Configurations and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.2.3 Unsupported Configurations and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.3 Preparing to Install a NetWare VM Guest Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
11.3.1 Planning for VM Host Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.3.2 Planning for NetWare VM Guest Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
11.3.3 You Must Use Timesync for Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.3.4 Disabling the Alt+Esc Shortcut on the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.4 Installing Virtualized NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.4.1 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.4.2 Creating a Xen Virtual Machine and Installing a NetWare VM Guest Server . . . . . . . . . . 210
11.5 Managing NetWare on a Virtual Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
11.5.1 Using the Virtual Machine Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
11.5.2 Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
6 OES 11 SP2: Installation Guide
11.6 If VM Manager Doesn’t Launch on a Xen VM Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
12 Disabling OES 11 Services 219
13 Reconfiguring eDirectory and OES Services 221
13.1 Cleaning Up the eDirectory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
13.1.1 Before You Clean Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
13.1.2 Reconfiguring the Replica Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
13.1.3 Reconfiguring the CA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
13.1.4 Cleaning Up eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
13.2 Reconfiguring the eDirectory Server through YaST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
13.3 Reconfiguring OES Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
13.3.1 Re-creating eDirectory Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
13.3.2 Services Requiring Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
13.3.3 Manually Starting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
13.4 Re-configuring iManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
14 Security Considerations 229
14.1 Access to the Server During an Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
14.2 Remote Installations Through VNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
14.3 Improperly Configured LDAP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
15 Troubleshooting 231
15.1 Deleting the Existing eDirectory Objects when Reinstalling the OES Server or Reconfiguring
the eDirectory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
15.2 eDirectory User Password Screen Does Not Show Up During an Upgrade . . . . . . . . . . . . . . . . . . 232
15.3 eDirectory Restart Results in an Error Message on a Non-DSfW Server . . . . . . . . . . . . . . . . . . . . 232
15.4 Problem In Assigning IP Address For autoinst.xml-based Installations. . . . . . . . . . . . . . . . . . . . . . 232
15.5 iManager not Configured or Installed Properly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
15.6 eDirectory Restart Results in an Error Message on a Non-DSfW Server . . . . . . . . . . . . . . . . . . . . 233
15.7 The DEFAULT SLP Scope Gets added to the slp.conf File During an Upgrade to OES 11 SP2. . . 233
15.8 zlib-devel and zlib-devel-32bit Package Conflict During the Channel Upgrade to OES 11 SP2 . . . 234
15.9 The change_proxy_pwd.sh Script Fails to Synchronize Password . . . . . . . . . . . . . . . . . . . . . . . . . 234
15.10 OES Installation Fails Due to Encrypted OES Media URL in the autoinst.xml File . . . . . . . . . . . . . 235
15.11 The POODLE Security Vulnerability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
A OES 11 File and Data Locations 237
A.1 General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
A.2 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
B AutoYaST XML Tags 239
B.1 arkmanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
B.2 edirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
B.3 imanager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
B.4 iprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
B.5 ncpserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
B.6 ncs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
B.7 netstorage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
B.8 novell-afp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Contents 7
B.9 novell-cifs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
B.10 novell-dhcp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
B.11 novell-dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
B.12 novell-ifolder3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
B.13 novell-lum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
B.14 novell-quickfinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
B.15 novell-samba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
B.16 nss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
B.17 oes-ldap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
B.18 sms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
C Documentation Updates 263
8 OES 11 SP2: Installation Guide
About This Guide
This guide describes how to install, upgrade, and update Novell Open Enterprise Server (OES) 11
SP2. Except where specifically stated, the content of this guide applies to installing OES on a
computer’s physical hardware rather than on a Xen virtual machine host server.
Chapter 1, “What’s New or Changed in the OES Install,” on page 11
Chapter 2, “Preparing to Install OES 11 SP2,” on page 13
Chapter 3, “Installing OES 11 SP2 as a New Installation,” on page 43
Chapter 4, “Installing or Configuring OES 11 SP2 on an Existing Server,” on page 109
Chapter 5, “Upgrading to OES 11 SP2,” on page 115
Chapter 6, “Completing OES Installation or Upgrade Tasks,” on page 159
Chapter 7, “Updating (Patching) an OES 11 SP2 Server,” on page 165
Chapter 8, “Using AutoYaST to Install and Configure Multiple OES Servers,” on page 181
Chapter 9, “Installing OES as a VM Host Server,” on page 191
Chapter 10, “Installing, Upgrading, or Updating OES on a VM,” on page 195
Chapter 11, “Installing and Managing NetWare on a Xen-based VM,” on page 205
Chapter 12, “Disabling OES 11 Services,” on page 219
Chapter 13, “Reconfiguring eDirectory and OES Services,” on page 221
Chapter 14, “Security Considerations,” on page 229
Chapter 15, “Troubleshooting,” on page 231
Appendix A, “OES 11 File and Data Locations,” on page 237
Appendix B, “AutoYaST XML Tags,” on page 239
Appendix C, “Documentation Updates,” on page 263
Audience
This guide is intended for system administrators.
Feedback
We want to hear your comments and suggestions about this guide and the other documentation
included with Novell OES. Please use the User Comment feature at the bottom of each page of the
OES online documentation.
Documentation Updates
The latest version of the OES 11 SP2: Installation Guide is available at the Open Enterprise Server 11
documentation website.
About This Guide 9
Additional Documentation
For more information about See
Planning and implementing OES 11 SP2 OES 11 SP2: Planning and Implementation Guide
Migration from and coexistence with other products “Different Migration Tools” in the OES 11 SP2:
Migration T ool Administration Guide
Installing OES 11 SP2 on a Xen Virtual Host Server Chapter 10, “Installing, Upgrading, or Updating
OES on a VM,” on page 195
SLES 11 SP3 Deployment details SUSE LINUX Enterprise Server 11 SP3
Deployment Guide (https://www.suse.com/
documentation/sles11/book_sle_deployment/data/
book_sle_deployment.html)
SLES 11 SP3 Administration details SUSE LINUX Enterprise Server 11 SP3
Administration Guide (https://www.suse.com/
documentation/sles11/book_sle_admin/data/
book_sle_admin.html)
10 OES 11 SP2: Installation Guide
1
What’s New or Changed in the OES
1
1.1
Install
This section describes enhancements to Install for Novell Open Enterprise Server (OES) 11:
Section 1.1, “What’s New (OES 11 SP2),” on page 11
Section 1.2, “What’s New or Changed in OES 11 SP1 Install,” on page 12
Section 1.3, “What’s New or Changed in OES 11 Install,” on page 12
What’s New (OES 11 SP2)
In addition to bug fixes, the following enhancements and behavior changes are provided in OES 11
SP2:
Express Install
Beginning with OES 11 SP2, Express Install has been introduced to help you install OES 11 SP2 with
minimal user intervention. For more information, see “Typical and Custom OES Configuration” in the
OES 11 SP2: Installation Guide.
Cloning Post Install or Upgrade
Beginning with OES 11 SP2, you can clone an OES server after the installation or upgrade. For more
information, see “Cloning an OES Server Post OES Installation and Configuration” in the OES 11
SP2: Installation Guide.
NCPFS Package Dependency Replaced with Novell Client for Linux
Beginning with OES 11 SP2, the OES dependency on the NCPFS open source package has been
replaced with the Command Line Utilities for Novell Client,
is no longer supported or bundled.
novell-qtgui-cli
. The NCPFS package
Reconfiguring iManager
If iManager is not configured or installed properly, you can use the reconfiguration scripts to reinstall
it. For more information, see “Re-configuring iManager” in the OES 11 SP2: Installation Guide.
Interoperability with Partnering Vendors
Interoperability with some antivirus and Hierarchical Storage Management (HSM) partner products
has been improved in OES 11 SP2.
What’s New or Changed in the OES Install 11
1.2
What’s New or Changed in OES 11 SP1 Install
Unattended upgrade from OES 2 or OES 11 to OES 11 SP1 has been enhanced and has
undergone some changes. For more information, see “Using AutoYaST for an OES 11 SP2
Upgrade” in the OES 11 SP2: Installation Guide.
A single integrated ISO to install or upgrade OES 11 SP1 is now available. This ISO contains
both SLES 11 SP2 and OES 11 SP1.
Channel upgrade support is added in OES 11 SP1. It supports upgrade from OES 11 to OES 11
SP1.
1.3
What’s New or Changed in OES 11 Install
Novell Linux Volume Manager (NLVM) replaces the Enterprise Volume Management System
(EVMS).
Rug and Zen-updater are now replaced with zypper and PackageKit.
OpenWBEM has now been replaced with Small Footprint CIM Broker (SFCB) as the Web-Based
Enterprise Management system.
12 OES 11 SP2: Installation Guide
2
2
Preparing to Install OES 11 SP2
In preparation for the installation, perform the tasks and understand the information in the following
sections:
Section 2.1, “Before You Install,” on page 13
Section 2.2, “Meeting All Server Software and Hardware Requirements,” on page 13
Section 2.3, “NetIQ eDirectory Rights Needed for Installing OES,” on page 15
Section 2.4, “Installing and Configuring OES as a Subcontainer Administrator,” on page 15
Section 2.5, “Preparing eDirectory for OES 11 SP2,” on page 20
Section 2.6, “Deciding What Patterns to Install,” on page 25
Section 2.7, “Obtaining OES 11 SP2 Software,” on page 35
Section 2.8, “Preparing Physical Media for a New Server Installation or an Upgrade,” on page 35
Section 2.9, “Setting Up a Network Installation Source,” on page 36
Section 2.10, “Always Install OES as an Add-On Product,” on page 40
Section 2.11, “Install Only One Server at a Time,” on page 41
Section 2.12, “What's Next,” on page 41
2.1
2.2
2.2.1
Before You Install
Before you install Novell Open Enterprise Server 11 (OES 11 SP2), review the following information:
“Planning Your OES 11 SP2 Implementation” in the OES 11 SP2: Planning and Implementation
Guide
“Before You Install” in the OES 11 SP2: Readme
Meeting All Server Software and Hardware
Requirements
Before installing OES 11 SP2, ensure that your system meets the following requirements:
Section 2.2.1, “Server Software,” on page 13
Section 2.2.2, “Server Hardware,” on page 14
Server Software
As part of the OES 11 SP2 installation, you install SUSE Linux Enterprise Server 11 SP3.
IMPORTANT: OES 11 SP2 services were developed and tested on a default and fully-patched SLES
11 SP3 server base.
Preparing to Install OES 11 SP2 13
As you install OES 11 SP2, do not change any of the SLES 11 SP3 Base Technologies package
selections, such as Java support. Doing so can cause various problems, such as the installation
failing or one or more OES 11 SP2 services not working properly.
If you are installing on an existing SLES 11 SP3 server, be sure to verify that all of the default SLES
11 SP3 components are installed before attempting to install OES 11 SP2 services.
2.2.2
Server Hardware
Table 2-1 Server Hardware Requirements
System Component Minimum Requirements Recommended Requirements
Computer Any server-class computer that
runs with AMD64 or Intel*
EM64T processors.
Memory 1 GB of RAM 2 GB of RAM for the base system. Additional RAM
Free Disk Space 7 GB of available, unpartitioned
disk space
DVD Drive DVD drive if installing from
physical media
IMPORTANT: OES 11 SP2 is an add-on product
to SLES 11 SP3; it only runs on x86_64. Other
processors that are supported by SLES 11 SP3,
such as Itanium (IA64) and Intel x86(IA32), are not
supported for running OES services.
NOTE: Services such as iManager, SMS, and
NRM run in 32-bit mode on a 64-bit platform.
might be required depending on which OES
components are selected and how they are used.
10 GB of available, unpartitioned disk space.
Additional disk space might be required,
depending on which OES components are
selected and how they are used.
DVD drive if installing from physical media
Hard Drive 20 GB
Network Board Ethernet 100 Mbps
IP address
One static IP address
Subnet mask
Default gateway
Mouse N/A USB or PS/2
Server computer BIOS Using a DVD installation
source, prepare the BIOS on
your server computer so that it
boots from the DVD drive first.
Video Card and Monitor 1024 X 768 resolution or higher
with a minimum color depth of 8
bits (256 colors)
Although it is technically possible to run the
ncurses installation at a lower resolution, some
informational messages aren’t displayed because
text strings don’t wrap to the constraints of the
window.
NOTE: The RAM and disk space amounts shown here are for system components only. The OES
service components that you install might require additional RAM and disk space.
14 OES 11 SP2: Installation Guide
Be sure to complete the planning instructions in the OES 11 SP2: Planning and Implementation
Guide for each component that you install.
2.3
2.3.1
2.3.2
NetIQ eDirectory Rights Needed for Installing OES
Section 2.3.1, “Rights to Install the First OES Server in a Tree,” on page 15
Section 2.3.2, “Rights to Install the First Three Servers in an eDirectory Tree,” on page 15
Section 2.3.3, “Rights to Install the First Three Servers in any eDirectory Partition,” on page 15
Rights to Install the First OES Server in a Tree
To install an OES server in a tree, you must have rights to extend the schema, meaning that you need
Supervisor rights to the root of the tree.
You can extend the schema by using the Novell Schema Tool in YaST or by having a user with
Supervisor rights to the root of the eDirectory tree install the first OES server and the first instance of
each OES service that will be used into the tree. For more information, see Section 2.5.4, “Extending
the Schema,” on page 23.
Rights to Install the First Three Servers in an eDirectory
Tree
If you are installing the server into a new tree, the Admin user that is created during the OES
installation has full rights to the root of the tree. Using the account for user Admin allows the installer
to extend the eDirectory schema for OES as necessary. To install the first OES server in an
eDirectory tree, you must have the Supervisor right at the root of the eDirectory tree.
2.3.3
2.4
Rights to Install the First Three Servers in any eDirectory
Partition
By default, the first three servers installed in an eDirectory partition automatically receive a replica of
that partition. To install a server into a partition that does not already contain three replica servers, the
user must have either the Supervisor right at the root of the tree or the Supervisor right to the
container in which the server holding the partition resides.
Installing and Configuring OES as a Subcontainer
Administrator
IMPORTANT: The information explained in Section 2.3, “NetIQ eDirectory Rights Needed for
Installing OES,” on page 15 is prerequisite to the information contained in this section.
This section outlines the required eDirectory rights and explains how a subcontainer administrator
approaches various installation tasks.
Section 2.4.1, “Rights Required for Subcontainer Administrators,” on page 16
Section 2.4.2, “Providing Required Rights to the Subcontainer Administrator for Installing and
Managing Samba,” on page 18
Preparing to Install OES 11 SP2 15
Section 2.4.3, “Starting a New Installation as a Subcontainer Administrator,” on page 20
Section 2.4.4, “Adding/Configuring OES Services as a Different Administrator,” on page 20
2.4.1
Rights Required for Subcontainer Administrators
For security reasons, you might want to create one or more subcontainer administrators
(administrators that are in a container that is subordinate to the container that user Admin is in) with
sufficient rights to install additional OES servers, without granting them full rights to the entire tree.
A subcontainer administrator needs the rights listed in Table 2-2 to install an OES server into the tree.
These rights are typically granted by placing all administrative users in a Group or Role in eDirectory,
and then assigning the rights to the Group or Role. Sample steps for assigning the rights to a single
subcontainer administrator are provided as a general guide.
Table 2-2 Subcontainer Administrator Rights Needed to Install
Rights Needed Sample Steps to Follow
Supervisor right to itself 1. In iManager, click View Objects > the Browse tab, then browse to and
select the subcontainer administrator.
2. Click the administrator object, then select Modify Trustees.
3. Click the Assigned Rights link for the administrator object.
4. For the [All Attributes Rights] property, select Supervisor, then click Done
> OK.
Supervisor right to the
container where the server
will be installed
1. Browse to the container where the subcontainer administrator will install
the server.
2. Click the container object and select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] and [Entry rights] properties, select
Supervisor, then click Done > OK > OK.
Supervisor right to the W0
object located inside the KAP
object in the Security
container
Supervisor right to the
Security container when
installing the NMAS login
methods
16 OES 11 SP2: Installation Guide
1. Browse to Security > KAP.
2. In KAP, click W0 and select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] and [Entry rights] properties, select
Supervisor, then click Done > OK > OK.
If the subcontainer administrator will install the NMAS login methods:
1. Browse to and select Security.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] and [Entry rights] properties
Supervisor, then click Done > OK > OK.
, select
Rights Needed Sample Steps to Follow
Create right to its own
container (context)
Create right to the container
where the UNIX Config object
is located
Read right to the Security
container object for the
eDirectory tree
1. Browse to and select the container where you created the subcontainer
administrator.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [Entry Rights] property, select Create, then click Done > OK > OK.
1. Browse to and select the container where the UNIX Config object is
located. By default, this is the Organization object.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [Entry Rights] property, select Create, then click Done > OK > OK.
This is not needed if the Supervisor right was assigned because of NMAS.
If the subcontainer administrator won’t install the NMAS login methods, do the
following:
1. Browse to and select Security.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] property, select Read, then click Done > OK
> OK.
Read right to the
NDSPKI:Private Key attribute
on the Organizational CA
object (located in the Security
container)
Read and Write rights to the
UNIX Config object
1. Browse to Security and select the Organizational CA object.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the
Assigned Rights link for the administrator object.
5. Click the Add Property button.
6. Select NDSPKI:Private Key, then click OK.
The Read right should be automatically assigned.
7. Click Done > OK > OK.
1. Browse to and select the UNIX Config object.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] property, select Write (Read is already
selected), then click Done > OK > OK.
Preparing to Install OES 11 SP2 17
Rights Needed Sample Steps to Follow
2.4.2
Write right to the [All Attribute
Rights] property for the
admingroup object
1. Browse to and select the admingroup object.
2. Select Modify Trustees.
3. Click Add Trustee, browse to and select the subcontainer administrator,
then click OK.
4. Click the Assigned Rights link for the administrator object.
5. For the [All Attributes Rights] property, select Write (Compare and Read
are already selected), then click Done > OK > OK.
When you install DNS/DHCP into an existing tree with DNS/DHCP, see the following additional
guidelines:
For DNS, see “eDirectory Permissions ” in the OES 11 SP2: Novell DNS/DHCP Services for
Linux Administration Guide.
For DHCP, see “eDirectory Permissions ” in the OES 11 SP2: Novell DNS/DHCP Services for
Linux Administration Guide.
Providing Required Rights to the Subcontainer
Administrator for Installing and Managing Samba
Prior to installing any new OES Samba server in a tree, ensure that you provide supervisor rights to
the subcontainer administrator for the location mentioned in Table 2-3.
Table 2-3 Subcontainer Administrator Rights Needed to Manage Samba
Rights Needed Sample Steps to Follow
Supervisor rights to the container where the Linux
workstation object will be located
1. In iManager, click View Object s, then browse and
select the container where the OES Samba
server will be installed.
2. Click Actions > Modify Trustees.
3. On the Modify Trustees page, click Assigned
Rights next to the trustee name for which you
want to modify rights.
4. Click the desired container admin object to add it
to the Selected Objects section.
5. Click OK.
6. Select Property Name rights (All Attribute Rights
and Entry Rights) and assign Supervisor rights,
then click Done.
18 OES 11 SP2: Installation Guide
Rights Needed Sample Steps to Follow
Supervisor rights to the container where the Unix
config object will be located
Supervisor rights to the container where the Samba/
LDAP base context will be located
1. On the Novell iManager, click View Objects, then
in the Tree, browse and select the container
where Unix Config object is located.
2. Select the Unix Config object, then click Actions
> Modify trustees.
3. On the Modify Trustees page, click Assigned
Rights next to the trustee name for which you
want to modify rights.
4. Click the desired container admin object to add it
to the Selected Objects section.
5. Click OK.
6. Select Property Name rights (All Attribute Rights
and Entry Rights) and assign Supervisor rights,
then click Done.
1. On the Novell iManager, click View Objects, then
in the Tree, browse and select the container
where the Samba/LDAP base context will reside.
2. Select the Current Level tree object, then click
Actions > Modify trustees.
3. On the Modify Trustees page, click Assigned
Rights next to the trustee name for which you
want to modify rights.
4. Click the desired container admin object to add it
to the Selected Objects section.
5. Click OK.
6. Select Property Name rights (All Attribute Rights
and Entry Rights) and assign Supervisor rights,
then click Done.
Supervisor rights to the container where the Samba
proxy user will be installed
1. On the Novell iManager, click View Objects, then
in the Tree, browse and select the container
where the Samba proxy user context will be
installed.
2. Select the Samba proxy object, then click Actions
> Modify trustees.
3. On the Modify Trustees page, click Assigned
Rights next to the trustee name for which you
want to modify rights.
4. Click the desired container admin object to add it
to the Selected Objects section.
5. Click OK.
6. Select Property Name rights (All Attribute Rights
and Entry Rights) and assign Supervisor rights,
then click Done
.
Preparing to Install OES 11 SP2 19
2.4.3
Starting a New Installation as a Subcontainer Administrator
You can install a new OES server into an existing tree as a subcontainer administrator if you have the
following:
The rights described in “Rights Required for Subcontainer Administrators” on page 16
The rights described in “Providing Required Rights to the Subcontainer Administrator for
Installing and Managing Samba” on page 18
(If applicable) The rights described for the server installations in “NetIQ eDirectory Rights
Needed for Installing OES” on page 15
When you reach the eDirectory Configuration - Existing Tree page, enter your fully distinguished
name (FDN) and password. After verifying your credentials, the installation proceeds normally.
2.4.4
2.5
2.5.1
Adding/Configuring OES Services as a Different
Administrator
To add or configure OES services on an OES server that another administrator installed, see “Adding/
Configuring OES Services on a Server That Another Administrator Installed” on page 114.
Preparing eDirectory for OES 11 SP2
Section 2.5.1, “If Your Directory Tree Is Earlier than eDirectory 8.6,” on page 20
Section 2.5.2, “If Your LDAP Server Is Running NetWare 6.5 SP2 or Earlier,” on page 21
Section 2.5.3, “If Your Tree Has Ever Contained an OES 1 Linux Server with LUM and NSS
Installed,” on page 21
Section 2.5.4, “Extending the Schema,” on page 23
If Your Directory Tree Is Earlier than eDirectory 8.6
If you are installing an OES 11 SP2 server into an eDirectory tree that is earlier than eDirectory 8.6,
do the following before installing your first OES server in an existing NetWare tree:
1 Extend the schema by using Deployment Manager. See “Schema Update” in the NW65 SP8:
Installation Guide.
2 Ensure that the schema is synchronized throughout the tree from root:
2a Enter the following commands at the System Console prompt of the NetWare server with
the Master of root:
set DSTRACE=on
set DSTRACE=nodebug
set DSTRACE=+Schema
set DSTRACE=*SSD
set DSTRACE=*SSA
2b Toggle to the Directory Services screen and look for the message
2c On each server that holds a Master of a partition, enter the following commands at the
System Console prompt:
set DSTRACE=off
20 OES 11 SP2: Installation Guide
All Processed = YES.
set DSTRACE=nodebug
set DSTRACE=+Schema
set DSTRACE=*SS
2d Toggle to the Directory Services screen and look for the message
All Processed = YES.
2.5.2
2.5.3
If Your LDAP Server Is Running NetWare 6.5 SP2 or Earlier
If you are installing into an eDirectory tree that is using a NetWare server to supply LDAP, you should
upgrade the LDAP server that the OES installation will communicate with to NetWare 6.5 SP3 or later.
A server running NetWare 6.5 SP2 or earlier will probably abend.
If Your Tree Has Ever Contained an OES 1 Linux Server with
LUM and NSS Installed
Having NSS volumes on OES servers requires certain system-level modifications, most of which are
automatic. For more information, see “System User and Group Management in OES 11 SP2” in the
OES 11 SP2: Planning and Implementation Guide.
“NetStorage, X-Tier, and Their System Users” on page 21
“An NSS Complication” on page 21
“eDirectory Solves the Basic Problem” on page 22
“The OES 2 Solution: Standardizing the UIDs on all OES servers” on page 22
NetStorage, X-Tier, and Their System Users
By default, certain OES services, such as NetStorage, rely on a background Novell service named XTier.
To run on an OES server, X-Tier requires two system-created users (named
novlxregd
) and one system-created group that the users belong to (named
novlxsrvd
novlxtier
and
).
An NSS Complication
The two X-Tier users mentioned above, and their group, are created on the local system when X-Tier
is installed. For example, they are created when you install NetStorage, and their respective UIDs
and GID are used to establish ownership of the service’s directories and files.
For NetStorage to run, these X-Tier users and group must be able to read data on all volume types
that exist on the OES server.
As long as the server has only Linux traditional file systems, such as Ext3 and Reiser, NetStorage
runs well.
However, if the server has NSS volumes, an additional requirement is introduced. NSS data can only
be accessed by eDirectory users. Consequently, the local X-Tier users can’t access NSS data, and
NetStorage can’t run properly.
Preparing to Install OES 11 SP2 21
eDirectory Solves the Basic Problem
When NSS volumes are created on the server, the two X-Tier system users and their group are
moved to eDirectory and enabled for Linux User Management (LUM). See “Linux User Management:
Access to Linux for eDirectory Users” in the OES 11 SP2: Planning and Implementation Guide.
After the move to eDirectory, they can function as both eDirectory and POSIX users, and they no
longer exist on the local system.
The OES 2 Solution: Standardizing the UIDs on all OES servers
If your eDirectory tree has ever contained an OES 1 Linux server with NSS and LUM installed, do the
following on each server (including OES 2) that has NSS and LUM installed:
1 Log in as
id novlxregd
id novlxsrvd
The standardized X-Tier IDs are UID 81 for
novlxtier
2 If you see the following ID information, the X-Tier IDs are standardized and you can move to the
root
and open a terminal prompt. Then enter the following commands:
novlxregd
, UID 82 for
novlxsrvd
.
, and GID 81 for
next server:
uid=81(novlxregd) gid=81(novlxtier) groups=81(novlxtier)
uid=82(novlxsrvd) gid=81(novlxtier) groups=81(novlxtier),8(www)
If you see different IDs than those listed above, such as 101, 102, 103, etc., record the numbers
for both X-Tier users and the novlxtier group. You need these IDs to standardize the IDs on the
server.
3 Download the following script file:
fix_xtier_ids.sh (http://www.novell.com/documentation/oes2/scripts/fix_xtier_ids.sh)
4 Customize the template file by replacing the variables in angle brackets (<>) as follows:
<server_name>: The name of the server object in eDirectory.
Replace this variable with the server name.
For example, if the server name is myserver, replace <server_name> with myserver so that
the line in the settings section of the script reads
server=myserver
<context>: The context of the X-Tier user and group objects.
Replace this variable with the fully distinguished name of the context where the objects
reside.
For example, if the objects are an Organizational Unit object named servers, replace
ou=servers,o=company.
<admin fdn>: The full context of an eDirectory admin user, such as the Tree Admin, who
has rights to modify the X-Tier user and group objects.
Replace this variable with the admin name and context, specified with comma-delimited
syntax.
For example, if the tree admin is in an Organization container named company, the full
context is cn=admin,o=company and the line in the settings section of the script reads
admin_fdn="cn=admin,o=company"
22 OES 11 SP2: Installation Guide
<novlxregd_uid>: The UID that the system assigned to the local novlxregd user. It might or
might not be the same on each server, depending on whether the
successfully.
Replace this variable with the UID reported for the novlxregd user on this server as listed
when you ran the commands in Step 1 on page 22.
In the example script, the original UID is 101. It is changed to 81 in the third line of the script.
The sixth line changes the UID on all of the files and directories on the server that are
owned by the novlxregd user from 101 to 81.
<novlxsrvd_uid>: The UID that the system assigned to the local novlxsrvd user. It might
not be the same on each server, depending on whether the
successfully.
Replace this variable with the UID reported for the novlxsrvd user on this server as listed
when you ran the commands in Step 1 on page 22.
In the example script, the original UID is 103. It is changed to 82 in the fourth line of the
script. The seventh line changes the UID on all of the files and directories on the server that
are owned by the
<novlxtier_gid>: The GID that the system assigned to the local novlxtier group. It might not
be the same on each server, depending on whether the
Replace this variable with the GID reported for the novlxtier group on this server as listed
when you ran the commands in Step 1 on page 22.
In the example script, the original GID is 101. It is changed to 81 in the second line of the
script. The sixth and seventh lines change the GID from 101 to 81 for all of the files and
directories on the server that are owned by the
5 Make the script executable and run it on the server.
novlxsrvd
user from 103 to 82.
novlxtier
nssid.sh
group.
nssid.sh
nssid.sh
script ran
script ran successfully.
script ran
2.5.4
IMPORTANT: Changes to the X-Tier files are not reported on the terminal.
Error messages are reported, but you can safely ignore them. The script scans the entire file
system, and some files are locked because the system is running.
6 Repeat from Step 1 for each of the other servers in the same context.
Extending the Schema
An eDirectory tree must have its schema extended to accommodate OES 11 servers and services as
explained in the following sections:
“Who Can Extend the Schema?” on page 23
“Which OES 11 SP2 Services Require a Schema Extension?” on page 24
“Extending the Schema While Installing OES 11 SP2” on page 24
“Using the YaST Plug-In to Extend the Schema” on page 25
“Extending the Schema for Novell Cluster Services” on page 25
Who Can Extend the Schema?
Only an administrator with the Supervisor right at the root of an eDirectory tree can extend the tree’s
schema.
Preparing to Install OES 11 SP2 23
Which OES 11 SP2 Services Require a Schema Extension?
The following service schema extensions are included with OES 11 SP2.
A single asterisk (*) indicates a service that is either required for OES 11 SP2 servers or for the
default services that are installed on every OES 11 SP2 server.
Unmarked extensions are implemented the first time their respective services are installed, unless
the schema was previously extended using another method, such as the YaST plug-in (see “Using
the YaST Plug-In to Extend the Schema” on page 25).
NetIQ Directory Services*
Novell Linux User Management (LUM)*
Novell iPrint Services
Novell DHCP Services
Novell DNS Services
Novell NCP Server
Novell NetStorage
Novell Storage Services (NSS)
Novell SMS*
Novell iFolder
Novell Domain Services for Windows
NetIQ NMAS*
Novell CIFS
Novell Clustering
Novell Cluster Services requires you to extend the schema manually. Follow the instructions in
“Installing, Configuring, and Repairing Novell Cluster Services” in the OES 11 SP2: Novell
Cluster Services for Linux Administration Guide.
Novell Remote Manager
Novell Samba
Extending the Schema While Installing OES 11 SP2
The simplest way to extend the schema for OES 11 SP2 servers is to have a tree admin install the
first OES 11 SP2 server and the first instance of each OES 11 SP2 service that you plan to run on
your network.
After this initial installation, you can assign subcontainer admins with the required rights to install
additional servers and services. For more information on the required rights for the various OES
services, see “Rights Required for Subcontainer Administrators” on page 16.
24 OES 11 SP2: Installation Guide
Using the YaST Plug-In to Extend the Schema
If you want a subcontainer admin to install the first OES 11 SP2 server or the first instance of an OES
11 SP2 service in an existing tree, and you don’t want to grant that admin the Supervisor right to the
root of the tree, someone with the Supervisor right to root can extend the schema by using YaST from
any of the following locations:
An OES 11 SP2 server running in another tree
Install a fully patched SLES 11 SP3 server, then install OES 11 SP2 without installing any of the
services, followed by the
To run the Novell Schema Tool:
1 On the server’s desktop, click Computer and open the YaST Control Center.
2 Click Open Enterprise Server > Novell Schema Tool.
3 Depending on the installation method you used, you might be required to insert your OES 11
SP2 installation media.
4 On the NetIQ eDirectory Extension Utility page, specify the information for an eDirectory server
with a Read/Write replica of the Root partition.
Be sure to provide the correct information to authenticate as an admin user with the Supervisor
right at the root of the target tree. Otherwise, the schema extension fails.
5 Select all of the other services you plan to run on any of the OES 11 SP2 servers in the tree.
6 Click Next.
The schema is extended.
The YaST2 novell-schematool utility writes the schema event messages to the
novell/eDirectory/log/oes_schema.log
yast2 novell-schema
file on the server where the utility is running.
tool installation.
/var/opt/
2.6
Extending the Schema for Novell Cluster Services
If you want a subcontainer administrator to install the first instance of Novell Cluster Services in a
tree, you can extend the schema by following the instructions in “Installing, Configuring, and
Repairing Novell Cluster Services” in the OES 11 SP2: Novell Cluster Services for Linux
Administration Guide.
Deciding What Patterns to Install
A default SLES 11 SP3 installation has the following base technology, graphical environment, and
primary function patterns selected for installation. With the exception explained in the two Important
notes below, you can accept or deselect these patterns and install additional patterns as desired.
Preparing to Install OES 11 SP2 25
Table 2-4 Standard SLES 11 SP3 Installation Patterns
Pattern Description
Server Base System Consists of all packages that are common to all Novell SUSE Linux
Enterprise products. Also provides a Linux Standard Base 3.0 compliant
runtime environment.
This pattern is selected for installation by default.
IMPORTANT: You must either install this pattern or the Common Code
Base pattern.
Common Code Base The largest system. It includes all packages available with SUSE Linux,
except those that would result in dependency conflicts.
IMPORTANT: You must either install this pattern or the Server Base
System pattern.
Novell AppArmor Novell AppArmor is an open source Linux application security framework
that provides mandatory access control for programs, protecting against
the exploitation of software flaws and compromised systems. AppArmor
includes everything you need to provide effective containment for
programs (including those that run as
and even zero-day attacks. AppArmor offers an advanced tool set that
largely automates the development of per-program application security so
that no new expertise is required.
root
) to thwart attempted exploits
This pattern is selected for installation by default.
GNOME Desktop Environment The GNOME desktop environment is an intuitive and attractive desktop for
users. The GNOME development platform is an extensive framework for
building applications that integrate into the rest of the desktop.
This pattern is selected for installation by default.
X Window System In continuous use for over 20 years, the X Window System provides the
only standard platform-independent networked graphical window system
bridging the heterogeneous platforms in today's enterprise: from network
servers to desktops, thin clients, laptops, and handhelds, independent of
operating system and hardware.
This pattern is selected for installation by default.
Print Server Sets up a print server to host print queues so that they can be accessed
by other computers on the same network, including machines running
Microsoft Windows operating systems. The print server can accept print
jobs from client computers and direct them to locally attached printers or to
network printers. LPD, CUPS, and SMB print servers and queues are
supported.
This pattern is selected for installation by default.
The OES add-on installation includes the following OES Services patterns:
26 OES 11 SP2: Installation Guide
Table 2-5 OES Services Pattern Descriptions
Pattern Description
Novell AFP
Novell Archive and
Version Services
A Novell AFP server allows Macintosh clients to access data stored on NSS
volumes in the same way they access data on a Mac OS X server.
This pattern selects and installs these services:
Novell Backup / Storage Management Services (SMS)
NetIQ eDirectory
Novell Storage Services (NSS)
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Novell NCP Server
This pattern cannot be installed on the same server as these services:
Novell Domain Services for Windows
Novell Archive and Version Services systematically captures and stores versions of
your network files in an archive database, on a schedule that you determine. Users
can search for a previous version of a file and quickly restore it.
This pattern selects and installs these services:
Novell Backup/Storage Management Services (SMS)
NetIQ eDirectory
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Novell Storage Services (NSS)
Novell NCP Server
Novell Backup/Storage
Management Services
(SMS)
This pattern cannot be installed on the same server as these services:
Novell Domain Services for Windows
The Novell backup infrastructure (called Storage Management Services or SMS)
provides backup applications with the framework to develop a complete backup
and restore solution.
SMS helps back up file systems (such as NSS) or application data (such as data
from GroupWise) on NetWare and SUSE Linux Enterprise Server (SLES) to
removable tape media or other media for off-site storage. It provides a single
consistent interface for all file systems and applications across NetWare and
SLES.
This pattern selects and installs these services:
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Preparing to Install OES 11 SP2 27
Pattern Description
Novell CIFS CIFS (Common Internet File System) is a network sharing protocol. Novell CIFS
enables Windows, Linux, and UNIX client workstations to copy, delete, move, save,
and open files on an OES 11 SP2 server. CIFS allows read and write access from
multiple client systems simultaneously.
This pattern selects and installs these services:
Novell Backup / Storage Management Services (SMS)
NetIQ eDirectory
Novell Storage Services (NSS)
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Novell NCP Server
This pattern cannot be installed on the same server as these services:
Novell Domain Services for Windows
Novell Samba
Novell Cluster Services
(NCS)
Novell Cluster Services is a server clustering system that ensures high availability
and manageability of critical network resources including data, applications, and
services. It is a multinode clustering product for Linux that is enabled for NetIQ
eDirectory and supports failover, failback, and migration (load balancing) of
individually managed cluster resources.
Novell Cluster Services lets you add Linux nodes to an existing NetWare 6.5
cluster without bringing down the cluster, or it lets you create an all-Linux cluster.
With a mixed cluster, you can migrate services between OS kernels, and if services
are alike on both platforms (such as NSS), you can set the services to fail over
across platforms.
Using Novell Cluster Services with iSCSI technologies included in OES, you can
build inexpensive clustered SANs on commodity gigabit Ethernet hardware. You
can leverage existing hardware into a high availability solution supporting Linux
and NetWare clusters.
This pattern selects and installs these services:
Novell Backup/Storage Management Services (SMS)
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
This pattern cannot be installed on the same server with these services:
High Availability
28 OES 11 SP2: Installation Guide
Pattern Description
Novell DHCP Novell DHCP (Dynamic Host Configuration Protocol) uses eDirectory to provide
configuration parameters to client computers and integrate them into a network.
The eDirectory integration lets you have centralized administration and
management of DHCP servers across the enterprise and lets you set up DHCP
subnet replication via NetIQ eDirectory.
This pattern selects and installs these services:
Novell Backup/Storage Management Services (SMS)
NetIQ eDirectory
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Novell DNS Novell DNS uses NetIQ eDirectory to deliver information associated with domain
names, in particular the IP address.
This eDirectory integration lets you have centralized administration and
management of DNS servers across the enterprise and lets you set up a DNS zone
via NetIQ eDirectory.
This pattern selects and installs these services:
Novell Backup/Storage Management Services (SMS)
NetIQ eDirectory
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Preparing to Install OES 11 SP2 29
Pattern Description
Novell Domain Services
for Windows
Novell Domain Services for Windows provides seamless cross-authentication
capabilities between Windows/Active Directory and Novell OES 11 SP2 servers. It
is a suite of integrated technologies that removes the need for the Novell Client
when logging on and accessing data from Windows workstations in eDirectory
trees. This technology simplifies the management of users and workstations in
mixed Novell-Microsoft environments.
This pattern selects and installs these services:
Novell Backup / Storage Management Services (SMS)
NetIQ eDirectory
Novell DNS
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
Novell Storage Services (NSS)
Novell NCP Server
This pattern cannot be installed on the same server as these services:
Novell Samba
Novell CIFS
Novell AFP
Novell Archive and Version Services
Novell FTP
Novell iFolder
Novell NetStorage
Novell Pre-Migration Server
Novell QuickFinder
NetIQ eDirectory NetIQ eDirectory services are the foundation for the world's largest identity
30 OES 11 SP2: Installation Guide
management, high-end directory service that allows businesses to manage
identities and security access for employees, customers, and partners. More than
just an LDAP data store, eDirectory is the identity foundation for managing the
relationships that link your users and their access rights with corporate resources,
devices, and security policies.
This pattern selects and installs these services:
Novell Backup/Storage Management Services (SMS)
Novell Linux User Management (LUM)
Novell Remote Manager (NRM)
This pattern cannot be installed on the same server as these services:
OpenLDAP
Loading...