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.

An earlier major release updated RAID controller firmware to version 4.11, Sun StorEdge Configuration Service (SSCS) 2.0, and Sun StorEdge Command-Line Interface (CLI) 2.0. This release involved substantial changes from all previous releases and upgrading to it required an unusual and sometimes difficult set of procedures. To simplify these procedures somewhat, a script file and flowchart was included as part of the firmware package, as well as an unusually detailed README file detailing the steps involved.

If you install the current 4.13 firmware on controllers running version 3.2x firmware, the same procedures are involved, and the same information is contained in the firmware package. If you install the current 4.13 firmware on controllers running version 4.1x firmware, the upgrade is simple and the complex procedures are not required. The README file contained in the firmware package provides instructions for both circumstances.

See Important Feature Changes in 4.1x RAID Controller Firmware and 2.x Software for a description of the new features.

See Upgrading to Software Version 2.1 and Controller Firmware Version 4.13 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 provides a minor upgrade to RAID controller firmware 4.13, Sun StorEdge Configuration Service (SSCS) 2.1, and Sun StorEdge Command-Line Interface (CLI) 2.1. It incorporates fixes to bugs and other known issues.

New translated 2.0 software (in French, Japanese, Traditional Chinese and Simplified Chinese) is available on the Sun Download Center for Solaris systems. Translated documentation is available on the product documentation websites (see Release Documentation). In addition, previously translated 1.5 and 1.6 documentation is also available on the product documentation websites.

New CLI 2.1 Command

scan disk

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

TABLE 1 highlights the features that are implemented in all software and in the firmware unless otherwise indicated.

TABLE 1 Summary of Sun StorEdge 3000 Family 4.1x Firmware and 2.x Software Features
Feature	Description
Default IP address assigned by a DHCP server	By default, each chassis has an IP address 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.
Logical Drive Capacity	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.
Number of Logical Drives	You can configure up to 16 logical drives per configuration, and are limited to a maximum of 32 partitions per logical drive.
Configurable Parameters per Logical Drive	You can configure stripe size and write (cache) policy individually for each logical drive with a maximum LUN limit of 128 LUNs.
Optimization Mode and Stripe Size Change	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.
Media Scan	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. By default, media scans are run continuously on all active drives and local spares in all logical drives. 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 for every active drive.
SNMP Traps	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.
Network Protocol Access	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.
Telnet Inactivity Timeout Time	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.
Online Initialization and Online Expansion	If you enable the online initialization feature, you can use a logical drive while the logical drive is being initialized. Similarly, you can enable the online expansion feature and use a logical drive while it is being expanded with another drive. The completion of the initialization or the expansion, however, takes longer than if you had allowed the processes to complete without use of the logical drives.
Logical and Physical Drive Safeguards	There are safeguards against improperly combining physical drives of different types in logical drives, with accompanying explanatory error messages.
Fault-Management Safeguards	Automatically switch to write-through cache mode based on: Low battery level AC power loss Fan failure Power supply failure High temperature in CPU/Enclosure Failure of a redundant controller Single-controller configuration Automatic system shutdown based on critical environmental conditions
Ethernet and RS-232 Security	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 allows access to the firmware menu.
CLI Version Information	The sccli `about` command provides a sccli version 2.1.0 number with a "built" date and time such as 2005.05.18.20.08, which is year 2005, month 5, day 18, hour and minute 20:08. The build number 13 provides an additional identifier.
CLI Status Commands	The CLI `set led` and `show led-status` commands are supported on StorEdge 3320, Sun StorEdge 3510 FC, Sun StorEdge 3511 SATA RAID arrays, and JBODs connected to RAIDs.
SMART Feature Enabled by Default	The Self-Monitoring, Analysis and Reporting Technology (SMART) feature is enabled by default in the firmware, with the Detect and Clone+Replace option turned on.

Optimization Mode and Stripe Size Features

The optimization mode controls cache block size only. Stripe size can now be set individually for each logical drive.

With firmware version 4.1x, when you specify sequential or random cache optimization, the controller determines a default stripe size for newly-created logical drives. However, you can specify whatever stripe size you choose for each logical drive when you create it, enabling you to maximize performance by matching stripe size with your application requirements. Since different applications may use different logical drives, this functionality provides you with greatly increased flexibility.

For sequential optimization, the following rules apply:

Available stripe size choices 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.

The cache block size is 128 Kbyte.

For random optimization, the following rules apply:

Available stripe size choices 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.

The cache block size is 32 Kbyte.

With firmware version 4.1x, as with previous firmware versions, you specify a write-back or write-through cache write policy that applies to the entire RAID array. But with firmware version 4.1x, you can now specify a cache write policy for each individual logical drive.

The following table provides a summary of firmware differences:

TABLE 2 Summary of Optimization and Stripe Size Features
Feature	Current 4.13 controller firmware
Sequential or Random Cache Optimization Mode	Sets block size for cache in a chassis. Stripe size for each logical drive is user-selectable, but optimization mode determines default stripe size.
Changing the optimization mode	To change the optimization mode without deleting logical drives, use the Sun StorEdge CLI `set cache-parameters` command.
Stripe Size	Using the controller firmware, you can now specify an appropriate stripe size for each logical drive when you create it.
Changing the stripe size	To change the stripe size of an individual logical drive, delete the logical drive and create a new logical drive with the desired stripe size.
Cache Write Policy	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.

Release Documentation

These release notes supplement the documents shown in TABLE 3.

TABLE 3 Sun StorEdge 3310 SCSI Array Documentation
Title	Part Number
Sun StorEdge 3000 Family Installation, Operation, and Service Manual	816-7290
Sun StorEdge 3000 Family Best Practices Manual	816-7293
Sun StorEdge 3000 Family FRU Installation Guide	816-7326
Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays	817-3629
Sun StorEdge 3000 Family RAID Firmware 4.1x User's Guide	817-3711
Sun StorEdge 3000 Family 2.x Software Installation Guide	817-3764
Sun StorEdge 3000 Family Configuration Service 2.x User's Guide	817-3337
Sun StorEdge 3000 Family Diagnostic Reporter 2.x User's Guide	817-3338
Sun StorEdge 3000 Family CLI 2.x User's Guide	817-4951
Sun StorEdge 3000 Family Safety, Regulatory, and Compliance Manual	816-7930

You can download the documents listed in TABLE 3 table from either of the following locations:

http://www.sun.com/products-n-solutions/hardware/ docs/Network_Storage_Solutions/Workgroup/3310

http://docs.sun.com/app/docs/coll/3310SCSIarray

Supported Operating Systems and Software

The supported operating systems are:

Solaris 8, 9, and 10 operating systems, SPARC Platform Edition

Solaris 9 (9 04/04) and 10 operating systems, x86 Platform Edition

Red Hat Linux AS 2.1 and 3.0

Microsoft Windows 2000 Advanced Server and Windows 2003 Server operating systems

IBM AIX 5.1, 5.2, and 5.3 operating systems

HP-UX 11.0 and 11i operating systems

Novell Netware 5.1, 6.0, and 6.5

SUSE Linux Enterprise Server 9.0, (32-bit and 64-bit)

The supported software includes:

Sun StorEdge 3000 Family Configuration Service 2.x

Sun StorEdge 3000 Family Diagnostic Reporter 2.x

Sun StorEdge 3000 Family CLI 2.x

Sun Storage Automated Diagnostic Environment (StorADE) 2.4

Sun Storage Automated Diagnostic Environment 2.3 (with patch 116720-10)

Solstice DiskSuite 4.2.1 or greater (for the Solaris 8 operating system)

Solaris Volume Manager (for the Solaris 9 operating system and above)

VERITAS Volume Manager 3.5 and 4.0 ASL. See Downloading the VERITAS Volume Manager Array Support Libraries for a description of how to obtain the 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 1.2 or later for all platforms., IBM AIX and SUSE Linux can also use IBM JRE 1.2 or later.

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.

TABLE 4 Supported Host Adapters and Connections
Operating System	Host Adapter	Part Number
Solaris operating system	An on-board SCSI port attachment (on the host system)	N/A
Solaris operating system	Sun StorEdge PCI Dual Ultra3 SCSI host adapter	(X)6758A
Solaris operating system	Dual Ultra2 SCSI and dual FastEthernet PCI adapter	(X)2222A
Solaris operating system	Dual Ultra2 SCSI and dual Gigabit Ethernet PCI adapter	(X)4422A
Solaris operating system	SunSwift adapter (Sun FastEthernet 10/100BaseT F/W UltraSCSI SBus adapter 1.0)	(X)1018A
Solaris operating system	Ultra320 SCSI Dual Channel PCI-X adapter	SG-XPCI2SCSI-LM320
Solaris 9 x86 update 6 and Solaris 10 x86 operating system	Ultra320 SCSI Dual Channel PCI-X adapter (throttled down to 160 speed)	X9265A LSI2230-R ³
Red Hat AS 2.1 and 3.0	Ultra320 SCSI Dual Channel PCI-X adapter (throttled down to 160 speed)	X9265A LSI22320-R ³
Windows 2000/2003 and Linux operating systems	Ultra320 SCSI Dual Channel PCI-X adapter	X9265A LSI22320-R ³
Novell Netware 5.1, 6.0, and 6.5	Adaptec Dual Ultra320 SCSI PCI host adapter	Adaptec 39320A-R ⁴
HP-UX operating system	HP Ultra 160 SCSI Adapter for SCSI ^[1]	A6829A
IBM AIX operating system	IBM Dual channel PCI Ultra3 SCSI Adapter ^[2]	SYM53C1010

Caution - If you are using Solaris 8 or 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. (See 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.

TABLE 5 Supported Sun SPARC-Based Systems and Connection Methods
	(X)6758A Host Adapter ^[3]	On-Board SCSI Port ^[4]	(X)2222A and (X)4422A HBAs	(X)1018A SBus Adapter	SG-XPCI2SCSI-LM320
Ultra 60 workstation	Yes	Yes	Yes	No	Yes
Ultra 80 workstation	Yes	Yes	Yes	No	Yes
Sun Blade 150 workstation	No	No	Yes	No	No
Sun Blade 1000 workstation	Yes	Yes	Yes	No	Yes
Sun Blade 1500 workstation	Yes	No	Yes	No	Yes
Sun Blade 2000 workstation	Yes	Yes	Yes	No	Yes
Sun Blade 2500 workstation	Yes	Yes	Yes	No	Yes
Netra 20 server	Yes	Yes	Yes	No	Yes
Netra 120 server	Yes	Yes	Yes	No	Yes
Netra 1280 server	Yes	Yes	Yes	No	Yes
Netra t 1120 server	Yes	Yes	Yes	No	Yes
Netra t 1125 server	Yes	Yes	Yes	No	Yes
Netra t 1400 server	Yes	Yes	Yes	No	Yes
Netra t 1405 server	Yes	Yes	Yes	No	Yes
Sun Enterprise 220R server	Yes	Yes	Yes	No	Yes
Sun Enterprise 250 server	Yes	Yes	Yes	No	Yes
Sun Enterprise 420R server	Yes	Yes	Yes	No	Yes
Sun Enterprise 450 server	Yes	Yes	Yes	No	Yes
Sun Enterprise 3500 server	No	Yes	No	Yes	No
Sun Enterprise 4500 server	No	Yes	No	Yes	No
Sun Enterprise 5500 server	No	Yes	No	Yes	No
Sun Enterprise 6500 server	No	Yes	No	Yes	No
Sun Enterprise 10000 server	No	No	Yes/No^{^[5]}	Yes	No
Sun Fire 280R server	Yes	Yes	Yes	No	Yes
Sun Fire V120 server	Yes	Yes	Yes	No	Yes
Sun Fire V210 server	Yes	Yes	Yes	No	Yes
Sun Fire V240 server	Yes	Yes	Yes	No	Yes
Sun Fire V250 server	Yes	Yes	Yes	No	Yes
Sun Fire V440 server	Yes	Yes	Yes	No	Yes
Sun Fire V480 server	Yes	No	Yes	No	Yes
Sun Fire V490 server	Yes	No	Yes	No	Yes
Sun Fire V880 server	Yes	No	Yes	No	Yes
Sun Fire V890 server	Yes	No	Yes	No	Yes
Sun Fire V1280 server	Yes	Yes	Yes	No	Yes
Sun Fire 2900 server	Yes	Yes	Yes	No	Yes
Sun Fire 4800 server	Yes	No	Yes	No	Yes
Sun Fire 4810 server	Yes	No	Yes	No	Yes
Sun Fire 4900 server	Yes	No	Yes	No	Yes
Sun Fire 6800 server	Yes	No	Yes	No	Yes
Sun Fire 6900 server	Yes	No	Yes	No	Yes
Sun Fire 12K server	Yes	No	Yes	No	Yes
Sun Fire 15K server	Yes	No	Yes	No	Yes
Sun Fire E20K server	Yes	No	Yes	No	Yes
Sun Fire E25K server	Yes	No	Yes	No	Yes

TABLE 6 Supported Solaris 9 and Solaris 10 Sun x86-Based Systems and Connection Methods
Server	On-board	X9265A LSI22320-R
Sun Fire V60x server ^[6]	Yes	No
Sun Fire V65x server	Yes	No
Sun Fire V20z server	No	Yes
Sun Fire V40z server	No	Yes

To Configure the Sun Fire V60x, Sun Fire V65x, Sun Fire V20Z, and Sun Fire V40z for Ultra160 Speed

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. This is done 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. See the Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays for installation instructions.

TABLE 7 Supported Cabinets and Associated Rackmount Kits
Cabinet Name	Cabinet Part Number(s)	Required Kit(s)	Required Kit Part Number	Maximum Number of Arrays Supported per Cabinet
Sun StorEdge 72-inch Expansion Cabinet	SG-(X)ARY030A	Rackmount Kit	(X)TA-3000-2URK-19U	14
Sun Fire Cabinet	SF-(X)CAB, SFE-(X)CAB	Rackmount Kit	(X)TA-3000-2URK-19U	5
Sun Rack 900 Cabinet	SR9-(X)KM038A-IP	Rackmount Kit	(X)TA-3000-2URK-19U	18
Sun Fire 6800 System	F6800-1	Rackmount Kit	(X)TA-3000-2URK-19U	3
Sun Fire E6900 System	E6900-BASE	Rackmount Kit	(X)TA-3000-2URK-19U	2
Standard EIA Cabinets	Not Applicable	Rackmount Kit	(X)TA-3000-2URK-19U	Varies
Telco flushmount racks	Not Applicable	Rackmount Kit	(X)TA-3310-RK-19F	Varies
Telco center-of-gravity racks	Not Applicable	Rackmount Kit	(X)TA-3000-2URK-19C	Varies

Note - For more information about using Sun StorEdge arrays with the Sun Rack 900 cabinet, refer to the Sun Rack 900 Qualified Products web page at: http://www.sun.com/servers/rack/approved.html

Supported Disk Drives

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

TABLE 8 Supported Disk Drives
Description	Part Number
36 GB 10,000 RPM	(X)TA-3310-36GB-10K
36 GB 15,000 RPM	(X)TA-3310-36GB-15K
73 GB 10,000 RPM	(X)TA-3310-73GB-10K
73 GB 15,000 RPM	(X)TA-3310-73GB-15K
146 GB 10,000 RPM	(X)TA-3310-146GB-10K
146 GB 15,000 RPM	(X)TA-3310-146GB-15K
300 GB 10,000 RPM	(X)TA-3310-300GB-10K

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. Do not use the Sun StorEdge Configuration Service or Sun StorEdge CLI utility to download disk drive firmware.

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

TABLE 9 Supported Cables
Cable Type and Length	Marketing Part Number	Manufacturing Part Number
VHDCI/VHDCI 0.8 m	(X)1136A	595-5645-01
VHDCI/VHDCI 1.2 m	(X)1137A	595-5647-01
VHDCI/VHDCI 2 m	(X)1138A	595-5646-01
VHDCI/VHDCI 4 m	(X)3830B	595-6349-01
VHDCI/VHDCI 10 m	(X)3831B	595-6350-01
HD-68/VHDCI, 0.8 m	(X)1132A	595-5660-01
HD-68/VHDCI, 1.2 m	(X)1135A	595-7460-01
HD-68/VHDCI, 2 m	(X)3832A	595-4693-01
HD-68/VHDCI, 4 m	(X)3830A	595-4694-01
HD-68/VHDCI, 10 m	(X)3831A	595-4695-01

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.

Software Support for JBODs

Sun StorEdge Configuration Software supports Sun StorEdge 3310 SCSI JBOD arrays (arrays without controllers that are directly attached to servers). However, since Sun StorEdge 3310 SCSI JBOD arrays do not have a RAID controller or RAID controller firmware to manage the disks, this software support is necessarily limited. Monitoring functionality that does not require a RAID controller or RAID controller firmware works properly.

The Sun StorEdge CLI supports Sun StorEdge 3310 SCSI JBOD arrays. However, since Sun StorEdge 3310 SCSI JBOD arrays do not have a RAID controller or RAID controller firmware to manage the disks, this CLI support is limited to the following sccli commands:

about

download safte-firmware

exit

help

quit

select

set led

show access-mode

show configuration

show enclosure-status

show frus

show inquiry-data

show led (or show led-status)

show safte-devices

version

To obtain information about each command, run the help command or on Unix systems, access the man page.

Caution - Be sure to uninstall any earlier versions of software before you install the new version. Two software versions on a server will cause invalid operation or results due to changes in the communications protocols.

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 Red Hat has a kernel panic.

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 /vmlinuz-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

Solaris 8: 115275-03

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. An online copy of the installation guide is available from the web site:

http://www.sun.com/products-n-solutions/hardware/docs/ Network_Storage_Solutions/Adapters/index.html

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:

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

and search for "Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter" in the "Search SunSolve" search area.

Required Patches

The Solaris 8, 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-11, containing firmware version 4.13 and SAF-TE firmware version 1170, 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 8 Operating System: 112697-04

Solaris 9 Operating System: 112706-03

Solaris 10 Operating System: 119555-02

Installing Required Solaris Patches

Make sure the Solaris Recommended Patch Cluster is installed on a Solaris host before connecting the host to the array.

To Download and Install the Solaris Recommended Patch Cluster

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 Resources, click Patches and Updates.

4. Under Downloads find Recommended and Security Patches and click Recommended Patch Clusters.

5. Find your version of Solaris 8, 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 Solaris 8, 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.1 and Controller Firmware Version 4.13

The upgrade process includes:

Downloading and Installing Software Applications

Downloading and Installing Firmware

Note - If you are using 3.25W controller firmware and do not want to upgrade to version 4.13, you can still download 3.25W firmware patch 113722-09 for the Sun StorEdge 3310 SCSI array, from sunsolve.sun.com.

Downloading and Installing Software Applications

Before installing the new firmware, you must upgrade the Sun StorEdge Configuration Service agent, Sun StorEdge Configuration Service console, Sun StorEdge Diagnostic Reporter, and Sun StorEdge Command-Line Interface (CLI) utility.

Because the communication protocol changes from version to version, you must install the SUNWsscs package on all systems that manage the storage when upgrading.

Caution - 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 Updated Software

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 Sun StorEdge 3000 Family Storage Products - Related Software link, and click the Download button.

A Sun Download Center page is displayed.

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

4. 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 the Continue button.

5. On the software download page, click the link for your array and operating system.

6. In the dialog box that is displayed, specify a destination directory and save the file.

To Install or Upgrade the Software

To install or upgrade the software on the Solaris operating system to include the latest bug fixes and new features, perform the following steps.

Note - For installation or upgrading instructions for other operating systems, refer to the Sun StorEdge 3000 Family 2.x Software Installation Guide.

Note - Make sure that Java runtime environment (JRE) software is installed on the computer or workstation on which you are installing Sun StorEdge Configuration Service. The earliest release of Java runtime environment software that is compatible with Sun StorEdge Configuration Service on a Solaris 2.6 host is 1.3.1. The earliest release of Java runtime environment software that is compatible with Sun StorEdge Configuration Service on a Solaris 8, Solaris 9, or Solaris 10 host is 1.2.

1. Login 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.

TABLE 10 Software Filenames
Application	Filename
Configuration Service Agent	`SUNWscsd`
Configuration Service Console	`SUNWscsu`
Diagnostic Reporter Agent	`SUNWscsa`
Diagnostic Reporter Config Tool	`SUNWscui`
CLI	`SUNWsccli`

3. To install the version 2.1 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.

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.

/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

6. Edit /kernel/drv/sd.conf if LUNs other than LUN 0 are mapped from the array to the host and an onboard HBA for Sun hosts or third-party HBAs are used for connecting the device.

Add lines for LUNs as appropriate for your configuration. LUNs can be numbered from 0-31. Generally, do not add more LUN definitions than you actually plan to have, since doing so increases the time needed to scan each SCSI bus. For information about modifying the sd.conf file, refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for your SCSI array.

7. If the sd.conf file has been edited, perform a reconfiguration reboot.

If the sd.conf file has not been edited, you do not have to perform a reconfiguration reboot and the agent starts automatically.

Downloading and Installing Firmware

Firmware patch ID # 113722-11 is available from SunSolve to upgrade controller firmware for Sun StorEdge 3310 SCSI arrays running firmware versions earlier than 4.13 and to upgrade SAF-TE firmware earlier than 1170.

Firmware patch ID # 113722-11 provides the following firmware:

Controller firmware 413B

SAF-TE firmware 1170

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 the README for the firmware upgrade prior to upgrading your array. Downgrading back to the 3.xx controller firmware is recommended only for a FRU replacement module. All other downgrades risk loss of all data.

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. Do not use the Sun StorEdge CLI or Sun StorEdge Configuration Service to download disk drive firmware.

To Determine Your Current Controller Firmware Version

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 and tip. Select the "view system information" firmware menu option. The current firmware version is displayed as "Firmware Version."

In the Sun StorEdge Configuration Service program, 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

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.

To Download the Firmware Patch

1. Go to http://sunsolve.sun.com

2. Under Support Resources, click Patches and Updates.

3. Use Patch Finder to locate patch ID 113722-11 by entering the patch ID into the search field and clicking the Find Patch button.

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 is displayed, 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 and 4.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 3.5 or 4.0 software to enable the software to recognize the Sun StorEdge 3310 SCSI array. Follow the procedure to download the ASL for the Sun StorEdge 3310 SCSI array from the Sun Download Center.

To Download the ASL

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/allproducts.html

3. Under the V heading, click on VERITAS Volume Manager Array 3.5/4.0 Libraries (ASL).

4. Choose the link that is appropriate for your platform.

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

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

7. Type your Username and Password in the left column, and click Login.

8. Download the compressed ZIP file that contains the ASL package for the 3310 SCSI array.

9. Use the unzip command to expand the zip file.

Known Issues

Bug 6263096: SE3310: Getting scsi errors from SE3310 when used as boot device. When more than one SE3310 LUN is configured on the boot path under Solaris 10 x86 Platform Edition, the system will get SCSI resets or will hang.
Workaround: Configure only a single LUN on the boot path.

Bug 6273060: Diagnostic Reporter Event email does not report the correct event time stamp. The emailed events carry the time stamp of the email, rather than the actual time when the event occurred on the array. This can be confusing to the customer and cause unnecessary hardware replacements.

Bug 6281875: No amber LEDs seen on failing disk in 3310. In some split-bus scenarios, when the SAF-TE device isn't on the same bus as the failing drive, the LED will not go amber but the event log will show a failed disk entry. When the 3310 is configured for split-bus mode, disks reside on channel 0 and channel 2 while SAF-TE is only on channel 0. The SAF-TE specification does not have any provisions to provide status of disk drives on a remote channel. Therefore the controller will always show a "not present" status for disks on channel 2 when in split-bus mode.

Bug 6299214: Fujitsu MAU3073NC drives getting timeout and then failed by 3.25W firmware on 3310. After the drive is failed, timeouts occur for the same drive and bus resets are issued, followed eventually by a gross error on the SCSI bus.

Bug 6303025: pkgadd -R of package SUNWsscs fails. Pkgadd cannot be used with a live upgrade. When sccli is installed on a host and pkgadd attempts to remove previous packages, the removal fails because the query is made to the live version of sccli. pkginfo -q $PKG_LIST should be pkginfo -R $PKG_INSTALL_ROOT -q $PKG_LIST.

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

^{2 (TableFootnote) This IBM AIX HBA is officially tested and supported. Equivalent AIX HBAs are also supported.}3 The LSI22320-R HBA is not available from Sun. 4 The Adaptec HBA is not available from Sun.

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

^{4 (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.}

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

^{6 (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.}