A P P E N D I X A |
Using the CLI to Install, Set Up, Uninstall, Start, and Stop Sun Management Center Software |
This appendix describes how to install, set up, uninstall, start, and stop Sun Management Center Software from the command-line interface (CLI). For more details, refer to the Sun Management Center Installation and Configuration Guide.
First ensure that the base Sun Management Center 3.5 software is installed on your system. Refer to the Sun Management Center Installation and Configuration Guide for instructions about installing this software.
Also ensure that any required patches are installed on your system.
|
1. To install only the Sun Fire midrnage add-on software, run the es-inst command in the sbin directory where the Sun Fire Midrange add-on software was installed.
The es-inst script prompts you for a source directory.
2. Enter the source directory.
Refer to the Sun Management Center Installation and Configuration Guide for more information about the es-inst command and its options.
3. If the general Sun Management Center 3.5 software package is already installed, and you are installing only the Sun Fire supplement software, enter n (for no) when you are prompted to begin the setup process.
![]() |
Caution - Entering y(for yes) may cause the loss of any customized setup information, such as security keys. |
4. Install the Sun Management Center 3.5 software package on any systems (agent machines) that you will use for platform administration on the Sun Fire midrange systems.
Read the Caution and Note in Step 2 above. The Domain Administration and Dynamic Reconfiguration add-on software must be installed on the server, console, and agent machines. (Note that you can install the Sun Fire midrange or high-end systems Platform Agents on any machine where you have Sun Management Center software running.)
The system displays the following message:
5. Type y for those products you want to install.
If you type y for all the add-on software, the system displays this message:
6. Type y to continue installing the add-on products.
Before setting up the agent and server layers, you must first set up the SC.
|
1. Enable the SC Failover Capability if you want to use it--See Enabling the SC Failover Capability.
2. Set Up SNMP on the System Controller--See Setting Up SNMP on the System Controller.
This section describes how to set up the agent and server layers.
|
If the agent machine has both server and agent layers, this procedure automatically sets up both layers.
1. Become superuser by using the su command.
2. Go to the PUn_path/addons/SunFirePltAdmin/sbin directory, where n is the number of the Platform Update, and PUn_path is the directory where Sun Management Center software is installed.
For example, if Sun Management Center software is installed in /opt/SUNWsymon, go to the directory /opt/SUNWsymon/addons/SunFirePltAdmin/sbin.
3. Run the es-setup.sh script.
To set up this module for the default platform agent instance, type:
The script asks for the following information:
A ping command is sent to the system controller IP address or host name that you entered. If the ping command fails, you will have the option of providing a different IP address or host name. If you prefer, you can continue without providing a new value:
Tip - This script can be run again to change the information provided in the previous setup. |
The Sun Management Center software ships with one platform agent named "platform."
When the module has been set up, you can start the appropriate agent. For more on how to start platform agents, see Starting Sun Management Center Software Using the CLI.
|
This procedure sets up only the server layer. To set up the server, agent, and console layers on a server, see To Set Up the Sun Fire Midrange Systems Platform Administration Module on an Agent Machine.
Note - If you chose to set up only the server layer (without a console or agent layer), user groups are not automatically added to the /etc/group file unless you use the -S option, as shown in this procedure. For a list of user groups, see TABLE A-1. |
1. Become superuser by using the su command.
2. Go to the PUn_path/addons/SunFirePltAdmin/sbin directory, where n is the number of the Platform Update, and PUn_path is the directory where Sun Management Center software is installed.
For example, if Sun Management Center software is installed in /opt/SUNWsymon, go to the directory /opt/SUNWsymon/addons/SunFirePltAdmin/sbin.
3. Run the es-setup.sh script with the -S option:
When the module has been set up, you can start the appropriate agent. The Sun Management Center software ships with one platform agent named "platform." For more on how to start platform agents, see Starting Sun Management Center Software Using the CLI.
The default platform administration module can monitor one Sun Fire midrange system. To monitor more than one Sun Fire midrange system, you must create one platform agent instance for each additional Sun Fire midrange system.
|
1. Become superuser by using the su command.
2. Go to the directory where Sun Management Center software is installed.
For example, if Sun Management Center software is installed in /opt/SUNWsymon, go to the directory /opt/SUNWsymon/sbin.
3. Run the es-platform script:
where instanceName is the name of a new platform agent instance.
This script asks for the port number for the new platform agent and the security seed. If you used a seed other than the default when setting up the Sun Management Center server, provide the same seed for this agent.
|
1. Become superuser by using the su command.
2. Go to the directory where Sun Management Center software is installed.
For example, if Sun Management Center software is installed in /opt/SUNWsymon, go to the directory /opt/SUNWsymon/addons/SunFirePltAdmin/sbin.
where instanceName is the name of a new platform agent instance.
The es-setup.sh script asks for the following information:
Note - This script can be run again to change the information provided in the previous setup. |
When the module has been set up, you can start the appropriate agent. For more on how to start platform agents, see Starting Sun Management Center Software Using the CLI.
|
If your user name is listed in the esusers file, you can log onto the Sun Fire midrange system with read-only access for domain administration agents. In order to read and/or write platform or domain information under the platform agent, your user name must also be listed in the group file on the server.
The setup procedure creates up to 10 groups on the Sun Fire midrange systems server machine. These groups are:
1. Become superuser by using the su command.
2. Add each user to the appropriate group in the file /etc/group.
3. Add each user to the file /var/opt/SUNWsymon/cfg/esusers.
|
|
2. Type y to set up the platform administration module, or type n not to set up the module now.
3. Type the IP address of the System Controller (for example, 10.8.28.209).
4. Type the read community for platform (for example, P-public).
5. Type the write community for platform (for example, P-private).
where X is the domain letter (A-D).
6. Type the write community for each domain (for example, use A-private for domainA).
When you have finished entering the write community for each domain, the system displays (in our example):
Please wait, Pinging the host 10.8.23.209. Host 10.8.38.209 is networked. Please wait, getting domain info from system controller Enter the Sun Management Center agent Port for domainX |
where X is the domain letter (A-R).
7. Type the agent port number for each domain (for example, use 161 for each domain).
When you have finished entering the agent port number for each domain, the system displays:
Updating the configuration, Please Wait... Done. .... .... .... Do you want to start Sun Management Center agent and server components now? [y|n|q] |
|
The system displays this message:
2. Type y to uninstall the 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] |
3. Type n not to change your selection.
The system displays the following message:
4. Type y to keep any existing topology and event data; or type n to discard the data.
The system displays the following message:
5. Type y to proceed with the uninstall, or type n not to 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 system displays this message:
2. Type n not to uninstall the Production Environment.
The system displays this message:
3. Type y beside each module you want to uninstall and n beside each module you do not want to uninstall.
The system displays the modules that will be uninstalled and the following message:
a. Type y to change your selection.
The system displays your selections; go to the beginning of Step 2.
b. Type n not to change your selections.
The system displays the following message:
5. Type y to proceed with the uninstall, or type n not to 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 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 procedures describe some common es-start options.
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Start the default platform agent by typing:
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Start a specific platform agent instance by typing:
For example, if P1 is the name of the platform agent instance, type:
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Start all Sun Management Center components, except the console, by typing:
The es-stop command requires different command arguments, depending on which component you are stopping. Refer to the Sun Management Center Installation and Configuration Guide for a list of the options for es-stop. The -h option for es-stop also lists all the options. The following procedures describe some common es-stop options.
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Stop the default platform agent by typing:
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Stop a specific platform agent instance by typing:
For example, if P1 is the name of the platform agent instance, type:
|
1. Become superuser by using the su command.
2. Go to the path/sbin directory, where path is the directory where the Sun Management Center software is installed.
3. Stop all Sun Management Center components, except the console, by typing:
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.