| Sun StorageTek Common Array Manager Software Release Notes |    
|
| Sun StorageTek Common Array Manager Software Release Notes |
|
|
|
This document contains
important information about release 5.0 of the Sun StorageTek
Common
Array Manager software 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 Common Array Manager software.
These release notes cover the software released on the Sun StorageTek Common Array Manager Software 5.0 CD.
The Release Notes consist of the following sections:
This section describes
the main features of the Sun StorageTek Common Array Manager Software
in the following sections:
The Sun StorageTek Common Array Manager software provides you with an easy-to-use interface to configure, manage, and monitor Sun StorageTek storage arrays. The Common Array Manager software includes the following functions:
Common Array Manager software supports the following Sun storage systems:
The management software runs on the platforms described in TABLE 1.
|
Windows 2000 with Service Pack 4 or higher |
TABLE 2 lists the version information for the software included in this release.
|
Firmware files, as listed in Firmware Files |
The software and hardware products that have been tested and qualified to work with the Sun StorageTek Common Array Manager software are described in the following sections:
The management host on which the management software resides must meet the system requirements described in TABLE 3.
|
SPARC server or workstation or Solaris x86 running one of the following: Windows servers with 800 MBytes on system drive running one of the following: |
|
|
930 Mbytes (Solaris); 800 Mbytes (Windows) (see complete list of disk space requirements in File Space Requirements). |
|
The remote scripting CLI client sends commands to a management host, which in turn sends the commands to the array. TABLE 4 lists remote platforms that can run the CLI client.
The Sun StorageTek Common Array Manager software supports the web browsers listed in TABLE 5.
|
Note - The software requires that you enable pop-up windows in your web browser. |
Documentation for the Sun StorageTek Common Array Manager is available only in English.
The array installation procedures are described in the Sun StorageTek Common Array Manager Software Installation Guide (part number 819-7035-nn). This section describes release-specific steps for firmware and management software patch upgrades that you must perform:
The Sun management software is distributed on the Sun StorageTek Common Array Manager Software CD. The installation script on that CD verifies host requirements. In particular, it ensures that there are at least 800 Mbytes of disk space available before starting the installation script. Be sure to do the following before performing the upgrade:
Should a failure occur, be sure to check the available disk space again. Then consult the system log /var/sadm/install/se6000/se6000_Host_SW.log for more information.
If a requirement is not met, the script informs you and then cleans up afterward, where appropriate. The script prompts you for input or fails and exits if it detects any of the following in the system:
The total size of the installation files is approximately 800 Mbytes when the files are extracted from the CD or download file. The management host software requires 800 MBytes on a Windows platform or the following available space for successful installation on Solaris:
If you are installing the array and the management software, follow the entire installation and configuration procedure described in the Sun StorageTek Common Array Manager Software Installation Guide.
After the initial installation and configuration, you will be able to upgrade the management software and firmware with each release.
When you run the RunMe wizard, it will search for earlier versions and determine if a new installation or an upgrade is necessary. If the script detects that there is no earlier version installed, it will perform a complete new installation. The procedures for upgrading the array manager software are the same as those for installing the software, as described in the Sun StorageTek Common Array Manager Software Installation Guide. When performing an upgrade, it is not necessary to uninstall the existing software. The installer also installs the firmware update bundle on the host server. To upgrade the firmware on the array, see To Upgrade the Array Firmware.
This procedure downloads the firmware binary on the management host to the array and upgrades the firmware running in the array. It is not necessary to uninstall the existing firmware. You can also upgrade firmware from the management software.
1. On the Java Web Console page, click Sun StorageTek Common Array Manager.
2. Go to the Storage System Summary page and select the arrays to be upgraded.
3. Click the Upgrade Firmware button.
|
Note - The array will remain in a degraded state until all alarms are deleted. |
The following sections provide information about known issues and bugs filed against this product release:
If a recommended workaround is available for a bug, it follows the bug description.
Bug 6453816 - Using the Volume Creation wizard, if a pool that should have adequate space does not appear in the list, then you are no longer able to create volumes in that pool using the browser interface wizard. This only applies when you are creating volumes from SATA drives.
To determine the maximum volume size, go to the Vdisk Summary screen. Review the Total Capacity, Configured Capacity, and Max Volume Size for each virtual disk. Since you can create a volume from one virtual disk only, the maximum volume size indicates the largest volume that can be created on a virtual disk. You must match up virtual disks to the profile of the pool you want to use to determine if there is adequate space.
Workaround - Use the SSCS CLI to create volumes in a pool that did not show up in the wizard even though it has adequate space.
Bug 6444212 - The Version display in the Sun StorageTek Common Array Manager GUI and the sscs list mgmt-sw both show the correct Version number for the initial release: 5.0.0.0, However, they show the final build number as seven when it is eight.
Workaround - Verify the release using the build date: June 26, 2006.
Bug 644210 - The Service Advisor procedure for Resetting Controller Circuit Breakers has the following errors:
Bug 6444324 - In the zh (Chinese) locale, when an installation is finished the results page shows garbled characters.
Bug 6448643 - The Service Advisor procedure for Remove and Replace a Disk Drive Assembly has the following error:
Bug 6419579 - When a battery fails or is removed, the problem is reported multiple times in both alarms and email notifications.
Bug 6329784 - When an initiator is added or removed from a zone in a fabric, the Configuration Service software does not dynamically detect the change. The WWNs of initiators newly added to the SAN are not displayed.
Workaround - If the WWN of a new initiator is not in the drop-down list on the New initiator page, try creating the initiator by manually entering the new WWN. This will force the page to refresh. When you create another new initiator, the WWN will be in the list.
Bug 6356119 - The first time the online help window is displayed, the application might log you out.
Workaround - Re-enter the application from the main Java Web Console page.
Bug 6371462 - The switch setting 2 Gbits/sec or 4 Gbits/sec applies to the speed of the internal FC data path to disk drives. When a 2-Gbits/sec drive is set to 4 Gbits/sec, the drive enters a status of Bypassed.
Volumes on Bypassed drives are marked as Missing and lose their pool assignments. They are displayed on a separate Ghost Volumes list, with minimal info available.
Bug 6416680 - When you change a tray ID using the Common Array Manager software, the component appears to have been replaced with a new component.
Workaround - Avoid changing tray IDs. If you must change the tray ID, expect and delete the resulting alarm.
Bug 6403778 - After a firmware upgrade, the Solaris luxadm display lists two secondary paths instead of one as primary.
Workaround - Use the luxadm command to reset a path to primary.
Bug 6443960, 6431092 and 6433655 - Sometimes jobs that are long-running or involve performing a large number of operations will cause a time out in the GUI, forcing the user to log back in. In these cases the operation will still complete even though the GUI times out. Similarly, jobs with a lower priority may be found to be running before jobs with a higher priority. When mapping a large number of volumes at once, while the job is still mapping the volumes the Job Summary may fail to show a pending job.
Workaround: All of these cases are anomalies associated with the interface being unable to keep up with the number of operations performed. When the operations are complete, log back in to the interface and check the components related to the operation that was being performed.
Bug 6442500 - After replacing a failed drive, the degraded volume alarm is cleared before the volume reconstruction is complete.
Workaround - After replacing a failed drive, check the status of the affected volume(s) on the Volume Summary page to determine whether reconstruction is in progress and whether the volume has returned to the Optimal condition.
Bug 6413457 - If two browsers are open and one user logs out, when the other user initiates any action in the browser, the login page is displayed in the browser's main content frame instead of on its own page. This has also been seen to happen with single user login time outs. This requires the user to relaunch the application.
Workaround: Click on the Console button in the masthead (the top frame of the browser). The browser redisplays the web console page, where you must click on the management software link to relaunch the application.
Bug 6427632 - On the Register Storage System page, the I/O Module firmware is listed twice (duplicated). Array firmware upgrades have completed successfully, despite this unexpected display error.
Workaround - Ignore duplicate entries.
Bug 6429827 - Right- clicking on a component to open a new window causes system errors in some cases, and displays the wrong pages for some others. In some cases, the correct page displays.
Workaround - Do not use the right-click function.
Bug 6433654 - Successful unmap events are not written to the management host log file.
Workaround - Use the browser interface or the CLI to see whether volumes are mapped.
Bug 6266943 - After becoming a secondary volume of a replication set, a volume that was previously recognized by a host (through the format command) is displayed as drive type unknown. This secondary volume should be designated as a read-only device.
Workaround - Ensure that the intended secondary volume is a new (unlabeled) volume. Do not use an existing volume.
Bug 6453816 - If you have allocated all or most of the SATA disks as virtual disks, such that the system can no longer create virtual disks because there are not enough disks available, then you will not be able to create volumes through the browser interface in SATA-only pools. This situation occurs even if available space exists on SATA-based virtual disks that had been created. The same situation occurs for pools that allow any disk type if there is no Fibre Channel space available on the system.
Workaround - Leave enough disk drives available so that you can create volumes using the existing virtual disks. You can also use the SSCS command-line interface to create volumes when in this state.
This section describes issues related to Common Array Manager installation.
At the end of the procedure for Common Array Manager installation on a Windows platform, you need to perform the following registry edit to disable guest users. Without this step, users will not be able to log in.
|
Note - Regedit should be run only by experienced PC administrators. Please backup the registry before editing. |
Run Regedit and set the following registry value to 0:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\ForceGuest
To set up a firewall on a Windows management host, after the installation is complete you must allow an exception for port 6789. Common Array Manager will not work through a firewall without this. Some firewall programs prompt for your agreement to allow new programs to communicate through the firewall, and set the port for you. Refer to your firewall documentation for instructions on how to open a port through the firewall.
Bug 6458282 - If the installer is run by a Windows admin user with a space character in the user name, when any user tries to log in there will be a system error and the login will fail.
Workaround - The installer must be run by an administrative user without space characters in the user name.
This section describes issues related to Solaris OS 10 incompatibilities.
Bug 6450647 - The fault management service in Common Array Manager does not run on Solaris 10 systems running in a multi-byte locale. The service must operate in the default C locale.
Workaround - Change the locale of the machine to the default C locale. If this is not possible, execute the following commands:
2. ln -s wrapper-solaris-sparc-32 wrapper
On an x86 Solaris machine, the second step should be:
ln -s wrapper-solaris-x86-32 wrapper
Bug 6442868 - Common Array Manager 5.0 cannot be installed in a non-global zone on Solaris 10 when the Java Console needs to be upgraded, because the Java Console cannot upgrade as part of the CAM installation (Java Console requires installation in a global zone).
Workaround - Perform an upgrade of the Java Console to 2.2.5 in a global zone before installing the Common Array Manager. The Java Console 2.2.5 packages can be accessed from the extracted CAM distribution under /var/opt/CommonArrayManager/Host_Software_5.0.0.xx/components/lockhartSolaris. Use the setup script under lockhartSolaris (not the Common Array Manager installer setup script) to install the core packages. The localization packages need to be installed manually.
This section describes known issues and bugs related to storage configuration.
Bug 6408489 - When you use the software to set the Disk Scrubbing With Redundancy Enabled parameter from True to False while the Disk Scrubbing Enabled parameter is set to False, the page reports success, but the value of Disk Scrubbing Enabled remains False. When you make this change using the CLI, the prompt returns without a message, but the disk scrubbing setting remains the same as it was.
Bugs 6246249, 6335727 - When multiple management stations are accessing the array, there is no reservation message to inform the users that the array is locked, and there is no notice of reserving a host for maintenance.
Workaround - Inform users of other management stations that may be accessing the same array of pending array operations, to prevent attempts at making configuration changes from a different host.
Bug 6444767 - The power fan removal/replacement procedure in the Service Advisor applies to the Controller module and not the expansion units.
Workaround - Use the following procedure to replace a power-fan module in the 6540 array expansion modules:
1. From the rear, power-fan assembly A is located in the upper right corner of the tray and power-fan assembly B is located in the lower left corner of the of the tray.
2. Locate the failed power-fan assembly by checking the fault lights. If a fault is detected, the Service Action Required LED (Amber) will be on and the Service Action Allowed (Blue) LED should be on.
|
Caution - Potential loss of data access - Never remove a Power-Fan assembly unless the Blue Service Action Allowed LED is in the On position. |
3. Push the power switch on the failed power-fan assembly to the Off position.
4. Unplug the power cord from the failed power-fan assembly.
5. If you are replacing power-fan assembly A, lift the latch/handle up to unlock the power-fan assembly and pull the power-fan assembly out of the tray. If you are replacing power-fan assembly B, pull the latch/handle down to unlock the power-fan assembly and pull the power-fan assembly out of the tray.
|
Note - This illustration shows the removal or replacement of power-fan assembly B. Be sure to remove or replace the correct power-fan assembly. |
6. Unpack the new power-fan assembly and save all of the packing materials for return of the failed power-fan assembly. Use care when handling either the new or the failed power-fan assembly.
7. Ensure the power switch on the new power-fan assembly is in the Off position.
8. Insert the new power-fan assembly until it connects with the midplane connector and push the latch/handle in to the locked position.
9. Plug the power cord into the new power-fan assembly.
10. Push the power switch to the On position.
11. The Green power-fan LEDs should now be on. If this is not the case, please contact your service representative.
The current Getting Started Guides for the 6130 and 6140 arrays contain software installation instructions that are superseded by the Sun StorageTek Common Array Manager Software Installation Guide. You can still refer to the guides for the array installation instructions. Refer to the Sun StorageTek Common Array Manager Software Installation Guide for information about Common Array Manager software installation and logging into the browser interface and sscs CLI man pages.
Bug 6442690 - The Common Array Manager online help for creating a profile mentions a segment size option of 8 kb. The 8k segment size is not available, since it was removed from the product due to other issues.
This section describes known issues and bugs related to localization.
Bug 6445930 - Non-ASCII characters used in array name or volume name are displayed as question marks on several pages.
Workaround - Use only ASCII characters for array name, volume name or other device/component names.
Bug 6448835 - Non-ASCII characters cannot be used in some input fields since they will be displayed as question marks on several pages.
Workaround - Use only ASCII characters for site information or other text input fields.
This section provides useful operational information not documented elsewhere.
If you create management objects while an "import array" job is running, it might interfere with the import. Be sure that everyone who uses the destination array does not modify or create any objects (including volumes, initiators, mappings, and so on) while the import is in progress.
Following is a list of documents related to the Sun StorageTek Common Array Manager. For any document number with nn as a version suffix, use the most current version available.
You can search for this documentation online at http://www.sun.com/documentation.
|
Sun StorageTek Common Array Manager sscs (1M) CLI Quick Reference |
||
|
Sun StorageTek Common Array Manager Software Installation Guide |
In addition, the Common Array Manager software includes online help and man pages for CLI commands.
This section lists the firmware files included in the Common Array Manager 5.0, by array type.
The firmware files are named as follows:
Firmware file directories each contain a link, image.fw, that points to the firmware image, as well as a text file, baseline.txt, that contains the version of the firmware image. SATA drive firmware is installed at the factory for the Sun StorageTek 6540 and 6140 arrays and is not listed.
TABLE 6 lists the firmware files for the StorEdge 6130 Array included in this release. These files are located in /var/sadm/swimages/117856-35.
TABLE 7 lists the firmware files for the StorageTek 6140 Array included in this release. These files are located in /var/sadm/swimages/120337-11.
TABLE 8 lists the firmware files for the StorageTek 6540 Array included in this release. These files are located in /var/sadm/swimages/121540-02.
If you need help installing or using this product, go to:
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.
| Sun StorageTek Common Array Manager Software Release Notes | 819-7036-11 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To
Upgrade the Array Firmware
