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.

---

New Features in This Release

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.

New Instructions for Migrating From RAID Controller Firmware 3.2x to 4.2x

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.

Current NVRAM Version Displayed

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.

Recently Added Clear Core Dump Firmware Menu Option

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:

ALERT: Controller Unrecoverable Error 0001 00000000 00000000 45754677

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.

Consequences of Unsupported Configurations Minimized When Using More Than One Sun StorEdge Configuration Service Monitor Console (ssmon)

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.

Mixing Sun StorEdge 3320 and 3310 Controllers and Expansion Units

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.

---

Previous Feature Changes in 4.1x RAID Controller Firmware and 2.x Software

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.

Performance Implications of Migrating to Firmware Version 4.x

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.

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:

• Battery backup failure
• AC power loss
• Fan failure
• Power supply failure
• High temperature in CPU/Enclosure
• Failure of a redundant controller

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.

Optimization Mode and Stripe Size Features

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:

---

Obtaining Current Software and Documentation

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:

http://www.sun.com/software/download/

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:

http://docs.sun.com/app/docs/prod/wkgrp.disk

---

Release Documentation

These release notes supplement the documents shown in TABLE 3.

---

Service Contact Information

If you need help installing or using this product, call 1-800-USA-4SUN, or go to:

http://www.sun.com/service/contacting

---

Supported Operating Systems and Software

The supported operating systems are:

• 9 and 10 operating systems and later, SPARC Platform Edition
• Solaris 10 operating systems and later, x86 Platform Edition
• Red Hat Linux AS 3.0 and 4.0 and later
• Microsoft Windows 2003 Server operating systems
• IBM AIX 5.1, 5.2, and 5.3
• HP-UX 11i operating systems
• Novell Netware 5.1, 6.0, and 6.5
• SUSE Linux Enterprise Server 9.0, (32-bit and 64-bit)

Supported Sun Enterprise and application software includes:

• Sun StorEdge 3000 Family Configuration Service 2.x software
• Sun StorEdge 3000 Family Diagnostic Reporter 2.x software
• Sun StorEdge 3000 Family CLI 2.x software
• Sun Storage Automated Diagnostic Environment (StorADE) 2.4 software
• Solaris Volume Manager (for the Solaris 9 operating system and above)
• VERITAS Volume Manager 3.5, 4.0, 4.1, and 5.0. See Downloading the VERITAS Volume Manager Array Support Libraries for a description of how to obtain an Array Software Library (ASL) that enables the VERITAS software to work with the Sun StorEdge 3310 SCSI array.
• Sun StorEdge Performance Suite (with Sun StorEdge QFS software)
• Sun StorEdge Availability Suite
• Sun StorEdge Utilization Suite (with Sun StorEdge SAM-FS software)

Java Runtime Environment Requirements

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.

Enabling a Solaris Host to Recognize New Devices and LUNs

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.

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).

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:

device-type-scsi-options-list = “SUN     StorEdge 3310”,
“SE3310-scsi-options”;
SE3310-scsi-options = hexadecimal address;

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:

device-type-scsi-options-list =
		"SUN     StorEdge 3310", "SE33x0-scsi-options",
		"SUN     StorEdge 3320", "SE33x0-scsi-options";
	SE33x0-scsi-options = hexadecimal address;

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.

reboot -- -r 

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:

update_drv -f sd 
devfsadm

The new LUNs are displayed when you perform the format command.

3. To display the new LUNs, perform the following command:

format

---

Supported Connection Methods and Host Adapters

The Sun StorEdge 3310 array can be connected to a host in one of two ways:

• By means of a supported host adapter
• By means of a single-ended SCSI controller embedded in a supported host

TABLE 4 lists the supported host adapters and connections.

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.

---

Supported Sun Platforms and Connection Methods

TABLE 5 and TABLE 6 show the connection methods supported for each supported Sun 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.

name= “mpt” parent=”/pci@1f,700000”
unit-address=”2,1”
scsi-options=0x1ff8;

2. Reboot the system.

---

Supported Cabinets

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.

---

Supported Disk Drives

TABLE 8 gives descriptions and part numbers for the disk drives supported with the Sun StorEdge 3310 SCSI array.

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.

---

Supported Cables

TABLE 9 lists the supported SCSI cables. Cables can be ordered using the marketing part numbers in TABLE 9.

Network Connectivity Standard Practices

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).

---

Configuring Sun Fire V20z, V40z, V60x, and V65x Servers to Support JBODs (Linux and Windows)

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.

---

Modifications for Sun Fire V20z, V40z,V60x, and V65x Systems Running Red Hat AS 2.1 or 3.0

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.

---

Modifications for Sun Fire V440 Systems

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 the Sun StorEdge 3310 SCSI RAID array or the Sun StorEdge 3310 SCSI JBOD array, the following patches or greater are required to enable support:
• Sun StorEdge 3310 RAID: 113722-10 or later
• Solaris 9: 115663-03

• When a Sun StorEdge 3310 SCSI JBOD array equipped with Ultra320-capable disk drives is connected to the on-board SCSI port of a Sun Fire V440 system, the disks will attempt to negotiate at Ultra320. However, because of design and other limitations, this is not supported. The on-board SCSI port of the Sun Fire V440 system must be limited to Ultra160. This is done by creating a /kernel/drv/mpt.conf file with the following lines and then rebooting the system.


name= “mpt” parent=“/pci@1f,700000” unit-address=“2,1” scsi-options=0x1ff8;

---

Bootability

For embedded controllers and (X)2222A, (X)4422A and (X)1018A HBAs, booting from the array requires no special procedures.

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:

http://www.sun.com/sunsolve/

Bootability is not supported for this HBA on servers running the Solaris 10 operating system.

---

Required Patches

• The Solaris 9, or Solaris 10 Recommended Patch Cluster is required to use Sun StorEdge Configuration Service 2.x and Sun StorEdge Diagnostic Reporter 2.x. See To Download and Install the Solaris Recommended Patch Cluster for more information.
• Controller firmware patch 113722-19, containing firmware version 423A and SAF-TE firmware version 1180, is required. See Downloading and Installing Firmware for information about how to verify which firmware version is on your array and how to download the current version.
• If a Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter, X6758A, is used to connect the Sun StorEdge 3310 array, the bus driver must also be updated. The updated bus driver is available in the following patches:
• Solaris 9 Operating System: 112706-05
• Solaris 10 Operating System: 119555-03

---

Installing Required Solaris Patches

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.

---

Upgrading to Software Version 2.5 and Controller Firmware Version 4.2x

The upgrade process includes:

• Downloading and Installing Software Applications
• Downloading and Installing Firmware

Downloading and Installing Software Applications

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.

To download the software from the Sun Download Center web site, perform the following steps.

1. Go to:

http://www.sun.com/software/download/

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.

b. On the Terms of Use page, read the license agreement, click Yes next to Accept, and click Continue.

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.

To install or upgrade the software on Solaris operating systems, perform the following steps.

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:

# pkgrm filename

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:

# pkgadd -d . SUNWsscs

The Solaris installation package, SUNWsscs, includes the following components:

• Sun StorEdge Configuration Service agent
• Sun StorEdge Configuration Service console
• Sun StorEdge Diagnostic Reporter agent (daemon)
• Sun StorEdge Diagnostic Reporter Config Tool (UI)
• Sun StorEdge CLI

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.)

The previous configuration was saved. Do you want to restore the configuration [y,n,?,q]: y

b. To continue with the installation, type y and press Return.

Do you want to continue with the installation [y,n,?] y

After the package is installed, the following message is displayed, indicating it was installed successfully.

Installation of <SUNWscsd> was successful.

The Sun StorEdge Configuration Service components are installed in the following directories:

• /opt/SUNWsscs/ssagent
• /opt/SUNWsscs/sscsconsole

The Sun StorEdge Diagnostic Reporter components are installed in the following directories:

• /opt/SUNWsscs/ssdiagreporterd
• /opt/SUNWsscs/ssdiagreporterui

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.

b. Before starting the Sun StorEdge Configuration Service console, you must run the following command to specify the web browser to access online help.

/opt/SUNWsscs/sscsconsole/config_sscon

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:

/etc/init.d/ssagent enable start

d. To enable the Sun StorEdge Diagnostic Reporter to start automatically when the system boots, and to start it now, type:

/etc/init.d/ssdgrptd enable start

Downloading and Installing Firmware

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:

• Controller firmware 423A
• SAF-TE firmware 1180

To determine the current firmware versions for your array, see:

• To Determine Your Current Controller Firmware Version
• To Determine Your Current SAF-TE Firmware Version

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.

To determine your current controller firmware version, use one of the following methods:

• Access the controller firmware application through the serial port or through telnet. Select the “view system information” firmware menu option. The current firmware version is displayed as “Firmware Version.”
• Using Sun StorEdge Configuration Service, highlight any component of the desired Sun StorEdge 3310 SCSI array, click on the View menu and the View Controller command, and then check the FW Rev checkbox.
• Using the Sun StorEdge CLI, enter the show inquiry command.

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.

---

Downloading the VERITAS Volume Manager Array Support Libraries

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.

http://www.sun.com/software/download/products.html

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.

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.

---

Known Issues

• CR 6890196: Request to document "0" value for Maximum Drive Capacity in serial port menu. Logical drives can be created using either the firmware main menu or the CLI command line interface. Both interfaces enable you to specify a Maximum Drive Capacity if you want to use less than the full capacity of the physical drives in the logical drive. Otherwise, the default is to use the entire available capacity. However, due to a difference in the methods used by the two interfaces, a small size difference can exist between their default sizes. This can cause discrepancies when a logical drive created using one interface is mirrored or recreated using the other interface. This is true for all Sun StorageTek 3000 family RAID controllers since they share the same firmware and software interfaces.
  Workaround: When using the firmware to create a logical drive that uses the full capacity of the physical drives that comprise it, do not accept the default. Instead, specify a Maximum Drive Capacity of 0. This ensures that the resulting logical drive size will be identical with one created using the CLI and accepting the default drive size.

^{1 (TableFootnote) The LSI22320-R HBA is not available from Sun.}

^{2 (TableFootnote) The Adaptec HBA is not available from Sun.}

^{3 (TableFootnote) This HP HBA is officially tested and supported. Equivalent HP HBAs are also supported.}

^{4 (TableFootnote) This IBM AIX HBA is officially tested and supported. Equivalent AIX HBAs are also supported.}

^{5 (TableFootnote) No in this column = The HBA in the column heading is not supported on this platform.}

^{6 (TableFootnote) To enable support for either the Sun StorEdge 3310 SCSI RAID or JBOD arrays using the on-board SCSI port of the Sun Fire V440, see Modifications for Sun Fire V440 Systems. No on-board SCSI port is available on the V480, V880, 4800, 4810, 6800, and E10K servers.}

^{7 (TableFootnote) (X)2222A is supported. (X)4422A is not supported.}

---

Note - Note - To ensure cable and onboard HBA compatibility, review the HBA Sunswift manual for applicable restrictions.

---

^{8 (TableFootnote) To change the Ultra320 speed to the Ultra160 speed needed to operate with a 3310 SCSI JBOD array and the X9265A HBA, refer to the following procedure.}

Sun StorEdge 3310 SCSI Array Release Notes

819-7109-11

Copyright © 2009 Sun Microsystems, Inc. All rights reserved.