Sun Management Center 4.0 Installation and Configuration Guide

To Generate the Sun Management Center 4.0 Install and Setup Response Files

Select a machine on which to install and set up the Sun Management Center base agent, and log in as root.

This is the prototype machine.

Tip –
Select a machine on which Sun Management Center has not been installed. If such a machine is not available, uninstall the Sun Management Center software from the prototype machine as directed by the installation manual for the Sun Management Center software. Do not save the configuration data from the previous version of Sun Management Center.

Insert the Sun Management Center 4.0 DVD in your DVD drive.

Change to the directory /DiskMountDir/sbin.

Create a directory on the machine in which to store the Sun Management Center install and setup response files.

For example:
# mkdir /response-files

Generate the Sun Management Center Install Response file.

To generate the install response file, you must install the base agent using the command format ./es-inst -C /response-file-dir/install-response-file.cfg where:

response-file-dir is the directory that you created in which to store the response files
install-response-file is the name of the response file

For example:

# ./es-inst -C /response-files/install.cfg

You are prompted for the directory in which to install Sun Management Center.

Provide the name of the directory in which to install Sun Management Center

You are prompted for the target directory. The default location is /opt.

Sun Management Center software can be installed in any location on your system where the minimum required disk space is available. If you want to install to a directory other than /opt, type the directory name.

Tip –
The command df -ak lists the used space and free space for each file system on the machine.

You are prompted to select the Sun Management Center components that you want to install.

Select only the agent component.

Type n when prompted to install the server component.

Type y when prompted to install the agent component.

Type n when prompted to install the console component.

3 component(s) are available for your selection:
  Do you want to install the Server component (y|n|q) n
  Do you want to install the Agent component (y|n|q) y
  Do you want to install the Console component (y|n|q) n

The install process checks for add-on components, and then prompts you to select add-ons.

Do not select any add-on components for installation.

Type n when prompted to select each add-on.

Select the products you want to install:
    Advanced System Monitoring (y|n|q) n
    Service Availability Manager (y|n|q) n
    Performance Reporting Manager (y|n|q) n
    Sun Fire Platform Administration (y|n|q) n
    System Reliability Manager (y|n|q) n
    Workgroup Server (y|n|q) n

You are asked whether you want to proceed. Type y to continue.

Check disk space.

The installation process checks whether there is enough disk space to install the Sun Management Center base agent.
- If there is enough disk space, the base agent is installed.
- If there is not enough disk space, you are asked to provide an alternate file system. The amount of space that is available and the amount of space that is needed are displayed.
  
  Tip –
  In a terminal window on the machine where you are installing the Sun Management Center agent, type df -ak to list the amount of used and free space for each file system on the machine.
When the agent installation completes, you are asked whether you want to run setup.

Caution –
Do not run setup. Type n to exit. Running setup from within the install process will not create the Sun Management Center setup response file needed by the JumpStart finish script.

Go to the directory /opt/SUNWsymon/sbin.

If you installed Sun Management Center in a different location, go to the /install-dir/SUNWsymon/sbin directory, where install-dir is the directory you specified in Step 4.

Generate the Sun Management Center 4.0 setup response file.

To generate the Sun Management Center setup response file, you must set up the base agent using the command format ./es-setup -C /response-file-dir/setup-response-file.cfg where:
- response-file-dir is the directory that you created in which to store the response files
- setup-response-file is the name of the response file
For example:
# ./es-setup -C /response-files/setup.cfg
You are prompted to provide a seed for security key generation,
1. 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 seed that you provide. The seed must be between one and eight characters long, and contain no spaces. Entries that are greater than eight characters are truncated to eight characters.
  
  Caution –
  You must ensure that you use the same security seed for all the machines that you install in a single server context.
  
  Type the same password seed that you provided during Sun Management Center server setup in Step b in Setting Up Sun Management Center.
  
  Type the password seed again when prompted.
  
  Note –
  To ensure security, the password seed that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the password seed in the JumpStart finish script, or configure the finish script so that the install client prompts for the password seed when the finish script runs on the install client. Both methods of specifying the password seed are provided in To Create the JumpStart Finish Script.
  
  You are prompted for the SNMPv1 community string.
2. Specify the SNMPv1 community security string.
  
  An SNMPv1 community string is required for security, and by default is set to public. For additional security, a customized string can be specified.
  
  Caution –
  You must ensure that you use the same SNMPv1 community string on all the machines that you install in a single server context.
  
  Provide the same community string that you provided during Sun Management Center server setup in Step c in Setting Up Sun Management Center.
  - If you used the default community string of public, press Return when prompted to submit the SNMPv1 community string.
  - If you specified a custom community text string, type the same community string that you provided during Sun Management Center server setup.
  Note –
  To ensure security, the community string that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the community string in the JumpStart finish script, or configure the finish script so that the install client prompts for the community string when the finish script runs on the install client. Both methods of specifying the community string are provided in To Create the JumpStart Finish Script.
  
  You are prompted for the Sun Management Center server host name.
3. Specify the Sun Management Center server host name.
  
  Type the name of the machine on which the Sun Management Center server was installed.
  
  The setup process checks whether the SNMP port is in use.
  - If SNMP port 161 is not in use, you are asked whether you want to start the Sun Management Center agent. Go to Step e.
  - If SNMP port 161 is in use, you are prompted to assign an SNMP port number.
4. Resolve the SNMP port conflict.
  
  Type the same port number that you provided during Sun Management Center server setup in Step f in Setting Up Sun Management Center.
5. Start the Sun Management Center agent.
  
  Caution –
  If your network uses Network Address Translation (NAT), type n to exit setup without starting Sun Management Center. 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.
  - If you want to start the Sun Management Center base agent now, type y.
    
    The setup script starts the agent using es-start -A. See Starting Components Using es-start for information about es-start.
    
    Also, see Starting the Console for instructions on how to start the Sun Management Center console.
  - If you want to start Sun Management Center later, type n. See Chapter 8, Starting and Stopping Sun Management Center when you are ready to start the Sun Management Center agent on this machine.

Copy the install and setup response files to the JumpStart profile server.

As an example in the previous steps, the Sun Management Center install response file install.cfg was created on the prototype machine in the directory /response-files. The Sun Management Center setup response file setup.cfg was also created on the prototype machine in the directory /response-files.

Assume that your JumpStart profile server is named bootserver01, and the JumpStart profile directory on machine bootserver01 is /export/home/JumpStart/jumpstart. Also assume that you have enabled write-access to the JumpStart profile directory from the prototype machine. You would then copy the response files from the prototype machine to the JumpStart profiles directory on the JumpStart machine. For example:
# cd /response-files # cp install.cfg /net/bootserver01/export/home/JumpStart/jumpstart # cp setup.cfg /net/bootserver01/export/home/JumpStart/jumpstart

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Edit the Sun Management Center install response file.

You must edit the install response file so that it can be used by JumpStart. The install response file is the file name you specified in Step 4. Make the following changes to the install response file:
- Change the SOURCE_DIRECTORY value to /a/mnt/disk1/image. The /a/mnt/disk1/image corresponds to the $MNTDIR value specified in the JumpStart finish script.
- Change the TARGET_DIRECTORY value to /a/target_directory, where target_directory is the directory on each install client where the Sun Management Center base agent is to be installed.
- Change the value of the SETUP_NOW parameter to zero. Setting the value of the SETUP_NOW parameter to zero ensures that the Sun Management Center setup does not automatically run on each install client when the Sun Management Center base agent has been installed.
The following sample shows a basic Sun Management Center install response file after edits have been completed.
```
SUNMC_VERSION=4.0
ENVIRONMENT=1
SOURCE_DIRECTORY=/a/mnt/disk1/image
TARGET_DIRECTORY=/a/opt
OSVERS=8
PRTOUT= Sun Microsystems sun4u PCI (UltraSPARC-II 450MHz)
LAYER.SERVER=0
LAYER.AGENT=1
LAYER.CONSOLE=0
SETUP_NOW=0
```
The value of the PRTOUT parameter is not important because the base agent is platform independent. However, JumpStart requires this parameter to be present. Do not delete the PRTOUT parameter.

Edit the Sun Management Center setup response file.

You must edit the setup response file so that it can be used by JumpStart. The setup response file is the file name that you specified in Step 6. Make the following changes to the setup response file if needed:
- Make sure that the server name specified by the SUNMC_SERVER parameter is the name of the Sun Management Center 4.0 server machine.
- Make sure that the value of the START_SUNMC parameter is set to 1 (one). Setting the value of the START_SUNMC parameter to 1 ensures that the Sun Management Center base agent is started after it has been set up.
- Make sure that the agent_OPTIONAL_PORT parameter is present, and that the assigned value is either a valid port number, or the text string DEFAULT.
- Make sure that all of the parameters in the sample setup response file shown below are present.
The following examples show a Sun Management Center setup response file before and after JumpStart edits have been applied. In both examples, bootserver01 is the name of the Sun Management Center server machine.

Example 6–1 Setup Response File Before JumpStart Edits Are Applied

SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1

Example 6–2 Setup Response File After JumpStart Edits Are Applied

DISABLE_SNMPDX_DAEMON=1
STOP_SNMPDX=1
SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1

In this example, the line DISABLE_SNMPDX_DAEMON=1 disables the SNMP daemon. The line STOP_SNMPDX=1 stops the SNMP daemon. The line SUNMC_SERVER=bootserver01 specifies that the base agent Sun Management Center server host is the machine named bootserver01. The line agent_OPTIONAL_PORT=1161 assigns port 1161 to the agent. The line START_SUNMC=1 starts the base agent when base agent setup is complete.