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

Device Renaming

Dynamic Discovery of SAS Devices

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

Using the Array Management Software to Monitor Enclosure Health

Array Link Problems

Disks Problems

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

Enabling and Disabling Multipathing in the Linux Operating System

This section describes how to enable and disable multipathing in supported versions of the Linux operating system. The following subsections are included:

About Multipathing

After cabling your server for multipath, you will see two copies of each disk from the OS since you are using two separate array paths (SAS A and B). If you want to have multiple hosts accessing disks in the array, you must first set up zoning per host as described in Chapter 3, Adding and Zoning Array Storage Using CAM.

For example, if you have created a zone in each of the array's SAS domains that includes three disks, when entering the lsscsi command before MPxIO is installed, you will see two of each multipathed disk.

# lsscsi

[1:0:0:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sda
[1:0:1:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdb
[1:0:2:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdc
[1:0:3:0] enclosu SUN Storage J4500 3R21 -
[2:0:0:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdd
[2:0:1:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sde
[2:0:2:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdf
[2:0:3:0] enclosu SUN Storage J4500 3R21 -

Once the multipath daemon is started on the host, you can see multipath details using the multipath command.

# multipath -ll

35000c5000357625b dm-2 SEAGATE,ST340008SSUN0.4
[size=373G][features=0][hwhandler=0]
    \_ round-robin 0 [prio=2][active]
    \_ 1:0:1:0  sdb 8:0    [active][ready]
    \_ 2:0:1:0  sde 8:192  [active][ready]

To correlate the dm-2 dual path disks with what's displayed in CAM (in the Host details page, see Two Hosts With Zoned Disks in CAM), use the lsscsi command with the -g option.

# lsscsi -g

[1:0:0:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sda /dev/sg0
[1:0:1:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdb /dev/sg1
[1:0:2:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdc /dev/sg2
[1:0:3:0] enclosu SUN Storage J4500 3R21 - /dev/sg3
[2:0:0:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdd /dev/sg4
[2:0:1:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sde /dev/sg5
[2:0:2:0] disk SEAGATE ST330055SSUN300G 0B92 /dev/sdf /dev/sg6
[2:0:3:0] enclosu SUN Storage J4500 3R21 - /dev/sg7

For each disk, CAM will report the device names from the last column in the /dev/sgN format.

To Enable Multipathing in Linux

  1. Attach a J4500 array to a server with a supported version of Linux installed.
  2. On the server, edit or create the /etc/multipath.conf file.
  3. Reboot the server.
  4. After the reboot, make sure that the OS discovers all the disks in the J4500 array either by using the Linux commands, fdisk or lsscsi.
  5. Partition any disks you want to the desired sizes.
  6. Use the Linux command modprobe to add the loadable kernel modules dm-multipath and dm-round-robin.

    # modprobe dm-multipath

    # modprobe dm-round-robin

  7. Start the multipathd daemon.

    For Linux SUSE 9, use the following command:

    # multipathd -v0

    For other supported Linux versions, use the following command:

    # service multipathd start

  8. Start the multipathing device mapper target autoconfig.

    # multipath -v2

  9. List the multipath devices that have been created.

    # multipath -ll

    The output should list the same number of devices as there are disks in the J4500 array. The following is an example of output:

    35000c5000357625b dm-2 SEAGATE,ST340008SSUN0.4
    [size=373G][features=0][hwhandler=0]
        \_ round-robin 0 [prio=2][active]
        \_ 0:0:0:0  sda 8:0    [active][ready]
        \_ 1:0:0:0  sdm 8:192  [active][ready]

To Disable Multipathing in Linux

  1. If a RAID volume, LVM volume, or volume mount have been placed over the device node of the multipathed disk, quiesce the volume.
  2. Use the multipath -f command to disable multipathing to a specific device.

    # multipath -f mpath1

  3. Use the multipath -F command to disable multipathing on all multipathed devices.

    # multipath -F


    Note - If the message map in use appears for a device when you attempt to disable multipathing, the device is still in use. You must unmount or otherwise quiesce the device before you can disable multipathing. If you cannot quiesce the device, edit the /etc/multipath.conf file to exclude the device and then reboot the server.