Sun StorageTek RAID Manager Software Release Notes |
This document contains important information about the May 2009 release of the Sun StorageTek RAID Manager software package or information that was not available at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the Sun StorageTek RAID Manager software.
This document contains the following topics:
This section contains the following topics:
TABLE 1 lists the components and the component versions that are included with this software package release.
To Verify the Driver Version On The System |
1. Log into the Sun StorageTek RAID Manager software.
A list of managed systems is displayed.
2. Select the system for which you want to view driver version information.
A list of controllers (HBAs) installed in the system is displayed.
3. Right-click on an HBA and select Properties.
The Properties window is displayed.
4. Click the Versions tab and review the value in the Driver field.
This release of the Sun StorageTek RAID Manager software provides support for the Windows 2008 operating system.
The operating systems, servers, and storage systems that have been tested and qualified to work with the Sun StorageTek RAID Manager software are described in this section. This section contains the following topics:
The Sun StorageTek RAID Manager software supports, at minimum, the following operating system versions.
Solaris 10 OS for the x64 and x86 (32-bit and 64-bit) platforms |
|
Note - The Sun StorageTek RAID Manager graphical user interface (GUI) does not support VMware technology. If your operating system is running on top of VMware technology (even if the OS is supported, as described in TABLE 2), use the command-line interface and the BIOS Configuration utility to perform storage management activities. This is due to the VMware technology presenting a generic ISCSI attach point, preventing the use of the GUI. For more information about using the command-line interface, see the Uniform Command-Line Interface User’s Guide at: http://docs.sun.com/app/docs/prod/stortek.raid.hba#hic |
Note - For up-to-date operating system version support, visit http://support.intel.com/support/go/sunraid.htm. |
TABLE 3 lists the servers supported by the Sun StorageTek RAID Manager software.
The Sun StorageTek RAID Manager software works with the following storage systems:
The software installation procedures are described in the Sun StorageTek RAID Manager Software User Guide (part number 820-1177-nn). Refer to that document for the latest installation procedures except where noted in Known Issues.
This section provides information about known issues and bugs filed against this product release. This section contains the following topics:
This section contains the known issues related to the Sun StorageTek RAID Manager GUI. This section contains the following topics:
The Sun StorageTek RAID Manager GUI will not launch when installed on the Red Hat Enterprise Linux (RHEL) 5 operating system. The Sun StorageTek RAID Manger software requires the Java Runtime Environment (JRE) libraries and Java SE 6.0, which are not a part of the standard RHEL 5 installation at Sun.
Workaround - To run the Sun StorageTek RAID Manager GUI on RHEL 5, do the following:
1. Ensure that libXp.so.6 is in the LD_LIBRARY_PATH variable.
2. Obtain and install the following package from the RHEL5 CD:
xorg-x11-deprecated-libs-6.8.1-23.i386.rpm
If you install the SPARC version of the Sun StorageTek RAID Manager software package on an x86 system, you will encounter permissions issues when attempting to log into the GUI from the x86 local host on which the HBA resides. However, you will be able to log into the GUI from the x86 local host when managing a remote HBA that resides on another system.
Workaround - Do the following:
1. Uninstall the SPARC version of the Sun StorageTek RAID Manager software package from the x86 system.
http://support.intel.com/support/go/sunraid.htm
3. Install the Sun StorageTek RAID Manager for x86 software package on the x86 system.
If you have multiple JBODs attached to a RAID HBA, you may need to distinguish a specific JBOD in the stack through the GUI.
To physically identify a JBOD that has an indicator light, do the following:
1. Log into the Sun StorageTek RAID Manager software.
2. Right-click on a JBOD controller management device (RAID HBA).
A drop-down menu is displayed.
3. From the drop-down menu, choose Blink Enclosure.
This causes the indicator light on the JBOD to flash.
For Sun JBODs, you can also use the identifier number on the JBOD to physically identify it. Do the following:
1. Determine the identifier number on the JBOD and write the number down for your reference.
TABLE 4 lists the types of identifiers used by the GUI per Sun JBOD, and lists the location of the identifier sticker per JBOD.
2. Log into the Sun StorageTek RAID Manager software.
When you use the aarconf getconfig command through the CLI, only one enclosure temperature sensor is displayed, while in the GUI, several temperature sensors for that same enclosure are displayed (fans, power supplies, and so on).
Workaround -If you need detailed temperature information about an enclosure, use the GUI.
When you use the aarconf getconfig command through the CLI, logical drives that you know are protected by hot-spares are listed with a value indicating they are not being protected by hot-spares. From the Logical Devices view of the GUI, however, those same logical drives are shown with the correct value, indicating they are being protected by hot-spares.
Workaround -The GUI shows the accurate value. To manage and view hot-spares, use the GUI.
In the Logical Devices view of the GUI, a logical drive might be displayed as optimal but may have a yellow warning status icon next to it due to one or more bad stripes on the drive. This condition occurs when the GUI encounters either of the following conditions:
A bad stripe entry in the GUI does not mean the logical drive or container in the array is degraded. Instead, it means the logical drive and all members of the array are available, but some of the stripes are bad due to irrecoverable medium errors. This causes less space on the drive and in the array to be readable.
Workaround - None, as you can continue to use the logical drive. To remove the bad stripe entry, you must initialize the array by using the clear command. However, performing this operation erases all data on the drive.
If a disk subsystem, such as a blade or JBOD, is powered off separately from a host, the operating system (OS) continues to detect the logical drives of that powered-off disk subsystem. This is because the logical drives already existed prior to powering off the blade or JBOD. In this situation, the OS expects the logical drives could return to their operating status at any time. Therefore, the GUI displays the logical drives as failed, assuming no physical drives are present.
Workaround - This is expected behavior in the event that a disk subsystem is powered off separately from a host. To return the logical drives to their operating status, reapply power to the disk subsystem.
This occurs only on Solaris systems.
Workaround - Do either of the following:
When trying to rename a logical volume through the GUI on the Solaris OS, the Backspace and/or Delete keys might not work.
Workaround - Drag the mouse over the old logical volume name until the name is highlighted, and then type the new name. The new name will replace the old one.
This section contains the known VMware issue.
If you rescan or create a logical volume in a RAID HBA to which multiple JBODs are connected, the VMWare ESX Server technology might time out.
Workaround - None. This issue is related to a bug in the VMWare drive, tracked in the VMWare bug, PR#267814.
This section describes issues releasted to the user documentation. This section contains the following topics:
In the Sun StorageTek RAID Manager Software User’s Guide, several procedures tell you to click an HBA in order to complete certain tasks. When you try to complete those tasks through the GUI, you actually have to click a controller, not an HBA. This causes confusion.
Workaround - Review the “Terminology Used in This Guide” section of the Sun StorageTek RAID Manager Software User’s Guide. This section explains that an HBA is also known as a controller, adapter, board or card. For consistency, the documentation always uses the word HBA but these alternative terms can be substituted.
When you create an array using the BIOS Configuration Utility, the Sun StorageTek RAID Manager software displays the array as a logical drive. The documentation describes arrays, not logical drives.
Workaround - There is no workaround.
The following is a list of documents related to the Sun StorageTek RAID Manager software. For any document number with nn as a version suffix, use the current version.
Sun StorageTek SAS RAID HBA Installation Guide Eight-Port, Internal HBA |
|||
Sun StorageTek SAS RAID HBA Installation Guide Eight-Port, External HBA |
|||
In addition, the Sun StorageTek RAID Manager software includes online help.
For Sun StorageTek SAS RAID HBA hardware information, refer to the Sun StorageTek SAS RAID HBA Installation Guide Eight-Port, Internal HBA or Sun StorageTek SAS RAID HBA Installation Guide Eight-Port, External HBA.
You can search for these documents online at:
http://docs.sun.com/app/docs/prod/stortek.raid.hba#hic
If you need help installing or using this product, go to the following website:
http://www.sun.com/service/contacting
Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.