Sun Management Center 3.5 Version 6 Release Notes for Sun Fire Entry-Level Midrange Systems
The Sun Management Center 3.5 Version 6 Release Notes for Sun Fire Entry-Level Midrange Systems provides late-breaking news for Sun Management Center 3.5 Version 6 software for Sun Fire entry-level midrange systems. This document supplements the Sun Management Center 3.5 Version 6 Supplement for Sun Fire Entry-Level Midrange Systems (819-0419-10).
This document contains the following release notes for the Sun Management Center 3.5 Version 6 add-on software for Sun Fire entry-level midrange systems:
Supported Sun Fire entry-level midrange systems include:
The Capacity on Demand (COD) 2.0 option is supported. Refer to the description of the FRUID Info Config-Reader table in Chapter 3 of the Sun Management Center 3.5 Version 6 Supplement for Sun Fire Entry-Level Midrange Systems for details about identifying COD boards in this release. Also refer to the Sun Fire Entry-Level Midrange System Administration Guide for more information about COD.
Refer to the Sun Management Center 3.5 Version 6 Supplement for Sun Fire Entry-Level Midrange Systems for detailed information about this software.
The minimum Sun Fire entry-level midrange systems firmware and operating systems supported in this release are shown in TABLE 1.
Solaris Operating System
Solaris software patches might be available for the Sun Management Center 3.5 application. You must install all the patches required for your operating environment before installing the latest update of the Sun Management Center 3.5 software and this add-on.
If you have a Sun service contract, you can download the patches from the following web site:
You can also download the patches from the Sun Management Center product web site:
For more information about the patches required for the latest update to Sun Management Center 3.5 software, see the corresponding Sun Management Center Software Release Notes.
The Sun Management Center 3.5 Version 6 add-on software packages for Sun Fire entry-level midrange systems are supplied in a zip file named
on the software download site:
If you don't see the listing for Sun Management Center 3.5 Version 6 under New Downloads, do the following:
1. Click on the A-Z Index of All Products.
2. Click on M.
3. Scroll down and click on Management Center 3.5 Version 6.
4. Click on Download.
5. Log in to the Download Center.
6. Click on Accept to accept the License Agreement, and click on Continue.
7. Follow the instructions on the download page.
For details about using Sun Managemant Center 3.5 Version 6 for Sun Fire entry-level midrange systems, see the Sun Management Center 3.5 Version 6 Supplement for Sun Fire Entry-Level Midrange Systems. Refer to the preface of that document for information about related documentation. Sun documentation can be found here:
When the domain agent is shut down or rebooted, a critical Data Acquisition Error alarm is generated. Also, in the System table, the Module Status value is reported as FRU ID error. These errors are generated because information cannot be obtained from a domain that is unavailable due to a shutdown or reboot operation. However, the errors do not indicate the domain has been shut down or rebooted. 
Messages in the LOM Events table are truncated at approximately 88 characters.
Workaround: To see the full message, use the SC command showlogs.
In this release, DIMM errors do not generate an alarm. 
In this release, System Indicator Board (SIB) errors do not generate an alarm.
Workaround: When the FRUID Info table property fields display the value Reading... for an extended period, a SIB failure may be indicated. If a failure has occurred, it will be reported in /var/adm/messages.
The Entry-Level Midrange Add-On does not provide alarms when Ecache errors are encountered.
Workaround: Look for applicable Ecache error message strings in the file /var/adm/messages.
After a DR operation, you must restart the picl daemon so that the tables provided by this add-on software are updated.
In Solaris 8 or 9:
In Solaris 10:
No alarm is triggered when a power supply is not working properly. Moreover, the values of the PSU Input, PSU Output, and PSU Status properties in the Power Supplies table display an erroneous OK value for a degraded power supply.
Workaround: If the fault light indicates a fault (green), log on to the system controller and use the firmware's showboards command to determine which hardware is triggering the fault light.
Although the I/O Device table includes Disk Count, Network Count, and Tape Count properties, these values are not displayed. This table reports only PCI cards. 
The Disk Devices table sometimes fails to report internal disks. 
Not all alarms are displayed in the Physical View and Logical View.