Chapter 3 Documentation Issues

This chapter describes known documentation problems. The information included in these Release Notes supersedes the information in the Sun Management Center Release Notes on the Sun Management Center 3.5 Software 2 of 2 CD. The Sun Management Center 3.5 Release Notes can be found in the Sun Management Center 3.5 Software Collection on http://docs.sun.com.

The following documentation errata have been added to this chapter since this document was published on the Sun Management Center 3.5 Software 2 of 2 CD.

• Documentation Affected: Chapter 1 in Sun Management Center 3.5 Installation and Configuration Guide

• Document Affected: Chapter 1 in Sun Management Center 3.5 Supplement for Netra Servers, Japanese Version

• Document Affected: Page 81 in Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide

Documentation Errata

Documentation Affected: Chapter 1 in Sun Management Center 3.5 Installation and Configuration Guide

The Sun Management Center 3.5 documentation is available at http://docs.sun.com and on disk 2 of the product media. To read the documentation from the media, follow these steps:

1. Open a web browser window.

2. From the web browser window, open the /cdrom/cdrom0/image/index.html file, which is located on disk 2.

3. Follow the appropriate links to access HTML or PDF documentation in your preferred language.

To install the documentation from the media, use the pkgadd command to install the packages located in the following directory on disk 2:

/cdrom/cdrom0/image/PE/CommonForSolaris/Basic

Document Affected: Appendix E in Sun Management Center 3.5 Installation and Configuration Guide

The following tables list localization packages that were not included in Appendix E of the Sun Management Center 3.5 Installation and Configuration Guide.

Document Affected: “Sun Management Center Post-Installation Tasks” in Sun Management Center 3.5 Installation and Configuration Guide

The current description of the esadm security group in the post-installation section of the Sun Management Center 3.5 Installation and Configuration Guide mentions that esadm permits members to create top-level domains in a server context and assign privileges for other Sun Management Center users within these domains. The esadm security group does not provide the stated privileges: esadm users cannot create top-level domains and assign privileges within said domains.

Document Affected: “To Remove T3 Device Configuration” in Sun Management Center 3.5 Installation and Configuration Guide

The title of the section, To Remove T3 Device Configuration, located in the“Preparing Systems for Sun Management Center Upgrade and Installation” in Sun Management Center 3.5 Installation and Configuration Guide has been changed. The procedural information has also changed. The following is the updated procedure:

Uninstalling T3 Storage Devices

If you are running Sun Management Center 3.5, you must remove the T3 device configuration from Sun Management Center 3.5 if you are going to perform any of the following functions:

• Remove the T3 storage device.

• Move the T3 storage device to another machine.

• Assign a different IP or Ethernet address to the T3 storage device.

• Migrate the Sun Management Center server to a different machine.

• Uninstall the Monitoring and Management of A5x00 and T3 Devices add-on product.

• Uninstall Sun Management Center 3.5

If you uninstall the Monitoring and Management of A5x00 and T3 Devices add-on product without first removing the T3 device configuration, you can remove the T3 device configuration as described in the following procedure.

To Remove T3 Device Configuration

1. Log in as root on the machine where the Monitoring and Management of A5x00 and T3 Devices add-on product is installed.

2. Type the command /opt/SUNWsymon/es-stop -a to stop the Sun Management Center agent.

3. Run the pre-uninstall script to remove T3 device configuration information.

   1. Type the command /opt/SUNWsymon/addons/storage/sbin/pre-uninst.sh.

   2. When asked if you want to stop the T3 from sending syslog messages, type y.

   3. You are then prompted for the root password for the T3 device. Type the password.

      You are notified that the T3 device has been removed from the T3 module.

4. Uninstall the add-on product.

   See “To Uninstall Sun Management Center 3.5 Using” in Sun Management Center 3.5 Installation and Configuration Guide.

Document Affected: “Sun StorEdge A500 Patches” in Sun Management Center 3.5 Installation and Configuration Guide

The title and description for the Sun StorEdge^TMA5x00 Packages detailed in the “Preparing Systems for Sun Management Center Upgrade and Installation” in Sun Management Center 3.5 Installation and Configuration Guide The correct title is Sun StorEdge A5x00 Packages.

The following is the correct description for the Sun StorEdge A5x00 Packages:

If you want to use the Sun StorEdge A5x00 module, you must install the SUNWluxop and SUNWluxox packages on the system where you install the Monitoring and Management of A5x00 and T3 Devices add-on product. If you load the A5x00 module, and the packages are not installed on the system, the Sun Management Center agent cannot run.

To check whether the packages are installed, type the following command:

# pkginfo SUNWluxop SUNWluxox

If the packages are installed, the following lines are displayed:

system  SUNWluxop  Sun Enterprise Network Array firmware and utilities
system  SUNWluxox  Sun Enterprise Network Array libraries (64-bit)

If you need either package, you can download the package from http://sunsolve.sun.com. Make sure that you download the latest revision. Use the pkgadd(1M) command to install the packages.

Document Affected: Page 81 in Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide

Page 81 in the Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide incorrectly describes the Start Time field of the test schedule form as running on a 12–hour clock format, with a.m. and p.m. designations. This field is actually expressed in a 24–hour clock format.

Document Affected: “Package Name for English-Language Help File” in Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide

Chapter 1 of the Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide incorrectly lists the package name for the English-language help file as SUNWedh. The correct package name is SUNWenedh.

The following is a list of the help files and properties files for each locale:

• English: SUNWenedh, SUNWenedp

• Simplified Chinese: SUNWcedh, SUNWhedp

• Traditional Chinese: SUNWhedh, SUNWhedp

• French: SUNWfredh, SUNWfredp

• Japanese: SUNWjaedh, SUNWjaedp

• Korean: SUNWkoedh, SUNWkoedp

Document Affected: “Installing Localized Version” in Sun Management Center 3.5 Supplement for VSP High-End Entry Servers (Workgroup Servers)

Page 11 of the Sun Management Center 3.5 Supplement for VSP High-End Entry Servers (Workgroup Servers) Guide inaccurately refers to information in the Sun Management Center 3.5 Installation and Configuration Guide about installing the new localization packages.

The Sun Management Center 3.5 Installation and Configuration Guide does not contain information about installing new localization packages. The following revised text refers to the appropriate information in the Sun Management Center 3.5 Installation and Configuration Guide:

During installation, you are given the option to select additional languages for online help and support files.

Document Affected: “Installing Localized Version” in Sun Management Center 3.5 Supplement for Workstations

Page 8 of the Sun Management Center 3.5 Supplement for Workstations inaccurately refers to information in the Sun Management Center 3.5 Installation and Configuration Guide about installing the new localization packages.

The Sun Management Center 3.5 Installation and Configuration Guide does not contain information about installing new localization packages. The following revised text refers to the appropriate information in the Sun Management Center 3.5 Installation and Configuration Guide:

During installation, you are given the option to select additional languages for online help and support files.

Documents Affected: Only PDF File Format Available for French, Japanese, Korean, Simplified Chinese, and Traditional Chinese Supplemental Documentation

The following French (FR), Japanese (JA), Korean (KO), Simplified Chinese (ZH) and Traditional Chinese (ZH_ZW) supplemental documentation for Sun Management Center 3.5 is provided in only PDF file format:

• Sun Management Center 3.5 Supplement for Netra Servers

• Sun Fire Link Software Installation Guide (for Sun Management Center 3.5)

• Sun Management Center 3.5 Supplement for VSP High-End Entry Servers (Workgroup Servers)

• Sun Management Center 3.5 Supplement for Workstations

• Sun Management Center 3.5 Supplement for Sun Fire 15K/12K Systems

• Sun Management Center 3.5 Supplement for StarFire Servers

• Sun Management Center 3.5 Supplement for Sun Enterprise 6500/5500/4500/3500 Systems

• Sun Management Center 3.5 Supplement for Sun Fire 6800/4810/4800/3800 Systems

Document Affected: Chapter 1 in Sun Management Center 3.5 Supplement for Netra Servers, Japanese Version

The following table lists localization packages that were excluded from Chapter 1 of the Japanese version of the Sun Management Center 3.5 Supplement for Netra Servers.

Do not use the pkgadd command to install these packages. Instead, use the installation scripts, as described in Chapter 3 of the Sun Management Center 3.5 Supplement for Netra Servers.

Document Affected: “Uninstalling Software Using the CLI” in Sun Management Center 3.5 Supplement for Sun Fire 15K/12K Systems

The note at the beginning of the section on page 47, “Uninstalling Software Using the CLI,” in the Sun Management Center 3.5 Supplement for Sun Fire 15K/12K Systems erroneously states that you need to rerun the ./es-setup -F command to set up the platform agent. You do not need perform this step.

Document Affected: “Sun Fire Link Administration Overview” in Sun Fire Link Fabric Administrator's Guide

The following section, "Guidelines for Configuring Clusters With Sun Fire Link 1.1 Software," was omitted from Chapter 1, at the end of the section entitled, "Sun Fire Link Administration Overview". This additional information is important to understand and consider when configuring clusters with Sun Fire^TM Link (SFL) 1.1 software.

Guidelines for Configuring Clusters With Sun Fire Link 1.1 Software.

• Managing Cluster Configurations.

  Use a consistent method for Managing cluster configurations. If you use the Sun Management Center 3.5 graphical user interface (GUI) to configure a cluster, you should continue using the GUI for any subsequent changes that you make to the cluster's configuration. Do not use the Fabric Manager command-line interface (CLI) to change the configuration data for a cluster that was created using the GUI.

  Likewise, use the Fabric Manager CLI to change the contents of a cluster that was originally configured using the same interface. This consistency ensures that link mapping remains consistent over the life of the cluster.

  ---

  Note –

  You can monitor a cluster's state by using either the Sun Management Center 3.5 GUI or the Fabric Manager CLI, regardless of which method was used to configure the cluster.

  ---

• Using an Extended Markup Language (XML) File to Apply Multiple Changes to a Fabric Might Result in Out-of-Sync Configuration Data.

  If you use an XML file to apply multiple configuration changes to an existing fabric, any error in the XML file will cause the reconfiguration to fail. There is a possibility that one or more nodes will have data that are out of sync with the new configuration. This failure will also happen if a hardware component that is required by the new configuration is faulty at the time the reconfiguration is attempted.

  There are two ways to restore configuration consistency on the nodes:

  • If there was an error in the XML file, edit the file to correct the error. Reconfigure the fabric using the corrected file. If a hardware component was faulty, replace the component. Reconfigure the fabric using the XML file.

  • Remove the section of the XML file that produces the error and reconfigure the fabric using the modified XML file.

  In either case, a reconfiguration using a valid XML file and healthy hardware will correct any data inconsistencies that might have been introduced by the previous reconfiguration failure.

• Mixed Clusters Require That Sun Fire Link 1.1 Software Be Installed on the Fabric Manager Server and on All Nodes.

  If you want to configure a cluster that contains a combination of Sun Fire 6800 and Sun Fire 15K/12K systems, you must have Sun Fire Link 1.1 software installed on the FM server, as well as on all nodes in the cluster. Clusters containing both Sun Fire 6800 and Sun Fire 15K/12K nodes were not supported by Sun Fire Link 1.0 software.

Document Affected: Appendix B, “Importing Preconfigured XML Files Using the Manage XML Configurations Option” in Sun Fire Link Fabric Administrator's Guide (4841740)

The following are detailed instructions for importing preconfigured XML files using the Manage XML Configurations option. These instructions were omitted from Appendix B of the Sun Fire Link Fabric Administrator's Guide.

The Sun Management Center console's Fabric Details window includes the Manage XML Configurations menu option. You can use this option to open an XML file for editing or to apply any configuration information the file contains to an unconfigured fabric.

The term unconfigured fabric refers to a fabric that has been created and started, but does not yet contain any member data, such as descriptions of compute nodes.

An XML file can be opened for editing without being associated with an unconfigured fabric. However, if the file will be used to configure a fabric, that fabric must first be created and started.

The following steps explain how to use the Manage XML Configurations option:

1. Prior to using the Manage XML Configuration option, you must create and start a fabric, using the Fabric Manager (FM) CLI commands, createfabric and startfabric.

   ---

   Note –

   You must be superuser to execute the following FM commands.

   ---

   # cd /opt/SUNWwcfm/bin

   # ./createfabric fabric-name

   # ./startfabric fabric-name

2. Use the Sun Management Center console to load a FM agent module for the fabric. The Loading FM Agent Modules discussion in the Sun Fire Link Fabric Administrator's Guide provides detailed instructions for this step.

3. In the Fabric Details window, press mouse button 3 on the fabric icon. Select the Manage XML Configurations option from the pop-up menu that is displayed, or choose the Fabric Menu item Manage XML Configurations.

   At this point, the following invalid error message is displayed:

   Getting FM Info Values

   This error message can be safely ignored.

4. Press the OK button on the Error dialog window.

   Pressing the OK button closes the Error window. The XML Configuration dialog box is now the active window.

5. In the Look In field of the Configuration dialog window, enter the full path of the directory that contains the XML configuration file that you want to import. Press Return.

   A scrolling list of the files that are contained in the specified directory are displayed in the window.

6. Select the XML configuration file you want to import. The name of the file is displayed in the File Name field.

   ---

   Note –

   You must press Return in Step 5 and then select the XML file of interest as described in Step 6. Do not bypass these steps and manually enter the file name in the File Name field. The file will not open if you manually enter the file name.

   ---

7. Click Open to open the selected file.

   This displays the XML configuration file in the text area of the window.

8. Choose one of the following options:

   • You can edit the XML file. Refer to Appendices B and C of the Sun Fire Link Fabric Administrator's Guide for specific information about XML file configurations and the Document Type Definition (DTD).

   • If you want to apply the XML information to configure a fabric, proceed to the next step.

   • If you want to save your changes as a new XML file, click the Save As button. Enter a new filename.

9. Click Configure to apply the XML file contents to the fabric.

For more information, see Manage Extended Markup Language (XML) Configurations Option Produces an Invalid Error Message When Applying an XML File to a New Fabric (4855354).

Document Affected: Steps 3a and 3b in “Upgrading From Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5” in Sun Fire Link Software Installation Guide

The following two changes apply to page 7, Steps 3a and 3b, in the Sun Fire Link Software Installation Guide:

• Step 3a – The existing sentence should be replaced with the following sentence:

  Remove all RSM proxy packages on all nodes:

• Step 3b – The existing information should be replaced with the following:

  Remove all FM packages on the Sun Fire Link Manager server:

  SFLM–server–name# pkgrm SUNWwcfmu SUNWwcfmr SUNWwcfms WUNWwccmn

Document Affected: “Upgrading From Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5” in Sun Fire Link Software Installation Guide

The instructions on page 5 of the Sun Fire Link Software Installation Guide assume that the Sun Fire Link Manager server and the Sun Management Center server are the same server. The instructions for performing an upgrade on two different servers might vary slightly.

The following main points distinguish the differences between an upgrade on separate Sun Management Center and Sun Fire Link (Fabric Manager) servers, and an upgrade on a combined server for Sun Management Center and Fabric Manager (FM):

• If you have separate Sun Management Center and FM servers, you need to install different Sun Fire Link add-on packages on each server.

• If you have separate Sun Management Center and FM servers, you need to install the Sun Management Center server component on the Sun Management Center server. You also need to install the Sun Management Center agent component on the FM server.

The following instructions and examples outline how to perform an upgrade on two different servers:

1. On the Sun Management Center server, the only optional Sun Fire Link add-on components you need to install are the Sun Fire Link Server and the Sun Fire Link Console. See the following example.

   ---

   Example 3–1 Sun Management Center Server Sun Fire Link Add-On Components

   
   

   Select the products you want to install: ... Sun Fire Link (y|n|q) y This product has the following optional components: Sun Fire Link Server Select for install (y|n|q) y Sun Fire Link Manager Select for install (y|n|q) n Sun Fire Link Switch Select for install (y|n|q) n Sun Fire Link Cluster Node Select for install (y|n|q) n Sun Fire Link Console Select for install (y|n|q) y

   ---

2. On the FM server, the only optional Sun Fire Link add-on components you need to install are the Sun Fire Link Manager and the Sun Fire Link Switch. See the following example.

   ---

   Example 3–2 Fabric Manager Server Sun Fire Link Add-On Components

   
   

   Select the products you want to install: ... Sun Fire Link (y|n|q) y This product has the following optional components: Sun Fire Link Manager Select for install (y|n|q) y Sun Fire Link Switch Select for install (y|n|q) y Sun Fire Link Cluster Node Select for install (y|n|q) n

   ---

3. On the Sun Management Center server, refer to the following example for the correct responses during installation.

   ---

   Example 3–3 Sun Management Center Server Components

   
   

   Select the Sun Management Center components to install: 3 component(s) are available for your selection: Do you want to install the Server component (y|n|q) y Note: The Agent component will be installed automatically. Do you want to install the Console component (y|n|q) y

   ---

4. On the FM server, refer to following example for the correct responses during installation.

   ---

   Example 3–4 Fabric Manager Server Components

   
   

   Select the Sun Management Center components to install: 3 component(s) are available for your selection: Do you want to install the Server component (y|n|q) n Do you want to install the Agent component (y|n|q) y Do you want to install the Console component (y|n|q) n

   ---

Document Affected: “Upgrading From Sun Fire Link 1.0 Software to Sun Fire Link 1.1 Software” in Sun Fire Link Software Installation Guide

Step 2 of the “Upgrading From Sun Fire Link 1.0 Software to Sun Fire Link 1.1 Software” instructions, located on pages 5 and 75 in the Sun Fire Link Software Installation Guide, has been replaced with Step 2 and Step 3. The following are the revised steps:

• Step 2 – Remove the Remote Shared Memory (RSM) packages from each cluster node.

  # pkgrm SUNWrsmpu SUNWrsmpr SUNWwcfms

• Step 3 – Remove the Fabric Manager (FM) packages from the FM server.

  # pkgrm SUNWwcfmu SUNWwcfmr SUNWwcfms SUNWwccmn

Document Affected: Table 3–1, “Installation Location,” in Sun Fire Link Software Installation Guide

Entries that are included under the heading, “Installation Location,” in Table 3–1, located on pages 32–33 of the Sun Fire Link Software Installation Guide, are inaccurate. The following revised information should be included under this heading:

• The Sun Fire Link Manager server is the same as the FM Host.

• The package SUNWwcfms also resides on the RSM domains, and it is not needed on the Sun Management Center server.

• The packages SUNWwcfmr and SUNWwcfmu reside on the Sun Fire Link Manager server (FM Host). These packages are not needed on the Sun Management Center server.

Document Affected: "Setting Up the Sun Fire Link Add-On Software Using the Sun Management Center 3.5 Setup Wizard" in Sun Fire Link Software Installation Guide

The following replaces the current information on page 36, "Setting Up the Sun Fire Link Add-On Software Using the Sun Management Center 3.5 Setup Wizard," in the Sun Fire Link Software Installation Guide:

• Sun Fire Link Manager (Fabric Manager)

• Sun Fire Link Cluster Node

• Sun Fire Link Console

• Sun Fire Link Switch, FM, and RSM Agents

• Sun Fire Link Server

Generally, you would not be setting up all the components at once.

Document Affected: "Install, Set Up, and Uninstall Sun Management Center 3.5 Software Using the CLI" in Sun Fire Link Software Installation Guide

The following replaces the current information on page 74, "Install, Set Up, and Uninstall Sun Management Center 3.5 Software Using the CLI," in the Sun Fire Link Software Installation Guide:

These add-on components need to be installed on various systems:

• Sun Fire Link Manager (Fabric Manager)

• Sun Fire Link Cluster Node

• Sun Fire Link Console

• Sun Fire Link Switch, FM, and RSM Agents

• Sun Fire Link Server

The Sun Fire Link Manager (Fabric Manager), Sun Fire Link Console, and Sun Fire Link Server might be filled by the same system or by two or three different systems.

Document Affected: “Creating an Agent Update Image for Sun Fire Link” in Sun Fire Link Software Installation Guide

The second paragraph on page 62 of the section, “Creating an Agent Update Image for Sun Fire Link,” in the Sun Fire Link Software Installation Guide contains inaccurate information about the Sun Management Center 3.5 limitation.

The Sun Management Center 3.5 limitation no longer applies. All component setup questions will not be asked when you select a single component.

Documents Affected: “Uninstalling Sun Management Center 3.5 Software” in Sun Fire Link Software Installation Guide, Sun Management 3.5 Supplement for Sun Fire 15K/12K Systems, Sun Management Center 3.5 Supplement for 6800/4810/4800/3800 Systems, Sun Management Center 3.5 Supplement for Starfire Servers, and Sun Management Center 3.5 Supplement for Sun Enterprise 6500/5500/4500/3500 Servers

Both the Sun Management Center 3.5 GUI Uninstall Wizard, es-guiuninst, and the CLI uninstall script, es-uninst, allow you to uninstall the following software:

• All the Sun Management Center software

• Individual add-on software components

All references to uninstalling add-on modules in the “Uninstalling Sun Management Center 3.5 Software” section of the following add-on supplements should be replaced with the words, add-on products:

• Sun Fire Link Software Installation Guide

• Sun Management 3.5 Supplement for Sun Fire 15K/12K Systems

• Sun Management Center 3.5 Supplement for 6800/4810/4800/3800 Systems

• Sun Management Center 3.5 Supplement for Starfire Servers

• Sun Management Center 3.5 Supplement for Sun Enterprise 6500/5500/4500/3500 Servers

You can uninstall each separate add-on product, such as Sun Fire Link. However, you cannot uninstall the individual modules that comprise the add-on product, such as the Sun Fire Link FM Agent Module or the Sun Fire Link Switch Agent Module.

Refer to Appendix A, “Uninstalling Sun Management Center 3.5,”on page 191, in the Sun Management Center 3.5 Installation and Configuration Guide, for detailed instructions and options for using the GUI Uninstall Wizard, es-guiuninst.

Refer to Appendix B, on page 195, in the Sun Management Center 3.5 Installation and Configuration Guide for detailed instructions and options for using the CLI uninstall script, es-uninst.