Sun StorEdge 3310 SCSI Array Release Notes
This document contains important information about the Sun StorEdge 3310 SCSI array 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 impact the installation and operation of the Sun StorEdge 3310 SCSI array.
Read this document so that you are aware of issues or requirements that can impact the installation and operation of the Sun StorEdge 3510 FC array and the Sun StorEdge 3511 SATA array.
See Upgrading to Software Version 2.5 and Controller Firmware Version 4.2x for information about downloading and installing the firmware package that contains the README file and other supplemental information.
This release includes new versions of RAID controller firmware and related enclosure firmware, Sun StorEdge Configuration Service, Sun StorEdge Command-Line Interface (CLI), and Sun StorEdge Diagnostic Reporter. It incorporates requested enhancements as well as fixes to previously known issues.
|Note - The Sun StorEdge 3000 Family of storage products, including the Sun StorEdge 3510 FC array and the Sun StorEdge 3511 SATA array, are now often referred to as Sun StorageTek storage products. These are identical products. To avoid confusion, the manuals for these products will retain the old Sun StorEdge designation.|
The RAID controller firmware upgrade procedure has been streamlined and simplified, and additional logging capabilities have been added to the upgrade script. Refer to the Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide , 819-6573 for step-by-step procedures for upgrading RAID controller firmware version 3.2x to version 4.2x.
|Caution - These procedures must be followed when performing this major upgrade. Minor upgrades from earlier versions of 4.1x firmware do not require the use of this document and can be performed by following the instructions in the firmware patch README file.|
The RAID controller’s firmware now displays the current NVRAM version installed on the controller in the View System Information window. This helps diagnose any conflicts that might have occurred if a controller was replaced or new firmware installed without resetting NVRAM. Refer to the Sun StorEdge 3000 Family RAID Firmware 4.2x User’s Guide, 817-3711-17 for instructions on how to use this feature.
RAID controller firmware versions 4.23 and beyond include a Clear Core Dump firmware option on the system Functions menu.
In a redundant controller configuration, if an unrecoverable error condition occurs, the affected controller might write debug information to NVRAM. If this happens, an event message will be displayed each time the controller reboots, such as the following:
This message is displayed each time a failed controller is restarted after a redundant controller failure and does not indicate a new controller failure. The date and time of the event message indicates the time the controller was restarted, not the time of the failure.
If the unrecoverable error recurs, clear the core dump only on the advice of your support representative.
Refer to the “System Functions” chapter and “Event Messages” appendix of the Sun StorEdge 3000 Family RAID Firmware 4.2x User’s Guide, 817-3711, for details about clearing core dumps and about unrecoverable error messages.
Sun StorEdge Configuration Service uses a distributed architecture to monitor RAID arrays. One--and only one--Configuration Service console, a process called ssmon running on a host, gathers information from the array to which it is connected. Up to ten Configuration Service agents communicate this information as needed. Running more than one Configuration Service console is not supported. In previous releases, doing so could cause data loss.
|Note - It might be possible to inadvertently set up more than one host session running a Configuration Service console if ssmon is used to communicate with an SNMP client such as OpenView. Refer to your platform's
Connecting Sun StorEdge 3320 expansion units to Sun StorEdge 3310 RAID controllers is supported, but the Sun StorEdge 3320 drives will only perform at U160 speeds rather than U320 speeds. However, connecting a Sun StorEdge 3310 expansion unit to a Sun StorEdge 3320 RAID controller is not supported.
A number of firmware and software changes occurred when RAID controller firmware 4.11 was introduced; they apply to all firmware 4.x versions. TABLE 1 describes these changes.
By default, each chassis has an IP address assigned to it if your network uses a Dynamic Host Configuration Protocol (DHCP) server to automatically allocate IP addresses to attached devices. You can then access that IP address through the Sun StorEdge CLI, Sun StorEdge Configuration Service, or the firmware application. If you do not use a DHCP server and therefore have no IP address, you can set an IP address through serial connection to the firmware.
The firmware allows up to 64 TB per logical drive configuration with sequential optimization and up to 16 TB per logical drive configuration with random optimization. These limits are further modified by available drive sizes and the maximum number of drives allowed per product.
This optimization mode applies to cache optimization, rather than stripe size. You can fine-tune performance by setting the most desirable stripe size for each logical drive to best match the application of that logical drive. For more information, see Optimization Mode and Stripe Size Features.
The media scan feature sequentially checks each physical drive in a selected logical drive, block by block, for bad blocks. If a bad block is encountered, the controller rebuilds the data from the bad block onto a good block if one is available on the physical drive. If no good blocks are available on the physical drive, the controller designates the physical drive “Bad,” generates an event message, and if a spare drive is available, will begin rebuilding data from the bad physical drive onto the spare.
The media scan feature generates informational event messages for each drive that is part of a logical drive. The informational event messages are also generated each time a controller is reset or a logical drive is created. During the media scan, the green front-panel LEDs blink rapidly for every active drive comprising the logical drive.
Similar to Sun StorEdge Configuration Service, the controller firmware can send SNMP traps to an SNMP management console, send email messages, and broadcast events to specified servers, as defined in a text file called agent.ini.
For security reasons, you can restrict the network protocols you want to support, which limits access. Protocol access that can be enabled or disabled includes telnet, HTTP, HTTPS, FTP, SSH, PriAgentAll, SNMP, DHCP, and ping.
Set this security measure so that any telnet connection automatically disconnects after the connection has been idle for a configurable period of time. The current setting is displayed with the menu option.
Enabling Online Initialization or Online Expansion enables you to use the logical drive while it is being initialized or expanded. However, the completion of the initialization or expansion takes longer than if these processes are run while the logical drives are not in use.
For added security, a password can be supplied for access to the array using a telnet session or tip session. If a password has not been established, pressing the RETURN key enables access to the firmware menu.
When upgrading controller firmware from an earlier version of 4.1x, the Drive Predictable Failure Mode (SMART) will be set to 'Detect only' by default if the prior setting was 'Disabled.' The recommended setting is 'Detect and Clone+Replace' and must be set manually after the upgrade is complete.
|Note - After upgrading from 4.1x to 4.2x, an array reset is necessary for the new media scan default to take effect and automatic media scanning to stop.|
Sun has made changes to the firmware for the StorEdge 3310 and 351x arrays between versions 3.2x and 4.x that can impact performance. The algorithm for aggregating small writes in the cache has been improved so that they can be written to disk at the same time. This results in improved performance under workloads that issue mostly small sequential writes, or many small random writes within the same region. The performance improvement is most dramatic under workloads that queue many commands to the array, giving it the most opportunities to aggregate writes. Users should tune their applications and host driver stacks to queue up to 32 commands whenever possible.
Sun has also added increased error and data integrity checking to firmware 4.11 and later versions that can have an adverse affect on performance for StorEdge 33x0 and 351x arrays when upgrading from firmware version 3.2x. Users might experience a decrease in performance under workloads that primarily issue sequential reads. To mitigate this impact, tune applications and host driver stacks to issue the largest reads and maintain the highest queue depths possible.
Users may also see a small performance decrease under workloads that primarily issue large sequential writes. These users should also tune their host to issue the largest writes possible and maintain a large command queue depth.
|Note - Choosing sequential optimization, the default, almost always results in better performance than choosing random optimization, even if random optimization performed better for your configurations and applications in firmware versions 3.x. See Optimization Mode and Stripe Size Features for explanatory details.|
Firmware and software changes between 4.15 and 4.2x have no significant impact on performance.
Using cache write-through mode rather than write-back mode can have a significant impact on performance. To ensure that write-back cache is enabled for all LUNs after upgrading RAID controller firmware, from the RAID controller firmware Main Menu choose “view and edit Configuration parameters > Caching Parameters > write-back cache.” If it is disabled, choose 'Yes' to change the setting to Enabled.
Additional safety checks have been added to the 4.x firmware that will disable write-back cache and change the cache to write-through mode under certain error conditions. Conditions that can cause the array to switch to write-through mode include:
Once the condition is corrected, write-back cache is automatically re-enabled.
In firmware versions 4.11 and later, these triggering events can be enabled or disabled, and the threshold limits can be set, using the RAID controller firmware’s Main Menu. For more information about write-back cache, refer to Chapter 11, “Configuration Parameters,” in the Sun StorEdge 3000 Family RAID Firmware 4.2x User's Guide.
The optimization mode in firmware version 4.x controls cache block size only. This is a significant improvement in functionality and performance over earlier 3.x firmware, where the optimization mode chosen also determined stripe size for all logical drives.
With firmware version 4.x, when you specify sequential or random cache optimization, the controller determines and specifies a default stripe size for newly-created logical drives. However, you can specify a stripe size for each logical drive when you create it, enabling you to maximize performance by matching stripe size with your application requirements. Since different applications can use different logical drives, this functionality provides you with greatly increased flexibility.
Because of this, sequential optimization, which is the default, is almost always the best optimization choice. You should use random optimization only when performance testing in your production environment demonstrates improvement over the default sequential optimization.
For sequential optimization, the cache block size is 128 Kbyte. Available stripe size options include 16 Kbyte, 32 Kbyte, 64 Kbyte, 128 Kbyte, and 256 Kbyte. The default stripe size for sequential optimization is 128 Kbyte for all logical drives except RAID 3, which is 16 Kbyte.
For random optimization, the cache block size is 32 Kbyte. Available stripe size options include 4 Kbyte, 8 Kbyte, 16 Kbyte, 32 Kbyte, 64 Kbyte, 128 Kbyte, and 256 Kbyte. The default stripe size for random optimization is 32 Kbyte for all logical drives except RAID 3, which is 4 Kbyte.
With firmware version 4.x, you can also specify a cache write policy for each individual logical drive, giving you further opportunities for performance tuning.
The following table summarizes the functionality described above:
Sets block size for cache in a chassis. Stripe size for each logical drive is user-selectable, but optimization mode determines default stripe size. Use the default sequential optimization unless real-world tests in your production environment show better results using random optimization.
Specify a write-back or write-through cache policy for the entire RAID array. Specify a default write-back, or write-through policy for each logical drive. Specify event triggers that switch cache policy from write-back to write-through when specific environmental events occur, and switch back when the condition is rectified.
A CD-ROM containing Sun StorEdge Configuration Service and Diagnostic Reporter software, installation and configuration documents, along with Sun StorEdge 3000 family documentation, is not automatically shipped with the Sun StorEdge 3120, 3310, 3320, 3510, and 3511 products. Contact your Sun sales representative if you need these contents made available on a CD-ROM.
The most recent versions of software previously shipped on CD are available by clicking the “StorageTek 3000 Family Storage Products--Related Software V 2.3 General Availability” link on this Sun Download Center page:
You can download the related hardware and software documentation by clicking the appropriate Sun StorageTek 3xxx Array link on Sun Microsystems Documentation’s Workgroup Storage web page:
These release notes supplement the documents shown in TABLE 3.
If you need help installing or using this product, call 1-800-USA-4SUN, or go to:
The supported operating systems are:
Supported Sun Enterprise and application software includes:
Before you install Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, or the Sun StorEdge CLI, make sure that your system meets the Java Runtime Environment (JRE) prerequisites shown in the Sun StorEdge 3000 Family Software Installation Guide instructions for your operating system. In general, you can use Sun JRE version 1.2.2 or later for all platforms. IBM AIX and SUSE Linux can also use IBM JRE version 1.2 or later.
By default, a Solaris host is configured for one host LUN per SCSI target, which is insufficient for a Sun StorEdge 3310 SCSI array. You must edit the appropriate onboard HBA driver configuration file to add more targets and LUNs, up to 32 LUNs per logical drive, and a maximum of 128 LUNs per Sun StorEdge 3310 SCSI array.
Driver configuration files include /kernel/drv/qus.conf, /kernel/drv/mpt.conf, and /kernel/drv/glm.conf. Edit the file which is appropriate for your HBA.
|Caution - Do not edit the/etc/systemfile to accomplish the same purpose. While this can have the desired effect, it can also cause interference with other storage devices attached to the same host.|
|Note - Refer to the driver.conf(4) man page for information and syntax to use. Refer to your HBA release notes and your HBA installation guide for specific configuration information.|
Once you have edited the configuration file, reboot the host for the changes to take effect.
1. Edit the /kernel/drv/qus.conf, /kernel/drv/glm.conf, or /kernel/drv/mpt.conf file (whichever is appropriate to your HBA) to add more targets and LUNs (up to 32 LUNs per logical drive, and a maximum of 128 LUNs per Sun StorEdge 3310 array).
|Note - If the file does not exist, create it using the format shown in the following examples. Allow five blank spaces between “Sun” and “StorEdge” on the first line.|
In an environment where only Sun StorEdge 3310 SCSI devices are used, an example of text to add to /kernel/drv/qus.conf, /kernel/drv/glm.conf, or /kernel/drv/mpt.conf is:
In an environment where both Sun StorEdge 3310 and 3320 SCSI devices are used, an example of text to add to /kernel/drv/qus.conf, /kernel/drv/glm.conf, or /kernel/drv/mpt.conf is:
For more information about multiple device types, refer to the scsi_get_device_type_scsi_options(9F) man page.
2. Reboot the host to implement the file changes.
The Solaris 8 operating system requires a reconfiguration reboot to create device files and implement sd.conf changes, but you do not need a reconfiguration reboot for the Solaris 9 or 10 operating system.
For the Solaris 9 or 10 operating system, use the following commands to create device files after you have edited sd.conf. No reboot is necessary with this command:
The new LUNs are displayed when you perform the format command.
3. To display the new LUNs, perform the following command:
The Sun StorEdge 3310 array can be connected to a host in one of two ways:
TABLE 4 lists the supported host adapters and connections.
HP Ultra 160 SCSI Adapter for SCSI
IBM Dual channel PCI Ultra3 SCSI Adapter
|Caution - If you are using the Solaris 9 operating systems and if you are using the Sun StorEdge PCI Dual Ultra3 SCSI host adapter (X)6758A, you must download and install the adapter’s driver in the host where the adapter is installed. (Refer to the Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter Release Notes, part number 816-2157, for the download procedure.) Without the driver, any array connected to the adapter is not visible to the host, since this driver is not included in the Solaris operating system.|
TABLE 5 and TABLE 6 show the connection methods supported for each supported Sun server.
(X)6758A Host Adapter
Sun Fire V60x server
Perform the following steps to change the Ultra320 speed to the Ultra160 speed needed to operate with a Sun StorEdge 3310 SCSI JBOD array and the X9265A HBA.
1. Edit the mpt.conf file on the Sun x86-based system by creating a /kernel/drv/mpt.conf file with the following lines.
2. Reboot the system.
TABLE 7 shows the supported cabinets with their associated rackmount kits and other required kits. Refer to the Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays for installation instructions.
|Note - For more information about using Sun StorEdge arrays with the Sun Rack 900 and 1000 cabinets, refer to the Sun Rack 900 Qualified Products web page at http://www.sun.com/servers/rack/approved.html|
TABLE 8 gives descriptions and part numbers for the disk drives supported with the Sun StorEdge 3310 SCSI array.
|Note - In an array shipped with less than 12 drives, each empty slot in the array contains an air management sled to correctly handle the air flow and heat. Each drive slot requires either a disk drive or an air management sled.|
|Note - Disk drive firmware is provided through Sun disk firmware patches, which include the required download utility. Sun disk firmware patches are separate from the Sun StorEdge 3000 family firmware patches. Refer to the instructions in your disk drive firmware patch.|
|Caution - If you replace a disk drive, the replacement disk drive must have the same or greater capacity than the disk drive that is being replaced. You can mix capacity in the same chassis, but not spindle speed (RPM) on the same bus. For example, you can use 36 Gbyte and 73 Gbyte drives with no performance problems if both are 10K RPM drives. Violating this configuration guideline leads to poor performance.If you are adding a new disk drive, these same configuration guidelines apply.|
TABLE 9 lists the supported SCSI cables. Cables can be ordered using the marketing part numbers in TABLE 9.
|Note - The manufacturing part numbers supplied in the third column of the table can be checked against the manufacturing part numbers stamped on other cables that you might have in stock to confirm that they are supported.|
|Note - When you attach the provided SCSI bus cables to the Sun StorEdge 3310 SCSI array or expansion unit, it is important to tighten the cable jack screws with six full clockwise turns prior to powering up the array, to ensure proper operation.|
It is extremely important for the proper operation and reliability of the equipment that all network connectivity adhere to Ethernet and facility wiring standards IEEE 802.3 and EIA/TIA 568B. Make sure that the cabling and patch cords for your facilities are up to these specifications, and protect the cables from excessive stress and damage. The best practice, and the one that is recommended by all facilities wiring standards, is to test your structured cable system end-to-end with a quality cable test set. Adherence to these practices will help eliminate almost all connectivity issues.
Other related standards are ISO/IEC IS 11801 (International), Cenelec EN 50173 (Europe), CSA T529 (Canada), and SAA/SNZ HB27:1996 (Australia and New Zealand).
When a Sun StorEdge 3310 SCSI JBOD array equipped with Ultra320-capable disk drives is connected to the on-board Ultra320 SCSI port of one of these servers, the disks will attempt to negotiate the SCSI bus speed at Ultra320 speeds. However, because of design and other limitations, this is not supported. The on-board SCSI port of the Sun Fire V6Xx server must be limited to Ultra160 bus speeds.
Perform the following steps to configure the onboard SCSI port of the Sun Fire V20z, V40z, V60x, or V65x server to operate at Ultra160 SCSI speeds.
1. Power on the server.
2. When the Adaptec SCSI Bios appears, press <ctrl>-<a> when prompted.
3. Select slot a (external SCSI connection) and press Enter.
4. Select Configure/View SCSI Controller Settings and press Enter.
5. Select a Sync Transfer Rate (MB/sec) of 160 on all SCSI Device IDs.
6. Press Escape twice and select Yes to save changes.
7. Repeat Step 3 through Step 6 for mutable slots.
8. Press Escape to exit the utility.
The server will continue with the boot up.
Adding SCSI disks to a Sun Fire V20z, V40z, V60x, or V65x system running Red Hat AS 2.1 or 3.0 requires a change to where the system looks for the kernel. The new logical drive gets pushed to the front of the device list, so /dev/sdaX becomes /dev/sdbX. After reboot, the boot partition is now /dev/sdb3, and a kernel panic can result.
For Sun StorEdge 3310 SCSI arrays connected to the onboard AIC79xx, edit the
/etc/grub.conf file (or /etc/lilo.conf if you use lilo for your bootloader). This can be done before reboot or during boot up.
1. During boot up, press 'e' at the grub kernel selection screen.
2. Go to the line that points to the kernel and press 'e' again to edit the line:
kernel /vmlinux-2.4.9-3.24 ro root=/dev/sda3
3. If one drive was added to the system, change /dev/sda3 to /dev/sdb3 or for two new drives /dev/sdc3.
4. Press the Escape key to finish editing, and then press 'b' to boot.
These changes can also be made directly to the /etc/grub.conf file before reboot.
This section outlines the changes needed to enable either the Sun StorEdge 3310 RAID or JBOD arrays using the on-board SCSI port of the Sun Fire V440 systems.
For embedded controllers and (X)2222A, (X)4422A and (X)1018A HBAs, booting from the array requires no special procedures.
|Note - To ensure that the server will boot properly, the physical device must be mapped to LUN 0. Otherwise, the server will not boot properly.|
To boot a host through a Sun StorEdge PCI Dual Ultra3 SCSI host bus adapter (X)6758A, follow the procedures in the “Bootability” chapter in the Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter Installation Guide, part number 816-2156.
For a current list of patches for a Sun StorEdge PCI Dual Ultra3 SCSI host bus adapter, including driver patches, go to the web site and search for “Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter” in the “Search SunSolve” search area:
Bootability is not supported for this HBA on servers running the Solaris 10 operating system.
Make sure the Solaris Recommended Patch Cluster is installed on a Solaris host before connecting the host to the array.
1. Log in to the host that you want to connect to the array.
2. Go to: http://www.sun.com/sunsolve
3. Under Support, click Patches & Updates.
4. Under Downloads, click Recommended Patch Clusters.
5. Find your version of Solaris 9 or Solaris 10 in the Recommended Solaris Patch Clusters list, make sure the Readme checkbox is checked, and then click Go.
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 with 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 Save.
11. Follow the procedure in the INSTALL INSTRUCTIONS section in the README file to install the patches.
The upgrade process includes:
Use a recent version such as 2.x of the Sun StorEdge Configuration Service agent, Sun StorEdge Configuration Service console, Sun StorEdge Diagnostic Reporter, and Sun StorEdge Command-Line Interface (CLI) utility to download the firmware for your controller. If you are not using a recent version of this software, download and install it, using the following instructions, before downloading the controller firmware.
Because the communication protocol changes from version to version, you must install the SUNWsscs package on all systems that manage the storage when upgrading.
|Note - If different versions of the agent and console co-exist, Sun StorEdge Configuration Service is not able to discover previously configured arrays.|
To download the software from the Sun Download Center web site, perform the following steps.
1. Go to:
2. Under System Administration Storage Management, click the StorageTek 3000 Family Storage Products - Related Software link.
You are taken to the Sun StorEdge 3000 Family Storage Products - Related software page.
3. Click Download.
A Sun Download Center page is displayed.
4. Click Download.
A Sun Download Login page is displayed.
5. If not previously registered, register.
a. Click the Register Now link at the bottom of the left column.
b. On the registration page, enter applicable data in the required fields and click Register.
6. Log in.
a. Type your Username and Password in the left column, and click Login.
7. On the software download page, click the link for your array and operating system.
8. In the dialog box that is displayed, specify a destination directory and save the file.
|Note - For installation or upgrading instructions for other operating systems, refer to the Sun StorEdge 3000 Family 2.5 Software Installation Guide.|
To install or upgrade the software on Solaris operating systems, perform the following steps.
|Note - Before you install Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, or the Sun StorEdge CLI, make sure that your system meets the Java Runtime Environment (JRE) prerequisites shown in the Sun StorEdge 3000 Family Software Installation Guide instructions for your operating system. In general, you can use Sun JRE version 1.2.2 or later for all platforms. IBM AIX and SUSE Linux can also use IBM JRE version or later.|
1. Log in as superuser to install the package.
2. If you are upgrading, uninstall all current versions of Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, and Sun StorEdge CLI. To uninstall earlier versions of the software, type:
The single filename for software versions 2.x is SUNWsscs.
The filenames for software versions 1.x are listed in TABLE 10.
3. To install the version 2.5 software package, type:
The Solaris installation package, SUNWsscs, includes the following components:
4. Provide appropriate responses to each of the installation prompts.
a. If asked if you want to restore the agent configuration, type y. (If you type n, you will need to re-enable the managing servers.)
b. To continue with the installation, type y and press Return.
After the package is installed, the following message is displayed, indicating it was installed successfully.
The Sun StorEdge Configuration Service components are installed in the following directories:
The Sun StorEdge Diagnostic Reporter components are installed in the following directories:
The CLI is installed in /opt/SUNWsscs/sbin/sccli.
5. If you are using Sun StorEdge Configuration Service and Diagnostic Reporter to manage and monitor the storage, the following additional steps are required.
a. You must set passwords for all Sun StorEdge Configuration Service users.
|Note - User passwords are deleted when Sun StorEdge Configuration Service is uninstalled. Even if you had a previously saved configuration, you still have to reenter the ssmon, ssadmin, and ssconfig passwords.|
b. Before starting the Sun StorEdge Configuration Service console, you must run the following command to specify the web browser to access online help.
c. The Sun StorEdge Configuration Service agent and the Sun StorEdge Diagnostic Reporter agent (daemon) have been installed but are not configured to start at boot time by default. To enable the Sun StorEdge Configuration Service agent to start automatically when the system boots, and to start it now, type:
d. To enable the Sun StorEdge Diagnostic Reporter to start automatically when the system boots, and to start it now, type:
Firmware patch ID # 113722-19 is available from SunSolve to upgrade controller firmware for Sun StorEdge 3310 SCSI arrays running firmware versions earlier than 4.2x and to upgrade SAF-TE firmware earlier than 1180.
Firmware patch ID # 113722-19 provides the following firmware:
To determine the current firmware versions for your array, see:
To download the firmware patch, see To Download the Firmware Patch.
For information about installing the firmware, refer to the patch README file provided with the firmware patch.
|Caution - Review all procedures and release notes for this major upgrade prior to upgrading your array. DO NOT attempt to downgrade firmware back to controller firmware version 3.25. Such downgrades are NOT supported except when installing a new RAID controller FRU. If you feel you must downgrade your RAID controller firmware, contact authorized Sun service personnel for assistance. Time and materials charges may apply if not currently covered under warranty/support contract.|
|Note - Disk drive firmware is provided through Sun disk firmware patches that include the required download utility. Sun disk firmware patches are separate from the Sun StorEdge 3000 family firmware patches. Refer to the instructions in your disk firmware patch.|
To determine your current controller firmware version, use one of the following methods:
To determine your current SAF-TE firmware version, use the CLI and enter the show safte command. The SAF-TE version of each controller is displayed in the Rev column.
1. Go to http://sunsolve.sun.com
2. Under Support, click Patches and Updates.
3. Use PatchFinder to locate patch ID 113722-19 by entering the patch ID into the search field and click Find Patch.
4. Select the link for the format that you want, either HTTP or FTP next to Download Patch, or HTTP or FTP next to Download Signed Patch.
5. In the dialog box that appears, indicate the destination directory for the patch and proceed to download the file to that location.
6. Follow the instructions in the README file to install the patch.
This section describes what you need to do to enable VERITAS Volume Manager 3.5, 4.0, 4.1, and 5.0 software to work with the Sun StorEdge 3310 SCSI array on Sun hosts. VERITAS has provided an Array Support Library (ASL) that must be installed on the same host system as the Volume Manager software to enable the software to recognize the Sun StorEdge 3310 SCSI array. Follow the procedure to download the ASL and the accompanying installation guide for the Sun StorEdge 3310 SCSI array from the Sun Download Center.
1. Log in as superuser on the Sun server to be connected to the array.
2. Go to the All Products listing at the Sun Download Center.
3. Under the V heading, click on VERITAS Volume Manager Array Libraries (ASL).
4. Click the Downloads A-Z tab.
5. Choose the link that is appropriate for your platform.
6. Click Download to go to the Sun Download Center.
The page identifies the product you selected to download as VERITAS Volume Manager Array Support Library (ASL) for your platform and language.
7. If not previously registered, register.
a. Click the Register Now link at the bottom of the left column.
b. On the registration page, enter the required fields and click Register.
8. Type your Username and Password in the left column, and click Login.
|Note - In addition to the ASL that is specifically intended for your array, a recent ASL works with all Sun StorEdge 3000 family arrays. The title shown in the link for this ASL is VERITAS VOLUME MANAGER ARRAY SUPPORT LIBRARIES (ASLs).|
9. Download the compressed ZIP file that contains the ASL package for the 3310 SCSI array.
10. Use the unzip command to expand the zip file.
|Note - Note - To ensure cable and onboard HBA compatibility, review the HBA Sunswift manual for applicable restrictions.|