JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Storage J4500 Array System Overview
search filter icon
search icon

Document Information

Preface

1.  Hardware Overview

Overview of the Sun Storage J4500 Array

Features

Exterior Features, Controls, and Indicators

Front Panel

Back Panel

Supported Server Platforms

Supported Host Bus Adapters

Installation Overview

Sun Storage J4500 Array Rack Slide Rails

Compatible Racks

Tools and Staff Required

Configuration and Cabling

Term Definitions

Configuration Rules

Cabling the SAS Connectors

Example Configurations

Powering On and Off the Array

To Power On the Array

To Place the Array Into Standby Power Mode

To Power Off the Array

AC Power Failure Auto-Recovery

2.  Software Overview

Operating System Support

Updated Driver Files Required for Windows

Clustering Software Not Supported With the J4500 Array

Array Management Overview

Management Term Definitions

About Enclosure Management

Array Management Options

Management Options When Using the StorageTek SAS RAID External HBA (Adaptec-Based)

Management Options When Using the StorageTek SAS External HBA (LSI-Based)

Using the Common Array Manager Software

Viewing Sun Storage J4500 Array Information With CAM

Problem Resolution

Zoning Array Storage Resources Using CAM

Upgrading Sun Storage J4500 Array Firmware Using CAM

Obtaining CAM Software

Using the StorageTek RAID Manager Software

Viewing Sun Storage J4500 Array Information With the Sun StorageTek RAID Manager

3.  Adding and Zoning Array Storage Using CAM

Overview of Zoning

System Requirements

Access Configuration (Zoning) Guidelines

Adding (Cascading) a J4500 Array to An Existing Zoned J4500 Array

To Prepare an Existing Array Prior to Cascading Additional Storage

To Prepare a New J4500 Array for Cascading

To Cascade Arrays Using CAM

Configuring Multiple Host Access for a J4500 Array

To Configure Multiple Host Access for a J4500 Array

4.  SAS Multipathing

System Requirements

Supported Sun Storage J4500 Array Firmware and Common Array Manager (CAM) Software

Supported HBAs

Supported Operating Systems and Drivers

Supported Drives for Multipath

Multipathing Configuration Guidelines

Configuration Examples

Multipathing With One Host, One HBA and One Array

Multipathing With One Host, One HBA and Cascaded Arrays

Multipathing With One Host, Two HBAs and Cascaded Arrays

Multipathing With Two Hosts, Four HBAs and Cascaded Arrays

Multipathing With Two Hosts, Multiple HBAs and Cascaded Arrays

Enabling and Disabling Multipathing in the Solaris Operating System

About Multipathing

stmsboot Options

stmsboot Conditions

To Enable Multipathing on LSI-Based Multipath-Capable Controllers

To Disable Multipathing on LSI-Based Multipath-Capable Controllers

Configuring Multipathing on Selected Ports

Enabling and Disabling Multipathing in the Linux Operating System

About Multipathing

To Enable Multipathing in Linux

To Disable Multipathing in Linux

Enabling and Disabling Multipathing in the Windows Operating System

About Multipathing

How a Failover is Handled by Windows

To Enable Multipathing in Windows Server 2008

To Disable Multipathing in Windows Server 2008

5.  Troubleshooting

CAM Service Advisor

To Access Service Advisor Procedures

Taking Electrostatic Discharge (ESD) Precautions

To Reserve the Array for Maintenance

To Release the Array After Maintenance

Understanding the CAM Event Log

Troubleshooting Problems with the Array

Initial Start-up

Check the Event and Performance Logs

Identifying Disks in the Array Enclosure

Using the Array Management Software to Monitor Enclosure Health

Array Link Problems

Switching SAS Cables or Making New Connections

Disks Problems

To Replace a Disk

Guidelines for Removal and Replacement of RAID Storage

Persistent Affiliation When Changing HBAs

If You Do Not See All of the 48 Disks

Array Environment Problems

Power Problems

Resetting the Enclosure Hardware

To Reset the Enclosure Hardware Using the Reset Button

Clearing the Enclosure Zoning Password

To Clear the Enclosure Zoning Password

Index

Troubleshooting Problems with the Array

The following sections describe how to troubleshoot problems you may experience with the J4500 array.

Initial Start-up

If you are unable to see the array drives after powering on the array, check the following:

Check the Event and Performance Logs

The operating system event log is a good first place to start in identifying problems or potential issues with the array enclosure or its disks. If you experience disk problems, such as disk errors or invalid read/writes, the system event log can help identify the problem disk.


Note - By default, errors for the enclosure (temperature, voltage, device status), may not be logged in the system event log, but only in the array management software event log. If you want errors to be forwarded to the system event log, refer to the HBA documentation to see if it supports this feature.


You may have problems with the array listed in multiple log files (system and HBA). If this is the case, concentrate on recent errors that best relate to the problem. Try to pinpoint the time when problems began to appear. Search through the log files as soon as possible for when the problems first appeared—log files can quickly fill up with errors and some information may be lost.

Identifying Disks in the Array Enclosure

Disks in the array enclosure are typically identified by the operating system in sequential order in a list of 51 devices; the first 4 addresses (0-3) represent the array's four SAS expanders, the other 48 addresses (4-51) represent the 48 hard disks. Drives are mapped in numerical order as shown on the drive map label on the top of the array enclosure. Device names and address information depends on other mass storage devices attached to the server and where the array's HBA is located in the PCI bus boot order.

Using the Array Management Software to Monitor Enclosure Health

Your J4500 array supports a powerful set of SMP (Serial Management Protocol) and SES-2 (SCSI Enclosure Services) enclosure management features. Some or all of these features are available through supported management software (for example, the Sun Common Array Manager (CAM), or the Sun StorageTek RAID Manager software) to provide a system administrator at the array-connected server or network-connected management console the following capabilities:

Refer to Chapter 2, Software Overview for more information on array management software.

Array Link Problems

You may encounter a problem where the server is unable to communicate with the array. Complete the following troubleshooting tasks to reestablish communications with the array.

Switching SAS Cables or Making New Connections

In a single path environment: If your J4500 array is connected to the StorageTek SAS RAID External HBA, and you switch a cable from one port of the HBA to the other port on the HBA, you should wait long enough after the initial cable pull for all the physical hard drives shown in the GUI or through the CLI to be removed from the display. This prevents the problem of the controller attempting to remove drives at the same time it is reading the same drives on another port. If no display is available, you should wait at least 2 minutes between pull and reconnect.

In a multipath environment: Since the J4500 array uses SATA drives, the potential for SATA affiliation conflicts exists. Conflict can occur when more than one initiator tries to access the drive via the same path (for example, two hosts attached to SAS A on a J4500 array), or if you move an established connection from one domain port to another (for example, from port 0 to port 1). Possible symptoms of SATA affiliation conflicts are: operating system hangs, zoning operations take longer than 10 minutes to complete, and/or disk utilities like “format” will not return device lists in a timely fashion. For more about SATA affiliations, see Access Configuration (Zoning) Guidelines.

Disks Problems

Issues with array disks might be identified by viewing the system event log, being alerted by your array management software, or by viewing the J4500 array's LEDs. In the event of a disk failure, the disk may be replaced with the array online.

To Replace a Disk

If the disk must be replaced, complete the following tasks:

  1. Slide the J4500 array out of the rack far enough to remove the disk top cover panel. For step-by-step procedures, refer to the Sun Storage J4500 Array Service Manual (820-3160).
  2. To replace a disk, use the operating system, or enclosure management software command to unmount the disk and prepare it for removal. This is required to isolate the disk and stop all read/write activity.
  3. Identify the physical disk to be removed by looking for the blue ready-to-remove LED, or the amber failed LED, on the disk. Then, remove the disk. For step-by-step procedures for removing disks from the enclosure, refer to the Sun Storage J4500 Array Service Manual (820-3160).
  4. Replace the disk, then use the operating system or enclosure management software commands to remount the disk. If the disk is part of a RAID volume, it will automatically rebuild with the required data after replacement.

Guidelines for Removal and Replacement of RAID Storage

When removing and replacing RAID disks in the J4500 array, use the following guidelines:

Persistent Affiliation When Changing HBAs

When connecting your array to an HBA, it is possible that the SAS “affiliation” feature may cause problems if the array was previously connected to another HBA. An affiliation is used by the SAS protocol to prevent multiple SAS initiators (HBAs) from interfering with each other when communicating with SATA drives. If you encounter such a problem, affiliations may be removed by power cycling the array enclosure prior to connecting it to a different HBA.

If You Do Not See All of the 48 Disks

If you see only some of the available disks (for example, if you see only 20 or 28 of the total 48 disks), try the following:

Array Environment Problems

The array enclosure needs to operate within a specific temperature range (below 35 °C or 95 °F). If the internal temperature is above that, the fans automatically increase in speed when a thermal threshold is reached. This could be a reaction to higher external ambient temperatures in the local environment. If the fan noise level and tone seem high, check to ensure there is no airflow restriction raising the enclosure's internal temperature.

If an excessive temperature threshold is reached that could damage components in the enclosure, the J4500 array Over Temperature LED will light. If this happens do the following:

Power Problems

The J4500 array includes redundant, hot-swappable power supplies. If a power supply fails, you may be alerted by the array management software or the array power supply status LEDs (an alert LED will light amber both at the front and rear of the array enclosure when service is required). For step-by-step procedures for replacing an enclosure power supply, refer to the Sun Storage J4500 Array Service Manual (820-3160).