| Sun StorageTek Common Array Manager Software Release Notes, Release 6.1.2 |     |
|
Sun StorageTek Common Array Manager Software Release Notes |
This document contains important information about Release 6.1.2 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 (CAM) software provides an easy-to-use interface from which you can configure, manage, and monitor Sun StorageTek and Sun Storage arrays.
To obtain the most current software release and related information: From http://www.sun.com/storagetek/management_software/resource_management/cam, click the “Get It” tab to obtain the latest information and version available.
CAM software provides the following:
6000 Disk Module (B6000)
TABLE 1 lists the version information for the software included in this release.
|
Firmware files, as listed in Firmware for CAM |
|
| Note - Premium features are not supported for the J4000 Array Family. |
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 |
|||||||
For hardware information, refer to the array’s release notes and hardware installation guide. You can search for Sun documentation at http://www.sun.com/documentation.
System requirements for the Sun StorageTek Common Array Manager software are described in the following sections:
CAM software supports the following Sun storage systems:
6000 Disk Module (B6000)
|
Windows 2003 with Service Pack 1 Windows XP Professional with Service Pack 2[1] |
|||
|
Red Hat Enterprise Linux AS Release 4 (Nahant update 4) |
|||
TABLE 6 lists Solaris packages that must be installed on your Solaris host. Installing the minimum Solaris operating system package as listed in TABLE 5 will install all but the last four packages. Those packages are required by Java, but are not used by the management software.
|
X Window System & Graphics Runtime Library Links in /usr/lib |
TABLE 7 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
|
Windows 2003 with SP1 or higher Windows XP Professional Edition with SP2 |
||
If needed, download the files from the Microsoft Download site. You must be logged in to the Windows system as an administrative user.
The array installation files and installers are provided in a compressed file on the CD. The process unpacks the contents of the file on the host and then proceeds with the installation.
After the installation on a Windows platform, you will need to configure the Windows firewall on each host to allow an exception for port 6789.
For more information, refer to the appropriate product documentation. See Documentation.
Open the following incoming and outgoing ports for secure-by-default Solaris, Linux, and Windows platforms:
The remote scripting command-line interface client sends commands to a management host, which in turn sends the commands to the array.
TABLE 9 lists remote platforms from which you can run the CLI client:
For best web browser performance while using CAM, do the following:
| Note - Microsoft Internet Explorer version 7 is not supported. |
Using Solaris 10 and Firefox 3.0.1, the progress of array registration is not finishing in registration wizard with Firefox 3.0.1. To work around this issue, be sure to perform Step 5 below when registering an array:
1. Click the Registration Button.
4. Click Finish to display the Results window.
The progress bar is not in motion and the Closed button is active.
The registration process should finish as you had expected it to in Step 4.
To avoid DNS-lookup delays, be sure arrays are connected. Otherwise, Windows might take a long time looking up information for arrays that are not being managed by CAM, if you have them listed in the system as being connected to the system. Make sure the array names are in DNS or add them to the hosts table in the Windows OS.
| Note - This does not apply to JBOD arrays unless there is a mixture of JBOD's along with arrays that are communicated with via Ethernet. |
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:
CAM installation procedures are described in the Sun StorageTek Common Array Manager Software Installation Guide (part number 820-4193) and the Sun StorageTek Common Array Manager User Guide for the J4000 Array Family (part number 820-3765). This section describes release-specific steps for 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 website.
To obtain the most current software release and related information: From http://www.sun.com/storagetek/management_software/resource_management/cam, click the “Get It” tab to obtain the latest information and version available.
2. Locate the most current patches.
For the latest patches available for your system, check SunSolve at http://www.sunsolve.sun.com
3. If supported by your array types, verify that you have license certificates for all premium features, including storage domains.
See Licensing Optional Premium Features.
4. Read the installation instructions.
Refer to the appropriate documentation. See Documentation.
5. Log in as root (Solaris and Linux) or as a user with full administration privileges-not just local administrator privileges-(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.
For more information, contact Sun Microsystems Support Services. (Service Contact Information)
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, 5.1.3.2, and 6.x to this release are supported. You are not required to uninstall the existing CAM version before installing this release.
Linux: Upgrades are supported.
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
If you are installing the management software on a new host, check the installation requirements and follow the entire installation and configuration procedure described in the appropriate documentation. See Documentation.
You can install CAM on a local management host or on a central management server.
Before installing the management software, do the following:
To obtain the most current software release and related information: From http://www.sun.com/storagetek/management_software/resource_management/cam, click the “Get It” tab to obtain the latest information and version available.
After initial installation and configuration, you can upgrade the management software and firmware with each release.
During installation, the firmware update bundle is installed on the host server. For details about upgrading array firmware, refer to the appropriate documentation. See Documentation.
The Sun StorageTek Common Array Manager Installation Software CD provides three installation-related wizards:
To obtain the most current software release and related information: From http://www.sun.com/storagetek/management_software/resource_management/cam, click the “Get It” tab to obtain the latest information and version available.
After initial installation and configuration, you can upgrade the management software and firmware with each release
You can perform a minimal installation that enables one of two options: a command-line interface only or a command-line interface with firmware. In both cases, this installation is approximately 10%-20% smaller than the size of the full CAM installation since the Graphical User Interface (GUI) is not installed.
After the CLI-only Installation mode is chosen, the option will be given to make the installation on this host a proxy to another host running the full installation of CAM for the purposes of aggregating multiple poxy hosts.
| Note - Minimal Installation can stand alone, whereas Remote Client installation requires a fully installed image on a separate host. |
This light-weight management solution is installed on a data host attached to the array. The data host can also serve as a management host using the CLI only installation option and provides:
For complete instructions on CLI Minimal Installation, refer to the appropriate documentation. See Documentation.
For complete instructions on CLI (Minimal) Installation, refer to the appropriate documentation. See Documentation.
1. From the Common Array Manager Installation page, select one of these options in the Select a feature bundle list:
| Note - Array firmware files are not installed with the Command-Line Only option. Because firmware is not installed, the firmware analysis feature is not available with this installation. |
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:
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.
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-4193) and the Sun StorageTek Common Array Manager User Guide for the J4000 Array Family (part number 820-3765).
Navigate to the appropriate directory for your operating system:
%systemdrive%\Sun\CommonArrayManager\Host_Software_6.1.2.7\bin\uninstall.bat
For Solaris and Linux, navigate to:
/var/opt/CommonArrayManager/Host_Software_6.1.2.7/bin/uninstall
For the Suse 9 platform, CLI uninstall requires the following rpm packages:
2. Enter the command uninstall -f
If you still have problems, enter the command uninstall -f -s
The command will remove the current installation.
During installation, the firmware update bundle is installed on the host server. For details about upgrading array firmware, refer to the appropriate documentation. See Documentation.
| Note - To install the new 07.10.x.xx firmware for the 6140, 6540, and FLX380 arrays, contact Sun Microsystems Support Services (see Service Contact Information). |
To obtain the most current software release and related information: From http://www.sun.com/storagetek/management_software/resource_management/cam, click the “Get It” tab to obtain the latest information and version available.
For the latest patches available for your system, check http://www.sunsolve.sun.com.
This section describes the following topics:
CAM firmware is installed in the following locations:
Within the directory where you installed the firmware, a README file for each array type defines the firmware baseline.
You can upgrade array firmware by using CAM’s Install Firmware Baseline feature. The software prompts you when it’s time to upgrade array firmware.
| Note - You do not need to uninstall existing firmware before following this procedure. |
For optimal performance, Sun Microsystems recommends that the firmware on all arrays be at the level of the current firmware baseline. New features are not supported with non-baseline firmware. You can update your array firmware by clicking the Install Firmware Baseline button on the Storage System Summary page or the array’s Administration page.
As part of the CAM installation, the script puts the array firmware files in a directory on the management host. When you upgrade the firmware, the software analyzes the firmware installed on the array. If the firmware baseline on the host is newer, and you choose to install, the software installs the firmware baseline on the array.
1. Before you perform this task, be sure the array is not in a degraded state.
If it is degraded, the upgrade will fail. If the array is degraded because it is not at the baseline, you can upgrade the array.
2. Check to see if there are any alarms and resolve them.
Alarms can be checked in the Java Web Console masthead or in the Alarms Summary link in the Navigation Tree on the left. Use Service Advisor to fix any alarms.
3. Log in to the management software.
See Documentation for help in locating the appropriate product documentation.
4. From the Java WebConsole page, click Sun StorageTek Common Array Manager.
5. From the Storage System Summary page, select the array for which the firmware needs to be installed/upgraded.
6. Click Install Firmware Baseline, and follow the prompts.
Be sure to check the build notes file distributed with the software for the exact firmware build. CAM 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 or the J4000 Family Series).
| Note - Contact Sun Microsystems Support Services (see Service Contact Information) to install the new 07.10.x.xx firmware for the 6140, 6540, and FLX380 arrays. |
In the following tables, the path listed in the Firmware File column is relative to the images subdirectory where firmware files are located.
When you add a new CSM200 expansion module to an existing array in a production or active environment, you must 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 (see Service Contact Information). 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.
|
Caution - Not following correct procedures could result in loss of customer data. |
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 (see Service Contact Information) promptly upon experiencing any of the following symptoms:
| Note - There are no expansion modules for the J4000 Array Family. |
The following tables list the supported expansion modules:
|
Supported Expansion Modules with Controller Firmware 06.19.25.16 |
||
|---|---|---|
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.
You must contact Sun Microsystems Support Services (see Service Contact Information) to install the new 07.10.x.xx firmware for the 6140, 6540, and FLX380 arrays. After the initial installation, you can install future changes to the 07 firmware baseline using the procedure that follows.
| Note - 07.10.x.xx is not available for the 6130, FLX240, 280, 2500 and J4000 arrays. |
This following does not apply to J4000 arrays: After an upgrade to the 7.10 firmware version, the Cache Block size will reset to 4KB. In previous firmware levels, the default size was 16K. The GUI and CLI have options to change the default Cache Block size, if necessary, to the previous 16KB size.
Prerequisite: Before discovering a Sun StorageTek FLX240, FLX280, FLX380 array using CAM and before performing any tray migration (for example, adding FLA300 expansion trays behind an existing 6130, 6140 or 6540 controller), you must upgrade the arrays and associated trays to the firmware version 6.19.25.00 or later. After you register the arrays with CAM, you can upgrade to the current firmware baseline.
1. Before cabling the newly supported expansion module, upgrade the existing controller and trays.
1. Install the new controller and trays.
2. Perform the firmware upgrade.
Follow this procedure to add trays to arrays managed by CAM:
| Note - Do not cable the additional expansion tray. |
1. Install the Common Array Manager release following the standard installation procedure.
2. Register the array, if needed.
3. From the Storage Summary page or Array Administration page, click the Install Firmware Baseline button.
5. Use Service Advisor to cable the additional expansion tray and add it to the array.
6. Upgrade the array again to update the firmware on the new tray.
For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com.
In the following tables, the paths listed in the Firmware File column is relative to the images subdirectory where firmware files are located.
Support has been added for a third expansion tray and 48 drives.
For the most current cabling information, see the Sun StorageTek 2500 Series Array Release Notes. From http://www.sun.com/documentation, you can type “2500 Release Notes” in the “Search” field, and press Return. Then select the current Release Notes document.
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 6698254 -When you select the device name link from the Alarm Summary page, you might get an exception or an error. For instance, a Java stack trace might display in the main UI window.
Workaround -Select the device from the main window.
Bug 6736301 -Trying to change the name of a locally or remotely managed JBOD array appears to complete successfully but the array name is never changed. Issuing the command “sscs modify -N <new name> storage-system <old name>” returns successfully; however, the name on the J4500 does not change.
Workaround -Use the “sscs service -a <old name> set name=<new name>” command.
When an array is out of compliance, a number of operations might not occur, such as:
Bug 6744622 -Using Solaris 10 and Firefox 3.0.1, the progress of array registration is not finishing in registration wizard with Firefox3.0.1.
Workaround - Be sure to perform Step 5 below when registering an array.
1. Click the Registration Button.
4. Click Finish to display the Results window.
The progress bar is in motion and the Closed button is active.
The registration process should finish as you had expected it to in Step 4.
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.
Bug 6681173 -List devices can show multiple unlabeled entries. List storage systems can show multiple unlabeld entries as well. The CLI user is unable to differentiate between unlabeled entries.
Workaround -Rename each unlabeled device to a unique Temporary Name. Use list controller to determine IP address for the TN. Then rename TN to desired.
Bug 6698735 -When a power cord for a power/fan CRU on a J4200 is disconnected, the following CAM critical alarm is generated:
“The property Status for PowerSupply.00 on 0744QCJ005 has changed from OK to CRITICAL.”
Workaround -Check the following and take appropriate action:
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, the user will be notified.
Workaround -This should have no impact but if the status needs to be seen, you can run defragmentation jobs using the CLI: /opt/SUNWsesscs/cli/bin/sscs modify --array oz1-Shared-with-DavidBL --defragment vdisk 1
Bug 6592877-When a drive fails, the vdisk 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 6682034 -Attempting to reconstruct a disk results in message “error.reason.100404.” The vdisk to which the drive belongs is in an invalid state and cannot be reconstructed.
This occurs because of the loss of redundancy that results from more disk failures than a given RAID level can recover. This fix is in progress and will be available in a future release.
To avoid DNS-lookup delays, be sure arrays are connected. Otherwise, Windows might take a long time looking up information for arrays that are not being managed by CAM, if you have them listed in the system as being connected to the system. Make sure the array names are in DNS or add them to the hosts table in the Windows OS.
| Note - This does not apply to JBOD array unless there is a mixture of JBOD's along with arrays that are communicated with via Ethernet. |
Bug 6515237 -CAM 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 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.
When you install the CAM 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, CAM 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 6684322 -Cannot enable volume copy license by specifying the license file using Internet Explorer 7.
Workaround -Internet Explorer version 7 is not supported. Use a supported browser listed in TABLE 10.
There may be significant DNS delays on Windows hosts.
Workaround -To avoid DNS-lookup delays, be sure arrays are connected. Otherwise, Windows might take a long time looking up information for arrays that are not being managed by CAM, if you have them listed in the system as being connected to the system. Make sure the array names are in DNS or add them to the hosts table in the Windows OS.
| Note - This does not apply to JBOD array unless there is a mixture of JBOD's along with arrays that are communicated with via Ethernet. |
1. Before installing CAM on Windows, be sure the file or directory “%SystemDrive%\Program” does not exist.
This file can prevent some applications from functioning properly.
2. If it does exist, rename the file to “%SystemDrive%\Program1.”
Bug 6709828 -When using either the command-line interface only or command-line interface with firmware option for installation on the Windows platform, other CAM installations are unable to discover the JBOD array via the Windows proxy (%ProgramFiles%\Sun Microsystems\Common Array Manager\Component\fms\sbin\proxycfg.bat).
Workaround -Because the proxy has not been set up correctly on the Windows platform during installation, you must manually execute the proxycfg.bat file.
Bug 6635453 -sscs displays “Connection failed!” error when user’s home directory or its files cannot be read.
Workaround -If you get a “Connection failed!” error when using the CAM CLI command sscs, do the following:
1. Check the value of the HOME environment variable and that it is set to you home directory.
2. Verify that $HOME/.sscs_conf, if it exists, has owner read and write permission.
Bug 6730975 -CLI: Cannot modify date on J4200 controller. Error says invalid resource-type value was used.
Workaround -The J4200/J4400 JBODs only support syncTime:
sscs service --array J4400_box1 syncTime
Executing the syncTime command on J4400_box1
Bug 663281 -If gettext rpm is not present on Suse 9 platform, CLI uninstall gives error messages.
Solution -This is not a workaround but a solution to this issue. Before installing CAM on a Suse 9 platform, you must install the following RPM packages:
See Uninstalling a Previous CAM Version.
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 will 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 6727335 -Attempting to view communication events via the UI Events advanced filter returns an empty list. An empty list is also returned when Removal Events is selected. Filter does not find any events.
Workaround -In progress. To be fixed in a future release.
Bug 6738923 -Nickname not set on second expander B0/B1; original name seen during firmware upgrade.
Workaround -This is a limitation of the hardware. There is no workaround at this time.
Bug 6745468 -Registered name is offset by a character from the physical sticker identifier.
Workaround -This is expected behavior. The physical sticker indicates the base WWN shared by all four expanders. This offset does not affect ASR registration, because the chassis WWN is used to register rather than the nickname.
| Note - Issues listed in this section are in progress and will be updated with the CAM 6.2 release. For further details, contact your technical support representative. |
Two categories of J4500 Hot Plug issues have been identified: Those that require a Linux host reboot and those in which the hot plug is not supported. These are separated into two sub-sections as follows:
1. Linux host reboot is required if the array or any of its components are not recognized after changes such as cable re-configurations, firmware upgrades, etc.
Bug 6688831 -Linux Operating Systems hang when JBODs are disconnected from Sun StorageTek PCI-Express SAS Host Bus Adapter B3.
Bugs 6688831 and 6692819 -RHEL4 U6 64-bit Operating System hangs when Failed disk is recovered on JBOD 4000.
Bugs 670618 and 6731595-AL/RW: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SuSE 9 SP4: Multipath (device mapper): Alternate SIM failure causes host to hang.
Bug 6730211 -CAM: Linux RHEL5.2: PANIC when upgrading SIM firmware on J4000 array family with Sun StorageTek PCI-Express SAS Host Bus Adapter.
Bug 6730678 -AL/RW: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SuSE 9 SP4: Multipath (device-mapper): Alternate SIM failure causes host to hang.
Bug 6732411 -AL/RW: Sun StorageTek PCI-Express SAS Host Bus Adapter B3: SLES9SP4: Multipath: Lost Communication to AL/RW after CAM SIM firmware upgrade.
Bug 6732925 -RHEL5.2 J4000 array family: Panic when SIM is pulled while running IO on Sun StorageTek PCI-Express SAS Host Bus Adapter.
Bug 6737779 -J4000 array family: SUSE10: Loss of communication after upgrade of SIM and DISK Firmware.
Bug 6738394 -SUSE10:RW:SATA drives Replacing cable in HBA causes multipath -l to loose info in sysfs & device-map.
Bug 6741578 -Cannot register J4500 on Linux until host reboot3.
Bug 6741693 -RHEL5.2: Upgrade of SIM and disk firmware using CAM CLI causes panic.
2. Sun StorageTek SAS RAID HBA hot plug is not supported. Generally, the workaround is to reboot the array between any cable changes etc.
Bug 6723686 -J4500 failed disk drive (Sun StorageTek SAS RAID HBA) not reported by CAM.
Bug 6732704 -J4500 Windows agent (Sun StorageTek SAS RAID HBA) 0.0 MB reported; drive FRU missing unique identifier.
Bug 6739921 -Enclosure management device properties still shows old J4500 firmware version after upgrade.
Bug 6729062 -CAM fails to install on Windows with another version already installed.
Workaround -If either of the following two instances occur, use the procedure that follows:
1. Download the Windows Installer CleanUp Utility from the following website: http://support.microsoft.com/kb/290301
2. Install the Windows Installer CleanUp Utility, by running msicuu2.exe.
3. Execute the Windows Installer CleanUp Utility.
4. Select and remove all CAM components from the Windows Installer CleanUp Utility.
Bug 6657309 -After several minutes of inactivity, the Sun Java(TM) Web Console Version 3.0.2 goes into maintenance mode and yields errors similar to the following:
m4000 gconfd (noaccess-2277): I can't write to '/var/tmp/orbit-noaccess', ORB init failed
m4000 svc.startd[7]: system/webconsole:console failed: transitioned to maintenance (see 'svcs -xv' for details)
svc:/system/webconsole:console (Java web console)
State: maintenance since Tue Jan 22 14:08:06 2008
See: http://sun.com/msg/SMF-8000-8Q
See: man -M /usr/share/man -s 1M smcwebserver
See: /var/svc/log/system-webconsole:console.log
Impact: This service is not running.
Workaround -For unix hosts, set the directory permission to 01777 (i.e., chmod 01777 /var/tmp) and restart the console.
Bug 6701605 -WebConsole 3.1 patch is breaking the CAM UI on Linux host.
Workaround -Download patch 125954-16 or later from sunsolve.sun.com for Linux hosts and apply it to the CAM server to upgrade the WebConsole to 3.1. For Solaris and Windows, the upgrade is seamless but for Linux the CAM interface might have problems in which case you can refer to your Linux documentation.
Fix in progress. Look for version -17 to come out for the WebConsole 3.1 patch soon.
| Note - For the latest patches available for your system, check SunSolve at http://www.sunsolve.sun.com |
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 6684018 -Replication Set Detail page shows an incorrect replication dedicated port for 6540 array.
The fix will be delivered in a future release of CAM software.
Bug 6736979 -The J4500 and Sun Blade 6000 Disk Module display invalid Serial number data. Expander id is not the Serial number.
Workaround -None. Serial numbers will be used as device identifiers in a future release.
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 6681459 -There is a discrepancy in the snapshot quantity shown on Snapshot details and License summary pages.
Workaround -Use the License page for accurate snapshot quantity details.
Bug 6665092 -When used together, the -Z option overrides the -L option.
Therefore, the following command yields an error:
/sscs create -a 6540-1 -V master-vol-1 -f failsnapshot -m res-vol-1 -Z 5GB -w 50 -C 1 -L average snapshot snap-1.
Workaround -Do not use the -Z option. Instead, use the -w option.
| Note - The -Z option is not supported on any array other than the 6920. |
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 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.” The check for a legal numeric value is not localized, but the interpretation of the number afterwards is.
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. You can perform one of the following tasks:
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 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.
Bug 6710961 -CLI Quick Reference contains an error in the sscs list in this example:
List the field replaceable components in this device.
sscs list -d device-name [-t battery|ctrl|disk|
midplane|pcu|sfp|all] [-s] [-f string] [-l string]
The option “all” should be removed so the command reads like so:
sscs list -d device-name [-t battery|ctrl|disk|
midplane|pcu|sfp] [-s] [-f string] [-l string]
The 6.2 version of the CLI Quick Reference Guide will show the correct information.
Sun StorageTek Common Array Manager sscs (1M) CLI Quick Reference Guide (part number 820-2932) says: “Do not use spaces, commas, colons (:), or the special characters ?,*,!,@,%, or & as a character in any name you specify. Numbers in braces {0} and {1} represent variables.”
The correct wording in the note should be as follows:
Do not use spaces, commas, colons (:), or the special characters ?,*,!,@,%, or & as a character in any name you specify unless you are prepared to escape them in the shell. Numbers in braces {0} and {1} represent variables in some error messages.
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.
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:
Bug 6686472 -The 6140 sscs man page describes the wrong usage for the -o --off option in the sscs service locate command. The -o option is used to turn off the locate LED. The man page incorrectly states it is use to place a FRU into a failed state.
For /opt/se6x20/cli/bin: man -M /opt/se6x20/cli/man sscs-6140, the man page should display the following:
service -a|--array <array-name> [-t|--target <string>] [-o|--off] locate
Bug 6540170 - CAM 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 Browser User Interface or documentation that imply there is a command or function for this task is misleading.
Bug 6736935 -From a x6220 blade running Suse 9, expander firmware upgrade fails, displaying the message “Error upgrading firmware. Check the following error message and array alarm page for possible problems. - expander reset failed - FWR_NO_ERROR, 0.” After the failure, some of the expanders do not display on the FRU detail pages. In this state, re-running firmware upgrade may lead to system issues.
Workaround -Reboot the host and verify that all expanders show from the FRU detail pages. Retry the firmware upgrade.
To avoid issues regarding the new 7.10.x.xx firmware:
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.
There are two different agents that can be used for communication to arrays via the in-band (data) path, dependant upon the array type: the CAM Proxy Agent and the RAID Array LSI Proxy Agent. In-band management is supported on the Sun StorageTek 6130, 6140, 6540, 2530 and 2540 arrays. The CAM Proxy Agent is to be used for J4xxx and Sun Blade 6000 Disk Module.
| Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
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.
| Note - CAM 6.1 added support for Solaris (x86) and Windows proxy agents. |
| Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
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.
| Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
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. |
| Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
Download CAM in-band proxy agents for Linux from here: http://www.sun.com/download/products.xml?id=471e7573
To verify the host sees the arrays management (UTM) LUN:
[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 - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
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
| Note - This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays. |
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.
This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays.
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 then re-register the array.
This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays.
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:
For best performance, ensure both controllers are connected during configuration.
Bug 6739547 -If you have selected the Remote Proxy Only Without Firmware Custom Install option, the manufacturing image does not download. When CAM runs firmware upgrade of remote proxy in-band array expanders, the manufacturing image download is skipped.
Workaround -When installing a remote proxy: From the Custom Install menu of the CAM installer, select the option to install both remote proxy and array firmware.
This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays.
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.
This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays.
Bug 6612214 - When one of the arrays behind an in-band management proxy is removed in CAM, the 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.
This information applies only to FLX240, FLX280, FLX380, 6130, 6140, 6540, 2510, 2530 and 2540 arrays.
Bug 6681582 -Performance Monitoring page lists the Performance statistics as Unavailable.
Workaround -Check the physical connectivity from the management host to the array. If the connectivity is good, try un-registering and then re-registering this array.
Bug 6648569 -Apostrophes display incorrectly in the Browser User Interface in some cases for the French language.
Workaround -Please set your browser language to en-us.
Bug 6734714 -A parsing exception is thrown on Event and Alarm page with fr or ja or zh_cn languages of your browser.
Workaround -Please set your browser language to en-us.
Bug 6739084 -Some messages are still in English under local language of browser on FRU details pages for J4500 and Sun Blade 6000 Disk Module.
Workaround -Please set your browser language to en-us.
Bug 6747749 -For the zh locale, the first link on the left panel is not working for Online help.
Workaround -Please set your browser language to en-us.
| Note - This information applies only to 6000 and 2500 arrays. |
Bug 6500605 -For Solaris 10u4 and Solaris 8 and 9, the host cannot see the storage device's management UTM LUN.
| Note - This bug is fixed in S10u5. |
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>]
This information applies only to 6000 and 2500 arrays.
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 eight-character Vendor (VID) and Product IDs. Follow the procedure on the next page.
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
For the latest patches available for your system, check SunSolve at: http://www.sunsolve.sun.com
To download Common Array Manager software, go to http://www.sun.com, click the New Downloads tab, and scroll down the list to find the link.
To locate a document: From http://www.sun.com/documentation, you can type the document title, part of the title, or the specific document’s part number in the “Search” field, and press Return. Then select the current document.
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.1.2 | 820-5902-11 | |
Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.