Overview of the Sun Storage J4500 Array
Exterior Features, Controls, and Indicators
Sun Storage J4500 Array Rack Slide Rails
To Place the Array Into Standby Power Mode
AC Power Failure Auto-Recovery
Updated Driver Files Required for Windows
Clustering Software Not Supported With the J4500 Array
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
Zoning Array Storage Resources Using CAM
Upgrading Sun Storage J4500 Array Firmware Using CAM
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
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
Configuring Multiple Host Access for a J4500 Array
To Configure Multiple Host Access for a J4500 Array
Supported Sun Storage J4500 Array Firmware and Common Array Manager (CAM) Software
Supported Operating Systems and Drivers
Supported Drives for Multipath
Multipathing Configuration Guidelines
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
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
To Enable Multipathing in Linux
To Disable Multipathing in Linux
Enabling and Disabling Multipathing in the Windows Operating System
How a Failover is Handled by Windows
To Enable Multipathing in Windows Server 2008
To Disable Multipathing in Windows Server 2008
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
Check the Event and Performance Logs
Using the Array Management Software to Monitor Enclosure Health
Resetting the Enclosure Hardware
To Reset the Enclosure Hardware Using the Reset Button
Clearing the Enclosure Zoning Password
Use the following guidelines when configuring access for array storage resources, whether you are performing an initial setup, or adding to an existing setup.
Make a note of the following:
SATA affiliation. The J4500 array uses SATA drives. When SATA drives are used, an affiliation (dedication) to the initiator (HBA port) is automatically created. This complies with the SATA protocol and is point-to-point in nature. If multiple initiators are attached to a single SAS fabric (either SAS A or B), the drive-to-initiator affiliation will be arbitrarily chosen which can create potential issues. To avoid issues with SATA affiliation, when using the CAM Access Configuration feature to configure array storage access between initiators and drives, the following rules apply:
In a configuration that includes multiple array-connected hosts, all Access Configuration changes must be done from a designated primary host. The primary host can be either an array-connected server with a full version of CAM installed, or a combination of a network-connected Management station and a single CAM proxy server (designated as the primary host) directly connected to array storage.
Use the primary host to perform Access Configuration for both the primary host and additional host initiators. CAM proxy agents on the additional hosts must be either unregistered or uninstalled until Access Configuration is complete for all initiators (from any connected host) using the primary host.
Until the CAM Access Configuration is complete using the primary host, do not run commands or other I/O on other array-connected hosts which might attempt to access the attached storage.
If you move an initiator connection from one array port to another on the array, any access configurations that were previously created must be recreated (or imported from a saved file) for that initiator.
Using Linux hosts. When using Linux hosts, if you add or remove array disks either physically, or through CAM Access Configuration, the host might hang or panic due to known Linux kernel issues. If you encounter this problem, a reboot of the host should resolve it.
Multipathing initiators. When multipathing initiators in a host for failover, unless otherwise specified in the guidelines, configure zoning of array storage first using CAM, then install the operating system multipath drivers.
Saving zoning information. After the desired CAM Access Configuration is completed, you should export the current SAS domain settings using the import/export functionality within the CAM Access Configuration page. This will allow you to revert back to functional settings in the event of mis-configuration, or if the J4500 array System Controller module (where zoning configurations are stored) is replaced.
Note - For the latest information on using CAM for zoning storage with the J4500 array, refer to the appropriate version of CAM documentation on the Sun web site: http://docs.sun.com/app/docs/prod/stor.arrmgr#hic