-C H A P T E R

C H A P T E R 2

Installing Sun StorEdge Configuration Service on a Solaris Host

This chapter provides procedures for installing Sun StorEdge Configuration Service consoles and agents on a Solaris host. Topics covered in this chapter include:

Before Installing Sun StorEdge Configuration Service

System Requirements

Installing Software

Users and Passwords

Uninstalling Sun StorEdge Configuration Service

Restoring a Configuration

Troubleshooting

Before Installing Sun StorEdge Configuration Service

Before installing the program and its related software components, take the following steps:

Be sure to read the release notes for your array.

Install OS updates. To use Sun StorEdge Configuration Service on a Solaris host, you need to install the most current Sun recommended OS patches and Java runtime environment software patches for the Solaris 8 and Solaris 9 OS. For a list of Sun recommended patches, refer to the release notes for your array.

System Requirements

This section lists the system requirements for the Solaris host.

Netscape Navigator web browser - You require the web browser to view online help. Versions earlier than 4.0 are not supported.

TCP/IP-compliant network interface - Each console must have a TCP/IP-compliant network interface (such as an Ethernet or Token Ring network card, or a serial line with a modem). Each agent must have a TCP/IP-compliant network interface and driver set (included with the operating system).

Color monitor - The console is best viewed with a monitor resolution of 1024 x 768 pixels with 256 colors.

OS, memory, and disk space - TABLE 2-1 lists the console system requirements for the Solaris OS. TABLE 2-2 lists the agent system requirements for the Solaris OS.


Solaris OS Version	Memory	Disk Space
Solaris 2.6 with Sun recommended patches Solaris 8 and Solaris 9 with Sun recommended patches on SPARC platforms Solaris 9 x86 Platform Edition (9 08/03) with Sun recommended patches. (For a list of Sun recommended patches, refer to the release notes for your array.)	256 Mbyte required 512 Mbyte recommended	40 Mbyte minimum 100 Mbyte recommended


Solaris OS Version	Memory	Disk Space
Solaris 2.6 with Sun recommended patches Solaris 8 with Sun recommended patches on SPARC platforms Solaris 9 x86 Platform Edition (9 08/03) with Sun recommended patches. (For a list of Sun recommended patches, refer to the release notes for your array.)	128 Mbyte required 512 Mbyte recommended	20 Mbyte minimum 100 Mbyte recommended

Installing Software

Sun StorEdge Configuration Service includes the following components:

Sun StorEdge Configuration Service agent

Sun StorEdge Configuration Service console

Sun StorEdge Diagnostic Reporter (optional utility)

Command-Line Interface (CLI)

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.

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 to 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.

Installation Packages

The Sun StorEdge Configuration Service agent and console installation packages are contained on the Sun StorEdge 3000 Family Professional Storage Manager CD. Sun StorEdge Configuration Service on a Solaris OS offers language support for French, Japanese, Simplified Chinese, Traditional Chinese, and Korean. TABLE 2-3 specifies which files are required for each language.

If the translated software and documentation for Sun StorEdge Configuration Service version 1.5 are not available on the CD, or if you need to access the translated software and documentation for Sun StorEdge Configuration Service version 1.3, go to: http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/EOL_Products/index.html. Each language requires the English installation package for the console and the agent.


	English	French	Japanese	Simplified Chinese	Traditional Chinese	Korean
Agent	`SUNWscsd`	`SUNWscsd SUNWfscsd`	`SUNWscsd SUNWjscsd`	`SUNWscsd SUNWcscsd`	`SUNWscsd SUNWtscsd`	`SUNWscsd SUNWkscsd`
Console	`SUNWscsu`	`SUNWscsu SUNWfscsu`	`SUNWscsu`SUNWjscsu	`SUNWscsu SUNWcscsu`	`SUNWscsu SUNWtscsu`	`SUNWscsu SUNWkscsu`

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.

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.

If you are installing only the English version of the package, follow only the instructions for English. If you are adding language support, you must install the English version of the program first.

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.

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 on a Solaris 2.6 host is 1.3.1. The earliest release of Java runtime environment software that is compatible with Sun StorEdge Configuration Service on a Solaris 8 or 9 host is 1.2.

Note - You must uninstall earlier versions of Sun StorEdge Configuration Service when upgrading the console or agent. For details on uninstalling, see Uninstalling Sun StorEdge Configuration Service.

1. Insert the Sun StorEdge 3000 Family Professional Storage Manager CD and type:

# cd /cdrom/cdrom0/product/solaris/$ARCH

where $ARCH is either sparc or i386, depending on the Solaris OS version.

2. Install the packages in one of the following ways:

To install only the agent (English), type:

# pkgadd -d . SUNWscsd

(Optional) To add language support, type:

# pkgadd -d . SUNWxscsd

where x is f, j, c, t, or k, depending on what language you are installing. See TABLE 2-3 for package names.

To install only the console (English), type:

# pkgadd -d . SUNWscsu

(Optional) To language support, type:

# pkgadd -d . SUNWxscsu

where x is f, j, c, t, or k, depending on what language you are installing. See TABLE 2-3 for installation package names.

To install all packages, type:

# pkgadd -d . all

To choose which packages to install from a menu, type:

# pkgadd -d .

To install English versions of both agents (Sun StorEdge Configuration Service and Sun StorEdge Diagnostic Reporter) type:

# pkgadd -d . SUNWscsd SUNWscsa

(Optional) To language support, type:

# pkgadd -d . SUNWxscsd SUNWxscs

where x is f, j, c, t, or k, depending on what language you are installing. See TABLE 2-3 for installation package names. For Sun StorEdge Diagnostic Reporter package names, see Installing Sun StorEdge Diagnostic Reporter.

3. Provide appropriate responses to each of the standard installation prompts.

The installation prompts are standard pkgadd prompts regarding which packages to install and how to process scripts (with superuser privileges).

a. At the Select packages prompt, type the appropriate response depending on the install method.

For example, if you chose to install only the agent (English), type 1 and press Return.

Select package(s) you wish to process (or `all' to process all packages). (default:all) [?,??,q]: 1

If asked if you want to restore the agent configuration, type y. (If you type n, you will need to re-enable the managing servers.)

The previous configuration was saved. User passwords must be reentered. Do you want to restore the configuration [y,n,?,q]: y

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 as described in Users and Passwords.

If asked if you want to restore the console configuration, type y. (If you type n, you will need to readd the server information.)

The previous configuration was saved. Do you want to restore the configuration [y,n,?,q]: y

b. To continue with the installation, type y and press Return.

Do you want to continue with the installation [y,n,?] y

After the agent is installed, the following message is displayed, indicating the agent was installed successfully and has started.

Configuring and starting Sun StorEdge(tm) Configuration Service agent daemons:

       The configuration is complete.

       Sun StorEdge(tm) Configuration Service agent server daemon has started.

       Sun StorEdge(tm) Configuration Service agent monitor daemon has started.

Sun StorEdge(tm) Configuration Service agent startup is complete.

Installation of <SUNWscsd> was successful.

The installation program checks that Java runtime environment software is installed. The earliest release of Java runtime environment software that is compatible with Sun StorEdge Configuration Service is 1.2. If the installation program cannot find it, you are asked to specify the path. If you know that Java runtime environment 1.2.2, 1.3, or 1.4 software has been installed but the installation program cannot find it, check the /usr directory to confirm there is a link to the latest version. For instructions on creating the link, see, Troubleshooting.

The agent and console are installed in /opt/SUNWsscs/sscsconsole.

After the installation is complete, the agent starts automatically.

4. To access online help, you need to specify the path to the web browser.

a. Change to /opt/SUNWsscs/sscsconsole and type:

./config_sscon

b. Type the absolute path to the web browser.

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.

5. For Sun StorEdge 3310 SCSI arrays, edit /kernel/drv/sd.conf if:

Third-party HBAs with multiple drives and multiple LUNs are used

Fibre devices are used

All LUNs have the same ID

Add lines for LUNs as appropriate for your configuration. LUNs can be numbered from 0-31. Generally, do not add more LUN definitions than you actually plan to have, since doing so increases the time needed to scan each SCSI bus. For information on modifying the sd.conf file, refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for your SCSI array.

6. If the sd.conf file has been edited, perform a reconfiguration reboot.

If the sd.conf has not been edited, you do not have to perform a reconfiguration reboot and the agent starts automatically.

To Stop or Start the Agent

The agent can be stopped and started manually by using the run commands script in /etc/init.d/ssagent.

1. To stop the agent, type:

# /etc/init.d/ssagent stop

2. To start the agent, type:

# /etc/init.d/ssagent 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 agents.

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.

4. If the storage system is not being displayed after initial boot, stop the agent, and at the command prompt, run:

# format

5. Label the desired disks, and then restart the agent.

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 a Solaris 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 levels.

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:

ssmon

Represents the monitoring level of the software.

ssadmin

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

ssconfig

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 login names are required for the three security levels. After installation, you must assign a password to each security name.

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.

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 a Solaris host.

Administrators might also want to change group permissions, which are defined in the svrlist.dat file located in the /opt/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.

To Uninstall Sun StorEdge Configuration Service

Use the pkgrm command followed by the package you want to uninstall.

Note - If you added French, Japanese, or Simplified Chinese language support, you need to uninstall those packages before uninstalling the English package.

# pkgrm package-name

where package-name is the package you are uninstalling. See Installation Packages for a list of package names.

Restoring a Configuration

If you reinstall the agent or console, during the installation procedure you are asked whether you want to restore the configuration. If you select to have the configurations restored, the information is restored from the following files:

/var/opt/SUNWsscs/sscsagt.cfg.tar - Sun StorEdge Configuration Service agent

/var/opt/SUNWsscs/sscscon.cfg.tar - Sun StorEdge Configuration Service console

Note - If you are removing Sun StorEdge Configuration Service permanently, you might want to manually remove these files; however, if you later reinstall the program, you will not be able to restore the agent and console configurations.

Troubleshooting

When installing Sun StorEdge Configuration Service, running java -version might return a pre 1.2.2 software version even if the machine has Java runtime environment 1.2.2, 1.3, or 1.4 installed. If this happens, check that there is a link from Java runtime environment software to the latest version.

1. Check the /usr directory to confirm there is a link to the latest version of the Java runtime environment by typing:

# cd /usr

ls | grep java

If the link is not to the latest version listed, type:

rm java

ln -s /usr/xxx /usr/java

where xxx is the latest version of the Java runtime environment software.