Sun StorEdge 3510 FC Array Release Notes

This document contains information about outstanding issues or requirements that affect installation and operation of the Sun StorEdge 3510 FC array.

---

New Features in This Release

• The Sun StorEdge Diagnostic Automated Diagnostic Environment 2.3 utility is currently being updated to support the Sun StorEdge 3510 FC array. When the update is completed, the SUNWstade 116720-06 patch will be required to support the Sun StorEdge 3510 FC RAID array. Sun StorEdge Diagnostic Automated Diagnostic Environment does not support the FC JBOD array at this time.
• The CLI 1.5 software has been enhanced to include diagnostics and troubleshooting features. Refer to the Sun StorEdge 3000 Family CLI 1.5 User's Guide for detailed information about new commands and options.
• The new Sun StorEdge Configuration 1.5 software offers a new battery status feature which displays the status of the battery and sets the battery in-service date for newly installed FC battery modules (FRU part number F370-5545-02 Rev. 50 or later).
• This release contains new firmware patch ID # 113723-07.

This patch contains all three types of firmware updates for the Sun StorEdge 3510 array controller subsystem. The patch includes firmware for the array controller itself, firmware for the SES processor, and firmware for a programmable logic device (PLD) that routes Fibre Channel data within the enclosure.

The SES and PLD firmware updates are applicable to the Sun StorEdge 3510 FC array expansion chassis as well as the chassis that houses the array controllers.

You do not need to install this patch if you have all of the following firmware revision levels in all of your FRUs.

• Controller firmware 3.27R
• SES firmware 1040
• PLD firmware 1000

You do need to install this patch if you have any of the following:

• Controller firmware version earlier than revision 3.27R
• SES firmware version earlier than revision 1040
• PLD firmware version earlier than 1000

See Installing Controller Firmware Patches for more information.

---

Release Documentation

These release notes supplement the documents shown in the following table.

You can download the documents listed in the preceding table (except EOL items) from either of the following locations:

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

or

http://docs.sun.com/db/coll/3510FCarray

---

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

---

System Requirements

The software and hardware identified in the following list have been tested and proven to work with the Sun StorEdge 3510 FC array.

• Supported Operating Systems and Management Software
• Other Supported Software
• Supported Platforms and Connection Methods
• Supported FC Switches
• Supported Disk Drives
• Supported Cabinets
• Supported Cables for Sun Systems

Supported Operating Systems and Management Software

The following table lists the operating environments and operating systems supported for hosts connected to the Sun StorEdge 3510 FC array.

The following table lists the software components of the Sun StorEdge 3000 Family Professional Storage Manager software for Sun StorEdge 3000 Family SCSI and FC arrays. See Downloading and Installing Updated Sun StorEdge 3000 Family Software for information about how to obtain this software.

Other Supported Software

The following table lists backup, clustering, diagnostic, and other supported software.

Supported Platforms and Connection Methods

TABLE 5, TABLE 6 and TABLE 7 list the Sun systems that are supported for the Sun StorEdge 3510 FC array. The table also shows the connection methods supported for each of the supported Sun systems.

Caution - Before connecting the array to a host running the Solaris 8 operating system or Solaris 9 operating system, make sure to download and install the Sun StorEdge SAN Foundation software on the host where the adapter is installed. The SAN software includes the driver for the host adapter. See Installing the Sun StorEdge SAN Foundation Software. Installation is mandatory for these operating systems because the driver is not included in the Solaris operating system. Without the driver, any array connected to the adapter cannot be seen by the host.

Support for Solaris 2.6 is now available. Use the following HBAs and the native Qlogic drivers. You must download and use the Qlogic Solaris SPARC driver package 4.13.01 or later. See the following Qlogic website for more details:

http://www.qlogic.com/support/oem_detail_all.asp?oemid=124

TABLE 9 lists information and connection methods supported for the Windows, Linux, Novell NetWare, HP-UX and IBM AIX operating systems.

Supported FC Switches

The following table lists the FC switches that are supported for the Sun StorEdge 3510 FC array.

Supported Disk Drives

The following table lists the disk drives that are supported for the Sun StorEdge 3510 FC array.

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

---

Software Support for JBODs

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

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

• about
• download pld-firmware
• download ses-firmware
• exit
• help
• quit
• select
• show frus
• show ses-devices
• version

To obtain information on each command, refer to the Sun StorEdge 3000 Family CLI User's Guide.

Supported Cables for Sun Systems

The following table lists the supported Fibre Channel cables for connecting to the host adapters that are supported for Sun systems. You can order cables using the marketing part numbers in TABLE 13.

---

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 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 # 113723-07 is available to upgrade Sun StorEdge 3510 FC arrays running firmware versions lower than 3.27R, and to upgrade the firmware for the controller's SCSI Enclosure Services (SES) chip to version 1040.

This patch contains two types of firmware updates for the Sun StorEdge 3510 FC array controller subsystem: firmware for the array controller itself and firmware for the SES processor.

You do not need to install this patch if you have all of the following firmware revision levels in all of your FRUs.

• Controller firmware 3.27R
• SES firmware 1040
• PLD firmware 1000

You do need to install this patch if you have any of the following:

• Controller firmware version earlier than revision 3.27R
• SES firmware version 1000 or A100
• PLD firmware version earlier than 1000

Follow the first three steps in To Download and Install the Firmware Patch to read specific information about fixed bugs and other changes incorporated in this firmware patch, as well as other detailed information and installation instructions.

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

• Using the RAID Controller serial or telnet interface, 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 3510 FC array, click on the View menu and the View Controller command, and then check the "FW Rev" checkbox.
• Using the CLI, enter the show inquiry command.

To determine your current SES and PLD firmware versions, use the following method:

• Using the CLI, enter the show ses command. The SES version of each controller is displayed in the Rev column. The PLD version is displayed in the PLD column.

1. Go to

http://sunsolve.Sun.com

2. Click on Patch Portal.

3. Use Patch Finder to locate patch ID 113723-07 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.

Caution - Do not use a version of CLI earlier than version 1.5 to install this patch.

1. Using the bourne shell, korn shell (ksh) or the bash shell (Linux), type the following command to identify the two SES device filenames in the chassis.

# for d in /dev/es/*; do sccli --list $d; done | grep 3510F > jbods.txt

This command runs the command sccli -list /dev/es/<d> for each device filename found in /dev/es, and save the lines that match the FC JBOD Array to the file jbods.txt. This command may take a few moments to complete and may display some harmless error messages referring to non-existent devices that may safely be ignored. When it completes, jbods.txt should contain two lines for each directly-attached JBOD chassis. For example, if jbods.txt contains:

/dev/es/ses3 SUN StorEdge 3510F D SN#000187

/dev/es/ses9 SUN StorEdge 3510F D SN#000187

it indicates that /dev/es/ses3 and /dev/es/ses9 are two separate SES devices within the JBOD expansion chassis with serial number 000187.

2. Verify that two device filenames are listed for each chassis serial number, identifying two SES devices in that chassis.

3. Invoke the CLI with the name of an SES device identified in Step 1. Using the example given in Step 1:

# sccli /dev/es/ses3

4. Type the following command to verify the Product and Revision of the array:

sccli> show inquiry

If the device is a JBOD chassis, "Product: StorEdge 3510F D" and "Device Type: Enclosure" are displayed.

5. Type the following command to verify the SES firmware version:

sccli> show ses

The output of this command displays the SES version under Rev, and displays the PLD version under PLD.

6. Verify that the SES code version identified in the Rev column indicates 1030 or earlier. If the SES code version is 1040, proceed to Step 13.

7. If the SSCS agent is running on your workstation:

• Issue the following shell command as root on the system where the SUNWscss package is installed to stop the SSCS agent:

# /etc/init.d/ssagent stop

• If the SSCS agent is running on a Microsoft Windows system connected to the array, issue the following command to stop the SSCS Agent service:

Start Run services.msc

8. If StorEdge Diagnostic Automated Diagnostic Environment or any other application which monitors the status of the enclosure is running, follow the procedure described in the documentation for that application to stop the agent software.

9. Invoke the CLI with the name of an SES device identified in Step 1. Using the example given in Step 1:

# sccli /dev/es/ses3

10. Type the following command to download the SES firmware:

sccli> Download ses-firmware fc2u_sun_1040a.s3r

The CLI upgrades the SES firmware. It is not necessary to reset the JBOD enclosure.

11. Type the following command to verify that the SES device has been upgraded:

sccli> show ses

12. Ensure that the SES firmware version indicated in the Rev column has changed to 1040.

13. Verify that the PLD code version identified in the PLD column indicates A000 or earlier. If the PLD code version is 1000, proceed to step 22.

Caution - If you use a version of the CLI that precedes version 1.5, or if array power is lost during this procedure, the enclosure can be rendered unusable.

Caution - The PLD firmware upgrade cannot be completed without power-cycling the array at the end of the procedure. Do not proceed if it is not possible to power cycle the array at this time.

14. Ensure that all host I/O activity has been stopped. The JBOD will be unable to process host I/O activity for up to 10 minutes.

15. Type the following command to download the PLD firmware:

sccli> download pld-firmware pld1r10.s3r

The CLI indicates that it is sending the PLD firmware data, and programming the flash memory. All the LEDs on the array light while flash is programmed, and the CLI will pause for three to five minutes.

Caution - Do not power cycle the array at this point. Note the time and wait at least five minutes for the PLD flash programming operation to complete.

16. Wait at least five minutes after seeing the message "Please wait 3 to 5 minutes until PLD flashing completes." Then turn power to the array off, wait 10 seconds and then turn power back on.

17. Invoke the CLI with the name of an SES device identified in Step 1. Using the example given in Step 1:

# sccli /dev/es/ses3

18. Type the following command to verify that the SES device has been upgraded:

sccli> show ses

19. Verify that the PLD column says 1040, indicating that the PLD firmware has been upgraded.

20. If the JBOD array contains:

a. Only one I/O Module FRU, the JBOD array can be returned to service.

b. Two I/O Module FRUs and two cables, repeat Step 9 through Step 19 for the second ses device identified in Step 1. Using the example identified in Step 1, you would connect with the JBOD by typing the command:

# sccli /dev/es/ses9

c. Two I/O Module FRUs and only one cable, move the cable from one I/O Module to the other and repeat Step 9 through Step 19.

---

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.

1. Go to:

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

2. Under Storage Management click the Sun StorEdge 3510 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.

---

Installing the Sun StorEdge SAN Foundation Software

Before a Sun host running the Solaris 8 operating system or Solaris 9 operating system can communicate with the Sun StorEdge 3510 FC array through any of the host adapters that are supported for Sun servers, you must install the Sun StorEdge SAN Foundation software.

The Sun StorEdge SAN Foundation software is required in these operating environments because it provides drivers for the supported host adapters. (See Supported Platforms and Connection Methods for listings of the applicable host adapters.)

If you are already running version 4.1 of the Sun StorEdge SAN Foundation software and do not want to upgrade to version 4.3 software, you need to download and run a script file. For information about that script file, refer to Sun StorEdge 3000 Family EOL Items.

See the following procedure for how to download the SAN Foundation software without charge from:

http://www.sun.com/storage/san

1. Log in as superuser on the Sun server to be connected to the array.

2. Go to:

http://www.sun.com/storage/san

3. At the bottom of the page, look for Get the Software, select the Sun StorEdge SAN 4.3 release Software/Firmware Upgrades and Documentation link.

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

5. Log in.

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

b. Click Continue on the Sun Download Center Welcome page to see the Terms of Use page.

c. On the Terms of Use page, read the license agreement, click Accept and then click the Continue button.

6. On the Download page, download the Solaris 8 SFS Base Packages or Solaris 9 SFS Base Packages, depending on which version of the Solaris Operating Environment you are running.

7. You can also download and read the SFS Base Packages read-me file for software download instructions.

8. Once you uncompress and untar the SFS Base Packages archive, follow the instructions in the Sun StorEdge SAN Foundation Software Installation Guide to manually install the packages.

---

Downloading the VERITAS Volume Manager ASL

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 3510 FC 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 or 4.0 software to enable the software to recognize the Sun StorEdge 3510 FC array. Follow the procedure to download the ASL and the accompanying installation guide for the Sun StorEdge 3510 FC array from Sun's 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 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 3510 FC array and the installation guide.

The document title is VERITAS Volume Manager Array Support Library Installation Guide for the Sun StorEdge 3510 FC array, part number 817-3186.

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.

---

Known Issues Affecting Sun StorEdge 3510 FC RAID Arrays

• Bug 5007124: SE3XXX Array LUNs retain EFI labeling even when rebuilt to less than 1TB. When a LUN is created larger than 1TB, Solaris will label the LUN as an EFI drive. If the LUN is later rebuilt to less than 1TB it will retain the EFI label. If the operator wants to revert back to SMI labeling, the format -e | label command is required. To relabel a LUN named c1t2d3 that is less than 1TB, enter the command in the format:

# format -e c1t2d3

format> label

[0] SMI Label

[1] EFI Label

Specify Label type 0

Select option 0 (SMI) and follow on-screen prompts to relabel the device.

• Bug 4995551: Serial numbers in event log are inconsistent or missing. No serial numbers are displayed from the firmware for controller initialization events. Controllers are identified as p (primary) or s (secondary), but a controller's primary and secondary roles are not fixed, and may change over time. Similarly, in the sccli, all controller events display the serial number of the primary controller, even if the event was generated by the secondary controller.
• Bug 4996006: 3510 JBOD: "SES/PLD firmware mismatch" error should be captured by sccli & SSCS. If an SES/PLD firmware mismatch is encountered on a 3510 JBOD, this condition is indicated by a flashing Event LED and an audible alarm. Neither of these indications are reported by sccli or Sun StorEdge Configuration Service.
• Bug 4960959: Controller boot error in maintenance operation test with I/Os. In certain cases, an inserted controller sometimes fails to become primary/secondary under heavy load. The LED on both controller are solid green and the LUNs assigned to secondary controller can not be accessed from a host.
• Bug 4975700: Slow 1K blocksize sequential write performance with dual controller. Applications that performed 1K (1024 bytes) sequential writes on a Sun StorEdge 3510 FC Array with redundant controllers might can encounter reduced speed.
• Bug 4980144: Dual ported disk can be scanned twice. If a disk drive is assigned to two channels, that drive can be scanned two times, once time for each channel. If this happens, it is possible to assign the same disk drive to a logical drive two times. To prevent this, take care to scan from only one channel any disk drives that are assigned to two channels.
• Bug 4967520. Firmware does'nt 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 can continue to be scanned after it fails. To prevent confusion, always replace a drive that has failed due to a "reassignment failure."
• Bug 4955390: Scgdevs cluster command causes array to reset. Array resets may occur when certain cluster commands, such as scrubber or scgdevs, stores keys in the persistent reservation area. The workaround is to skip restoring persistent reservations when the controller boots.
• Bug 4743721: SSCS: no method for identifying disk drives. The Sun StorEdge Configuration Service program currently cannot identify a disk drive by flashing disk drive LEDs on the array. To perform this operation, you can use the firmware application and select the "view and edit scsi drives" command. Then select the desired disk drive, press Return, and select the "Identify scsi drive" command which offers three modes for flashing the drive LEDs.
• Bug 4975148: SES fw upgrade via cli connects inter-controller-links that were disconnected. If FC port bypass is disabled on an array when you upgrade SES firmware, FC port bypass is enabled during the upgrade process. The array will then be unavailable to any hosts connected to bypassed ports. Manually disable FC port bypass again.
• Bug 4976393: SSCS monitoring sw not backward compatible with previous versions. When using a central host with Sun StorEdge Configuration Service to monitor of a number of systems with arrays attached, the SSCS software is not backward compatible with previous versions. The upgraded software cannot discover any previously monitored systems until you upgrade the agent package on the attached hosts.
• Bug 4990550: disk drive firmware download failed, but script reset controller and says succee. When downloading disk drive firmware using sccli, if the download fails, sccli reports that the download was successful and resets the controller.
• Bug 4931174: Invalid Transmission Word stop incrementing when it reaches 65535. The Invalid Transmission Word counter, which increments on detecting receive errors, stops counting when it reaches 65535. This counter is reset to zero when there is a power cycle or reset.
• Bug 4964418: StorADE: LD initialization send FW event but LD deletion does not send event. The Sun StorEdge 3510 FC Array does not save an event to the event log when a logical drive is deleted.
• Bug 4964422: StorADE: LD initialization event is inconsistent between telnet and SCCLI. The event message displayed by a telnet session with the Sun StorEdge 3510 FC Array is not the same as the event message that is displayed through sccli for the same event.
• Bug 4950237: sccli - show disks should show both disk channels, not just one. The sccli 'show disks' command shows only one channel. It does not show when disks are connected to two channels.
• Bug 4950297: Parity checks run from the GUI always enables auto correction of parity. When you run a parity check from Sun StorEdge Configuration Service, auto correction of parity is always enabled. To prevent risk of data corruption, run the parity check manually from the serial port or telnet window.
• Bug 4901347: Disk information from sccli and firmware don't match. Information returned by the Sun StorEdge 3510 through sccli is not as complete as information returned when monitoring the array through the firmware. For example, the when you monitor drive parameters through sccli, the SCSI Motor Spin-Up, SCSI Reset at Power-Up, and Disk Access Delay Time parameters are not displayed, as they are through the firmware.
• Bug 4901393: SCCLI error messages are too vague. Error messages may be unclear as they are displayed by the sccli, and are not defined in the sccli manual.
• Bug 4966606: When a disk is pulled out from 3510 array, sccli: disk status should be missing. When a disk is pulled out of the Sun StorEdge 3510 FC Array, the disk status is displayed through sccli is "Bad drive" instead of "Drive missing." Use the sccli show bypass device command and compare status change to determine if a disk has been removed.
• Bug 4946986: SSCS reports incomplete information about a critical error. Error information, as provided by Sun StorEdge Configuration Service and described in the Error Codes and Messages appendix of the Sun StorEdge Configuration Service User's Guide is not complete.
• Bug 4900452: Network connectivity through default gateway is unreliable. The out-of-band connection of the Sun StorEdge 3510 FC Array may not communicate with a host through the configured default gateway until communication is established with a network device that is on the same subnet as the array.
• Bug 4944252: After a disk failure, the drive is no longer displayed by sccli. After a disk drive fails, the drive is no longer displayed by sccli. Use the sccli show bypass device command and compare status change to determine the disk status.
• Bug 4872004: Time not consistent between primary and secondary controllers during failure. Time stamps in event messages from a secondary controller might not be consistent with time stamps included in the same event messages from a primary controller. While the time stamp in primary controller event messages are correct, secondary controller event message time stamps might be off by 12 hours, and the year might be incorrect.
• Bug 4938844: repartitioning a logical disk can cause all data on the logical disk to be lost. When you repartition a logical drive, a message is displayed that says you will lose all the data on the partition. However, if you delete the first partition on a logical drive, you will lose all data on the logical drive.
• Bug 4968076: Firmware higher than 327N experiencing a multi-initiator problem. When a Sun StorEdge 3510 FC Array with firmware version higher than 327N is connected by switch in SAN configuration in a multi-initiator environment, Sun Cluster 3.0 receives SCSI timeout and transport errors. The array needs to be at firmware version 3.27N to work in SunCluster 3.0 environment.
• Bug 4903391: download disk drive firmware fail. Disk drive firmware will be delivered in a separate patch. The utility to download the patch will be included with the patch. Do not use sccli or SSCS to download disk drive firmware.
• Bug 4959806: SCCLI: can't gain access to LG# from the firmware. Logical drive numbers and logical volume numbers may not appear correctly when viewed through sccli. On the Sun StorEdge 3510 FC Array, if you create logical drive 0, 6 and 7, and map logical drive 0 to ch 0 id 40, to be used for the management port. While logical drive 0 is displayed as ld0 by the sccli, logical drives 6 and 7 are displayed as ld1 and ld2. If you use logical drives 6 and 7 to create logical volume 7, sccli displays logical volume 7 as lv0.
• Bug 4977959: SE3510 with 10 x 146GB drives, has the controllers failing without activity. The Sun StorEdge 3510 FC Array primary controller might fail with ten 146GB disks. This failure occurs when running the extractor or explorer scripts while the array is configured in the SAN or via direct attachment to a V880 server. The array primary controller can fail when there is no IO activity. It can also fail when running the explorer 4.2 or the se3kxtr 0.1.5. Do not use the command "unfail secondary" via sccli, because the command fails the other controller and the array hangs. The only fix is to power cycle the array, and if that does not restore operation, re-seat the controller. After a couple of hours, the controllers might fail again.
• Bug 4993789: ESM prohibits SSCS monitoring - no heartbeat from server. If ESM is installed and configured on a Sun StorEdge 3510 host, Sun StorEdge Configuration Service might report that it did not receive heartbeat around every 20 minutes. Turn off ESM and you can monitor the array through Sun StorEdge Configuration Service without issues.
• Bug 4883836: sccli: no method for identifying disk drives. There is currently no way to identify a disk drive by turning on its LED via sccli.
• Bug 4993105: Read/Write Failures on SE3510 during 24 hour RSCN fault injection test. During the twenty-four hour RSCN fault injection test, at varying intervals, the host may lose all paths to the Sun StorEdge 3510 FC Array. At this point, a read/write error occurs, and all I/O is stopped to the Sun StorEdge 3510 LUNs.
• Bug 4924834: Physical disk drive are displayed with inconsistent size throughout the product. The same disk drive size is displayed as 34476M by the sccli, 34476MB by the xml output, 33.92GB by the sccli show config command, and 34732MB by the tip/telnet output.
• Bug 4991110: sccli show channels indicates speed has changed from 2G to ASYNC. After upgrading the Sun StorEdge 3510 FC Array firmware to 327Q, the output from the show channels command for each of the host channels might change from "2g" to "ASYNC."
• Bug 4992074: failed drive disappears. When building a logical drive using a disk that has a bad block, if block reassignments fail and the drive fails, and logical drive initialization might also fail. If you try to use the firmware to identify the disk drive, the firmware "view and edit scsi Drives" menu will report that the disk drive is missing. If you reset the controller, the disk drive is displayed again
• 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. The cache in the Sun StorEdge 3510 RAID array is mirrored between the primary and secondary controllers; however, to ensure data integrity, you may choose to disable the Write Back cache option and switch to the Write Through cache option.
• Bug 4819218: Differences between firmware and sccli events. The firmware application menu event log timestamp and the sccli event log timestamp will appear as different times. This is because the firmware application menu gets its time stamp information from the time that is set on the RAID controller, and the sccli utility gets its time stamp information from the server that it is running on. Additionally, the sccli utility currently reports events from the primary controller only. The workaround is to manually set the clock on the controller to match the server to which it is connected.
• Bug 4714227: The character interface sometimes 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 4825806: BBU warnings should not be as severe. The Sun StorEdge 3510 FC array has a battery circuit board that monitors and charges the battery during normal operation. Since the battery is not charging while the array is powered off, some of the charge of the battery will dissipate. When the array is powered on, the battery circuit board will detect the power dissipation of the battery and will display the following message: "|[0125] WARNING: Controller BBU Not Fully Charged" and begin to recharge the battery. Once the battery is fully charged, the following message will be displayed: "|[01A5] NOTICE: Controller BBU Fully Charged!"
• Bug 4859115: long delays with StorEdge 3510 array (256 LUNs mapped). On a Sun StorEdge 3510 FC array with 256 LUNs mapped attached to a system, the Explorer diagnostic tool takes about six hours and forty minutes to complete. Even though there aren't any T3 arrays attached to they system, there was a large delay here. The workaround is to use the -w !t3,!t3extended option, reducing the time it takes explorer to complete to approximately 40 minutes.
• Bug 4822129: inconsistent error message between reporting methods and documentation. Event messages sometimes differ between firmware logs, Sun StorEdge Configuration Service, CLI, and SNMP traps. These inconsistencies will be addressed in a future release.
• Bug 4926681: FC3510 does not log into switch after switch fault. If you choose to connect one or more of the host channels on the StorEdge 3510 RAID to a 1-Gb switch in Loop mode, the speed on those channels must be set to 1 GHz. This will ensure proper negotiation if communication is lost to the switch and then restored. This is not required if you are operating in point-to-point mode. It is also not required if you are connected to a 2-Gb switch.
• Bug 4921484: 3510 and 3310 did not shut down during extended overtemp conditions. The unit must shut down if the temperature exceeds the given limit. Currently the unit does not shut down. However, the unit is fully NEBS certified, and will handle the required temperatures required by NEBS certification.
• Bug 4896313: Cache data isn't flushed correctly in case of primary battery failure. If the battery is unplugged or dead, write cache is not disabled. This means that if power is lost, data in the cache could be lost.
• Bug 4881785: Cluster panics with Logical Volume on Secondary Controller. In a Sun cluster environment, when the logical volumes are assigned to the secondary controller, the cluster will panic during node failover. The documentation has been modified to warn against using logical volumes (a legacy feature) in a Sun Cluster environment.
• Bug 4888608: Solaris SES driver receives incorrect response from 3510 RAID in attach. The issue concerns the SES emulation response with LUN masking. If the 3510 array is configured for LUN masking and LUN 0 is not mapped to a logical drive, the array will return a zero length response to an SES configuration mode page request. This causes the Sun driver not to attach the device.
• Bug 4906783: Firmware is not integrated with the FRU-ID's. The RAID Controller serial number is displayed in the error messages instead of the FRU-ID serial number. This can be very confusing and of little use to the customer.
• Bug 4911841: SE3510 - unable to send SNMP traps using 'agent.ini' file, as documented. SNMP traps from the SE3510FC are unable to be sent using the 'agent.ini' file, as documented in the User's Manual. The workaround is to use SSCS to send the SNMP traps.
• Bug 4942959: Storade - device port status is not monitored by 3510 firmware or sccli sw. The host should detect that a cable is removed. Adding this functionality to the RAID Controller Firmware would require a very significant amount of effort.
• Bug 4960491: Mix of 1gig and 2gig HBA on same channel causes loss of device. Connecting the Sun StorEdge 3510 RAID array to Fibre Channel HBAs on the same channel that use different speeds (1 Gb & 2 Gb) is not supported. You can, however, mix 1-Gb and 2-Gb FC HBAs on different channels. This limitation is due to the design of the Sun StorEdge 3510 RAID array's port bypass circuitry and the inability of Fibre Channel to support auto-negotiation in a multi-drop loop configuration.
• Bug 4967762: best practice for cabling expansion units isn't. The "Scaling Beyond 36 Disks" section of the Sun StorEdge 3000 Family Best Practices Manual for the Sun StorEdge 3510 FC Array, 816-7325-13, contains three new drawings whose cabling allows for a single point of failure and makes troubleshooting difficult.
• RFE 4949375: ability to map more than one partition to a LUN not documented. The chapter on mapping partitions to LUNs in the firmware guide: 5. Viewing and Editing Host LUNs Sun StorEdge 3000 Family RAID Firmware 3.27 User's Guide 816-7934-12 doesn't let customers know that multiple partitions can be assigned to the same LUN, nor does it cover when a customer might want to do this. Since there has been some confusion regarding this, as well as one escalation which was aided by this information, it should be described in the user docs.
• RFE 4949382: Skip option should be covered in user documentation. Through the serial port, customers currently have the option of skipping persistent group reservations as the controller comes up (from either a reset or power-cycle). These messages are displayed: "Scanning SCSI channels. Please wait a few moments! Preparing to restore saved persistent reservations. Type 'skip' to skip:" If you don't type "skip" within 30 seconds, these messages follow: "Scanning SCSI channels. Please wait a few moments! Restoring saved persistent reservations." This functionality and the purpose behind it aren't covered in any user documentation.
• Under heavy load, the SSCS console might become unresponsive. If the Sun StorEdge Configuration Service (SSCS) console does not reconnect after the load decreases, perform a rescan. This situation can also prevent event messages from being emailed by SSCS Console and Diagnostic Reporter software, as well as updating of the SSCS console. The workaround is to assign a primary host LUN for SSCS to communicate with exclusively. No data or I/O should be used on this path. In order for this workaround to be effective, you must map only the LUN that SSCS will use and configure SSCS before mapping the data drives.
• When configuring the Web Server for use with ESM the Configure Web Server feature may fail. When configuring the Web Server for use with Enterprise Storage Manager, the Configure Web Server feature under Custom Configuration Options may fail. To configure the Web Server manually, log in as root on the host on which the Sun StorEdge Configuration Service agent is running and issue the command:

# /usr/sbin/sscfghtml.sh -i ipaddress -p password

where ipaddress is the host name or IP address of the array, and password is the password assigned to the array. Allow 20-30 seconds for this command to complete, and then verify that it worked by using any web browser to visit:

http://ipaddress/esm.html

The Web browser displays a message "This page launches the Sun StorEdge(tm) Configuration Service Console applet" and, if the SUNWnsmat package is installed, the SSCS GUI will be launched.

---

Fixed Software Bugs

The following bugs have been fixed in Version 1.5 of Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter and Sun StorEdge CLI.

---

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

---

Sun StorEdge 3000 Family EOL Items

For End-of-Life documentation for the Sun StorEdge 3000 Family products, 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:

• Sun StorEdge 3000 Family Rack Installation Guide for 2U Arrays (816-7320) which covers older rackmount kits
• Sun StorEdge SAN Foundation 4.1 Information for the Sun StorEdge 3000 Family (817-6620)
• Translated documentation dated July 2003, in French, Japanese, Simplified Chinese, Traditional Chinese, and Korean

^{1 (TableFootnote) This manual includes instructions for the universal rack kit. To obtain the rack kit guide for older rackmount kits, refer to Sun StorEdge 3000 Family EOL Items.}

Sun StorEdge 3510 FC Array Release Notes

816-7301-20

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