1 - C H A P T E R -

C H A P T E R 1

Preparation and Upgrading

This chapter describes the preparation necessary for installing the software that supports the Sun Fire Link high-performance cluster interconnect for the Sun Fire 15K/12K and Sun Fire 6800 servers.

This software includes the following components:

Node firmware

Switch firmware

Sun Fire Link Manager software

Sun Management Center 3.5 add-ons

SunVTS add-ons

This chapter also describes how to upgrade from Sun Management Center 3.0, Platform Update 4 (PU4), software to Sun Management Center 3.5 software. If you are doing a fresh installation using the Sun Management Center 3.5 Installation Wizard, see Chapter 3. If you are doing a fresh installation using the command-line interface, see Appendix A.

Preparing for the Installation

Before installing the Sun Fire Link software, you need to perform the following procedures:

To Read the Sun Fire Link Release Notes

To Install the Sun Fire Link Network Hardware

To Identify Your Target Systems

To Verify Required Software and Patches

To Read the Sun Fire Link Release Notes

Read the Sun Fire Link Release Notes, which lists the supported hardware configurations and the required versions of the Solaris Operating Environment and other related software, including software patches.

The release notes also describe open bugs and any workarounds there are for the bugs.

To Install the Sun Fire Link Network Hardware

Install the Sun Fire Link hardware assemblies: Sun Fire Link I/O assemblies, optical cables, and Sun Fire Link switches (if used).

For Sun Fire Link hardware installation instructions, see the following documents:

Sun Fire Link Hardware Installation Guide

Sun Fire Link Switch Installation and Service Manual

These documents are available in PDF format on the Sun Fire Link 1.1 CD-ROM that comes with your hardware or on the Web at:

http://www.sun.com/products-n-solutions/hardware/docs/Servers/ Cluster_Interconnects/Sun_Fire_Link/Hardware/index.html

Table showing locations of Sun Fire Link hardware installation instructions in PDF and HTML formats.

Note - The same documents apply to both Solaris 8 and Solaris 9 installations.

To Identify Your Target Systems

1. Use TABLE 1-1 to identify the various servers and other host systems that play some role in the Sun Fire Link software installation process.

Note that some roles can be performed by a single system.

2. Ensure that the host systems shown in TABLE 1-1 are available.


Role	Description	Requirements
Installation host	System on which to load the Sun Fire Link software CD-ROM	Shall be connected by TCP/IP network to all Sun Fire systems on which Sun Fire Link software will be installed Can, but need not, be a target for Sun Fire Link installation
FTP or web server	System to be used for updating the flash memory on boards in the Sun Fire systems and Sun Fire Link switches	Shall be connected by TCP/IP network to all Sun Fire systems that are also connected to the Sun Fire Link network Can, but need not, be an installation target for Sun Fire Link software
Sun Fire Link Manager server	System where the Sun Fire Link Fabric Manager (FM) software is to reside. When this system is also host to the Sun Management Center console, it is also referred to as the Sun Fire Link Management Station.	Shall be connected by TCP/IP network to all Sun Fire systems that are also connected to the Sun Fire Link network Shall be external to the Sun Fire Link network Can be the same system as the Sun Management Center server
Sun Management Center server	System where the Sun Management Center base software is to reside	Shall be connected by TCP/IP network to all Sun Fire systems that are also connected to the Sun Fire Link network Can be the same system as the FM server, or it can be a different system
Sun Management Center console	System where the Sun Management Center console is to run	Shall be connected by TCP/IP network to all Sun Fire systems that are also connected to the Sun Fire Link network. Can be the same system as the FM server and Sun Management Center server, or it can be a different system
Sun Fire system cluster compute nodes	Sun Fire systems that are to operate as Sun^TM Cluster or Sun HPC ClusterTools^TM platforms in a Sun Fire Link network	Shall be connected to both Sun Fire Link and TCP/IP networks
Sun Fire Link Switch System Controllers	System controller (SC) for the Sun Fire Link switch; its role is similar to system controllers in Sun Fire systems	Terminal or server shall be connected to the switch SC's serial port for configuring the SC and flash updating the switch firmware

To Verify Required Software and Patches

1. Use TABLE 1-2 to identify various dependencies that the Sun Fire Link 1.1 software has on other software.


Software	Sun Fire Link Dependency
Operating environments	Solaris 8, 2/02, Solaris 9, 12/02, or Solaris 9 4/03
RSM in Solaris 8	Incorporated in the Solaris 8 software distribution
RSM in Solaris 9	Incorporated in the Solaris 9 software distribution
Switch firmware	1.12.31
Sun Management Center base software and Sun Fire Link add-ons. Other add-ons depend on what machines you are using and what add-ons you have licensed.	3.5
Sun Fire 15K/12K System Management Services (SMS)	1.3
Sun Fire 6800 firmware	5.15.0
SunVTS for Solaris 8 2/02	4.6
SunVTS for Solaris 9 12/02	5.1 PS1
SunVTS for Solaris 9 4/03	5.1 PS2
Java Development Kit (JDK)	Sun Management Center server layer requires JDK 1.4+ Sun Management Center console layer requires JDK 1.3+ Sun Management Center agent layer, FM, and RSM proxy recommends JDK 1.2.2_10+^[1]

2. Refer to the Sun Fire Link 1.1 Release Notes for the list of software patch requirements. You can download the patches from SunSolve if they are not included on your CDs.

Instructions for Upgrading From Sun Fire Link 1.0 Software to Sun Fire Link 1.1 Software

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

Upgrading from Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5

Note - These instructions assume that the Sun Fire Link Manager server and the Sun Management Center server are the same. The instructions might be slightly different if the servers are different.

Things to consider:

If you do not plan to upgrade your RSM driver, you do not need to unconfigure the cluster to bring down the links.

If you do not want to preserve your existing cluster configuration, you can skip Steps 1, answer n in Step 5, skip Step 7, use a different data directory for Step 9, and skip Step 11.

If you do plan to preserve your existing cluster configuration, you need to follow all the steps. In addition, you need to know the current setup for the Fabric Management data directory. The file /opt/SUNWwcfm/config/wcfm_base_data_dir.cfg on the Sun Fire Link Manager server (<SFLM_server_name>) has the information for the data directory.

<SFLM_server_name># cat /opt/SUNWwcfm/config/wcfm_base_data_dir.cfg <FM_setup_directory>/SUNWwcfm/config

The <FM_setup_directory> is the directory path you need to enter for Step9b.

1. Before the upgrade:

a. List current configured fabrics:

<SFLM_server_name># /opt/SUNWwcfm/bin/listfabrics

b. Stop all fabrics (<fabric_name_1>, <fabric_name_2>, ....) only on the Sun Fire Link Manager server; do not delete fabrics.

<SFLM_server_name># /opt/SUNWwcfm/bin/stopfabric <fabric_name_1>

<SFLM_server_name># /opt/SUNWwcfm/bin/stopfabric <fabric_name_2>

....

2. Stop all Sun Management Center processes on all nodes and the Sun Management Center server.

a. To stop all the Sun Management Center processes on each node (<node_name-a>, <node_name-b>, ....):

<node_name-a># /opt/SUNWsymon/sbin/es-stop -a

<node_name-b># /opt/SUNWsymon/sbin/es-stop -a

....

b. To stop all the Sun Management Center processes on the Sun Management Center server (<SunMC_server_name>):

<SunMC_server_name># /opt/SUNWsymon/sbin/es-stop -Sa

3. Remove all Fabric Manager (FM) packages on all nodes and the Sun Fire Link Manager server using the pkgrm command.

a. To remove all FM packages on all nodes:

<node_name-a># pkgrm SUNWrsmpu SUNWrsmpr SUNWwcfms

<node_name-b># pkgrm SUNWrsmpu SUNWrsmpr SUNWwcfms

....

b. To remove all FM packages on the Sun Fire Link Manager server:

<SFLM_server_name># pkgrm SUNWwccmn SUNWwcfms SUNWwcfmu SUNWwcfmr

4. Uninstall Sun Management Center 3.0, Platform Update 4, software from the Sun Management Center server using es-uninst.

<SunMC_server_name># /opt/SUNWsymon/sbin/es-uninst

5. Be sure to type y for yes to the following question if you have kept the cluster configured and the links up, and you want to retrieve cluster information after the upgrade. Otherwise, type n for no.

If you are upgrading Sun Management Center, you may want to save your existing data.

Do you want to preserve your existing data [y|n|q] y

Will not remove the existing data.

6. Install the Sun Management Center 3.5 core and Sun Fire Link add-on software on the Sun Management Center server.

<SunMC_server_name># /opt/SUNWsymon/sbin/es-inst

7. Be sure to type y for yes to the following question if you answered yes in Step 5 to preserve your existing data. If you answered no in Step 5, you will not see this question.

Existing Sun Management Center Data detected.

Would you like to migrate your previous data [y|n|q] y

8. Set up the Sun Management Center 3.5 core and Sun Fire Link add-on software on the Sun Management Center server.

<SunMC_server_name># /opt/SUNWsymon/sbin/es-setup

9. During the setup of the Sun Fire Link add-on module, use the original Fabric Manager data directory that you set before you began the upgrade.

Do you want to import your previous data [y|n|q] y

....

Enter a NON EXISTING Data Directory for the Sun Fire Link Manager (Suggested location is a new subdirectory of /var/opt/): /var/opt/<subdirectory_name>

a. Type y for yes to the question "Do you want to import your previous data?"

b. Enter the directory name that you set up previously (<FM_setup_directory>).

10. Use the Agent Update feature to install Sun Management Center 3.5 software on all nodes.

For more information about using Agent Update, see Chapter 4.

a. Create an image file using /opt/SUNWsymon/sbin/es-imagetool or /opt/SUNWsymon/sbin/es-gui-imagetool on the Sun Management Center server.

<SunMC_server_name># /opt/SUNWsymon/sbin/es-imagetool

i. Type y for yes to the following questions when prompted while running es-imagetool:

Do you want to upgrade components of Base Agent [y|n|q] y

Do you want to install/upgrade components of Addons [y|n|q] y

ii. You are prompted to enter an image name while running es-imagetool. Remember the image name (<image-name>) you enter, because you need it again in Step 10d.

Enter image name : <image-name>

b. Copy /opt/SUNWsymon/base/bin/agent-update.bin from the Sun Management Center server to a temporary directory on each of your agent nodes (any directory is okay).

You can use the remote copy command (rcp) to remotely copy agent-update.bin from the Sun Management Center server to the agent nodes.

<node_name-a># rcp <SunMC_server_name>:/opt/SUNWsymon/base/bin/agent-update.bin <temp_directory>

<node_name-b># rcp <SunMC_server_name>:/opt/SUNWsymon/base/bin/agent-update.bin <temp_directory>

....

c. Run the following command on each agent node:

<node_name-a># <directory_on_agent_machine>/agent-update.bin -s <SunMC_server_name> -r <http_port> -p <image-name>

<node_name-b># <directory_on_agent_machine>/agent-update.bin -s <SunMC_server_name> -r <http_port> -p <image-name>

....

The default http port (<http_port>) is 8080. The image name (<image-name>) is the same one you entered in Step10bii.

11. After the completion of the Agent Update, start the fabrics on the Sun Fire Link Manager server.

<SFLM_server_name># /opt/SUNWwcfm/bin/startfabric <fabric_name_1>

<SFLM_server_name># /opt/SUNWwcfm/bin/startfabric <fabric_name_2>

....

^{1 (TableFootnote) The FM and the proxy JDK versions should match to avoid problems. If you choose to run JDK 1.3 for the proxies, use this same JDK for the FM.}