| Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.0 |     |
| Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.0 | |
|
Sun StorageTek Common Array Manager Software Release Notes |
This document contains important information about Release 6.0.0 of the Sun StorageTek
Common Array Manager software or information that was not available at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the Common Array Manager software.
These release notes cover the software released on the Sun StorageTek Common Array Manager Software 6.0.0 CD.
The Release Notes consist of the following sections:
This section describes the main features of the Sun StorageTek Common Array Manager software in the following sections:
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.x.x or higher allows tray mixing of 6540, 6140, 6130, FLX240, FLX280, and FLX280 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.
| 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.
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, in order to avoid a variety of issues including those listed below.
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.
Contact Sun Microsystems Support Services promptly upon experiencing any of the following symptoms:
| Note - 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.
TABLE 2 and TABLE 3 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.
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 6.0.0:
TABLE 5 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 7.
|
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 8 lists Solaris packages that must be installed on your Solaris host. Installing the minimum Solaris operating system package as listed in TABLE 7 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 9 lists Linux packages and libraries that must be installed on your Linux host. The 32-bit versions of the packages and files are required.
A new patch is required to resolve an issue with the online help. (Bug 6540170) The context-sensitive help will not display in the right-hand pane for systems when you use the fully-qualified name to access the management host. Instead, the default help title page displays.
Install the required patch to resolve this issue. Otherwise, navigate to the appropriate context-sensitive help page from the online help table of contents in the left-hand pane.
Patches are available from SunSolve (http://www.sunsolve.sun.com). TABLE 10: lists the patch number and the corresponding platform.
The following table lists the disk and directory space requirements of the management host software.
|
Windows 2000 with Service Pack 4 Windows 2003 with Service Pack 1 Windows XP Pro with Service Pack 2 [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 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 CLI client sends commands to a management host, which in turn sends the commands to the array. TABLE 12 lists remote platforms that can run the CLI client.
The Sun StorageTek Common Array Manager software supports the Web browsers listed in TABLE 13.
| 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:
For Solaris, Linux and Windows:
The command line interface is available in:
The online help is available in:
The 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.
| Note - For the latest SAS and firmware patches available for your system, check SunSolve (http://www.sunsolve.sun.com) . |
Solaris: Upgrade 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 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. 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.
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 firmware function is available 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, and the FLX240, FLX280, and FLX380 arrays.
| Note - Mixing trays is not supported for the Sun StorageTek 2500 Series Arrays. |
Refer to TABLE 2, TABLE 3, and TABLE 4 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 the Common Array Manager release 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. |
4. Upgrade the array firmware.
After registering the arrays, the software prompts you if the array needs to update its firmware.Upgrade the array firmware from the Storage System Summary page or Array Administration page by clicking the Upgrade Firmware button.
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 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 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.
Bug 6590097, 6577775, 6592717, 6592703 -Using an invalid array password may result in configuration error messages.
Workaround - Use the correct array password.
Bug 6590617 -Since the Sun StorageTek 6130 array does note 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).
Bug 6604026 -Data channels 3 and 4 cannot be managed using Service Advisor; only channels 1 and 2 are available for management.
Workaround - Use the sscs CLI service command to manage data channels 3 and 4.
Bug 6569930 -Attempting to reset the array configuration while a volume has a persistent reservation appears successful but, 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 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 6602902 -When a virtual disk is in the 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 6498717 -When creating a data replication set, if the primary array cannot communication 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 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.
| Note - In-band management is supported on the Sun StorageTek 6130, 6140, 6540, and 2500 Series arrays. |
The in-band management proxy agent is a package which is added to a host (or group of hosts) which have 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 many 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 .exe files which include their own "Install Anywhere" installer.
| Note - CAM 6.0.0 was only qualified with Solaris (SPARC) and Linux agents for the 6.0.0 Release. |
You can download CAM in-band proxy agents for Solaris (Sparc) and Linux from here:
http://www.sun.com/download/products.xml?id=471e7573
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. Added new storage arrays to the configuration).
To verify the host sees the arrays management (UTM) LUN is accomplished as follows.
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
[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.0 |
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
Bugs 6610504, 6609734, 6609155, 6607104, 6609732, 6612120 -A problem exists where the in-band proxy agent may return the paths to the controllers in reverse order which is not properly accounted for in this release of CAM but will be correct in the next release.
This will not always occur but when it does, the net result is an immediate communications error. The error message will typically read as: " 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 may occur when performing the following operations:.
Workaround -Change the Current Volume Ownership when a "communication error" is encountered during volume expansion. Do this by selecting Volumes>Select the 'Specific Volume' and then change the value of the "Owning Controller".
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 6584815 -When an access LUN is mapped to a proxy agent host for in-band management use, you can only correlate the mappings between the access LUNs and the host they are mapped to by using the format command at the UNIX prompt to get a listing of the access LUNs, and then get a listing of the array ports from the UI or the CLI, and comparing 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 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, unregister and reregister the array.
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 6593318 - When a number of in-band managed arrays are selected for removal, the operation appears to complete successfully. However, when viewing the Storage Summary page, one array may still be listed on the Storage System Summary page.
This section describes known issues and bugs related to storage configuration.
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 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 6595884 -A firmware upgrade can lock volumes longer than the upgrade process indicates. The array can report the upgrade completed and show an optimal state but the process can still lock the volumes.
The upgrade completion timing in the management software will be evaluated.
Workaround -Wait an extra 5 to 10 minutes and retry.
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 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 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.
Bug 6598844 -Members of a replication write consistency group should all have matching attributes and roles.
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 6596281 - If a data replication set is created between two volume with the primary volume having 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 6560461 -Although both the base volume and the snapshot reserve volume support readahead, the snapshot volume itself does not support readahead. As a result, the Readahead Enabled Option is set to False on the Snapshot Details page.
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 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 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 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 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 are listed as options with the CLI sscs switch command, these options are not yet implemented.
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 6593508 - The review step of firmware upgrade wizard may display a false warning that the array health is not optimal.
Workaround -Check the Alarm Summary page to verify the alarm.
Bug 6593883 -When attempting to force a firmware upgrade from the Firmware Upgrade wizard when without hard disk drive (HDD) firmware, the wizard action reads that "no disks" will be upgraded, but the warning reads "Forced upgrade on all components including disks”.
Bug 6500605 -For Solaris 10u4, 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 output like the following which indicates 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 -When upgrading to S10U3 (or later) a problem may occur the in-band management UTM LUN's will now fall under control of Solaris Traffic Manager (MPxIO). In-band management will not fail for most cases but it is important for a few types of management, that the UTM LUN's are -not- controlled by MPxIO.
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
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 do not specify that when using the -p option with the sscs modify firmware command, you must suppli the file path of the firmware image file.
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. Therefore, when attempting to create more than the supported number of volumes, an error message is returned.
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 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.
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:
Page 44 of the Sun StorageTek Common Array Manager Software Installation Guide, v.6.0 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.”
This section describes known issues and bugs related to localization.
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.
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 register an array with the management software, it notifies you if an array’s firmware needs to be upgraded by sending an alarm that the array firmware is not at the firmware baseline.You can choose when and if to upgrade an array’s firmware using the Upgrade Firmware button from the Storage System Summary page or Array Administration page.
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.
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 must register the array with ASR before using the Test button. |
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.
This section lists the firmware files included in the Common Array Manager 6.0.0, by array type.
Common Array Manager software is installed in the following locations
Within the directory where you installed the Common Array Manager software, a README file for each array type define the firmware baseline.
Firmware files are located in the /images subdirectory.
TABLE 14 lists the controller information for the Sun StorageTek 2540 and 2530 arrays.
TABLE 15 lists the controller information for the 2500 Series Arrays
TABLE 16 lists the controller information for the 2500 Series Arrays
TABLE 17 lists the IOM information for the 2500 Series Arrays
TABLE 18 lists the disk drive information for the 2500 Series Array
TABLE 19 lists the controller information for the 2Sun StorageTek 6130, 5140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 20 lists the NVSRAM information for the 2Sun StorageTek 6130, 5140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 21 lists the IOM information for the 2Sun StorageTek 6130, 5140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 22 lists the disk drive information for the Sun StorageTek 6130, 5140, 6540, FLX240, FLX280, and FLX380 arrays.
| Note - For the latest SAS and firmware patches available for your system, check SunSolve (http://www.sunsolve.sun.com) . |
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
| Note - For the latest SAS and firmware patches available for your system, check SunSolve (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 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 6.0.0 | 820-2935-11 | |