HP StorageWorks HSG80 Enterprise Modular Storage RAID Array Fibre Channel Solution Software V8.8 for Sun Solaris Release Notes (AA-RV1SA-TE, March 2005)

Host Operating System Notes
41HSG80 Enterprise Modular Storage RAID Array Fibre Channel Solution Software V8.8 for Sun
Solaris Release Notes
Number of Supported LUNs
This release of HP Solution Software adds support for 16 LUNs per port/Target.
This should be adequate for most installations.
However, the array controller and Solaris can support up to 64 LUNs per
port/Target. If your environment requires more than 16 LUNS/Target, you may
perform the following work-around, keeping the following items in mind:
■ Make sure that all the required patches are loaded.
■ You may need to adjust the sd_max_throttle setting in /etc/system.
■ SWCC has not been tested, and is not supported with more than 32 LUNs.
■ See the driver.conf (4) and sd (7D) man pages for more information.
1. Run
config.sh and choose Option 20; Add/change adapters.
2. Choose Option 4; Modify an adapter.
3. Select the adapter that you want to modify.
4. Follow the instructions to modify the number of LUNs/Target.
Note: Do not enter more than 64.
5. Create your LUNs on the array controller. If you are working in transparent
mode, units 0–99 appear on port 1 (al_pa=72, target=64), and units 100–199
appear on port 2 (al_pa=71, target=65). If you are working in multi-bus mode,
units 0-199 are visible on both ports.
6. Shut down and do a reconfigure boot (
boot -r), and your new units should be
ready for formatting.
sd_max_throttle Setting in /etc/system
Solaris defaults to a queue depth of 256 tagged commands per LUN, but it only
recognizes LUN 0 on each target. The HP RAID Manager software adds support
for 16 LUNs per target, but Solaris still allows 256 queued commands per LUN.
With 32 LUNs mounted, you can have over 8000 outstanding queued requests, but
the controller only supports 256 queued commands per port.
The solution is to restrict the maximum queue depth by setting
sd_max_throttle
in the
/etc/system file. The Solution Software has already throttled the queue
depth back to 32 during the installation. This works fine for most environments. If