| StorageTek Automated Cartridge System Library Software Installation Guide Release 8.3 E48579-06 |
|
 Previous |
 Next |
| StorageTek Automated Cartridge System Library Software Installation Guide Release 8.3 E48579-06 |
|
Previous |
Next |
ACSLS 8.3 is supported to run on Solaris 10, Updates 10 and 11, and Solaris 11, Update 1.
This chapter describes procedures for installing ACSLS 8.3. Topics include:
In addition to the Oracle Right to Use License for ACSLS, this product contains numerous third-party software components, each with its own license criteria. Read the THIRDPARTYLICENSEREADME.txt agreement located in the ACSLS_8.3.0 installation directory. For software components whose license requires re-distribution of the source code, you can find that source code under the initial package installation directory, ACSLS_8.3.0 (typically under /opt). Look in the subdirectory, acsls_thirdPartySoftware/.
If you are upgrading from a prior release, you need to export the database and control files. As user acsss, run the command:
db_export.sh -f myExport
In the example above, myExport is the name you assign to your export file. You should save myExport and myExport.misc to a non-volatile location. If you are updating your OS, then transfer these files to a remote machine for safe keeping.
For more information and procedures, refer to Exporting the Database in the ”Database Administration” chapter of the StorageTek ACSLS 8.3 Administrator's Guide.
If you have created additional ACSLS GUI users on ACSLS 8.1 or later releases, record those user IDs so you can re-add them after installing the new version of ACSLS. To do this:
As user acsss:
cd $ACS_HOME/install
Type su root.
Do not type su - root if you want to retain your acsss environment.
Run userAdmin.sh to get a list of existing users of the ACSLS GUI:
./userAdmin.sh
Select the List Users option and then the Exit option when you have finished.
Record the user IDs so you can re-add them later as described in "Adding Users of the ACSLS GUI".
This section describes the steps to install Solaris.
For installation procedures, please refer to the Solaris Installation instructions.
ACSLS 8.3 was tested using the Entire Distribution selection for the Solaris install. Oracle does not provide a minimum list of required packages for ACSLS, but the Entire Distribution is recommended.
Your Solaris installation should "Enable remote services" to ensure that network client applications are able to communicate with the ACSLS server.
If you select the Solaris "Secure by Default" installation option, then it is necessary to alter a network configuration property for rpc-bind. To do this:
Check the property setting:
# svccfg -s rpc/bind listprop config/local_only
If the local_only property setting is true, you must set it to false.
# svccfg -s rpc/bind setprop config/local_only=false
ACSLS 8.3 may be installed in any file system. The ACSLS base and the ACSLS backup directories (for example, /export/home and /export/backup) must be mounted to allow SETUID so user acsss can run as root. Super user access is required for scripts that start and stop ACSLS services and for scripts that collect diagnostic information for a support call.
The acsss umask is set to 027 during installation.
Network services, specifically rpcbind, must be enabled to allow ACSLS client communication unless the firewall security on ACSLS and all ACSAPI clients is configured without the need for the portmapper. For more information, see the ACSLS Administrator's Guide, "Firewall Security Option" for details.
Three ACSLS user accounts, (acsss, acssa, acsdb) are added automatically when you install the ACSLS package.
The package install creates an acsls group and assigns all three users to this group. It also adds root to the acsls group.
If user accounts for the three acsls users already exist, the user home directory and group id will be adjusted automatically (if necessary) by the package install routine.
ACSLS 8.3 allows for a user-defined home directory for the ACSLS application. The parent directory of each user home directory is referenced by the variable, $installDir. The user home directories for ACSLS are:
acsss $installDir/ACSSS acssa $installDir/ACSSA acsdb $installDir/acsdb/ACSDB1.0
If user accounts already exist for these users and you are changing the $installDir, then these users must be logged out of the system during the installation since their home directory will change.
If the user accounts already exist and they are locked, they must be unlocked before you install the package.
To check if the acsss account is locked:
# passwd -s acsss acsss LK
The "LK" tells you that the account is locked. To unlock the account:
# passwd -u acsss
Do this for each user account.
If these user accounts exist on an LDAP or NIS server and the root user on the local machine lacks usermod authority on the LDAP or NIS server, then manual intervention by the system administrator is needed to complete the ACSLS installation. Make sure the users are re assigned to the acsls group and their home directories conform as stated in the fourth bullet. The user shell should be: /bin/bash
Specific automated schedules known as crontabs are created for users acsss, and acsdb when you run the install.sh utility. These crontabs are provided for ACSLS database maintenance backup activities.
An optional file /etc/cron.d/cron.allow may exist on the system. This file controls which users are allowed to run the crontab command. If cron.allow exists, then user IDs for acsss and acsdb must be included in that file before you run install.sh. Otherwise, crontab creation for these users fail.
The file cron.deny exists by default on most systems. Any users listed in this file are explicitly denied access to the crontab command. Make sure that acsss and acsdb are not contained in the cron.deny file.
Is this a new installation?
YES - go to "Installing the ACSLS Package"
NO - make sure you exported the database by using the db_export.sh utility command.
Shut down ACSLS:
You need to be logged in as acsss to do this.
acsss shutdown
Remove any acsss and acsdb crontab entries:
crontab -r acsss crontab -r acsdb
If you are migrating from a release prior to 8.1, remove these user accounts.
A change was introduced in ACSLS 8.1 that affects the group association for users acsss, acsdb, and acssa. If you are installing from a release prior to 8.1, there are steps you should take before installing the STKacsls package for 8.3. First remove the ACSLS user accounts as explained in the steps below. These accounts are re-created when you install the new STKacsls package for ACSLS 8.3.
# userdel acsss # userdel acsdb # userdel acssa
su to root and perform the following:
cd /var/tmp rm -rf acsls cd /var/mail rm -f acsss acsdb acssa
Remove ACSLS, backup and other files:
ACSLS 6.0 or 6.0.1
cd /export/home rm -rf ACSSS informix cd /export/backup rm -rf informix misc
ACSLS 6.0 or 6.0.1 and the server_to_server directory exists
cd /export/home rm -rf informix misc server_to_server cd / rm -rf INFORMIXTMP nsr
ACSLS 6.1 to 7.1
cd /export/home pkgrm STKacsls cd /export/backup rm -rf informix misc server_to_server cd / rm -rf INFORMIXTMP rm -rf /nsr d /var/tmp rm -rf acsls
ACSLS 7.2 to 7.3.1
cd /export/home pkgrm STKacsls rm -rf ACSSS ACSSA acsdb cd /export/backup rm -rf *
(this removes all contents of the backup directory)
ACSLS 8.0 to 8.0.2
cd /export/home pkgrm STKacsls rm -rf ACSSS ACSSA acsdb SSLM cd /export/backup rm -rf *
ACSLS 8.1 to ACSLS 8.3
cd /export/home pkgrm STKacsls rm -rf ACSSS ACSSA acsdb SSLM wlinstall Oracle cd /export/backup rm -rf *
If pkgrm STKacsls fails because the database server is running, you may need to kill postmaster processes. To do this:
Run: ps -rf | grep post
Kill the parent postmaster process.
Run pkgrm STKacsls again.
For ACSLS releases before 7.2, remove files under second disk (if installed).
cd /second_disk
If you installed the second disk in another directory other than /second_disk, cd to that directory.
rm -rf data cd /second_disk/backup
If you installed the second disk in another directory other than /second_disk/backup, cd to that directory.
For ACSLS 6.0 - 7.1, enter:
rm -rf informix misc
Verify that no database processes are running before you begin the install. If in doubt, reboot.
|
Note: If you are removing ACSLS (and not installing a new version), remove the ACSLS user IDs from/etc/cron.d/cron.allow. |
ACSLS 8.3 installs in any directory. Determine the base install directory where the ACSLS application should reside. If that directory does not exist, you should create it before installing the STKacsls package. The directory must be owned by root with permissions set to 755.
|
Note: Unless otherwise specified by the user, ACSLS will be installed in/export/home. |
To follow the default installation procedure:
Go to the Oracle Software Delivery Cloud website, and find the ACSLS_8.3.0 software bundle available for both SPARC and X86 platforms.
ACSLS_8.3.0_SPARC.zip
ACSLS_8.3.0_X86.zip
Download the appropriate software bundle to a common installation directory, typically /opt, and unzip the compressed file. The extracted package set is found in the resulting ACSLS_8.3.0 subdirectory.
Go into the ACSLS_8.3.0 directory and run the command:
./pkg_install.sh
The pkg_install script first prompts you to confirm your intent to install ACSLS 8.3.
A number of packages are included with the ACSLS 8.3 installation bundle. They include STKacsls and five SUNW packages that support PostgreSQL. The SUNW packages typically reside already on Solaris 10, but if not, they are installed automatically by the pkg_install.sh routine.
On Solaris 11 the specific SUNW packages are not already installed, so they are installed automatically when you run the pkg_install script. Review the license for each package and respond y to accept the package.
Before installing the STKacsls package, the script prompts you (y/n) whether to accept /export/home as the default base directory for the ACSLS application.
If you answer n, the script asks you to enter the desired path to the package base directory. If the directory you specify does not exist, the script prompts for permission create the directory.
When the package installation is complete, you find that the packages in
ACSLS_8.3.0 have been moved to /var/spool/pkg. They remain there for ease of re-installation until they are manually removed. What remains in
ACSLS_8.3.0 is pkg_install.sh, pkg_uninstall.sh, and README.txt. You can use these scripts to uninstall or re-install ACSLS at any time.
The package installation utility creates user and group IDs for the following users: acsss, acssa, and acsdb. It assigns home directories for these users and places them in the acsls group. The root user is also added to the acsls group.
On systems where users acsss, acssa, and acsdb may already exist, advise those users to log out before you install the package. The package install fails if the user is logged in while it should be necessary to change the user's home directory. This will happen in upgrade contexts where you have defined a different install directory from the previous ACSLS installation.
|
Note: Secure administration practices recommend that you to set initial passwords for these users immediately after the package installation. |
Once the ACSLS packages are installed, root needs to inherit the ACSLS environmental attributes. To do this, log out and log back in, or simply
su - to inherit the acsls group identity. Verify with the groups command.
su - # groups root acsls
(other groups may be listed)
To set your shell to the ACSLS installation environment, source the.acsls_env file:
. /var/tmp/acsls/.acsls_env
This step enables you to refer to $ACS_HOME during subsequent installation operations.
Proceed to "Running install.sh".
The install.sh utility enables you to select from the extracted ACSLS 8.3 package the specific features required for your unique Oracle StorageTek library environment. Flexibility has been added in ACSLS 8.3, allowing you to choose whether to install options including the Graphical User Interface (GUI) and fibre library support. You can run this utility to install the entire product, any portion of the product, or to alter an already-installed product without the need for a full installation.
While you are still logged in as root, run the commands:
cd $ACS_HOME/install ./install.sh
Database creation is first step in the install.sh routine. This step is necessary if you are installing the package for the first time. If your ACSLS database already exists and you do not want to rebuild it, then you have the option to skip this step. This step creates a new database under PostgreSQL and establishes an automated schedule for database backups.
Determine the directory where you intend for the database to reside. If that directory does not exist, then you must first create the directory. The directory must be owned by root with permissions set to 755. Unless you specify otherwise, the backup directory will be placed directly under your base directory. See step-1(c) in "Installing the ACSLS Package".
The install.sh routine asks:
Which file system will be used to store database backups? [/export/backup]
Click Return to select the suggested directory, or specify a different directory. If you assign a relative path, it is placed directly under the desired path that you assigned in step-2 in the previous section, "Installing the ACSLS Package".
The install routine proceeds to load policy modules. These allow the ACSLS application to freely access its PostgreSQL database.
The mchanger driver is relevant only to fibre-attached or SCSI-attached library configurations. The install.sh routine asks:
Shall we install the mchanger driver for fibre-attached libraries? (y/n)
Respond with y or n whether your library environment includes a fibre-attached library such as the SL500 or SL150 library.
If you enter y, the routine scans the attached SAN environment, looking for any StorageTek library devices. It reports the devices it finds and prompts whether any additional libraries are attached. If you have an older SCSI attached L700 or L180 library, respond y to the prompt.
For SCSI attached libraries, simply enter the target:lun address for each library, separating them by a space. For example:
==> 4:0 5:0 5:1
ACSLS can present logical libraries to client applications over a fibre connection. Any portion of an attached physical library can be represented as a (SCSI) fibre-attached library with a fibre target port. To implement this capability, you must have a QLogic fibre HBA. This step converts one or more QLogic HBA ports from their default initiator mode to target mode.
The install.sh routine probes the system for qualified HBAs, and then lists the ports it finds with the following prompt:
Please select the HBA port you intend for Target-mode operation: 1) HBA Port WWN xxxyyyzzz Not connected 2) HBA Port WWN aaabbbccc Connected to a remote HBA
Select the desired port by the corresponding number. The port you choose must be connected to a remote HBA.
If you are installing logical libraries, then the ACSLS GUI is a required feature. Simply proceed with the GUI installation procedure described below.
If you chose not to install support for Logical Libraries, then the GUI installation is an option. To install the GUI:
Enter y at the following prompt:
Do you want to install the ACSLS Graphical User Interface? (y/n)
If this is a minor update or configuration change (not a new installation) your ACSLS GUI may already be installed.
In this case, you will have the option to re-install the GUI or to skip this section and retain the current ACSLS GUI domain. The install routine prompts:
The Acsls GUI Domain exists. Do you want to re-install it? (y/n
Select one of the following:
Enter y if you are installing a new ACSLS release.
The WebLogic server package is extracted and the default GUI admin user account is created with the user name, acsls_admin.
You are then asked to assign a password for the admin user. The password must be between eight and sixteen characters using both alpha and numeric characters.
The install procedure unpacks and deploys the ACSLS GUI application and then creates the Acsls user group. At a later time, you can add GUI users to this group using the administrative tool, userAdmin.sh.
If you enter n, you have the option (y/n) whether to remove the existing GUI configuration.
When you install WebLogic on your ACSLS server, a simple 512-bit public key is automatically available to support basic https exchanges with client browsers. Normally, no further configuration should be necessary. However, some browsers, notably the Microsoft Internet Explorer, require a lengthier key of no less than 1024 bits. Refer to "Configuring an SSL Encryption Key" for a description of and procedures for configuring an SSL encryption key.
The lib_cmd feature is a command-line interface that performs many of the same operations that can be performed in the ACSLS GUI. This tool is installed automatically if you choose to install the GUI. While many lib_cmd operations apply to logical library functions, this feature is also useful for displaying the status of physical libraries, volumes and drives. The option to install lib_cmd is presented when support for logical libraries was not selected.
Shall we install the optional lib_cmd interface (y or n):
Depending on the set of features that you have selected in the above installation dialog, this final step installs Solaris SMF services to control the automatic start, stop, and status functions for each selected ACSLS feature.
The service list includes any subset of the following:
acsdb acsls smce rmi-registry surrogate stmf weblogic
During install.sh, you created the acsls_admin user. This user can now create accounts and assign passwords for other users of the ACSLS Web-based GUI application. You can refer to the list of GUI users that you saved earlier. To add a user, follow this procedure:
As root, go to the /export/home/ACSSS/install directory.
Run ./userAdmin.sh.
Enter the acsls_admin password that you assigned in "Installing the Graphical User Interface."
From the menu, select (1) to add a new user.
Enter the ID of the user you want to add.
Assign a password for that user.
Passwords must contain eight characters with a combination of alpha and numeric or special characters.
You can use the userAdmin.sh utility at any time to add or delete users or to change passwords for all ACSLS GUI users. See userAdmin.sh in the Utilities chapter of the StorageTek ACSLS 8.3 Administrator's Guide.
To complete ACSLS installation continue with "Getting Started". This chapter provides information on importing the database or configuring your library hardware and verifying your ACSLS Installation.
|
 Copyright © 2013, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|