Chapter 2 - |
Installing CST |
This chapter provides information on the following topics:
CST3.0 software has the following packages:
Note - In a stand-alone environment, you only need SUNWcstu. |
Ensure that a copy of CST is running on the systems at all times. Note that CST is not automatically installed as part of an OS upgrade. It must be added later.
CST3.0 supports upgrading from the following CST versions:
CST3.0 does not support an upgrade from CST 1.0.1 or CST 1.1.3_AMS.
The requirements for the CST server are listed below:
Since the FRU related libraries have a dependency on Solaris 8, there is a constraint that a CST middleware machine should have Solaris 8 installed. However, note that there is NO install dependency between CST packages and the FRU related packages. The FRU packages can be installed at any time, and CST will start using the libraries when they are available.
![]() |
Caution - Do not install or upgrade the middleware and the agent software concurrently. |
Have the following information available before you start to install SUNWcstu on the CST server machine.
a. Type ps -ef |grep httpd to verify that httpd daemon is running.
b. Find the root path to the docs based on httpd path.
If you are installing SUNWcstu on a middleware server for the first time, go to To Install CST Server for the First Time.
If you are upgrading SUNWcstu on a middleware server where the CST server is already installed, go to To Upgrade CST Server.
1. Log in as superuser into the system that will be the middleware server.
2. Go to the directory on the server where the SUNWcstu package is available. Type:
4. During the install, closely monitor the comments from the install process and answer questions as they occur.
Note - If HTTP ROOT is null, none of the applet files are installed. |
5. One of the questions asked is, "Do you want to install a server or agent?" Select server.
6. If the installation of SUNWcstu is successful, the following message displays:
7. To verify the CST server component has been installed properly, type:
This indicates that the server package is installed, has initiated configuration tracking on this system, and has the directory structure set up to hold data for other hosts that will use this server as the middleware.
CST 3.0 supports upgrades from all previously installed CST server versions. The upgrade is a pkgadd, so much of the procedure is automated.
2. Remove the existing CST server packages. Type:
3. Change directories to the directory on the server where the SUNWcstu package is available. Type:
5. As CST already saved data in /var/opt/SUNWcst, the install script does not ask you any directory or path questions. The script automatically installs the server component.
The CST application that resides on each Sun machine to be monitored by CST is the CST agent.
CST 3.0 is supported on Solaris operating environment versions 2.6, 7, 8, and 9. CST does not support Solaris 2.5.1.
![]() |
Caution - Ensure that the SUNWcstu server component on the middleware machine has been installed or upgraded before installing SUNWcstu on the agent machine. |
Have the following information available before you start to attach a SUNWcstu agent component to a server:
1. System locations--lab, offices, remote, etc.
3. Functions performed by systems
The CST agent, SUNWcstu, must be installed on each host (node) to be tracked by CST.
2. Change directory to the release directory where CST packages are located. Type:
3. Add SUNWcstu package by typing this command:
4. Answer any questions as they are presented.
Note - When you install the CST agent component for the first time, the CST agent is run in the unattached mode. You need to attach the agent to the server. |
When an agent is installed and it has not been previously attached to a middleware, you must bind the CST agent to the CST middleware system by running either the cstattach utility or the cstattagt utility.
By attaching an agent to CST middleware system, you can:
Note - For details on this utility, Chapter . |
CST 3.0 supports upgrading the CST agent from all the previous CST versions except CST 1.0.1 and CST 1.1.3_AMS and for situations where the CST 3.0 agent is uninstalled and reinstalled.
2. Remove the existing CST agent packages. Type:
3. Change directories to where SUNWcstu is installed. Type:
If CST is installed on the machine and attached to CST middleware, before the operating system (OS) upgrade, after the OS upgrade, all the previously collected data stored on the machine disk is unavailable. You can reinstall CST following the below procedure so CST tracking can be reinstated.
2. Change directories to where SUNWcstu is installed. Type:
4. From the displayed choices, select Install Agent.
5. When the install script asks if you want to restore the date, Answer Yes.
6. To restore the data to the machine, follow the procedure displayed on your screen.
Sun multi-domain servers include either a system service processor (SSP) or a system controller (SC). The installation of CST on a multi-domain server works the same in both of these types of platforms.
CST on the SSP or SC and CST on the domains collectively give the complete information regarding the multi-domain platform. It is required that you install CST first on the SSP or SC and then on the domains. Be aware that, by default, the CST agent installs in unattached mode, and the agent is required to be attached to a running CST middleware.
The CST attach functionality is designed to ensure a consistent hierarchical structure within the hierarchical view for the multi-domain server supported by its SSP or SC.
1. Install SUNWcstu on the SSP or SC.
2. Install SUNWcstu on all the existing domains.
3. Whenever a new domain is added, install SUNWcstu on that domain.
Installing CST on a Sun Cluster is essentially installing CST on its individual nodes. The installation on various nodes can be done in any sequence. No specific setup is required. CST 3.0 can track events from Sun
Cluster 3.0 and Sun
Cluster 3.1.
Note - For easy manageability, ensure that, during install, the various nodes of a cluster are grouped closely within a well defined hierarchy. |
These guidelines apply to the following Sun system platforms.
It is recommended that the domains be grouped together using the following hierarchy guideline. The hierarchy can be specified using the
-h option when using the cstattach command.
USER_DEFINED_HIERARCHY is optional. When you use the hierarchy option, the Sun Fire system or E10K platform name should be added at the end of the hierarchy value.
This command includes an F15K with the platform name "clyde." Type:
Same node with no user defined hierarchy
CST provides support for the following tracking on a SSC:
To attach an SSC system, the hierarchy should be in the following format:
The difference from the domain is that the fixed word, SSC, is added at the end of the platform hierarchy command.
To attach global platform data, use the following procedure:
1. Log into the main SSC system.
2. Change to the directory where platform data is stored. Type:
3. Create a compressed (tar) file of the data stored in that directory. Type:
4. Transfer the tar file to the CST middleware system and extract the content to the path:
5. Unlock the platform tracking functionality. This can be accomplished by writing a 0 to the file, /var/opt/SUNWcstu/ssc/comm_lock, on the system controller.
CST provides support for the following tracking on an E10K SSP:
To attach an SSP system, the hierarchy should be in the following format:
The difference in the command from usage on a domain is that the fixed word, SSP, is added at the end of the platform hierarchy command.
The E10K platform in this example has the name, clyde.
To attach the global platform data, use the following procedure:
1. Log into the main SSP system.
2. Change to the directory where platform data is stored. Type:
3. Create a compressed (tar) file of the data stored in that directory. Type:
4. Transfer the tar file to the CST middleware system and extract the content to the path:
5. Unlock the platform tracking functionality. This can be accomplished by writing a 0 to the file, /var/opt/SUNWcstu/ssp/comm_lock, on the E10K service system processor.
There are two scenarios when you verify installation:
1. Once you finish installing the SUNWcstu agent component, there should be two processes running;
2. From any system, bring up a browser and go to the CST applet. Type this URL in your browser address field:
3. Look for the host where the new CST agent was installed. Browse the information presented in the applet.
The CST software consists of three packages:
Before you begin this procedure, Sun Management Center must already be installed, configured, and running. See the Sun Management Center 3.0 Software User's Guide for further instructions.
CST server and agent processes are started automatically as soon as the software is installed.
Install the CST 3.0 server packages on the Sun Management Center server, and install the agent packages on each agent machine. The space requirements are described in TABLE 2-1:
2. Download CST 3.0 from the Sun Management Center Website:
Note - You are asked to specify the directory in which to save the CST tar file. For the purpose of these instructions, this directory is referred to as <tmp_dir>. |
3. Change directories to the location of the downloaded tar file. Type:
4. Uncompress and untar the CST tar file. Type:
This command creates a directory in tmp_dir called image, and places the CST source packages in it.
5. Listed below are the questions within the installation script. Be prepared with the answers to these questions before you run the installation script.
Note - The Sun Management Center agent is automatically stopped and restarted by the CST installation script. |
The set of questions you receive depends on the installation procedure you perform. Not all of the above questions are asked during your installation.
2. On the system using the Sun Management Center server software, change directories to the root path where Sun Management Center is installed. The default path is /opt/SUNWsymon, but the exact path can be different and is determined by the user.
3. Run the installation script from the directory where the Sun Management Center software resides. Type:
Note - After the CST installation is completed, answer n to running the setup procedure. |
4. Verify the installation of both CST server packages by checking for the CST daemon processes. Type:
The output could look similar to this if both processes are running:
root 13855 1 0 11:44:17 ? 0:00 csthb.svr
root 13846 1 0 11:44:16 ? 0:00 /opt/SUNWcstu/bin/cstd.svr option
5. On the server system, verify that the CST service agent process within Sun Management Center has started. Type:
root 19666 1 0 Oct 10 ? 1:36 esd - init cstservice -dir /var/opt/SUNWsymon -q
6. Now that the CST server software is installed, follow steps 1 through 4 to install the CST 3.0 agent software on each Sun Management Center agent.
Note - The CST agent is already a part of the CST server. You do not need to separately install the agent on the server system. |
Note - Only the CST agent package can be installed on an E10K SSP, and on a Sun Fire 15K and Sun Fire 12K system controller. |
To view an agent under the Sun Management Center console, follow the steps outlined in the Chapter 3, Getting Started. That chapter provides information on how to start Sun Management Center and view each machine through the CST console.
2. Remove any previously installed versions of the CST software.
3. To remove the packages, type the following:
4. On the system using the Sun Management Center server software, change directories to the root path where Sun Management Center is installed. The default path is /opt/SUNWsymon, but the exact path can be different and is determined by the user.
5. Run the installation script from the directory where the Sun Management Center software resides. Type:
Note - After the CST installation is completed, answer No to running the setup procedure. |
6. Verify the installation of the CST server packages by checking for the cstd.svr and csthb processes. Type:
The output could look similar to this if both processes are running:
root 13855 1 0 11:44:17 ? 0:00 csthb.svr 1
root 13846 1 0 11:44:16 ? 0:00 /opt/SUNWcstu/bin/cstd.svr
7. On the server system, verify that the CST service agent process within Sun Management Center has started. Type:
root 19666 1 0 Oct 10 ? 1:36 esd - init cstservice -dir /var/opt/SUNWsymon -q
8. Now that the CST server software is installed, follow steps 1 through 4 to install the CST 3.0 agent software on each Sun Management Center agent.
9. The CST agent is installed and run in unattached mode. Please, refer to the cstattach section to attach the agent to the CST server.
Note - Only the CST agent package can be installed on an E10K SSP, and on a Sun Fire 15K and Sun Fire 12K system controller. |
To view an agent under the Sun Management Center console, follow the steps outlined in the Chapter 3, Getting Started. That chapter provides information on how to start Sun Management Center and view each machine through the CST console.
To uninstall previous versions of CST, see Step 1 of To Prepare for CST Installation in Sun Management Center Environment. There is currently no support for uninstalling Sun Management Center add-on packages using the es-uninst script.
![]() |
Caution - Do not remove the repository directory from the CST server that was created when CST was first installed. CST collected data will be lost if the repository directory is removed. |
2. Check for existing packages. Type:
3. Remove the CST packages installed on your machine, one package at a time. Type:
4. Repeat until all packages are removed.
5. If you want to also remove the CST software footprint left on the machine (required if you want to perform a fresh install of CST), type:
![]() |
Caution - On your server system, you must remove SUNWecsts first, then SUNWcstu. On an agent, remove SUNWecst first, then SUNWcstu. |
Note - If you want to totally remove CST and want to perform a fresh install, you must remove the directory, /var/opt/cst, on the agent machine. |
When the tracking of events is to be stopped on a host, such that availability tracking and reporting for this host can be terminated on the Sun side, cstdecomm utility needs to be executed.
Execution of this utility accomplishes the following:
1. Appends a marker event called "Tracking Ended," to the history file
2. Moves the data for this host to a separate "Decommissioned Agents" directory
3. Detaches the host from the middleware
See Chapter 6, Utilities, cstdecomm, for details on this utility.
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.