Quickstart: Installing and Setting Up Sun Management Center 3.6

Hardware and Software Requirements

This section provides the minimal Sun Management Center 3.6 hardware and software requirements. For detailed requirements and sizing information, see the Sun Management Center 3.6 Installation and Configuration Guide.

Supported Hardware

The following table lists the Sun systems supported by Sun Management Center 3.6.

For updated information on supported hardware, see the Sun Management Center 3.6 Installation and Configuration Guide.

Table 3 Sun Systems Supported by Sun Management Center 3.6


System Type	Model
Netra^TM	Netra 1280
	Netra T4/Netra 20
	Netra T 1120/1125
	Netra T 1400/1405
	Sun Fire V100
	Sun Fire V120/Netra 120
	Sun Fire V210
	Sun Fire V240
	Sun Fire V250
	Sun Fire V440
	Netra 240
	Netra 440
Sun Fire midrange and high-end	Sun Fire 6800/4810/4800/3800
	Sun Fire E6900/E4900
	Sun Fire E25K/E20K/15K/12K
	Sun Fire E2900
	Sun Fire V1280
Workgroup Server	Sun Fire 280R
	Sun Fire V480
	Sun Fire V490
	Sun Fire V880
	Sun Fire V890
Desktop	Sun Blade^TM 100
	Sun Blade 150
	Sun Blade 1000
	Sun Blade 1500
	Sun Blade 2000
	Sun Blade 2500

Sun Management Center Base Layer Requirements

The following table provides a summary of Sun Management Center 3.6 base layer requirements.

Note –

Some hardware platform config readers (add-ons) do not work on all layers of Sun Management Center when installed on Solaris 10.

For specific information about determining the total amount of resources needed, see “Determining Hardware Resources”.

Table 4 Sun Management Center 3.6 System Requirements


Base Layer	Operating System	Disk Space	RAM	Swap
Server (SPARC)	Solaris 8, Solaris 9, and Solaris 10 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 (SPARC)	Solaris 2.6, Solaris 7, Solaris 8, Solaris 9, and Solaris 10 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
Agent (x86)	Solaris 9 and Solaris 10	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
Agent (Linux) on x86	Red Hat Linux Enterprise 2.1 - 3.0 (32–bit and 64–bit), Sun Java^TM Desktop System 2.x, SUSE Linux Enterprise 8.0 (32–bit and 64–bit), SUSE Professional 9 (32–bit and 64–bit)	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, and Solaris 10 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 XP	Microsoft Windows platform: 35 Mbytes	Microsoft Windows platform: 256 Mbytes	Microsoft Windows platform: 768 Mbytes
	Linux 2.4.21 or higher	62 Mbytes	256 Mbytes	130 Mbytes

The default maximum heap size for the console and server is 64 Mbytes apiece.

Java console does not install jar files for add-ons.

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 installation requirements for other add-ons, see the documentation supplement for that add-on. See Sun Management Center Documentation Resources.

For specific information about determining the total amount of resources needed, see “Determining Hardware Resources”.

Table 5 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, Solaris 10 releases Windows 98, Windows NT, Windows 2000, Windows XP	Server: 3300 Kbytes Agent: 2020 Kbytes Console: 270 Kbytes
Service Availability Manager	Solaris 2.6, Solaris 7, Solaris 8, Solaris 9, Solaris 10 releases	Server: 1600 Kbytes Agent: 1000 Kbytes Console: 500 Kbytes
Solaris Container Manager	Solaris 8, Solaris 9, Solaris 10 releases	Server: 300 Mbytes Agent: 18 Mbytes Console: 500 Kbytes
System Reliability Manager	Solaris 2.6, Solaris 7, Solaris 8, Solaris 9, Solaris 10 releases	Server: 3000 Kbytes Agent: 1000 Kbytes Console: not applicable
Performance Reporting Manager	Solaris 2.6, Solaris 7, Solaris 8, Solaris 9, Solaris 10 releases Windows 98, Windows NT, Windows 2000, Windows XP	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.
X86Rack	RedHat, SuSE Linux kernel version 2.4.x or higher Note – This add-on can be installed only on hosts that has the N1^TM System Manager (N1SM) server installed.

Installing the Required JDK Version

Sun Management Center 3.6 requires JDK^TM 1.4.2 (minimum requirement), which is available on the <DiskMountDir>/disk1/jdk_dir directory, where jdk_dir is the name of the JDK directory on the disk.

Note –

The JDK available on the disk is only for Windows and Solaris. Download the appropriate JDK for Linux.

To Install the Required JDK Version

Steps

Install the JDK from the disk using the pkgadd command.

Type the command pkgadd -d <DiskMountDir>/disk1/jdk_dir.

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

Reset the JAVA_HOME environment variable to /usr/j2se.
- In a C shell environment, type:
  # setenv JAVA_HOME /usr/j2se
- In a Bourne or Korn shell environment, type:
  # JAVA_HOME=/usr/j2se # export JAVA_HOME
  Tip –
  Set the JAVA_HOME environment variable in your .login or .cshrc file.