Skip Headers
Oracle® Real User Experience Insight Installation Guide
Release 6.0.1 for Linux x86-64

Part Number E16360-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Installing the Linux Operating System

This chapter describes the procedure for installing Oracle Enterprise Linux 5.3. However, the procedure for installing Oracle or RedHat Enterprise Linux 5.x is very similar.

2.1 Introduction

The procedure for installing Oracle Enterprise Linux 5.3 is fully described in the product documentation. This section presents a summary of that procedure, and assumes a sound knowledge of Linux system administration.

For information on vendor-specific variations, consult the appropriate documentation. The installation procedure described is based on the use of a DVD media package.

Obtaining the Linux Operating System

The Oracle Enterprise Linux 5.3 software is available from the Oracle E-Delivery Web site (http://edelivery.oracle.com/linux).

Planning Network Interfaces

For remote access, one interface with a fixed IP address is required for each server. For a Collector (and an all-in-one RUEI server), one (SPAN/copy) or two (TAP) interfaces without IP address, are required.

For explanation of the RUEI global settings specified in the rest of this section, see Section 4.3.1, "The RUEI Configuration File".

Planning the Software Installation Location

Depending on installation location of the database and the RUEI software, the necessary disk space needs to be carefully planned. During operating system installation, you will need this information at hand during the disk partitioning phase.The following are the disk space requirements when using the default installation locations indicated throughout this guide:

Note:

As of RUEI release 5.1, a Collector only system does not require any database.

2.2 Download ISO Image and Burn DVD

  1. Download the appropriate ISO image. This guide assumes you are using the DVD version of Oracle Enterprise Linux 5.3.

  2. Unzip the files.

  3. Burn the ISO file to DVD. Note that this requires the use of a DVD-burning utility (such as UltraISO or Magic ISO Maker).

    Note:

    According to your corporate policy, the Linux installation procedure may use a different procedure to that described in the following sections.

2.3 Run Installer

Note:

After installing Linux on the first node, repeat the Linux installation procedure for each system.
  1. Ensure that server system is able to boot from DVD. Insert the Oracle Enterprise Linux DVD, and power on.

  2. When the Oracle Enterprise Linux boot screen appears, press Enter to start the installation process.

  3. When asked to test the DVD media, select Skip. After a short interval, the installer goes into GUI mode. (The media test is not necessary because the DVD burning software would have informed you of any errors on the media).

  4. At the Welcome to Oracle Enterprise Linux screen, click Next.

  5. Select the appropriate options from the Language and Keyboard settings screens.

  6. If the installer detects a previous version of Enterprise Linux, you are prompted to "Install Enterprise Linux" or "Upgrade an existing installation". Select "Install Enterprise Linux", and click Next.

Important:

Oracle recommends that you install the Linux operating system with the default software packages (RPMs), and that you do not customize the RPMs during installation. This installation includes most required packages, and helps you limit manual checks of package dependencies.

2.4 Set up Disk Partitioning

  1. When prompted, select the default Remove Linux partitions on selected drives and create default layout option, and check the option Review and modify partitioning layout. When prompted to confirm your selection, select Yes. Click Next to continue.

    Important:

    For security reasons, it is strongly recommended you check the Encrypt System check box so that all sensitive data is stored in a secure manner. A passphase is required during booting the system.
  2. When prompted to confirm the removal of all partitions, click Yes.

  3. Review and modify (if necessary) the automatically selected disk partitions.

    For most automatic layouts, the installer assigns 100 MB for /boot, 2 GB for swap, and the remainder is assigned to the root (/) partition. Ensure the specified SWAP space is sufficient. See Table 2-1 and Table 2-2 for required disk space and swap space requirements.

    The installer creates a disk configuration using the Logical Volume Manager (LVM). For example, it will partition the first hard drive (/dev/sda in the described configuration) into two partitions: one for the /boot partition (/dev/sda1), and the remainder of the disk dedicated to a LVM named VolGroup00 (/dev/sda2). The LVM Volume Group (VolGroup00) is then partitioned into two LVM partitions: one for the root file system (/), and another for swap. If you have selected a non-standard layout, ensure that the system meets the required disk space specifications shown in Table 2-1. Ensure enough swap space is allocated for Oracle Enterprise Linux. Its required swap space is shown in Table 2-2.

Table 2-1 Required Disk Space Specifications

Partition Minimum Required Disk Space (GB)

ORACLE_BASE (default /u01/app/oracle)Foot 1 

300

RUEI_HOME (default /opt/ruei)

1

RUEI_DATA (default /var/opt/ruei/)

100


Footnote 1 This is the example location of the database used throughout this guide.

Table 2-2 Required Swap Space

Available RAM Swap Space Required

Up to 8192 MB

Equal to the size of RAM.

More than 8192 MB

0.75 times the size of RAM.


Important:

The Reporter server requires high performance data storage. RAID-10 or RAID-5 (or equivalent) storage configurations with high performance disks are strongly recommended.

Note:

The requirements shown in Table 2-1 and Table 2-2 can vary depending upon the composition and volume of monitored data. For more information, please contact Customer Support.
  1. Accept the GRUB boot loader, as well as all default values, and click Next.

2.5 Network Configuration

  1. Ensure that a static IP address is assigned to the interface used to access the RUEI Web interface. In addition, the assigned IP address and host name should be configured in the /etc/hosts file. If necessary, ensure that all Reporter and Collector systems are correctly defined in the DNS system.

  2. Ensure that the network interface(s) used for network packet monitoring are administratively up, but without an IP address.

    Important:

    Make the network interface up status permanent (after a reboot) by setting the ONBOOT parameter of the capturing interfaces to yes. The network interfaces configuration can be found in /etc/sysconfig/networking/devices/ifcfg-ethX (where X represents the necessary network interface). Alternatively, use the graphical utility system-config-network to perform the above actions.

2.6 Package Installation

  1. Select the appropriate time zone for your environment, and click Next.

    Important:

    In distributed environments, all time zones specified for Reporter and Collector systems must be identical.
  2. Specify a root password, and click Next.

  3. At the additional tasks dialog box shown in Figure 2-1, leave the Customize later radio button checked, leave all the check boxes unchecked, and click Next.

    Figure 2-1 Additional Tasks Dialog Box

    Description of Figure 2-1 follows
    Description of "Figure 2-1 Additional Tasks Dialog Box"

  4. At the About to install screen, click Continue to start the installation.

  5. At the prompt screen, click Next to begin installation of Enterprise Linux.

  6. Upon successful installation, remove the DVD, and click Reboot.

Important:

It is strongly recommended that you use the settings described above, and do not perform a "minimal" installation of Oracle Enterprise Linux. This can lead to a wide range of problems, further described in Section C.8, "Missing Packages and Fonts Error Messages".

2.7 Post-Installation Wizard

  1. When the system boots for the first time, a post-installation wizard appears, and allows you to finalize the operating system configuration settings. Click Forward.

  2. At the User license agreement screen, read the license terms. You will not be able to proceed until you have accepted them. Then click Forward.

  3. Use the screen shown in Figure 2-2 to allow only secure WWW (HTTPs) and SSH traffic. Be aware that, by default, SSH traffic is enabled, but secure WWW (HTTPS) traffic is not. Note that, when prompted with a warning about not setting the firewall, click Yes.

    Figure 2-2 Firewall Configuration

    Description of Figure 2-2 follows
    Description of "Figure 2-2 Firewall Configuration"

  4. Use the screen shown in Figure 2-3 to disable Security Enhanced Linux (SELinux). Click Forward. Note that you are prompted with a warning that changing the SELinux setting requires rebooting the system so that the entire system can be relabeled. Click Yes.

    Figure 2-3 SELinux Configuration

    Description of Figure 2-3 follows
    Description of "Figure 2-3 SELinux Configuration"

    Important:

    Security Enhanced Linux (SELinux) must be disabled for correct operation of RUEI.
  5. Accept the default setting on the Kdump screen (disabled), and click Forward.

  6. Adjust the date and time settings using the screen shown in Figure 2-4. The use of NTP is strongly recommended, and is required in a split-server deployment. Click OK.

    Figure 2-4 Date and Time Settings

    Description of Figure 2-4 follows
    Description of "Figure 2-4 Date and Time Settings"

Important:

In distributed environments, all time zones specified for Reporter and Collector systems must be identical.

2.8 Create Additional Users and Reboot

  1. Create any additional required (non-Oracle) operating system user accounts. Note that during the installation of the RUEI software, the moniforceFoot 1  user account is created. The creation of the oracleFootref 1 user is described in a later section. Do not create either user account at this point.

  2. If prompted, confirm the detection of a sound card.

  3. On the Additional CDs screen, click Finish.

  4. Because the SELinux option has been changed (to disabled), you are prompted to reboot the system. Click OK.

  5. After reboot, use the root user account, and the password you specified during installation to logon.

    Text Mode Installation (Optional):

    When using the text mode installation, by default:
    • Firewall: HTTPS (TCP 443) is blocked.

    • Security: SE Linux is enabled.

    Allow HTTPS traffic (TCP 443) and disable SElinux using the system-config-securitylevel utility.

2.9 Verify NTP Daemon Operation

Because the NTP daemon is a critical component of RUEI, especially in a split Reporter-Collector configuration, it is recommended that you verify that it is activated in at least run level 5 during boot. Use the following commands:

chkconfig --list | grep ntp
ntpd     0:off   1:off   2:off   3:off   4:off   5:off   6:off
chkconfig ntpd on
chkconfig --list | grep ntp
ntpd     0:off   1:off   2:on    3:on    4:on    5:on    6:off
/etc/init.d/ntpd start
Starting ntpd:                                     [  OK  ]

Note that if the NTP daemon is not already running, you can start it with the command

/etc/init.d/ntpd restart

The following sample output show when the NTP daemon is synchronized (indicated by an "*").

ntpq -pn
       remote           refid      st t when poll reach   delay   offset  jitter
  ==============================================================================
  *194.171.167.130     .PPS.         1 u 994 1024 377     6.429   0.041   0.093
  +80.85.129.25        130.235.20.3  3 u 725 1024 377     4.435   0.673   0.129
  +82.94.235.106       135.81.191.59 2 u 678 1024 377     1.709   1.774   0.020
   127.127.1.0         .LOCL.       10 l   8   64 377     0.000   0.000   0.001

Important:

In distributed environments, all time zones specified for Reporter and Collector systems must be identical.


Footnote Legend

Footnote 1: This is the default user names used throughout this guide. For a complete explanation of the settings used by RUEI, see Section 4.3.1, "The RUEI Configuration File".