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 3.5 installation.

This chapter discusses the following topics:

• Preinstallation Checklist

• Prerequisite Packages

• Solaris Systems With More Than 4 Gbytes RAM

• Java Environment Variables and Path

• Microsoft Windows 98 Swap Space and Environment Space

• Sun StorEdge A5x00 Patches

• T3 Storage Devices

• Determining the Installation Source

Preinstallation Checklist

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

• If the Solstice SyMON server, or the Enterprise SyMON server is installed, you must upgrade the SyMON installation to Sun Management Center 2.1 or Sun Management Center 2.1.1 before you can upgrade to Sun Management Center 3.5. See Upgrading from Solstice SyMON 1.x and Sun Enterprise SyMON 2.x Software.

  If you customized the email.sh script that Sun Enterprise SyMON software uses to send email notification of alarm conditions, save the email.sh script to another directory, then move the script back after your upgrade is complete. The email.sh script is overwritten when you upgrade SyMON software to version Sun Management Center 3.5.

  ---

  Note –

  If you do not want to migrate your SyMON configuration data, you must uninstall the SyMON software as described in Uninstalling Solstice SyMON 1.x or Enterprise SyMON 2.x before you can install Sun Management Center 3.5.

  ---

• Determine which components of Sun Management Center 3.5 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 2, Sun Management Center 3.5 Requirements. Also, refer to the Sun Management Center add-on product supplements in the Sun Management Center documentation CD (2 of 2), and the Sun Management Center Web site at http://www.sun.com/solaris/sunmanagementcenter.

    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 2–3 and Table 2–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 2–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 console.

    The default location for JDK versions 1.3.1 and 1.4 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. See To Set PATH on Microsoft Windows 98.

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

• If your network includes StorEdge A5X00 devices, install the required patches. See Sun StorEdge A5x00 Patches.

• If your network includes T3 storage devices, you must update the /etc/hosts and /etc/ethers files on the machine to which the devices are attached. You must also update the /etc/hosts and /etc/ethers files on the machine where you will install the Monitoring and Management of A5X00 and T3 Devices add-on product. See T3 Storage Devices.

• If you are upgrading an older version of Sun Management Center and you use the older version to monitor and manage T3 devices, you must remove Sun Management Center T3 device configuration before performing the upgrade to Sun Management Center 3.5. See Removing T3 Device Configuration If Present.

• Select the installation source.

  You can install from a CD-ROM disk or from CD images. See Determining the Installation Source.

Prerequisite Packages

The following Solaris operating environment packages are required by the Sun Management Center 3.5 server layer, and are included as part of the Solaris development 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 3.5. 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 CD.

  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 3.5 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 3.5 can fail.

To Set JAVA_HOME and PATH on the Solaris Platform

If JDK 1.3.1 or JDK 1.4 software has been installed in the default location:

1. Log in as root by typing su - root.

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

   ---

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

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

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

To Set PATH on Microsoft Windows 98

The following procedure assumes that JDK 1.3.1 or JDK 1.4 software has been installed to the default location C:\j2sdkversion number, for example, C:\j2sdk1.4.

1. Edit the file c:\autoexec.bat.

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

   For example, if the PATH statement in the autoexec.bat file is PATH=c:\windows;c:\windows\command, the new PATH statement would then be PATH=c:\windows;c:\windows\command;c:\j2version-number\bin where version-number is the JDK version.

   For example:

   PATH=c:\windows;c:\windows\command;C:\j2sdk1.4\bin

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

3. Save and close the file.

To Set PATH on Microsoft Windows NT or Microsoft Windows 2000

1. Choose Start -> Settings -> Control Panel.

2. Double-click System.

3. On Microsoft Windows NT, select the Environment tab. On Microsoft Windows 2000, select the Advanced tab and then Environment Variables.

   The Environment Variables window is displayed.

4. Click Path in the User Variables and System Variables.

5. 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%.

   ---

6. 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.4\bin

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

7. Click OK to successively close each window.

Microsoft Windows 98 Swap Space and Environment Space

Microsoft Windows 98 requires a minimum of 768 Mbytes of swap space or virtual memory to run the Sun Management Center 3.5 console. 4096 bytes of environment space are required for the Microsoft Windows 98 and the Sun Management Center environment variables. If the swap space and environment space are not set correctly, Sun Management Center installation could fail and your machine could run out of environment space. Set the minimum swap space and environment space for Microsoft Windows 98 as described in the following procedures.

The following procedures are applicable only to Microsoft Windows 98. Microsoft Windows NT and Microsoft Windows 2000 do not require you to set minimum swap space and environment space.

To Set Microsoft Windows 98 Minimum Swap Space Size

1. Log in as administrator, or as the user account that has full administration privileges.

2. Choose Start -> Settings -> Control Panel.

3. Double-click the System icon.

   The System Properties window appears.

4. Select the Performance tab.

   The Performance Options window is displayed.

5. Select Virtual Memory.

6. Select Let me specify my own virtual memory settings.

7. Type 768 in the Minimum field.

   The value in the Maximum field must be at least three times the amount of total system RAM.

   For example, if your Microsoft Windows 98 machine has 512 Mbytes of RAM, the Maximum field value should be 1536.

8. Click OK.

   The Confirm Virtual Memory Settings dialog box appears.

9. Click Yes in the Confirm Virtual Memory Settings dialog box.

   The dialog box closes.

10. Click Close in the System Properties window.

    The System Properties window closes, and you are prompted to reboot the system.

11. Click Yes to reboot the system.

    The virtual memory settings that you specified are applied and used when the system completes rebooting.

To Set Microsoft Windows 98 Minimum Environment Space Size

1. Add the following line to the config.sys file if the line is not present.

   SHELL=C:\COMMAND.COM /P /E:4096

2. If you added the shell line to the config.sys file, or if you modified the existing shell line, reboot the system.

Sun StorEdge A5x00 Patches

If you want to use the Sun StorEdge A5x00 module, you must install either the SUNWluxop storage patch, or the SUNWluxox storage patch, or both storage patches for the corresponding operating environment. If you load the A5x00 module and did not install the appropriate patch, the Sun Management Center agent cannot run. You can obtain either patch at http://www.sun.com.

Install the patches on the server to which the A5x00 storage device is attached.

T3 Storage Devices

This section provides the procedures for preparing T3 devices for Sun Management Center 3.5, and procedures for removing T3 device configuration data from existing Sun Management Center 2.x or Sun Management Center 3.x installations.

T3 device configuration data must be removed from existing Sun Management Center installations before you can upgrade to Sun Management Center 3.5.

Preparing a T3 Storage Device

Before you install and set up the Sun Management Center T3 Add-on, you must modify the /etc/hosts and /etc/ethers files on the system where the Sun Management Center add-on Monitoring and Management of A5x00 and T3 Devices is to be installed.

The following procedure assumes that you have installed and configured the T3 storage device as described by the Sun StorEdge T3 Disk Tray Installation, Operation, and Service Manual.

When the /etc/hosts and /etc/ethers files have been updated on the machine where the Sun Management Center add-on Monitoring and Management of A5X00 and T3 Devices will be installed, you can proceed with installing and setting up the T3 add-on.

To Prepare a T3 Storage Device

1. Determine the IP address and ethernet address for each T3 storage device.

   Open a terminal window and type the command arp t3-device-name where t3-device-name is the name of the T3 storage device. For example:

   # arp T3-001 T3-001 (10.100.20.300) at 1:2:30:ab:ba:45 permanent published

   In the above example, 10.100.20.300 is the IP address, and 1:2:30:ab:ba:45 is the Ethernet address of the T3 storage device T3-001.

2. Repeat Step 1 for each T3 device on your network.

   When you have recorded the IP address, Ethernet address, and name for each T3, go to the next step.

3. Log in as root on the machine where you will install the Sun Management Center add-on Monitoring and Management of A5X00 and T3 Devices.

   This machine can be either the machine where you install the Sun Management Center server or the machine that you have allocated as dedicated platform agent server.

4. Record each T3 IP address and name in the /etc/hosts file.

   For example, assume that three T3 devices are attached to your network. Assume that you used the arp command to determine the IP address, and Ethernet address of each T3 device, and recorded the information as follows:

   storage-t3–1	172.16.100.10	0:20:f2:0:59:48
   storage-t3–2	172.16.100.11	0:20:f2:0:5f:40
   storage-t3–3	172.16.100.12	0:20:f2:0:7f:a8

   The entries in the server /etc/hosts file would then be as follows:

   172.16.100.10   storage-t3–1
   172.16.100.11   storage-t3–2
   172.16.100.12  storage-t3–3

5. Record each T3 storage device Ethernet address and name in the /etc/ethers file.

   Create the /etc/ethers file if the file does not already exist.

   Using the example given in Step 4, the entries in the server /etc/ethers file would then be as follows:

   0:20:f2:0:59:48   storage-t3–1
   0:20:f2:0:5f:40   storage-t3–2
   0:20:f2:0:7f:a8  storage-t3–3

   ---

   Caution –

   If you include the domain name as part of the T3 device name, make sure the domain name is identical in both the /etc/hosts and /etc/ethers files. The entries are case sensitive.

   ---

   For example, assume that the /etc/hosts file contains:

   0:20:f2:0:59:48   storage-t3–1.sun.com

   Also assume that the /etc/ethers files contains

   0:20:f2:0:59:48   storage-t3–1.Sun.Com

   In this example, the T3 storage device cannot be set up using the Sun Management Center setup tools because the domain name case is different.

Removing T3 Device Configuration If Present

If you monitor and manage T3 storage devices using the Monitoring and Management of A5x00 and T3 Devices add-on, remove T3 device configuration information before you uninstall Sun Management Center 2.x or Sun Management Center 3.x. The es-uninst command does not remove T3 device configuration information.

To Remove T3 Device Configuration

1. Log in as root by typing su - root on the machine where the Sun Management Center 2.x or Sun Management Center 3.x server is installed.

2. Stop the Sun Management Center agent.

   Type the command /opt/SUNWsymon/sbin/es-stop -a.

3. Run the pre-uninstall script to remove T3 device configuration information.

   Type the command /opt/SUNWsymon/addons/storage/sbin/pre-uninst.sh.

   You are asked if you want to stop the T3 from sending syslog messages. Type y. You are then prompted for the root password for the T3 device. Type the password.

   You are notified that the T3 device has been removed from the T3 module.

   • If you do not run the pre-uninst.sh script before you install Sun Management Center 3.5, you will have to manually remove T3 configuration information before you can set up the new Sun Management Center 3.5 installation.

   • If you run the pre-uninst.sh script but then decide to keep your Sun Management Center 2.x or Sun Management Center 3.x installation, type /opt/SUNWsymon/es-setup -F to set up your T3 devices again.

Determining the Installation Source

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

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

• Creating Installation CD Images

• Creating CD Images From the Download Tar File

There are two methods for capturing an installation image. You can copy Sun Management Center installation CDs 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.

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

Creating Installation CD Images

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

To Create CD Images

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

2. Create a directory to which you will copy each CD.

   For example:

   # mkdir /SunManagementCenter

3. Go to the directory you created for the CD images.

   For example:

   # cd /SunManagementCenter

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

   For example:

   /SunManagementCenter# mkdir disk1 disk2

5. 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 &

6. Insert Sun Management Center 3.5 CD 1 of 2 in your CD-ROM drive.

7. List the contents of the Sun Management Center 3.5 installation CD 1. Then copy the contents to the disk1 subdirectory.

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

   For example:

   /SunManagementCenter# ls -p /cdrom cdrom0 sunmc_3_5_sparc/ /SunManagementCenter# cp -r /cdrom/sunmc_3_5_sparc/.* disk1 /sunmanagementcenter > ls -acp /cdrom/cdrom0sunmc_3_5_sparc . .CD Copyright image/ lib/ .. .CD01 classes/ install/ sbin/ /sunmanagementcenter > ls -acp disk1 . .CD Copyright image/ lib/ .. .CD01 classes/ install/ sbin/

   ---

   Caution –

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

   ---

8. Eject CD.1 of 2.

   SunManagementCenter# eject

9. Insert Sun Management Center 3.5 CD 2 of 2 in your CD-ROM drive.

10. List the contents of the Sun Management Center 3.5 installation CD 2. Then copy the contents to the disk2 subdirectory.

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

    For example:

    /SunManagementCenter# ls -p /cdrom cdrom0 sunmc_3_5_sparc_2/ /SunManagementCenter# cp -r /cdrom/sunmc_3_5_sparc_2/.* disk2 /sunmanagementcenter > ls -acp /cdrom/cdrom0sunmc_3_5_sparc_2 . .. .CD .CD01 .CD02 Copyright image/ /sunmanagementcenter > ls -acp disk2 . .. .CD .CD01 .CD02 Copyright image/

11. Eject CD 2 of 2.

12. Make the Sun Management Center 3.5 CD image directory NFS-shared.

    Using NFS to share the CD image directory enables you to install Sun Management Center 3.5 from other machines by using the CD installation images instead of manually installing from the CDs.

    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 cd-image-dir

       where cd-image-dir is the Sun Management Center 3.5 cd-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 3.5 cd-image directory is now accessible from other machines.

    You can now use the Sun Management Center CD images to install Sun Management Center 3.5, or to upgrade previous versions of Sun Management Center as described in the following chapters.

Creating CD 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 cd-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.

Before you download the tar file, ensure that you have at least 1.6 Gigabytes of free disk space for the tar file and for the CD image files that are created when you uncompress and unpack the tar file.

To Download the Tar File From the Web Site

1. In a terminal window, log in as root on the system where you want to create the Sun Management Center installation image.

2. Go to the Sun Management Center Web site at http://www.sun.com/sunmanagementcenter/.

3. Click Get the Software.

4. Click Sun Management Center 3.5.

   Follow the instructions and download the Sun Management Center 3.5 tar file to a location that is accessible by root.

5. Go to the location where the tar file has been downloaded:

   # cd /download-directory

6. Extract the Sun Management Center packages:

   # zcat downloaded-filename | tar xvf -

   The cd-image source directory is created, containing the subdirectories disk1 and disk2.

7. Make the Sun Management Center 3.5 cd-image directory NFS-shared.

   Using NFS to share the CD image directory enables you to install Sun Management Center 3.5 from other machines by using the CD installation images instead of manually installing from the CDs.

   For example, if you extracted the cd-images to the directory SunManagementCenter, you would make the directory NFS-shared as follows.

   1. Stop the Network File System daemon mountd:

      /SunManagementCenter# /etc/init.d/nfs.server stop

   2. Edit the /etc/dfs/dfstab file.

      Add the following line:

      share -F nfs -o ro cd-image-dir

      where cd-image-dir is the Sun Management Center 3.5 cd-image directory.

      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 3.5 cd-image directory is now accessible from other machines.

   You can now use the Sun Management Center CD images to install Sun Management Center 3.5, or to upgrade previous versions of Sun Management Center as described in the following chapters.