C H A P T E R  6

Installing Sun StorEdge Configuration Service on an IBM AIX Host

This chapter provides procedures for installing Sun StorEdge Configuration Service consoles and agents on an IBM AIX host. Topics covered in this chapter are as follows:


System Requirements

This section lists the system requirements for the IBM AIX host.

 

TABLE 6-1 Console System Requirements for IBM AIX OS

IBM AIX OS Version

Memory

Disk Space

4.3.3 and 5.1L

256 Mbyte minimum

512 Mbyte recommended

40 Mbyte minimum

100 Mbyte recommended

 

 


 

TABLE 6-2 Agent System Requirements for IBM AIX OS

IBM AIX OS Version

Memory

Disk Space

4.3.3 and 5.1L

128 Mbyte minimum

512 Mbyte recommended

20 Mbyte minimum

100 Mbyte recommended

 



Installing Software

Sun StorEdge Configuration Service software includes the following components:

For installation information for Sun StorEdge Diagnostic Reporter, see Installing Sun StorEdge Diagnostic Reporter. For installation information for the CLI, see Installing and Accessing the Command-Line Interface.

Installation Packages

The installation packages are contained on the Sun StorEdge 3000 Family Professional Storage Manager CD, and include the following files:



Note - Before installing Sun StorEdge Configuration Service, be sure to read the release notes for your array.





Note - You must be superuser to install Sun StorEdge Configuration Service and run the console.



Upgrading Software - Agent and Console Version Compatibility

Because the communication protocol changes from version to version, you must install both the agent and console when upgrading. If different versions of the agent and console co-exist, Sun StorEdge Configuration Service is not able to discover previously configured arrays.


procedure icon  To Install the Agent and Console

Install the agent on each of the servers that is part of Sun StorEdge Configuration Service. Install the console on the computer or workstation you plan to use for managing and maintaining the storage system.

The console can be installed on the server or on any client system. The agent must be installed on the server to which the storage is attached.

installed on the server to which the storage is attached.

If you are upgrading, you must install both the agent and console. If different versions of the agent and console co-exist, Sun StorEdge Configuration Service is not able to discover previously configured arrays.

Complete the following steps to install the agent, console, or both. You must install at least one agent and one console for the program to run.



Note - Make sure that Java runtime environment software is installed on the computer or workstation on which you are installing Sun StorEdge Configuration Service. The earliest release of Java runtime environment software that is compatible with Sun StorEdge Configuration Service is 1.3.



1. If Java runtime environment software is not installed on the computer or workstation on which you are installing Sun StorEdge Configuration Service, install it now.

To check the Java runtime environment software version, type:

# java -version

2. Insert the Sun StorEdge Professional Storage Manager CD and type:

# mount -v cdrfs -o ro CD-ROM-drive

3. To install the agent, type:

# installp -a -d /cdrom/product/aix/SUNWscsd.bff

4. To install the console, type:

# installp -a -d /cdrom/product/aix/SUNWscsu.bff

After the agent or console is installed successfully, "SUCCESS" is displayed in the Result column of the Installation Summary.

5. Specify a path to the default web browser.

To access Sun StorEdge Configuration Service online help, Netscape Navigator must be installed on the system on which you are installing the console. Versions earlier than 4.08 are not supported. If a web browser is not detected, you are asked to specify the path to the web browser.

Netscape Navigator is usually installed in /usr/bin/netscape.



Note - You can configure the web browser path name at any time; however, if you do not specify a path name at some point, you cannot access online help.



The agent is installed in /usr/SUNWsscs/ssagent. The console is installed in /usr/SUNWsscs/sscsconsole.


procedure icon  To Stop or Start the Agent

The agent can be stopped or started manually.

1. To stop the agent, type:

# /etc/ssagent.rc stop

2. To start the agent, type:

# /etc/ssagent.rc start



Note - You must be superuser to start the agent.



If you use start without first using stop, the script restarts any agents that have stopped. If all the agents have stopped (as with a stop option) the script reconfigures the runtime environment before restarting the daemons.

3. To determine if the agent is running, type:

# ps -e | grep ss

Both ssmon and ssserver are displayed in the output. If you have enabled SNMP trap generation, you also see the name sstrapd.


Users and Passwords

The following sections explain how to create users and passwords.

Administrative (User) Security Levels and Guidelines

If you are running the program on an IBM AIX host, administrator security levels are automatically created during the installation process. You only need to set passwords and assign users according to the desired permission level.

Administrative functions require access logins and passwords to prevent the possibility of one administrator reallocating or removing storage resources belonging to other clients and hosts without authorization.

You assign separate passwords for the three levels of security for the program. You do this by setting up three users on the agents that have storage devices that are managed by the program. These three users are automatically added during the installation of the agent.

The security levels must have these exact names:

Represents the monitoring level of the software.

Represents the administration level of the software and provides access to the Rebuild, Parity Check, and Schedule Parity Check functions, as well as monitoring.

Represents the configuration level of the software and gives the installer direct access to the configuration functions and all other related aspects of the program.

These names are required for the three security levels. After installation, you must assign a password to each security name.



Note - User passwords are deleted when Sun StorEdge Configuration Service is uninstalled. If you had a previous configuration, you have to reenter the ssmon, ssadmin, and ssconfig passwords



The ssmon, ssadmin, and ssconfig names are logins that correspond only to security levels within the program. For UNIX operating environments, the default shell for these accounts is assigned to /bin/false to prevent the user IDs from being used for interactive logins.

You can set up Sun StorEdge Configuration Service so that monitoring does not require users to type the ssmon password. To do so, select the Auto Discovery option when the servers are added to the Managed Servers list at the console. You can set up these three logins and passwords locally on each server. (The accounts can have different passwords on each server, if desired.)

Once you have set up these three logins on the agents to be managed, the system administrator typically provides user access to the program by assigning employees appropriate passwords, which are based on the level of security required to complete tasks. For example, everyone who has administration privileges on a particular server is assigned the same password that was established for the user ssadmin.



Note - To add servers to the Managed Servers list, refer to the Sun StorEdge 3000 Family Configuration Service User's Guide.




procedure icon  To Create Passwords and Permissions

Create a password for each of the new users by typing:

# passwd user-name

 Screen capture showing an example of the passwd command on an IBM AIX host.

Administrators might also want to change group permissions, which are defined in the svrlist.dat file located in the /usr/SUNWsscs/sscsconsole directory during installation.

The console is a Java technology-based utility, and as such, cannot provide facilities to control permissions or ownership of files that Sun StorEdge Configuration Service creates. The svrlist.dat file is easily readable by various forms of ASCII text processors. It contains the encrypted password for the user ssmon and can be decrypted.



Note - Do not change the permissions and group ownership of svrlist.dat after adding all agents that are being monitored.




Uninstalling Sun StorEdge Configuration Service

You must uninstall earlier versions of Sun StorEdge Configuration Service when upgrading the console or agent. Note that some files are not removed because they are created after the installation and are still valid for the upgrade environment.


procedure icon  To Uninstall Sun StorEdge Configuration Service

Use the installp -u command followed by the package you want to uninstall,. SUNWscsd (agent) or SUNWscsu (console).

# installp -u SUNWscsd
# installp -u SUNWscsu