CHAPTER 2

Installing Solstice SyMON

---

Solstice SyMON was first supported in the Solaris 2.5.1 software environment. You must be running at least the Solaris 2.5.1 software environment in order to use Solstice SyMON.

---

Installation Requirements

TABLE 2-1 lists the required disk space for each of the packages and the system on which the packages should be installed.

TABLE 2-1

Package	Package Name	Description	Install On	Disk Space
Server subsystem	SUNWsys SUNWsyrt	Server subsystem package Runtime package	Monitored server	~ 1.15 Mbytes ~ 0.30 Mbytes
Event Manager	SUNWsye SUNWsyrt	Event Generator package Runtime package	Any SPARC system other than the monitored server	~ 1.26 Mbytes ~ 0.30 Mbytes
GUI	SUNWsyu SUNWsyua	GUI subsystem package Images for Sun Enterprise	Desktop SPARC system	~ 4.06 Mbytes ~ 9.81 Mbytes
	SUNWsyub	3000 - 6000 and 3500 - 6500 servers Images for the SPARCserver		~1.65 Mbytes
	SUNWsyuc	1000(E) and SPARCcenter 2000(E) Images for the Sun		~ 4.57 Mbytes
	SUNWsyud	Enterprise 2 and Sun Enterprise 150 Images for the Sun		~ 2.63 Mbytes
	SUNWsyue	Enterprise 450 Images for the Sun		~ 0.78 Mbytes
	SUNWsyuf	Enterprise Network Array Images for the Sun		~ 1.80 Mbytes
	SUNWsyrt	Enterprise 250 Runtime package		~ 0.30 Mbytes
man pages	SUNWsym	man pages	Any SPARC system	~ 0.03 Mbytes
SunVTS Online Diagnostics	SUNWsyc	Standalone configuration reader; prerequisite for	Monitored server	~ 0.29 Mbytes
	SUNWodu	SunVTS Online Diagnostics SunVTS Online Diagnostic utility	Monitored server	~ 1.6 Mbytes
	SUNWvts	SunVTS kernel GUI and tests	Monitored server	~ 23.0 Mbytes

---

Note - The SUNWsyrt package is required on the Server subsystem, Event Manager, and GUI configurations.

---

Only one instance of the Server subsystem and the Event Manager operate on a given server. However, you can have many instances of the GUI subsystem on different systems to monitor one server.

Installing the Software

Installing Solstice SyMON requires these steps:

1. Installing the CDE packages from the Solaris Desktop CD

2. Mounting the Supplement CD

3. Saving any user-customized Solstice SyMON event rules and removing previous versions of Solstice SyMON (all previously installed packages--if upgrading from a previous release)

4. Installing the packages

5. Setting up your environment

6. Configuring the software

7. Starting agents

Installing CDE From the Solaris Desktop CD

In order to have Solstice SyMON online help available (this help is CDE-based online help), you must install the following in this order:

1. Solaris CD

2. Solaris Desktop CD (This CD contains the CDE packages. One of these packages, SUNWdtbas, is required in order to use Solstice SyMON online help)

3. Install Solstice SyMON from the Supplement CD (see the next section)

Installing Solstice SyMON from the Supplement CD

The Solstice SyMON software is located on the SMCC Supplement CD. You need to mount the SMCC Supplement CD so that you can retrieve the Solstice SyMON software from it.

Mounting the CD

Follow the procedure "To Mount the Locally Connected CD-ROM" or "To Mount the Remotely Connected CD-ROM."

· To Mount the Locally Connected CD-ROM

1. Become superuser and create the /cdrom directory (if one doesn't exist).

2. Place the SMCC Supplement CD in the CD-ROM drive and close the drive door.

   If Volume Manager is running, the CD is mounted and the path is: /cdrom/upd_sol_2_6_smcc/Product.

   If Volume Manager is not running complete Step 3, mounting the /cdrom directory manually.

3. Mount the CD manually by typing:

# mount -r -F hsfs /dev/dsk/c0t6d0s0 /cdrom

· To Mount the Remotely Connected CD-ROM

1. Export the /cdrom directory from the server:

   a. Edit the /etc/dfs/dfstab file by adding the following line at the end of the /etc/dfs/dfstab file:

share -F nfs -o ro /cdrom/supp_sol_2_6_598_smcc/Product

b. Start NFS and the mount daemon:

# /usr/lib/nfs/nfsd -a 16 # /usr/lib/nfs/mountd

c. Export the /cdrom file system:

# shareall

2. Mount the /cdrom directory from the server.

• If automountd is running, type:

# cd /net/server_ hostname/cdrom/supp_sol_2_6_598_smcc/Product

• If automountd is not running, type:

# mkdir /cdrom # mount server_ hostname:/cdrom /cdrom # cd /cdrom/supp_sol_2_6_598_smcc/Product

Installing Packages

---

Note - The packages you install for the Server Subsystem, Event Manager, and GUI subsystem are dependent on SUNWsyrt, the SyMON Runtime Library package, and SUNWdtbase, the CDE-base package. Ignore warning messages if you do not install the SUNWsyrt package first.

---

Updating Solstice SyMON From a Previous Release

Before you can install the Solstice SyMON packages, you must completely remove the currently installed Solstice SyMON configuration and remove the previously installed packages.

· To Save Customized Rules Files and Remove Solstice SyMON

1. Save any customized rules files.

   There were syntax and pattern matching changes to rules between Solstice SyMON 1.1 and Solstice SyMON 1.3. Some rule files from Solstice SyMON 1.1 and Solstice SyMON 1.3 SyMON are incompatible.

2. Completely remove the currently installed Solstice SyMON configuration by typing as superuser:

# /opt/SUNWsymon/sbin/sm_confsymon -D

3. Install Solstice SyMON by following the procedures that follow.

   The first step in each procedure describes how to remove the existing packages.

Identifying Previously Installed Packages With pkginfo

Before removing all previously installed packages, you must identify which previously installed packages are installed on each system with the pkginfo command. For example:

# pkginfo SUNWsyrt

If the SUNWsyrt package is installed, the following is displayed:

application scripts SUNWsyrt Solstice SyMON Runtime library and Tcl

If the SUNWsyrt package is not installed, the following is displayed:

ERROR: information for "SUNWsyrt" was not found

Use pkginfo to identify the remaining previously installed packages.

· To Install the Server Packages

1. If you are upgrading from a previous release, remove the existing SUNWsys and SUNWsyrt packages on the monitored server by typing the following as superuser:

# /usr/sbin/pkgrm SUNWsys SUNWsyrt

Answer yes to all questions.

2. Go to the installation directory on the monitored server:

# cd dirname

where:

dirname is the directory where the Solstice SyMON packages are located

3. Add the SUNWsyrt and SUNWsys packages:

# /usr/sbin/pkgadd -d source_directory SUNWsyrt SUNWsys

where:

source_directory is the full path name of the directory where the packages you want to add are located. You can also use 'pwd' for the source_directory.

· To Install SunVTS for Online Diagnostics

· Install the packages necessary for SunVTS Online Diagnostics on the monitored system by typing:

# /usr/sbin/pkgadd -d source_directory SUNWsyc SUNWvts SUNWodu

where:

source_directory is the full path name of the directory where the packages you want to add are located. You can also use 'pwd' for the source_directory.

· To Install the Event Generator Packages

---

Note - If you are installing both the Event Generator and the User GUI subsystem packages on the same system, install SUNWsyrt only one time.

---

1. If you are upgrading from a previous release, remove the existing Solstice SyMON Event Generator software from your desktop system (or on any other system other than the server) by typing:

# /usr/sbin/pkgrm SUNWsye SUNWsyrt

2. Install the Event Generator packages on your desktop system (or on any other system other than the server) by typing:

# /usr/sbin/pkgadd -d source_directory SUNWsyrt SUNWsye

where:

source_directory is the full path name of the directory where the packages you want to add are located.

· To Install the GUI Subsystem Packages

---

Note - If you are installing the Event Generator and User GUI subsystem packages on the same system, do not remove SUNWsyrt (see Step 1, which follows) since you previously installed SUNWsyrt in Step 2 of the previous procedure.

---

1. If you are upgrading from a previous release, remove the existing SUNWsyu and SUNWsyrt packages from the desktop system by typing:

# /usr/sbin/pkgrm SUNWsyu SUNWsyrt

2. Install the GUI subsystem packages on the desktop system by typing:

# /usr/sbin/pkgadd -d source_directory SUNWsyrt SUNWsyu [SUNWsyua SUNWsyub SUNWsyuc SUNWsyud SUNWsyue SUNWsyuf]

where:

• source_directory is the full directory path name where the packages are located
• SUNWsyua contains images for the Sun Enterprise 3000, 4000, 5000, and 6000 systems
• SUNWsyub contains the images for the SPARCserver 1000(E) and SPARCcenter 2000(E)
• SUNWsyuc contains the images for the Sun Enterprise 2 and 150
• SUNWsyud contains the images for the Sun Enterprise 450
• SUNWsyue contains the images for the Sun StorEdge^(TM) A5000
• SUNWsyuf contains the images for the Sun Enterprise 250

Installing the man Pages

You can install the man pages in two ways :

• Without using the Windex database for man pages
• Using the Windex database for man pages

Review the following information before deciding which method to use.

The Windex database is generated with the catman command. The Windex man page database is used by the man -k and apropos commands. For example, if you need to know every man page that mentions disk, you would type man -k disk. You can also invoke the apropos command, by typing apropos logout, which returns man pages related to logout.

Use pkgadd to install the Windex database of man pages. The catman command indexes the Windex database.

· To Install the Man Pages Without the Windex Database

1. If you are upgrading from a previous release, remove the existing SUNWsym package by typing:

# /usr/sbin/pkgrm SUNWsym

2. Add the new man page package by typing:

# /usr/sbin/pkgadd -d source_directory SUNWsym

where:

source_directory is the full path name of the directory where the packages you want to add are located.

· ITo Install the Man Pages With the Windex Database

1. If you are upgrading from a previous release, remove the existing SUNWsym packages and the Windex database by typing:

# /usr/sbin/pkgrm SUNWsym # rm /opt/SUNWsymon/man/Windex

2. Add the new man page package by typing:

# /usr/sbin/pkgadd -d source_directory SUNWsym

where:

source_directory is the full path name of the directory where the packages are located that you want to add

3. Create the new Windex database by typing:

# catman -w M /opt/SUNWsymon/man

Setting Up Your Environment

You can set up your environment for the GUI using the Bourne, Korn, or C shells as follows.

· To Set Up the Environment for the GUI With Bourne and Korn Shells

1. Add the following lines to the .profile file:

SYMONHOME=/opt/SUNWsymon PATH=$SYMONHOME/bin:/opt/SUNWvts/bin:$PATH MANPATH=$SYMONHOME/man:$MANPATH LD_LIBRARY_PATH=$SYMONHOME/lib:$LD_LIBRARY_PATH export SYMONHOME export PATH export MANPATH export LD_LIBRARY_PATH

---

Note - If the software is not installed in /opt/SUNWsymon, replace the /opt/SUNWsymon path with the path you used to install the software in the line beginning with SYMONHOME.

---

2. Make the previous setup parameters effective by logging out and then logging in.

· To Set Up the Environment for the GUI With the C Shell

1. Add the following lines to the .cshrc file:

setenv SYMONHOME /opt/SUNWsymon set path=$SYMONHOME/bin /opt/SUNWvts/bin $path setenv MANPATH $SYMONHOME/man:$MANPATH setenv LD_LIBRARY_PATH $SYMONHOME/lib:$LD_LIBRARY_PATH

---

Note - If the software is not installed in /opt/SUNWsymon, replace the /opt/SUNWsymon path with the path you used to install the software in the line beginning with setenv.

---

2. Make the previous setup parameters effective by typing:

# source .cshrc # rehash

Configuring Solstice SyMON

Before you can run Solstice SyMON in your environment, you must configure the host and the Event Generator host (event host). For example, if you have two systems, server A and a desktop system B, and you want desktop system B to monitor server A, a diagram of the monitoring configuration would look similar to FIGURE 2-1.

FIGURE 2-1

· To configure the host, type the following on server A:

# /opt/SUNWsymon/sbin/sm_confsymon -s EventMonitor_host

where:

EventMonitor_host is the host that monitors this server, which is Server A in this example.

· To configure the Event Generator, invoke the uname -i command on server A.

This command returns the platform name of the system. Use the platform name (for example SUNW,Ultra-Enterprise) as an argument to the sm_confsymon -e command.

---

Note - If the uname -i command returns SUNW,Ultra-1, this platform name is for the Sun Enterprise 150, which is supported by Solstice SyMON. The same platform name is used for the Sun Enterprise 1 system, which is not supported by Solstice SyMON.

Also, the uname -i command returns SUNW,Ultra 2 for both the Sun Enterprise 2 server, which is supported by Solstice SyMON and the Sun Enterprise 2 workstation, which is not supported by Solstice SyMON.

---

3. Type the following on the Event Host:

# /opt/SUNWsymon/sbin/sm_confsymon -e agent_host -P platformname [-d disk_box_name]

where:

• agent_host is the host name of the server running the Server Subsystem, which is Server A in this example
• platformname (SUNW,Ultra-Enterprise in this example) is the platform type returned by the uname -i command
• disk_box_name ia the name of the disk storage enclosure, such as sena, the disk_box_name for the Sun Enterprise Network Array

Starting Solstice SyMON

This section describes how to start running Solstice SyMON. The Server subsystem and the Event Manager start automatically after you reboot your system. To start the server subsystem without rebooting, follow the next procedure, "To Start Solstice SyMON Without Rebooting."

· To Start Solstice SyMON Without Rebooting

---

Note - You can also use the -v flag (verbose installation) with the sm_confsymon command. The system echoes all actions and requests permission to continue when you use the -v flag.

---

1. Start Solstice SyMON on the Server subsystem host by typing:

# /opt/SUNWsymon/sbin/sm_control start

2. Start the Event Generator on the Event Generator machine by typing:

# /opt/SUNWsymon/sbin/sm_control start

3. Run the GUI from your desktop as a regular user by typing:

CTRL-d (to become a regular user) % rehash % /opt/SUNWsymon/bin/symon -t target_system &

where:

target_system is the name of the server running the monitor agents.

Solstice SyMON also recognizes command line options (see Chapter 5, "Command Line Options)." When you invoke the software at the shell prompt, you can use these options on the command line. For example, in the previous screen, the -t option refers to the target system to monitor.

---

Exiting the GUI

This section describes how to exit the GUI. Exiting the GUI shuts down the GUI but does not shut down the software application, which continues to monitor the server.

· To Exit the GUI

1. In the Launcher window, select File > Exit from the menu bar.

   An exit inquiry diaglog box prompt you the "Do you really want to exit?"

2. Click yes to exit Solstice SyMON.

---

Shutting Down Solstice SyMON

---

Note - Normally, the agents and the Event Generator should run continuously, even if GUIs are not attached. Running them continuously monitors the server for events and gathers historical data.

---

· To shut down Solstice SyMON, type the following command as superuser on the server or the event host:

# /opt/SUNWsymon/sbin/sm_control stop

---

Removing Solstice SyMON

---

Caution - SUNWsyrt is the runtime library. Remove SUNWsyrt only if all the SyMON packages are removed from that machine.

---

· To Remove Solstice SyMON

---

Caution - If the Event Generator is also installed on this machine and you want to continue running the Event Generator on this machine, do not remove the SUNWsyrt package.

---

TABLE 2-2

If you remove	The following is removed
SUNWsye package	Event Generator binaries and data
SUNWsyrt package	Runtime library
SUNWsys package	Server binaries and executables
SUNWsyu package	GUI binaries and executable
SUNWsyua package	Images for the Sun Enterprise 3x00-6x00
SUNWsyub package	Images for the SPARCserver 1000/E and SPARCcenter 2000/E
SUNWsyuc package	Images for the Sun Enterprise 2 and 150 systems
SUNWsyud package	Images for the Sun Enterprise 450 system
SUNWsyue package	Images for the Sun StorEdge A5000 subsystem
SUNWsyuf package	Images for the Sun Enterprise 250 system
SUNWsyc package	Standalone configuration reader (prerequisite for SunVTS)
SUNWvts package	SunVTS kernel, GUI, and tests
SUNWodu package	SunVTS Online Diagnostic utility

1. Remove the Server subsystem, runtime library, and SunVTS packages on the Server Subsystem host by typing:

# /usr/sbin/pkgrm SUNWsys SUNWsyrt SUNWsyc SUNWodu SUNWvts

2. Remove the Event Manager and runtime library on a desktop system or any system except the server host by typing:

# /usr/sbin/pkgrm SUNWsye SUNWsyrt

3. Remove the GUI and runtime library on the desktop system by typing:

# /usr/sbin/pkgrm SUNWsyu [SUNWsyua SUNWsyub SUNWsyuc SUNWsyud SUNWsyue] SUNWsyrt

4. Remove the man pages.

• If you do not have the Windex database of man pages, type:

# /usr/sbin/pkgrm SUNWsym

• If you have the Windex database of man pages, type:

# /usr/sbin/pkgrm SUNWsym # rm /opt/SUNWsymon/man/Windex

---

Troubleshooting

If you have problems installing Solstice SyMON, see Chapter 6, "Troubleshooting."

---

Installing and Setting Up SNMP Traps

To install and set up SNMP traps, see Appendix C, "Installing and Setting Up SNMP Traps." An SNMP trap is an asynchronous message directed to a specific monitor.