Installing OES Linux

Installing OES Linux is a straightforward process, but you should be familiar with several aspects of the installation prior to beginning the process. When you know what to expect, you can begin the process of installing a new server or upgrading an existing server to OES.

The following topics are contained in this section:

• Preparing to install OES Linux

• Installing a new OES Linux server

• Upgrading SLES9 to OES Linux

Preparing to Install OES Linux

Before beginning the OES Linux installation, it is a good idea to double-check the installation prerequisites. This section contains the official prerequisites of an OES Linux server.

It is also important to understand the OES Linux installation patterns. These patterns determine what OES components are installed by default. If necessary, each pattern can be customized to address specific needs.

Finally, creating a network-based installation source is an efficient way to perform multiple installations, or just maintain the installation without relying on the CD media.

When you fully understand these topics, you'll be ready to begin the actual OES Linux installation.

INSTALLATION PREREQUISITES

Before attempting to install OES for Linux, review the following minimum hardware prerequisites list to ensure that your server meets these requirements:

• Server-class computer with Pentium II or AMD K7 450MHz processor (Pentium III, Pentium 4, AMD K8 or higher recommended)

• 512MB of RAM (1GB recommended)

• 2GB of available, unpartitioned hard disk space (10GB recommended; additional space may be required depending on OES component implementation)

• 4X CD-ROM drive (48X recommended)

Keep in mind that these requirements are specifically referring to the minimum hardware requirements and may not be sufficient for your needs. It is obviously a good idea to use the best hardware available to you, and plan for increased server use in the future.

INSTALLATION PATTERNS

New installations of OES allow you to perform the installation based on one of several different patterns. The installation screen providing these choices is seen in Figure 2.1. Depending on the pattern you choose, one or more of the preconfigured OES Linux software categories are installed. After you select a pattern, additional software can be installed through a Detailed Selection option.

Figure 2.1. OES Linux installation patterns.

The patterns available for installation, and their description, are as follows:

• Minimum System Installs the bare minimum required for a SLES9 server. With this pattern, the following software categories are installed:

  • Basis Runtime System

  • YaST

• Minimum Graphical System (without KDE) This performs the same type of installation as a Minimum System, but also adds the X server and FVWM graphical environment. With this pattern, the following software categories are installed:

  • Basis Runtime System

  • YaST

  • Graphical Base System

• Full Installation This performs a complete installation of SLES9 and includes all standard software categories. This pattern does not install any Novell OES components, but all non-OES categories of software are installed.

• Default System This performs a default installation of SLES9. This pattern does not install any Novell OES Components. The following software categories are installed:

  • Basis Runtime System

  • Basis Sound Libraries and Tools

  • Graphical Base System

  • KDE Desktop Environment

  • YaST

  • Linux Tools

  • Authentication Server (NIS, LDAP, Kerberos)

  • Print Server (CUPS)

  • Help & Support Documentation

• Novell QuickFinder Server This performs an installation of a dedicated QuickFinder server. The following software categories are installed:

  • Basis Runtime System

  • YaST

  • Novell QuickFinder

• Novell iFolder2 Server This performs an installation of a dedicated iFolder server. The following software categories are installed:

  • Basis Runtime System

  • YaST

  • Novell iFolder 2.x

• Novell Virtual Office Server This installs a server configured to provide access to Virtual Office. The following software categories are installed:

  • Basis Runtime System

  • YaST

  • Novell eDirectory

  • Novell eGuide

  • Novell Linux User Management

  • Novell iPrint

  • Novell iManager

  • Novell QuickFinder

  • Novell Virtual Office

  • Novell NetStorage

• Novell Print Server This installs a server configured for offering iPrint services. With this pattern, the following software categories are installed:

  • Basis Runtime System

  • YaST

  • Novell eDirectory

  • Novell Linux User Management

  • Novell iPrint

  • Novell iManager

• Novell Management Server This installs a server with the primary management tool for OESiManager. No graphical environment is installed with this pattern, so management must be performed from a browser running on a local workstation. The following software categories are installed with this pattern:

  • Basis Runtime System

  • YaST

  • Novell iManager

• Novell Open Enterprise Server This installs a default Open Enterprise Server. This does not install every OES component. The following software categories are installed:

  • Basis Runtime System

  • Basis Sound Libraries and Tools

  • Graphical Base System

  • KDE Desktop Environment

  • YaST

  • Linux Tools

  • Authentication Server (NIS, LDAP, Kerberos)

  • Help & Support Documentation

  • Novell eDirectory

  • Novell eGuide

  • Novell Linux User Management

  • Novell iPrint

  • Novell iManager

  • Novell QuickFinder

  • Novell Virtual Office

  • Novell Samba Configuration

  • Novell Health Monitoring

  • Novell Backup Services (SMS)

CONFIGURING INSTALLATION SOURCES

Although it is possible to install OES Linux directly from the CD media, there are many reasons why you might want to consider creating a network-based installation source. For example, you might want to install multiple OES Linux servers, or you may just want to perform an installation without having to watch the install and swap CDs occasionally. Regardless of the reason, creating a network-based installation source is easy and definitely recommended for ease of installation.

Creating a network-based installation source only requires a SUSE Linux server and enough disk space to hold the contents of the OES Linux CDs. If you meet these requirements, complete the following steps to create your installation source:

1.	Download the netInstall.sh script from the Novell documentation site at the following URL: http://www.novell.com/documentation/oes/script/netInstall.sh
2.	From your SUSE Linux machine, execute netInstall.sh and provide the following information: Installation Directory This is the directory you would like the installation source to be created in. There should be sufficient space at this location to hold the contents of all the OES Linux CDs. ISO Image Location This is the directory in which ISO images for OES Linux can be located. At the conclusion of the netInstall.sh script, your installation source should be complete. At this point, the server needs to be configured to make the installation source available over NFS. NOTE You can also provide an installation source over FTP and HTTP. For information on this configuration, see the online OES documentation.
3.	On your installation server, edit /etc/exports using a text editor and add an entry for your installation source directory as follows: <Full_Path_To_Install_Source> *(ro,root_squash,sync)
4.	Restart your NFS server using /etc/rcnfsserver restart.

If you only have ISO images of OES Linux, be sure to burn a copy of CD1. This CD will be used to boot the new OES Linux server and initiate access to the network-based installation source.

Installing a New OES Linux Server

After you have gathered all the information you need and made the necessary decisions with regard to installation and configuration, you are ready to perform the OES Linux installation.

This section explains how to install a new server. If you are adding OES to an existing SLES9 server, skip to "Upgrading SLES9 to OES Linux" later in this chapter.

There are three main steps to the OES Linux installation:

• Configure primary installation options
  
  
• Create filesystem and copy files
  
  
• Configure OES components
  
  

The first step is required to configure the entire server installation process. It is this step that allows the disk partitions to be created, software selection to be made, and general installation options to be configured.

The second step is an automated step that actually installs the requested software. If this is a CD-based installation, you will be required to swap disks when prompted. Network-based installations do not require any type of administration during this phase.

The final step takes place after the software has been installed and the server is rebooted. Upon startup, the installation process will resume and prompt for information such as the root user's password, network configuration, and final hardware configuration. This stage also performs your OES component configuration. At the conclusion of this step, your OES Linux server is ready for use!

After you have gathered all the information you need and made the necessary decisions with regards to installation and configuration, you are ready to perform the OES Linux installation.

CONFIGURE PRIMARY INSTALLATION OPTIONS

To begin the installation, you will use the bootable, OES Linux CD1 to boot your new OES Linux server. To begin the installation process, follow these steps:

1.	Boot the server with the OES Linux installation CD (CD 1).
2.	After the CD has booted, you will be presented with a GRand Unified Bootloader (GRUB) prompt (shown in Figure 2.2). Figure 2.2. GRUB boot menu. The GRUB menu provides the following startup options: Boot from Hard Disk This option will exit the GRUB menu and attempt to boot from the first hard disk. Installation This will begin the installation process. Installation - ACPI Disabled If necessary, this option can be used to begin the installation process with Advanced Configuration and Power Interface (ACPI) disabled. This is useful if the normal installation option is failing due to ACPI settings on your server. Installation - Safe Settings If necessary, this option can be used to begin the installation process using safe settings. Safe settings disables DMA mode for the CD-ROM device, and power management functions. Manual Installation This option can be used to begin a manual installation process. This may be necessary to customize the device drivers being loaded, or provide advanced settings to the installation routine. Rescue System If you are unable to boot your OES Linux server, this option will invoke a rescue mode version of Linux running off the installation CD-ROM. After bootup, you are presented with a command shell where manual repairs to the installed system can be performed. Automated repairs are available through the normal installation routine. Memory Test This option automatically loads Memtest-86 and performs memory read and write procedures in a continuous loop. This is used to locate defective RAM. If you suspect defective RAM, run this routine for several hours. If no problems are detected, your RAM is most likely intact. In addition to the standard menu selections, there are a number of additional options that can be used to begin a network-based installation, configure a remote VNC-based installation, or configure specific installation parameters. For information on these options, refer to the following description of each main GRUB option: Boot Options This field is used to enter options that are passed to the Linux kernel used during the installation process. One way this field is commonly used is to enable a remote installation over VNC. To enable this type of installation, enter the following options in this field: vnc=1 vncpassword=<PASSWORD> This causes a VNC server to be spawned during the installation process. When the server is running, a message is displayed on the server console containing instructions on accessing the installation over VNC. NOTE If you are performing a remote installation over VNC, also use the ipaddress=X netmask=X and gateway=X parameters to enable your static network from the beginning. This is necessary to configure OES components later in the installation. In addition to VNC configuration, many other Linux kernel options can be passed using this field. For information on these options, see the online OES Linux or SLES documentation. F1 Help This invokes the GRUB help screen. Use this option immediately after selecting one of the other function-key options for help on that specific topic. F2 800x600 If you are encountering graphical problems during the OES Linux installation, use this option to select an appropriate screen resolution. F3 CD-ROM This option is used to select between a CD-ROM-based installation and one of several alternate installation methods. Depending on the option selected, you will be prompted to provide the information required to perform that type of installation. Possible installation options are CD-ROM SLP FTP HTTP NFS SMB Hard Disk F4 English This option can be used to change the language used on the GRUB screen. F5 Silent This option is used to adjust the log level during the startup of the installation program. If problems are encountered starting the installation, set this option to Native. F6 Driver If you are using hardware that requires drivers that do not ship with OES Linux, use this option to load those drivers prior to beginning the installation process. After configuring any installation options, parameters or installation sources, select Installation and press Enter.
3.	Read through the license agreement. (The English agreement can be found near the bottom of the page.) When finished, select I Agree to begin the installation.
4.	Select the appropriate language for the installation and click Accept.
5.	Select the type of installation being performed from the following list. After deciding on an installation type, click OK to continue. New Installation This will begin a new installation of OES Linux using default settings that will overwrite any existing operating system already on the disk. Update an Existing System This option can be used to update an installed version of Linux to OES Linux. This will attempt to preserve configuration settings from the installation of Linux being upgraded. Repair Installed System This option can be used to repair a damaged OES Linux installation. Boot Installed System This option will attempt to boot the Linux distribution that is currently installed on the local hard disk. This is useful if the Master Boot Record (MBR) or Bootloader has been damaged, and the installation will not boot automatically. Abort Installation This option can be used to abandon the installation process without writing data to the hard disk.
6.	The Installation Settings page, shown in Figure 2.3, is now displayed. This is the main configuration page, which allows you to determine general options for the OES Linux install process. System This option invokes the hardware detection process, which scans for all devices attached to the server. At the conclusion of the scan, you have the option to review the scan results, and save those results to a file. Mode This provides access to the initial list of possible installation types: New Installation, Update an Existing Installation, Repair Installation, and Boot Installed System. Keyboard Layout This option is used to select and test an appropriate keyboard layout. Mouse This option is used to select and test the mouse configuration to ensure that the correct driver is in use. Partitioning This option invokes the YaST Partitioner, which is used to create and modify your disk partitioning scheme. The default partition configuration is based largely on the type of installation you are performing (New Install or Update). The default partitioning can be used as a base for further customizing, or the default recommen- dations can be ignored and partitioning can be manually defined. Software This option is used to configure which SLES and OES Linux components will be installed on the new server. Upon selecting this option, you are presented with the Software Selection window, which is used to select an installation pattern for the server. Possible installation patterns were explained earlier in this chapter. Figure 2.3. Installation Settings page. Although there are a wide variety of installation patterns available, it is possible that one matching your requirements does not exist. In this case, select the Detailed Selection option to customize your installation. The Detailed Selection option invokes the YaST Install and Remove Software module, as shown in Figure 2.4. Figure 2.4. Detailed Software SelectionYaST Add and Remove Software. From this module, it is possible to select OES Linux components, such as Novell Virtual Office, or individual software packages, such as NOVLice, or findutils-locate. To select OES components, ensure that the Filter drop-down box is set to Selections. To locate specific software packages, change the Filter to Search and use the resulting dialog to locate the desired software. After customizing your installation, select Accept to finalize the installation choices. Prior to accepting the changes, software dependencies are checked. If additional software must be installed in addition to your selections, an informational dialog is displayed. Click Continue to accept the automatic changes, and return to the main Installation Settings page. Booting This option is used to adjust the default configuration of the GRUB bootloader. Time Zone This option is used to select the current time zone in which the server is located. The server's clock can also be adjusted and designated as using GMT or local time. Language This option is used to adjust the default language of the OES Linux installation. Default Runlevel This option is used to adjust the default runlevel of the server. Possible runlevel settings are 2 Multiuser mode with limited network support 3 Multiuser mode with full network support. 5 Graphical, multiuser mode with full network support For more information on runlevels, see Chapter 6, "SUSE Linux Enterprise Server Management."
7.	When satisfied with the configuration of your installation, click Accept.
8.	Prior to beginning the installation, the YaST installation process will warn you that the installation process is about to begin. When prompted with this warning, select Yes, Install to begin the installation process.

At this point, the configuration of the installation process is complete, and the second stage of the install is begun. The second stage of install is responsible for performing the tasks configured in stage one.

CREATE FILESYSTEM AND COPY FILES

The second stage of the installation process requires no manual user intervention for network-based installations. Installations being performed via CD-ROM will require you to swap disks when prompted.

The following processes are completed during this phase:

1. The disk partitions are formatted with the filesystem you selected during the installation configuration.

2. When the filesystems exist, the file copy process can begin. This process will display a progress bar and estimated usage time remaining on the current installation disk. If you are performing an installation using CD-ROM media, this phase will require you to swap the CDs.

3. At the end of the file copy process, the GRUB bootloader configuration is written to the disk. When this is complete, the system is rebooted to begin the final configuration phase.

At the conclusion of phase two, the final phase of installation is the configuration phase. This phase is used to customize the components that were installed on the server during phase two.

CONFIGURE OES COMPONENTS

After the server has performed the first reboot, the operating system is loaded off the root filesystem, and the final phase of the installation is automatically started. Among other things, this phase configures the OES components, so pay careful attention.

A number of steps need to be completed in the final phase of installation. First, on the root password configuration page, enter the password for the root, administrative user. After entering the password twice, click Next to continue.

Next, the Network Configuration page is used to adjust network settings, including the server's IP address, hostname, default gateway, and DNS information. OES Linux requires a static IP address that can be configured through these steps:

1.	Select the Network Interfaces link.
2.	If your device was automatically configured, select Change to adjust the networking parameters. If the device was not automatically configured, select your device in the available devices list and click Configure.
3.	In the Network Cards Configuration Overview, select the appropriate device and click Edit. If no device is listed, select Add to manually add your card.
4.	In the Network Address Setup page, shown in Figure 2.5, complete the following configuration options: Setup Method In the Setup Method box, ensure that the Static Address Setup radio button is selected. After selecting this option, enter the IP Address and Subnet Mask for your OES Linux server. Host Name and Name Server This option is used to configure the host name and domain name of your OES Linux server. Name resolution (local DNS client) is also configured through this option. Routing Use this option to configure a default route on your OES Linux server. Figure 2.5. Network Address Setup options.
5.	When finished, click Next to save your network configuration.

When prompted to test your Internet connection and download the latest product updates, select No. This option can be performed after installation using Red-Carpet. Click Next to continue.

Complete the installation by following these steps:

1.

At the Service Configuration screen, you have the option to configure your Certificate Authority (CA) and your OpenLDAP server. The CA password is defaulted to match the password specified for the root user. If you would like a higher level of security, it is recommended that you change this at this time. The OpenLDAP server should be left as disabled.

2.

At the main Open Enterprise Server Configuration screen, you have the option of configuring the components now or later. It is typically best to configure the components now. If you are performing an installation over VNC, and did not specify a static IP address configuration, select to configure later and skip to step 9. Click Next to continue.

3.

Select New Tree to install your OES Linux server into a new eDirectory tree. Select Existing Tree if you are adding this server to an existing eDirectory tree. Enter either the new or existing eDirectory tree name in the appropriate field and click Next.

4.

If you selected to install a new eDirectory tree, enter the new, fully distinguished name of the admin user and a password for the user. If you are installing into an existing eDirectory tree, enter the current admin name and password, as well as the IP address of a server in the existing tree. Click Next to continue.

5.

Enter the eDirectory context in which the new server will be installed. Also make any necessary changes to port assignments and click Next.

6.

Enter the IP address of the Network Time Protocol (NTP) server you are using for time synchronization. This should be the time source used to synchronize both NetWare and Linux servers if in a mixed environment.

SLP is also configured on this screen. SLP is required for eDirectory trees consisting of more than three servers. If you are unsure of how to configure SLP, see the online OES documentation.

7.

The eDirectory configuration is written to the disk and the eDirectory daemon is started; this step may take some time.

8.

When the eDirectory daemon has started, you are presented with a list of all OES components selected for installation (shown in Figure 2.6).

Figure 2.6. OES component configuration settings.

From this main OES Component screen, each OES component can be configured. To configure an OES component, select the desired component name. This will invoke a dialog box specific to the component and similar to the one shown in Figure 2.7.

Figure 2.7. Health Monitoring LDAP configuration.

Each OES component has a specific list of requirements that may need to be configured. Table 2.1 shows the requirements for each component.

Table 2.1. OES Component Configuration Options

OES COMPONENT	CONFIGURATION OPTIONS	NOTES
iManager	eDirectory Tree Admin name with Context	These parameters should be configured automatically and do not normally need adjustment.
Health Monitoring	Directory Server Address Admin name with Context Admin Password	This component requires an LDAP connection to a local or remote eDirectory tree.
		The default configuration uses an LDAP connection to the eDirectory tree on the local server.
Linux User Management	Directory Server Address Admin name with Context Admin Password Linux/Unix Config Object LUM Workstation Context (Optional) Proxy user name with context (Optional) Proxy user password PAM-enabled services to integrate with eDirectory	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the the local server. In addition to the LDAP configuration, a LUM configuration object, and location for users must be configured. The following PAM-enabled services can be configured for use with LUM:
		login	rlogin
		ftp	passwd
		sshd	xdm
		su	openwbem
		rsh
eGuide	Directory Server Address Admin name with Context Admin Password	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server.
Novell Samba	Directory Server Address Admin name with Context Admin Password LDAP server Host IP address Base Context for Samba users eDirectory tree name with context proxy user password	This component requires an LDAP connection to a local or remote eDirectory tree.This default configuration uses an LDAP connection tree on the local server. Samba also requires additional information such as the LDAP server used for client authentication, and the location of Samba users in the eDirectory tree.
iPrint	Directory Server Address Admin name with Context Admin password iPrint eDirectory Tree Name	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server. iPrint also requires the name of the eDirectory tree.
Novell Storage Service (NSS)	Directory Server Address Admin name with Context Admin Password NSS Unique Admin object	This component requires an lDAP connection to a local or.remote eDirectory tree The default configuration uses an LDAP connection to the eDirectory tree on the local server. The NSS unique Admin Object is a user in eDirectory who should have administrative rights to NSS.
NetStorage	Directory Server Address Admin name with context Admin Password (Optional) iFolder 2 Server Address Authentication Domain Host Proxy user password User Context	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration usesan LDAP connection to the eDirectory tree on the local server. If NetStorage is to be integrated with iFolder, enter the iFolder 2 server address..The authentication domain host, proxy user name and password, and location in eDirectory for your NetStorage users are also required.
QuickFinder	LUM Enable Admin User QuickFinder Admin name QuickFinder Admin Password	You have the option of using a LUM-enabled user or local user account for administering QuickFinder.
	Add novlwww user to shadow group Admin name with Context Admin Password	If local user accounts will also be used with QuickFinder, you must select to add the novlwww user to the shadow group. The eDirectory admin name and password are also required for this component.
Virtual Office	Directory Server Address Admin name with Context Admin Password Virtual Office server address or DNS Hostname User Context	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server. The Virtual Office server address and context in eDirectory for Virtual Office users are also required.
Novell Cluster Services (NCS)	Directory Server Address Admin name with Context Admin Password Cluster fully distinguished name Cluster IP Address (Optional) Device for SBD partition	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server. NCS can be configured at a later date (after configuring hardware components such as a SAN). If you choose to configure NCS now, you can connect the server to an existing cluster or create a new cluster. New clusters require the name of the cluster and an IP address for the cluster. The device for the SBD partition is optional, but should be specified when creating new clusters.
NCP Server	Admin name with Context Admin Password	The NCP Server is a component of eDirectory and does not normally require modification.
Storage Management Services (SMS)	Directory Server Address Admin name with Context Admin Password	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server.
iFolder 2.x	Directory Server Address Admin name with Context Admin Password iFolder 2.x Server IP Address iFolder 2.x Server Netmask iFolder 2.x Server DNS Host Name iFolder 2.x user data path iFolder 2.x admin users	This component requires an LDAP connection to a local or remote eDirectory tree. The default configuration uses an LDAP connection to the eDirectory tree on the local server. If iFolder will be the only web application on the server, specify the path to the user data. If iFolder will be running alongside other web applications, iFolder must have a dedicated IP address. Specify the dedicated IP address, netmask, and DNS hostname in addition to the path to user data.

9.

After the configuration of your OES components, the SuSEconfig process is used to update local configuration files.

10.

Following SuSEconfig, Novell Open Enterprise Server Release Notes are displayed. Be sure to review this document for last-minute notices regarding OES. After installation, the release notes can be found in the /usr/share/doc/release-notes directory. When finished, click Next to continue.

11.

At the Hardware Configuration screen you have the option to configure video and sound. If you are performing a VNC-based installation, video can only be configured after installation using sax2 at the server console. Make any necessary changes on this screen, and then click Next.

12.

The Installation Completed page provides basic information about getting started with OES. After reviewing this page, click Finish to exit the installation program.

Your OES Linux server is now fully installed and ready for use. To begin further customizing of OES, access the OES Linux home page at the following URL:

http://<Server_IP_Address_or_DNS_Name>