1# CDDL HEADER START 2# 3# The contents of this file are subject to the terms of the 4# Common Development and Distribution License (the "License"). 5# You may not use this file except in compliance with the License. 6# 7# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 8# or http://www.opensolaris.org/os/licensing. 9# See the License for the specific language governing permissions 10# and limitations under the License. 11# 12# When distributing Covered Code, include this CDDL HEADER in each 13# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 14# If applicable, add the following below this CDDL HEADER, with the 15# fields enclosed by brackets "[]" replaced with your own identifying 16# information: Portions Copyright [yyyy] [name of copyright owner] 17# 18# CDDL HEADER END 19# 20# Copyright 2008 Sun Microsystems, Inc. All rights reserved. 21# Use is subject to license terms. 22# 23# Copyright 2019 RackTop Systems 24# 25# 26name="scsi_vhci" class="root"; 27 28# 29# Load balancing global configuration: setting load-balance="none" will cause 30# all I/O to a given device (which supports multipath I/O) to occur via one 31# path. Setting load-balance="round-robin" will cause each path to the device 32# to be used in turn. 33# 34load-balance="round-robin"; 35 36# 37# Automatic failback configuration 38# possible values are auto-failback="enable" or auto-failback="disable" 39auto-failback="enable"; 40 41#BEGIN: FAILOVER_MODULE_BLOCK (DO NOT MOVE OR DELETE) 42# 43# Declare scsi_vhci failover module paths with 'ddi-forceload' so that 44# they get loaded early enough to be available for scsi_vhci root use. 45# 46# NOTE: Correct operation depends on the value of 'ddi-forceload', this 47# value should not be changed. The ordering of entries is from 48# most-specific failover modules (with a "probe" implementation that is 49# completely VID/PID table based), to most generic (failover modules that 50# are based on T10 standards like TPGS). By convention the last part of a 51# failover module path, after "/scsi_vhci_", is called the 52# "failover-module-name", which begins with "f_" (like "f_asym_sun"). The 53# "failover-module-name" is also used in the override mechanism below. 54ddi-forceload = 55 "misc/scsi_vhci/scsi_vhci_f_asym_lsi", 56 "misc/scsi_vhci/scsi_vhci_f_asym_emc", 57 "misc/scsi_vhci/scsi_vhci_f_sym_emc", 58 "misc/scsi_vhci/scsi_vhci_f_sym_hds", 59 "misc/scsi_vhci/scsi_vhci_f_sym", 60# "misc/scsi_vhci/scsi_vhci_f_tpgs_tape", 61# "misc/scsi_vhci/scsi_vhci_f_tape", 62 "misc/scsi_vhci/scsi_vhci_f_tpgs"; 63 64# 65# For a device that has a GUID, discovered on a pHCI with mpxio enabled, vHCI 66# access also depends on one of the scsi_vhci failover modules accepting the 67# device. The default way this occurs is by a failover module's "probe" 68# implementation (sfo_device_probe) indicating the device is supported under 69# scsi_vhci. To override this default probe-oriented configuration in 70# order to 71# 72# 1) establish support for a device not currently accepted under scsi_vhci 73# 74# or 2) override the module selected by "probe" 75# 76# or 3) disable scsi_vhci support for a device 77# 78# you can add a 'scsi-vhci-failover-override' tuple, as documented in 79# scsi_get_device_type_string(9F). For each tuple, the first part provides 80# basic device identity information (vid/pid) and the second part selects 81# the failover module by "failover-module-name". If you want to disable 82# scsi_vhci support for a device, use the special failover-module-name "NONE". 83# Currently, for each failover-module-name in 'scsi-vhci-failover-override' 84# (except "NONE") there needs to be a 85# "misc/scsi_vhci/scsi_vhci_<failover-module-name>" in 'ddi-forceload' above. 86# 87# " 111111" 88# "012345670123456789012345", "failover-module-name" or "NONE" 89# "|-VID--||-----PID------|", 90# scsi-vhci-failover-override = 91# "STK FLEXLINE 400", "f_asym_lsi", 92# "SUN T4", "f_tpgs", 93# "CME XIRTEMMYS", "NONE"; 94# 95#END: FAILOVER_MODULE_BLOCK (DO NOT MOVE OR DELETE) 96