Solaris10: San/SAS/MPXIO/STMS config files
With the release of Solaris 10 Operating System (OS), the configuration of Storage Area Network (SAN), Serial Attached SCSI (SAS) attached devices, and turning on STMS/MPXIO has changed. This Post details the new ways devices are brought into the operating system, and their configuration files.
The default way Solaris 10 handles SAN/SAS attached devices is to auto-configure them. All devices seen on a Host Bus Adapter(HBA)/Attachment point in the SAN/SAS are automatically configured.
Use of the command: cfgadm -c configure is no longer needed.
If the old behavior is required, it can be turned on in the file:
/kernel/drv/fp.conf (only for SAN)
Uncomment the line below from the fp.conf file and reboot:
NOTE: Use of this property is not recommended. If used, the fabric devices accessed at boot time, need to be manually configured before the next reboot. Otherwise, fabric devices needed at boot-time may not get configured, and may cause boot problems.After manual_configuration_only is turned on, each device must be manually configured, as in past Solaris OS releases.
# cfgadm -c configure
The old repository, the /etc/cfg/fp/fabric_WWN_map file, is not used by default, on Solaris 10 OS. This file will not exist until the manual_configuration_only option has been turned on, and a device has been manually configured.
The new location to turn mpxio/stms off/on has moved from the file /kernel/drv/scsi_vhci.conf to the bottom of the /kernel/drv/fp.conf and /kernel/drv/mpt.conf file.
NOTE: patch 125081-10 is required to enable mpxio on SAS devices
The option is the same.
mpxio-disable=”yes” Disables mpxio for all FC/SAS devices.
mpxio-disable=”no” Enables mpxio for all FC/SAS devices.
The /kernel/drv/scsi_vhci.conf file still exists, which can be used for the following purpose.
If mpxio-disable=”yes” is specified it will disable the mpxio/stms globally, if you want to disable or enable mpxio/stms for the third-party storage arrays (for example: EMC), if you want to configure load-balancing and auto-failback behavior.
To disable STMS on a Per-FC-Port Basis in /kernel/drv/qlc.conf is not used now. Solaris 10 OS uses the /kernel/drv/fp.conf file, with the following syntax:
name=”fp” parent=”parent name” port=port-number mpxio-disable=”yes”
To disable STMS on a Per-SAS-Port Basis, Solaris 10 OS uses the /kernel/drv/mpt.conf file, with the following syntax:
name=”mpt” parent=”parent name” unit-address=”unit-number” mpxio-disable=”yes”;
The stmsboot command has new arguments to manage STMS in Solaris 10 OS:
stmsboot [-D fp|mpt] [-d | -e | -u | -L | -l controller_number]
-D fp|mpt -> to select the protocol where you want to enable/disable mpxio
-e -> to enable STMS on all HBA
-d -> to disable STMS on all HBA
-u -> to update vfstable and dump config after manual file configuration
-l or -L unchanged – see the manpage of stms for a full description.
eg:stmsboot -D mpt -d -> disable mpxio only on mpt devices.
Note: It is recommended to use the stmsboot -e command, to enable mpxio globally, and the stms -u command after a manual file configuration.
The deprecated option – show_FCP_dev has been replaced by the new show_SCSI_LUN option, and the deprecated unusable_FCP_dev option has been replaced by the new unusable_SCSI_LUN option.
# cfgadm -o show_SCSI_LUN -al
Ap_Id Type Receptacle Occupant Condition
c1 fc-private connected configured unknown
c1::50020f23000004aa,0 disk connected configured unknown
c1::50020f23000004aa,1 disk connected configured unknown
c2 fc-private connected unconfigured unknown
c3 fc connected unconfigured unknown
c4 fc connected unconfigured unknown