2730 Release Notes for Software Version J200R05 P/N 83-00004282-15 Revision A October 2007
Copyright Protected Material 2006-2007. All rights reserved. R/Evolution, RAIDar, Simulcache, EcoStor, and AssuredSnap are trademarks or registered trademarks of Dot Hill Systems Corp. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. U.S. Government Rights—Commercial use.
Contents Firmware Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 What’s New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Persistent IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 New Critical Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 RAID 6 Support . . . . . . .
Updating Expansion Enclosure Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Updating the Expansion Enclosure Using RAIDar Related Documentation Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release Notes This document contains late-breaking information about requirements that affect installation and operation of the R/Evolution 2730 and R/Evolution 2730T (2730 Turbo) storage systems. It supplements the R/Evolution 2730 documentation set. Note – In this document, unless otherwise stated, the term “R/Evolution 2730” refers to both the R/Evolution 2730 and R/Evolution 2730T products.
Firmware Versions These release notes describe the functionality of software package J200R05. ■ Management Controller (MC) firmware version W420R09 ■ MC Loader version 12.013 ■ Storage Controller (SC) firmware version J200R05 ■ SC loader 15.
New Critical Events In adding support for a new critical event that signals the 2730 shutting down due to temperature problems, a new critical event type has been defined. The previous event types were informational, warning, and error. Because of this change, SNMP traps are now mapped to corresponding categories of informational, minor, major, and critical. "Error" events are mapped to "major" severity traps. Informational and minor traps are unchanged.
PHY Status Diagnostic information relating to SAS expander controller physical channels (PHY lanes) has been enhanced to include additional status information. Also, the fault isolation algorithm can now be enabled or disabled. Scheduler You can use the Scheduler feature to create tasks and define schedules at which the system will automatically perform those tasks. Using the Scheduler, you can create tasks to take a snapshot, reset a snapshot, or copy a volume.
License Management Virtual Disk Service (VDS) and Volume Shadow Copy Service (VSS) hardware providers are now enabled through a license certificate file. Solaris MPxIO Volume Naming Structure The Solaris MPxIO volume naming structure has changed in this release from the structure used in release J11x.
Updating RAID Controller Software It is important that you install and configure your J200R05 software package file carefully, following the instructions in this section. Caution – Upgrading firmware from J110 or J111 to J200 is disruptive and must be performed off-line, with all host I/O stopped. Completing the upgrade requires a maintenance window of up to an hour. Caution – This upgrade procedure can be used to upgrade from J110 to J200.
4. If the IP address source is DHCP, change it to Manual to preserve the current IP values. a. Set Source For IP Address to Manual. b. Click Change LAN Configuration. When processing is complete, a message near the top of the page informs you that your change was successful. Retrieving Firmware from the Customer Resource Center 1. Download the firmware from Dot Hill’s Customer Resource Center at http://crc.dothill.com. a.
Updating the Controllers Using RAIDar Caution – Do not attempt to upgrade both controllers at the same time. It is not supported and will result in unpredictable failures and may yield unpredictable results. Note – Enable pop-ups on your browser for each controller. The upgrade process will produce a pop-up window to show you the progress of downloading the code. 1. Stop all host I/O. 2. Log in to RAIDar on controller A as a Manage user with the correct password. 3.
8. Log in to RAIDar on controller B as a Manage user with the correct password. The message area warns you that a code load is in progress. In this case, you can ignore the warning. 9. Select Manage > Update Software > Controller Software 10. Click Browse and locate neptunesw-J200R05-01.bin. 11. Click Load Software Package File When processing is complete, the page shows the version of each software component that will be installed. 12. Click Proceed With Code Update.
Your installation package contents included a micro-DB9-to-DB9 serial cable. If necessary, use a DB9-to-DB25 adapter (not included) for connecting the serial cable to a DB25 serial port on the host computer. 3. Start and configure a terminal emulator, such as HyperTerminal or VT-100, using the display settings in Table 1 and the connection settings in Table 2.
4. In the terminal emulator, connect to controller A. 5. Press Enter to display the CLI prompt (#). 6. At the prompt, type the following command to list the current settings: show network-parameters 7.
10. If you are not able to ping the controller, you need to restart the Management Controllers. a. Type the following command: restart mc both b. Confirm by typing Y. c. Enter the ping command again. 11. Exit the emulator and disconnect from the CLI. 12. Log in to RAIDar on controller A as a Manage user with the correct password. The login page is displayed. Continue with “Completing the Upgrade”. Completing the Upgrade 1.
Updating Expansion Enclosure Firmware If your RAID controllers are connected to expansion enclosures, after you have upgraded the firmware for the RAID controllers as shown in the previous instructions, update the expansion enclosure firmware for each connected expansion controller. You must update the firmware on each expansion enclosure individually. The upgrade process can take several minutes to complete. Updating the Expansion Enclosure Using RAIDar 1.
Note – Though the panel title that shows the version information is entitled “Displaying All Enclosure Processors,” it is actually only displaying information about all expansion enclosure processors. Version information about RAID controller enclosure processors is displayed when you select Manage > Update Software > Controller Software. Related Documentation These release notes supplement the documents shown below. .
Supported Systems The R/Evolution storage system has been verified as compatible with the software and hardware identified in the following subsections. Supported Operating Systems Operating systems supported in this release are shown below. Table 4 Supported Operating Systems Operating System Versions or Required Patches Windows 2003 Standard Edition With Service Pack 1 or R2 Windows 2003 Enterprise Edition With Service Pack 1 or R2 RedHat 4.
Supported Disk Drives Disk drives supported in this release are shown below.
Supported Fibre Channel Switches Fibre Channel switches supported in this release are shown below. Table 7 Supported Fibre Channel Switches Switch Firmware Version Brocade Switches Brocade 3250 5.3.0 Brocade 3850 5.3.0 Brocade 3900 5.3.0 Brocade 4100 5.3.0 Brocade 4900 5.3.0 Brocade 200E 5.3.0 QLogic Switches SANbox 2-8 6.7.0.04 SANbox 2-16 6.7.0.04 SANbox 5200 6.7.0.04 SANbox 5600 6.7.0.04 McData Switches Sphereon 4400 9.03.01 Sphereon 4700 9.03.
Supported HBAs and Operating Systems The following tables list supported Fibre Channel HBAs by operating system. Microsoft Windows 2003 Operating System HBA Support Fibre Channel HBAs you can use with Microsoft Windows 2003 are shown below. Table 8 Microsoft Windows 2003-Supported HBAs HBA Driver Emulex LP1050 1.30a9 Storport or later Emulex LP10000 1.30a9 Storport or later Emulex LP 11002 1.30a9 Storport or later Emulex LP 101 1.30a9 Storport or later Emulex LPe11002 1.
Solaris 10 Operating System HBA Support Fibre Channel HBAs you can use with Solaris 10 are shown below. Table 9 Solaris 10-Supported HBAs HBA Driver Emulex LP 11002 Solaris 10 Update 1 or later includes the needed driver Qlogic QLA2462 Solaris 10 Update 1 or later includes the needed driver The Solaris 10 operating system includes fp and fcp drivers, which each have a timeout setting. The default for fcp_offline_delay is 20 seconds.
The Solaris SAN Foundation Kit includes fp and fcp drivers, which each have a timeout setting. The default for fcp_offline_delay is 20 seconds. To avoid certain filesystem warning messages when a cable is removed or a controller is killed or shut down, you can change the timeout setting to 60 seconds by changing this line on Solaris 9 hosts in /kernel/drv/fcp.conf: fcp_offline_delay=60; Note – One reboot of the host is necessary for this parameter to take effect.
Recommended Settings for QLogic HBAs Recommended settings for QLogic HBAs are shown below.
Table 13 OS-dependent Emulex HBA Parameters (Continued) Parameter Windows 2003 Solaris 9 and Solaris 10 RedHat Linux SUSE Linux QueueTarget Enabled N/A N/A N/A Extra I/O Timeout N/A 0 N/A N/A lpfc-scsi-req-tmo N/A N/A 60 60 Supported SFPs Table 14 lists supported RoHS-compliant SFPs for use with a Fibre Channel (FC) controller enclosure.
6. Print or save the README file from the browser window. 7. Click the browser’s Back icon to return to the previous page. 8. Select the format you want in the row that begins Solaris 9, or Solaris 10 in the Recommended Solaris Patch Clusters list, click either Download HTTP or Download FTP, and then click Go. 9. In the File Download dialog box, click Save. 10. In the Save As dialog box, type a destination directory for the patch cluster, and then click OK. 11.
Snapshot Configuration The basic snapshot license that comes with the R/Evolution 2730 provides a maximum of 16 snapshots. An optional license can be purchased that expands this capability to a maximum of 64 snapshots. When you purchase this license, you receive a license key along with instructions for installing it. The instructions can be found in a document called Obtaining and Installing the License Certificate File, part number 83-00004343.
Known Issues The following sections describe known issues for this release. Persistent IP Address Beginning with the J200 release, the IP address is persistent. The IP address is stored on the midplane. When the controller is powered on, the firmware looks at the IP address in the midplane and stores this address in the controllers flash memory. When you replace a controller with a new controller, the new controller will have the same IP address as the old controller.
Known Bugs Known bugs in the J200 release are described below: ■ 4620: If a controller module is moved into another enclosure, stale licensing is presented in the WBI until a screen refresh is executed. The CLI is correct. ■ 4652: The CLI command set system name accepts 80 characters but only 79 are saved.
■ 4860: During online creation of a vdisk with a single volume spanning the entire allowable size of the vdisk, the free-space column (Free) will display a value of “B” when a show vdisk command is executed. For example: # show vdisk Name Size Free Own RAID Dsk Spr Chk Stat Jobs Serial# ------------------------------------------------------------------------------------------------------------RAID6.1 87.9GB B B RAID6 6 0 64 CRIT INIT 9% 00c0ff0a56710048c318cc4600000000 RAID6.2 87.
■ ■ ■ ■ 5030: Help for the Verify Virtual Disk page incorrectly says to click the Verify & Update Virtual Disk Parity button, but the button's correct name is Verify Virtual Disk Parity. 5035: Data corruption can occur upon a failover on SPARC Solaris 10 with Emulex HBAs and a Qlogic 5600 switch. The cause is redriving write I/Os to a switch port in which the WWNN of the target has changed due to the failover.
