A P P E N D I X A |
Install, Set Up, and Uninstall Sun Management Center 3.5 Software Using the CLI |
This appendix provides instructions for installing, setting up, uninstalling, starting, and stopping the Sun Management Center 3.5 software, including the base software, the Fabric Manager, the RSM proxies , and the Sun Fire Link agent softwareon their respective hosts using the CLI.
This appendix assumes you are doing a fresh installation. If you are upgrading Sun Management Center 3.0 PU4 software to Sun Management Center 3.5 software, see Upgrading from Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5.
![]() |
Caution - Use the installation and setup scripts or Wizards provided with the Sun Management Center 3.5 software. Do not manually add packages or manually change configuration files. |
See Chapter 3 for instructions on installing, setting up, and uninstalling the same software using the Sun Management Center 3.5 Wizards.
The CLI script es-uninst has an option to uninstall one module, several modules, or all Sun Management Center 3.5 software.
You can install on multiple nodes in parallel using the Agent Update feature. See Chapter 4 for using the Agent Update feature.
Sun Management Center software runs on top of the Sun Fire Link Manager and provides a convenient GUI interface for monitoring and managing the RSM network on a Sun Fire cluster.
The Sun Fire Link release provides Sun Management Center add-on packages for Sun Fire 15K/12K and 6800 systems. TABLE 3-1 lists the Sun Management Center packages provided in the Sun Fire Link release.
These packages need to be installed on various systems.
The latter three roles might be filled by the same system or by two or three different systems. Most commonly, the administration server doubles as the Sun Management Center console, and a separate (usually larger) system acts as both Sun Management Center server and Sun Fire Link Manager server. See FIGURE 3-1 for a graphic representation of the system location requirements of the various packages.
Note - The es-inst script changes various /etc/system entries to provide sufficient resources for database activities that Sun Management Center performs. These changes are shown in CODE EXAMPLE A-1. |
The examples shown in this section assume the following:
If your configuration differs from this, adjust your use of the installation script accordingly.
To perform the Sun Management Center 3.5 base software installation, log in to each target system as superuser, and run the Sun Management Center CLI script es-inst, which walks you through the installation. For more information about installing using the CLI, refer to Appendix A of the Sun Management Center 3.5 Installation and Configuration Guide.
If you will be upgrading a system from Sun Fire Link 1.0 software to 1.1 software, you must first remove the version 1.0 packages from the FM server and the cluster nodes. The procedure for doing this is described below.
1. Stop the RSM proxy daemons on every cluster node.
# /etc/init.d/wrsm_proxy stop |
2. Remove the FM packages from the FM server and every cluster node.
# /etc/init.d/wrsm_proxy stop |
You need to install the Sun Management Center 3.5 Base software first. Once that is installed, you can install the add-on software that supports the Sun Fire Link. At this point you can also install add-on software that supports the Sun Fire 15K/12K systems and Sun Fire 6800 systems. For more information about installing Sun Fire 15K/12K systems using the CLI, refer to Appendix A of the Sun Management Center 3.5 Supplement for Sun Fire 15K/12K Systems. For more information about installing Sun Fire 6800 systems using the CLI, refer to Appendix A of the Sun Management Center 3.5 Supplement for Sun Fire 6800/4810/4800/3800 Systems.
Note - When installing the Sun Management Center software, type y for yes, n for no, or q to quit. |
# ../sbin/es-inst -S |
The preceding example assumes you are in the .../disk1/image directory.
The script displays this message.
2. Either accept the default of /opt, or enter a different target directory.
The script displays this message.
3. Type y for each optional component you want to install.
The script displays this message.
The following Add-On Products will be installed: Sun Fire Link Do you want to proceed? [y|n|q] |
4. Type y to proceed with installation, n to not proceed, or q to quit.
If you type y to proceed, all the add-on products you selected are installed in turn. The script displays a message when each product is installed, saying that the installation was successful. You then receive a message asking if "you want to run setup now?"
You can specify that you want to run setup right after installation. Or you can do it at a separate time, which the procedure below assumes. For more information about setting up Sun Management Center 3.5 software using the CLI, refer to Appendix A in the Sun Management Center 3.5 Installation and Configuration Guide.
|
Note - When setting up Sun Management Center software, type y for yes, n for no, or q to quit. |
# ./es-setup |
The script displays this message.
2. Type l to load a module instance, u to unload an instance, or d for done.
If you type d, the script displays this message.
Enter the path to a valid JRE[/usr/java]: |
3. Either accept the default path to a valid Java Runtime Environment (/usr/java), or enter a different path to a valid JRE.
The script displays this message.
Enter a NON EXISTING Data Directory for the Sun Fire Link Manager(Suggested location is a new subdirectory of /var/opt/): |
4. Enter a NON-EXISTING Data Directory for the Sun Fire Link Manager; for example, /var/opt/fmjm as a subdirectory of /var/opt/.
The script displays this message.
5. Type l to load a module instance, u to unload an instance, or d for done.
If you enter d, the script displays this message.
Do you want to start Sun Management Center agent and server components now? [y|n|q] |
Whether you start the software now or not, the script tells you that the "Setup of Sun Management Center is complete," and tells you the location of the setup logfile.
When the Sun Fire Link add-on component is installed and set up during Sun Management Center 3.5 installation, all the Sun Fire Link packages are installed. You will need to set up security access for Sun Fire Link users once the Sun Fire Link add-on component is installed and set up.
1. On each RSM domain, establish security settings for Sun Fire Link user access.
Add a group named sfladmin and add the valid users to this group.
Add the users you listed in /etc/group to /etc/passwd.
c. Execute pwconv to update /etc/shadow.
d. Execute passwd to assign passwords to the new users.
2. On the Sun Fire Link Manager server, establish security settings for Sun Fire Link users.
Add a group named sfladmin and add the valid users to this group.
Add the users you listed in /etc/group to /etc/passwd.
c. Execute pwconv to update /etc/shadow.
d. Execute passwd to assign passwords to the new users.
For more information about uninstalling using the CLI, refer to Appendix A of the Sun Management Center 3.5 Installation and Configuration Guide.
|
Note - When uninstalling the Sun Management Center software, type y for yes, n for no, or q to quit. |
# ./es-uninst |
The system displays this message.
2. Type y to uninstall Production Environment, which uninstalls all Sun Management Center software.
The system displays this message.
This will uninstall ALL Sun Management Center Products. !!! Do you want to change selection? [y|n|q] |
The system displays your selection; go to the beginning of Step 2.
The system displays this message.
Do you want to preserve database? [y|n|q] |
4. Type y to keep any existing topology and event data; or type n to discard the data.
The system displays this message.
Proceed with uninstall? [y|n|q] |
5. Type y to proceed with the uninstall; or type n to not proceed with the uninstall.
If you type y to proceed, the system displays the list of packages to be uninstalled, the packages as they are uninstalled, the status of the uninstallation, and the location of the log file.
The Sun Fire Link add-on module you can install is:
Note - When uninstalling the Sun Management Center software, type y for yes, n for no, or q to quit. |
# ./es-uninst |
The system displays this message.
2. Type n to not uninstall the Production Environment; in other words, type n to uninstall individual modules.
The system displays this message.
Do you want to uninstall Sun Fire Link [y|n|q] |
3. Type y beside the module if you do want to uninstall it and n beside the module if you do not want to uninstall it.
The system displays the module that will be uninstalled and this message.
Do you want to change selection? [y|n|q] |
The system displays your selections; go to the beginning of Step 3.
The system displays this message.
Proceed with uninstall? [y|n|q] |
5. Type y to proceed with the uninstall; or type n to not proceed with the uninstall.
If you type y to proceed, the system displays the list of packages to be uninstalled, the packages as they are uninstalled, the status of the uninstallation, and the location of the log file.
The es-start command requires different command arguments, depending on which component you are starting. Refer to the Sun Management Center 3.5 Installation and Configuration Guide for a list of the options for es-start. The -h option for es-start also lists all the options. The following procedure describes some common es-start options.
1. Log in as superuser on the machine where the components are to be started.
2. Change the directory to the /opt/SUNWsymon/sbin directory.
This example assumes that your software is in the default area /opt. If not, replace /opt with your own path.
# cd /opt/SUNWsymon/sbin |
On the system controller, start the Sun Management Center agents.
# ./es-start -al |
This command starts the base and platform agents. The platform agent provides all the Sun Fire 15K/12K, Sun Fire 6800, and Sun Fire Link system information to Sun Management Center software.
3. To start the Sun Management Center agent on a Sun Fire 15K/12K or Sun Fire 6800 domain with only the Sun Management Center agent layer installed, type:
# ./es-start -a |
4. To start all the Sun Management Center components on the Sun Management Center server host with all layers installed, type:
# ./es-start -A |
Note - Upon rebooting, all Sun Management Center agents start automatically. |
5. To start the console, type:
# ./es-start -c |
This section describes stopping and exiting Sun Management Center software.
The es-stop command requires different command arguments depending on which component you are stopping. Refer to the Sun Management Center 3.5 Installation and Configuration Guide for a list of the es-stop options. The -h option for es-stop also lists all the options. The following procedure describes some common es-stop options.
1. Log in as superuser on the machine where the components are to be stopped.
2. Change the directory to the /opt/SUNWsymon/sbin directory.
This example assumes that your software is in the default area /opt. If not, replace /opt with your own path.
# cd /opt/SUNWsymon/sbin |
3. To stop the server and agent components on the server machine, type:
# ./es-stop -Sa |
4. To stop the domain agent components on the host machine for a domain, type:
# ./es-stop -a |
5. On the system controller, to stop the host agent, which monitors the SC, and platform agent, type:
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.