| Sun Management Center 3.6 Version 2 Add-On Software Release Notes for Sun Fire, Sun Blade, and Netra Systems |     |
| Sun Management Center 3.6 Version 2 Add-On Software Release Notes for Sun Fire, Sun Blade, and Netra Systems | |
|
Sun Management Center 3.6 Version 2 Add-On Software Release Notes |
This document contains release notes for the Sun
Management Center 3.6 Version 2 add-on software for Sun Fire, Sun Blade, and Netra systems (or ELP Config-Reader Monitoring). The document includes the following sections:
This section describes changes in Sun Management Center add-on software for Sun Fire, Sun Blade, and Netra systems between the release of Sun Management Center 3.6 software and this release of Sun Management Center 3.6 Version 2 add-on software. This new software release adds support for Sun Ultra 45 workstations.
Sun Management Center 3.6 Version 2 add-on software supports the following systems:
TABLE 1 lists the software versions required for Sun Management Center 3.6 Version 2 add-on software.
|
Solaris Operating System[1] |
8, 9, 102 |
|
|
Sun Management Center ELP Config-Reader Monitoring add-on software |
||
|
Solaris Operating System1 |
Depends on platform[2] |
|
|
Sun Management Center ELP Config-Reader Monitoring add-on software |
||
|
Solaris Operating System1 |
||
|
Note - The Sun Management Center server and agent machines need to use the same versions of add-on software. |
Solaris software patches and Sun Management Center patches might be available for the core Sun Management Center 3.6 application and for this add-on software. You must install all the patches required for your operating system before installing Sun Management Center 3.6 software and this add-on.
If you have a Sun service contract, you can download the patches from:
For more information about the patches required for the latest update to Sun Management Center 3.6 software, see the corresponding Sun Management Center Software Release Notes.
This document contains additional information to supplement the Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade and Netra Systems (819-1153). Also refer to the preface of that document for a full list of related documentation.
You can find Sun documentation at:
http://www.sun.com/documentation/
The Sun Management Center 3.6 Version 2 add-on software packages are supplied in a zip file on the software download site at:
http://wwws.sun.com/software/download/index.html
If you do not see the listing for Sun Management Center 3.6 Version 2 under New Downloads, use the A-Z Index of All Products to find the software[3].
Refer to the Sun Management Center Installation and Configuration Guide for information about installing and setting up Sun Management Center 3.6 software. The Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade, and Netra Systems describes general information about installing the version of this ELP Config-Reader Monitoring add-on software included with the core Sun Management Center 3.6 software. However, this 3.6 Version 2 add-on software is installed using a separate zip file, requiring a change to the installation procedure. FIGURE 1 shows a high-level view of the installation process.
|
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. |
If you have already installed core Sun Management Center 3.6 software on your server and console systems, use the following procedures:
|
|
1. Refer to the Sun Management Center Installation and Configuration Guide.
The appendixes of the installation and configuration guide provide instructions for uninstalling add-on products using the es-guiuninst wizard or the es-uninst command-line script. Uninstall only the ELP Config-Reader Monitoring add-on software.
|
|
Refer to Obtaining the Add-On Software of this document for information about obtaining the software.
2. Unzip the zip file to a directory located at a path named downloadpath.
3. Log in as superuser on the host machine.
4. Change the directory to the path where the core Sun Management Center 3.6 software is installed.
The directory will look similar to this:
installed_directory/SUNWsymon/sbin
5. Run the es-guiinst or es-inst installation script with a pointer to the path named downloadpath described in Step 2.
You will see a list of add-on products that you can install.
6. Choose the ELP Config-Reader Monitoring add-on product.
7. Complete the remaining steps in the installation script.
8. Follow the steps to set up the software.
The installation wizard will prompt you to set up the software. For more information, refer to the Sun Management Center Installation and Configuration Guide.
If you have not yet installed any Sun Management Center 3.6 software, you must install it before installing this Version 2 add-on software.
1. Refer to the Sun Management Center 3.6 Supplement for Sun Fire, Sun Blade, and Netra Systems for information about preparing for installation.
2. Refer to the Sun Management Center Installation and Configuration Guide for instructions for installing the core software.
If you are updating a previous release of Sun Management Center software, read the information about updating the software from your currently installed release.
a. Do not install ELP Config-Reader Monitoring as part of this step.
In the course of performing this installation you will come to a dialog that allows you to select from a list of add-on products (Figure 1-3, "Add-on Products," in the Sun Management Center 3.6 Installation and Configuration Guide). Do not install the add-on product ELP Config-Reader Monitoring.
3. Perform the steps outlined in the procedure To Install the 3.6 Version 2 ELP Config-Reader Monitoring Add-On Software.
Updated packages are installed with this release to support the newly supported model. TABLE 2 lists the server and agent components for Sun Ultra 45 workstations.
This section describes software bugs known at the time of this release that you might notice or that can affect the operation of Sun Management Center 3.6 Version 2 add-on software.
After installation of localized packages has occurred, the es-validate command erroneously displays the value 3.5 in the Version column for this release of the ELP Config-Reader Monitoring software. When this happens, you might also see an erroneous, older copyright date during a CLI installation and in the installer log file.
Workaround: Use the pkginfo command to obtain accurate information about the packages.
Alarms are not displayed in the Physical View and Logical View.
Workaround: Rely on the tables and the Alarms tab for for alarms.
An alarm is not generated by the agent when a CPU is taken offline using the command psradm -f. Additionally, when the CPU is brought back online, the Processors table does not immediately update the CPU as online.
Workaround: To see an updated status, click on other tables in the GUI and then click back on the table of interest. A default refresh interval updates all the tables once an hour. [6296273]
The Total Disks in the Hardware Summary of the Hardware tab (the System node property value for Total Disks) incorrectly includes the CD/DVD drive. Thus, on platforms with four disks and an optical drive, the Disk Count displays 5.
On Netra 440/240 systems, the Hardware Summary table sometimes does not display.
Workaround: Close the Details window, then launch it again.
On Netra 440 systems, if a network cable is unplugged, no alarm is generated. Further, the Network Interfaces table is not updated to indicate that the cable is unplugged.
On Netra 440 systems with QFE cards, the Network Interfaces table displays values for the Name property in an erroneous format.
On Netra 440 systems running Solaris 10 Operating System, the Fans table erroneously displays the value double-dash (--) for the Description property for the FT1/F1 fan.
For PDB components on Netra 440 systems, the Other Components table erroneously displays the value double-dash (--) for the Description property.
Workaround: Use the prtfru command to see the PDB component description.
For DVD-ROM devices on Netra 440 systems, the Media Devices table erroneously displays the value double-dash (--) for the Type property.
Workaround: Use the prtpicl command to determine the type of media device.
The Locations table and the Logical View do not display information about USB locations on Netra 240 and Sun Fire V240 systems.
The environmental Voltage Sensors table does not display the PSU Power OK fault sensor property, ps0_ff_pok, for Netra 440 and Sun Fire 240/210 systems running Solaris 10.
Workaround: Use the prtdiag command to obtain the status of voltage sensors.
The value of Operational Status is sometimes not updated on Netra 240 systems, despite changes that should trigger such a change. The following events fail to trigger an expected change in Operational Status:
Workaround: Observe the alarms in the Alarms tab and Fan table properties for accurate fan status.
Workaround: Observe the alarms in the Alarms tab, as well as the value of Current Reading in the environmental Current Sensors table.
Workaround: Observe the alarms in the Alarms tab, as well as the value of Current Reading in the environmental Voltage Sensors table.
On Netra 440/240 and Sun Fire V240 servers with Solaris 10 OS, PICL might not interpret some system configuration changes after initialization, such as the bge1-bge3 drivers. The instances for these drivers are reflected in the output of the prtconf -v command but not in the output of the prtpicl -v command.
Workaround: Realign PICL with the prtconf utility by executing the command svcadm restart picl.
The physical component descriptions of the Entry Level Platforms Config Reader incorrectly display the value double-dash (--) as Model Name, Part Number, Version, and Serial Number on Sun Fire V440 servers with Solaris 9 4/04 and Solaris 10 OS.
The Physical View of Sun Fire V240 servers with Solaris 8 OS does not display the CD/DVD drive. Information similar to the following is displayed:
On the cited platforms running Solaris 8 OS, information pertaining to the second network interface connector (ce1) is not reported in the Memory Modules or Network Interfaces tables, nor in the Physical View. Information pertaining to the first network interface connector (ce0) is reported and displayed.
The Sun XVR-1200 Graphics Accelerator might incorrectly use the same device name as the Sun XVR 500 graphics accelerator and thus be listed as XVR-500 in the Expansion Card Table and Physical View.
Workaround: To verify if the graphics accelerator is listed correctly, check the IO Devices section of the output of the command
/usr/platform/platform-name/sbin/prtdiag
In this command, platform-name must be replaced with the entire output of the uname -i command on your system.
On Sun Blade 2500 workstations with one CPU, the Physical view incorrectly displays two CPU fans. This issue also results in a blue alarm for the nonexistent second CPU fan, displaying the value Lost Comms for the Operational Status property in the Fans table.
The Environmental Sensors/Temperature Sensors table of the ELP config reader on Sun Blade 2500/1500 workstations do not list some sensors. This situation could result in critical temperatures not triggering alarms. TABLE 3 lists the temperatures that are included and missing on each workstation model.
Workaround: Whle all these temperature readings are listed in the PICL output, there is no workaround for the missing alarms.
On Sun Blade 2500 workstations, the rear view of the Physical view incorrectly indicates PCI card slots as populated. For example, on a system with only one PCI card in slot 5, the rear view indicates that slots 0, 2, 3, 4, and 5 are populated. However, none of the nonexistent card images are highlighted when the mouse is moved over them. Only the image for the slot with the card inserted (5 in this example) is correctly highlighted.
Workaround: Move the mouse over the slots indicated as populated to verify that they are actually populated. The correctly populated slot is highlighted when the mouse is moved over it.
Some of the images displayed in the Topology view and the platform Physical view might not match the actual physical colors for Sun Blade 2500/1500 (Silver) systems. In such cases, these views display instead the colors for Sun Blade 2500/1500 (Red) systems.
In addition, the System-Side Physical View, which displays the Motherboard and other internal components for the Sun Blade 2500 (Silver) platform, also does not display the DIMM Duct or the Disk Fan assembly.
During installation of the core Sun Management Center 3.6 software on Sun Fire T2000 systems, the following error messages might be displayed multiple times and should be ignored.
/opt/SUNWsymon/sbin/es-inst: /usr/platform/sun4u/sbin/prtdiag: not found
In the Module Manager tab, you can use Unload to unload the ELP Config-Reader Monitoring software module on a Sun Fire T2000 system. If you then use Load to reload the software module, the Module Browser information for the Sun Fire T2000 systems is not displayed.
Workaround: Perform the following for a temporary fix:
Sun Management Center incorrectly displays Sun-Fire-T200 as the platform name for Sun Fire T2000 systems. The Sun Fire T2000 system controller correctly displays Sun-Fire-T2000 as the platform name.
| Sun Management Center 3.6 Version 2 Add-On Software Release Notes for Sun Fire, Sun Blade, and Netra Systems | 819-4987-10 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Uninstall the 3.6 ELP Config-Reader Monitoring Add-On Software