| StorageTek Tape Analytics Installation and Configuration Guide Release 2.0.1 E41585-03 |
|
 Previous |
 Next |
| StorageTek Tape Analytics Installation and Configuration Guide Release 2.0.1 E41585-03 |
|
Previous |
Next |
Before installing Linux on the STA server, review the system requirements in the STA Requirements Guide.
|
Note: You cannot perform an in-place upgrade of Linux 5.x to Linux 6.x. If you are installing Linux 6.x as part of an upgrade to STA 2.0.x, consult Chapter 9, "Upgrading STA." |
To install and configure Linux for STA, perform the tasks in Table 1-1.
Table 1-1 Linux Installation Tasks
Due to the wide variety of network configuration requirements and options, refer to the following documents for help with installing and configuring the hardware, software, and network. IPv4 and IPv6 network configuration are discussed in detail in these documents.
Oracle Linux Installation Guides:
http://www.oracle.com/technetwork/topics/linux/index-099698.html
RedHat Linux Documentation:
You must obtain Oracle Linux from the Oracle Software Delivery Cloud website. If you do not have a user ID and password, contact Oracle Support.
Navigate to the Oracle Software Delivery Cloud website:
Click Sign In/Register.
Enter the user ID and password provided by Oracle Support.
On the Terms & Restrictions screen, select the boxes to indicate your acceptance of the License Agreement and Export Restrictions, and then click Continue.
On the Media Pack Search screen:
In the Select a Product Pack menu, select Oracle Linux.
In the Platform menu, select x86 64 bit (STA requires 64-bit Linux).
Click Go.
Select a Linux version, and then click Continue.
For Linux version requirements, see the STA Requirements Guide.
Click Download for the 64-bit option.
Save the ISO file and write it to media.
The following procedures assume an Oracle Enterprise Linux (OEL) 6u4 DVD installation with graphical installer and setup agent. If you install a different version of Linux, use different media, or use the console mode, the steps and packages may vary.
Check with your system administrator to obtain:
Hostname and IP address for the STA server
Gateway IP address and netmask for your network
DNS server IP addresses and search domains for your network
IP address of the NTP (network time protocol) servers you will be using
Network proxy information, if applicable
Connect the installation media to the STA server.
Start the Linux installer using the instructions in the README file on the media.
Select Install or upgrade an existing system.
If you are installing from a DVD, the CD Found screen appears. You can optionally perform a test of the media. To skip the test, press Tab to highlight the Skip option, and then press Spacebar.
On the Welcome screen, click Next.
Select a language, and then click Next.
Select a keyboard layout, and then click Next.
Select Basic Storage Devices, and then click Next.
Enter a hostname for the STA server, and then click Configure Network.
Select the network adapter name, and then click Edit.
Ensure that Connect automatically and Available to all users are both selected.
In the remaining tabs, configure the adapter as per your network administrator's IPv4 or IPv6 specifications. You must specify a static IP address for the STA server, and at least one DNS server. When done, click Apply, Close, and Next.
Select the STA server's time zone, select the System clock uses UTC check box, and then click Next.
Enter and confirm a root password for the server, and then click Next.
Identify a partitioning layout to use on the server:
Because STA requires a dedicated server, Oracle recommends selecting Use All Space.
Select the Review and modify partitioning layout check box, and then click Next.
Use Table 1-2 to modify the filesystem layout, as the default does not meet the minimum requirements for STAFoot 1 . When done, click Next.
|
Note: Oracle recommends creating all of these filesystems in advance of installing STA; otherwise, STA will be installed in the "/" and /var directories, requiring additional space allocation to those directories. While the STA installer will create directories as needed, you will have greater control of filesystem properties if you create them in advance. |
Table 1-2 Recommended Filesystem Structure
| Filesystem | Directories/ Mountpoints | Size | Purpose | Recommendations |
|---|---|---|---|---|
|
root |
/ |
32 GB minimum |
/tmp files |
If /tmp is contained on this filesystem, a minimum of 4 GB of free space should be maintained. This space is required during STA installations and upgrades. |
|
STA Oracle |
/Oracle |
20 GB minimum 30 GB optimum |
STA application |
This should be a separate filesystem on a separate volume. Maintain a minimum of 4 GB free space for STA installations and upgrades. Maintain an additional 5 GB free space for WebLogic log rotation. STA creates the following Oracle Middleware subdirectories:
|
|
swap |
None |
1/2X-1X RAM |
Swap space |
None. Defined as memory. |
|
STA var |
/var/log/tbi |
10 GB minimum 50 – 100 GB optimum |
STA logs |
This should be a separate volume at this mount point. Content is managed through log rotation. Note: Except for log rotation, STA does not perform space management. Caution: You must configure the STA backup utility to manage the log files in /var/log/tbi/db/stadb_bin. Otherwise, these files may require manual management (see "MySQL Binary Logs" in the STA Administration Guide). |
|
STA_DB |
/dbdata |
250 GB – 2 TB |
STA database |
Oracle highly recommends you place this directory on its own volume, separate from /root, /swap, /Oracle, and /var, on separate mirrored or striped drives. Required size depends on the number of libraries, drives, media, exchanges per day, and historical years of data. Oracle recommends that you configure STA services to alert if space utilization exceeds a specified percentage. |
|
STA_DB local backup |
/dbbackup |
60-70% of /dbdata |
STA last local DB backup |
This should be on a different volume from /dbdata, and on mirrored or striped drives, in case of database corruption or failure. |
When ready, select Write changes to disk.
In the boot loader screen, leave all options as-is, and then click Next.
In the software selection screen, select Basic Server, and do not change the repository options. Then, select Customize now, and then click Next.
In the package selection screen, use Table 1-3 to configure the packages for each package category:
Select a package category.
Select the box for each package in the Select column.
If a package requires an option (indicated with a +), highlight the parent package, click the Optional packages button, select the child package in the list, and then click Close.
Deselect the box for each package in the Deselect column.
Leave other check boxes as-is.
Table 1-3 Linux Package Selection
| Package Category | Select | Deselect |
|---|---|---|
|
Base System |
|
|
|
Servers |
|
NA |
|
Web Services |
NA |
All packages |
|
Databases |
NA |
All packages |
|
System Management |
NA |
NA |
|
Virtualization |
NA |
NA |
|
DesktopsFoot 2 |
|
NA |
|
Applications |
|
NA |
|
Development |
|
NA |
|
Languages |
NA |
NA |
Footnote 1 Optional.
Footnote 2 Recommended. Used to perform certain post-installation steps in a graphical environment, as documented later in this chapter.
Footnote 3 Optional. Can be used to configure or re-configure the filesystem once Linux installation is complete.
Footnote 4 Optional. Can be used to locally configure and manage the STA server with the GUI interface.
When you are finished with package selection, click Next. Installation will begin.
If you accidentally click Next before configuring all the packages, click Back after the software completes a dependency check.
When the Congratulations screen appears, remove the installation media, and then click Reboot.
A complete log of the installation can be found in /root/install.log.
The Linux Setup Agent starts automatically when you reboot the Linux server.
On the Welcome screen, click Forward.
Read the License Agreement, select Yes, I agree to the License Agreement, and click Forward.
On the Software Updates screen, if you'd like to register your system for updates, select Yes, I'd like to register now. Otherwise, select No, I prefer to register at a later time, and click Forward.
On the Finish Updates Setup screen, click Forward.
On the Create User screen, leave the fields blank, click Forward, and then Yes to continue. The STA server does not require a non-administrative user.
In the Date and Time screen:
Set the current date and time.
Select the Synchronize date and time over the network check box.
Add or remove the desired NTP servers (obtained from your IT administrator), and then click Forward.
|
Note: To ensure that STA data and log files are correct, the date and time on the STA server must be correct. Additionally, any library connected to STA must also have the correct time. |
On the Kdump screen, do not select Enable kdump?, and then click Finish.
The system will reboot.
After the system reboots, log in as the root user:
Click Other....
Enter username root, and then click Log In.
Enter the root password, and then click Log In again.
If a message appears about being logged in as root super user, you may ignore the message.
(Optional) You can confirm the Linux release and update level by issuing the following command:
# cat /etc/issue
Oracle Linux Server release 6.4
Kernel \r on an \m
Oracle recommends disabling SELinux on the STA server.
Open a terminal session on the STA server.
Open the SELinux configuration file with a text editor.
# vi /etc/sysconfig/selinux
In the file, set SELINUX to disabled:
SELINUX=disabled
Save and exit the file.
Oracle recommends disabling the firewall on the STA server. However, you may choose to enable and configure the firewall depending on your site requirements.
To disable the firewall:
Open a terminal session on the STA server.
Check the settings of the Linux firewall (for next boot) by issuing the following command:
# chkconfig --list |grep "ip"
If the firewall is set to be disabled on next boot, all output for both iptables and ip6tables will show as off. If this is not the case, disable the firewall:
# chkconfig iptables off # chkconfig ip6tables off
Check the current status of the Linux firewall by issuing the following commands:
# service iptables status # service ip6tables status
The command output will indicate if the firewall is currently running. If the firewall is running, stop the firewall:
# service iptables stop # service ip6tables stop
If either of the following is true, you will need to reboot the server.
You disabled SELinux in Task 1.
You disabled the Linux firewall (using chkconfig) in this section.
Access control must be disabled for certain directories.
Execute the ls -ld command for the /Oracle, /dbbackup, /dbdata, and /var/log/tbi directories.
# ls -ld directory-name
For example:
# ls -ld /Oracle drwxr-xr-x 5 root root 4096 Mar 11 15:09 /Oracle # ls -ld /dbbackup drwxr-xr-x 5 root root 4096 Aug 8 2013 /dbbackup
In the output for each command, look for a dot at the end of the stated permissions. In the below example, note the "." after drxwr-xr-x:
# ls -ld /Oracle drxwr-xr-x. 5 root root 4096 Mar 17 18:27 /Oracle
If none of the directories contain a period after the permissions statement, access control is already disabled, and you can skip to the next task. If access control is enabled on a directory, as root, execute the following command for that directory:
# setfattr -h -x security.selinux directory-name
For example:
# setfattr -h -x security.selinux /Oracle
You can configure the STA server to connect to the network directly or through a proxy server.
From the Linux desktop, select System > Preferences > Network Proxy.
In the Network Proxy Preferences dialog box, specify the proxy configuration per your site requirements.
Click Close.
Yum (Yellowdog Updater, Modified) is used for managing software package updates. Use this procedure to ensure that yum is configured correctly on the STA server.
The following command examples use the yum repository for Oracle Linux. In these commands, the ”l” in ”ol6” is lowercase 'L'.
|
Note: This procedure assumes you can reach Oracle's public yum server. If your network firewall prohibits external network access, you can install locally available packages from the Linux media. For example:# cd /mnt/install-media-mount-location/packages # yum install ./package-name |
Ping the Oracle public-yum server to ensure the network connection is working.
# ping public-yum.oracle.com
Change to the yum repository directory and determine the yum repository filename.
# cd /etc/yum.repos.d # ls public-yum-ol6.repo
Remove the existing yum repository file.
# rm public-yum-ol6.repo
Download the latest yum repository file from the yum website.
# wget http://public-yum.oracle.com/public-yum-ol6.repo
|
Note: Subsequent executions of this command will copy a new repository file into the yum.repos.d folder with a new extension (for example, public-yum-ol6.repo.1). However, yum always uses the repository file with no extension. |
Open the repository file with a text editor.
# vi public-yum-ol6.repo
In the file, locate the entry that matches your Linux version and enable it by setting enabled=1. Disable all other entries by setting enabled=0.
For example:
[Linux_Version] name=Oracle Linux $releasever Update x installation media copy ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/x/base/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=1
Save and exit the file.
Additional packages are required for STA installation and operation. The STA installer will check for these packages — if they are not present, STA installation will fail.
Depending on your specific Linux installation, some of these packages may have already been installed. If a package is already installed and at the most current version, the system will notify you.
|
Note: The command used to install the packages will check for and install the most current version (and any dependencies) for your specific Linux version. |
To install the packages, do the following.
Open a terminal session on the STA server.
Issue the following command:
# yum install package_name
The package will be downloaded and checked. Follow the prompts to install the package. Repeat this step for each of the following packages:
|
|
|
Use this procedure to ensure that SSH (secure shell) is set up correctly on the STA server. This will speed up transfers of STA database backups to a remote host.
Open the SSH configuration file with a text editor.
# vi /etc/ssh/sshd_config
Search for the AddressFamily and UseDNS entries. Modify them so they are not preceded with the comment character and their values are as follows:
AddressFamily inet UseDNS no
Save and exit the file.
Restart the sshd daemon.
# service sshd restart
Use this procedure to ensure that the STA server's IP address is mapped to its hostname.
Open the hosts file with a text editor.
# vi /etc/hosts
At the end of the file, add the STA server's IP address, followed by a tab, and then the STA server's hostname. For example:
127.0.0.1 localhost localhost.localdomain localhost4...
::1 localhost localhost.localdomain localhost6...
192.0.2.20 sta_server
Save and exit the file. You do not need to restart the STA server for the new setting to take effect.
Name services such as LDAP can conflict with STA installation. Use this procedure to temporarily disable these services.
Open the Name Service Switch config file with a text editor.
# vi /etc/nsswitch.conf
Disable any name service entries. For example, to disable LDAP, comment out "ldap" from the following lines as shown:
passwd: files #ldap nis nisplus shadow: files #ldap nis nisplus group: files #ldap nis nisplus
Save and exit the file. You do not need to restart the STA server for the new setting to take effect. After you install STA, you can modify the nsswitch.conf file to re-enable the name services.
During STA installation, a temporary local user and group, "install", will be created. If this fails for any reason (for example, due to site security policies), then the installation will fail. Use the following procedure to ensure that this user and group can successfully be created.
Check the user and group definition files for "install".
# grep "install" /etc/passwd /etc/group
Expected result: Neither user nor group should exist (no results are returned).
Test that the "install" user and group can be created.
# useradd install # grep "install" /etc/passwd /etc/group
Example output:
/etc/passwd:install:x:501:501::/home/install:/bin/bash /etc/group:install:x:501:
If either the user or group was not created, investigate your site for the failure reason.
Remove "install" prior to installing STA.
# userdel install
To configure and administer STA locally on the STA server, ensure you have the minimum supported browser versions and plugins installed (see the STA Requirements Guide).
|
Note: Oracle does not recommend local access to the STA application due to server performance degradation. |
Footnote Legend
Footnote 1: Alternately, you can modify the filesystem after Linux installation with the system-config-lvm utility.
|
 Copyright © 2012, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|