Sun Fire Link Software Installation Guide for Sun Fire 15K/12K Systems
|
    |
| Sun Fire Link Software Installation Guide for Sun Fire 15K/12K Systems
|
|
|
Sun Fire Link Software Installation Guide |
This manual provides instructions for installing the software that supports the Sun FireTM Link high-performance cluster interconnect for the Sun Fire 15K/12K servers from Sun Microsystems, Inc.
This software includes the following components:
Management Center add-ons (install if planning to use Sun Management Center software to administer Sun Fire Link clusters)
Before installing the Sun Fire Link software, you need to perform the following procedures:
The Sun Fire Link Software Release Notes list the supported hardware configurations and the required versions of the SolarisTM operating environment and other related software. The release notes also describe open bugs and any workarounds there are for the bugs.
Install the Sun Fire Link hardware: Sun Fire Link I/O assemblies, optical cables, and Sun Fire Link switches (if used). For Sun Fire Link hardware installation instructions, see the documents listed in TABLE 1.
TABLE 2 identifies 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. Ensure that the host systems shown in TABLE 2 are available.
TABLE 3 identifies various dependencies that the Sun Fire Link software has on other software. Verify that these dependencies are satisfied.
|
Note - Some of the software listed in TABLE 3 may require patches. See the Sun Fire Link Release Notes for up-to-date patch information. |
|
Use a version of Java 1.2.2 that is later than Java 1.2.1_06 |
Load the Sun Fire Link CD-ROM on the server chosen to be the installation host. The server is used as an NFS server for the software installation. In the following example, install_host is the host name of this system.
1. Log in to the server and become superuser.
2. If the CD-ROM is not already inserted into this system, insert it now.
3. Check that the CD-ROM contents are visible.
install_host# cd /cdrom/sun-fire-link_1.1/ install_host# ls Docs Patches Product |
4. Add the following line to /etc/dfs/dfstab to support remote sharing of files.
If this file does not already exist, create it and add the following line to it.
share -o ro /cdrom/sun-fire-link_1.1/ |
5. Stop and restart the NFS daemons so the new share command takes effect.
install_host# /etc/init.d/nfs.server stop install_host# /etc/init.d/nfs.server start |
6. Verify that the CD-ROM is available for mounting by remote systems.
install_host# share - /cdrom/sun-fire-link_1.1/ ro "" |
The Sun Fire Link firmware is copied from the CD-ROM onto an FTP server or web server, from which it is flashed onto the boards and switches of the Sun Fire cluster.
The server can be any preconfigured FTP or web server, or you can configure the administration server to serve this purpose. Use your preferred method to configure an FTP server or web server. One simple method is to run the script documented in the Solaris man page for ftpd that creates an anonymous FTP server.
1. Find the ftp-script description on the ftpd man page and copy it to your chosen FTP server.
% man ftpd ... |
2. Add the anonymous ftp user name and password entry to the /etc/passwd file. For example:
ftp:x:30000:30000:Anonymous FTP:/export/anonymous-ftp:/nosuchshell |
3. Add the following line to the /etc/shadow file:
ftp:NP:6445:::::: |
4. As superuser, run ftp-script on the FTP server (named ftp_host in this example).
ftp_host# ftp-script /export/anonymous-ftp |
5. Create a directory on the FTP server to hold the Sun Fire Link firmware.
ftp_host# mkdir /export/anonymous-ftp/firmware |
6. On the FTP server, install the package that loads the switch firmware. The package name is SUNWwcsfi.
Assuming that the Sun Fire Link CD-ROM is inserted in the administration server and the FTP server is a different system, change directory to either the Solaris_8 or Solaris_9 directory and add the SUNWwcsfi package, as shown below.
For the Solaris 8 operating environment, enter:
ftp_host# cd /net/admin_host/cdrom/sun-fire-link_1.1/Product/Solaris_8 ftp_host# pkgadd -d . SUNWwcsfi |
For the Solaris 9 operating environment, enter:
ftp_host# cd /net/admin_host/cdrom/sun-fire-link_1.1/Product/Solaris_9 ftp_host# pkgadd -d . SUNWwcsfi |
7. Copy the Sun Fire Link switch firmware from its destination on the FTP server into the server's firmware directory.
Step 6 loaded the switch firmware into the /opt directory on the FTP server. This step makes it available for anonymous FTP access.
ftp_host# cp /opt/SUNWwcsfi/flash/SscApp.jflash /export/anonymous-ftp/firmware |
FIGURE 1 illustrates the sequence of procedures you perform to install the software components provided on the Sun Fire Link software distribution CD-ROM. Detailed instructions for these procedures follow.
Before configuring the switch SC and updating its firmware, ensure that the System Controllers in the node chassis have been configured and the firmware has been updated.
If your cluster configuration includes Sun Fire Link switches, you need to configure each switch system controller (SSC). If you did not perform this procedure at the time of installing the switch hardware, do so now.
1. Connect to the SSC (switch1 in this example) via the serial port.
For the requested password, enter the password that was specified as part of the switch installation procedure.
2. Use setupplatform to configure the SSC.
3. Assign the SSC's RMI password.
switch1:SSC> rmi_password Enter new password: Enter new password again: |
1. Update the firmware on the SSC from the flashupdate server you set up previously--either an FTP server or HTTP server.
The following example shows the update being done from an FTP server:
switch1:SSC> flashupdate -f ftp://ftp-server-ip/firmware/SscApp.jflash |
switch1:SSC> reboot |
Repeat these SSC configuration and firmware update procedures on the remaining Sun Fire Link switches.
When setting up domains in the Sun 15K/12K systems, configure some to include the I/O slots that contain Sun Fire Link link assemblies. These domains can then be included as nodes in the Sun Fire Link network
Perform an "Entire Distribution" installation of the Solaris operating environment onto the FM server, on each cluster node SC, and on each cluster domain. Also, apply any patches identified in the Sun Fire Link Release Notes.
The Solaris 8 and Solaris 9 operating environments require different versions of the SunVTS software.
The SunVTS packages, including those that support Sun Fire Link, are listed below. Install all packages on each domain of the Sun Fire Link cluster.
1. Insert the software supplement CD-ROM supplied with the Solaris 8 or Solaris 9 operating environment CD-ROM. This supplement CD-ROM contains the SunVTS core software packages.
2. Install the SunVTS core software:
For the Solaris 8 operating environment:
# cd $S8_BASEDIR/SUNWvts_4.6 # pkgadd -d . SUNWvts # pkgadd -d . SUNWvtsx |
where $S8_BASEDIR is the root directory for the SunVTS packages in the Solaris 8 path.
For the Solaris 9 operating environment:
# cd $S9_BASEDIR/SUNWvts_5.1 # pkgadd -d . SUNWvts # pkgadd -d . SUNWvtsx |
where $S9_BASEDIR is the root directory for the SunVTS packages in the Solaris 9 path.
3. Verify that the packages are installed.
For the Solaris 8 operating environment:
# pkginfo | grep SUNWvts system SUNWvts ... system SUNWvtsx ... |
For the Solaris 9 operating environment:
# pkginfo | grep SUNWvts system SUNWvts ... system SUNWvtsx ... |
4. Apply any patches identified in the Sun Fire Link Release Notes.
5. Repeat the SunVTS installation procedure on each domain of the Sun Fire Link cluster.
The next steps in the installation process depend on whether or not you are planning to use the Sun Management Center 3.0 PU4 software to administer Sun Fire Link clusters.
If you will be using version 3.0 PU4 of the Sun Management Center software, you must use a special script, called install, which is part of this release of the Sun Fire Link software. The primary purpose of this script is to make it possible for various add-on packages, including a set of Sun Fire Link add-ons to be installed and used with Sun Management Center 3.0 PU4 software.
However, install also installs and sets up all the Sun Fire Link software packages, both the basic packages and add-ons. This means, if you are going to use the install script for its adaptation purposes, you will not need to install and set up the Sun Fire Link packages by hand. The general process for using this approach consists of the following:
If you will not be using Sun Management Center software, you will need to install and set up the Sun Fire Link management software by hand, as described in Install the FM and FM Proxy Agent Software by Hand.
TABLE 4 identifies the various Sun Fire Link add-on packages, including localized packages that provide support for the console and FM server layers.
SUNWensfl |
||
|
Solaris 8 or 9 Packages[1] |
||
Install the General Availability (GA) version of the Sun Management Center 3.0 software as described in the Sun Management Center 3.0 Software Installation Guide.
Note that the Sun Management Center installation script, es-inst, changes various /etc/system entries to provide sufficient resources for database activities that the Sun Management Center software performs. These changes are shown in TABLE 5.
Refer to the Sun Fire Link Release Notes to see what patches may be required by the Sun Management Center software and apply any that are listed.
The images for the Sun Fire Link add-on packages that are supported by the install adapter script are contained in image/Addons/SunFireLink directory.
The procedure described below focuses on installing and setting up the SunFireLink add-on packages. However, the installation procedure is the same for all three groups of add-ons.
The usage for the install script is:
# install -h Usage: install [-S dir] [-h] where the options represent: S dir: dir is the location of the image to be installed. h : prints this usage report. |
After you start the install script, it will perform the adaptation tasks that allow the version 3.0 es-inst tool to install and set up the SunFireLink, Sun-Fire-15000, and SunFireLink add-on packages. Once those tasks are complete, install will start es-inst, which will manage the actual installation and setup operations. That's why you will see es-inst prompts at various points in the operation.
Before the script installs a set of packages, it checks to see if previous versions of the add-on packages are present. If so, it prints out a list of the packages that were found. In such cases, you must exit from the script and remove the earlier versions using pkgrm before continuing with the installation.
|
Caution - Do not use es-uninst to remove the previously installed add-on packages. The Sun Management Center 3.0 version of es-uninst may remove other packages you want to keep. |
1. Stop the Sun Management Center components.
# /opt/SUNWsymon/sbin/es-stop -A |
2. Go to the directory containing the install script and start the script.
Use the -S flag to specify the image source directory.
# cd /cdrom/sun-fire-link_1.1/Product/Sun_Management_Center_Sun_Fire_Supplements_5_03/adapter_script # ./install -S ../disk1/image |
3. Answer the installation and setup prompts.
For each set of component packages, es-inst will ask if you want to install that component. Install only those components that belong on the current system. Refer to TABLE 4 for guidance.
4. When the installation and setup process completes, the script will print the path to the installation log file and an "End of Installation" message.
5. Start the agents that were stopped in Step 1.
# /opt/SUNWsymon/sbin/es-start -A |
6. Apply any required RSM patches to all cluster node systems.
See the Sun Fire Link Release Notes for a list of required RSM patches.
8. Apply any required FM patches.
See the Sun Fire Link Release Notes for a list of required FM patches.
See TABLE 4 for a list of the localized Sun Fire Link add-on packages.
1. Stop the Sun Management Center agents.
# /opt/SUNWsymon/sbin/es-stop -A |
2. Go to the directory containing the install script and start the script.
Use the -S flag to specify the image source directory.
# cd /cdrom/sun-fire-link_1.1/Product/Sun_Management_Center_Sun_Fire_Supplements_5_03/adapter_script # ./install -S ../disk1/image |
3. Answer the installation prompts.
For each set of component packages, es-inst will ask if you want to install that component. Install only those components that belong on the current system. Refer to TABLE 4 for guidance.
4. When the install script completes the package installation phase, it will ask if you want to start the setup phase. Enter n to exit the script without starting the setup phase.
Do you want to run setup now? [y|n|q] n |
5. Install the localized Sun Fire Link common add-on packages on the agent layer.
# cd /cdrom/sun-fire-link_1.1/Product/Sun_Management_Center_Sun_Fire_Supplements_5_03/disk1/image/Addons/SunFireLink/Common/Basic # pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc |
6. Verify that the packages were successfully installed.
# pkginfo SUNWjsflc SUNWcsflc SUNWfsflc system SUNWcsflc ... system SUNWfsflc ... system SUNWjsflc ... |
7. Install the localized Sun Fire Link common packages and the localized packages support for the Sun Management Center/FM console and online help on the console layer.
# pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc SUNWjeswc SUNWceswc SUNWfeswc SUNWjwhlp SUNWcwhlp SUNWfwhlp |
8. Verify that the packages were successfully installed.
9. Install the localized Sun Fire Link common packages and the localized packages support for the Sun Management Center/FM server and online help on the server and FM layers.
# pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc SUNWjswsr SUNWcswsr SUNWfswsr SUNWjwhlp SUNWcwhlp SUNWfwhlp |
10. Verify that the packages were successfully installed.
11. Once all the localized add-on packages are installed, run the setup script.
# /opt/SUNWsymon/sbin/es-setup |
12. When the installation and setup process completes, the script will print the path to the installation log file and an "End of Installation" message.
13. Start the agents that were stopped in Step 1.
# /opt/SUNWsymon/sbin/es-start -A |
14. Apply RSM patches to all cluster node systems.
See the Sun Fire Link Release Notes for a list of required RSM patches.
16. Apply FM patches to the FM server.
See the Sun Fire Link Release Notes for a list of required FM patches.
The Sun Fire Link Manager consists of six packages, which are identified below. On each cluster domain, install the shared file package, the common jar file package, and the two proxy packages. On the FM server, install the shared file package, the common jar file package, and the Sun Fire Link root and user packages.
|
Sun Fire Link Manager Shared Files |
If you think one or more of these packages might have been previously installed, check the FM server and cluster domains to see if they are present. If so, remove them before performing the installation procedure described below.
Removal of the SUNWwcfmu package will usually stop any existing fabrics that are listed in the fabric base data directory, as indicated in the file /opt/SUNWwcfm/config/wcfm_base_data_dir.cfg on the FM server. This means you do not need to run /opt/SUNWwcfm/bin/killfabrics to clear any existing fabrics from the RMI registry.
|
|
1. On each RSM domain, become superuser and change directory to either the Solaris_8 or Solaris_9 location in the software distribution path.
For the Solaris 8 operating environment, enter:
# cd /cdrom/sun-fire-link_1.1/Product/Solaris_8 |
For the Solaris 9 operating environment, enter:
# cd /cdrom/sun-fire-link_1.1/Product/Solaris_9 |
2. Install the RSM proxy packages and the Sun Fire Link Manager shared files.
# pkgadd -d . SUNWwcfms # pkgadd -d . SUNWrsmpr # pkgadd -d . SUNWrsmpu # pkginfo | egrep "SUNWrsmp|SUNWwcfm" system SUNWrsmpr ... system SUNWrsmpu ... system SUNWwcfms ... |
3. On each RSM domain, set up the RSM proxies.
As superuser, run the script that sets up the RSM proxies.
# /opt/SUNWwrsmp/bin/wrsm_proxy_setup |
4. On each RSM domain, start the RSM proxies.
As superuser, run the script that starts the RSM proxies.
# /etc/init.d/wrsm_proxy start |
5. On each RSM domain, establish security settings for Sun Fire Link user access.
Add a group named sfladmin and add the appropriate 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.
1. On the FM server, become superuser and change directory to either the Solaris_8 or Solaris_9 location in the software distribution path.
For the Solaris 8 operating environment, enter:
fm_host# cd /cdrom/sun-fire-link_1.1/Product/Solaris_8 |
For the Solaris 9 operating environment, enter:
fm_host# cd /cdrom/sun-fire-link_1.1/Product/Solaris_9 |
2. Install the Sun Fire Link Manager packages.
fm_host# pkgadd -d . SUNWwcfms fm_host# pkgadd -d . SUNWwccmn fm_host# pkgadd -d . SUNWwcfmr fm_host# pkgadd -d . SUNWwcfmu fm_host# pkginfo | egrep "SUNWwcfm|SUNWwcc" ... |
The following procedure explains how to install the localized Sun Fire Link packages. See TABLE 4 for a complete list of the localized Sun Fire Link add-on packages.
1. Insert the Sun Fire Link CD-ROM.
2. Install the localized Sun Fire Link common add-on packages on the agent layer.
# cd /cdrom/sun-fire-link_1.1/Product/Sun_Management_Center_Sun_Fire_Supplements_5_03/disk1/image/Addons/SunFireLink/Common/Basic # pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc |
3. Verify that the packages were successfully installed.
# pkginfo SUNWjsflc SUNWcsflc SUNWfsflc system SUNWcsflc ... system SUNWfsflc ... system SUNWjsflc ... |
4. Install the localized Sun Fire Link common packages and the localized packages support for the Sun Management Center/FM console and online help on the console layer.
# pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc SUNWjeswc SUNWceswc SUNWfeswc SUNWjwhlp SUNWcwhlp SUNWfwhlp |
5. Verify that the packages were successfully installed.
6. Install the localized Sun Fire Link common packages and the localized packages support for the Sun Management Center/FM server and online help on the server and FM layers.
# pkgadd -d . SUNWjsflc SUNWcsflc SUNWfsflc SUNWjswsr SUNWcswsr SUNWfswsr SUNWjwhlp SUNWcwhlp SUNWfwhlp |
7. Verify that the packages were successfully installed.
1. As superuser, run the wcfm_setup script. Be prepared to supply a location for dynamically created files. For example:
2. On the FM server, establish security settings for Sun Fire Link users.
Add a group named sfladmin and add sfluser to this group.
c. Execute pwconv to update /etc/shadow.
d. Execute passwd to assign passwords to the new users.
After installing the Sun Fire Link software, the next step is to configure the RSM controllers. This can be done in two ways:
Both methods are described in the Sun Fire Link Fabric Administrator's Guide, which is provided as a PDF file on the Sun Fire Link CD-ROM.
After configuring the RSM controllers, you may wish to configure the DLPI interface to permit communication via the TCP/IP protocol. Use your preferred method, as on any other cluster interconnect.
| Sun Fire Link Software Installation Guide for Sun Fire 15K/12K Systems
|
817-2194-10 | |
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.
To