Sun StorEdge 3310 SCSI Array Release Notes
|
![Table Of Contents Table Of Contents](shared/toc01.gif) ![Previous Chapter Previous Chapter](shared/prev01.gif) ![NoNext NoNext](shared/next02.gif) ![NoIndex NoIndex](shared/index02.gif) |
Sun StorEdge 3310 SCSI Array
Release Notes
|
Read these release notes before attempting to install or use the Sun StorEdge
3310 SCSI array.
New Features in This Release
The following features, supported systems, and products are now available in this release:
- Support of the Sun StorEdge 3310 RAID or JBOD arrays when attached to the on-board SCSI port of the Sun Fire V440 server. For details about enabling a Sun StorEdge 3310 RAID or JBOD array to operate with a Sun Fire V440 server, see Modifications for Sun Fire V440 Systems.
- The Sun StorEdge Diagnostic Automated Diagnostic Environment 2.3 utility is currently being updated to support the Sun StorEdge 3310 SCSI array. When the update is completed, the SUNWstade 116720-06 patch will be required for RAID arrays, and the SUNWstade 116720-07 patch will be required for the JBOD arrays.
- The Sun StorEdge CLI 1.5 software has been enhanced to include many new options and commands. Refer to the Sun StorEdge 3000 Family CLI 1.5 User's Guide for detailed information.
- Controller firmware patch 113722-05, containing firmware version 3.25S and
SAF-TE firmware version 1159, is now available. See Installing Controller Firmware Patches for more information.
Released Documentation
These release notes supplement the documents shown in the following table.
TABLE 1 Sun StorEdge 3310 SCSI Array Documentation
Title
|
Part Number
|
Sun StorEdge 3000 Family Installation, Operation, and Service Manual for the Sun StorEdge 3310 FC Array
|
816-7290
|
Sun StorEdge 3000 Family Best Practices Manual for the Sun StorEdge 3310 SCSI Array
|
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 3.25 and 3.27 User's Guide
|
817-3711
|
Sun StorEdge 3000 Family 1.5 Software Installation Manual
|
817-3764
|
Sun StorEdge 3000 Family Configuration Service 1.5 User's Guide
|
817-3337
|
Sun StorEdge 3000 Family Diagnostic Reporter 1.5 User's Guide
|
817-3338
|
Sun StorEdge 3000 Family CLI 1.5 User's Guide
|
817-4951
|
Sun StorEdge 3000 Family Safety, Regulatory, and Compliance Manual
|
816-7930
|
You can download the documents listed in the preceding table from either of the following locations:
http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/Workgroup/3310
or
http://docs.sun.com/db/coll/3310SCSIarray
Translated Manuals and Software
While the latest documentation and software are being translated, you can obtain the earlier translated versions of software and documentation at the following locations.
- For translated documentation in French, Japanese, Simplified Chinese, Traditional Chinese, and Korean, go to:
http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/EOL_Products/index.html
- For translated version 1.3 software and for the English 1.3 software which must be installed before the translated files are installed, go to the following location and click on the download button:
http://wwws.sun.com/software/download/products/3edcd6a5.html
Note - Sun StorEdge 3000 Family CLI 1.5 is required for download procedures with the latest FC 3.27R firmware and can be used on servers which also contain version 1.3 software.
|
Supported Operating Systems and Software
The supported operating systems are:
- Solaris 8 and 9 operating systems
- Solaris 9 OS x86 Platform Edition (9 04/04)
- Red Hat Linux AS 2.1 and 3.0
- Microsoft Windows NT Server 4.0, Windows 2000 Advanced Server, and Windows 2003 Server operating systems
- IBM AIX 4.3.3 and 5.1L operating systems
- HP-UX 11.0 and 11i operating systems
- Novell Netware 5.1 and 6.5
The supported software includes:
- Sun StorEdge 3000 Family Configuration Service 1.5
- Sun StorEdge 3000 Family Diagnostic Reporter 1.5
- Sun StorEdge 3000 Family CLI 1.5
- Sun Cluster
3.0 and 3.1 software
- Sun StorEdge Diagnostic Automated Diagnostic Environment 2.3 (with appropriate patch)
The Sun StorEdge Diagnostic Automated Diagnostic Environment 2.3 utility is currently being updated to support the Sun StorEdge 3310 SCSI array. When the update is completed, the SUNWstade 116720-06 patch will be required for RAID arrays, and the SUNWstade 116720-07 patch will be required for the JBOD arrays.
- 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.2
(The instructions in the "Enabling VERITAS DMP" section of the Sun StorEdge 3000 Family Installation, Operation, and Service Manual apply to version 3.2.)
- VERITAS Volume Manager 3.5 and 4.0 ASL. See Downloading the VERITAS Volume Manager Array Support Libraries for 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)
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
Refer to TABLE 2 for the list of supported host adapters and connections.
TABLE 2 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 x86 9 update 6
|
Ultra320 SCSI Dual Channel PCI-X adapter (throttled down to 160 speed)
|
X9265A
LSI2230-R 3
|
Red Hat AS 2.1 and 3.0
|
Ultra320 SCSI Dual Channel PCI-X adapter (throttled down to 160 speed)
|
X9265A
LSI22320-R 3
|
Windows 2000/2003/NT and Linux operating systems
|
Ultra320 SCSI Dual Channel PCI-X adapter
|
X9265A
LSI22320-R 3
|
Novell Netware 5.1 and 6.5
|
Adaptec Dual Ultra320 SCSI PCI host adapter
|
Adaptec 39320A-R 4
|
HP-UX operating system
|
HP Ultra 160 SCSI Adapter for SCSI
|
A6829A
|
IBM AIX operating system
|
IBM Dual channel PCI Ultra3 SCSI Adapter
|
SYM53C1010
|
|
Caution - If you are using the Sun StorEdge PCI Dual Ultra3 SCSI host adapter (X)6758A, make sure to 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
Tables 3 and 4 show the connection methods supported for each supported Sun server.
TABLE 3 Supported Sun SPARC-Based Systems and Connection Methods
|
(X)6758A Host Adapter
|
On-Board
SCSI Port
|
(X)2222A and
(X)4422A HBAs
|
(X)1018A
SBus Adapter
|
Ultra 60 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Ultra 80 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Sun Blade 150 workstation
|
No
|
No
|
Yes
|
No
|
Sun Blade 1000 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Sun Blade 1500 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Sun Blade 2000 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Sun Blade 2500 workstation
|
Yes
|
Yes
|
Yes
|
No
|
Netra 20 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra 120 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra 1280 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra t 1120 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra t 1125 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra t 1400 server
|
Yes
|
Yes
|
Yes
|
No
|
Netra t 1405 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Enterprise 220R server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Enterprise 250 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Enterprise 420R server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Enterprise 450 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Enterprise 3500 server
|
No
|
Yes
|
No
|
Yes
|
Sun Enterprise 4500 server
|
No
|
Yes
|
No
|
Yes
|
Sun Enterprise 5500 server
|
No
|
Yes
|
No
|
Yes
|
Sun Enterprise 6500 server
|
No
|
Yes
|
No
|
Yes
|
Sun Enterprise 10000 server
|
No
|
Yes
|
No
|
Yes
|
Sun Fire 280R server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V120 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V210 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V240 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V250 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V440 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire V480 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire V880 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire V1280 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire 2900 server
|
Yes
|
Yes
|
Yes
|
No
|
Sun Fire 4800 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 4810 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 4900 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 6800 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 6900 server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 12K server 3
|
Yes
|
No
|
Yes
|
No
|
Sun Fire 15K serve3 3
|
Yes
|
No
|
Yes
|
No
|
Sun Fire E20K server
|
Yes
|
No
|
Yes
|
No
|
Sun Fire E25K server
|
Yes
|
No
|
Yes
|
No
|
TABLE 4 Supported Sun x86-Based Systems and Connection Methods
Server
|
On-board
|
X9265A
LSI22320-R
|
Sun Fire V60x server
|
Yes
|
Yes
|
Sun Fire V65x server
|
Yes
|
Yes
|
Sun Fire V20z server
|
No
|
Yes
|
Supported Cabinets
The following table 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 instruction.
TABLE 5 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-3310-RK-19C
|
Varies
|
Supported Disk Drives
The following table gives descriptions and part numbers for the disk drives supported with the Sun StorEdge 3310 SCSI Array.
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
|
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.
|
Supported Cables
The following table lists the supported SCSI cables. Cables may be ordered using the marketing part numbers in TABLE 1.
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.
|
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 Service software supports Sun StorEdge 3310 SCSI JBOD arrays (arrays without controllers which 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 configuration
- show enclosure-status
- show led (or "show led-status")
- show frus
- show inquiry-data
- show safte-devices
- version
To obtain information on each command, run the help command or access the man page on Unix systems.
|
Caution - Be sure to uninstall the old version 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 V60x, 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 a Sun Fire VXx server, 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 VXx 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 V60x, V65x Systems Running Red Hat AS 2.1 or 3.0
Adding SCSI disks to a Sun Fire V6xx 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, etc. After reboot, the boot partition is now /dev/sdb3, and Redhat 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, hit 'e' at the grub kernel selection screen.
2. Go to line the which points to the kernel and hit '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' etc.
4. Hit the Escape key to finish editing, then hit '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 RAID Array, the following patches or greater are required to enable support:
Sun StorEdge 3310 RAID: 113722-04
Solaris 8: 115275-03
Solaris 9: 115663-03
- When a Sun StorEdge 3310 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, 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, you can go to:
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 or Solaris 9 Recommended Patch Cluster is required to use Sun StorEdge Configuration Service and Diagnostic Reporter software. See To Download and Install the Solaris Recommended Patch Cluster for more information.
- Controller firmware patch 113722-05, containing firmware version 3.25S and SAF-TE firmware version 1159, is required if you are running an earlier firmware version. See Installing Controller Firmware Patches for information about how to verify which firmware version is on your array and how to download the 3.25S version.
If a Sun StorEdge PCI Dual Ultra3 SCSI Host Adapter, X6758A, is used to connect the Sun StorEdge 3310 array, the qus driver must also be updated. The updated qus driver is available in the following patches:
- Solaris 8 Operating Environment: 112697-04
- Solaris 9 Operating Environment: 112706-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.
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 "SunSolve Patch Contents," click "Patch Portal."
4. Under Downloads, click Recommended Patch Clusters.
5. Find either Solaris 8 or Solaris 9 in the OS column of the Recommended Solaris Patch Clusters list, click Readme 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 or Solaris 9 in the Recommended Solaris Patch Clusters list, click either Download HTTP or Download FTP, and then click Go.
9. In the File Download dialog box, click Save.
10. In the Save As dialog box, type a destination directory for the patch cluster, and then click OK.
11. Follow the procedure in the INSTALLATION INSTRUCTIONS section in the Readme file to install the patches.
Installing Controller Firmware Patches
Firmware patch ID # 113722-05 is available to upgrade controller firmware for Sun StorEdge 3310 SCSI arrays running firmware versions lower than 3.25S and to upgrade SAF-TE firmware lower than 1159.
Carefully review the following criteria before you upgrade the controller firmware:
- You must install and use Sun StorEdge CLI 1.5 to download SAF-TE version 1159.
- If you are already running firmware version 3.25S or later and SAF-TE version 1159 or later, you should not download and install this patch.
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 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 sccli, enter the show inquiry command.
To Download and Install the Firmware Patch
|
1. Go to http://sunsolve.Sun.COM
2. Click on Patch Portal.
3. Use Patch Finder to locate patch ID 113722-05 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 HTTPS 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 and Installing Updated Sun StorEdge 3000 Family Software
Sun StorEdge 3000 Family software version 1.5 is now available on the Sun Download Center.
To Download and Install the Updated Software
|
1. Go to: http://www.sun.com/software/download/sys_admin.html
2. Under Storage Management click the Sun StorEdge 3310 FC Array Related Software link.
You are taken to a Sun Download Center page.
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 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.
7. Follow the software installation instructions in the Sun StorEdge 3000 Family 1.5 Software Installation Guide.
Downloading the VERITAS Volume Manager Array Support Libraries
This section explains 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 Software Library (ASL) that must be installed on the same host system as the Volume Manager 3.5 and 4.0 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 Sun's 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 Sun's Download Center.
http://www.sun.com/software/download/allproducts.html
3. Under the V heading, click on VERITAS Volume Manager Array Support Library (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. 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.
8. Download the compressed ZIP file that contains the ASL package for the 3310 SCSI array and the related VERITAS installation guide.
The document title is VERITAS Volume Manager Array Support Library Installation Guide for the Sun StorEdge 3310 SCSI array.
9. Use the unzip command to expand the zip file.
10. Use acroread to read and print the manual, and follow the installation instructions it contains.
Documentation CorrectionsDriver .CONF File Example Corrected
In the installation manual for the Sun StorEdge 3310 SCSI array, please note the syntax correction in the example text for Solaris qus.conf and glm.conf files where the first line needs more spaces between Sun and StorEdge, and the second line should end in a ";" (not a ":"), found on page F-6:
1. Edit the/kernel/drv/qus.conf or/kernel/drv/glm.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 below.
|
An example of text to add to /kernel/drv/qus.conf or /kernel/drv/glm.conf
device-type-scsi-options-list = "SUN StorEdge 3310",
"SE3310-scsi-options"; (correct syntax shown)
SE3310-scsi-options = 0x43ff8;
|
Allow five blank spaces between "Sun" and "StorEdge" on the first line.
Drive Capacity Statement Corrected
In the Sun StorEdge 3000 Family RAID Firmware 3.25 and 3.27 User's Guide, the note in Chapter 8 under "Preparing for Logical Drives Larger Than 253 Gbytes on Solaris Systems" has been corrected. The note in the manual text says:
Note - Earlier versions of the Solaris operating environment do not support drive capacities larger than 1 terabyte.
|
The corrected text for that note is:
Note - Refer to your operating environment documentation for limitations on device sizes.
|
Known Issues
- Bug 4990478: SSCS shows 2 SAF-TE's even after removing the SES devices and running devfsadm. Sun StorEdge Configuration Service shows 2 SAF-TE devices after removing the SES devices and running devfsadm. After downloading the SAF-TE 1.5, address IDs are not showing correctly in Sun StorEdge Configuration Service. The probe operation changed the SES device ID. The SSCS agent is not able to remove the duplicate SES in this case. Restart the SSCS agent to remove the duplicate SES icon from the SSCS console.
- Bug 5001923: Downloading SAF-TE fw on the 1U with CLI 1.5 on windows os fails. On Microsoft Windows operating systems, use Sun StorEdge Configuration Service to download SAF-TE firmware rather then Sun StorEdge CLI. Using the CLI results in an unsuccessful download.
- Bug 4999185: ssmon dumps application core, analysis of core points to bad argument in memcpy.
- Bug 4881122: Cached blocks from a deleted logical drive are returned on READ. After a logical drive is deleted and a new logical drive is created with the same index (for example, "P1"), the controller might return blocks from the deleted logical drive to satisfy host READ requests if data has not been written to those block addresses in the new logical drive.
- Bug 4881132: Disk status is incorrect when rebuilding after RAID 1 multiple drive failures. After failing two disks in a four-disk RAID 1 logical drive, the status of the two failed disks is shown as FAILED, and the logical drive is shown as DRV FAILED. After rebuilding one of the failed disks, the status of the logical drive is changed to GOOD, even though one of its constituent disks has a status of FAILED. Because the logical drive has a status of GOOD, it is impossible to rebuild the second disk that failed.
- Bug 4988102: Port scanning/security software causes the SE3310 to hang. Port scanning and other security software causes controller failovers. Within seconds (under 10 seconds), after the following command is issued from a host on a different subnet, the controller and out-of-band tools (telnet, serial, and so forth), fails: nmap -sS -p 1-32768 -v minnow-disk1. Though sccli (in-band) continues to work, the only way to establish a telnet session is to reset the controller.
- Bug 4986468: Giving up messages on SE3310 RAID array and LUNs. After VxVM 3.5 is installed, the host starts reporting a "giving up" message for each RAID LUN during the vxinstall process and for each host reboot.
- Bug 4937092: The SCCLI/GUI does'nt allow us to set scsi-io-timeout > 10. The recommended setting for SCSI I/O timeout is 15, but the maximum setting allowed by Sun StorEdge Configuration Service and the CLI is 10. The firmware application does support timeout values greater than 10 seconds; therefore, use tip or telnet to access the menu interface and assign the desired value.
- Bug 4969758: SE3310 uses wrong MAC address for ICMP echo reply under some circumstances. For an ICMP echo reply, the first MAC address known to a specific IP address is used, regardless of an ARP being sent by the system that owns the MAC address. A controller reset or power cycle will flush the cached ARP information.
- Bug 4907020: Request Sense couldn't get sense data on SE3310 when VEA rescan performed. Installing VxVM 4.0 on an E10K domain and performing a rescan results in warning error messages on the Solaris console for each LUN on the storage array.
- Bug 4997565: Disk drives fail during bad-block reallocation. During bad block reassignment, the disk drive is failed. This is partially due to bad blocks, write-faults, and other hardware issues.
- Bug 4972674: inability to rebuild RAID drive if online drive has bad blocks. If a RAID 0+1 disk drive has bad blocks at 3 LBAs, when you try to rebuild through the UI, the rebuild starts but fails the rebuild after the first bad block. If you try the rebuild again, it asks if it should "Continue Rebuilding on Media Error?" If you respond "Yes," the rebuild completes, but all the bad blocks are silently overwritten and no errors will occur on subsequent reads of the previously bad blocks. Incorrect data is returned instead. After the rebuild completes, the controller should retain the fact that some of the blocks contain bad data and return an error on the subsequent reads. When a drive fails and it's mirror has a bad block, there is no good way to rebuild the failed drive.
- Bug 4990965: SE3310 controller reset itself while there is scsi transport failures. The Sun StorEdge 3310 SCSI array controller might reset itself if there are scsi transport failures. This leads to a loss of the connection between the server and the array. Reboot the server to reconnect with the array, and if that fails unmount and remount.
- Bug 4967518: Firmware doesn't track drive failure and the drive can scan back ok. The controller does not keep track of a failed drive. There is no update in the meta-data area and there is no test to determine this reassignment failure if a failed drive is scanned back into the system. Because of this, a failed drive continues to be scanned after it fails. To prevent confusion, always replace a drive that has failed due to a "reassignment failure."
- Bug 4994282: SE3310 cannot finish rebuild process completely and stop status at 99%. When a drive fails, the rebuilding process begins automatically. However, this process might not complete, and its status might remain "Rebuilding" at 99%.
- Bug 4991302: Investigate possible high rate of battery failures on se3310. A higher than normal rate of defective batteries have been encountered, particularly batteries with date codes of 0201 and 0301. If you encounter a group of defective batteries, continue to replace the battery until you find a good one.
- Bug 4976389: Download of SAF-TE fw via SSCS interface says it succeeded even though it didn't. When you update SAF-TE firmware using Sun StorEdge Configuration Service or sccli, the firmware does not display the new version until you reset controller.
- Bug 4994740: standard configuration cabling in a single bus SCSI JBOD. When configuring a Sun StorEdge 3310 SCSI Array and Expansion Unit in a single bus configuration, connect the SCSI cables as shown in the instructions and examples shown in Chapter 4 of the Sun StorEdge 3310 SCSI Array Installation, Operation and Service Manual.
- Bug 4948848: (X)2222A and (X)4422a are not able to see SE3310 RAID LUN numbers in range [8-31]. The (X)2222A firmware is designed to not probe device LUN numbers greater than 7 because some older SCSI devices behave badly when probed for those higher LUN numbers. The LUN numbers over 7 are available with the OS when the /kernel/drv/glm.conf and sd.conf files are modified as described in bug 4844899.
- Bug 4947971: probe-scsi-all on (X)2222A doesn't see target ID F. The probe-scsi-all command has a problem showing device 'f', but the device becomes available when the Solaris system is rebooted.
- Bug 4889967: Time Stamp reported for an event log entry is not constant, it changes over time. The time stamps on the event log entries are not constant when viewed from either the serial port firmware menu or via the sccli utility. When viewed through the serial port, the time stamps drift forward. When viewed through the sccli utility, the time stamps drive backward.
- Bug 4903457: Deassert Reset on Failed Controller (reinit failed ctrlr) loses access to disks. Reinitializing a failed controller (Deassert Reset) and then issuing a sccli from the host caused lost access to the data/disks. All LEDs began blinking and host reported SCSI bus reset messages.
- Bug 4923583: sccli caused panic after upgraded to 325S thru LSI1030 scsi port. Upgrading controller firmware can cause a host panic when connected to the onboard SCSI port of a Sun Fire V440 system. This panic occurs if the first command to the upgraded RAID array after a reset is either a CLI INQUIRY or a REQUEST SENSE command which causes a parity error. The panic is due to the Sun Fire V440 system mpt driver getting a parity error command from the HBA that it does not understand. The parity error is covered in bug 4722610.
- Bug 4722610: Parity Error and Target synch. rate reduced after upgrading FW. A parity error is displayed at the console of the agent server right after downloading 3.25L firmware and then rescanning the device using the SSCS program. This "Parity Error" message only occurs at the first Rescan right after successfully downloading 3.25L firmware. The target synch rate is reduced when using the CLI or when performing the first Rescan with SSCS right after upgrading the controller firmware. Non-Solaris drivers automatically adjust and correct the target sync rate to the higher speed available. To correct the synch rate with Solaris drivers, you must reboot the host system.
- Bug 4702532: Write cache not automatically disabled when battery is offline. Write cache is not automatically disabled when battery is offline due to battery failure or a disconnected battery. The current design allows the user to enable or disable the write-back cache capabilities of the RAID controller. To ensure data integrity, you may choose to disable Write Back cache option and switch to the Write-through cache option. The risk of data loss is remote.
- Bug 4714227: Under heavy load, the character interface fails to respond correctly. While running heavy I/O to several LUNs on different logical drives and scrolling through a menu that is long, such as a long, multiple LUN mapping menu, occasionally the menu will "escape" back one or two menus. This problem only occurs under heavy I/O and occasionally when accessing the unit using telnet over long distances.
- Bug 4802207: SCSI Bus Reset and daemon.error under heavy load test for 3310. The following type of message are output under heavy load test.
- Target Timed-out
- SCSI Bus Reset
- Select Timeout
Under certain heavy I/O conditions, these error messages are reported by the controller with a frequency on the order of once every 24 hours, due to an internal SCSI command time-out resulting from a combination of events. This is a firmware time-out issue and does not indicate a hardware problem. These informational messages do not affect data integrity or performance. No user intervention is required. The most important factor is extremely heavy I/O while the SSCS daemon is running. This can cause added I/O command queue backup because SSCS is busy obtaining SAF-TE and RAID controller information and not handling regular I/O commands.
- Bug 4743721: SSCS: no method for identifying disk drives. The Sun StorEdge Configuration Service program currently cannot identify disk drive status by flashing disk drive LEDs on the array. To perform this operation, you can use the firmware application and select "view and edit scsi drives" command. Then select the desired disk drive, press Return, and select the "Identifying scsi drive" command which offers three modes for flashing the drive LEDs).
Fixed Software Bugs
TABLE 6 Fixed Bugs in Software Version 1.5
Bug ID
|
Synopsis
|
4959620
|
"download controller-configuration" command fails if one drive of the same model has a different firmware version than the others
|
4930016
|
sccli reports wrong SCSI ID for SCSI bus
|
Sun StorEdge 3000 Family EOL Items
For End-of-Life documentation and other Sun StorEdge 3000 Family files, refer to the Sun StorEdge 3000 Family on the following website page:
http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/EOL_Products/index.html
The items now available in this location are:
- 816-7320, Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays which covers older rackmount kits
- Translated documentation for version 1.3 software and earlier firmware and installation guides, dated July 2003.