Chapter 4 Documentation Issues

This chapter describes documentation errors and omissions. Bug numbers are shown in parentheses.

Sun Management Center 3.5 Update 1 Supplement Issue

“Support for New Hardware Products” Section

The “Support for New Hardware Products” section in the Sun Management Center 3.5 Update 1 Supplement (Chapter 1, page 10) had incomplete information. The UltraSPARC® IV CPU board support applies to the Sun Fire 6800/4800, Sun Fire V1280, and Netra 1280 systems. If you install the UltraSPARC IV CPU/Memory board upgrade in a Sun Fire V1280 or Netra 1280 system, you must install the following:

• Midrange systems firmware 5.17.0

• Netra-T Add-on packages for Sun Management Center 3.5 Update 1

The Sun Fire V1280 and Netra 1280 systems are also called the Sun Fire entry-level midrange systems.

“Upgrade Path 3.5 to 3.5 Update 1” Section

This information was omitted from the “Upgrade Path from 3.5 to 3.5 Update 1” section in the Sun Management Center 3.5 Update 1 Supplement: When you upgrade to Sun Management Center 3.5 Update 1 from Sun Management Center 3.5, the installation wizard launches the uninstallation wizard automatically.

Sun Management Center 3.5 Update 1 Online Help and Documentation Issue

Even though online help and other documentation were not revised for this release and are labeled for Sun Management Center 3.5, they still apply to the Sun Management Center 3.5 Update 1.

Sun Management Center 3.5 Installation and Configuration Guide Issues

“Installation Overview” Chapter

This following information was omitted from the “Installation Overview” section in the 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, you have two options:

• Install the documentation during the product installation.

• Use the pkgadd command to install the packages that are located in the following directory on disk 2:

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

“Preparing Systems for Sun Management Center Upgrade and Installation” Chapter

The title and description for the section“Sun StorEdge^TM A500 Patches” in the Sun Management Center 3.5 Installation and Configuration Guide are wrong. The correct title is Sun StorEdge A5x00 Packages (not Patches).

The following is the correct description for the section 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.

Sun Management Center 3.5 Update 1 requires the latest patch for the SUNWluxop package. See A5x00 Module Does Not Populate Tables With Values (4973319).

“Removing T3 Device Configuration If Present” Section

The title and information in the section, Removing T3 Device Configuration If Present, located in the “T3 Storage Devices” in Sun Management Center 3.5 Installation and Configuration Guide section has changed. The corrected version is as follows:

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.

The corrected procedure is as follows:

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 following command to stop the Sun Management Center agent.

   #/opt/SUNWsymon/es-stop -a

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 whether you want to stop the T3 from sending syslog messages, type y.

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

   3. 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 es-guiuninst” in Sun Management Center 3.5 Installation and Configuration Guide.

“To Install Sun Management Center 3.5 on the Solaris Platform” Procedure

Step 4 of the “To Install Sun Management Center 3.5 on the Solaris Platform” procedure in the Sun Management Center 3.5 Installation and Configuration Guide incorrectly lists the file /disk1/sbin/INSTALL.README. The correct file name is /disk1/sbin/README.INSTALL.

“Creating Agent Installation and Update Images” Section

The first paragraph of the section, “Creating Agent Installation and Update Images” in Sun Management Center 3.5 Installation and Configuration Guide omitted the following information. Agent-update images are supported on systems that have only the Sun Management Center agent component installed. If you try to use agent-update images on systems where you have installed the agent as well as the server or console or all three layers at the same time, the operation fails.

“To Install Sun Management Center 3.5 on the Microsoft Windows” Section

Step 6 of the procedure, “To Install Sun Management Center 3.5 on Microsoft Windows” in Sun Management Center 3.5 Installation and Configuration Guide says the default location in which to install Sun Management Center is C:\ProgramFiles\SunMC. This path is wrong. The default location is C:\ProgramFiles\SUNWsymon.

“Setting Up Users” Section

The current description of the esadm security group in the “Setting Up Users” in Sun Management Center 3.5 Installation and Configuration Guide section 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.

“Reconfiguring Sun Management Center Ports” Section

“es-config Options” table in the “Reconfiguring Sun Management Center Ports” section omitted the following parameter.

The following information for the -P option is incorrect: The range of ports for the -P option must be at least 100, for example, 1024:1124 where 1024 is the MinPort and 1124 is the MaxPort. The correct information is as follows: The range of ports must be 20 ports or larger, for example, 1024:1044. The minimum specified ports for -P is 20.

“Using Sun Management Center With a Firewall” Section

Step 3 in the procedure, “To Restrict the Firewall Port Range” in Sun Management Center 3.5 Installation and Configuration Guide incorrectly says: “You are asked whether you want to start the Sun Management Center components.” The software does not prompt you to start the Sun Management Center components. These components are started automatically.

Appendix E, Sun Management Center 3.5 Packages

The following localization packages were omitted from the “Sun Management Center 3.5 Packages” section in the Sun Management Center 3.5 Installation and Configuration Guide.

“Sun Management Center Security Concepts” Section

The information in the “Domain Admin, Admin, Operator, and General Functions” table in the Sun Management Center 3.5 User's Guide is incorrect. The correct information is that the operator has the right to set the module-active time window and that the Domain Admin has the right to view events.

Sun Fire Link Fabric Administrator's Guide Issues

“Sun Fire Link Administration Overview” Section

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 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 Extensible 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 causes the reconfiguration to fail. One or more nodes might have data that are out of sync with the new configuration. This failure also happens 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 functioning hardware corrects 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 High-End 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 High-End nodes were not supported by Sun Fire Link 1.0 software.

Appendix B, “Importing Preconfigured XML Files Using the Manage XML Configurations Option”

The following detailed instructions describe how to import preconfigured XML files using the Manage XML Configurations option. These instructions were omitted from Appendix B.

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 that 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 is 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. Before 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” section 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 Manage XML Configurations from the Fabric menu.

   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 in the Error dialog window.

   The XML Configuration dialog box is now the active window.

5. In the Look In field of the Configuration dialog box, type 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 is displayed.

6. Select the XML configuration file that 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 type the file name in the File Name field. The file does not open if you type the file name.

   ---

7. Click Open to open the selected file.

   The XML configuration file appears in the text area of the window.

8. Choose one of the following options:

   • If you want to edit the XML file, see 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. Provide a new filename.

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

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

Sun Fire Link Software Installation Guide Issues

Steps 3a and 3b in “Upgrading From Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5”

The following two changes apply to page 7, Steps 3a and 3b:

• 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 information:

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

  SFLM–server–name# pkgrm SUNWwcfmu SUNWwcfmr SUNWwcfms WUNWwccmn

“Upgrading From Sun Management Center 3.0, Platform Update 4, to Sun Management Center 3.5” Section

The instructions on page 5 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 describe 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 that you need to install are the Sun Fire Link Server and the Sun Fire Link Console.

   ---

   Example 4–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.

   ---

   Example 4–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 4–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 4–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

   ---

“Upgrading From Sun Fire Link 1.0 Software to Sun Fire Link 1.1 Software” Section

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 should be replaced with Step 2 and Step 3:

• 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

Table 3–1, “Installation Location”

Entries that are included under the heading, “Installation Location,” in Table 3–1, located on pages 32–33 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. This package 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.

“Setting Up the Sun Fire Link Add-On Software Using the Sun Management Center 3.5 Setup Wizard” Section

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”

• 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.

“Install, Set Up, and Uninstall Sun Management Center 3.5 Software Using the CLI” Section

The following replaces the current information on page 74, “Install, Set Up, and Uninstall Sun Management Center 3.5 Software Using the CLI.”

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 roles might be filled by the same system or by two or three different systems.

“Creating an Agent Update Image for Sun Fire Link” Section

The second paragraph on page 62 of the section “Creating an Agent Update Image for Sun Fire Link” 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 are not asked when you select a single component.

Sun Management Center 3.5 System Reliability Manager User's Guide Issue

The following information was omitted from the “Script Repository and Script Launcher Modules” chapter in the Sun Management Center 3.5 System Reliability Manager User's Guide. The procedure “To Access the Script Launcher Module” in Sun Management Center 3.5 System Reliability Manager User's Guide omitted that you must load the Script Repository Module before using the Script Launcher Module.

Sun Management Center 3.5 Supplement for the Sun StorEdge A5x00 and T3 Arrays Issue

Table 1–42, “Sun StorEdge T3 Module – Rules” omitted the following rules.

Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide Issues

Page 81

Page 81 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.

Package Name for English-Language Help File

Chapter 1 incorrectly lists the package name for the English-language help file as SUNWedh. The correct package name is SUNWenedh.

The following list shows 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

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

Page 11 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 provides the appropriate information:

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

Sun Management Center 3.5 Supplement for Workstations Issue

Page 8 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 provides the appropriate information:

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

French, Japanese, Korean, Simplified Chinese, and Traditional Chinese Supplemental Documentation Issue

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 PDF only:

• 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 Version 3 Supplement for Sun Fire Midrange Systems

• Sun Management Center 3.5 Supplement for Sun Fire Midrange Systems

Sun Management Center 3.5 Supplement for Netra Servers, Japanese Version, Issue

Chapter 1 omitted the following localization packages.

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.

Sun Management Center 3.5 Version 2 Supplement for Sun Fire 15K/12K Systems Issue

The note before the section title on page 32, “Uninstalling Software Using the CLI,” erroneously states that you need to rerun the ./es-setup -F command to set up the platform agent. You do not need to perform this step.

Issue Affecting Sun Fire Link Software Installation Guide, Sun Management Center 3.5 Supplement for Starfire Servers, and Sun Management Center 3.5 Supplement for Sun Enterprise 6500/5500/4500/3500 Systems

The section “Uninstalling Sun Management Center 3.5 Software” in these manuals has errors and omissions.

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 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.

For detailed instructions and options for using the GUI Uninstall Wizard, es-guiuninst, see 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 CLI uninstall script, es-uninst, see Appendix B, on page 195, in the Sun Management Center 3.5 Installation and Configuration Guide.

Sun Management Center 3.5 for Sun Fire, Sun Blade and Netra Systems Release Notes Issue

This document is not available in HTML and is not installed as part of the Sun Management Center documentation packages. Sun Management Center 3.5 for Sun Fire, Sun Blade and Netra Systems Release Notes is available in PDF on the Sun Management Center 3.5 Update 1 Software CD 2 of 2 in the directory disk2/image/ as sunfire-sunblade-netra_notes.pdf.