| Sun StorageTek 6140 Array Release Notes |    
|
| Sun StorageTek 6140 Array Release Notes |
|
|
Sun StorageTek 6140 Array Release Notes |
This document contains important release information about the Sun StorageTek
6140 Array 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 Sun StorageTek 6140 Array.
These Release Notes cover the software released on the Sun StorageTek 6140 Array Host Software 2.0 CD, and related hardware issues.
The Release Notes consist of the following sections:
This section describes the main features of the Sun StorageTek 6140 Array, including the following:
The Sun StorageTek 6140 Array is a 4-Gb/2-Gb Fibre Channel (FC) array that offers both direct attached and SAN attached storage. The Sun StorageTek 6140 Array features:
|
Note - SATA drives require Sun StorageTek 6140 Array Firmware Release 2.1. |
The Sun StorageTek Configuration Service browser interface provides you with an easy-to-use interface to configure, manage, and monitor the Sun StorageTek 6140 Array. You can also use the Configuration Service browser interface to access the Storage Automated Diagnostic Environment software, which enables you to diagnose problems, view events, and monitor the health of your array.
This version of the Sun StorEdge Configuration Service software includes the following new features:
TABLE 1 lists the version information for the software included in this release.
|
Sun Storage Automated Diagnostic Environment software (including localized versions) |
|
TABLE 2 lists the firmware files for this release.
The firmware location on the CD (/var/sadm/swimages/120337-03) contains the following firmware files:
Each of these directories contains a link, image.fw, that points to the firmware image, as well as a text file, baseline.txt, that contains the version of the firmware image.
The software and hardware products that have been tested and qualified to work with the Sun StorageTek 6140 Array are described in the following sections:
The management host on which the management software resides must meet the system requirements described in TABLE 3.
|
(see complete list of disk space requirements in File Space Requirements) Note: Be aware that you need 550 Mbytes more disk space than is required for your OS installation. |
|
The remote Scripting CLI client sends commands to a SPARC Solaris management host, which sends the commands to the array. TABLE 10 lists the remote platforms from which the CLI client can send commands to the SPARC Solaris management host. You can obtain the package you need from the Sun Download Center (SDLC), http://www.sun.com/software/download/, or from the Sun StorageTek 6140 Array Host Software CD.
TABLE 4 lists the supported host bus adapters (HBAs) for the Solaris 8, 9, and 10 Operating Systems (OSs).
You must install multipathing software on each data host that communicates with the Sun StorageTek 6140 Array. For Solaris OS 8 and 9 data hosts, the multipathing software is part of the Sun StorageTek SAN Foundation software. In Solaris OS 10, multipathing is included in the OS. For data hosts running the Solaris OS, follow the instructions in the Sun StorageTek 6140 Array Getting Starting Guide to install the software from the CD.
|
Solaris 10[1] |
||
TABLE 5, TABLE 6, and TABLE 7 lists supported HBAs for Windows, Linux, and other data host platforms. For multipathing support on data hosts running these operating systems, you can use the Sun StorageTek RDAC Driver software or other multipathing software as listed.
You can download HBA drivers and other host software from the Sun Download Center, http://www.sun.com/software/download/. Download operating system updates from the web site of the operating system company.
|
Note - For data hosts using multipathing software, you must install the multipathing software before you install any OS patches. |
|
Redundant Dual Array Controller (RDAC) |
|||||
|
Oracle Real Application Clusters (RAC) |
||||
|
Note - The multipathing driver for the IBM AIX platform is VERITAS DMP, bundled in VERITAS Volume Manager 3.x for the Sun StorageTek 6140 Array on AIX. Download the Array Support Library (ASL) from http://support.veritas.com/ as documented in To Download the AIX ASL Package. |
The enterprise software applications listed in TABLE 8 are compatible with the Solaris OS on the data host.
The following FC fabric and multilayer switches are compatible for connecting data hosts and the Sun StorageTek 6140 Array:
TABLE 9 lists the size, speed, and tray capacity for the supported FC and Serial Advanced Technology Attachment (SATA) disk drives in the Sun StorageTek 6140 Array.
|
SATA 2, 500G7.2K[2] |
TABLE 10 lists which management host OSs support array management through the CLI and which can serve as SMI-S providers. All supported management host OSs support management of the array through the Sun StorageTek Configuration Service browser interface. SMI-S enables other applications to communicate with 6140 Array management software.
|
Solaris 10[3] SPARC |
|||
All the supported management hosts in TABLE 10 use JRE version 1.4x and above for Java support, except Novell Netware and IRIX (which do not support Java software).
The Sun StorageTek Configuration Service software supports the web browsers listed in TABLE 11.
|
Note - The software requires that you enable pop-up windows in your web browser. |
Documentation for the Sun StorageTek 6140 Array is provided for the languages and locales listed in TABLE 12.
|
Note - Online help and man pages are available only in English. |
The array installation procedures are described in the Sun StorageTek 6140 Array Getting Starting Guide (part number 819-5045-10) that came with your array. This section describes release-specific steps for firmware and management software patch upgrades that you must perform:
The Sun management software is distributed on the Sun StorageTek 6140 Array Host Software CD. The installation script on that CD verifies host requirements. In particular, it ensures that there are at least 550 Mbytes of disk space available before starting the installation script. Be sure to do the following before performing the upgrade:
Should a failure occur, be sure to check the available disk space again. Then consult the system log /var/sadm/install/se6000/se6000_Host_SW.log for more information.
If a requirement is not met, the script informs you and then cleans up afterward, where appropriate. The script prompts you for input or fails and exits if it detects any of the following in the system:
The total size of the installation files is approximately 550 Mbytes when the files are extracted to a local directory. The management host software requires the following available space for successful installation:
If you are installing the array and the management software for the first time, follow the entire installation and configuration procedure described in the Sun StorageTek 6140 Array Getting Starting Guide.
After the initial installation and configuration, you will be able to upgrade the management software and firmware with each release.
If you have a previous release of the Sun StorageTek 6130 or 6140 Array management software and array firmware installed, the upgrade script will detect it and upgrade to the new software and firmware versions required for this release. If the script detects that there is no earlier version installed, it will perform a complete new installation. The upgrade scripts are included on the Sun StorageTek 6140 Array Host Software CD, or in the package you obtain from the Sun Download Center, http://www.sun.com/software/download/.
|
Note - This procedure upgrades the software files (TABLE 1) on a management host on which an earlier version of the software has been installed. It is not necessary to uninstall the existing software. It also installs the firmware update bundle on the host server as a part of the management host software. To upgrade the firmware running on the array, see To Upgrade the Firmware on the Array. |
1. Verify that you registered the arrays in the Sun Storage Automated Diagnostic Environment software after the previous installation.
2. Open the Sun Storage Automated Diagnostic Environment interface to review, acknowledge, and delete all existing alarms.
The upgrade script will not perform an upgrade on arrays that have critical or down alarms.
3. Use the command-line interface to log in to the management host as root.
4. Insert the host software CD in the local CD drive (or go to the directory where the upgrade files were downloaded).
5. Start up the upgrade install script by doing either of the following:
./RunMe.bin
6. When prompted, specify the full path of the directory location in which the files are to be unpacked. This must be the same location in which the previous version was installed.
The files are unpacked in the following directory in the location you specify:
where xx is the version number of the installed files.
The default location for the directory is /var/tmp/
The host upgrade installer wizard launches automatically after the files are unpacked.
7. Follow the steps in the wizard.
8. When the upgrade is complete, click Finish.
9. Open the Sun Storage Automated Diagnostic Environment interface to review and delete any alarms that were logged for components upgraded during the upgrade process.
If you need to unpack the files or run the upgrade installer as a single step, the commands are, respectively:
Alternatively, if you want to unpack the files or complete the upgrade using the CLI, type the command with the -c option (Solaris only). For example:
./setup -c
1. Use the command line interface to log in to the management host as root.
2. Change to the Host_Software_2.0.0.xx directory where the files are located. For example:
cd /var/tmp/Host_Software_2.0.0.xx
3. Start the upgrade installer by typing:
./arrayinstall
The firmware upgrade installer wizard displays.
If you wish to step through the upgrade via the CLI instead, enter the arrayinstall command with the -c option (Solaris only): ./arrayinstall -c
4. Follow the steps in the wizard.
5. When the upgrade is complete, click Finish.
6. Open the Sun Storage Automated Diagnostic Environment interface to review and delete any alarms that were logged for components upgraded during the upgrade process.
|
Note - The array will remain in a degraded state until all alarms are deleted. |
Alternatively, you can upgrade the firmware on the array using the Configuration Service software:
1. On the Java Web Console page, click Sun StorageTek Configuration Service.
2. Go to the Array Summary page and select the arrays to be upgraded.
3. Click the Upgrade Firmware button.
|
Use the uninstall command if you need to remove all management and data host software from the host.
1. Log in to the management host as root.
2. Change to the Host_Software_2.0.0.xx directory where the files were unpacked. For example:
cd /var/tmp/Host_Software_2.0.0.xx
./uninstall
The uninstall wizard is displayed.
Alternatively, if you want to use the CLI to uninstall the software, enter the uninstall command with the -c option (Solaris only):
./uninstall -c
4. Follow the steps in the wizard.
5. When the uninstallation is complete, click Finish.
If for any reason the uninstall fails, use the -f option to uninstall the management host software:
./uninstall -f
There is no wizard with the -f option; the option forces a complete removal of the management host software.
After installing software for the data hosts from the Sun StorageTek 6140 Host Installation Software CD, go to SunSolve (http://www.sun.com/sunsolve) and download the SSD driver for data hosts running the Solaris 8 or 9 OS.
|
Note - Patch 108974-49 or higher requires patch 108528-29 or higher. If needed, apply patch 108528-29 or higher first. |
1. Download the 108974-49 or higher patch from SunSolve.
Refer to the README file for more information on downloading patches.
unzip 108974-49.zip
4. Apply the patch with the patchadd command:
patchadd 108974-49
reboot -- -r
1. Download the 113277-44 or higher patch from SunSolve.
Refer to the README file for more information on downloading patches.
unzip 113277-44.zip
4. Apply the patch with the patchadd command.
patchadd 113277-44
reboot -- -r
VERITAS Volume Manager provides support for the Sun StorageTek 6140 Array in the form of the Array Support Library (ASL). There are ASL software packages for the Solaris 8, 9, and 10 OSs, and for the IBM AIX 5.1 and 5.2 OSs. The ASL must be installed on the same host system as the Volume Manager software to enable it to recognize the Sun StorageTek 6140 Array trays.
Download the ASL and the accompanying README file for the Sun StorageTek 6140 Array from the Sun Download Center, http://www.sun.com/software/download/. Download the AIX ASL from http://support.veritas.com. The AIX ASL is available only from VERITAS.
1. Log in as superuser on the Sun server to be connected to the array.
2. Go to the Products Download page:
http://www.sun.com/software/download
3. In the Search area, search for VERITAS.
The Products Downloads > VERITAS Volume Manager ASL link is displayed.
5. If you have not previously registered, register as follows:
a. Click the Register Now link at the bottom of the left column.
b. On the registration page, complete the required fields and click Register.
a. Type your user name and password in the left column, and click Login.
b. On the Terms of Use page, read the license agreement, click Yes to Accept, and click Continue.
7. Download the compressed zip file that contains the ASL package for the Sun StorageTek 6140 array and README file.
8. Use the unzip command to extract the files.
9. Refer to the README file for instructions on installing the VERITAS Volume Manager ASL.
1. Go to the Veritas AIX ASL page:
http://support.veritas.com/docs/279730
A page displays with the ASL installation instructions.
2. Read the instructions and click the Download Now button.
3. Follow the instructions to uncompress and install the ASL.
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.
This section describes known issues and bugs related to installing and initially configuring the Sun StorageTek 6140 Array.
Bug 6258674 - You should not perform volume operations, such as volume resizing, until volume initialization is complete. The Sun StorageTek 6140 Array can hang if volume resizing operations are done before a volume is initialized.
Bug 6359847 - After the sccs reset array command is run, the array ID is not recognized by the system and cannot be modified.
|
Caution - Resetting the array destroys all user data, including volumes, hosts, and initiators. |
Workaround - After you reset the array, the name is blank. You can reset the name as follows:
1. Use the sscs command sscs list array array.no.name to provide the World Wide Name (WWN) for the unnamed array.
The output shows, among other things, the WWN for the array:
60:0A:0B:80:00:16:41:A9:00:00:00:00:42:6D:94:D7
2. Use the WWN in the modify array command to reset the name. For example:
sscs modify -N array-10 -T wwn array 60:0A:0B:80:00:16:41:A9:00:00:00:00:42:6D:94:D7
In this example, the array name is reset to array-10.
Bug 6356732 - When modifying the DHCP usage of an Ethernet port on the Controllers page, if you change the DHCP selection from Enable DHCP to Specify Network Configuration without changing the IP address of the port, the change to the DHCP setting will not take effect.
|
Note - After Specify Network Configuration is selected, the IP box may stay grayed out, but the value can be changed. |
Workaround - If you want to set the Ethernet port to a Static configuration with the same IP address the port is using under DHCP, change the IP address first to a different address, then back to the desired one. The temporary IP address should not currently be in use.
Bug 6356119 - The first time the online help window is displayed, the application might log you out.
Workaround - Reenter the application from the main Java Web Console page.
This section describes general issues related to the Sun StorageTek 6140 Array hardware and firmware.
Bugs 6339202 & 6358173 - The 6768A (QLogic 2342) 2-Gb dual-port adapter cannot be used in direct attach mode, and you cannot boot from it.
Workaround - To use 6768A in direct attach mode, move the jumpers from pins 1 to 2. To boot using this HBA, move the 6768A jumper pins from 2 to 3 and put a switch between the host and array.
Bug 6415976 - Volumes on expansion trays are failed by the controller when all access to the expansion tray is lost. A failed volume cannot be recovered even after power to the expansion tray is restored.
Workaround - Follow correct power up and power down procedures.
Bug 6411928 - Switch ports used for the dedicated link in a remote replication are not automatically usable as regular ports when the replication link is removed.
Workaround - Disable and re-enable the switch port to make it usable for regular data access.
Bug 6417872 - When Small Form-factor Plugs (SFPs) are installed into the I/O Module (IOM) 2A and 2B ports, the front amber fault LED lights and the IOM displays an "H8" error.
Workaround - Do not install SFPs into these slots; they are reserved for future use.
Bug 6352085 - A write-cache activation error causes the mpxio failback to not complete when no controller batteries are installed.
Workaround - Install batteries in the controller. This will be fixed in Solaris 8 and Solaris 9 patch SAN 4.4.10, and Solaris 10 patch 118833-16 (Sparc) or patch 118855-14 (x86).
Bug 6388627 - When an expansion tray goes down, access to the volumes and other virtual storage elements on that tray is lost.
Workaround - Restore the correct mapping, pools, and profiles.
Bug 6180131 - Using a faulty expansion cable causes the management software to report the array health as Degraded and causes the Sun Storage Diagnostic Environment to report the error Drive tray path redundancy lost. However, the status LED on the front of the chassis does not signal an error and remains green instead of turning amber, as expected.
Bug 6203836 - If a volume failure on a Sun StorageTek 6140 Array results from failed disk drives, you must be careful when introducing replacement drives that were part of a volume in use by another Sun StorageTek 6140 Array.
Workaround - To avoid having the array incorrectly initiate a volume migration process with the newly introduced replacement drives, perform one of the following tasks:
The following issues are related to Solaris OS 10 incompatibilities.
Bug 6378869 - During a live host upgrade with I/O running, the host panics and I/O fails.
Workaround - Do not upgrade a host with I/O running. Will be fixed in Solaris 10 patch 118833-16 (SPARC) or patch 118855-14 (x86).
Bug 6358541 - An infinite failover loop occurs when there is a path failure on the volume of a primary array, when the volume is a part of a replication set.
Workaround - This will be fixed in Solaris 10 patch 118833-16 (Sparc) or patch 118855-14 (x86).
Bug 6362850 - The cfgadm -c unconfigure command unconfigures Universal Transport Mechanism (UTM) LUNs only and not other 'data' LUNs. When this happens, you will not be able to unconfigure LUNs.
Workaround - Will be fixed in Solaris 10 patch 118833-16 (Sparc) or patch 118855-14 (x86).
This section lists issues related to data replication.
Bug 6406178 - When a replication set is created between a Sun StorEdge 6130 Array and a Sun StorageTek 6140 Array, the PID from the primary array is copied onto the secondary array. The format command displays the label as type CSM1, whereas luxadm displays the same label as type CSM2.
Bug 6266943 - After becoming a secondary volume of a replication set, a volume that was previously recognized by a host (through the format command) is displayed as drive type unknown. This secondary volume should be designated as a read-only device.
Workaround - Ensure that the intended secondary volume is a new (unlabeled) volume. Do not use an existing volume.
This section describes known issues and bugs related to the Sun StorageTek Configuration Service software.
Bug 6224251 - When creating initiators on an array previously connected to a host, be aware that should this host be removed and another host attached, the pull-down menu for creating an initiator will show the WWNs for the original host, as well as the WWNs of the new host.
Workaround - Reboot the array.
Bug 6418696 - Controller tray IDs can be set to any number between 0 and 99. However, they should be limited to the values of 80 through 99, with expansion trays using 0 through 79. If tray IDs are duplicated, the array will not be able to detect the drives on one of the two trays that have the same ID (which one is arbitrary).
Workaround - Ensure that any assigned tray ID value is not a duplicate.
Bug 6410568 - A failed base volume stays read-only even after the associated snapshot volume has been deleted. If a reserved volume exceeds threshold, the base volume fails as expected, and further writes to the volume are blocked. After the snapshot volume is deleted, the base volume should regain its read/write permissions.
Bug 6340983 - Users can see management LUNs using format and other utilities, causing confusion when LUNs should be hidden. This is corrected by the following patches:
Bug 6433629 - Patch 113277-44 fixes the problem reported in Bug 6340983, but causes delays and errors when users configure or unconfigure LUNs.
Bug 6403778 - After a firmware upgrade, the luxadm display lists two secondary paths instead of one as primary.
Workaround - Use the luxadm command to reset a path to primary.
Bug 6413513 - The window title for the Configuration Service wizard window title is displayed as "Sun StorEdge 6130"; it should be "Sun StorageTek Configuration Service."
Bug 6416083 - The Configuration Service interface shows double views when the interface times out and the user tries to change view. The timeout occurs when multiple applications are running.
Workaround - Close the browser window and reopen it.
Bug 6416680 - When you change a tray ID using the Configuration Service software, the component appears to have been replaced with a new component.
Workaround - Avoid changing tray IDs. If you must change the tray ID, expect and delete the resulting alarm.
Bug 6405314 - When using Service Advisor to place a controller offline, an error occurs stating that a connection cannot be opened to an alternate controller. Investigation reveals that Service Advisor has an invalid IP address for the alternate controller.
Workaround - Delete and reregister the alternate controller array on Service Advisor. Reset the password and retry the operation.
Bug 6329784 - When an initiator is added or removed from a zone in a fabric, the Configuration Service software does not dynamically detect the change. The WWNs of initiators newly added to the SAN are not displayed.
Workaround: If the WWN of a new initiator is not in the drop-down list on the New initiator page, try creating the initiator by manually entering the new WWN. This will force the page to refresh. When you create another new initiator, the WWN will be in the list.
Bug 6408489 - When you use the Configuration Service software to set the "Disk Scrubbing With Redundancy Enabled" parameter from True to False while the Disk Scrubbing Enabled parameter is set to False, the page reports success but the value of Disk Scrubbing Enabled remains False. When you make this change using the CLI, the prompt returns without a message, but the disk scrubbing setting remains the same as it was.
Bug 6400524 - The path information in the luxadm display output is not reliable.
Workaround - Before disconnecting cables, use the Configuration Service software to verify that LUNs are not on an active path.
Bug 5079007 - When the first path to a device is disabled, luxadm fails to display device information.
Bug 6371462 - The switch setting 2 Gb/s or 4 Gb/s applies to the speed of the internal FC data path to disk drives. When a 2-Gb/s drive is set to 4 Gb/s, the drive enters a status of Bypassed.
Volumes on Bypassed drives are marked as Missing and lose their pool assignment. They are displayed on a separate Ghost Volumes list, with minimal info available.
Bug 6416025 - The Configuration Service interface shows a tray health of OK after an I/O module (IOM) is removed from the tray. The health status reflects the state of the tray and batteries, but not of other components such as IOMs and Small Form-factor Plugs (SFPs).
Workaround - To monitor the health of these subcomponents, see appropriate events and alarms in the Sun Storage Automated Diagnostic Environment software.
Bug 5084996 - When run for the first time from one of the hosts in a multihost configuration, the format command might fail to detect all 256 or more LUNs created on the Sun StorageTek 6140 Array.
Workaround - Wait a few minutes, and then execute a second format command. All volumes should now be detected.
Bug 6238963 - If you refresh a Configuration Services page using the browser Reload button, the following message is displayed:
The page you are trying to view contains POSTDATA. If you resend the data, any action the form carried out (such as search or online purchase) will be repeated. To resend the data, click OK. Otherwise, click Cancel.
If you click OK in response, error messages appear or unexpected actions occur.
Workaround - Do not use the browser refresh button when using any Java Web Console application, such as Configuration Service. Use the application Refresh button only.
If you do use the browser Refresh button, press the Cancel button in response to the prompt instead of the OK button.
Bug 6246249 - When the array is locked for a Service Advisor procedure, a reservation message displays in the Sun StorageTek Configuration Service browser interface only on the management host initiating the procedure.
Workaround - Using the Storage role, warn others of pending Service Advisor procedures, since they will not receive a warning when making configuration changes from a different host.
Bug 5084996 - When you run the Solaris format command to detect a large number of LUNs that have just been mapped to a Solaris system from a Sun StorageTek 6140 Array, there might be some delay before the Solaris host detects and reports these newly added LUNs. This behavior typically happens only when more than 100 LUNs are simultaneously mapped to the Solaris system.
Workaround - Wait approximately 20 minutes after the volumes have been created for all of the LUNs to be properly detected when you issue the format command. This is fixed in version 4.4.10 (Solaris 8 and 9) of the Sun StorageTek SAN Foundation software.
This section describes known issues and bugs related to the Sun StorageTek 6140 Array CLI.
Bug 6422504 - A user who knows the password and the URL syntax used by the Storage Automated Diagnostic Environment's middle tier for sscs commands could potentially run any system command.
Workaround - Change the default password at all the application levels (Storage Automated Diagnostic Environment middle tier and GUI tier) and change the file permissions of the password stored at the UI level, as follows:
1. Set the Storage Automated Diagnostic Environment password to unique value. Use the same password everywhere.
2. Set all the default passwords in Storage Automated Diagnostic Environment:
ras_admin login_update -l peer -p $PASSWORD
ras_admin login_update -l srm -p $PASSWORD
ras_admin login_update -l ras -p $PASSWORD
ras_admin login_update -l $PASSWORD
3. Set each password so SLM and Configuration Service can use the Storage Automated Diagnostic Environment Client API.
echo peer:$PASSWORD > /opt/SUNWstade/DATA/IPC_Access
chmod 600 /opt/SUNWstade/DATA/IPC_Access
chown noaccess /opt/SUNWstade/DATA/IPC_Access
4. Set the master/slave password:
This section describes known issues and bugs related to the Sun Storage Automated Diagnostic Environment software that may affect operations of the Sun StorageTek 6140 Array. Read the release notes that came with your Sun Storage Automated Diagnostic Environment software for a complete understanding of issues and bugs.
Bug 6417279 - Whenever a storage system is reserved for maintenance using the Service Advisor, the Run Agent skips the reserved system.
Bug 6418428 - There are several problems in the tray midplane removal/replacement procedure that make it unusable. If you need to perform tray midplane removal and replacement, call Service.
Bug 6416680 - When someone changes a tray ID, an email is automatically issued that gives misleading information and incorrectly instructs the user to perform unnecessary remedies. In fact, no action is necessary.
Bug 6417891 - In Service Advisor, Array Troubleshooting and Recovery, Recovery From an Overheated Power Supply fails to light the white LED and generates errors.
Bug 5086807 - In Sun StorageTek 6140 Array configurations using expansion trays, if one RAID controller or one of the inter-tray cables connecting the RAID controller to the expansion trays is removed, some expansion tray data fields are reported incorrectly.
This results from the loss of one monitoring path to the expansion tray. The incorrect data fields from the expansion tray can cause the Sun Storage Automated Diagnostic Environment to incorrectly report a firmware revision change on the expansion trays.
Workaround - Replace the missing cable or missing RAID controller to restore full and accurate status reporting of the expansion trays.
Bug 6405520 - The Storage Automated Diagnostic Environment agent cannot be run when the system is reserved for maintenance.
Workaround: Do not use the reserve maintenance function to redistribute volumes, place a controller offline or online, or perform controller replacement procedures.
Bug 6421335 - When an expansion tray has been removed while the array is still active, it remains listed in the Tray Summary window.
Workaround - Release reservation of the array in Service Advisor before attempting to rerun the Storage Automated Diagnostic Environment agent.
Bug 6419046 - The Storage Automated Diagnostic Environment Alarm Summary page shows a status of Degraded on alarms that have been repaired and acknowledged.
Workaround - Delete the events in the Storage Automated Diagnostic Environment so the array can report an OK status.
Bug 6418380 - The Service Advisor in the Storage Automated Diagnostic Environment has a diagram showing RAID controller LEDs; the LED on the rear of the controller closest to the ID/Diag display is mislabeled as "Power (On or Off)". This is actually the Cache Active LED, as stated correctly in the Sun StorageTek 6140 Array Getting Starting Guide.
Bug 5076153 - Results of diagnostic tests are not updated during the tests on the data hosts or management hosts using Perl Version 5.8.
The following error message appears:
Error on test-name: ERR: Invalid PID:
The test results are updated when the test finishes.
Workaround - Run diagnostic tests from the command-line interface on the client, or simply wait for the test to reach completion.
Alternatively, use an older version of Perl.
Bug 5096265 - When you manually place a controller offline using the Sun Storage Automated Diagnostic Environment, monitoring applications might report this offline controller as Failed. This is expected behavior. After you place the controller back online, the controller state will change to Optimal.
This section describes known issues and bugs related to the online help, the command-line interface sscs man page, or any other Sun StorageTek 6140 Array release documentation.
Both the Sun StorageTek 6140 Array Getting Starting Guide and the 6140 Array Host Software CD booklet state that, to unpack the contents of the compressed installation file, you must double-click the RunMe.bin icon or type the command ./RunMe. This is incorrect. If typing the command, you must execute ./RunMe.bin from the bin directory.
The final version of the 6140 Array Getting Starting Guide was not included on the CD-ROM for this release. However, a hardcopy of the Getting Starting Guide is included in the box with the array. The appropriate version of the guide is also available in PDF format on the Sun documentation web site (http://www.sun.com/documentation).
Page 136 of the Sun StorageTek 6140 Array Getting Started Guide shows a default of 8 domains for 6140 array. There are no default domains for the 6140 array. Also, page 122 mentions enabling premium features for 16 or 64 domains. Optional domains can be purchased in the following allotments:
Bug 6407953 - The number of Fibre Channel ports shown in illustrations of controllers varies. Disregard the display showing four ports.
The descriptions for the battery LEDs in the 6140 Array Getting Starting Guide and the Configuration Service online help are incorrect. In both places, the data for the LEDs references the power supply instead of the battery. These tables need to be updated to reflect the appropriate data for the battery LEDs.
The following table shows the corrected Battery Backup LED descriptions:
Bug 6400237 - The 6140 Array Getting Starting Guide procedure for establishing a connection with the serial port to display the Service Interface menu needs to be updated for Solaris with the following information:
When using the tip application, it is necessary to use ~# to send a Ctrl-Break, as in the following example:
Bug 6400929 - The procedure for enabling multipathing software in the 6140 Array Getting Starting Guide is valid for Solaris OSs 8 and 9. For Solaris OS 10 and above, multipathing must be enabled as follows:
1. Run # stmsboot -e to enable multipathing on all FC ports.
WARNING: This operation will require a reboot.
Do you want to continue ? [y/n] (default: y)
Bug 6414602 - Page 99 of the Getting Starting Guide should read as follows:
1. On the Array Summary page, click the Register Button to launch the Register wizard and discover arrays on the subnet.
There are two methods of registering arrays:
The headings on page 99 should be as follows:
Bug 6183884 - The online help for volume snapshots indicates that creating a snapshot causes the array controller tray to suspend input/output (I/O) to the base volume during creation of a physical volume. However, this is incorrect. The I/O is not suspended in this situation.
There are no localization issues at this time.
This section provides useful operational information not documented elsewhere.
The 6140 array does not include default storage domains. You must purchase a premium license to be able to use the storage domain feature.
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 create a volume and label it, you can start using the volume before it is fully initialized.
During bootup, the battery light might flash for an extended period. The battery charger performs a series of battery qualification tests before starting a battery charge cycle. This series of tests occurs at subsystem power-up. The tests are automatically reinitialized approximately every 25 hours by a timer.
Each controller tray contains a hot-pluggable lithium ion battery pack for cache backup in case of power loss. The on-board battery is capable of holding a 2-gigabyte cache for three days (72 hours). The service life of the battery pack is three years, at the end of which the battery pack must be replaced (it is field-replaceable).
Data replication can generate three warnings in the Sun Storage Automated Diagnostic Environment software that require no action:
This warning indicates a positive state change. The data replication link is operating nominally.
This warning indicates a negative state change. Either the data replication link is physically broken, or the round-trip time exceeds the maximum allowed delay.
This warning indicates a significant change in the World Wide Name (WWN) of the mirrored volume and may indicate a change in configuration.
Following is a list of documents related to the Sun StorageTek 6140 Array. For any document number with nn as a version suffix, use the most current version available.
You can search for this documentation online at http://www.sun.com/documentation.
In addition, the Sun StorageTek 6140 Array includes the following online documentation:
Contains system overview and configuration information.
Includes system maintenance, management, and basic troubleshooting information.
Provides FRU replacement procedures with system information in a section of the Sun Storage Automated Diagnostic Environment interface.
Provides help on man page commands available on a management host or on a remote CLI client.
If you need help installing or using this product, go to:
http://www.sun.com/service/contacting
Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
| Sun StorageTek 6140 Array Release Notes | 819-5044-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Upgrade the Management Host Software
