| Configuration and Service Tracker, version 3.5 |    
|
| Configuration and Service Tracker, version 3.5 |
|
| Chapter 2- |
|
Installing CST |
This chapter provides information on the following topics:
CST 3.5 software has the following packages:
SUNWcstu is the CST 3.5 core package which contains both server component and agent component. Server component should be installed on the CST server (middleware) machine and agent component should be installed on each monitored host. Based on the user's choice during the install, the corresponding component will be installed on the machine automatically.
SUNWcstu supports both standalone and Sun Management Center versions 3.0 and 3.5 environments.
SUNWecsts is the CST service module to be installed on the Sun Management Center server to communicate between CST and Sun Management Center. SUNWecsts is bundled within CST 3.5_Sun Management Center compressed files.
SUNWecst is the CST agent module to be installed on Sun Management Center agent to communicate between CST and Sun Management Center. SUNWecst is bundled within CST 3.5 Sun Management Center compressed files.
|
Note - In a stand-alone environment, you only need SUNWcstu. |
Install the CST 3.5 server packages on the selected server, and install the agent packages on each agent machine. The space requirements are described in TABLE 2-1:
|
Note - The SUNWecsts and SUNWecst packages should be installed only in a Sun Management Center environment. |
CST 3.5 does not support an upgrade from CST 1.0.1 or CST 1.1.3_AMS.
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.
The requirements for the CST server are listed below:
Since the FRU related libraries have a dependency on Solaris 8, or later, there is a constraint that a CST middleware machine should have Solaris 8, or later, 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.
|
Note - There is no cost for TCP protocol use between the agent and the server. The TCP protocol should be used sparingly and only on machines in the DMZ in the customer IT environment. |
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.
The installation script asks for several bits of information, including the CST central file system root directory path and the root path where the HTTP documents are located.
|
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:
Installation of <SUNWcstu> was successful.
7. To verify the CST server component has been installed properly, type:
The CST daemon, cstd.svr, and csthb.svr should be up and running.
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.5 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: one of thse pkgrm commands, as appropriate for your system:
# pkgrm SUNWcstve
or
# pkgrm SUNWcstv
or
# pkgrm SUNWcstu
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.5 is supported on Solaris OS 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
To enable the CST agent to correctly track system availability in a live upgrade or multi-boot environments, add the following entry to the /var/opt/SUNWcst/cst.conf file
ALT_TSDIRPATH<tab><path_to_directory>
The directory path must be a local file system (e.g,, ufs) mounted on the same mount point across all the boot environments on that system. This serves as a static reference point for CST to record the outage timestamp information.
In case this has to be done on an already installed CST 3.5 agent, stop the agent and restart it after making the necessary changes to the /var/opt/SUNWcst/cst.conf file.
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:
The usage format for cstattach is:
cstattach [-h hierarchy] [-m middleware] [-t transport] -a <agentname> -k <agentkey>
The cstattach utility must be run from the server.
The usage format for cstattagt is:
cstattagt [-h hierarchy] [-t transport] <middleware>
The cstattagt utility must be run from the agent.
|
Note - See, the Utilities chapter for details on cstattach and other utilities. |
CST 3.5 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.5 agent is uninstalled and reinstalled.
2. Remove the existing CST agent package, SUNWcst or SUNWcstu. Run pkgrm for the file that is currently installed. Run the one appropriate for your system. Type either:
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 are 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.
It may take SUNWcstu up to 30 minutes to probe the SSP or SC configuration. During this time, the CST SC software automatically detects the platform, and SSP names and creates the appropriate hierarchy.
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.5 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.
15K domains and system controller
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]/[PLATFORM_NAME]
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.
To attach an F15K domain with the platform name, "clyde," type:
# cstattach -h department1/group2/clyde -a sunfiredomain1.eng.sun.com -k 123456
To attach the same node with no user defined hierarchy, type:
# cstattach -h clyde -a sunfiredomain1.eng.sun.com
-k 123456
15K System Controller CST provides support for the following tracking on a SSC:
To attach an SSC system, the hierarchy should be in the following format:
[USER_DEFINED_HIERARCHY]/[PLATFORM_NAME]/SSC
The difference from the domain is that the fixed word, SSC, is added at the end of the platform hierarchy command.
# cstattach -h clyde/SSC sunfiressc1.eng.sun.com 123456
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:
This creates a file named ssc.tar.
4. Transfer the tar file to the CST middleware system and extract the content to the path:
[repository_path]/[USER_DEFINED_HIERARCHY]/[PLATFORM_NAME]
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:
[USER_DEFINED_HIERARCHY]/[PLATFORM_NAME]/SSP
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.
# cstattach -h clyde/SSP e10kssp1.eng.sun.com 123456
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:
This creates a file named ssp.tar.
4. Transfer the tar file to the CST middleware system and extract the content to the path:
[repository_path]/[USER_DEFINED_HIERARCHY]/[PLATFORM_NAME]
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:
http://<middlewarename>/cstj2.html
or
http://<middlewarename>/cst.html
Where <middlewarename> is the host name where you installed the CST middleware. cstj2.html, using java plug-in technology, has a much improved performance for the applet.
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 or Sun Management Center 3.5 Software User's Guide for further instructions.
CST server and agent processes are started automatically as soon as the software is installed.
2. Download the CST 3.5 Sun Management Center packages from the Sun Download center. The URL is:
http://wwws.sun.com/software/download/sys_admin.html
|
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:
# uncompress CST3.5_SunMC.tar.Z
There are three packages in the directory, tmp_dir/Addons/CST/Common/Basic:
5. Apply the Sun Management Center 3.5 patch, 113122-01, to your Sun Management Center 3.5 server system.
|
Note - For Sun Management Center 3.0 installations, you must follow the next several steps to prepare your Sun Management Center environment. |
1. Log into your Sun Management Center 3.0 server.
/opt/SUNWsymon/sbin/es-stop -A
3. In the /opt/SUNWsymon/sbin/es-start file, change all "SUNWcstv" to "SUNWcstu"
4. In /opt/SUNWsymon/sbin/es-stop file, change all "SUNWcstv" to "SUNWcstu"
5. Start the Sun Management Center server. Type:
/opt/SUNWsymon/sbin/es-start -A
1. Log into the Sun Management Center server as a superuser. and run the pkgadd command to install the CST server component. Type:
The CST 3.5 software is installed in /opt/<SUNWcstu> by default. However, the installation script will allow you to enter another path if you prefer.
2. 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
3. On the server system, verify that the CST service agent process within Sun Management Center has started. Type:
The output could look similar to this if the process is running:
root 19666 1 0 Oct 10 ? 1:36 esd - init cstservice -dir /var/opt/SUNWsymon -q
This step is only necessary for server installation. You can skip this step for agent software installations.
4. Now that the CST server software is installed, follow steps 1 through 4 to install the CST 3.5 agent software on each Sun Management Center agent.
When installing the agent software, the script uses the words "agent component" wherever you saw "server component." Both agent packages are installed in this process.
The installation script prompts you for the name of the CST server to which the agent reports.
|
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 the Getting Started chapter, and go to the Starting CST in the Sun Management Center section. That section and others following provide 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.
To check for previously installed versions, type:
Each detected CST package will be listed.
Each listed package must be removed before you install the new version of CST.
3. To remove the packages, type the following:
On systems where CST server software was installed, the package names are SUNWcstu, SUNWcstve or SUNWcstv, and SUNWecsts. For agent software, the package names are SUNWcst and SUNWecst.
During package removal, answer the script questions as they display. The messages notify you when the package removal is complete and successful.
The CST software is installed in /opt/<SUNWcstu> by default. However, the installation script will allow you to enter another path if you prefer.
4. 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
5. On the server system, verify that the CST service agent process within Sun Management Center has started. Type:
The output could look similar to this if the process is running:
root 19666 1 0 Oct 10 ? 1:36 esd - init cstservice -dir /var/opt/SUNWsymon -q
This step is only necessary for server installation. You can skip this step for agent software installations.
6. Now that the CST server software is installed, follow steps 1 through 4 to install the CST 3.5 agent software on each Sun Management Center agent.
When installing the agent software, the script uses the words "agent component" wherever you saw "server component." Both agent packages are installed in this process.
7. 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 Getting Started chapter. Go to the Starting CST in Sun Management Center. That section and following sections provide 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 the Utilities chapter, cstdecomm section for details on this utility.
| Configuration and Service Tracker, version 3.5 | 817-0706-02 |
|
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.
