Sun Management Center 4.0 Installation and Configuration Guide

Chapter 4 Preparing Systems for Sun Management Center Upgrade and Installation

This chapter provides procedures for preparing your Solaris and Microsoft Windows systems for Sun Management Center 4.0 installation.

This chapter discusses the following topics:

Compatibility With Other Software and Earlier Versions of the Product

Sun Management Center 4.0 software is compatible with the following software:

Any Simple Network Management Protocol (SNMP) v1, v2, v2 usec, and v3 entities, regardless of the Operating System and architecture.
Solstice Enterprise Agents^TM software for Solaris 8, Solaris 9, and Solaris 10 Operating System versions. Solstice agents can coexist with Sun Management Center agents on the same host system if you configure the Solstice agents as subagents of the Sun Management Center agent. See Configuring a Legacy SNMP Agent as a Subagent of an Agent.

Sun Management Center software does not offer the following features:

Backward compatibility with the Solstice SyMON™ 1.x software
SunVTS™ support in the Sun Management Center 4.0 software

Preinstallation Checklist

The following list describes the tasks that you need to perform before you can install Sun Management Center 4.0, or upgrade an existing Sun Management Center installation to Sun Management Center 4.0.

Determine which components of Sun Management Center 4.0 and which product add-ons you want to install on each machine on your network.
- Make sure the platforms on which you want to install Sun Management Center or Sun Management Center components are supported platforms. See Supported Platforms.
- For minimum RAM and disk space requirements, see Chapter 1, Installing Sun Management Center 4.0. Also, refer to the Sun Management Center add-on product supplements at http://docs.sun.com.
  
  Total the amount of RAM and disk space needed for the selected components and add-on products.
- Ensure that each machine is running the correct operating system for the components you want to install. See Table 1–3 and Table 1–4.
Ensure that the correct JDK version is installed on machines that are designated for the Sun Management Center server and console components. See Table 1–3. You can download the JDK software from http://java.sun.com/.
Set the PATH and the JAVA_HOME environment variables.
- For the Solaris platform:
  
  Make sure that the DISPLAY and JAVA_HOME environment variables are set in any account that is used to run the Sun Management Center Web or Java console.
  
  The default location for JDK versions 1.5 is /usr/j2se. See To Set JAVA_HOME and PATH on the Solaris Platform.
- For the Microsoft Windows platform:
  
  Ensure the path to the JDK bin directory is added to the Microsoft Windows %PATH% environment variable.
If any machine on your network has 4 Gbytes of RAM or more, install the 64–bit compatibility patch SUNWscpux on the machine. See Solaris Systems With More Than 4 Gbytes RAM.
Select the installation source.

You can install from a media or from installation images. See Determining the Installation Source.

Prerequisite Packages

The following Solaris operating environment packages are required by the Sun Management Center 4.0 server layer, and are included as part of the Solaris developer environment installation.

SUNWsprot - Solaris Bundled tools
SUNWtoo - Programming Tools
SUNWbtool - CCS tools included with SunOS

Solaris Systems With More Than 4 Gbytes RAM

The SUNWscpux 64–bit source compatibility package must be installed on systems that have more than 4 Gbytes of RAM before you can install Sun Management Center 4.0. If the package is not installed, the command-line installation process will report the following messages and fail.

ps: read() on /proc/551/as: Value too large for defined data type
ps: read() on /proc/542/as: Value too large for defined data type

The SUNWscpux package is installed automatically during Solaris installation when any of the following Solaris environments are selected.

Entire +OEM
Entire
Developer

To determine if the package is installed on the system, type the command pkginfo SUNWscpux in a terminal window.

If the package is installed, information about the package is displayed.

# pkginfo SUNWscpux
system      SUNWscpux      Source Compatibility (Usr) (64-bit)

If the package is not installed, an error message is displayed.
# pkginfo SUNWscpux ERROR: information for "SUNWscpux" was not found
To install the SUNWscpux package:
1. Log in as root (su - root).
2. Locate the package on the Solaris installation media.
3. Install the package using the pkgadd command.

Java Environment Variables and Path

The JAVA_HOME and PATH environment variable must be set on Solaris systems in order for the Sun Management Center 4.0 installation wizards, the setup wizards and the Java console to function properly. Similarly, the Microsoft Windows %PATH% must be modified to include the path to the JDK software for the Sun Management Center Java console to work properly on Microsoft Windows.

If the environment variables and path are not set properly, installation and setup of Sun Management Center 4.0 can fail.

To Set `JAVA_HOME` and `PATH` on the Solaris Platform

You must set the JAVA_HOME and PATH environment on the Solaris platform if the JDK 1.5 software has been installed in the default location on your system.

Set JAVA_HOME to /usr/j2se.
- In a C shell environment:
  # setenv JAVA_HOME /usr/j2se
- In a Bourne or Korn shell environment:
  # JAVA_HOME=/usr/j2se # export JAVA_HOME
Tip –
Add the appropriate statement to your .login or .cshrc file.

Add /usr/j2se/bin to your system path.

Place /usr/j2se/bin in your PATH before /usr/bin.

Place /usr/bin in your PATH before /usr/ucb.

To Set `PATH` on Microsoft Windows 2000

Choose Start -> Settings -> Control Panel.

Double-click System.

Select the Advanced tab and then Environment Variables.

The Environment Variables window is displayed.

Click Path in the User Variables and System Variables and click Edit.

The Edit System Variable window is displayed.

Note –
The Edit System Variable window shows the Microsoft Windows root directory using the environment variable %SystemRoot%.

Add the location of the JDK bin directory to the PATH statement.

For example, if the PATH statement shown in the Edit System Variable window is %SystemRoot%\system32;%SystemRoot%, the new path statement would then be %SystemRoot%\system32;%SystemRoot%;c:\j2version-number\bin where version-number is the JDK version.

For example:

%SystemRoot%\system32;%SystemRoot%;c:\j2sdk1.5\bin

Separate each directory in the PATH statement with a semicolon as shown.

Click OK to successively close each window.

To Set `PATH` on Microsoft Windows XP

Choose Start -> Settings -> Control Panel.

Double-click System.

Select the Advanced tab and then Environment Variables.

The Environment Variables window is displayed.

Click Path in the User Variables and System Variables and click Edit.

The Edit System Variable window is displayed.

Note –
The Edit System Variable window shows the Microsoft Windows root directory using the environment variable %SystemRoot%.

Add the location of the JDK bin directory to the PATH statement.

For example, if the PATH statement shown in the Edit System Variable window is %SystemRoot%\system32;%SystemRoot%, the new path statement would then be %SystemRoot%\system32;%SystemRoot%;c:\j2version-number\bin where version-number is the JDK version.

For example:

%SystemRoot%\system32;%SystemRoot%;c:\j2sdk1.5\bin

Separate each directory in the PATH statement with a semicolon as shown.

Click OK to successively close each window.

To Set `PATH` on Linux

Change to your home directory.

cd $HOME

Open the .bashrc file.

Add the following line to the file. Replace the JDK-directory with the name of your Java installation directory.

export PATH=/usr/java/JDK-directory/bin:$PATH

Save the file and exit.

Use the source command to force Linux to reload the .bashrc file which normally is read only when you log in each time.

source .bashrc

Note –
Note that if you wish to set the PATH for all users, you need to log in as root in the bash shell and perform the above steps on the .profile file in the etc directory and not the .bashrc file in the home directory.

Determining the Installation Source

You can install, set up, and configure Sun Management Center 4.0 using either the Sun Management Center installation DVDs or a Sun Management Center installation image located on your network. DVD images eliminate the need to install Sun Management Center on each machine from the DVDs.

This section provides the procedures for creating Sun Management Center installation images.

There are two methods for capturing an installation image. You can copy Sun Management Center installation DVDs to a location on your network. You can also download and unpack the Sun Management Center installation image from the Sun Management Center Web site.

Note –

To install, set up, and configure , you must be logged in as root on Solaris machines, and as administrator on Microsoft Windows.

Creating Installation DVD Images

To create the Sun Management Center DVD images, you create a directory to contain the images, copy the DVD to the directory, and then share the directory using network file system mounting.

To Create DVD Images

In a terminal window, log in as root by typing su - root.

Create a directory to which you will copy the DVD.

For example:
# mkdir /SunManagementCenter

Change to the directory you created for the DVD images.

For example:
# cd /SunManagementCenter

Create a diskn directory for each DVD, where n is the sequence number of the disk.

For example:
/SunManagementCenter# mkdir disk1 disk2

Make sure the vold daemon is running.

/SunManagementCenter# ps -eaf | grep vold
root 19033 19000  0 08:37:55 pts/9    0:00 vold
/SunManagementCenter#

If the grep command returns only the system prompt, then the vold daemon is not running, and must be started as follows:

/SunManagementCenter# /usr/sbin/vold &

Insert Sun Management Center 4.0 DVD in your DVD drive.

List the contents of the Sun Management Center 4.0 DVD. Then copy the contents to the disk1 subdirectory.

When the copy completes, list the contents of the DVD and the directory to verify the contents of the disk image.

For example:

/SunManagementCenter# cp -r /DiskMountDir/.* disk1
/sunmanagementcenter > ls -acp /DiskMountDir/.*
.          .CD        Copyright  image/      lib/
..         .CD01      classes/    install/    sbin/
/sunmanagementcenter > ls -acp disk1
.          .CD        Copyright  image/      lib/
..         .CD01      classes/    install/    sbin/

Caution –

<DiskMountDir> is a symbolic link. Copy only the Sun Management Center directory as shown in the above example.

Make the Sun Management Center 4.0 DVD image directory NFS-shared.

Using NFS to share the DVD image directory enables you to install Sun Management Center 4.0 from other machines by using the DVD installation images instead of manually installing from the DVDs.
1. Stop the Network File System daemon mountd:
  /SunManagementCenter# /etc/init.d/nfs.server stop
2. Add the following line to the /etc/dfs/dfstab file.
  
  share -F nfs -o ro image-dir
  
  where image-dir is the Sun Management Center 4.0 image directory that you created in Java Environment Variables and Path.
  
  For example: share -F nfs -o ro /SunManagementCenter
3. Save and close /etc/dfs/dfstab.
4. Start the Network File System daemon mountd:
  /SunManagementCenter# /etc/init.d/nfs.server start
  The Sun Management Center 4.0 image directory is now accessible from other machines.
You can now use the Sun Management Center DVD images to install Sun Management Center 4.0, or to upgrade previous versions of Sun Management Center as described in the following chapters.

Creating Images From the Download Tar File

You can download the Sun Management Center Sun Management Center compressed tar file from the Web to a Solaris machine on your network. You then decompress and untar the tar file to a image directory.

To download Sun Management Center, you must be registered with Sun as a Sun Web site user, and log in using your registered user ID. The download software Web page provides a link for registration.