1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. OES 11 SP2
  6. Installation manual

Novell OES 11 SP2 Installation Manual

Novell open enterprise server 11 sp2 installation guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
www.novell.com/documentation

Installation Guide

Open Enterprise Server 11 SP2
January 2014

Advertisement

Table of Contents
loading

Related Manuals for Novell OES 11 SP2

Summary of Contents for Novell OES 11 SP2

  • Page 1: Installation Guide

    Installation Guide Open Enterprise Server 11 SP2 January 2014...

  • Page 2: Legal Notices

    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.

  • Page 3: Table Of Contents

    Preparing eDirectory for OES 11 SP2 ........
  • Page 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 .

  • Page 5: Contents

    Upgrading OES 11 SP1 to OES 11 SP2 Using SMT ......153...
  • Page 6 10.4.4 Completing the OES 11 SP2 VM Guest Installation ......201 10.5 Upgrading an OES 2 VM Guest to OES 11 SP2 .

  • Page 7: Contents

    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 .
  • Page 8 B.14 novell-quickfinder ........

  • Page 9: About This Guide

    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...

  • Page 10: Additional Documentation

    “Different Migration Tools” in the OES 11 SP2: Migration Tool 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/...

  • Page 11: What's New Or Changed In The Oes Install

    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”...

  • Page 12: What's New Or Changed In Oes 11 Sp1 Install

     Channel upgrade support is added in OES 11 SP1. It supports upgrade from OES 11 to OES 11 SP1. 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.

  • Page 13: Preparing To Install Oes 11 Sp2

    Section 2.2.2, “Server Hardware,” on page 14 2.2.1 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.

  • Page 14: Server Hardware

    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.

  • Page 15: Netiq Edirectory Rights Needed For Installing Oes

    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.

  • Page 16: Rights Required For Subcontainer Administrators

    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. OES 11 SP2: Installation Guide...
  • Page 17 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...

  • Page 18: Providing Required Rights To The Subcontainer Administrator For Installing And Managing Samba

    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 ”...
  • Page 19 Rights Needed Sample Steps to Follow Supervisor rights to the container where the Unix 1. On the Novell iManager, click View Objects, then config object will be located in the Tree, browse and select the container where Unix Config object is located.

  • Page 20: Starting A New Installation As A Subcontainer Administrator

    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: Extend the schema by using Deployment Manager.

  • Page 21: If Your Ldap Server Is Running Netware 6.5 Sp2 Or Earlier

    “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 X- Tier. To run on an OES server, X-Tier requires two system-created users (named novlxsrvd and ) and one system-created group that the users belong to (named novlxtier ).
  • Page 22 “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.

  • Page 23: 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 ...
  • Page 24 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.

  • Page 25: Deciding What Patterns To Install

    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...
  • Page 26 Table 2-4 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.
  • Page 27 Table 2-5 Pattern Description Novell AFP 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: ...
  • Page 28 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.
  • Page 29  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.
  • Page 30 Windows 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.
  • Page 31  Novell Domain Services for Windows Novell iFolder Novell iFolder 3.9 is a simple and secure storage solution that increases user productivity by enabling users to back up, access, and manage their personal files from anywhere, at any time. This pattern selects and installs these services: ...
  • Page 32 Novell Backup/Storage Management Services (SMS)  Novell Remote Manager (NRM) Novell NCP Server / Novell NCP Server for Linux enables support for login scripts, mapping drives to Dynamic Storage OES servers, and other services commonly associated with Novell Client access. Technology This means that Windows users with the Novell Client installed can be seamlessly transitioned to file services on OES.
  • Page 33  Novell Domain Services for Windows Novell Pre-Migration A Novell Pre-Migration Server is not actually a service. Rather, it is a special- Server purpose server—the target of a Server ID Transfer Migration. Selecting this option causes this server to be installed without an eDirectory replica, thus preparing it to assume the identity of another server that you plan to decommission.
  • Page 34 Novell Remote Manager lets you securely access and manage one or more (NRM) servers from any location through a standard Web browser. You can use Novell Remote Manager to monitor your server's health, change the configuration of your server, or perform diagnostic and debugging tasks.

  • Page 35: Obtaining Oes 11 Sp2 Software

    Open Enterprise Server. For more information, see “Customizing the Software Selections” on page 52 “Installing or Configuring OES 11 SP2 on an Existing Server” on page 109. Obtaining OES 11 SP2 Software For information on obtaining OES software, see “Getting and Preparing OES 11 SP2...

  • Page 36: Setting Up A Network Installation Source

    Files needed 64-bit server with DVD drive  SLES 11 SP3 DVD ISO (SLES-11-SP3-DVD- x86_64-GM-DVD1.iso)  OES 11 SP2 DVD ISO (OES11-SP2-addon- x86_64-DVD1.iso)  Integrated ISO that has SLES 11 SP3 and OES 11 SP2 (OES11-SP2-addon_with_SLES11-SP3- x86_64-DVD.iso) These ISO files can be downloaded from the OES 11 SP2 download page (http://download.novell.com/...
  • Page 37 This DVD will be the network installation boot DVD. With these steps completed, you are ready to perform a new installation or upgrade using a network installation source. See “Starting the OES 11 SP2 Installation” on page 44 “Upgrading to OES 11 SP2” on page 115.

  • Page 38: Netware As A Network Installation Source Server

    NetWare 6.5 SP8 server.  “Prerequisites” on page 39  “Copy the Files and Mount Them as NSS Volumes” on page 39 “Create the Boot DVDs” on page 40  OES 11 SP2: Installation Guide...
  • Page 39 Prerequisites You need the following:  A NetWare 6.5 SP8 server accessible on the network where you plan to install the OES 11 SP2 servers with the following:  6 GB free disk space on the server  The Apache Web Server for NetWare installed and running ...

  • Page 40: Windows As A Network Installation Source Server

    You must always install OES by adding it as an add-on product while running the YaST install. This is not the same as adding the OES installation media as an installation source. Failure to do this will prevent the server from registering as an OES 11 SP2 server with the Novell Customer Center.

  • Page 41: Install Only One Server At A Time

    “Using AutoYaST to Install and Configure Multiple OES Servers” on page 181  “Installing, Upgrading, or Updating OES on a VM” on page 195  “Installing or Configuring OES 11 SP2 on an Existing Server” on page 109 Preparing to Install OES 11 SP2...
  • Page 42 OES 11 SP2: Installation Guide...

  • Page 43: Installing Oes 11 Sp2 As A New Installation

    TIP: You can also use the integrated iso ( OES11-SP2-addon_with_SLES11-SP3-x86_64-DVD.iso ) for OES 11 SP2 installation. This ISO has both OES 11 SP2 and SLES 11 SP3. When you use this ISO, you are not require to select OES as an add-on product in the Installation Mode screen.

  • Page 44: Linux Software Raids

    RAIDs) for devices that you plan to use for storage objects that are managed by NSS management tools. The Novell Linux Volume Manager (NLVM) utility and the NSS Management Utility (NSSMU) list Linux software RAID devices that you have created by using Linux tools. Beginning with Linux Kernel 3.0 in OES 11 SP1, NLVM and NSSMU can see these devices, initialize them, and allow you...

  • Page 45: Installing From A Network Source With Dhcp

    “Specifying the Installation Settings for the SLES Base and OES Installation” on page “Specifying Configuration Information” on page “Finishing the Installation” on page 106. Complete the server setup by following the procedures in “Completing OES Installation or Upgrade Tasks” on page 159. Installing OES 11 SP2 as a New Installation...

  • Page 46: Installing From A Network Source Without Dhcp

    (Conditional) Depending on the protocol you specified, you might see additional screens for FTP or HTTP. Select the options that are appropriate for your network, then continue with Step Specify the path to your installation source on the network installation server, then press Enter. OES 11 SP2: Installation Guide...

  • Page 47: Specifying The Installation Mode

    Next:  New Installation  Include Add-On Products from Separate Media NOTE: If you have used the integrated iso ( OES11-SP2-addon_with_SLES11-SP3-x86_64- ) for the OES 11 SP2 installation, do not select Include Add-On Products from Separate DVD.iso Media. Continue with Section 3.5, “Specifying the Add-On Product Installation Information,”...

  • Page 48: Specifying The Add-On Product Installation Information

    Next and supply the required information. Read and accept the Novell Open Enterprise Server 11 SP2 license agreement, then click Next. Confirm that the Add-On Product Installation page shows the correct path to the OES media, then click Next.

  • Page 49: Setting Up Disk Partitions

    This contains system logs and should therefore be a separate partition to avoid impacting /var system and service stability because of a disk-full condition. Define this partition as 4 GB or more. Installing OES 11 SP2 as a New Installation...
  • Page 50 NSS on the System Disk For OES, Novell Storage Services (NSS) volumes can be used only as data volumes, not as system volumes. Additionally, they cannot be created as part of the install process.
  • Page 51 First logical partition within the extended partition on that disk /dev/hda5 Second SCSI disk /dev/sdb Third primary partition on the second SCSI disk /dev/sdb3 Disk Partition Statistics Use the following commands to get information about system storage usage: Installing OES 11 SP2 as a New Installation...

  • Page 52: Customizing The Software Selections

    The Open Enterprise Server add-on adds the OES Services category of patterns to the base software selection categories offered by the SLES 11 SP3 installation. OES Services include patterns that contain Novell services or products such as Novell DNS and DHCP services, iPrint, or iManager.
  • Page 53 You must install at least one of the SLES Base Technologies patterns. Selecting a pattern automatically selects the other patterns that it depends on to complete the installation. Installing OES 11 SP2 as a New Installation...

  • Page 54: Accepting The Installation Settings

    For installations using a network installation source, you can remove the network boot DVD (SLES 11 SP3 DVD 1) from the DVD drive. For installations using a DVD installation source, leave the DVD in the DVD drive. After the server reboot, proceed with “Specifying Configuration Information” on page OES 11 SP2: Installation Guide...

  • Page 55: Specifying Configuration Information

    Section 3.8.3, “Specifying Network Configuration Settings,” on page 56  Section 3.8.4, “Testing the Connection to the Internet,” on page 59  Section 3.8.5, “Specifying Novell Customer Center Configuration Settings,” on page 59  Section 3.8.6, “Updating the Server Software,” on page 61 ...

  • Page 56: Specifying Network Configuration Settings

    Click OK to return to the Detailed Settings list. Click Next to return to the Network Card Configuration Overview page. Complete Step 2 through Step 6 for each network board, then click Next to return to the main Network Configuration page. OES 11 SP2: Installation Guide...
  • Page 57 Novell AFP  Novell Archive and Version Services  26029 Novell CIFS  636 (secure LDAP) IMPORTANT: The scripts that manage the common proxy user require port 636 for secure LDAP communications. Installing OES 11 SP2 as a New Installation...
  • Page 58 When the firewall is disabled, the status for Firewall should read Firewall is disabled. Verify that the settings on the Network Configuration page are set as desired, then click Next to save the configuration. Continue with “Testing the Connection to the Internet” on page OES 11 SP2: Installation Guide...

  • Page 59: Testing The Connection To The Internet

    Specifying Novell Customer Center Configuration Settings OES 11 SP2 requires that the SLES 11 SP3 base be updated prior to installing and configuring OES 11 SP2 services. If not, some OES services, such as Novell FTP, will not function properly after the installation and will need to be configured again after the SLES patches are applied.
  • Page 60 On the Novell Customer Center Registration page, specify the required information in the following fields, then click Submit: Field Information to Specify Email Address The email address for your Novell Login account. Confirm Email Address The same email address for your Novell Login account...

  • Page 61: Updating The Server Software

    3.8.6 Updating the Server Software When you have a successful connection to the Internet and have registered the server in the Novell Customer Center, the server displays the Online Update page. You must run the online update now for a successful OES installation.
  • Page 62 On the page that shows that updates are available, click Accept. The check marks that are shown on the summary portion of the page are the patches that will be installed on your system after clicking Accept. When you see the following message, click Next. OES 11 SP2: Installation Guide...

  • Page 63: Specifying Service Configuration Settings

    Because the server was rebooted during the installation, the default settings for CA management lost the root password as indicated by the red text under CA Management. Reset the password for root . Installing OES 11 SP2 as a New Installation...
  • Page 64 For more information about OES certificate management, see “Certificate Management” in OES 11 SP2: Planning and Implementation Guide.  OpenLDAP Server: Do not enable this option. On OES servers, NetIQ eDirectory LDAP server replaces the SLES 11 SP3 OpenLDAP server.

  • Page 65: Typical And Custom Oes Configuration

    3.8.8 Typical and Custom OES Configuration Beginning with OES 11 SP2, you can configure OES in two methods: Typical Configuration and Custom Configuration. The Typical Configuration is also called as Express Install. It helps to install OES 11 SP2 with minimal user intervention and the Custom Configuration is the detailed usual method to configure OES.

  • Page 66: Custom Configuration

    This is the normal method of installing and configuring OES by providing every configuration detail that OES requires instead of using the default configuration details. Custom configuration is explained in detailed in Section 3.8.9, “Specifying LDAP Configuration Settings,” on page OES 11 SP2: Installation Guide...

  • Page 67: Specifying Ldap Configuration Settings

    Do the following for each server you want to add: Click Add. On the next page, specify the following information for the server to add, then click Add.  IP address Installing OES 11 SP2 as a New Installation...
  • Page 68  LDAP port and secure LDAP port When all of the LDAP servers that you want to specify are listed, click Next. Verify that the Novell Open Enterprise Server Configuration page displays the settings that you expected, then click Next.

  • Page 69: Specifying Edirectory Configuration Settings

    Use this in environments that have not established SLP DAs (Directory Agents). IMPORTANT: If you select this option, you must disable the firewall for SLP to work correctly. Multicast creates a significant amount of network traffic and can reduce network throughput. Installing OES 11 SP2 as a New Installation...
  • Page 70 15 minutes or more. Continue with “Specifying SLP Configuration Options” on page For more information on time synchronization, see “Implementing Time Synchronization” in the 11 SP2: Planning and Implementation Guide. OES 11 SP2: Installation Guide...
  • Page 71  The ports to use for servicing LDAP requests The default ports are 389 (non-secure) and 636 (secure). IMPORTANT: The scripts that manage the common proxy user introduced in OES 11 SP2 require port 636 for secure LDAP communications.  The ports to use for providing access to the iMonitor application The default ports are 8028 (non-secure) and 8030 (secure).
  • Page 72 In the eDirectory Tree Name field, specify a name for the eDirectory tree you want to join. On OES servers, services that provide HTTPS connectivity are configured to use either of the following:  An eDirectory certificate issued by the Novell International Cryptographic Infrastructure (NICI)  The YaST self-signed common server certificate created in Step 2 on page 64 Self-signed certificates provide minimal security and limited trust.
  • Page 73 Guide.  Select Enable NMAS-based login for LDAP authentication to enforce the use of a single- secure password for all Novell and partner products. The Secure Password Manager of the NMAS module manages this universal password implementation. On the eDirectory Configuration - Existing Tree Information page, specify the required information: ...
  • Page 74 On the NetIQ Modular Authentication Services page, select all of the login methods you want to install. IMPORTANT: The NMAS client software must be installed on each client workstation where you want to use the NMAS login methods. The NMAS client software is included with the Novell Client software. OES 11 SP2: Installation Guide...
  • Page 75 For information about this option, see “Common Proxy User” in the OES 11 SP2: Planning and Implementation Guide. On the OES Common Proxy User Information page, specify the configuration settings for this user, then click Next. Installing OES 11 SP2 as a New Installation...
  • Page 76 For example, ou=acap,o=novell . Where ou is the organization unit, acap is the organization unit name, o is the organization, and novell is the new organization name. For an existing tree, click Browse and select the container where the Common Proxy User must be created.

  • Page 77: Configuring Oes Services

    “Configuring OES Services” on page 3.8.11 Configuring OES Services After you complete the LDAP configuration or the eDirectory configuration, the Novell Open Enterprise Server Configuration summary page is displayed, showing all of the OES components that you installed and their configuration settings.

  • Page 78: Configuration Guidelines For Oes Services

    Novell Storage Services  When you have finished the configuration of a component, you are returned to the Novell Open Enterprise Server Configuration summary page. If you want to skip the configuration of a specific component and configure it later, click Enabled in the Configure is enabled status to change the status to Reconfigure is disabled.
  • Page 79  “Novell Samba” on page 104  “Novell Storage Services (NSS)” on page 105 Service Configuration Caveats Keep the following items in mind as you configure the OES 11 SP2: Caveats for Configuring OES Services Table 3-3 Issue Guideline Software Selections...

  • Page 80: Ldap Configuration For Open Enterprise Services

    Some contexts must be specified using periods (.) and others using commas (,). However, eDirectory supports names like cn=juan\.garcia.ou=users.o=novell. The period (.) inside a name component must be escaped. When using NDAP format (dot), you must escape all embedded dots. For example: cn=admin.o=novell\.provo...

  • Page 81: Novell Afp Services

    Directory Server Address: The IP address of the eDirectory server.  Proxy user name with context: Specify the FQDN of the eDirectory containers that contain AFP users, for example ou=afp_users.o=novell. In an existing tree, you can select the context using Browse. For additional configuration instructions, see “Installing and Setting Up...

  • Page 82: Novell Cifs For Linux

    For additional configuration instructions, see “Setting Up Archive and Version Services ” in the 11 SP2: Novell Archive and Version Services Administration Guide. Novell Backup/Storage Management Services (SMS) Novell Backup/Storage Management Services Parameters and Values Table 3-7 Page and Parameters SMS Configuration ...

  • Page 83: Novell Cluster Services

    For example: cn=user, o=novell NOTE: This user is granted rights to read the passwords of any users, including non-CIFS users, that are governed by any of the password policies you select in the Novell CIFS Service Configuration page. ...
  • Page 84 Page and Parameters Before you configure a node for a Novell Cluster Services cluster, ensure that you have satisfied the prerequisites and have the necessary Administration rights described in “Planning for Novell Cluster Services” in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

  • Page 85: Novell Dhcp Services

    Page and Parameters Before you configure a node for a Novell Cluster Services cluster, ensure that you have satisfied the prerequisites and have the necessary Administration rights described in “Planning for Novell Cluster Services” in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.
  • Page 86  Do Not Chase Referral: Select this option to ignore LDAP referrals. Default: Chase referral Novell DHCP LDAP and Secure Channel Configuration  eDirectory Server Address or Host Name: The IP address shown is the default LDAP server for this service. If you do not want to use the default, select a different LDAP server in the list.
  • Page 87 LDAP User Password: Type a password for the LDAP user.  LDAP Port for DHCP Server: Select a port for the LDAP operations to use. IMPORTANT: The scripts that manage the common proxy user introduced in OES 11 SP2 require port 636 for secure LDAP communications. Default: 636 ...

  • Page 88: Novell Dns Services

    For more information on proxy user and password management, see “Planning Your Proxy Users” in the OES 11 SP2: Planning and Implementation Guide. Default: The password that you specified for the OES server you are installing.  Credential Storage Location: Specify where the DNS proxy user’s credentials are to be stored.

  • Page 89: Novell Domain Services For Windows

    Locator, Root Server Info, Group and Proxy User contexts.  Existing Novell DNS Server Address: If you have enabled the previous option, you can type the IP address of an NCP server (must be up and running) that is hosting the existing DNS server.
  • Page 90 Be sure to carefully check all of the service configuration summaries on the Novell Open Enterprise Server Configuration summary screen. If any of the services don’t show the eDirectory change you made, click the service link and modify the configuration manually. Otherwise, your installation will fail.
  • Page 91 This option appears only if you are joining an existing tree. IMPORTANT: The scripts that manage the common proxy user introduced in OES 11 SP2 require port 636 for secure LDAP communications. Default: 389 (LDAP), 636 (Secure LDAP) ...
  • Page 92 For more information, see “Time Services” in the OES 11 SP2: Planning and Implementation Guide.  Use Local Clock: Alternatively, you can select Use Local Clock to designate the server’s hardware clock as the time source for your eDirectory tree.
  • Page 93 It is enabled for input only when you configure SLP to use an existing Directory Agent. NetIQ Modular Authentication Services IMPORTANT: NMAS client software (included with Novell Client software) must be installed on each client workstation where you want to use the NMAS login methods.

  • Page 94: Novell Ftp Services

    If you want to use an NSS volume to store iFolder data, you must reconfigure iFolder after the initial OES installation. To reconfigure, use Novell iManager to create an NSS volume, then go to YaST > Open Enterprise Server > Install and Configure Open Enterprise Services and select iFolder 3.9 to enter new information.
  • Page 95 Private URL: Specify the private URL corresponding to the iFolder Enterprise Server to allow communication between the servers within the iFolder domain. The private URL and the public URL can be the same. Default: The OES server’s IP address Installing OES 11 SP2 as a New Installation...
  • Page 96 If you are installing into an existing tree, you must enter the password of an admin user in the tree. Default: The first server selected in the LDAP Configuration list of servers OES 11 SP2: Installation Guide...
  • Page 97 For example, o=acme, o=acme2, or o=acme3 If no context is specified, only the iFolder administrative user is provisioned for services during the install. Default: The server context you specified while configuring eDirectory. Installing OES 11 SP2 as a New Installation...
  • Page 98 The Host or IP Address of the iFolder Server That Will Be Used by the iFolder Web Application: The iFolder Web Admin application manages this host. Default: The IP address of the OES server you are installing OES 11 SP2: Installation Guide...

  • Page 99: Novell Imanager

    This is the user that has full administrative rights to perform operations in iManager. To change this configuration, you must change the eDirectory configuration. For additional configuration instructions, see “Installing iManager” in the NetIQ® iManager Installation Guide. Installing OES 11 SP2 as a New Installation...

  • Page 100: Novell Iprint

    For information about specifying multiple LDAP servers for Linux User Management (LUM), see “Configuring a Failover Mechanism” in the OES 11 SP2: Novell Linux User Management Administration Guide. Default: The first server selected in the LDAP Configuration list of servers...
  • Page 101 Using the default selection changes the umask setting in from 022 to 077. /etc/login.defs Default: Selected Linux User Management Configuration (2) Installing OES 11 SP2 as a New Installation...

  • Page 102: Novell Netstorage

     sfcbd: yes This is selected by default because it is used by many of the OES services such as NSS, SMS, Novell Remote Manager, and Samba. To access iManager and NRM, you must enable SFCB.  gdm: no ...

  • Page 103: Novell Quickfinder

    Page and Parameters Novell QuickFinder Admin User  Novell QuickFinder Admin User Type: Make the QuickFinder administrator a LUM-enabled eDirectory user or a local Linux user.  Local: Select this option to give QuickFinder Server administration rights to a local Linux user (the default is the user if no other local users exist).

  • Page 104: Novell Remote Manager

    Novell QuickFinder Admin Password  eDirectory Admin Name: Specified on the previous page.  Novell QuickFinder Admin User Type: If a different admin user was created, specify a password. For additional configuration instructions, see “Installing QuickFinder Server” in the OES 11 SP2: Novell QuickFinder Server 5.0 Administration...
  • Page 105 Default: The server hostname concatenated with the LDAP Admin Name you entered for this server,. cn=myserveradmin,o=organization. For additional configuration instructions, see “Installing and Configuring Novell Storage Services” in OES 11 SP2: NSS File System Administration Guide for Linux. Installing OES 11 SP2 as a New Installation...

  • Page 106: Finishing The Installation

    In the Address field of your web browser, enter the following URL: http://IP_or_DNS Replace IP_or_DNS with the IP address or DNS name of your OES server. You should see a web page similar to the following: OES 11 SP2: Installation Guide...

  • Page 107: What's Next

    “What's Next” on page 107. 3.11 What's Next After you complete the initial installation, complete any additional tasks you might need to perform. “Completing OES Installation or Upgrade Tasks” on page 159. Installing OES 11 SP2 as a New Installation...
  • Page 108 OES 11 SP2: Installation Guide...

  • Page 109: Installing Or Configuring Oes 11 Sp2 On An Existing Server

    Installing or Configuring OES 11 SP2 on an Existing Server After installing or upgrading to Novell Open Enterprise Server (OES 11 SP2), you can also install additional products or services and configure them to work in the new environment. If you have installed or upgraded a server to SUSE Linux Enterprise Server (SLES) 11 SP3, you can also add OES 11 SP2 services to the server.

  • Page 110: Don't Install Oes While Running The Xen Kernel

    Don’t Install OES While Running the Xen Kernel If you are adding supported OES 11 SP2 components to a server that is running the Xen kernel, you must reset the boot loader to boot the standard kernel before adding the OES 11 SP2 components.
  • Page 111 IMPORTANT: If you need to reconfigure eDirectory, we recommend that you use tools provided by eDirectory, such as iMonitor or iManager, rather than using YaST to change the configuration. The configuration provided in YaST is only for the initial eDirectory installation and configuration. Installing or Configuring OES 11 SP2 on an Existing Server...
  • Page 112 Newly installed services that have not been configured have the status of Configure is enabled Services that have already been configured have a status of Reconfigure is disabled . OES 11 SP2: Installation Guide...
  • Page 113 If you are installing OES services for the first time on this server, see Section 3.8.5, “Specifying Novell Customer Center Configuration Settings,” on page 59 for help with registering OES and updating the software. Installing or Configuring OES 11 SP2 on an Existing Server...

  • Page 114: Adding/Configuring Oes Services On A Server That Another Administrator Installed

    On the Software Selection page, select the additional OES services you want to install, then click Accept. The required packages are installed. When the Novell Open Enterprise Server Configuration summary screen appears, click the disabled link under LDAP Configuration for Open Enterprise Services. The link changes to enabled.

  • Page 115: Upgrading To Oes 11 Sp2

    All OES releases can be upgraded by installing the interim support packs in order. For example, you can upgrade from OES 2 SP2 to OES 2 SP3, then from OES 2 SP3 to OES 11 SP2. Cross- architecture upgrades (32-bit to 64-bit and 64-bit to 32-bit) are not supported.

  • Page 116: Planning For The Upgrade To Oes 11 Sp2

    Might Not Work After Upgrading During the upgrade process from earlier OES 2 releases to OES 11 SP2, packages that are not part of the SLES 11 SP3 and OES 11 SP2 distributions are automatically retained unless you select them for deletion.

  • Page 117: Meeting The Upgrade Requirements

    Meeting the Upgrade Requirements Meet the following requirements before you upgrade and install any OES 11 SP2 components:  Section 5.3.1, “Securing Current Data,” on page 117  Section 5.3.2, “Ensuring That There Is Adequate Storage Space on the Root Partition,” on page 117 ...

  • Page 118: Preparing The Server You Are Upgrading

    1. Run YaST > Software > Online Update to patch the OES 2 SP3 server to the latest patch level. 2. Ensure that the server and services are still running as desired. 3. Upgrade to OES 11 SP2 using the instructions in this section, then apply all patches and verify services. OES 11 1.

  • Page 119: Checking The Server's Dns Name

    XEN whose root partition is on EVMS. Before starting the upgrade, apply the latest patches for OES 2 SP3 and SLES 10, then proceed with the upgrade to OES 11 SP2. NOTE: After performing this procedure, do not attempt to boot the OES2 server. Instead, start the upgrade to OES11 SP2.
  • Page 120 In the Expert Partitioner window, select a partition, such as root(/), then click Edit > Fstab Options. Under Fstab options:, click Device ID or Device path > OK > OK. OES 11 SP2: Installation Guide...
  • Page 121 SLED 10 SP1: mount "by Device ID"”. Repeat Step 4 Step 5 on page 120 for all the partitions. After you have changed the mount options, click Apply. In the Changes: dialog box, click Finish. Upgrading to OES 11 SP2...

  • Page 122: Preparing An Installation Source

    “Setting Up a Network Installation Source” on page 36. We recommend using the network installation option, especially if you are upgrading multiple servers. Upgrading to OES 11 SP2 Use the following instructions to complete the upgrade applicable to the installation source you are using: ...

  • Page 123: For Servers With Evms And Lvm On The System Device

    If you are attempting to upgrade an OES 2 SP3 server that has boot and swap partitions controlled by EVMS, to OES 11 SP2, you must manually perform the following steps before the system reboots in order to restore the boot and swap disks to the default /dev/system/sys_lx directory.

  • Page 124: Upgrading Using A Network Installation Source Without Dhcp (Offline)

    Insert SUSE Linux Enterprise Server 11 SP3 DVD into the DVD drive of the server that you are upgrading to OES 11 SP2, then reboot the machine. From the DVD boot menu, select one of the following Installation options that matches your environment, but do not press Enter.
  • Page 125 Verify that the upgrade was successful. See the procedures in “Verifying That the Installation Was Successful” on page 106. Complete the server setup by following the procedures in “Completing OES Installation or Upgrade Tasks” on page 159. Upgrading to OES 11 SP2...

  • Page 126: Using Physical Media To Upgrade (Offline)

    Insert the SUSE Linux Enterprise Server 11 SP3 DVD or the OES 11 SP2 Integrated DVD into the DVD drive of the server that you are upgrading to OES 11 SP2, then reboot the machine. From the DVD boot menu, select the Installation option that best fits your environment, then press Enter.

  • Page 127: Specifying The Partition To Update

    If there is only one partition listed, click Next. If there are several partitions, select the partition with /lvm in the path. Click Next. YaST reads the old fstab on this partition to analyze and mount the file systems listed there. Upgrading to OES 11 SP2...
  • Page 128 Step 4 on page 128 Step 5 on page 128 are applicable when you are upgrading from an OES 2 SP3 server. If this error displays, click Specify Mount Options. The Mount Options dialog box appears. OES 11 SP2: Installation Guide...

  • Page 129: Specifying The Add-On Product Installation Information

    Otherwise, skip to Step In the Insert the Add-On Product DVD dialog box, select the drive where you want to insert the DVD labeled Novell Open Enterprise Server 11 SP2 DVD if there is more than one drive. Click Eject.
  • Page 130 If Novell Open Enterprise Server is not listed, click the Add-On Products link and follow the steps “Specifying the Add-On Product Installation Information” on page 129. When the Installation Settings page shows Novell Open Enterprise Server 11 SP2 as an installation setting, proceed...
  • Page 131 OES Services patterns and the components selected with each pattern, see Table 2-5 on page Some OES services, such as Novell CIFS and Novell Samba, are not supported together on the same server. For more information, see “Unsupported Service Combinations” in the...
  • Page 132 If you want to see the details of your selections, click Details. OES 11 SP2: Installation Guide...
  • Page 133 They must be manually selected under the following upgrade scenarios:  When upgrading to OES 11 SP2 from OES 2 SP3 or OES 11, ensure that you select the RPM under the eDirectory pattern. This RPM was added to OES novell-ndsgrepair beginning with OES 11 SP1.

  • Page 134: Accepting The Installation Settings

    When the server reboots, you are required to complete the following configuration information:  “Testing the Connection to the Internet” on page 135  “Specifying Novell Customer Center Configuration Settings” on page 135  “Updating the Server Software During the Upgrade” on page 138 “Upgrading eDirectory” on page 141 ...
  • Page 135 135. Specifying Novell Customer Center Configuration Settings To receive support and updates for your OES 11 SP2 server, you need to register it in the Novell Customer Center. When the Novell Customer Center Configuration page is displayed, you have three options: ...
  • Page 136 Proceeds with registering this server and the SLES 11 SP3 and OES product in Configure Now the Novell Customer Center. Sends information to the Novell Customer Center about the hardware that you Hardware Profile are installing SLES 11 SP3 and OES 11 SP2 on.
  • Page 137 If you don’t specify a code, the server cannot receive any updates or patches.  System Name or Description (optional): The hostname for the system is specified by default. If you want to change this to a description, for the Novell Customer Center, specify a description to identify this server. Click Submit.
  • Page 138 Updating the Server Software During the Upgrade If you have a successful connection to the Internet and have registered the server in the Novell Customer Center, the server displays the Online Update page. You can run the online update now or skip it and get updates later.
  • Page 139 When you see the message, Installation finished on the Patch Download and Installation page, click Next. If the update makes changes to YaST, the following message displays. If so, click OK to restart YaST. Upgrading to OES 11 SP2...
  • Page 140 If you do install patches that have changes to the kernel, click OK when you see the following message. After all the patches are installed, continue with “Upgrading eDirectory” on page 141. OES 11 SP2: Installation Guide...

  • Page 141: Upgrading Edirectory

    Upgrading eDirectory OES 11 SP2 includes eDirectory 8.8.8. When the following dialog box appears, click Upgrade. NOTE: If you are upgrading from OES 2 SP3, this dialog will show that the OES 2.0 eDirectory database (DIB) and config file were found.
  • Page 142 “Configuring Novell Open Enterprise Server Services” on page 142. Configuring Novell Open Enterprise Server Services After you complete the LDAP configuration or eDirectory configuration, the Novell Open Enterprise Server Configuration summary page is displayed, showing all the OES components you updated and installed and their configuration settings.
  • Page 143 When you specify the configuration information for OES services during the upgrade, see the information in “Configuration Guidelines for OES Services” on page When you have finished the configuration of that component, you are returned to the Novell Open Enterprise Server Configuration summary page. Upgrading to OES 11 SP2...

  • Page 144: Finishing The Upgrade

    You can now use AutoYaST to upgrade an OES 2 (64-bit), OES 11, or OES 11 SP1 server to OES 11 SP2 with no user intervention. Ensure that you use the integrated OES 11 SP2 ISO ( OES11-SP2-addon_with_SLES11-SP3-x86_64-DVD.iso ) for the upgrade.

  • Page 145: Prerequisites

    5.6.2 Remastering the Integrated ISO without the add_on_products.xml For a truly unattended OES 11 SP2 upgrade from OES 2, OES 11, or OES 11 SP1, use the remastered integrated ISO ( OES11-SP2-addon_with_SLES11-SP3-x86_64-DVD.iso ) that does not have the add_on_products.xml file.

  • Page 146: Upgrading An Oes 2 (64-Bit), Oes 11 Or Oes 11 Sp1 Server To Oes 11 Sp2

    Once you have successfully generated the answer key file using any of the above stated methods, copy it from the current working directory to /opt/novell/oes-install/ . TIP: To invoke help for creating the answer key file, in the terminal window, type yast2 create- answer-file.ycp --help...

  • Page 147: Upgrading An Oes 2 (64-Bit), Oes 11 Or Oes 11 Sp1 Xen Guest Server To Oes

    The upgrade proceeds without any user intervention. 5.6.5 Upgrading an OES 2 (64-bit), OES 11 or OES 11 SP1 XEN Guest Server to OES 11 SP2 Ensure that you have met all the requirements listed in Section 5.6.1, “Prerequisites,” on page 145.

  • Page 148: Troubleshooting An Autoyast Upgrade

    The upgrade proceeds without any user intervention. 5.6.6 Troubleshooting an AutoYaST Upgrade  “Providing the Correct eDirectory and DSfW Administrator Password” on page 149  “Unattended Upgrade Scenarios That Require User Input” on page 149 OES 11 SP2: Installation Guide...

  • Page 149: Channel Upgrade From Oes 11 Sp1 To Oes 11 Sp2

    Channel Upgrade from OES 11 SP1 to OES 11 SP2  Section 5.7.1, “Channel Upgrade from OES 11 SP1 to OES 11 SP2 Via Wagon,” on page 149  Section 5.7.2, “Channel Upgrade from OES 11 SP1 to OES 11 SP2 Using Zypper,” on page 152 ...
  • Page 150 The NCC screen is displayed again. Click Next, and it does a sync and pops up a message stating that the configuration is successful. Click Details and ensure that the following repositories are enabled as shown in the following figure. OES 11 SP2: Installation Guide...
  • Page 151  Product Novell Open Enterprise Server 11 SP1 (Open_Enterprise_Server) will be upgraded  Product Novell SUSE Linux Enterprise Server 11 SP2 (SUSE_SLES) will be upgraded NOTE: In the following screen shot, the number of packages to be updated may vary based on the patterns selected.

  • Page 152: Channel Upgrade From Oes 11 Sp1 To Oes 11 Sp2 Using Zypper

    Section 5.6.3, “Creating an Answer File to Provide the eDirectory and DSfW Passwords,” on page 145. 5.7.2 Channel Upgrade from OES 11 SP1 to OES 11 SP2 Using Zypper Register the OES 11 SP1 server with NCC using the suse_register -a email=<Email- Address> -a regcode-sles=<SLESactivation-key> -a regcode-oes=<OES-activation- command.

  • Page 153: Upgrading Oes 11 Sp1 To Oes 11 Sp2 Using Smt

    Subscription Management Tool Guide. After registration, upgrading the OES 11 SP1 to OES 11 SP2 is the same as that of NCC upgrades as described from Step 2 in Section 5.7, “Channel Upgrade from OES 11 SP1 to OES 11 SP2,”...

  • Page 154: Rolling Back The Server In The Middle Of A Wagon-Based Channel Upgrade

    OES 11 SP1server with the latest patches. Perform the service pack migration: Log in to the SUSE Manager Web console with administrative credentials. Click System, then select the OES server to be migrated. OES 11 SP2: Installation Guide...

  • Page 155: Verifying That The Upgrade Was Successful

    Click Software > SP Migration and verify the information of the installed product (SLES 11 SP2 and OES 11 SP1) and target product (SLES 11 SP3 and OES 11 SP2). Click Schedule Migration > Confirm. After the support pack migration action completion, reboot the OES server.

  • Page 156: Moving To Common Proxy Users After An Upgrade

    Moving to Common Proxy Users After an Upgrade After you successfully upgrade to OES 11 SP2 from OES 2 SP3, OES 11 or OES 11 SP1, it is recommended to run the move_to_common_proxy.sh script as a post-upgrade activity. This script moves services (CIFS, DNS, DHCP, iFolder, NetStorage, NCS and LUM) that use a service-specific proxy user to common proxy user.
  • Page 157 5.11 What's Next After you complete the upgrade and verify that it was successful, see “Completing OES Installation or Upgrade Tasks” on page 159. Upgrading to OES 11 SP2...
  • Page 158 OES 11 SP2: Installation Guide...

  • Page 159: Determining Which Services Need Additional Configuration

    Planning and Implementation Guide. If a component requires additional configuration that is not part of the Novell Open Enterprise Server (OES) 11 SP2 installation, see the component's administration guide for more information. The following table include links to the installation and configuration information for most OES 11 SP2 services.
  • Page 160 If you want to use an NSS volume to store iFolder data, you must reconfigure iFolder after the initial OES installation. To reconfigure, use Novell iManager to create an NSS volume, then go to YaST > Open Enterprise Server >...

  • Page 161: Rebooting The Server After Installing Nss

    /etc/init.d/novell-tomcat6 restart Launching and Configuring Firefox for Linux After upgrading to OES 11 SP2, you need to launch and configure Mozilla Firefox before accessing other applications via a URL. For example, you cannot configure the Novell Customer Center from the YaST until Firefox is configured.

  • Page 162: Configuring The Digital Certificate

    Click the LDAP Options > View LDAP Servers tab, then click the LDAP server > Connections. In the Server Certificate text box, search for and select the certificate that you created. Click Apply and OK. Repeat Step 4 Step 5 for all the LDAP servers in the LDAP group. OES 11 SP2: Installation Guide...
  • Page 163 For example, to rename SourceCert.der , execute cp /root/certs/SourceCert.der /var/ lib/novell-lum/.198.162.1.1.der Refresh the nam settings using the namconfig cache_refresh command. To view the certificate details, execute the openssl x509 -in /var/lib/novell-lum/ command. .198.162.1.1.der -noout -inform der -text Completing OES Installation or Upgrade Tasks...
  • Page 164 OES 11 SP2: Installation Guide...

  • Page 165: Overview Of Updating (Patching)

    Updating (Patching) an OES 11 SP2 Server Updating an Novell Open Enterprise Server (OES) 11 SP2 Linux server is essentially the same as updating a SUSE Linux Enterprise Server (SLES) 11 SP3 server except that you apply patches for both SLES 11 SP3 and OES 11 SP2.

  • Page 166: Update Options

     Subscription Management Tool (SMT) for SUSE Linux Enterprise: This product doesn’t require a separate license. It lets you host patches from the Novell online update repository on a server, which provides more security and greatly reduces Web traffic related to server updates.

  • Page 167: Registering The Server In The Novell Customer Center

    Registering the Server in the Novell Customer Center Before you can patch an OES 11 SP2 server with updates from Novell, you must register the server either during installation or later by using the instructions in this section. If you register through evaluation codes, your server can receive patches for only 60 days, at which time the codes expire.

  • Page 168: Registering The Server In The Novell Customer Center Using The Command Line

     The activation codes for SLES and OES 11 SP2 that you received when you purchased your product.  An established connection to the Internet. 7.3.2 Registering the Server in the Novell Customer Center Using the Command Line To register a new server or to replace evaluation activation codes with standard codes.

  • Page 169: Registering The Server In The Novell Customer Center Using The Gui

    On the Novell Customer Center Configuration configuration page, select all of the following options, then click Next.  Configure Now: Proceeds with registering this server and the OES product with the Novell Customer Center.  Hardware Profile: Sends information to the Novell Customer Center about the hardware that you are installing SLES 11 SP3 and OES 11 SP2 on.
  • Page 170 If you don’t specify a code, the server cannot receive any updates or patches.  System Name or Description (optional): The hostname for the system is specified by default. If you want to change this to a description for the Novell Customer Center, specify a description to identify this server.

  • Page 171: Updating The Server

    7.4.1 Updating the Server Using the Command Line After you have registered the server in the Novell Customer Center, you can update the server by using commands at the command line. The following procedure specifies steps for updating the server with all available patches for SLES 11 SP3 and OES 11 SP2.

  • Page 172: Verifying That Your Repository Subscriptions Are Up-To-Date

    Verifying That Your Repository Subscriptions Are Up-to-Date When an OES 11 SP2 server is updated properly, the update repository list is refreshed to include Updates entries for your OES 11 and SLES 11 versions. To verify that you have updates from both update repositories:...

  • Page 173: Patching From Behind A Proxy Server

    Patching From Behind a Proxy Server TID 3132246 (http://www.novell.com/support/viewContent.do?externalId=3132246&sliceId=2). GUI Based Patching The method of installing patches using the GUI is same for both OES 11 SP2 and SLES 11 SP3. For more information, see Installing Patches in the SLES 11 SP3 Administration Guide.
  • Page 174 After the keys are imported, other OES channels are mirrored without any issues. Repeat Step 4 and mirror the following OES 11 SP1,OES 11 SP2, SLES 11 SP1, SLES 11 SP2 and SLES 11 SP3 channels:  For OES 11: sles11-sp1-pool , sles11-sp1-updates, sles11-sp1-suse-manager-tools, oes11-pool, oes11-updates, and sles11-extras.
  • Page 175  Description: Specify a short description that identifies the settings this key creates on the systems that use it.  Key: Specify a key of your choice. For example, novell-production could be a key.  Usage: Specify the number of servers that can use this key. Leave it blank for unlimited usage.

  • Page 176: Patching An Oes 11 Or Later Server Using Suse Manager

    This section contains the following Quick Path steps for patching an OES 11 server:  Section 7.10.1, “Do Not Use zypper up without the -t Option,” on page 177  Section 7.10.2, “Command Line Quick Path for Updating OES 11 SP2,” on page 177 OES 11 SP2: Installation Guide...

  • Page 177: Do Not Use Zypper Up Without The -T Option

    Make sure you have the following:  A Novell Customer Center account If you don’t have one, create it at http://www.novell.com/register. This is the same account that you use for Bugzilla.  Activation Codes for both SLES 11 SP3 and OES 11 SP2 ...
  • Page 178 -r SLES11-SP3-Updates -r OES11-SP2-Updates Update the server with all available SLES 11 SP3 and OES 11 SP2 patches by entering: zypper up -t patch -r SLES11-SP3-Updates -r OES11-SP2-Updates Repeat Step 3b Step 3c until there are no more SLES 11 SP3 or OES 11 SP2 patches.

  • Page 179: Installing The Latest Imanager Npms After Applying Oes Patches

    Under the Version column, select all the modules that have version 2.7.7 or above associated with it and the following iManager framework modules: iManager Base Content, iManager Framework and iManager Framework Content, then click Install. After successfully installing all the NPMs, restart tomcat using the /etc/init.d/novell- command. tomcat6 restart 7.12...
  • Page 180 OES 11 SP2: Installation Guide...

  • Page 181: Prerequisites

    Section 8.4, “Cloning an OES Server Post OES Installation and Configuration,” on page 188 Prerequisites You need at least the following components to install an OES 11 SP2 server by using AutoYaST:  A server with OES 11 SP2already installed.

  • Page 182: Setting Up A Control File With Oes Components

    Solution: You must insert the CA section manually. To add this information to the control file: 1. Open YaST as root . 2. Click Miscellaneous > Autoinstallation. 3. Select Security and Users > CA Management, then click Edit. OES 11 SP2: Installation Guide...

  • Page 183: Using The Autoinstallation Module To Create The Control File

    <password>actual_password</password> <server_email>name@example.com</server_email> <state></state> <takeLocalServerName config:type="boolean">true</takeLocalServerName> </ca_mgm>  Issue 3: If you install Novell Cluster Services, one package does not install correctly. Solution: Comment out the following line in the control file. <package>novell-cluster-services-kmp-smp</package> For example: <!--<package>novell-cluster-services-kmp-smp</package>-->  Issue 4: If you did not patch the server during the installation, the OES product is not identified correctly in the control file.
  • Page 184 On the User Script Management page, click New. In the File Name field, specify a descriptive name for the script, such as hello_world_script In the Script Source field, specify commands such as the following example script: #!/bin/sh ‘echo "hello world" > /tmp/post-script-output' OES 11 SP2: Installation Guide...
  • Page 185 “Deciding What Patterns to Install” on page Pattern Other Module Dependencies  Novell AFP Novell Backup / Storage Management Services (SMS)  NetIQ eDirectory  Novell Storage Services (NSS)  Novell Linux User Management (LUM) ...
  • Page 186  Novell Linux User Management (LUM) Management Services  Novell Remote Manager (NRM) (SMS) Novell CIFS  Novell Backup / Storage Management Services (SMS)  NetIQ eDirectory  Novell Storage Services (NSS)  Novell Linux User Management (LUM)  Novell Remote Manager (NRM) Novell Cluster Services ...
  • Page 187 Novell iManager  Novell Linux User Management (LUM)  Novell Remote Manager (NRM) Novell Pre-Migration  Novell Backup / Storage Management Services (SMS) Server  NetIQ eDirectory (without a replica)  Novell Linux User Management (LUM)  Novell Remote Manager (NRM) Novell QuickFinder ...

  • Page 188: Setting Up An Installation Source

    188. Setting Up an Installation Source For OES 11 SP2, you must set up a separate directory for the SLES 11 SP3 software and the OES 11 SP2 software. AutoYaST requires an installation source. You have several options. For an explanation of each, see “Network Based Installation”...

  • Page 189: Generating The Autoinst.xml File

    8.4.1 Generating the autoinst.xml File The autoinst.xml file contains all the configuration details of the components, passwords, IP address, and so on. Store this file in a secure location, and use it to reinstall and reconfigure your OES server when there is a crash. To generate the autoinst.xml file: Log on to the OES server with administrative privileges and execute the following command: yast2 clone_system...
  • Page 190 HTTP location where the autoinst.xml file is hosted> netsetup=hostip hostip=<enter machine IP> netmask=<enter the netmask> gateway=<enter the gateway> For example: autoyast=http://198.162.1.1/autoinst.xml netsetup=hostip hostip=192.168.1.2 netmask=255.255.254.0 gateway=192.164.1.254 Press Enter and the OES installation and configuration starts and completes without any user intervention. OES 11 SP2: Installation Guide...

  • Page 191: Installing The Kvm Hypervisor And Tools

    Installing OES as a VM Host Server You can install Novell Open Enterprise Server (OES) 11 as a VM host server for either the Xen or KVM virtualization services included with SLES 11. To understand why you might want your VM host server to have OES 11 installed, see “Why Install OES Services on Your VM...

  • Page 192: Installing The Xen Hypervisor And Tools

    SLES 11 SP3 server that you have previously installed. NOTE: You can also install Xen and OES 11 SP2 at the same time as SLES either using the integrated SLES 11 SP3 with OES media or using OES 11 SP2 add-on media. For either of these later options, the instructions that follow require slight but straight-forward adjustments.
  • Page 193 In either case, the server will be configured as an OES server. If you selected any of the supported OES services, Novell Remote Manager (NRM) is also selected. Click the green check mark by NRM to deselect NRM and prevent it from being installed.

  • Page 194: Upgrading An Oes 2 Xen Vm Host Server To Oes 11

    When prompted to configure a network bridge, click Yes. When the hypervisor and tools installation is completed, click OK. Click YaST > Virtualization > VirtualMachineManager. Click File > Add Connection > Connect. Your VM guests are now able to be run. OES 11 SP2: Installation Guide...

  • Page 195: System Requirements

    10.1 System Requirements To create an OES 11 SP2 VM guest, you need a SLES 11 SP3 or OES 11 SP2 server that is set up as a VM host server. Section 10.1.1, “OES 11 SP2 VM Host Considerations,” on page 196 ...

  • Page 196: Oes 11 Sp2 Vm Host Considerations

    10.1.1 OES 11 SP2 VM Host Considerations When you set up a virtual machine host for OES 11 SP2 VM guests, ensure that the host server has the following:  Time synchronization: Set the server’s time configuration to the same reliable, external time source as the eDirectory tree that the virtual machines on that host will be joining.

  • Page 197: Prerequisites

    SLES-11-SP3-DVD-x86_64-GM- DVD1.iso 10.3.2 Preparing the Installation Source Files To create an OES 11 SP2 VM guest, you must make the installation software available in one of the following locations:  A Local Installation Source: The 64-bit (Table 10-1) ISO files copied to the host server’s local drives.

  • Page 198: Specifying Options For Creating An Oes 11 Sp2 Vm Guest

    10.4.1 Specifying Options for Creating an OES 11 SP2 VM Guest The Create Virtual Machine Wizard helps you through the steps required to create a VM guest and install the desired operating system. Launch the Create Virtual Machine Wizard by using one of the following methods: ...
  • Page 199 Click Disks. The Virtual Disks dialog box lets you create one or more virtual disks that the OES 11 SP2 VM guest has access to. If you are installing from a DVD on the host server or from an ISO image file copied to the host server’s storage devices, these are also listed as virtual disks.

  • Page 200: Specifying The Installation Mode

    When the Installation Mode screen displays, select the following menu options:  New Installation  Include Add-On Products from Separate Media Click Next. Continue with Section 10.4.3, “Specifying the Add-On Product Installation Information,” on page 201. OES 11 SP2: Installation Guide...

  • Page 201: Specifying The Add-On Product Installation Information

    Upgrading an OES 2 VM Guest to OES 11 SP2 IMPORTANT: To upgrade an OES 2 VM paravirtualized guest to OES 11 SP2, you must install using files on the network. Physical media upgrades and using ISO image files are not supported methods.

  • Page 202: Before You Start The Upgrade Process

    OES 11 SP2 cannot run as a paravirtualized guest on SLES 10 SP4 or earlier hosts. Performing a down-server upgrade on a Xen VM guest running on a SLES 11/OES 11 SP2 VM host is very much like upgrading a physical machine ...
  • Page 203 /boot , swap , and root ( / ) volumes. After the virtual machine is set up, you need to perform additional tasks to set up additional Novell Storage Service (NSS) devices.
  • Page 204 OES 11 SP2: Installation Guide...

  • Page 205: Introduction

    You can install NetWare as a virtual machine guest (VM guest) operating system on the following servers:  A SUSE Linux Enterprise Server (SLES) 11 SP3 Linux server “Setting Up a Virtual Machine Host” (http://www.novell.com/documentation/sles10/ book_virtualization_xen/data/cha_xen_virtualization_vhost_setup.html) in the Virtualization with Xen guide (http://www.novell.com/documentation/sles10/book_virtualization_xen/data/...

  • Page 206: Support Information

     NetWare 6.5 SP6 and earlier running on a virtual machine.  VCPU hotplug.  Network or block device hotplug.  Virtual memory resizing.  Direct access to physical devices.  The save, restore, and migrate commands.  Some Novell Remote Manager debugging features. OES 11 SP2: Installation Guide...

  • Page 207: Preparing To Install A Netware Vm Guest Server

    OES services on the host server itself. For more information, see “Why Install OES Services on Your VM Host?” in the OES 11 SP2: Planning and Implementation Guide. Installing and Managing NetWare on a Xen-based VM...

  • Page 208: Planning For Netware Vm Guest Servers

    For more information on NSS disk storage, see “Using NSS in a Virtualization Environment” in the OES 11 SP2: NSS File System Administration Guide for Linux. Network Planning Each Xen guest VM is assigned one virtualized network card by default. You can create additional cards if desired.

  • Page 209: You Must Use Timesync For Time Synchronization

    eDirectory Planning You can place a NetWare virtual machine in an existing tree or as the first server in a new tree. However, the performance of virtualized NetWare doesn’t match a physical NetWare installation. In most cases, it is probably preferable to add your NetWare virtual machine to an existing tree located on a physical NetWare server, particularly if the tree is large.

  • Page 210: Installing Virtualized Netware

    Section 11.4.2, “Creating a Xen Virtual Machine and Installing a NetWare VM Guest Server,” on page 210. 11.4.2 Creating a Xen Virtual Machine and Installing a NetWare VM Guest Server Open YaST, then click Virtualization > Create Virtual Machines. OES 11 SP2: Installation Guide...
  • Page 211 Read the Create a Virtual Machine welcome page, then click Forward. Select I need to install an operating system, then click Forward. Installing and Managing NetWare on a Xen-based VM...
  • Page 212 Click the triangle next to NetWare, select Novell Open Enterprise Server 2 (NetWare), then click Forward. The Summary page appears, showing the settings to be used for the virtual machine. OES 11 SP2: Installation Guide...
  • Page 213 Click Name of Virtual Machine. Specify the name that you want displayed for this virtual machine in the Virtual Machine Manager. For example, you might specify hostname_vm, where hostname is the host name of the server you are installing. Click Hardware. Change the initial memory setting to at least 1024 MB and the maximum setting to as much as 8 GB, depending on the RAM available on your host server.
  • Page 214 When you have the virtual machine settings the way you want them, click OK to proceed with the creation of the virtual machine and the installation of the virtual NetWare server. A VNC viewer window appears, displaying the progress of the NetWare install program. OES 11 SP2: Installation Guide...

  • Page 215: Managing Netware On A Virtual Machine

    Do the following: Click inside the installation window to set the mouse pointer. The mouse is not used on the first few screens, but you must set it now. Otherwise, the mouse and the keyboard might not work as expected when the GUI pages appear. Enter all of the installation information as you would for a physical NetWare installation.

  • Page 216: Using The Virtual Machine Manager

    Virtualization with Xen guide (http://www.novell.com/ documentation/sles10/book_virtualization_xen/data/book_virtualization_xen.html).  To make a break in NetWare from a terminal, enter xm sysrq x c , where x is the domain ID and c is any keyboard character. OES 11 SP2: Installation Guide...

  • Page 217: If Vm Manager Doesn't Launch On A Xen Vm Host Server

    If the option to launch the VM Manager for installing a NetWare guest is not available, the most likely cause is that the Xen kernel is not running on the Xen VM host server. See The Boot Loader Program (http://www.novell.com/documentation/sles10/book_virtualization_xen/data/ sec_xen_config_bootloader.html) in the Virtualization with Xen guide (http://www.novell.com/ documentation/sles10/book_virtualization_xen/data/book_virtualization_xen.html). Installing and Managing NetWare on a Xen-based VM...
  • Page 218 OES 11 SP2: Installation Guide...
  • Page 219 Disabling OES 11 Services Although you can uninstall Novell Open Enterprise Server 11 (OES) service RPMs through YaST, we do not recommend it because so many modules have interdependencies. Uninstalling services can leave the server in an undesirable state. Instead, we recommend disabling the service.
  • Page 220 OES 11 SP2: Installation Guide...

  • Page 221: Cleaning Up The Edirectory Server

    This section outlines the steps to be performed, depending on the role of the server with regard to your eDirectory tree. If a backup of the eDirectory database is not available, you can contact Novell Support or perform the following procedures: ...

  • Page 222: Reconfiguring The Replica Server

    Moving the Organizational CA to a Different Server (http:// www.novell.com/documentation/crt33/crtadmin/data/a2ebop8.html#acea8nu) Creating a Server Certificate Object (http://www.novell.com/documentation/crt33/crtadmin/data/ fbgcdhec.html) in the Novell Certificate Server 3.3.2 Administration Guide. Clean up the server. For more information, see Section 13.1.4, “Cleaning Up eDirectory,” on page 222.

  • Page 223: Reconfiguring The Edirectory Server Through Yast

    13.2 Reconfiguring the eDirectory Server through YaST The eDirectory reconfiguration can be done on the Root partition Master replica server, a Read-Write replica server, a server without a replica, or the CA server. Open YaST. Click Open Enterprise Server > OES Install and Configuration. On the Software Selection Page, click Accept.

  • Page 224: Re-Creating Edirectory Objects

    Section 13.3.2, “Services Requiring Reconfiguration,” on page 225  Section 13.3.3, “Manually Starting Services,” on page 226 13.3.1 Re-creating eDirectory Objects “Novell Storage Service” on page 224   “NCP Server” on page 225 Novell Storage Service Use the NSS Management utility to re-create the eDirectory objects for NSS pools and volumes. For additional information, see NSS Management Utility Quick Reference (http://www.novell.com/...

  • Page 225: Services Requiring Reconfiguration

    Click Open Enterprise Server > OES Install and Configuration. On the Software selection page, click Accept. The status of the Novell DNS service is displayed as Reconfigure is Disabled. To reconfigure the DNS service, click disabled to change the status to enabled.

  • Page 226: Manually Starting Services

    The status of Novell CIFS service is displayed as Reconfigure is Disabled. To reconfigure CIFS, click the Disabled link to change the status to Enabled. Click the Novell CIFS services heading link and enter admin password to access the configuration dialog box.

  • Page 227: Re-Configuring Imanager

    Ensure that the OES server is registered to NCC, and you have applied all the latest patches available in the patch channel using the zypper up command. For more information on patching using the zypper command, see Chapter 7, “Updating (Patching) an OES 11 SP2 Server,” on page 165.
  • Page 228 OES 11 SP2: Installation Guide...

  • Page 229: Access To The Server During An Installation Or Upgrade

    Security Considerations This section includes issues that you should consider when installing and configuring a Novell Open Enterprise Server (OES) 11 Linux server.  Section 14.1, “Access to the Server During an Installation or Upgrade,” on page 229  Section 14.2, “Remote Installations Through VNC,” on page 229 ...
  • Page 230 OES 11 SP2: Installation Guide...

  • Page 231: The Edirectory

    233  Section 15.7, “The DEFAULT SLP Scope Gets added to the slp.conf File During an Upgrade to OES 11 SP2,” on page 233  Section 15.8, “zlib-devel and zlib-devel-32bit Package Conflict During the Channel Upgrade to OES 11 SP2,” on page 234 ...

  • Page 232: Edirectory User Password Screen Does Not Show Up During An Upgrade

    User Password Screen Does Not Show Up During an Upgrade When you upgrade an OES 2 server to OES 11 SP2, the eDirectory pattern will not be selected as part of the product listing and the eDirectory user password screen will not show up.

  • Page 233: Imanager Not Configured Or Installed Properly

    File During an Upgrade to OES 11 SP2 When you upgrade an OES server that is configured as an SLP DA to OES 11 SP2, the DEFAULT SLP scope gets added to the slp.conf file along with the SLP scope configured by you. This might result in adding extra load to the OES server.

  • Page 234: Zlib-Devel And Zlib-Devel-32Bit Package Conflict During The Channel Upgrade To Oes 11 Sp2

     Upgrading an OES 2 SP3 server that has C/C++ Compiler and Tools pattern installed to OES 11 SP1 using media upgrade.  Upgrading the resultant OES 11 SP1 server to OES 11 SP2 using the channel upgrade. Cause: These packages (zlib-devel and zlib-devel-32bit) are no longer available in the SLES 11 base.

  • Page 235: Oes Installation Fails Due To Encrypted Oes Media Url In The Autoinst.xml File

    OES media URL in an encrypted form. An OES installation with that XML file will fail with the following error: “failed to add add-on product.” To resolve this issue, replace the OES media URL with the actual installation source path and retry the installation. <add_on_products config:type="list"> <listentry> <media_url><![CDATA[https:// 866254f853cb4f668594269ecec05dd9:f62283a76d964e4b8c0cebd447fdd54a@nu.novell.com/ repo/$RCE/OES11-SP2-Pool/sle-11-x86_64]]></media_url> <product>Open_Enterprise_Server</product> <product_dir></product_dir> </listentry> </add_on_products> 15.11...
  • Page 236 OES 11 SP2: Installation Guide...

  • Page 237: A.1 General Rules

    If a product or service has multiple log files, they are stored in a subdirectory named for the product or service.  /var/log: Contains the log messages and the YaST logs.  All files and directories that could not follow the above rules have the prefix novell- where possible. OES 11 File and Data Locations...

  • Page 238: A.2 Exceptions

    /etc/init.d , and cron scripts, which must be in /etc/cron.d . When possible, these files have a novell- prefix. When standard conventions preclude the use of prefixes (such as PAM modules, which use suffixes instead of prefixes), the standard conventions are followed.

  • Page 239: B.1 Arkmanager

    Section B.5, “ncpserver,” on page 246  Section B.6, “ncs,” on page 246  Section B.7, “netstorage,” on page 248  Section B.8, “novell-afp,” on page 248  Section B.9, “novell-cifs,” on page 249  Section B.10, “novell-dhcp,” on page 250 ...

  • Page 240: B.2 Edirectory

    Specify the DSfW DNS domain name. The value of this tag and xad_domain_name tag should be same. Example: <domain_name>acme.com</domain_name> existing_dns_ip Specify the existing DNS server IP address. Example: <existing_dns_ip>192.168.1.1</existing_dns_ip> group_context Specify the DNS DHCP group object context. Example: <group_context>ou=OESSystemObjects,dc=labs,dc=wdc,dc=acme,dc=com</ group_context> OES 11 SP2: Installation Guide...
  • Page 241 Attribute Name Description host_name Specify the host name of the current server where the installation is being done. Example: <host_name>acme-208</host_name> http_port Specify the HTTP port of the eDirectory server where the installation is being done. Example: <http_port config:type="integer">8028</http_port> https_port Specify the HTTPS port of the current eDirectory server. Example: <https_port config:type="integer">8030</https_port>...
  • Page 242 Specify the SLP backup time in seconds. The default is (900 seconds or 15 minutes). If the server is configured as Director Agent, this value will be used. Example: <slp_backup_interval>900</slp_backup_interval> slp_da Specify the list of IP addresses of the SLP Directory Agents. Example: <slp_da config:type="list"> <listentry>198.162.1.1</listentry> </slp_da> OES 11 SP2: Installation Guide...
  • Page 243 Attribute Name Description slp_dasync Set this to 'yes' when you want to enable SLPD to sync service registration between SLP Das on startup. If the server is configured as Director Agent, this value be used. Example: <slp_dasync>no</slp_dasync> Slp_mode Specify the SLP mode to multicast, da, or da_server. By default, it is set to multicast.
  • Page 244 DC hosting the domain acme.com. <xad_parent_domain_address>192.168.1.1</xad_parent_domain_address> xad_parent_domain_admin_c Specify the immediate DSfW parent domain's administrator context. For ontext example, for the domain sales.acme.com, <xad_parent_domain_address>cn=administrator,cn=users,dc=acme,dc=com</ xad_parent_domain_address> xad_parent_domain_admin_ Specify the immediate DSfW parent domain's administrator password. password Example: <xad_parent_domain_admin_password>SAM23#$</ xad_parent_domain_admin_password> OES 11 SP2: Installation Guide...

  • Page 245: B.3 Imanager

    Attribute Name Description xad_replicate_partitions Always set this to 'yes'. This indicates that the replicas of the configuration and schema partitions will be added to the local domain controller. Example: <xad_replicate_partitions>yes</xad_replicate_partitions> xad_retain_policies Set this to 'yes' when you want to retain the existing NMAS universal password policies.

  • Page 246: B.5 Ncpserver

    Set this to 'true' always as NCP is a must for OES to work. Example: <configure_now config:type="boolean">true</configure_now> NOTE: Novell Cluster Services does not support using autoyast to configure cluster nodes for new clusters or existing clusters. If you create an autoyast file from a cluster node, you must remove or comment out the NCS section before you use it to build or rebuild a server.
  • Page 247 Attribute Name Description proxy_user Specify the NCS proxy user credentials--the username and password. The NCS proxy user is the user identity used by the NCS daemon to communicate with eDirectory (the LDAP server). In the proxy_user tag, specify the Fully Distinguished name of the NCS proxy user in comma-delimited typeful format.

  • Page 248: B.7 Netstorage

    Example: <afp_proxy_user>cn=afpproxy,o=acme</afp_proxy_user> If you are using common proxy for AFP, mention the user FQDN of the common proxy as shown below. <afp_proxy_user>cn=OESCommonProxy_localhostname,o=acme</ afp_proxy_user> afp_proxy_user_password Specify the password for the AFP proxy user. Example: <proxy_user_password>SAM23#$</proxy_user_password> OES 11 SP2: Installation Guide...

  • Page 249: B.9 Novell-Cifs

    Set this to 'yes' for AFP proxy user to grant search rights over user contexts. This is required for subtree search feature. Example: <usercontext_rights>yes</usercontext_rights> novell-cifs Attribute Name Description ldap_server Specify the IP address of the eDirectory LDAP server that AFP connects to at install time.

  • Page 250: B.10 Novell-Dhcp

    If a certificate is provided and it cannot be verified, the session is immediately terminated.  Hard: The server requests for a certificate and a valid certificate must be provided, otherwise the session is immediately terminated. Example: <check_method>never</check_method> OES 11 SP2: Installation Guide...
  • Page 251 Attribute Name Description client_certificate Specify the path of the LDAP CA file that contains the client certificate. Example: <client_certificate>/etc/opt/novell/certs/client.pem</ client_certificate> client_key Specify the path of the LDAP client key file that contains the key file for the client certificate. Example: <client_key>/etc/opt/novell/certs/cli_key_cert.pem</client_key>...

  • Page 252: B.11 Novell-Dns

    Specify the host name of the current server where the installation is being done. Example: <host_name>acme-208</host_name> ldap_basedn Specify the LDAP base DN context. Example: <ldap_basedn>o=acme</ldap_basedn> ldap_server Specify the IP address of the LDAP server. Example: <ldap_server>192.168.1.2</ldap_server> locator_context Specify the DNS locator context. Example: <locator_context>ou=OESSystemObjects.dc=acme.dc=wdc.dc=acme.dc=c om</locator_context> OES 11 SP2: Installation Guide...

  • Page 253: B.12 Novell-Ifolder3

    Specify the DNS server context. Example: <server_context>ou=sales,o=acme</server_context> use_secure_port Set this to 'yes' when you want to use a secure port for communicating with the LDAP server. Example: <use_secure_port>yes</use_secure_port> B.12 novell-ifolder3 Attribute Name Description admin_alias Specify the iFolder administrator name. Example: <admin_alias>/admin</admin_alias> alternate_ldap_admin Specify the admin user for the alternate LDAP source.
  • Page 254 Specify the URL or IP address used by the iFolder server or multi-server configuration. This is also used for Web Access/Admin to communicate. Example: <private_url>164.99.100.34</private_url> proxy_password Specify the LDAP proxy password. If OES common proxy is used, then specify the password of the common proxy. Example: <proxy_password>SAM23#$</proxy_password> OES 11 SP2: Installation Guide...
  • Page 255 Attribute Name Description public_url Specify the URL or IP address used by the iFolder clients to communicate with the iFolder server. Example: <public_url>164.99.100.34</public_url> recovery_path Specify the path in the server where the Encryption key recovery file is stored. Example: <recovery_path>/var/simias/data/simias</recovery_path> server_name Specify the name of the iFolder server.

  • Page 256: B.13 Novell-Lum

    LUM service will be added to this admin group and this group will be associated with the workstation object. Example: <admin_group>cn=admingroup,o=acme</admin_group> alternate_ldap_servers_list1 Specify a list of the IP addresses of the local eDirectory servers that you are connecting to. Example: <alternate_ldap_servers_list1 config:type="list"> <listentry>192.168.1.1</listentry> <listentry>192.168.1.2</listentry> </alternate_ldap_servers_list1> OES 11 SP2: Installation Guide...
  • Page 257 Attribute Name Description alternate_ldap_servers_list2 Specify one or more external LDAP servers. Ensure to specify the IP address of a valid LDAP server that is up and running. Example: <alternate_ldap_servers_list2 config:type="list"> <listentry>192.168.1.3</listentry> <listentry>192.168.1.4</listentry> </alternate_ldap_servers_list2> ldap_server Specify the IP address of the LDAP server. Example: <ldap_server>164.99.100.38</ldap_server>...

  • Page 258: B.14 Novell-Quickfinder

    Manager and rights-based searches will be turned off. Example: <shadow_access>yes</shadow_access> B.15 novell-samba NOTE: Novell Samba must not be installed on the same server as Novell CIFS. Attribute Name Description ldap_server Specify the IP address (in IPv4 format) of the LDAP server in the tree that you want Novell Samba to use for LDAP (eDirectory) communications.
  • Page 259 Attribute Name Description netbios_name Specify the NetBIOS name to use for the virtual Samba server. Use the hostname and append "-W" to it. The total length of the NetBIOS name can be up to 15 characters (this is a NetBIOS restriction). This means the hostname of the server should be limited to 13 characters.

  • Page 260: B.16 Nss

    Specify the LDAP secure port number. Example: <ldap_servers config:type="list"> <listentry> <ip_address>164.99.100.38</ip_address> <ldap_port config:type="integer">389</ldap_port> <ldaps_port config:type="integer">636</ldaps_port> </listentry> </ldap_servers> proxy_context Specify the FQDN of the default common proxy user. Example: <proxy_context>cn=OESCommonProxy_wdcsales34,o=acme</ proxy_context> proxy_password Specify the common proxy user password. Example: <proxy_password>SAM23#$</proxy_password> OES 11 SP2: Installation Guide...

  • Page 261: B.18 Sms

    Attribute Name Description tree_name Specify the eDirectory tree name. Example: <tree_name>sales_wdc_acme</tree_name> use_common_proxy Set it to 'yes' when you want to use the default common proxy. Example: <use_common_proxy>yes</use_common_proxy> xad_tree_admin_context Specify domain tree admin FQDN context. Example: <xad_tree_admin_context></xad_tree_admin_context> xad_tree_admin_password Specify domain tree admin password. Example: <xad_tree_admin_password>SAM23#$</ xad_tree_admin_password>...
  • Page 262 OES 11 SP2: Installation Guide...

  • Page 263: Documentation Updates

    Documentation Updates This section summarizes the changes made to this guide since the initial release of Novell Open Enterprise Server 11. December 2014 (OES 11 SP2) A troubleshooting section on resolving the POODLE security vulnerability has been added for the December 2014 OES patches.
  • Page 264 OES 11 SP2: Installation Guide...

This manual is also suitable for:

Open enterprise server 11 sp2

Table of Contents