Chapter 2 Sun Management Center 3.5 Update 1 Installation and Configuration

Sun Management Center 3.5 Update 1 is installed and configured with the same procedures as Sun Management Center 3.5 except for minor differences for the x86 agent. For information on installing, configuring, or upgrading from previous product releases, see the Sun Management Center 3.5 Installation and Configuration Guide.

This chapter discusses the following topics that pertain to the installation and configuration of Sun Management Center 3.5 Update 1:

• Upgrade Path from 3.5 to 3.5 Update 1

• Supported Platforms, Requirements, and Agent Resource Usage

• Installation and Agent Update for x86

• Documentation Installation

• SNMP Encryption (Privacy)

• Multiple Trap Destinations

• Registration Trap Configuration

Upgrade Path from 3.5 to 3.5 Update 1

Upgrading from Sun Management Center 3.5 to Sun Management Center 3.5 is similar to the upgrading procedure from Sun Management Center 3.0 to Sun Management Center 3.5. For details on upgrading, see “Upgrading From Sun Management Center 3.0” in Sun Management Center 3.5 Installation and Configuration Guide.

On an installed, set up, and running Sun Management Center 3.5 host, do the following:

1. Run es-inst from the 3.5 Update 1 source image.

   This uninstalls Sun Management Center 3.5 and asks you whether to preserve the data.

2. Type y to preserve the data.

   After uninstallation of Sun Management Center 3.5 components, the new packages for Update 1 are installed. The Installer takes you to setup. The setup detects the preserved data and asks you whether or not to migrate the data.

3. Type y to migrate the data.

   The upgrade procedure is complete.

Supported Platforms, Requirements, and Agent Resource Usage

This section gives updated information on supported platforms, requirements, and agent resource usage for Sun Management Center 3.5 Update 1.

Supported Platforms

Sun Management Center 3.5 Update 1 supports the same operating environments as Sun Management Center 3.5. The following table lists the supported platforms. For more information, see the Sun Management Center 3.5 Installation and Configuration Guide.

JDK Version Requirements

Sun Management Center 3.5 Update 1 requires JDK 1.4.2 for the Sun Management Center server layer. The JDK 1.4.2 is shipped with Sun Management Center 3.5 Update 1 and can be found on the Sun Management Center 3.5 Update 1 Software CD 1 of 2 in the directory JDK1.4.2_03.

For more information, see the README.html file in the JDK1.4.2_03/Solaris directory and the “JDK Version Requirements” in the Sun Management Center 3.5 Installation and Configuration Guide.

Agent Resource Usage

The following table gives estimates of the agent CPU and RAM usage by system type and includes information for the x86 agent.

Installation and Agent Update for x86

Installing and updating the x86 agent is similar to the SPARC procedures with some minor differences.

Installing the x86 Agent

You can install the x86 agent by using the command-line installation script, es-inst, or by using the graphic user interface installer, es-guiinst.

To Install the x86 Agent Using the Command-Line Installation Script

1. Log in as root on the machine where you want to install the x86 agent.

2. In the /etc/nsswitch.conf file, ensure that the group entry has files as the first token.

   group: files nis

3. Review the README file, either /cd-rom-mount-point/disk1/x86/sbin/README.INSTALL or /cd-image-dir/disk1/x86/sbin/README.INSTALL.

4. Run the command-line installer at the following location.

   • If you are installing from CDs, insert disk 1 and then type:

     cd-rom-mount-point/x86/sbin/es-inst

     If you are prompted for disk 2, insert disk 2 and then type:

     cd-rom-mount-point/x86/image

   • If you are installing from a CD image, type:

     cd-image-dir/disk1/x86/sbin/es-inst

     where cd-image-dir is the directory where you copied the installation CD or where you downloaded and untarred the installation image from the Web.

5. Follow Steps 5 to 18 in “To Install Using the es-inst Script” in the Sun Management Center 3.5 Installation and Configuration Guide.

To Install the x86 Agent Using the GUI

1. Open a terminal window, then type the command xhost + in the terminal window.

   Also, ensure that the DISPLAY environment variable is set to the machine's display.

2. Log in as root on the machine where you want to install the x86 agent.

3. Make sure that the group entry in the /etc/nsswitch.conf has files as the first token.

   group: files nis

4. Review the README file, either /cd-rom-mount-point/disk1/x86/sbin/README.INSTALL or /cd-image-dir/disk1/x86/sbin/README.INSTALL.

5. Run the GUI installer at the following location.

   cd-rom-mount-point/x86/sbin/es-guiinst

   If you are prompted for disk 2, insert disk 2 and then type:

   cd-rom-mount-point/x86/image

6. Follow Steps 6 to 18 in “To Install Sun Management Center 3.5 on the Solaris Platform” in the Sun Management Center 3.5 Installation and Configuration Guide as appropriate.

Using the Agent-Update Image Feature for x86

When you use the agent update feature, you create a single image and apply it to multiple hosts. You need to create separate update images for SPARC and x86. The procedures for creating and applying agent-update images varies slightly for x86. For general information on creating an agent installation and update image, see “Creating Agent Installation and Update Images” in the Sun Management Center 3.5 Installation and Configuration Guide.

You can create the agent-update image by using the es-gui-imagetool, which has a graphical user interface, or by using the es-imagetool, which has a command-line interface.

To Create an Agent-Update Image Using es-gui-imagetool for x86

1. Log in as root on the Sun Management Center 3.5 Update 1 server machine.

2. Run the Sun Management Center 3.5 Update 1 GUI image tool by typing the following command:

   # /opt/SUNWsymon/sbin/es-gui-imagetool

   The Welcome screen appears. Click Next. The Overview screen appears, listing the information that you might need to provide. Click Next.

   The Select Update-Image Components screen appears.

3. Select the update-image components.

   Four choices are provided:

   • Base Agent Packages

   • Add-on Agent Packages

   • Base and Add-on Agent Packages

   • Base and Add-on Agent Patches Only

   ---

   Note –

   Any patches needed for a selected package are automatically included when you select the package. If you want to install base agent patches and add-on agent patches only, select Base and Add-on Agent Patches Only.

   ---

   Select the type of update-image that you want to create, and then click Next. The Specify the Installation Files Source Directory screen appears.

4. Provide the name of a valid Sun Management Center 3.5 Update 1 source directory.

   The installation source default /cdrom/cdrom0/image is displayed.

   • If you are installing from CDs, insert Sun Management Center 3.5 Update 1 Software CD 1 of 2 in the CD-ROM drive.

     Enter the following path:

     /cd-rom-mount-point/x86/image

   • If you are installing from a Sun Management Center 3.5 Update 1 image on disk, type the path to the disk1/x86 in the Source Directory field. For example, type:

     Source Directory: cd-image-dir/disk1/x86/image

   Click Next.

5. Follow Steps 5 to 12 in “To Create an Agent-Update Image Using es-gui-imagetool” in the Sun Management Center 3.5 Installation and Configuration Guide as appropriate.

   ---

   Note –

   When you are asked to provide a name for the agent update-image, it is recommended that you use a naming convention that indicates the x86 architecture, for example, x86baseagent.

   ---

6. Apply the agent-update image by following To Install or Update Agents From an Agent-Update Image Using agent-update-bin for x86.

To Create an Agent-Update Image Using es-imagetool for x86

1. Log in as root on the Sun Management Center 3.5 Update 1 server machine.

2. Run the Sun Management Center 3.5 Update 1 command-line image tool by typing the following command:

   # /opt/SUNWsymon/sbin/es-imagetool

3. Select the components to update.

   You are prompted to select the components that you want to add to the update-image, for example:

   Select the components you want to add to the update-image. Do you want to upgrade components of Base Agent? [y|n|q] y Do you want to install/upgrade components of Addons? [y|n|q] y

   Type y to add the component to the update-image, or type n to exclude the component from the update-image.

   You are prompted for a valid source directory.

4. Provide the name of a valid Sun Management Center 3.5 Update 1 source directory.

   • If you are installing from CDs, insert Sun Management Center 3.5 Update 1 Software CD 1 of 2 in the CD-ROM drive and type the path to the Sun Management Center 3.5 Update 1 installation directory for x86.

     Enter a valid source directory: /cdrom-mount-point/x86/image

   • If you are installing from a Sun Management Center 3.5 Update 1 image on disk, type the path to the image disk1/x86/image directory. Type:

     Enter a valid source directory: /cd-image-dir/disk1/x86/image

5. Follow Steps 5 to 9 in “To Create an Agent-Update Image Using es-imagetool” in the Sun Management Center 3.5 Installation and Configuration Guide as appropriate.

   ---

   Note –

   When you are asked to provide a name for the agent update-image, it is recommended you use a naming convention that includes the x86 architecture. For example, type x86baseagent.

   ---

6. Apply the agent-update image by following To Install or Update Agents From an Agent-Update Image Using agent-update-bin for x86.

Because Sun Management Center 3.5 Update 1 is the first version to have the x86 agent, you can update agents initially by using the agent-update.bin method only. For incremental add-on installations of agents, you can use the manage jobs tasks, described in “To Install Agents From an Agent-Update Image Using the Manage Jobs Task” in the Sun Management Center 3.5 Installation and Configuration Guide.

To Install or Update Agents From an Agent-Update Image Using agent-update-bin for x86

1. Log in as root on the Sun Management Center 3.5 Update 1 server machine.

2. Create an agent-update image using either of the image tools.

   • To create an agent-update image using es-gui-imagetool, follow the instructions in To Create an Agent-Update Image Using es-gui-imagetool for x86.

   • To create an agent-update image using es-imagetool, follow the instructions in To Create an Agent-Update Image Using es-imagetool for x86.

3. Download the appropriate agent-update.bin from the Sun Management Center server to each target machine's root directory.

   • For x86 agents, the file is found in /opt/SUNWsymon/base/bin/i386-sun-solaris/agent-update.bin.

   • For SPARC agents, the file is found in /opt/SUNWsymon/base/bin/sparc-sun-solaris/agent-update.bin.

4. Log in as root on the target machine.

5. Go to the directory where you downloaded agent-update.bin.

6. Type ./agent-update.bin -s server -r http-port -p image-name, where

   • server is the server that you logged into in Step 1.

   • http-port is the Sun Management Center 3.5 Update 1 Web server port.

   • image-name is the name of the agent-only image you created in Step 2.

   For example, assume that the Sun Management Center 3.5 Update 1 server name is Production1 and that the Web server port is 8080. Also, assume that the agent-update image name is x86baseagent. You would then type:

   # ./agent-update.bin -s Production1 -r 8080 -p x86baseagent

7. Provide the security seed and the SNMPv1 community string.

   The agent-update process prompts you for the security seed and the SNMPv1 community string.

   • The security seed must be the same seed that you provided when you set up the Sun Management Center 3.5 Update 1 server and agent.

   • The SNMPv1 community string must be the same community string you provided when you set up the Sun Management Center 3.5 Update 1 server and agent.

   The update process applies the update to the machine without prompting for further information.

   When the update process completes, check the update status by viewing the log file /var/opt/SUNWsymon/log/agent-update.log on the target machine.

To Create an Agent-Only Installation Image Using es-makeagent for x86

1. Log in as root.

2. Put the Sun Management Center 3.5 Update 1 Software CD 1 of 2 in the CD-ROM drive.

3. Type the command /opt/SUNWsymon/sbin/es-makeagent.

   You are prompted for the installation source files directory.

4. Type the source directory.

   If you are installing from CD-ROM, type:

   cdrom-mount-point/x86/image

   If you are installing from a CD image, type:

   cdrom-image-dir/x86/image

5. Type the name of the target directory.

   If the directory does not exist, you are asked whether you want to create it. Type y to create the directory, or type n or q to exit to the system prompt.

   The directory you specify must have write permission for root.

   For example:

   # enter the target directory: /es-makeagent-image Directory /es-makeagent-image does not exist Do you want to create it (y|n|q) y

   The es-makeagent script creates the subdirectories disk1 and disk2 in the directory you specified, and then copies the files required to the subdirectories.

   When es-makeagent completes copying files from Sun Management Center 3.5 Update 1 Software CD 1 of 2, the CD is ejected, and you are prompted to insert the second CD or specify the source directory for disk 2.

   1. Remove the first Sun Management Center 3.5 Update 1 installation CD.

      Place the Sun Management Center 3.5 Update 1 CD 2 of 2 in the CD-ROM drive, then close the drive.

   2. When the CD-ROM drive LED turns off, press Return.

      es-makeagent copies the remaining files from the CD.

      You are informed that the agent-only product is available in the directory you specified. The command required to install the agent on the local machine is also displayed.

   ---

   Tip –

   Mount the target directory using NFS, so that the directory is accessible by other machines on your network.

   ---

6. Type the command eject to eject the CD.

   You can now install the Sun Management Center 3.5 Update 1 x86 agent using any of the following methods.

   • Use the es-inst -a command. When prompted for the installation source directory, provide the name of the agent-only installation image that you specified. Make sure that you have shared the agent-only installation image by using Network File Sharing.

   • Apply the agent-only installation image using the JumpStart software.

   ---

   Note –

   The agent-only installation image also contains a tar file that you can ftp to other agent machines and uncompress on each agent machine to create an installation image. The uncompressed installation image directory contains the subdirectories disk1 and disk2. To install from the uncompressed image on each agent machine, change directory to the disk1/sbin directory, and use the es-inst command.

   ---

Limitations to the x86 Agent

The Solaris x86 agents do not support any hardware-specific add-ons. The x86 agents have modules under the Operating System, Local Applications, and Remote Systems categories of the Module Browser tab in the Host Details window. Features such as Physical View, Logical View, Hardware Diagnostic module, and the Config Reader module are not yet available on the Solaris x86 platform.

In the Java Console window, all x86 platforms have the same x86 icon. For example, two different x86 platform machines, such as the LX50 and the VX60, would both have the same icon.

You can filter by platform type when you use the Discovery feature, the Manage Jobs feature, or the PRM add-on. You can filter for the x86 platform by selecting x86 as the platform option.

For the Performance Reporting Manager (PRM) add-on, no system reports and hardware configuration reports are available.

Documentation Installation

Sun Management Center 3.5 Update 1 gives you the option of installing the product documentation packages (SUNWpsmd and SUNWsmd) during product installation. Both the GUI and command line installation ask you to specify whether you want the documentation to be installed into your own environment. Online help for is always installed with the product.

In addition, you can directly view the documentation in HTML or PDF from the Sun Management Center 3.5 Update 1 Software CD 2 of 2.

To Install the Documentation Using pkgadd

1. Log in as superuser (su) on the machine on which you want to install the documentation packages.

   This machine might be a documentation server or an administrative console.

2. Ensure that the SUNWsdocs package is already installed by typing:

   # pkginfo | grep SUNWsdocs

   If the package is installed, the system shows:

   application SUNWsdocs

3. Insert the Software CD 2 of 2 CD into the CD-ROM drive.

   The Volume Manager (vold) should mount the media automatically.

4. Change to the following directory:

   # cd /cdrom/cdrom0/image/PE/CommonForSolaris/Basic

5. Install the packages by typing the following command:

   # pkgadd -d .

   where -d means from the device and the period (.) means to install from the current directory.

6. Select the documentation collections that you want to install from the list.

   All is the default.

   The documentation is installed in /var/opt/sun_docs/sundocs.html.

7. (Optional) View the documentation by opening /var/opt/sun_docs/sundocs.html in your web browser.

To Install the Documentation During Product Installation

1. Follow the directions in the Sun Management Center 3.5 Installation and Configuration Guide.

   For directions on using the graphical user interface installation es-guiinst, see Chapter 6.

   For directions on using the command line installation es-inst, see Appendix B.

2. After you select a language during installation, type y at the prompt that asks whether to install the product documentation:

3. (Optional) View the product documentation by opening /var/opt/sun_docs/sundocs.html in your web browser.

To View Documentation Directly From the Media

1. Launch your browser.

2. Insert Sun Management Center 3.5 Update 1 Software CD 2 of 2.

3. Open the file by choosing the appropriate Open command from the File menu and typing:

   cdrom-mount-point/image/index.html

4. At “Sun Management Center 3.5 Update 1 Software Collection,” select the appropriate language and format for the documentation.

Even though online help and other documentation were not revised for this release and are labeled for Sun Management Center 3.5, they still apply to the product. For documentation issues for the Sun Management Center 3.5 Update 1 collection, see the appropriate release notes and supplements and the Sun Management Center 3.5 Update 1 Release Notes.

es-makeagent Operating System Selection

When creating an agent-only installation image using the es-makeagent command, you can now specify which operating systems to include in the image. Only the packages specific to the specified operating systems are included in the image. You can specify the following versions of the Solaris software:

• Solaris 2.6

• Solaris 7

• Solaris 8

• Solaris 9

SNMP Encryption (Privacy)

Sun Management Center 3.5 Update 1 supports encryption of SNMP communications between server and agent components of Sun Management Center. SNMP encryption support uses the CBC-DES symmetric encryption algorithm. Note the following:

• SNMP encryption on both the Sun Management Center server and agent hosts depends on the SUNWcry package. You must install this package separately.

• SNMP encryption is not supported on Sun Management Center 3.5 and earlier servers and agents even if SUNWcry is installed.

• SNMP encryption support is automatically configured during agent or server setup if the SUNWcry package is detected.

• If SNMP encryption is supported by the agent, SNMP encryption can be enabled on Sun Management Center servers using the es-config script. By using this script, you can turn on or off the auto-negotiate feature. For details, see Enabling SNMP Encryption.

Auto-Negotiate Feature

Sun Management Center 3.5 Update 1 servers that support encryption can be set up to support agents dynamically regardless of whether those agents support encryption. This feature is called auto-negotiate and can be set to on or off.

When you set the auto-negotiate feature to off, you ensure that the server always uses encryption when initiating communication with agents. Environments with strict security policies might prefer this set up. If you set auto-negotiate to off:

• If the agent supports encryption, the agent understands the encrypted SNMP messages.

• If the agent does not support encryption, the agent does not understand the encrypted message. Thus, a timeout occurs and a console message states, “Agent is not responding.” The timeout is recorded in the agent log.

When you set the auto-negotiate feature to on, the server encrypts its SNMP communication with an agent only if the agent supports encryption. As a result, the one of the following events occurs:

• If the agent supports encryption, the agent understands the encrypted SNMP messages.

• If the agent does not support encryption, the SNMP messages are authenticated only and not encrypted.

Enabling SNMP Encryption

To find the current state of SNMP encryption, run the es-config command with no arguments.

To Enable SNMP Encryption for Server Installations

1. Make sure the SUNWcry package, which contains the /usr/lib/libcrypt_d.so encryption library, is installed on the system by typing:

   % pkginfo | grep SUNWcry

   If the package is installed, the system shows:

   application SUNWcry

   ---

   Note –

   The SUNWcry package is part of the Solaris Encryption Kit. To obtain the Solaris Encryption Kit, see your Sun sales representative. For important information about administering secure systems, see your Solaris system administration documentation.

   ---

2. Type the following command as superuser from the agent host:

   # es-config -r

   The system detects whether the SUNWcry package is present and automatically stops all Sun Management Center components. The script then asks for the security seed.

3. Type the security seed.

   The script asks for the SNMPv1 community string.

4. When asked whether you want to initiate encrypted communication, type y to initiate encrypted communication or n to decline.

5. When asked whether you want to enable the auto-negotiate feature, type y to enable or n to decline.

   For details on the auto-negotiate feature, see Auto-Negotiate Feature.

If the SUNWcry package is added or is removed after the initial agent setup, use the es-config script to enable SNMP encryption for the agent.

Multiple Trap Destinations

You can specify multiple secondary trap destinations for Sun Management Center agents with the es-trapdest command. Secondary trap destinations (zero or more) receive the same set of traps that are sent to the primary trap destination. Secondary trap destinations do not receive event traps. By default, all traps sent to secondary destinations use SNMPv2c with a community of public. The security level for secondary destinations is noauth.

Using the es-trapdest Command

Secondary trap destinations are managed with the es-trapdest command. You can use the following options with the command.

You can also specify the following optional parameters when adding a new secondary trap destination with the es-trapdest -a command:

-v version

Specify SNMP version: SNMPv1, SNMPv2c, or SNMPv2u

-u user

Specify the SNMP community or user name

-f filter

Specify the trap filter

Trap Filter Specification

Trap filters are specified as a list of criteria, which can be either a series of numerical OID prefixes or a series of these mnemonic trap names:

• sunmcTraps

• snmpTraps

• coldStart

• warmStart

• linkDown

• linkUp

• authenticationFailure

The trap name sunmcTraps represents the OID prefix for all Sun Management Center enterprise-specific traps, and the trap name snmpTraps represents the OID prefix for all the standard traps defined in the SNMP RFCs.

Trap filters can be either positive or negative. A positive filter specifies which traps to send. A negative filter specifies which traps should not be sent. A negative filter is defined by specifying NOT as the first criterion.

For example, to forward only standard SNMP traps to the secondary trap destination, specify the filter as -f "snmpTraps".

To forward all traps except Sun Management Center enterprise-specific traps to the secondary trap destination, specify the filter as -f "NOT sunmcTraps".

Filter specifications that contain spaces must be enclosed in quotation marks to prevent misinterpretation by the shell.

The following command adds machine02:162 as a secondary trap destination that only receives warmStart and coldStart traps for the Sun Management Center agent:

es-trapdest -a machine02:162 -f "warmStart coldStart"

Platform Agent Instances

Each instance of a platform agent can have its own set of secondary trap destinations. To specify secondary trap destinations for a particular instance of a platform agent, use the -c instance option to the es-trapdest command, where instance is the name of the platform agent instance. If the -c is not specified as an argument to the es-trapdest command, the es-trapdest command uses the default value of agent, which manages the secondary trap destinations for the Sun Management Center agent component.

Registration Trap Configuration

You can configure the agent to send the registration trap at a custom interval. The parameter agentRegisterHoldOff controls the initial delay in sending the first registration trap. By default, the value of this parameter is set to 90 seconds. You can change this parameter value in the file /var/opt/SUNWsymon/cfg/domain-config.x. For example, to set the value to 120 in the file, you would type:

agent = { 
agentServer = <myHostname>   
	..                 
	agentRegisterHoldOff = 120   
}

If for some reason the initial trap is lost and is not received by the configuration server, the parameter agentRegisterRetry controls the interval for resending of the agent registration trap. The parameter has a default value of 300 seconds. If the registration trap is lost, the agent resends the registration trap at the retry interval until it is received by the configuration server.

You can change the parameter value from a minimum of 300 seconds to a maximum of 900 seconds. For example, to set the value to 450 in the file, you would type:

agent = { 
 agentServer = <myHostname>      
	 ..                 
	 agentRegisterRetry = 450         
}