Chapter 1 Installing Sun Management Center 4.0
This chapter describes how to install and set up SunTM Management Center 4.0. This chapter assumes that the product has not been installed before.
This chapter has the following topics:
Installing the Product
Sun Management Center has three main components, called base layers, that need to be installed: server, agent, and JavaTM Console (console). The server is a collection of processes on a central host that enables management services. The agent is a process that runs on each monitored host. The Java Console is the window through which you monitor and manage the agents. It is the main user interface to the product.
Before you can use Sun Management Center 4.0, you must install the following:
-
Server – On at least one machine.
Note –When the server is installed, the Sun Management Center agent is installed on the server machine as well.
-
Agent – On all machines you want to monitor.
-
Java Console – On any machine from which users will log into Sun Management Center.
In planning your installation you need to consider the following items:
-
On which machine do you want to run the Sun Management Center server?
-
Which machines do you want to monitor and manage? On these machines you need to install the Sun Management Center agent.
-
On which machines do you want to run the Sun Management Center console? On these machines you need to install the Java Console.
-
Which add-on products do you want to use? Sun Management Center has add-on products to extend its feature set and to make it work with specific software products or hardware platforms. For more information on the product and how it works in these different environments, see the documentation listed in Sun Management Center Documentation Resources.
In addition to installing the product components and the add-ons, you must set up the product components and add-ons before you can start the product.
Preinstallation Information
The following table lists the prerequisite information that you need before installing the product.
Table 1–1 Information Needed Before Installing|
Installation Item |
Description |
|---|---|
|
Base Layers (Components) |
Determine the machines on which you will install each component, for example, server, agent, and console. |
|
Languages |
Determine which, if any, additional languages (French, Traditional Chinese, Simplified Chinese, Korean, or Japanese) you need. The documentation for Sun Management Center 4.0 is not available on the media. Go to http://docs.sun.com for documentation in English and the supported languages. |
|
Add-on Products |
Review the add-on supplements to determine which add-ons you want to install. For a list of add-on supplements, see Sun Management Center Documentation Resources. Add-on products are installed on the same machine as the server. |
|
Space Needed |
If the machine does not have enough space in the default /opt directory, you might need to make one of the following adjustments:
|
|
You must have permission to write to the /var/opt and /opt/SUNWsymon directories as root on each machine. You also need privileges to run commands such as chmod. |
After installing the product and its add-ons, you will need to set up the product and its add-ons. The following table lists the prerequisite information that you need before setting up the product.
Table 1–2 Information Needed Before Setting Up|
Set Up Item |
Description |
|---|---|
|
A valid Solaris/Linux user name is required for assignment as the Sun Management Center administrator on Sun Management Center server machines. |
|
|
Sun Management Center uses two types of addressing for communication between the server and agent: IP addressing, and Network Address Translation (NAT). You must have the following information:
See Appendix D, Network Address Translation for further information. |
|
|
Sun Management Center requires an encrypted security key for communication between processes. The security key is generated based on a unique password you provide. Store the password securely. You need the password if you modify your Sun Management Center installation. |
|
|
Sun Management Center requires an SNMPv1 community string for security. The default is public. You have the option of specifying a more secure custom string. Store the SNMPv1 string securely. You need the SNMPv1 security string if you modify your Sun Management Center installation. |
|
|
The Sun Management Center Web server requires an encrypted security key. The security key is generated based your organization name and location. Store the organization name and location securely. You need this information if you modify your Sun Management Center Web server. |
|
|
Ports |
Determine the assignments for the following ports:
See Default Ports for further information. |
Sun Management Center Requirements
The following table provides a summary of Sun Management Center 4.0 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 Appendix C, Determining Hardware Resources.
Table 1–3 Sun Management Center 4.0 System Requirements
The default maximum heap size for the console and server is 64 Mbytes each.
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.
Installing the Required JDK Version
The minimum JDKTM requirement for Sun Management Center 4.0 is JDK 1.5. The JDK software is available in the DiskMountDir/disk1/jdk-dir/TargetOS directory, where jdk-dir is the name of the JDK directory on the disk and TargetOS is the Linux, Solaris, or Windows operating system.
To Install the Required JDK Version
-
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.
-
Sun Management Center Base Add-on Requirements
The following table shows the minimum disk space necessary to install the basic 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 Appendix C, Determining Hardware Resources.
Table 1–4 Add-on Disk Space Requirements by Base Component
Installing Sun Management Center
Note –
On Solaris 10, you can install Sun Management Center inside a whole root zone. For information about this, see (On Solaris 10) Installing and Setting Up a Sun Management Center Server Inside a Whole Root Zone. On Linux, you can install only agent and console layers.
This section describes how to install Sun Management Center 4.0 on Solaris and Linux platforms using the graphical user interface (GUI).
This installation procedure assumes that you are installing Sun Management Center from a media image directory on your network.
For information on creating an installation DVD image, see Creating Installation DVD Images.
To Install Sun Management Center
Before You Begin
(On Solaris 10 and above) Ensure that the packages SUNWtcatu and SUNWtcatr are installed in the global zone before running the Sun Management Center server layer.
-
Set up the installation environment.
-
If you are installing the product remotely, grant access to the X server by typing the command xhost + machine in a terminal window where machine is the name of the machine where you want to install the product.
-
Log into the machine. If you are installing the product remotely, type the command rlogin machine and type the password.
-
Log in as root by typing su - root and the root password.
Note –Do not miss the hyphen (-) after the su command
-
If you prefer a specific UNIX shell, type the command to use the shell, for example, csh.
-
If you are installing the product remotely, ensure that the DISPLAY environment variable is set to the machine's display, for example, setenv DISPLAY local-machine:0.0.
-
Ensure that the group entry in the /etc/nsswitch.conf has files as the first token.
group: files nis
-
Change to the image directory. Ensure that the image directory is NFS-shared.
For example:
# cd /net/machine/image/disk1/sbin
where machine is the machine where you created the installation image, and image is the root directory containing the installation images.
-
-
Run the installation.
-
Follow the screen prompts.
-
To accept the default /opt installation directory, click Next, or click Browse to choose another directory.
-
Select the components you want to install.
-
Review the Server Layer Binary Code License and use the scroll bar to scroll down to the end of the text.
-
To agree to the terms of the license, click I Agree.
-
If you want to install the product in additional languages, select the additional languages and click Next. The progress bar appears.
Figure 1–2 Checking for Available Products Progress Bar
-
Select the add-on products.
The Select Add-on Products screen appears. Your list of add-on products might vary from this screen.
Figure 1–3 Add-on Products
-
If you selected add-on products that have optional components, select the optional components required and click Next.
-
Review the add-on products binary license and use the scroll bar to scroll down to the end of the text.
Some add-ons require binary license.
-
To agree to the terms of the license, click I Agree.
The Checking Disk Space progress bar appears. If there is not enough disk space, you are asked to provide an alternate file system.
Tip –In a terminal window on the machine where you are installing Sun Management Center, type df -ak to list the amount of used and free space for each file system on the machine.
-
Confirm installation selections and click Next.
Note –The installation process can take from a few minutes to half an hour or more, depending on the products selected.
If installation failed, a summary screen is displayed.
Review the installation log in /var/opt/SUNWsymon/install to find out why the installation failed, and correct the problem.
-
-
Choose whether to run the setup wizard.
Caution – If you have used es-guiinst to install only add-on products, click Close to exit the installation and setup process. You must set up the add-on products as described by To Set Up an Add-on Product Using es-setup. Otherwise, you will overwrite your security keys and will then have to set up all of the agents on all of your machines for the agents to work properly.
Setting Up Sun Management Center
You use the graphical setup wizard to set up, configure, and re-configure your Sun Management Center installation.
For information on using the command-line setup script, see To Set Up Sun Management Center Using the es-setup Script.
To Set Up Sun Management Center
-
Set up the installation environment. For more information, see Step 1 in To Install Sun Management Center.
-
Change to the Sun Management Center sbin directory. For example:
# cd /opt/SUNWsymon/sbin
If you installed Sun Management Center in a directory other than /opt, Change to /installdir/SUNWsymon/sbin, where installdir is the directory you specified.
-
Run the set up by typing:
# ./es-guisetup
The Set Up screen appears.
-
Follow the screen prompts.
-
You are given the opportunity to store all of your setup responses in the file /var/opt/SUNWsymon/install/setup-responses-file. The setup-responses-file file is useful if you need to duplicate the setup on the current machine on other machines.
-
To continue setup without creating the response file, click Next.
-
To create the response file, select Store Response Data and then click Next.
-
-
Generate the Sun Management Center security key.
Type a password in both fields and click Next to generate the security keys.
An encrypted security key is needed for communications between all Sun Management Center processes. The key is generated based on the password you provide, which must be between one and eight characters long and contain no spaces. Entries that are greater than eight characters are truncated to eight characters.
Note –Keep a record of the password you use to generate the security key for this machine in a secure location. You might need to regenerate the key for the machine at a later time. You can also change the security key later, if needed, as described in Regenerating Security Keys.
-
Specify the SNMPv1 community security string.
The community string is used for SNMP security and is set to public by default.
Set the community string to a value other than public or private to provide better SNMP security.
Caution – The same SNMP community string must be used on all of the machines on which you install Sun Management Center. If you use different community strings on each machine, SNMP communications between the machines and Sun Management Center components will not work.
-
If you want to accept the community string default value of public, click Next.
-
If you want to use a custom community string:
-
Select Use Custom Community String.
The community string can be up to 255 characters and must not contain any spaces or blanks.
-
Type the same community string in both fields, and then click Next.
-
-
-
Enter a valid Solaris/Linux user name as the UNIX administrator account and click Next.
The setup process checks whether the SNMP port is in use.
-
If the SNMP port is in use, the SNMP Port Conflict screen appears.
Figure 1–4 SNMP Port Conflict Screen
-
Resolve the port conflict.
In most cases, port 161 is the default port assigned to and used by the SNMP daemon. However, other processes or daemons could be using port 161. Several third-party replacements and enhancements for the SNMP daemon exist and could be installed on your system. The Sun Management Center agent is such a daemon.
We recommend that you use a different port number, such as port 1161.
-
To assign a different port number to Sun Management Center:
-
Click Use a Different Port Number.
For instructions on how to find out whether a port is used, see To Determine Whether a Port Is Used.
-
Type the port number, for example, 1161, in the Port ID field and click Next.
Note –Keep a record of this alternate port number. You will need this number if you later install agents using JumpStart or update the Sun Management Center agents using the agent update-image tools.
-
-
To use port 161, select Use Port 161 and click Next.
-
-
If you use port 161, you are reminded to manually stop and disable the SNMP daemon snmpdx.
Note –(On Solaris 10) If you use port 161, you will be reminded to stop and disable the SNMP daemon SMA manually.
There is no SNMP daemon on Linux by default.
-
To stop and disable the SNMP daemon snmpdx automatically, make sure that Stop and Disable SNMP Daemon snmpdx has been selected, and then click Next.
Caution – Stopping and disabling the system SNMP daemon does not guarantee that you have stopped the actual process using port 161. To determine the actual daemon process that uses port 161, you must manually review all /etc/rcN and /etc/rcN.d files, where N is 0 through 6 and S. When you have identified the file that defines the process using port 161, you can disable the process by renaming the file. For example,
/etc/rc3.d# mv S76snmpdx s76snmpdx
You must stop all other processes that use port 161 before you can start Sun Management Center.
-
To stop and disable the SNMP daemon SMA, navigate to the /etc/init.d directory. Type ./init.sma stop.
-
-
If any Sun Management Center ports are in use, you are prompted to resolve the port conflict.
The ports are checked in the following order: trap service, event service, topology service, configuration service, platform agent, cst service, metadata service, database, look-up service, Web server default port, and Web server secure port.
If any of the ports are in use, you are prompted to provide an unused port number. Type an unused port number in the field, and then click Next.
-
Generate the Web server security key.
Figure 1–5 Web Server Security Key Generation
An encrypted security key is needed for the Sun Management Center Web server. The key is generated based on the name of your organization and the name of your location. The names that you provide must not contain any spaces or blanks.
Type the name of your organization and the name of your location to generate the Web server security key and click Next.
For example, you could type admin in the Name of Your Organization field and headquarters in the Name of Your Location field.
Note –Keep a record of the entries you use to generate the security key in a secure location in case you need to regenerate the key for a particular machine at a later time.
-
Confirm setup selections.
The setup process can take from a few minutes to half an hour or more, depending on the products selected.
If base product setup failed, you are informed that the setup of the base products was not successful. You are directed to see the log file for more details. The name of the log file is provided.
-
If you installed add-ons, click Next to set them up.
Some add-on products are included with the Sun Management Center 4.0 installation media. These add-ons are the ones listed in the Select Add-on Products panel. For information on how to set up each add-on, refer to the Sun Management Center supplement for each add-on. Each supplement provides the setup procedure for the specific add-on.
-
Start the product by selecting the components to start and clicking Next.
Figure 1–6 Start Up the Product
For more information on starting and stopping Sun Management Center, see Chapter 8, Starting and Stopping Sun Management Center.
Caution – If your network uses Network Address Translation (NAT), click Close. Use the es-config command-line utility described in To Enable NAT Support to configure the machine for NAT before you start Sun Management Center.
-
-
Start the console by typing this from a terminal window: ./es-start —c&.
The Java Console login screen appears.
Figure 1–7 Console Start Up
Tip –If help does not come up in Java Console, modify the browser path in the javaconsole.properties file. This file is available in /var/opt/SUNWsymon/cfg/ if you have installed the console layer. Otherwise, this file will be available in /opt/SUNWsymon/cfg/.
You are prompted to select the default domain and then a screen similar to this appears.
Figure 1–8 Sun Management Center Default Domain
Note –(On Solaris 10) When Sun Management Center is installed and set up, the services run as Service Management Facility (SMF) services. Based on the layers chosen, appropriate services will be started.
For information on using the product, see Sun Management Center 3.6.1 User's Guide.
(On Solaris 10) Installing and Setting Up a Sun Management Center Server Inside a Whole Root Zone
Zone is a virtualized operating system environment that you can set up for systems that run the Solaris 10 Operating System. Every Solaris system contains a global zone, the default zone for the system. You can create non-global zones. Non-global zone can either be a whole root zone or a sparse root zone.
Before You Begin
The following must be available:
-
A whole root zone must be available.
-
Host name and IP address must be available for the whole root zone.
-
Lockhart 2.2.3 or above must be available in the global zone.
-
Apache Tomcat must be available in the global zone.
|
Task |
Instructions |
|---|---|
|
Install Sun Cluster 3.1 Update 4 on each cluster node This task is required only if the user wants to configure Sun Management Center in a Sun Cluster environment. |
Chapter 2, Installing and Configuring Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS. |
|
Install and configure Sun Cluster HA agent for Solaris Container data service This task is required only if the user wants to configure Sun Management Center in a Sun Cluster environment. |
Chapter 1, Installing and Configuring Sun Cluster HA for Solaris Containers, in Sun Cluster Data Service for Solaris Containers Guide |
|
Enable a zone to run in a failover configuration | |
|
Configure and install a whole root zone |
To Configure a Whole Root Zone and To Install a Whole Root Zone |
|
Install and set up Sun Management Center inside a whole root zone |
To Install and Set Up Sun Management Center Server Inside a Whole Root Zone |
To Enable a Zone to Run in a Failover Configuration
-
Register the SUNW.HAStoragePlus resource type.
# scrgadm -a -t SUNW.HAStoragePlus
-
Create a failover resource group.
# scrgadm -a -g solaris-zone-resource-group
-
Create a resource for the zone disk storage.
# scrgadm -a -j solaris-zone-has-resource \
-g wholerootzone-resource-group \
-t SUNW.HAStoragePlus \
-x FilesystemMountPoints=/global/zones/HA
-
Add an entry for logical host in the /etc/hosts file on each cluster node.
# scrgadm -a -L -g sunmc-zone-resource-group -j sunmc-lh-rs -l logical host name
-
Enable the failover resource group.
# scswitch -e -j solaris-zone-has-resource
# scswitch -Z -g wholerootzone-resource-group
To Configure a Whole Root Zone
-
Start the zone configuration.
#zonecfg -z wholerootzone, where wholerootzone is the name of the new whole root zone.
-
Create a configuration for the specified zone.
zonecfg:wholerootzone> create -b
-
Set the zone path.
The zone path must specify a highly available local file system. The file system must be managed by the SUNW.HAStoragePlus resource.
zonecfg:wholerootzone> set zonepath=/global/zones/HA/wholerootzone
-
Set the autoboot value.
If the autoboot value is set to true, the zone is automatically booted when the global zone is booted. The default value is false.
zonecfg:wholerootzone> set autoboot=false
-
If resource pools are enabled on the system, associate a pool with the zone.
zonecfg:wholerootzone> set pool=pool_default, where pool_default is the name of the resource pool on the system.
-
Add a network virtual interface.
zonecfg:wholerootzone> add net
-
Set the IP address for the network interface.
zonecfg:wholerootzone> set address=10.255.255.255
-
Set the physical device type for the network interface.
zonecfg:wholerootzone> set physical=hme0
zonecfg:wholerootzone> end
-
Verify and commit the zone configuration.
zonecfg:wholerootzone> verify
zonecfg:wholerootzone> commit
zonecfg:wholerootzone> exit
To Install a Whole Root Zone
-
Install the whole root zone that is configured.
# zoneadm -z wholerootzone install, where wholerootzone is the name of the whole root zone that is configured.
-
Boot the whole root zone.
# zoneadm -z wholerootzone boot
-
Log in to the zone console.
# zlogin -C wholerootzone
-
Log in to the zone.
# zlogin wholerootzone
-
(required for Sun Cluster environment) Add the entry of the whole root zone to the /etc/zones/index file on the cluster node.
-
(required for Sun Cluster environment) Copy the wholerootzone.xml file to the /etc/zones/index directory on the cluster node.
# rcp zone-install-node:/etc/zones/wholerootzone.xml
-
Verify the zone installation and configuration.
# zoneadm -z wholerootzone boot
# zlogin -z wholerootzone
To Install and Set Up Sun Management Center Server
Inside a Whole Root Zone
-
Ensure that you are inside the whole root zone that is configured and installed.
-
Follow the steps in the install wizard to install Sun Management Center.
-
Edit the /etc/project file for shared memory before setup. Otherwise, database setup will fail. For example,
default:3::::project.max-shm-memory=(privileged,2147483648,deny)
2147483648 is the sample shared memory in bytes. The shared memory depends on the amount of physical memory.
-
Follow the steps in the setup wizard to set up Sun Management Center.
Sun Management Center supports the server layer of all add-ons inside a non-global zone. Sun Management Center does not support the agent layer of add-ons like ELP Config Reader, X86 Config Reader, and Solaris Container Manager inside a non-global zone.
Sun Management Center Documentation Resources
Sun Management Center has many add-on products. Documentation for Sun Management Center is not installed with the product. The documents are available at http://docs.sun.com.
Table 1–6 Documentation Resources|
Environment |
Documentation |
|---|---|
|
If you install and use the product in a production environment, see |
Sun Management Center 3.6.1 User's Guide- Describes how to use the product. |
|
Sun Management Center 4.0 Installation and Configuration Guide- Describes how to install and configure the product. |
|
|
If you use the product with other software products or add-ons (listed alphabetically), see | |
|
Advanced System Monitoring |
Not Applicable |
|
Hardware Diagnostic Suite 2.0 |
Hardware Diagnostic Suite 2.0 User's Guide |
|
Solaris Container Manager 4.0 |
Installing and Administering Solaris Container Manager 4.0 |
|
Performance Reporting Manager |
Sun Management Center 3.6.1 Performance Reporting Manager User's Guide |
|
Service Availability Manager |
Sun Management Center 3.6.1 Service Availability Manager User’s Guide |
|
Sun Cluster |
Task Map: Installing the Sun Cluster Module for Sun Management Center in the Sun Cluster Software Installation Guide for Solaris OS |
|
System Reliability Manager |
Sun Management Center 3.6.1 System Reliability Manager User’s Guide |
|
Unicenter TNG |
Sun Management Center CA Integration Package User's Guide for Unicenter TNG |
|
If you use the product with these hardware platforms (listed alphabetically), see | |
|
ELP Config Reader (CommonConfigReader) |
See Sun FireTM V210/V240/V250/V440/1500/2500 |
|
Desktop |
See Sun BladeTM 100/150/1000/1500/2000/2500 |
|
Dynamic Reconfiguration for Sun Fire high-end and midrange |
See Sun Fire V880/V890/15K to 3800 |
|
hPCI+ board and CP2140 system controller for Sun Fire high-end systems |
See Sun Fire high-end systems |
|
NetraTM 20/120/1280 |
Sun Management Center 3.5 Supplement for Netra Servers |
|
Netra 240/440 |
Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade and Netra Systems |
|
Netra T4/20 |
Sun Management Center 3.5 Supplement for Netra Servers |
|
PCI+ support for Sun Fire midrange systems |
See Sun Fire midrange systems |
|
Sun Blade 100/150/1000/2000 |
Sun Management Center 3.5 Supplement for Workstations |
|
Sun Blade 1500/2500 |
Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade and Netra Systems |
|
Sun CobaltTM LX50 |
See the software product, Sun Management Center Linux Agent |
|
Sun Fire V60x/V65x/V20z/V40z |
See the software product, Sun Management Center Linux Agent |
|
Sun Fire 280R/V480/V490/V880/V890 |
Sun Management Center 3.5 Supplement for VSP High-End Entry Servers (Workgroup Servers) |
|
Sun Fire high-end E25K/E20K/15K/12K |
Sun Management Center 3.5 Version 6 Release Notes and Supplement for Sun Fire High-End Systems |
|
Sun Fire midrange E6900/E4900/6800/4810/4800/3800 |
Sun Management Center 3.5 Version 6 Release Notes and Supplement for Sun Fire Midrange Systems |
|
Sun Fire entry-level midrange E2900 |
Sun Management Center 3.5 Version 6 Release Notes for Sun Fire Entry-Level Midrange Systems Sun Management Center 3.5 Version 6 Supplement for Sun Fire Entry-Level Midrange Systems |
|
Sun Fire V100/V120 |
Sun Management Center 3.5 Supplement for Netra Servers |
|
Sun Fire V210/V240/V250/V440 |
Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade and Netra Systems |
|
Sun LX50 |
See the software product, Sun Management Center Linux Agent |
|
UltraSPARC® IV CPU board support for Netra 1280 |
Requires midrange systems firmware 5.17.0 and Netra-T add-on packages for Sun Management Center |
|
UltraSPARC IV CPU board support for Sun Fire 6800/4800 |
See Sun Fire 6800/4800 |
- © 2010, Oracle Corporation and/or its affiliates