| Sun StorageTek Common Array Manager Software Release Notes, Release 5.1 |    
|
| Sun StorageTek Common Array Manager Software Release Notes, Release 5.1 |
|
|
Sun StorageTek Common Array Manager Software Release Notes |
This document contains important information about release 5.1 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.1 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:
This section describes the main new features of the firmware, including the following:
Controller firmware 06.19.xx.xx allows tray mixing of array controllers and two versions of expansion trays. After installing the firmware, older controllers can use new expansion trays and older expansion trays can be used with the new controllers. There are restrictions on adding trays with data. The following table lists the supported tray intermixing. TABLE 1 lists the supported tray intermixing without data. For adding trays with data, contact your service representative.
|
Expansion Trays without data - Controller Firmware 06.19.xx.xx |
||
|---|---|---|
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:
The following features are not supported in Release 5.1, even though they may be described elsewhere in the Common Array Manager 5.1 documentation set:
TABLE 2 lists the version information for the software included in this release.
|
Firmware files, as listed in Firmware Files |
For optional premium features, you must purchase licenses. When you order premium feature licenses, the licenses will be sent to you with instructions on how to activate the features.
The following premium features are available from Sun:
|
Combo Data Snapshot, Data Volume Copy, Data Replicator, and 64 Domains |
|||
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:
Common Array Manager software supports the following Sun storage systems:
The management software runs on the platforms described in TABLE 4.
|
Windows 2000 with Service Pack 4 or higher Windows 2003 with Service Pack 1 or higher Windows XP Pro with Service Pack 2 or higher[1] |
|
The management host on which the management software resides must meet the system requirements described in TABLE 5.
|
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: |
|
|
555 Mbytes (Solaris); 530 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 6 lists remote platforms that can run the CLI client.
The Sun StorageTek Common Array Manager software supports the web browsers listed in TABLE 7.
|
Note - The software requires that you enable pop-up windows in your web browser. |
The browser user interface for the Sun StorageTek Common Array Manager is available in:
The command line interface, online help, and the man pages are available in:
The array installation procedures are described in the Sun StorageTek Common Array Manager Software Installation Guide (part number 820-0213-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 550 Mbytes of disk space available before starting the installation script. Be sure to do the following before performing the upgrade:
Should an installation failure occur, be sure to check the available disk space again. Then consult the system log for more information.
Solaris: /var/sadm/install/se6000/se6000_Host_SW.log
Linux: /var/opt/cam
Windows: \Program Files\Common Files\Sun Microsystems\se6000
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 555 Mbytes when the files are extracted from the CD or download file. The management host software requires 530 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.
|
Note - On Linux and 64-bit Windows 2003 platforms, you must remove previous Common Array Manager 5.1 versions and perform a clean install of 5.1.0.11. See Cannot Upgrade From 5.1.0.10 to 5.1.0.11 on Linux and Windows; Clean Install Required. |
Upgrade the firmware on the arrays after you install the Common Array Manager software on the management host. If you are adding new expansion trays, upgrade the firmware on the existing trays before you add the new trays to the array. See Upgrading Firmware for Adding Expansion Trays.
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 - An upgrade will fail for an array in a degraded state. |
Before you cable a newly supported expansion tray to an array, you must upgrade the existing controller and trays to Controller Firmware 06.19.xx.xx. If you want to add an existing expansion tray to a new array, it is also safest to install the new controller and trays first, complete the upgrade, add the existing expansion tray, and then upgrade the whole array again.
For adding trays to arrays managed by Sun StorageTek Common Array Manager Software:
1. Do not cable the additional expansion tray.
2. Install Release 5.1 or later following the standard installation procedure.
There are separate procedures for Solaris, Windows, and Linux management hosts. The software update places a copy of the latest firmware on the management software server.
3. Register the array, if needed.
The upgrade function is available as part of the Registration procedure or in the Sun StorageTek Common Array Manager software. The software prompts you if the array needs to update its firmware.
The firmware is installed on the array.
6. Use Service Advisor to cable the new expansion tray and add it to the array.
7. Upgrade the array again to update the firmware on the new tray.
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 6523157 - Common Array Manager does not distinguish between tray types. Now that it supports mixed tray type configurations, the Tray Summary/Details page needs to indicate the tray type of each tray.
Workaround - In mixed tray configurations, a user wishing to create a new VDisk spanning trays of different types should do as follows:
1. Use the manual creation mode in the volume creation wizard.
2. Instead of entering a number of disks, manually select the disks.
Bug 6522922 - Job completion and elapsed time estimates are not updating during unmapping operations.
Bug 6522808 - The Volume Copy job stops at 90% if the source volume is in the Degraded state.
Bug 6521739 - When a user tries to unmap the volumes from a Host or Hostgroup Details page, the message displayed afterward is "The selected objects were deleted". The correct message should be "All selected volumes/snapshots have been unmapped".
Bug 6521695 - The Common Array Manager navigation pane (left-side pane) sometimes fails to update when an array is added or removed.
Workaround - Reload the page by clicking on the Reload button on the browser.
Bug 6505546 - When multiple volumes are selected from the Volume Summary, the Common Array Manager is not able to map them to the default storage domain.
Workaround - If you are unable to map all of the volumes in one command, map them one at a time.
Bug 6441062 - At certain points in the upgrade during the registration process, the wizard reports an invalid password as valid. This can be confusing later on when the operation fails.
Workaround - Re-attempting the upgrade after it is registered will correctly report the invalidity of the password.
Bug 6504473 - While mapping to a host or host group, permission to a volume remains set to Read/Write even if set to readonly by the sscs map volume command.
Workaround - Change the permissions using the browser user interface.
Bug 6486712 - If the Storage Domains license is disabled the user can still create Host groups. They will be unable to map to them and get an error message when they try.
Workaround - The license must be added for mapping.
Bug 6475717 - On subnets with many arrays the registration wizard may time out when scanning the subnet.
Workaround - Remove any "web proxy" from the browser settings, or register arrays via IPs.
Bug 6438016 - Both the Remove and Upgrade buttons on the Storage Systems Summary page are highlighted, even when no array is selected. This issue occurs only on Mozilla 1.7 browsers.
Workaround - There are no adverse effects of having these buttons enabled with no array selected.
Bug 6356119 - When a user first logs into Common Array Manager and opens a help window, unexpected behavior occurs with the main application session: the main pane displays the Java Web Console app menu screen, instead of the proper page. Clicking on another node in the tree opens a new main window.
Workaround - Once the problem happens, return to the console and reenter the app. At this point, the help window will not interfere with the session. It only happens initially when first logging in the app and opening the help window.
Bug 6444324 - In the zh (Chinese) locale, when an installation is finished the results page shows garbled characters.
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 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 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 - The right-click and open page in new window or tab function is not supported. Do not use the right-click function.
This section describes issues related to Common Array Manager installation.
Bug 6527565 - On Linux and 64-bit Windows 2003 platforms, Common Array Manager cannot be upgraded from 5.1.0.10 to 5.1.0.11.
Workaround - On these platforms it is necessary to remove (uninstall) 5.1.0.10 first, then do a clean reinstall of 5.1.0.11.
When you install the Common Array Manager software for the first time, upon logging into the browser user interface, a registration page will display. Fill out the information before continuing.
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 6442868 - Common Array Manager cannot be installed in a non-global zone on early versions of 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 - Common Array Manager now supports Java Console 3.x. In Solaris 10 Update 3, Java Console is pre-installed. In earlier Solaris 10 versions, perform an upgrade of the Java Console to 3.0 or later in a global zone before installing the Common Array Manager. The Java Console 3.0 packages can be accessed from the extracted CAM distribution under /var/opt/CommonArrayManager/Host_Software_5.1.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 6518063 - When replacing an IOM unit after removing it earlier, the unit will will subsequently beep and restart the array.
Workaround - Remove the IOM and reinsert it.
Bug 6502481 - Reinserting two drives into two critical LUN will cause the system to rebuild only one of the LUNs. The other LUN will stay in the critical/degraded state.
Bug 6518942 - Whenever a LUN is mapped or unmapped and also when an AVT event occurs, the controllers host ports can reset the bus after the events occur. This occurs no matter how many volumes are already mapped to a host.
Bug 6509206 - When there is a power failure or a replacement of a power supply in a CSM200 tray, the event is not logged in syslog nor is there an email notice of the failure or replacement.
Bug 6490889 - When there is an over temperature alarm signaling on a 6140 array, there should be tray fault LED's shown. However, the tray fault LED's will not turn on, thus giving no visual signal of the over temperature alarm.
Bug 6503637 - MPP is only able to reconcile 2 out of the 4 LUNs when 4 initiators are assigned to 2 hosts on the same array.
1. Assign all 4 initiators to just one host.
2. Assign different LUN numbers to the volumes from each host.
3. Assign both hosts to a host group then map the volumes to that host group.
Bug 6517078 - The user gets an email message stating a log of a critical error that the filesystem is full. This message is sent in error because the filesystem is not full.
Bug 6520741- Can not restore LUN paths after removing controller B and reinserting it. An empty (ghost) LUN appears.
Workaround - This condition requires a service call.
Bug 6502481 - Removing multiple hotspare drives from a CSM200 tray and reinserting them can result in one drive causing its LUN to remain in a degraded state.
Bug 6486677- When creating another volume on the 6130 and mapping it to the host instead of the host group, the I/O terminates with errors.
Workaround: Map volume to corresponding host group instead of the host itself.
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. Installation of array hardware is now covered in Hardware Installation Guides for these arrays. 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.
The Common Array Manager online help refers to a default of 8 domains for 6140 and 6540 arrays. These arrays have only one default domain each, and it is not a storage domain. Normally storage domains are pre-purchased and installed at the factory with the array. Storage domains can be purchased in the following allotments:
Storage domains and other premium features require licenses. You can purchase additional domain and premium feature licenses at any time from your Sun Sales office.
This section describes known issues and bugs related to localization.
Bug 6498568 - Common Array Manager can not be installed on any non-English, fully localized version of Windows. It can be installed only on English base versions of Windows that have language packs.
Bug 6442523 - There are no localized versions of Java Web Console installable on Windows. Therefore a localized version of Common Array Manager cannot be enabled on a Windows server.
Workaround - Use the English version of the product on a Windows server.
Bug 6447044 - Non-ASCII characters are not supported in CLI commands.
Workaround - Use ASCII characters only in CLI applications and for array and volume names. Also, the CLI does not support double-byte character set array data, such as Korean. In cases such as this, use the browser user interface.
Bug 6495952 - SuSe Linux displays square for Chinese characters when installing the CAM 5.1 software. The same problem occurs on the pie charts after installation.
Workaround - Use Red Hat linux on server for Chinese or Japanese locale. There is no Java Asian support on SuSE linux.
Bug 6516766 - Localized characters are displayed as small squares on the pie charts when server locale is English.
Workaround - Use the supported locale for server.
Bug 6520459 - Service advisor files are partially translated for release 5.1.
This section provides useful operational information not documented elsewhere.
Firefox and Mozilla browsers on the same machine share session information among multiple tabs or browser windows when pointed to the Common Array Manager URL. For example, if you log in to Common Array Manager and then open another browser instance or tab pointed to the same URL, you access it through the same user session and you do not have to log in again. The Current Logins field in the Common Array Manager does not increment to include the new window as another login.
If you require a different user session, you must define a different profile or log in from a different machine. This does not happen with Microsoft Internet Explorer browsers, so you could also open a new session that way.
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.
|
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.
For array hardware information, refer to the array's release notes and hardware installation guide.
You can search for this documentation online at http://www.sun.com/documentation.
This section lists the firmware files included in the Common Array Manager 5.1, 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.
TABLE 8 lists the firmware files for the StorEdge 6130 Array included in this release. These files are located in /var/sadm/swimages/6130.
TABLE 9 lists the firmware files for the StorageTek 6140 Array included in this release. These files are located in /var/sadm/swimages/6140.
TABLE 10 lists the firmware files for the StorageTek 6540 Array included in this release. These files are located in /var/sadm/swimages/6540.
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, Release 5.1 | 820-0030-11 |
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.
To Upgrade the Array Firmware