C H A P T E R 2 |
Installation and Setup |
This chapter contains instructions for installing, setting up, and uninstalling Sun Fire midrange systems add-on software using the Sun Management Center Wizards. Refer to the Sun Management Center Installation and Configuration Guide for information about installing, setting up, uninstalling, starting, and stopping base Sun Management Center software.
![]() |
Caution - Use the installation scripts and the setup scripts provided with the Sun Management Center software. Do notmanually add packages or manually change configuration files. |
Your Sun Management Center installation and setup scripts or Wizard panels may not display exactly the same messages in exactly the same sequence as the examples shown in this supplement. However, these examples show the basic messages you will receive in approximately the sequence you will receive them. Your actual installation and setup scripts depend on the add-on components you choose to install and other choices you make.
See Using the CLI to Install, Set Up, Uninstall, Start, and Stop Sun Management Center Software for more information about how to perform these functions using the command-line interface (CLI).
TABLE 2-1 lists the Sun Fire midrange system-specific packages with the host they should be installed on, and the base layer they belong to.
You can install, set up, uninstall, and update Sun Management Center software in different ways, primarily using the Sun Management Center Wizards or the command-line interface (CLI). You might also need to perform certain other procedures if you want to use certain features. TABLE 2-2 lists the various procedures with a cross-reference to the information about them in this supplement.
Install software using the Sun Management Center Installation Wizard |
"Installing Sun Management Center on the Solaris Platform" in Chapter 6 of the Sun Management Center Installation and Configuration Guide |
Set up the Sun Fire midrange systems add-on software using the Setup Wizard |
Setting Up the Sun Fire Midrange Systems Add-On Software Using the Setup Wizard Using Advanced Wizard Setup Options "Setting Up Base Products and Add-ons on the Solaris Platform" in Chapter 6 of the Sun Management Center Installation and Configuration Guide |
Updating Multiple Hosts Using Agent Update Creating Agent Installation and Update Images" in Chapter 6 of the Sun Management Center Installation and Configuration Guide |
|
Creating and Setting Up a Sun Fire Midrange Systems Platform Agent Instance |
|
"Starting Components Using es-guistart" in Chapter 8 of the Sun Management Center Installation and Configuration Guide |
|
"Stopping Components Using es-guistop" in Chapter 8 of the Sun Management Center Installation and Configuration Guide |
|
"Uninstalling Sun Management Center" in Appendix A of the Sun Management Center Installation and Configuration Guide |
|
Appendix B of the Sun Management Center Installation and Configuration Guide |
|
Install Sun Fire midrange systems add-on packages using the CLI |
|
Set up Sun Fire midrange systems add-on packages using the CLI |
Setting Up the Sun Fire Midrange Systems Add-On Software Using the CLI |
FIGURE 2-1 shows a high-level view of the installation process.
If you are updating existing Sun Management Center 3.5 add-on software for Sun Fire midrange systems, you must:
Note - Before you start, be aware that you can use Agent Update to install Sun Management Center software on multiple agent hosts. For instructions about updating multiple hosts using agent update, see Updating Multiple Hosts Using Agent Update. |
See the following references depending on whether you are installing and setting up using the CLI or GUI:
Refer to Chapter 5 of the Sun Management Center Installation and Configuration Guide for detailed information about upgrading from Sun Management Center 3.0 software.
This section summarizes new installation and setup procedures for Sun Management Center 3.5 software on Sun Fire midrange systems:
For a new installation for this release:
1. Log in as superuser on the host machine.
2. Change the directory to the path/sbin directory, where path is the location of the Sun Management Center 3.5 CD or the disk copy of the CD.
3. Install the Sun Management Center base software using es-guiinst.
4. Change the directory to the path where you installed the base software in Step 3 (installed_directory/SUNWsymon/sbin).
5. Run the es-guiinst script again with a pointer to the path where you placed the Sun Fire midrange systems add-on software for Version 6. Use the disk1 image (addon_path/disk1/image).
You will see a list of add-on products that you can install.
6. Choose the add-on software that applies to Sun Fire midrange systems, and click Next.
|
1. From the SC, set up a logical IP address for the SC using the following command.
The system displays the following:
2. Enter the logical IP Address.
If you want to use the SC Failover capability, you must do the following before you install and set up the Sun Fire midrange systems add-on software:
You must then use that logical IP address when you set up the Sun Fire midrange systems add-on software.
|
1. Choose an unused IP address that begins with the same subnet address as both SCs.
For example, if one SC has an physical IP address of 129.146.235.14 and the other SC has a physical IP address of 129.146.235.41, the logical IP address would be 129.146.235.xxx, where xxx is an unused IP address within that subnet. For the example in Step 2, 129.146.235.251 is used as the logical IP address.
2. From the SC, set up a logical IP address for the SC using the following command.
The system displays the following:
3. Type yes to Enable SC Failover.
4. Type the logical IP address you chose in Step 1 (129.146.235.251 in our example).
5. Use this logical IP address to set up the platform agent during es-setup or es-guisetup.
Before you install and set up Sun Fire midrange systems add-on software, you must configure SNMP on the platform and the domain. This section contains both required procedures.
|
To configure SNMP on the platform, you can use telnet, ssh, or a direct connection to the console. This example uses the telnet command.
Note - Do not set up multiple Platform Administration Agents to manage the same Sun Fire midrange system controller. Doing so causes the system to run slowly or even hang. |
1. As superuser, access the system controller by using the telnet(1) command.
# telnet schostname System Controller schostname:SC> Type 0 for Platform Shell Type 1 for domain A Type 2 for domain B Type 3 for domain C Type 4 for domain D |
where schostname is the system controller host name.
2. At the system controller main menu, type 0 (or alternatively P or p) to enter the platform shell.
The platform shell prompt, schostname:SC, is displayed.
3. Type setupplatform -p snmp, and answer the questions.
Note - You must enter both the platform trap host here and the domain trap host in Step 4 in To Configure SNMP on a Domain for the platform administration module to monitor the domain state changes. You must also enter both a domain and platform trap host to refresh the data displayed in the Sun Management Center console. |
4. Type disconnect to disconnect from the platform shell and the telnet session.
|
To configure SNMP on the platform, you can use telnet, ssh, or a direct connection to the console. This example uses the telnet command.
1. As superuser, access the system controller by typing the telnet command.
where schostname is the system controller host name. In this example, domain A is chosen.
2. Enter a domain. Type 1, 2, 3, or 4 (or alternatively a, b, c, d, or A, B, C, D) to enter the proper domain shell.
Type 0 for Platform Shell Type 1 for domain A Type 2 for domain B Type 3 for domain C Type 4 for domain D Input: 1 Password: schostname:A> |
The domain shell prompt, schostname:X, is displayed, where X is the domain that you have chosen.
3. If the domain is active and the domain keyswitch is set to on, diag, or secure (you are running the Solaris Operating System, you are in OpenBoot PROM mode, or you are running POST), perform the following steps:
a. Press and hold the Control key while pressing the ] key, to return to the telnet> prompt.
b. At the telnet> prompt type send break.
4. Type setupdomain -p snmp, and answer the questions.
For Trap Hosts, enter the host name (or the IP address) of the Sun Management Center server from which you will perform platform administration.
Note - You must enter both the platform trap host in Step 3 in To Configure SNMP on the Platform and the domain trap host here for the platform administration module to monitor the domain state changes. You must enter both a domain and platform trap host to refresh the data displayed in the Sun Management Center console, as well. |
For Public and Private Community Strings, enter a different string for each domain and platform.
5. Type disconnect to exit the connection to the domain shell and the telnet session.
6. Repeat Step 1 through Step 5 for each additional domain, if any.
This section provides a summary of installing Sun Management Center base software and Sun Fire midrange systems add-on software using the Install Wizard. The Sun Management Center Installation and Configuration Guide describes in detail how to install all the software.
1. As superuser, run the es-guiinst script as described in Chapter 6, "Installation and Setup," of the Sun Management Center Installation and Configuration Guide.
2. After the base software is installed, the Select Add-on Product screen provides a selectable list of add-on products that you can install. Choose those add-on software items that apply to Sun Fire midrange systems, and click Next.
3. The Sun Management Center Setup Wizard starts automatically after all the software is installed.
This section describes how to set up the platform agent and the domain agent on Sun Fire midrange systems using the Sun Management Center Setup Wizard. For more details about the entire software setup process, refer to Chapter 6, "Installation and Setup," of the Sun Management Center Installation and Configuration Guide.
|
1. Set up the Sun Fire midrange systems Platform Agent on any machine where you have installed it.
Once the Sun Management Center base software setup is complete, the Wizard displays the following message:
Select Add-on Products The following add-on products are newly installed on this system and will be set up. - Sun Fire Platform Administration |
Select the Yes to set up only the server host.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message. Go to Step 27.
Select No to continue and set up all hosts. Go to Step 4.
The Sun Fire Midrange Systems Platform Agent Setup panel displays this screen:
If you do not want to set up the Platform Administration module, Select No, then go to Step 28.
To set up the Platform Administration module, select Yes.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following screen:
6. Enter a value for each prompt:
a. Type the host name or IP address of the System Controller (for example, 10.8.28.209).
![]() |
Caution - Only one SC can use a physical IP address. If you want to use the SC failover feature, you must put a logical IP address in this field. Both SCs can then use this logical IP address. If you do not put a logical IP address in this field and if an SC failover occurs, you receive a red alarm that the SCisnotresponding. For information about enabling SC failover and setting up a logical IP address, see To Enable the SC Failover Capability and Set Up a Logical IP Address. |
![]() |
Caution - If you set a logical IP address for the system controller, you must keep using a logical IP address for the SC, whether you are going to use the failover feature or not. |
b. Type the read community string for the platform (for example, P-public).
c. Type the write community string for the platform (for example, P-private).
A ping command is sent to the system controller IP address or host name that you entered.
a. If the ping command fails, you will see a Warning pop-up, with an option to continue:
The system controller at: IPaddress_or_hostname is not responding. The hostname or address may be invalid. Please press "Cancel" to change, or "OK" to continue with setup. |
b. If the ping command is successful or you choose to continue with setup, the Sun Fire Midrange Systems Platform Agent Setup panel displays the following screen:
8. Enter the domain write community strings.
a. Type the write community string for domain A, such as A-private
b. Type the write community string for domain B, such as B-private
c. Type the write community string for domain C, such as C-private
d. Type the write community string for domain D, such as D-private
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following screen:
10. (Optional) Enter the domain IP addresses or host names.
a. Type the IP address or host name of domain A, or leave blank.
b. Type the IP address or host name of domain B, or leave blank.
c. Type the IP address or host name of domain C, or leave blank.
d. Type the IP address or host name of domain D, or leave blank.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following screen:
12. Enter the domain agent ports.
a. Type the Sun Management Center agent port number on domain A.
b. Type the Sun Management Center agent port number on domain B.
c. Type the Sun Management Center agent port number on domain C.
d. Type the Sun Management Center agent port number on domain D.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message:
Updating configuration files with platform and domain information... Status: Updating configuration files... Update of configuration files complete. |
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message:
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message:
b. Enter 3800, 4800, 4810, 6800, E4900, or E6900 for the chassis model.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message:
Checking configuration files... Status: Set the platform server: <hostname> or <IPaddress> platform.snmpPort: 166 Default platform agent port: 166 Checking of configuration files complete. |
To use the default Sun Management Center platform agent port, select Yes.
If you do not want to use the default Sun Management Center platform agent port, select No.
The Sun Fire Midrange Systems Platform Agent Setup panel displays the following message:
20. Enter the platform agent port number you want to use.
If you prefer to choose a different (nondefault) port, select No. Go to Step 19.
To still use the default port, select Yes.
To regenerate the security keys now, select Yes; then go to Step 26.
If you prefer not to regenerate the security keys now, select No, then go to Step 27.
The Sun Fire Midrange Systems Platform Agent Setup panel displays this message:
Note - Ensure you store the seed password securely. It will be needed if you perform any modifications to your Sun Management Center installation. |
a. Enter a unique password for the seed if this is a first-time installation. If not, enter the seed used in previous versions of Sun Management Center.
b. Re-enter the seed to confirm.
The Sun Fire Midrange Systems Platform Agent Setup panel displays this message:
Updating configuration files with module and discover table information... Status: Added module.... Added module.... Updated Discovery Table.... Update of configuration files complete. |
The Sun Fire Midrange Systems Platform Agent Setup panel displays this message:
The Sun Fire Midrange Systems Platform Agent Setup panel displays this message:
The following products have been set up: - Sun Fire Platform Administration Click Next to invoke the Start Wizard now to the various Sun Management Center components. |
|
Set up the Sun Fire midrange systems Domain Agent on any Sun Fire midrange systems Domain where you have installed it.
1. Type es-guisetup on a Sun Fire midrange systems Domain where the domain agent is installed to start the Sun Management Center Setup Wizard.
Once the Sun Management Center base software setup is complete, the Wizard displays the following message:
2. Click Next to start the Domain Agent setup.
The Sun Fire Midrange Systems Domain Agent Setup panel displays the following message:
Updating configuration files... Status: Updating configuration files... Update of configuration files complete. |
The Sun Fire Midrange Systems Domain Agent Setup panel displays the following message:
The base Sun Management Center Setup Wizard provides these advanced setup options when the current Sun Management Center installation is already configured:
Note - Use the Reconfigure All option instead of the Remove Setup Configuration option at this time. |
Refer to the Sun Management Center Installation and Configuration Guide for more information about using these options.
This section describes how to update multiple hosts at once using Agent Update. The Agent Update process itself must be run on the Sun Management Center server machine. You must also ensure that Sun Management Center agents are running on all the target hosts.
You must create an Agent Update configuration file for the module on the target hosts before you run the Agent Update Process on the Sun Management Center server machine.
|
1. Ensure that the Sun Fire midrange systems Platform Administration module is installed on the target hosts.
2. Ensure that the Sun Fire midrange systems Platform Administration module is set up on the target hosts using either the es-setup or the es-guisetup script.
After this has been done, subsequent Platform Administration setup operations using Agent Update will work automatically, using the host-specific information provided initially.
Using the Agent Update process, you will create an Image File of the add-on components to be distributed to the target machines, and then add a New Job to the Manage Jobs Task list to be run at the time you specify.
Using Agent Update, you can update the configurations created by the following procedures:
|
This procedure applies only to updating from Sun Management Center 3.5 add-on software.
1. Create an Image File of the desired Sun Fire midrange systems add-on components to be distributed to the desired agent machines using one of the base Sun Management Center scripts es-gui-imagetool or es-imagetool.
Refer to Chapter 8, "Post-Installation Tasks," in the Sun Management Center Installation and Configuration Guide for detailed instructions about using either the GUI or the CLI Image Tool.
2. From your main Sun Management Center console window, choose the Manage Jobs... option from the Tools menu.
The system displays the Manage Jobs panel (see FIGURE 2-9), which allows you to distribute the Image File.
3. In the Manage Jobs panel, choose the New Task... button.
The system displays the New Task panel (see FIGURE 2-10), which allows you to specify the Agent Update Image File to distribute.
4. In the New Task panel (FIGURE 2-10), do the following:
a. Choose Agent Update for the Task Type.
b. Choose the Image File you created in Step 1.
5. In the Manage Jobs panel (FIGURE 2-9), do the following:
b. Choose the Task you created in Step 4.
c. Do one of the following to schedule when you want the Task to run:
d. Do one of the following to choose the objects (agent machines) to which you want to distribute the Image File:
e. Preview the objects (agent machines) you have chosen and redo your selections if necessary.
The job starts and distributes the Image File to the objects (agent machines) you chose. When the job is running, it appears in the Job list of the Manage Jobs panel. The panel shows the status of the job when running and when complete.
|
This procedure applies to either:
1. Log in as root on the Sun Management Center server machine.
2. Create an agent-update image using either of the image tools.
3. Download the file /opt/SUNWsymon/base/bin/agent-update.bin to each target machine's root directory.
If you installed Sun Management Center in a different directory than /opt, download /installdir/SUNWsymon/base/bin/agent-update.bin, where installdir is the install directory you specified.
4. Log in as root on the target machine.
5. Go to the directory where you downloaded agent-update.bin.
6. Type ./agent-update.bin -s server -r http-port -p image-name, where
7. Provide the security seed and the SNMPv1 community string.
The agent-update process prompts you for the security seed and the SNMPv1 community string.
The update process applies the update to the machine without prompting for further information.
When the update process completes, check the update status by viewing the log file /var/opt/SUNWsymon/log/agent-update.log on the server host.
Note - You must re-run ./es-setup -F to set up the platform agent. |
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.
4. To set up this instance, go the Step 3 in the procedure To Set Up a Sun Fire Midrange Systems Platform Administration Module for a New Platform Agent Instance
|
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.
a. Enter a new, not previously used port number.
Note - Be sure you use this port number when you set up this instance and when you create this platform instance object on the Sun Management Center console. |
The script asks for the security seed.
b. If you used a seed other than the default when setting up the Sun Management Center server, provide the same seed for this agent.
4. Stop the Sun Management Center agent process.
5. To set up this instance, go the Step 3 in the procedure To Set Up a Sun Fire Midrange Systems Platform Administration Module for a New Platform Agent Instance.
|
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.
Note - Before you perform Step 3, be sure you have stopped the Sun Management Center agent layer. To stop the agent layer, run the command /opt/SUNWsymon/sbin/es-stop -a. |
where instanceName is the name of a new platform agent instance.
The es-setup.sh script asks for this information:
This script can be run again to change the information provided in the previous setup.
4. To start the platform instance, go to the procedure To Start the Platform Instance.
5. After starting the platform instance, restart the agent daemon:
|
When the platform instance is set up, you can start it.
To start the platform instance, type:
|
If you need to stop the platform instance, type:
For information about how to undo setups and delete platform agents, see Undoing Setups and Deleting Platform Agents.
This section describes how to assign users to administrator and operator groups to give the users the type of access they will require to perform operations that are assigned to them.
|
If a user name is listed in the esusers file, that user can log onto that Sun Fire midrange system with read-only access for domain administration agents. In order to read and write platform or domain information under the platform agent, the 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 system 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.
a. Add Sun Fire midrange systems platform administrators to spltadm, to allow them to administer the platform through the platform view of a platform agent.
b. Add Sun Fire midrange systems domain administrators to the appropriate domain administrator group.
For example, adding the name of a domain administrator to sdaadm allows that domain administrator to administer domain A through the platform agent.
3. Add each user to the file /var/opt/SUNWsymon/cfg/esusers.
If you a particular Sun Fire midrange system no longer requires monitoring, you can save system resources by undoing the setup for the corresponding platform agent or instance, and then deleting it.
|
1. As superuser, stop the agent daemon.
For example, if Sun Management Center software is installed in /opt/SUNWsymon, the command looks like this:
2. Go to the path/addons/SunFirePltAdmin/sbin directory, where 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. Undo the setup for the default platform agent by typing:
For example, if Sun Management Center software is installed in /opt/SUNWsymon, the command looks like this:
|
1. As superuser, stop the agent daemon.
2. Go to the path/addons/SunFirePltAdmin/sbin directory, where path is the directory where the 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. Undo the setup for a specific platform agent instance by typing:
Note - Undoing this setup stops the Sun Management Center agent. |
|
1. Become superuser by using the su command.
2. Go to the directory path/sbin, where 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/sbin.
3. Delete the platform agent instance by typing:
The instructions in this document deal with two types of domains:
|
Sun Fire midrange systems come from the factory configured with one hardware domain, domain A. The system administrator has the option of creating additional hardware domains. A Sun Fire E6900 or 6800 system can have up to four hardware domains. A Sun Fire E4900, 4810, 4800, or 3800 system can have up to two hardware domains.
To create additional hardware domains on Sun Fire midrange systems, refer to the Sun Fire Midrange Systems Platform Administration Manual.
|
To create and populate an administrative domain, refer to the Sun Management Center User's Guide.
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.