C H A P T E R  6

Maintaining Your Array

This chapter covers the following maintenance topics:

6.1 Scanning Drives

When a SCSI array is powered on, the controller scans all physical drives that are connected through drive channels. Unlike Fibre Channel and SATA arrays, if a SCSI array has completed initialization and then a physical drive is connected, the controller does not automatically recognize the new drive until the next controller reset. This difference in behavior is due to differences between Fibre Channel and SCSI architectures and protocols.

Use the "Scan scsi drive" firmware application menu option to force the controller to scan a drive that has been added to a SCSI array, or use the scan disk command to scan and make available a hard drive without having to shut down the array. For more information about the scan disk command, refer to the "Disk Commands" section of the Sun StorEdge 3000 Family CLI User's Guide.

Note - Neither the "Periodic Auto-Detect Failure Drive Swap Check Time" firmware application menu option nor the "Periodic Drive Check Time" menu option force the scanning of a SCSI drive.

6.2 Using Software to Monitor and Manage Your Array

This section describes the software management tools available for monitoring and managing the Sun StorEdge 3310 SCSI array with inband connections.

Note - The Sun Storage CLI and the Sun StorEdge Configuration Service software can also be accessed through the Ethernet port for out-of-band management of the array. See Section 4.12, Setting Up Out-of-Band Management Over Ethernet.

The following software management tools are provided on the Sun StorEdge 3000 Family Software and Documentation CD provided with your array.

For details on how to install Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, or the Sun StorEdge CLI software, refer to the Sun StorEdge 3000 Family Software Installation Manual.

The CD also provides the related user guides, with detailed installation and configuration procedures for Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, and Sun StorEdge CLI.

6.2.1 Out-of-Band Connection

With the out-of-band serial port connection, you can use a Solaris tip session or a Microsoft Windows terminal emulation program to access the firmware application. For details about Microsoft Windows, see Section E.1, Setting Up the Serial Port Connection.

With the out-of-band Ethernet port connection, you can use the telnet command to access the firmware application. For details, see Section 4.12, Setting Up Out-of-Band Management Over Ethernet. You can also configure an array over the Ethernet connection with the CLI and the Sun StorEdge Configuration Service software.

6.2.2 Inband Connection

With inband host connections, you can use Sun StorEdge Configuration Service software or the command-line interface (CLI). Refer to the:

6.2.3 Enabling VERITAS DMP

To enable VERITAS Dynamic Multipathing (DMP) support on VERITAS Volume Manager in the Solaris OS, perform the following steps.

Note - To see instructions for enabling VERITAS DMP on other supported platforms, refer to your VERITAS user documentation.

1. Configure at least two channels as host channels (channels 1 and 3 by default) and add more host IDs, if needed.

2. Connect host cables to the I/O host ports configured in Step 1.

3. Map each LUN to two host channels to provide dual-pathed LUNs.

4. Add the correct string to vxddladm so VxVM can manage the LUNs as a multipathed JBOD.

# vxddladm addjbod vid=SUN pid="StorEdge 3310"
# vxddladm listjbod
VID       PID     Opcode   Page     Code   Page Offset SNO length
SEAGATE ALL 		     PIDs      18   		-1       36         12
SUN      StorEdge  3310     18      -1       36         12

5. Reboot the hosts. System reboot is required to implement these changes.

Note - JBOD arrays require a license from VERITAS to enable any of its advanced features. Refer to the VERITAS Volume Manager Release Notes or contact VERITAS Software Corporation for licensing terms and information.

6.2.4 The VERITAS Volume Manager ASL

VERITAS has provided an Array Software Library (ASL) that must be installed on the same host system as the Volume Manager software to enable the software to recognize a Sun StorEdge 3310 SCSI array.

Perform the following procedure to download the ASL and the accompanying installation guide for the Sun StorEdge 3310 SCSI 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.


3. Under the V heading, click on VERITAS Volume Manager Array Support 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. 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 Sun StorEdge 3310 SCSI array.

Note - The download link titled VxVM 3.5/4.x Sparc ASL for Sun StorEdge 3xxx Array, English is used for all 3000 family products.

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

6.3 Battery Operation

The battery LED (on far right side of the controller module) is an amber LED if the battery is bad or missing. The LED is blinking green if the battery is charging and is solid green when the battery is fully charged.

6.3.1 Battery Status

The initial firmware screen displays the battery status at the top of the initial screen where BAT: status displays somewhere in the range from BAD to ----- (charging), or +++++ (fully charged).

For maximum life, lithium ion batteries are not recharged until the charge level is very low, indicated by a status of -----. Automatic recharging at this point takes very little time.

A battery module whose status shows one or more + signs can support cache memory for 72 hours. As long as one or more + signs are displayed, your battery is performing correctly.

TABLE 6-1 Battery Status Indicators

Battery Display



Discharged; the battery is automatically recharged when it reaches this state.


Adequately charged to maintain cache memory for 72 hours or more in case of power loss. Automatic recharging occurs when the battery status drops below this level.


Over 90% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.


Over 90% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.


Over 90% charged; adequate to maintain cache memory for 72 hours or more in case of power loss.


Fully charged; adequate to maintain cache memory for 72 hours or more in case of power loss.

Your lithium ion battery should be changed every two years if the unit is continuously operated at 77°F (25°C). If the unit is continuously operated at 95°F (35°C) or higher, it should be changed every year. The shelf life of your battery is three years.

Note - The RAID controller has a temperature sensor that shuts off battery charging above 129.2°F (54°C). When this happens, the battery status might be reported as BAD, but no alarm is written to the event log since no actual battery failure has occurred. This behavior is normal. As soon as the temperature returns to the normal range, battery charging resumes and the battery status is reported correctly. It is not necessary to replace or interfere with the battery in this situation.

For information on the date of manufacture and how to replace the battery module, refer to the Sun StorEdge 3000 Family FRU Installation Guide.

For more information about the acceptable operating and non-operating temperature ranges for your array, see Section 2.3, Environmental Requirements.

6.4 Silencing Audible Alarms

An audible alarm indicates that either a component in the array has failed or a specific controller event has occurred. Error conditions and controller events are reported by event messages and event logs. Component failures are also indicated by LED activity on the array.

Note - It is important to know the cause of the error condition because how you silence the alarm depends on the cause of the alarm.

To silence the alarm, perform the following steps:

1. Check the error messages, event logs, and LED activity to determine the cause of the alarm.

Component event messages include but are not limited to the following terms:

caution icon

Caution - Be careful to observe and rectify a temperature failure alarm. If you detect this alarm, shut down the controller and the server as well if it is actively performing I/O operations to the affected array. Otherwise, system damage and data loss can occur.

Controller event messages include but are not limited to the following terms:

Refer to the "Event Messages" appendix in the Sun StorEdge 3000 Family RAID Firmware User's Guide for more information about controller events.

2. Depending on whether the cause of the alarm is a failed component or a controller event and which application you are using, silence the alarm as specified in the following table.

TABLE 6-2 Silencing Alarms

Cause of Alarm

To Silence Alarm

Failed Component Alarms

Use a paper clip to push the Reset button on the right ear of the array.


Controller Event Alarms

In the Firmware Application: From the RAID firmware Main Menu, choose
"system Functions right arrow Mute beeper." Refer to the Sun StorEdge 3000 Family RAID Firmware User's Guide fore more information.


In Sun StorEdge Configuration Service: Refer to "Updating the Configuration" in the Sun StorEdge 3000 Family Configuration Service User's Guide for information about the "Mute beeper" command.


In the Sun StorEdge CLI: Run mute [controller].

Refer to the Sun StorEdge 3000 Family CLI User's Guide for more information.

Note - Pushing the Reset button has no effect on controller event alarms and muting the beeper has no effect on failed component alarms.

6.5 Viewing Event Logs on the Screen

A controller event log records an event or alarm that occurs after the system is powered on. The controller event log records up to 200 events that occur after the system is powered on. The event log records configuration and operation events and error messages. The event log also shows alarm events reported by the event monitoring units in each RAID unit and expansion unit. The status of battery backup units, fans, temperatures, and voltages are sometimes recorded as well.

For each event, a <P> or <S> on the right side of the screen indicates whether the primary or secondary controller in a dual-controller configuration issued the event message.

caution icon

Caution - Powering off or resetting the controller automatically deletes all recorded event logs.

1. Choose "view and edit Event logs" on the RAID firmware Main Menu.

Screen capture showing the main menu with "view and edit Event logs" selected. 

A log of recent events is displayed.

TABLE 6-3 Example Event Logs

Controller Initialization Completed

LG:0 Logical Drive NOTICE: Starting On-Line Initialization

On-Line Initialization of Logical Drive 0 Completed

LG:1 NOTICE: CHL:2 ID:3 Starting Media Scan

LG:1 ALERT: CHL:2 ID:0 Media Scan Aborted

Note - The controller can store up to 200 event logs. An event log can record a configuration or operation event as well as an error message, notification, or alarm event.

2. Use your arrow keys to move up and down through the list.

3. To clear the events from the log once you have read them, use your arrow keys to move down to the last event you want to clear and press Return.

A "Clear Above xx Event Logs?" confirmation message is displayed.

4. Choose Yes to clear the recorded event logs.

Note - Resetting the controller clears the recorded event logs. To retain event logs after controller resets, you can install and use the Sun StorEdge Configuration Service program or the Sun StorEdge CLI.

6.6 Upgrading Firmware

From time to time, firmware upgrades are made available as patches that you can download from SunSolvetrademark Online, located at http://sunsolve.sun.com. Each patch applies to one or more particular pieces of firmware, including:

SunSolve has extensive search capabilities that can help you find these patches, as well as regular patch reports and alerts to let you know when firmware upgrades and other patches become available. In addition, SunSolve provides reports about bugs that have been fixed in patch updates.

Each patch includes an associated README text file that provides detailed instructions about how to download and install that patch. But, generally speaking, all firmware downloads follow the same steps:

6.6.1 Patch Downloads

1. Once you have determined that a patch is available to update firmware on your array, make note of the patch number or use SunSolve Online's search capabilities to locate and navigate to the patch.

2. Read the README text file associated with that patch for detailed instructions on downloading and installing the firmware upgrade.

3. Follow those instructions to download and install the patch.

6.6.2 Controller Firmware Upgrade Features

The following firmware upgrade features apply to the controller firmware:

When download is performed on a dual-controller system, firmware is flashed onto both controllers without interrupting host I/O. When the download process is complete, the primary controller resets and lets the secondary controller take over the service temporarily. When the primary controller comes back on-line, the secondary controller hands over the workload and then resets itself so the new firmware can take effect. This rolling upgrade is automatically performed by the controller firmware, and the user's intervention is not necessary.

A controller that replaces a failed unit in a dual-controller system is often running a newer release of firmware version. To maintain compatibility, the surviving primary controller automatically updates the firmware running on the replacement secondary controller to the firmware version of the primary controller.

Note - When you upgrade your controller firmware in the Solaris operating system, the format(1M) command still shows the earlier revision level.

6.6.3 Installing Firmware Upgrades

caution icon

Caution - Before updating your firmware, make sure that the version of firmware you want to use is supported for your array. Refer to the release notes for your array for Sun Microsystems patches containing firmware upgrades that are available for your array, and to SunSolve Online for subsequent patches containing firmware upgrades.

If you are downloading a Sun Microsystems patch that includes a firmware upgrade, the README file associated with that patch tells you which Sun StorEdge 3000 Family arrays support this firmware release.

To download new versions of controller firmware, disk drive firmware, or SAF-TE firmware, use one of the following tools:

Note - To download firmware to disk drives or SAF-TE firmware to a JBOD directly attached to a host, you must use the Sun StorEdge Configuration Service program.

Note - For instructions on how to download firmware to disk drives in a JBOD directly attached to a host, refer to the README file in the patch that contains the firmware.

caution icon

Caution - You should not use both inband and out-of-band connections at the same time to manage the array or you might cause conflicts between multiple operations.

6.7 Replacing the Front Bezel and Ear Caps

Some procedures require that you remove the front bezel and the small vertical plastic caps on either side of the bezel that cover the rackmount tabs. These rackmount tabs are often referred to as "ears."

6.7.1 Removing the Front Bezel and Ear Caps

1. Use the provided key to unlock both bezel locks.

2. Grasp the front bezel cover on both sides and pull it forward and then down.

Note - For many operations, including replacing disk drives, it is not necessary to further detach the bezel, since dropping it down moves it sufficiently out of the way.

3. Press the right bezel arm (hinge) towards the left side to release it from the chassis hole.

The left hinge also disengages.

4. Note the location of the chassis bezel holes on each ear.

5. Remove the plastic caps from the front left and right ears of the array.

Both plastic caps are removed in the same way.

a. Squeeze both sides of the cap at the top and the bottom.

b. Turn the cap toward the center of the array until it disengages and pull it free.

6.7.2 Placing the Bezel and Ear Caps Back Onto the Chassis

Each plastic cap is replaced in the same way, but be sure to place the cap with LED labels on the right ear.

1. Align the inside round notches of the cap with the round cylindrical posts (ball studs) on the ear.

2. Push the top and bottom of the ear cap onto the ear, pressing in on the top side toward the center of the array first.

3. Continue pushing the top and bottom of the ear cap onto the ear, pressing on the side toward the outside of the array.

Do not use force when placing a cap on an ear.

caution icon

Caution - Be careful to avoid "wedging" the Reset button below the LEDs on the right ear when you replace the plastic cap over it.

4. Insert the bezel arms into the chassis holes.

5. Lift the bezel into position and press it onto the front of the chassis until it is flush with the front.

6. Use the key to lock both bezel locks.