| Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.1 |     |
| Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.1 | |
|
Sun StorageTek Common Array Manager Software Release Notes |
This document contains important information about Release 6.0.1 of the Sun StorageTek
Common Array Manager software, including issues and requirements that can affect installation and operation.
These Release Notes include the following sections:
The Sun StorageTek Common Array Manager software provides an easy-to-use interface from which you can configure, manage, and monitor Sun StorageTek storage arrays.
TABLE 1 lists the version information for the software included in this release.
|
Firmware files, as listed in Firmware Files |
|
To use optional premium features, you must purchase licenses. When you order licenses, they will be sent to you with instructions on how to activate the features. For more information, search for these topics in the online Help:
The following licenses for premium features are available from Sun:
|
Combo Data Snapshot, Data Volume Copy, Data Replicator, and 64 Domains |
|||||||
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 hardware information, refer to the array’s release notes and hardware installation guide. You can search for this documentation at http://www.sun.com/documentation.
System requirements for the Sun StorageTek Common Array Manager software are described in the following sections:
Common Array Manager software supports the following Sun storage systems:
New to the Sun StorageTek CAM software in release 6.0.1 is Internet Small Computer Systems Interface (iSCSI) support for the Sun StorageTek 2510 storage system. Initiators are the clients of the iSCSI interface, issuing requests for services from components or logical units called targets. One iSCSI target is supported per array.7
The iSCSI port is used for communication between the iSCSI initiator and the iSCSI target. The array supports two iSCSI ports per controller, for a total of four per array.
An iSCSI session consists of up to four connections between an initiator and its target. The iSCSI initiator and target send and receive data over an Ethernet connection, using the SCSI protocol. Across all connections within a session, an initiator sees the same target. Multiple initiators may be connected to the iSCSI target.
| Note - For initial installation and configuration of iSCSI on the 2510, see the Sun StorageTek 2500 Series Array Installation Guide. |
| Note - For the complete list of drives, refer to Table 5 in the Sun StorageTek 2500 Series Array Release Notes, Version 1.3. |
Consult the Sun StorageTek Common Array Manager software online Help for further information and procedures, such as configuring iSCSI targets and ports, mutual authentication for an iSCSI session, unnamed discovery sessions, and Internet Storage Name Service (iSNS), and more.
CAM software runs on the platforms described in TABLE 3.
|
Windows 2000 with Service Pack 4 Windows 2003 with Service Pack 1 Windows XP Pro with Service Pack 2[1] |
|||
|
Red Hat Enterprise Linux AS Release 4 (Nahant update 4) Red Hat Enterprise Linux AS Release 3 (Taroon update 8) |
|||
TABLE 4 lists Solaris packages that must be installed on your Solaris host. Installing the minimum Solaris operating system package as listed in TABLE 3 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 5 lists Linux packages and libraries that must be installed on your Linux host. The 32-bit versions of the packages and files are required.
For the latest patches available for your system, check SunSolve at http://www.sunsolve.sun.com
TABLE 6: lists the patch numbers and corresponding platforms.
TABLE 7 lists the disk and directory space requirements.
|
Windows 2000 with Service Pack 4 Windows 2003 with Service Pack 1 Windows XP Pro with Service Pack 2[2] |
||
Open the following incoming and outgoing 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 that 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 command-line interface client sends commands to a management host, which in turn sends the commands to the array. TABLE 8 lists remote platforms that can run the CLI client.
TABLE 9 lists supported browsers.
For best web browser performance while using the Sun StorageTek Common Array Manager software, do the following:
For Solaris, Linux and Windows, the browser user interface for the Sun StorageTek Common Array Manager is available in:
The command-line interface is available in:
The online Help is available in:
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:
Before you perform an installation procedure, do the following:
1. Locate the management software.
The management software is distributed on the Sun StorageTek Common Array Manager Software CD and is also available from the Sun Download Center (Systems Administration > Storage Management) here: http://www.sun.com/download/
2. Locate the most current patches.
For the latest patches available for your system, check SunSolve at http://www.sunsolve.sun.com
3. Verify that you have license certificates for all premium features, including storage domains.
See Licensing Optional Premium Features.
4. Read the installation instructions.
See your Sun StorageTek Common Array Manager Software Installation Guide (part number 820-0213-nn)
5. Log in as root (Solaris and Linux) or as a user with administrator privilege (Windows) on the management host.
6. Note that before starting the installation script, the CD verifies host requirements, such as the following:
If the host meets the requirements, the script will search for earlier versions and determine if a new installation or an upgrade/baseline installation is necessary. If the script detects that there is no earlier version installed, it will perform a complete new installation.
| Note - Before you install CAM in a sparse-root zone, install Lockhart 3.0.4 with its L10N packages in the global zone. |
Solaris: Upgrades from CAM 5.0.0.8, 5.0.1.1, 5.0.2.1, 5.1.0.10, 5.1.0.11, 5.1.1.2, 5.1.2.2, and 5.1.3.2 to this release are supported. You are not required to uninstall the existing CAM version before installing 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.
If installation failure occurs, check the available disk space.
For more information, consult the installation log:
Solaris: /var/sadm/install/se6000/se6000_Host_SW.log
Linux: /var/opt/cam
Windows: \Program Files\Common Files\Sun Microsystems\se6000
1. Log in to the CLI on the management host or using the remote CLI client as documented in the Sun StorageTek Common Array Manager Software Installation Guide (part number 820-0213-nn).
2. Navigate to the appropriate directory for your operating system:
%systemdrive%\Sun\CommonArrayManager\Host_Software_6.0.0.10\bin\uninstall.bat
For Solaris and Linux, navigate to:
/var/opt/CommonArrayManager/Host_Software_6.0.0.10/bin/uninstall
For the Suse 9 platform, CLI uninstall requires the following rpm packages:
3. Enter the command uninstall -f
The command will remove the current installation.
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 (part number 820-0213-nn).
After initial installation and configuration, you can 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 / Installing the Firmware Baseline.
You can perform a minimal installation that enables only command-line interface (CLI) functionality. This feature is new in release 6.0.1. Array firmware files are not installed with this option. Because firmware is not installed, the firmware analysis feature is not available with this installation.
The CLI in previous versions of Sun StorageTek Common Array Manager software required the web server in order to run. Minimal installation does not require the web server to be running in order to function and is limited to calls on the management host where the management software is installed.
The sscs command behaves normally, with the following exceptions:
1. From the Common Array Manager Installation page, select one of these options in the Select a feature bundle list:
2. Click Next and follow the prompts by pressing 1 for Next, 3 to Cancel, or 5 to Redisplay.
The software will notify you as it checks your system and does any or all of the following:
The system will notify you that the installation has been successful.
3. Press 3 to Finish or 5 to Redisplay.
1. From the host software installer, select Uninstall.
2. Click Next and follow the prompts by pressing 1 for Next, 3 to Cancel, or 5 to Redisplay.
The software will notify you as it checks your system and does any or all of the following:
The system will notify you that the un-installation has been successful.
3. Press 3 to Finish or 5 to Redisplay.
This section describes the main features of the firmware, including the following:
To add trays with data already on them, contact your service representative for assistance to avoid data loss.
Refer to Upgrading Firmware for Additional Expansion Trays for the procedure to upgrade trays without data.
Controller firmware 06.19.x.x or higher allows tray mixing of 6540, 6140, 6130, FLX240, FLX280, and FLX380 array controllers modules and the Sun StorageTek CSM100, CSM200, FLA200, FLC200, and FLA3 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.
When you add a new CSM200 expansion module to an existing array in a production or active environment, it is best practice to cable and add the trays while the RAID controller module is powered on.
Before connecting any replacement drive or additional expansion module to an existing functioning array, it is best practice to contact Sun Microsystems Support Services. One reason for this is to avoid issues related to DACstore, the configuration and status database maintained by the array firmware, that stores its information on each of the disk drives.
Because corrective actions for a DACstore issue may require a configuration restoration, it is important to maintain a current image of the configuration. And, as always, it is best practice to maintain recoverable backups of your data.
Contact Sun Microsystems Support Services promptly upon experiencing any of the following symptoms:
TABLE 10 and TABLE 11 list the supported expansion modules.
|
Supported Expansion Modules with Controller Firmware 06.19.25.16 |
||
|---|---|---|
The Sun StorageTek 2500 Series Array uses Controller Firmware 6.17.52.10 and supports the Sun StorageTek 2501 expansion module.
The Sun StorageTek FLX240, FLX280, and FLX380 arrays use Controller Firmware 6.19.25.26 and supports the CSM100, CSM200, FLA200, FLC200, and FLA300 expansion modules.
For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com.
Common Array Manager firmware is installed in the following locations:
Within the directory where you installed the firmware, a README file for each array type define the firmware baseline.
Firmware files are located in the /images subdirectory.
TABLE 13 lists 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 legacy features on previously supported arrays. (This does yet apply to the new Sun StorageTek 2500 Series Arrays).
For information about how to install firmware, see Upgrading Array Firmware / Installing the Firmware Baseline.
The firmware files for each array are listed in Firmware Files.
For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com.
In the following tables, the file path listed in the Firmware File column (for example, nge/RC_0617xxxx.dlp) is the relative path to the /images subdirectory where the firmware files are located.
TABLE 14 lists the controller information for the Sun StorageTek 2500 arrays:
TABLE 15 lists the NVSRAM information for the Sun StorageTek 2500 arrays:
TABLE 16 lists the IOM information for the 2500 Series Arrays:
TABLE 17 lists the disk drive information for the 2500 Series Arrays:
For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com.
TABLE 18 lists the controller information for the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 19 lists the NVSRAM information for the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 20 lists the IOM information for the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 21 lists the disk drive information for the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
The Install Firmware Baseline function is available as a separate feature in the Sun StorageTek Common Array Manager software. The software prompts you when the array’s firmware needs to be upgraded. It is not necessary to uninstall the existing firmware before following this procedure.
If you are adding new expansion trays, see Upgrading Firmware for Additional Expansion Trays.
Prerequisite: Before you perform this task, be sure the array is not in a degraded state. If it is degraded, the upgrade will fail.
1. Log in to the management software as documented in the Sun StorageTek Common Array Manager Software Installation Guide (part number 820-0213-nn).
2. From the Java Web Console page, click Sun StorageTek Common Array Manager.
3. From the Storage System Summary page, select the array for which the firmware needs to be installed/upgraded.
4. Click the Install Firmware Baseline button, and follow the prompts.
Controller firmware 06.19.nn.nn allows tray mixing of array controllers modules, two versions of expansion modules for the Sun StorageTek 6130, 6140, and 6540 arrays, and the FLX240, FLX280, and FLX380 arrays.
A patch is available for Release 6.0.1 that adds support for a third expansion tray and 48 drives. Cabling instructions for the third expansion tray have not yet been added to Sun StorageTek 2500 Series Array Hardware Installation Guide or Service Advisor in the Sun StorageTek Common Array Manager software.
The patches are available from the Sun Download Center: http://www.sun.com/software/download/
| Note - Before installing the 48-drive patch, be at the firmware baseline of 06.70.42.10. |
Prerequisite: Before discovering a Sun StorageTek FLX240, FLX280, FLX380 array using Common Array Manager and before performing any tray migration (for example, adding FLA300 expansion trays behind an existing 6130, 6140 or 6540 controller), you must use existing management software to upgrade the arrays and associated trays to the firmware version 6.19.25.00. After you register the arrays using Common Array Manager, you can upgrade to the current baseline firmware, 6.19.25.26.
To add a newly supported expansion module to an existing array:
1. Before cabling the newly supported expansion module, upgrade the existing controller and trays.
To add an existing expansion tray to a new array, it is safest to follow a similar procedure:
1. Install the new controller and trays.
2. Perform the firmware upgrade.
For adding trays to arrays managed by Sun StorageTek Common Array Manager Software:
1. Do not cable the additional expansion tray.
2. Install the Common Array Manager release following the standard installation procedure.
3. Register the array, if needed.
4. From the Storage Summary page or Array Administration page, click the Install Firmware Baseline button.
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.
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 register an array with the management software, it sends an alarm if you need to upgrade/install the baseline for the firmware. To begin the procedure: From the Storage System Summary page or Array Administration page, click the Install Firmware Baseline button. (For more information, see Upgrading Array Firmware / Installing the Firmware Baseline).
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. 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 policies for your production environment.
The following sections provide information about known issues and recommended workarounds, as well as operational information not found elsewhere in the documentation:
Bug 6590617 -Since the Sun StorageTek 6130 array does not report asset data for the cache backup batteries, the management software inserts a dash (-) instead of a value in the Unique Identifier field on Component Summary for Battery page (Troubleshooting > FRUs > Battery).
Workaround - Use the sscs CLI service command to manage data channels 3 and 4.
Bug 6621713 -The first step of the array registration wizard has changed from “Scan Network” to “Scan Local Network” and the auto-discovery mechanism has been improved to be faster and more versatile. The system scans the local network for available storage systems that are not yet registered. This shortens the time it takes to scan the local network for storage systems, depending on the given IP addresses. When the process is complete, a list of discovered storage systems is displayed.
Bug 6590637 -Attempting to modify the Cache Start% and Cache Stop% parameters from the array’s Administration page so that the value assigned to Cache Stop% is greater than the value assigned to Cache Start% results in the error message “setCacheParams operation failed:43”.
Workaround - Use valid values. Since the Cache Stop% is the percentage of unwritten data in the cache that will stop a cache flush that is currently in progress, it must not be greater than the value for Cache Start%, which is the percentage of unwritten data in the cache that will trigger a cache flush.
Bug 6600387 -Some jobs, like volume creation jobs, cannot be cancelled on the array once they have started. However, if multiple jobs are queued up for an array, any job in the queue can be cancelled before the array actually starts the job.
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.
Controllers Reboot when Collecting Support Data
Bug 6649629 -When data is collected and a drive is by-passed, one or both controllers might reboot. This can also happen when an array (containing a drive that was part of a virtual disk) is removed while support data is collected. When support data is captured, satecapturedata.dmp file is also captured. This .dmp file contains a set of shell commands that are run on the controller. The “hids 108” command, added in release 6.0, can reboot the controller when run while a drive in a system is by-passed, or when a drive that was part of a virtual disk is physically removed.
Workaround - Avoid collecting support data during times of heavy use. The controller reset will only occur upon the capture of the support data. Individual collections of Alarms, Array Profiles, and Major Event Logs are possible within each of the management utilities. There is no completely successful workaround at this time and this issue remains under investigation.
Bug 6592811 -For small virtual disks, disk defragmentation jobs may complete too quickly for a job task to be created and listed on the Jobs Summary page. If an error does occur during execution, the user will be notified.
Workaround -Run defragmentation jobs using the CLI.
Bug 6515237 -Common Array Manager does not allow the disk drive order to be specified during volume creation.
Workaround - Use the CLI to specify disk drive order.
Bug 6498717 -When creating a data replication set, if the primary array cannot communicate with the secondary array, a misleading error message displays stating that it is “unable to get volume candidate list from array.”
Workaround - Verify that the arrays can communicate before replicating data.
Bug 6590097, 6577775, 6592717, 6592703 -Using an invalid array password may result in configuration error messages.
Workaround - Use the correct array password.
Bug 6661200 - Lockhart 3.0.4 cannot be installed or upgraded in a sparse-root zone.
Workaround - Before you install CAM in a sparse-root zone, install Lockhart 3.0.4 with its L10N packages in the global zone.
Bug 6600387 - When a long job is running, such as large volume creation, the Cancel checkbox does not display on current job status. Some jobs cannot be cancelled once they have started on the array.
Workaround - If the queue includes multiple jobs for the array to perform, the job can be cancelled at the point where the GUI sends the next job to the array.
Bug 6650124 -Sometimes the link status of all ports (A1, A2, A3, B1, B2, and B3) when viewed by CAM are reported as down when they are functioning properly. This was tested with CAM Build 6.0.1.10 and ST2530.
Workaround - This bug is fixed in CAM Build 6.0.1.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.
During the initial storage array registration process, Common Array Manager prompts you to register with the Auto Service Request service by displaying the Auto Service Request (ASR) Setup page. This page continues to display until you either fill out the page and click OK, or click Decline to either decline or defer ASR service registration.
| Note - You must register the array with ASR before using the Test button. |
Bug 6602902 -When a virtual disk is in a failed state and the drive causing the failure has been replaced, for the recommended action, the management software refers the user to access Service Advisor to initialize the disk. However, Service Advisor does not contain information about disk initialization and the link erroneously accesses the Collect Support Data page.
Bug 6604026 -Data channels 3 and 4 cannot be managed using Service Advisor; only channels 1 and 2 are available for management.
Bug 6569930 -Attempting to reset the array configuration while a volume has a persistent reservation appears successful; however, the job status displays as in error, indicating that the configuration reset failed.
Workaround - Release the persistent reservation on the volume and retry the array configuration reset.
Bug 6577194 -The sscs CLI client does not allow mapping to the access volume for in-band management.
Workaround -To map the access volume, use the Common Array Manager.
Bug 654985 -In the sscs CLI, special shell characters (or phrases that use them) have to be enclosed in double quotes.
For Windows only, the comma (,) is a special character. Options separated by commas should be enclosed in quotes, as shown in the following example:
sscs create -p Default -s 100MB -d "t1d01, t1d02, t1d03" volume dhamo_new_vdisk
Bug 659945 -Logging into the sscs CLI client remotely may fail when a Solaris machine is configured to use NIS for name resolution if the login host is not contained in the NIS map.
Bug 661094 -The sscs manpage was delivered only on the Solaris platform.
Workaround -Refer to the CLI Quick Reference Guide for a command list and command syntax.
Bug 6587666 -The CLI command sscs list fru does not list the number of fans installed on the Sun StorageTek FLX240 and FLX280 arrays.
Workaround -Use the Common Array Manager to view the number of fans installed.
Bug 6584193 -Although type generic and type vlac are listed as options with the CLI sscs switch command, these options are not yet implemented.
Bug 6597344 -Clicking the Test Communications button for an offline controller may erroneously report that the communications test has passed.
Workaround -Verify a controller’s offline state by viewing its alarms.
Bug 6529172 -A snapshot volume that is disabled can be automatically reenabled after a firmware update occurs. If the snapshot volume is full, it can start generating warning events.
Workaround-Disable the snapshot again after the firmware update.
Bug 6612858 -The Event list from two different hosts against the same array shows different events, even though the alarms generated are consistent.
Workaround -To display results based on the polling frequency and polling times of the arrays, select the Advanced Aggregation Filter option from the CAM Events page. When this option is de-selected, all hosts show consistent output. Therefore, this is working as designed.
Bug 6595884 -A firmware upgrade/baseline installation can lock volumes longer than the process indicates. The array can report the upgrade completed and show an optimal state but the process can still lock the volumes.
Workaround -Wait an extra five to ten minutes and try again.
Bug 6608890 -The array is limited in commands it can process simultaneously and CAM is not doing validation and queuing of (primarily volume create) commands.
Workaround -Check scripts for volume modification status before you issue new volume modification commands.
Bug 6596281 - If a data replication set is created between two volumes with the primary volume having a size less than the secondary volume, the primary volume can be expanded till it reaches the size of the secondary volume.
Bug 6561709 -When the primary volume in a replication set fails, the management software may incorrectly list the volume as replicating.
Bug 6501029 -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 6523608 -Refreshing a snapshot does not update the filesystem if there is insufficient reserve space, yet a message displays indicating success. The array’s event log says the resnap completed successfully.
Workaround -In the snapshot feature of the management software, configure snapshots to fail if sufficient reserve space is not available. The fail message will prompt you to increase the reserve space.
Bug 6560461 -Although both the base volume and the snapshot reserve volume support read-ahead, the snapshot volume itself does not support read-ahead. As a result, the Read-ahead Enabled Option is set to False on the Snapshot Details page.
Bug 6599933 -Changing a volume created with a one segment size to one with a different segment size requires that you create a new profile with the desired segment size, create a pool using that profile, and apply the new pool to the volume. However, if the original profile was created using a fixed number of disks instead of a variable number of disks, then an error is returned.
Workaround -Adjust the new profile so that the number of disks is variable instead of fixed.
Sun StorageTek 2500 series does not support volume-copy. Any instances in the user interface or documentation that imply there is a command or function for this task are misleading.
Bug 6665635 -Creating volumes with sizes that contain a fraction does not work in locales using a comma as decimal point. The check for a legal numeric value is not localized, but the interpretation of the number afterwards is. If you correctly enter the locale with a comma as 17,352, you will get this error message: “You must provide a numeric capacity value.”
Example -When you create a volume with 17.352GB under the standard “en” locale, you can enter the size as 17.352 and select GB as unit. However, under the “de” locale, the dot is interpreted as 1000-separator. A 17.352 size with a 1GB unit would try to create a ~17 TB volume and likely fail with this error message: “The size entered for the new volume exceeds the maximum space available on the selected pool.”
Workaround -For GB and TB values you can multiply by 1024 and enter as MB or GB.
Bug 6598844 -Members of a replication write consistency group should all have matching attributes and roles.
Bug 6599146 -Although the CLI command sscs map initiator is listed in the CLI manpage, it is not implemented. And, although the CLI manpage lists the -i option for use with the CLI commands sscs map volume and sscs map initiator, this option is not yet implemented.
The CLI Quick Reference Guide and the CLI manpage docs do not specify that when using the -p option with the sscs modify firmware command, you must supply the file path of the firmware image file.
Bug 6592776 - The manpage for the CLI command sscs modify volume should define the usage for the -c option, which enables you to select a controller, as follows:
In “list firmware,” “-x unit-type” should be “-x fru-type.”
In synopsis and options, fru-type and unit-type are used in an interchangeable way. For both -t and -x, use “fru-type” instead of “unit-type” to be consistent.
Bug 6592877-When a drive fails, the volume group to which it belongs is no longer redundant. A stand-by hot-spare drive is chosen and integrated into that volume group automatically if possible.
The drive is chosen to satisfy the following conditions:
Bug 652123 -All documentation might not yet reflect changes made in the graphical user interface for release 6.0.1. Mainly, the “forced firmware upgrade” option has been removed, and the term “Upgrade” has been replaced with “Install,” as described in the following instances:
Page 44 of the Sun StorageTek Common Array Manager Software Installation Guide, v.6.0 ((part number 820-0213-nn) should state:
“...remotely logging in to a management software station or by using the SSCS remote client on a remote host.” The Installation Guide currently says “Solaris” instead of “SSCS.”
Bug 6593949 -The online Help does not provide a description for the Type field on the Snapshot Summary page. The Type field refers to the model number of the array. For example, 6140, 6130, 6540, 2530, 2540, FLX240, FLX280, FLX380, etc.
Some distributed versions of the Sun StorageTek Common Array Manager CLI Quick Reference had the wrong paths to the SSCS CLI command line.
These paths should be stated as follows:
Solaris: /opt/SUNWsesscs/cli/bin/sscs
Linux: /opt/sun/cam/se6x20/bin/sscs
Windows:
%Program Files%\Sun\Common Array Manager\Component\sscs\bin
Bug 6540170 - Common Array Manager can be used to create up to 1022 volumes (volumes 0 through 1021) on the Sun StorageTek 6130 array. However, if the Access LUN is in use, up to 1023 volumes (volumes 0-1022) can be created. If you attempt to create more than the supported number of volumes, an error message is returned.
Sun StorageTek 2500 series does not support volume-copy. Any instances in the user interface or documentation that imply there is a command or function for this task is misleading.
Bug 6593508 - The review step of firmware Install wizard might display a false warning that the array health is not optimal.
Workaround -Check the Alarm Summary page to verify the alarm.
In-band management is supported on the Sun StorageTek 6130, 6140, 6540, 2530 and 2540 arrays. Whereas release 6.0.0 of the Sun StorageTek Common Array Manager software was only qualified with Solaris (SPARC) and Linux (5.1) agents, release 6.0.1 has added in-band management support for Solaris x86 and Windows.
The in-band management proxy agent is a package which is added to a host (or group of hosts) with in-band connectivity via Fibre Channel to the storage array. An external management station can then talk to this proxy host via an out-of-band connection and the management commands are then relayed to the storage device via the in-band path. This is a transparent proxy agent which simply converts the RPC request packets to UTM SCSI- specific messages. The API CAM uses to manage the arrays is identical whether the array is managed via the in-band or out-of-band path.
Multiple in-band proxy hosts may be used to access the same array and multiple arrays are allowed behind a single proxy host.
Installation of the proxy agents is accomplished via the standard package addition tools inherent to the specific operating system. For example, the pkgadd(1M) command would be used to install the Solaris agent and the associated Java Runtime package should also be installed. For Linux, the packages are RPM based and a runtime package is also needed. For windows, the installation packages are executable files that include their own “Install Anywhere” installer.
A proxy agent restart is required after disruptive changes to the storage configuration. This does not apply to changes in volumes exposed from a single array but it does apply if storage arrays are re-cabled differently or if the storage array configuration has changed (i.e. adding new storage arrays to the configuration).
The in-band proxy agents will start when the host boots, but they will terminate if storage is not immediately seen. A restart of the agent (instructions below) will force a re-scan for storage arrays and, if any are found, the agent will remain running.
Download CAM in-band proxy agents for Solaris from here:
http://www.sun.com/download/products.xml?id=471e7573
To verify the host sees the arrays management (UTM) LUN, do the following:
1. Start / Stop the Agent (Solaris):
If the agent is already running, this will stop and then restart it.
2. Check the status of the agent:
# ps -ef | grep SMagent | grep -v grep
root 5144 1 0 11:58:24 pts/3 0:01 /opt/SMgr/agent/jre/bin/java -classpath
/opt/SMgr/agent/SMagent.jar devmgr.launch
| Note - The SMagent requires Red Hat 5.1 (also known as “5 update 1”) or higher. It is not supported on Red Hat 5.0. |
Download CAM in-band proxy agents for Linux here: http://www.sun.com/download/products.xml?id=471e7573
To verify the host sees the arrays management (UTM) LUN, do the following:
[root@nsvr-150 agent]# /opt/SMgr/agent/SMagent start
[root@nsvr-150 agent]# SANtricity Storage Array Host Agent, Version 09.17.A0.03
Built Tue Dec 05 14:52:38 CST 2006
Copyright (C) 1999-2006 LSI Logic Corporation. All rights reserved.
Checking device /dev/sda (/dev/sg0): Skipping
Checking device /dev/sdb (/dev/sg1): Skipping
Checking device /dev/sdc (/dev/sg2): Activating
[root@nsvr-150 agent]# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep “Volume Access” /dev/sdc
(/dev/sg2) [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
| Note - Support for the Windows proxy agent is not qualified in CAM 6.0.1. |
To verify the host sees the arrays management (UTM) LUN, do the following:
E:\Program Files (x86)\StorageManager\agent>net start “SANtricity Storage Manager Agent”
The Storage Manager Agent service is starting.
The Storage Manager Agent service was started successfully.
E:\Program Files (x86)\StorageManager\agent>C:\Java\jdk1.5.0_11\bin\java -classpath SMagent.jar devmgr.versioned.agent.DeviceIdentifier |
\\.\PHYSICALDRIVE0 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>]
\\.\PHYSICALDRIVE1 [Storage Array fms-lca1, Volume Access, LUN 31, Volume ID <600a0b80002fc074
Bug 6584815 -When an access LUN is mapped to a proxy agent host for in-band management use, you must correlate the mappings between the LUNs and the host by using the format command at the UNIX prompt. The system will list the access LUNs and the array ports from the UI or the CLI, and it will then compare the results.
7. c8t0d31 <SUN-UniversalXport-9617 cyl 8 alt 2 hd 64 sec 64>
/pci@8,700000/fibre-channel@2/fp@0,0/ssd@w200500a0b82fbc3c,1f
13. c9t0d31 <SUN-UniversalXport-9617 cyl 8 alt 2 hd 64 sec 64>
/pci@8,700000/fibre-channel@2,1/fp@0,0/ssd@w200400a0b82fbc3c,1f
b. List the array ports using the UI or CLI:
A/1 A Up FC 2 Gbps 20:04:00:A0:B8:2F:BC:3B
A/2 A Up FC 2 Gbps 20:04:00:A0:B8:2F:BC:3C
B/1 B Up FC 2 Gbps 20:05:00:A0:B8:2F:BC:3B
B/2 B Up FC 2 Gbps 20:05:00:A0:B8:2F:BC:3C
In this example, Port A/2 exposes c9t0d31 and Port B/2 exposes c8t0d31
Bug 6593318 - When a number of in-band managed arrays are selected for removal, the operation appears to complete successfully. However, one array may still be listed on the Storage System Summary page.
| Note - For best performance, ensure both controllers are connected during configuration. |
Bug 6603978 -The controller for an in-band managed array cannot not be reset even when physical connectivity between the array and the management host has been verified.
Workaround -If physical connectivity is valid, un-register and re-register the array.
Bugs 6610504, 6609734, 6609155, 6607104, 6609732, 6612120 -An occasional problem exists where the in-band proxy agent may return the paths to the controllers in reverse order. This error can occur on any platform.
The net result is an immediate communications error. The error message will typically read “Error: Could not communicate with the controller to complete this request. Possible causes include network or connection problems, controller problems, or no power to the host or storage array. Check these possible causes, then retry the operation.”
This error might occur when performing the following operations:.
Workaround -Change the Current Volume Ownership when a “communication error” is encountered during volume expansion: From the Volumes page, select the “Specific Volume” and then change the value of the “Owning Controller.”
Changing the Current Volume Ownership will create an Alarm because the volume is not on the preferred controller. Select one of two actions:
| Note - For best performance, ensure both controllers are connected during configuration. |
Bug 6588699 - When an in-band managed array loses communication with management host, the network address listed in the Storage Summary page displays as an out-of-band address instead of an in-band address.
Workaround - If communication is lost with the array, view the alarms to determine if an in-band or out-of-band connection is lost.
Bug 6661742 - SMagent-LINUX-10.00.A2.02-1.i386.rpm will not load. SMagent is not supported on Redhat 5.0.
Workaround - The SMagent requires Red Hat 5.1 (also known as “5 update 1”) or higher.
Bug 6612214 - When one of the arrays behind an in-band management proxy is removed in Common Array Manager, the Common Array Manager software will change the management of the other arrays behind the proxy to out-of-band management if that path exists. An in-band discovery of the proxy agent would return them to in-band management in this case.
Bug 6490238 -When installing the French version of Common Array Manager on Solaris and LINUX platforms, non-ASCII characters display as garbled text in the copyright and license sections when the correct locale is not used.
Workaround -Use the correct locale (for example, fr_CA.ISO8859-1 for Solaris and fr_FR.iso88591 for LINUX) or use the browser in the English locale.
Bug 6495952 -When installing Chinese and Japanese version of Common Array Manager on SuSE Linux platforms, non-English characters are displayed as squares.
Workaround -Use English locale on SuSE Linux to install the software.
Bug 6645809 -Test parameter names in troubleshooting test pages are not localized. For example, performing a test from the “Trouble Shooting” menu in a Japanese environment does not display localized names for “Target Controller,” “Password,” and “Send Results to Email.”
Workaround -This fix is in progress.
Bug 6495952 -Graph titles and description pop-up is not localized for Virtual Disk page. This bug is a result of a workaround for another bug (6516766) where resource strings for graph titles, descriptions, pop-ups, etc. were commented out in the foreign resource property files.
Workaround -This fix is in progress.
Bug 6500605 -For Solaris 10u4 and Solaris 8 and 9, the host cannot see the storage device's management UTM LUN.
Workaround -Perform the following commands on the data host:
# setenv LD_LIBRARY_PATH /opt/SMgr/agent
# java -classpath /opt/SMgr/agent/SMagent.jar devmgr.versioned.agent.DeviceIdentifier | grep "Volume Access"
You should then receive output like the following, indicating which arrays have access LUNs visible to the agent:
/dev/rdsk/c5t200600A0B82458D4d31s2 [Storage Array fms-lca1, Volume
Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>]
/dev/rdsk/c5t200700A0B82458D3d31s2 [Storage Array fms-lca1, Volume
Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
Bug 6594360 -After you upgrade to S10U3 (or later), the in-band management UTM LUN's are controlled by Solaris Traffic Manager (MPxIO). In most cases, in-band management will not fail as a result of this; however, it is best practice to ensure that the UTM LUN's are not controlled by MPxIO. Performing the following workaround task will help prevent problems.
Workaround -Use the format inquire command to get the Vendor and Product IDs. (The VID needs to be 8 characters.)
1. Edit the file /kernel/drv/scsi_vhci.conf
The following line should read:
device-type-scsi-options-list = "SUN Universal Xport", "disable-option"; disable-option = 0x7000000
2. Run the stmsboot -u command.
Respond to the prompts as follows:
WARNING: This operation will require a reboot.
Do you want to continue? [y/n] (default: y) y
The changes will come into effect after rebooting the system.
Reboot the system now? [y/n] (default: y) y
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
| Note - For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com |
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 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 available on or through such sites or resources.
| Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.1 | 820-3997-11 | |
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.