| Sun StorageTek Common Array Manager Software Release Notes, Release 5.1.2 |    
|
| Sun StorageTek Common Array Manager Software Release Notes, Release 5.1.2 |
|
|
|
This document contains
important information about Release 5.1.2 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.2 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:
Common Array Manager software supports the following Sun storage systems:
This section describes the main new features of the firmware, including the following:
The following is the firmware for this release of Sun StorageTek Common Array Manager software.
Check the build notes file distributed with the software for the exact firmware build. The Sun StorageTek Common Array Manager software will support one prior version of the firmware for non-new features on previously supported arrays. (This does yet apply to the new Sun StorageTek 2500 Series Arrays).
The firmware files for each array are listed in Firmware Files.
For information about how to upgrade firmware, see Upgrading Array Firmware.
Controller firmware 06.19.25.10 or higher allows tray mixing of 6540, 6140 and 6130 array controllers modules and the Sun StorageTek CSM100 and CSM200 Expansion Modules. After installing the firmware, 6130 controllers can use CSM200 expansion modules and CSM100 expansion modules can be used with 6540 and 6140 controllers.
|
Note - To add trays with data already on them, contact your service representative for assistance to avoid data loss. |
Refer to Upgrading Firmware for Adding Expansion Trays for the procedure to upgrade trays without data.
TABLE 2 and TABLE 3 list the supported expansion modules.
|
Supported Expansion Modules with Controller Firmware 06.19.25.10 |
||
|---|---|---|
The Sun StorageTek 2500 Series Array uses Controller Firmware 6.17.52.10 and supports the Sun StorageTek 2501 expansion module.
The Sun StorageTek Common Array Manager software provides you with an easy-to-use interface to configure, manage, and monitor Sun StorageTek storage arrays.
New features in Release 5.1.2:
TABLE 4 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 licenses for 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:
The management software runs on the platforms described in TABLE 6.
|
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] |
||
|
Red Hat Enterprise Linux AS Release 4 (Nahant update 4) |
||
TABLE 7 lists Solaris packages that must be installed on your Solaris host. Installing the minimum Solaris operating system package as listed in TABLE 6 will install all but the last four files. Those files are required by Java, but are not used by the management software.
|
X Window System & Graphics Runtime Library Links in /usr/lib |
TABLE 8 lists Linux packages and libraries that must be installed on your Linux host. The 32-bit versions of the packages and files are required.
The following table lists the disk and directory space requirements of the management host software.
|
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[2] |
||
Open the following ports for secure-by-default Solaris, Linux, and Windows platforms. In Windows, refer to your firewall documentation for instructions on how to open a port through the firewall.
TCP 6788 - console http port which redirects to 6789
TCP 25 - SMTP used for email event notification from FMS
UDP 161 - SNMP used for event notification traps from FMS
TCP 2463 - used for RPC (remote procedure calls) with the arrays
The remote scripting CLI client sends commands to a management host, which in turn sends the commands to the array. TABLE 10 lists remote platforms that can run the CLI client.
The Sun StorageTek Common Array Manager software supports the web browsers listed in TABLE 11.
|
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
management software is distributed on the Sun StorageTek Common Array
Manager Software CD or is available from the Sun Download Center: http://www.sun.com/download/
(look for Systems Administration>Storage Management).
Be sure to do the following before performing the upgrade:
Before starting the installation script, the CD verifies host requirements. such as
If the host meets the requirements, the script 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.
Solaris: Upgrade from CAM 5.0.1.1, 5.0.2.1, 5.1.0.10, and 5.1.0.11 to this release is supported. Uninstalling the existing CAM version is not required to install this release.
Linux: Upgrade to the initial release of the Linux version is not needed.
Windows: Upgrade to this build is not supported in 64-bit Windows 2003. Uninstall of previous CAM version is required before installing this build in 64-bit Windows 2003. In other Windows platforms, upgrade to this build is supported.
This procedure uninstalls the previous CAM version if the upgrade to the current CAM version is not supported.
1. Log into the CLI on the management host or using the remote CLI client as documented in the Sun StorageTek Common Array Manager Software Installation Guide.
2. Enter the command uninstall -f.
The command will remove the current installation.
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 you are installing the management software on a new host, 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.
The installer also installs the firmware update bundle on the host server. To upgrade the firmware on the array, see Upgrading Array Firmware.
The upgrade function is available as part of the Registration procedure for new arrays or as a separate feature in the Sun StorageTek Common Array Manager software. The software prompts you if the array needs to update its firmware.
If you are adding new expansion trays, 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.
1. Log into the management software as documented in the Sun StorageTek Common Array Manager Software Installation Guide.
2. On the Java Web Console page, click Sun StorageTek Common Array Manager.
3. Go to the Storage System Summary page and select the arrays to be upgraded.
4. Click the Upgrade Firmware button.
|
Note - An upgrade will fail for an array in a degraded state. |
Controller firmware 06.19.nn.nn allows tray mixing of array controllers modules and two versions of expansion modules for the Sun StorageTek 6130, 6140, and 6540 Arrays.
|
Note - Mixing trays is not supported for the Sun StorageTek 2500 Series Arrays. |
Refer to TABLE 3 for a list of a list of the supported modules for intermixing trays without data.
|
Note - To add trays with data already on them, contact your service representative for assistance to avoid data loss. |
To add a newly supported expansion module to an existing array
To add an existing expansion tray to a new array, it is also safest to follow a similar procedure:
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.
|
Note - For CSM100 trays, the tray IDs need to be set manually. |
The upgrade function is available as part of the Registration procedure or as a separate feature 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 additional 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 6544481 - The wrong tray type, SS3600, for 2500 Series Arrays displays in the management software. The can be especially confusing on the new array information screen that displays when a new array is registered in the management software.
Workaround - Refer to the packing list shipped with the array if you need to check the tray type.
Bug 6503775 - When a user attempts to modify the host name on a busy array (higher than average I/O cycles), the host name may change but an error message is still returned.
Workaround - Turn off proxies. For example, in Mozilla the proxy setting is "no setting" or "direct connection to internet."
Bug 6537131 - When the management software lists a disk as failed and the Service Advisor procedure for replacing drives is followed, the step to verify that the disk is ready to remove may not list the failed disk.
Workaround - Use an alternative menu option, Array Troubleshooting and Recovery, to view the status of the disk.
Bug 6536982 - The disk replacement procedure in Service Advisor needs a step to verify drive status before firmware upgrade.
Workaround - After disk is replaced, the disk will be in non-optimal status while reconstructing volume. Wait and verify that the drive status is Optimal from the Physical Devices - Disks page before starting firmware upgrade.
Bug 6521775 - The software allows you to give the same name for the Snapshot name and the Reserve Volume name in the Snapshot Create window.
Workaround - Do not enter he same name for the Snapshot name and the Reserve Volume name in the Snapshot Create window.
Bug 6503775 - When a user attempts to modify the host name on a busy array (higher than average I/O cycles), the host name may change but an error message is still returned.
Workaround - Turn off proxies. For example, in Mozilla the proxy setting is "no setting" or "direct connection to internet".
Bug 6516228 - When an array is in "Loss of Communication" state, using an asterisk (*) in the search window causes an error.
Workaround - Connect the array to the network before using the search feature (or any other management feature) of Common Array Manager.
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.
Workaround - The job will still complete.
Bug 6522808 - The Volume Copy job stops at 90% if the source volume is in the Degraded state.
Workaround - Correct the degraded state before copying a volume.
Bug 6521739 - When a user unmaps 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 navigation pane (left-side pane) sometimes fails to update when an array is added or removed.
Workaround - Reload the left frame of 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 may report 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 settings from the browser preferences, or manually register an array using the IP address.
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 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 - The browser function to right-click the mouse and open a page in a new window or tab function is not supported and can display the wrong page.
Workaround - Do not use the right-click function to open in a new window or tab.
Bug 6544649 - Reliability Reporting service selection is listed on the Sun Connection registration window, but is not supported. Do not check this feature.
This section describes issues related to Common Array Manager installation.
Bug 6425924 - In Windows, you are unable to install Java Web Console with a directory or file name that has white spaces.
Workaround - Remove spaces from affected directories and filenames.
Bug 6465219 - When an install fails because there is not enough disk space, there is no indication why it failed other than that InstallShield suddenly starts its rollback process to return the host to its pre-install condition and reports that the installation was cancelled. No specific messages about the disk/filesystem being full are displayed or written to the install log.
Workaround - Ensure that there is sufficient space available on the host machine to perform a full install of the Common Array Manager package. See File Space Requirements.
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 Common Array Manager 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 Common Array Manager 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 - While multiple management stations can access the array, the array reservation message only appears on the local host.
Workaround - Co-ordinate with users of other management stations before you make changes that affect array operations to prevent conflicting configuration changes.
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 LUNs 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 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.
Workaround - Perform the following:
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 system can send email message stating a log of a critical error that the filesystem is full, even though 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 former Getting Started Guide for the 6140 array is no longer valid for 5.x Releases and 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.
The storage profile summary shown in Table 5-1 in the Common Array Manager Software Installation Guide needs to be updated with the following table:
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 eight domains for 6140 and 6540 arrays. Only the 6130 array has a default of eight domains. The 6140 and 6540 arrays have only one default domain each, and it is not a storage domain. 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.
Workaround - Install the English version of the Windows server with the appropriate language pack.
Bug 6442523 - There are no localized versions of Java Web Console that can be installed 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 Common Array Manager 5.1 software. The same problem occurs on the pie charts after installation.There is no Java Asian support on SuSE Linux.
Workaround - Use Red Hat Linux on server for Chinese or Japanese locale.
Bug 6444324 - In the zh (Chinese) locale, when an installation is finished the results page shows garbled characters.
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.2.
This section provides useful operational information not documented elsewhere.
Each release or patch of the Sun StorageTek Common Array Manager software spools the latest firmware on the management host during the software or patch installation. When you upgrade firmware from the management software, the software recommends needed upgrades and installs the new firmware on the array from the spooled firmware on the host.
In the unlikely event that updating the firmware on an array results in a performance or operational issue, you may want to revert back to the previous version of the array firmware by either rolling back to the previous version of the management software or backing out the firmware patch and then performing the update array function.
Such rollbacks or backouts must be planned in advance and implemented using tools and functions of the operating system on the management software host.
Each host platform that supports the Sun StorageTek Common Array Manager software offers its own facilities and methods (some by third party) for applying and backing out updates to installed software. On Solaris, for example, Live Upgrade can be used to perform upgrades of installed software such that the user can revert back to the previous version of the software by re-activating the previous environment and rebooting. Solaris also can apply and backout patches through the use of the patchadd and patchrm commands.
Refer to the operating system documentation for more information about implementing software rollback features. Such practices should be part of comprehensive software lifecycle management procedures and polices for your production environment.
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.
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.
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.2, 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 13 lists the firmware files for the StorEdge 6130 Array included in this release. After you install the CAM software, these files will be located in:
TABLE 14 lists the firmware files for the StorageTek 6140 Array included in this release. After you install the CAM software, these files will be located in:
TABLE 15 lists the firmware files for the StorageTek 6540 Array included in this release. After you install the CAM software, these files will be located in:
TABLE 16 lists the firmware files for the StorageTek 2540 Array included in this release. After you install the CAM software, these files will be located in:
TABLE 17 lists the firmware files for the StorageTek 2530 Array. After you install the CAM software, these files will be located in:
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.2 | 820-2128-10 |
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.
To Uninstall a Previous CAM
Version