Setup Guide

Queue Depth
Queue depth is the amount of SCSI commands (including I/O requests) that can be handled by a storage device at a given time.
A queue depth can be set on either of the following:
Initiator level - HBA queue depth
LUN level - LUN queue depth
The LUN queue depth setting controls the amount of outstanding I/O requests per a single path. The HBA queue depth (also
referred to as execution throttle) setting controls the amount of outstanding I/O requests per HBA port.
With PowerStore and Solaris, the HBA queue depth setting should retain its default value, and the initial LUN queue depth
setting should be modified to 64. This is a good starting point provided good I/O response times. The specific value can be
adjusted based on particular infrastructure configuration, application performance and I/O profile details.
Solaris Host Parameter Settings
This section describes the Solaris host parameter settings required for optimal configuration when using Dell Technologies
PowerStore storage.
Configuring Solaris native multipathing
For a PowerStore cluster to properly function with Oracle Solaris hosts, configure the multipath settings as described in the
following sections.
NOTE: If the host is connected to a cluster other than PowerStore, the configuration file may include additional devices.
NOTE: Currently, PowerStore clusters are only supported with native Solaris multipathing (MPxIO).
Enable Solaris native multipathing on Solaris 10 and 11.0-11.4 hosts (SPARC
and x86)
To enable management of storage LUNS that are presented to the host with MPxIO, use the following command:
# stmsboot -e
NOTE:
the host must be rebooted immediately after the command execution is complete. It is recommended to update all
storage-related host configuration files before rebooting.
Updating scsi_vhci.conf configuration file
About this task
the scsi_vhci.conf fie is used to configure third-party storage multipathing parameters on Solaris 11 hosts, based on SCSI inquiry
responses. The host sends SCSI inquiry commands and, based on the returned data, MPxIO driver will activate the
corresponding multipathing module. The load balancing and failover policies are also configured, based on the settings in the
scsi_vhci.con file.
Steps
1. Run the following command to verify the scsi_vhci.conf file location:
# ls /etc/driver/drv/
2. If the file is not in the expected location, run the following command to copy it from /kernel/drv:
# cp /kernel/drv/scsi_vhci.con /etc/driver/drv
3. Run the following commands to create a backup copy and modify the file:
46
Host Configuration for Solaris