test

Sun Management Center 3.5 Installation and Configuration Guide

Chapter 2 Sun Management Center 3.5 Requirements

The information in this chapter will help you determine what operating system, storage and computational resources must be allocated or acquired to implement a specific Sun Management Center software solution.

This chapter discusses the following topics:

Note –

If you plan to install the Sun Management Center 3.5 development environment, you should install the developer environment on a separate, dedicated machine. The Sun Management Center server, agent, and console layers are automatically installed on a developer environment machine. A machine used for Sun Management Center development must meet the minimum hardware and software requirements for the Sun Management Center server layer. The developer environment machine must also meet the requirements for the agent layer, console layer, and any add-ons you install.

Compatibility With Prior Versions

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

Sun Management Center software does not offer the following features:

The following table lists prior Sun Management Center version compatibility by Sun Management Center base product layer. Sun Management Center versions 2.0 and 2.0.1 are referred to as Sun Enterprise SyMONTM software. Versions 2.1, 2.1.1, 3.0, and 3.5 are referred to as Sun Management Center.

Table 2–1 Sun Management Center Prior Version Compatibility by Base Product

Console 

Server 

Agent 

3.0 

3.0 

2.0.1, 2.1, 2.1.1, 3.0 

3.5 

3.5 

2.0.1, 2.1, 2.1.1, 3.0, 3.5 

Supported Platforms

For the latest information on supported hardware platforms, refer to the Sun Management Center Web site at http://www.sun.com/sunmanagementcenter. The Config-Reader module is required for hardware configuration information.

The following table provides examples of supported platforms.

Table 2–2 Examples of Supported Platforms

Operating System 

Sun Management Center Layers 

Example Hardware 

Solaris 

Agent, console, add-ons 

Note –

Some add-ons are platform-specific.

  • SPARCStation 1, 2, 5, 10, 20

  • Ultra 1, 2, 5, 10, 30, 60, 80, 450

  • 100, 1000

  • T1 100, T1 105, T1 AC200, X1, T1 1120, T1 1125, T1 1400, T1 1405

  • Sun Enterprise 2, 150, 220R, 250, 420R, 450, 3000, 3500, E3500, 4000, 4500, E4500, 5000, 5500, E5500, 6000, 6500, E6500, 10000

  • Sun Ultra Enterprise 2, 5, 10, 150, 220R, 250, 420R, 450, 3000, 3500, E3500, 4000, 4500, 5000, 5500

  • Sun Fire 280R, V880, 3800, 4800, 4810, 6800, 15000

  • SPARCcenter® 2000, 2000E, 1000, 1000E

Solaris 

Agent, console, server, add-ons 

Note –

Some add-ons are platform-specific.

  • Small server: Up to 350 nodes under management.

    Netra X1, Netra T1, or Sun Blade 100 with a single 500 MHz UltraSPARC® IIe CPU or better

  • Medium server: Up to 600 nodes under management.

    Sun Enterprise 420R or Ultra 60 with two 450 MHz UltraSPARC II CPUs or better

  • Large server: Up to 750 nodes under management.

    Sun Fire 280R, Netra T4, or Sun Blade 1000 with two 750 MHz UltraSPARC III CPUs or better

  • Extra-large server: Up to 1,000 nodes under management.

    Sun Fire 480R or equivalent with 4 900 Mhz UltraSPARC III CPUs or better.

Windows 98, Windows NT, and Windows 2000 

Console layer and some add-ons 

Pentium 233 MHz or better 

The Config-Reader and the Dynamic Reconfiguration modules are not supported on all Sun hardware platforms. However, all other base Sun Management Center modules are supported on Sun hardware platforms.

For more information on base modules, refer to the Sun Management Center 3.5 User's Guide.

Sun Management Center Base Layer Requirements

The following table provides a summary of Sun Management Center 3.5 base layer requirements. For specific information about determining the total amount of resources needed, see Appendix C, Determining Hardware Resources.

Table 2–3 Sun Management Center 3.5 Base Layer System Requirements

Base Layer 

Operating System 

Disk Space 

RAM 

Swap 

Server 

Solaris 8, Solaris 9 Solaris Developer Software Group installation 

800 Mbytes total: 300 Mbytes in /opt, 500 Mbytes in /var/opt

512 Mbytes minimum 

1 Gbyte recommended for small to large servers 

2 Gbytes recommended for extra-large servers. 

1 Gbyte recommended 

Agent 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases 

18 Mbytes per agent in /opt/SUNWsymon. 2 Mbytes per agent in /var/opt/SUNWsymon.

10 to 29 Mbytes per agent depending on modules loaded and system type 

 

Java Console 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases

Solaris platform: 62 Mbytes

Solaris platform: 256 Mbytes

Solaris platform: 130 Mbytes

 

Microsoft Windows 98, Microsoft Windows NT SP 4 or later, Microsoft Windows 2000 Professional

Microsoft Windows platform: 35 Mbytes

Microsoft Windows platform: 256 Mbytes

Microsoft Windows platform: 768 Mbytes

The default maximum heap size for the console and server is 64 Mbytes apiece. You can customize the maximum heap size for the console and server as described in Starting Components Using es-start.

Sun Management Center Base Add-on Requirements

The following table shows the minimum disk space necessary for each Sun Management Center layer to install the base add-ons. For specific information about determining the total amount of resources needed, see Appendix C, Determining Hardware Resources.

Table 2–4 Base Add-on Disk Space Requirements by Base Component

Base Add-on 

Operating System 

Disk Space 

Advanced System Monitoring 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases 

Windows 98, Windows NT, Windows 2000 

Server: 3300 Kbytes 

Agent: 2020 Kbytes 

Console: 270 Kbytes 

Service Availability Manager 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases 

Server: 1600 Kbytes 

Agent: 1000 Kbytes 

Console: 500 Kbytes 

System Reliability Manager 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases 

Server: 3000 Kbytes 

Agent: 1000 Kbytes 

Console: 0 Kbytes 

Performance Reporting Manager 

Solaris 2.6, Solaris 7, Solaris 8, Solaris 9 releases 

Windows 98, Windows NT, Windows 2000 

Server: depends on reporting options selected. 

  • Small configuration: 5 Gbytes

  • Medium configuration: 12 Gbytes

  • Large configuration: 24 Gbytes

Agent: 8000 Kbytes minimum. For 1000 properties logged at five minute intervals, 80 Mbytes are needed. 

Console: 3 Mbytes 

 
Note –

The Performance Reporting Manager requires 1 Gbyte of RAM and 1 Gbyte of swap space.

JDK Version Requirements

JDK requirements for Sun Management Center 3.5 are listed in the following table.

Table 2–5 JDK Requirements

Component 

JDK Version 

Command-line install and setup 

Not required 

Agent graphical user interface install and setup 

JDK 1.2.2 

Console graphical user interface install and setup 

JDK 1.3.1 

Server graphical user interface install and setup 

JDK 1.4 

Run the Sun Management Center agent 

Not required. 

Run the Sun Management Center console 

JDK 1.3.1 

Run the Sun Management Center server 

JDK 1.4 

To Determine the Installed Java Version

  1. Type the command which java to determine where Java is installed.

    The path to the Java executable is displayed, for example:


    > which java
/bin/java
    Note –

    The path shown might be a symbolic link.

  2. Type the command java -version.

    The Java version is displayed.


    >java -version
Java(TM) 2 Runtime Environment, Standard Edition (build 1.2.0_01-b03)
Java HotSpot(TM) Client VM (build 1.2.0_01-b03, mixed mode)

    In the above examples, the version of Java installed in /bin/java is not sufficient for installing Sun Management Center 3.5 using the graphical user interface. The Java version is also not sufficient for running the Sun Management Center console and server.

    To use the graphical user interface to install, setup, and run the Sun Management Center console and server, you must install the required version of the Java software, which is included on the Sun Management Center 3.5 installation CD 1 of 2.

To Install the Required JDK Version

  1. Log in as root (su - root).

  2. Remove the path to the current version of the Java software.

    Assume that /bin/java is where the current version of the Java software is installed, and that /bin/java is a symbolic link to /usr/j2se.

    Edit your .login or .cshrc file, and remove /bin/java from the PATH statement.

  3. Rename the current Java directory.

    Assume the current Java version is 1.2. You could rename the current Java directory to Java version 1.2 using the command mv j2se java1.2. For example:


    # cd /usr
# mv j2se java1.2
# ls java1.2
COPYRIGHT     README.html   jre/          opt/
LICENSE       bin/          lib/          src.zip
README        include/      man/
    Note –

    If needed, you can still use the current version of the Java software for other projects by resetting the JAVA_HOME environment variable.

  4. Delete the symbolic link.

    For example, if /bin/java is a symbolic link to /usr/j2se, you would type the command rm /bin/java.

  5. Install the JDK from Sun Management Center 3.5 installation CD 1 of 2.

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

      List the contents of the CD.


      # ls -p /cdrom/cdrom0
Copyright                 classes/                  lib/
JDK1.4.1_02/              image/                    sbin/
ThirdPartyLicenseReadMe   install/

      The JDK directory on your Sun Management Center 3.5 machine might show a different version.

    2. Go to the JDK directory on the CD.

      List the contents of the JDK directory.


      # cd /cdrom/cdrom0/JDK*
/cdrom/cdrom0 # ls -p
Solaris/  Windows/

    3. Install the JDK packages using pkgadd.

      Type the command pkgadd -d /cdrom/cdrom0/jdk_dir/Solaris, where jdk_dir is the name of the JDK directory on the CD.

      A list of packages is displayed, and you are prompted to select the packages you want to install.

      Press Return to install all of the packages. The JDK packages are installed in the /usr/j2se directory.

  6. Reset the JAVA_HOME environment variable 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 –

      Set the JAVA_HOME environment variable in your .login or .cshrc file.

Determining Free Disk Space

This section describes how to determine the amount of free disk space on Solaris platforms and Microsoft Windows platforms.

To Determine Free Space on a Solaris System

  1. Open a terminal window.

  2. Type df -ak to list the used and free space for each file system on the machine.

To Determine Free Space on a Microsoft Windows System

  1. Choose Start -> Programs -> Windows Explorer.

    The Explorer window appears.

  2. Click the plus sign (+) to the left of My Computer.

    The list expands to show the hard drives on the system.

  3. Press mouse button 3 on the drive name.

    A pop-up menu appears.

  4. Choose Properties from the pop-up menu.

    The Disk Properties window appears, listing the amount of used space and free space.

  5. Click OK to close the Disk Properties window.