Wiki code for Using the mptt SAS target driver in COMSTAR

Hide Line numbers
1: =  Using the mptt SAS target-mode driver in COMSTAR
2: 
3: === Background
4: 
5:  The COMSTAR mptt driver provides the capability of using the following Sun SAS HBAs in target-mode within COMSTAR:
6: 
7: >
8: {{{
9: Marketing P/N		Sun P/N	    Chipset		Form factor
10: ~----------------	~--------    ~-------		~-----------
11: SG-XPCIE8SAS-E-Z	375-3487    1068e		PCIe
12: SG-XPCI8SAS-E-Z		375-3488    1068		PCI-X
13: }}}
14: 
15: === Driver
16: 
17:  The mptt driver is a COMSTAR target-mode driver loosely based on the "mpt" initiator driver that is currently part of the ON consolidation. It has been extensively modified to fit in the COMSTAR framework and to provide target-mode capability for SAS connectivity.
18: 
19:  This driver is not part of any Solaris release and is provided on an as-is basis. However, most of the necessary functionality is in place. This driver should operate well in standard SAS environments. Development was more or less complete in August, 2008, although a quick sanity check on build 107 indicates that the driver is still functional.
20: 
21: === Caveats
22: 
23:  The mptt driver does not support DDI suspend/resume, nor does it implement power management. This driver is designed to operate in wide- port configurations only.
24: 
25: === General Usage
26: 
27:  Usage of the mptt driver is similar to that of the qlt driver. See the existing COMSTAR documentation for details on creating and maintaining view entries (for zoning) and for details on enabling or disabling the COMSTAR service.
28: 
29:  The details provided here are intended for users that are already familiar with how to use COMSTAR and will aid in explaining how the various administrative actions (e.g. stmfadm) alter the behavior of the mptt driver.
30: 
31: === Installation
32: 
33:  The mptt driver was originally developed with the intent to have it installed as part of the SUNWstmf packages. Since it is not integrated into Solaris and the packaging has not been updated, there are no standalone packages for mptt.
34: 
35: 1. Download the "mptt.tar.gz" file from the Files link. It contains the following files:
36: >
37: {{{
38: ./root_i386-debug/usr/lib/mdb/kvm/amd64/mptt.so
39: ./root_i386-debug/usr/lib/mdb/kvm/mptt.so
40: ./root_i386-debug/kernel/drv/mptt.conf
41: ./root_i386-debug/kernel/drv/amd64/mptt
42: ./root_i386-debug/kernel/drv/mptt
43: ./root_sparc-debug/usr/lib/mdb/kvm/mptt.so
44: ./root_sparc-debug/usr/lib/mdb/kvm/sparcv9/mptt.so
45: ./root_sparc-debug/kernel/drv/mptt.conf
46: ./root_sparc-debug/kernel/drv/sparcv9/mptt
47: ./root_sparc-nondebug/kernel/drv/mptt.conf
48: ./root_sparc-nondebug/kernel/drv/sparcv9/mptt
49: ./root_sparc-nondebug/usr/lib/mdb/kvm/mptt.so
50: ./root_sparc-nondebug/usr/lib/mdb/kvm/sparcv9/mptt.so
51: ./root_i386-nondebug/kernel/drv/amd64/mptt
52: ./root_i386-nondebug/kernel/drv/mptt
53: ./root_i386-nondebug/kernel/drv/mptt.conf
54: ./root_i386-nondebug/usr/lib/mdb/kvm/amd64/mptt.so
55: ./root_i386-nondebug/usr/lib/mdb/kvm/mptt.so
56: }}}
57: 
58:  Pick the set of files for your system type and whether or not you want DEBUG drivers. That is, for x64 non-DEBUG, you want the files in the root_i386-nondebug directory. Or, for SPARC DEBUG, you’d want the files in the root_sparc-debug directory.
59:  The rest of the path indicates where the files need to be installed (you can just copy them with cp) relative to the root directory. The driver binaries and mdb library (mptt.so) should be "chown"ed to root:sys and "chmod"ed to 755 for the driver and 555 for the shared library. The mptt.conf file can also be "chown"ed similarly and "chmod"ed to 644.
60: 1. Modify driver bindings for a specific card type
61:  If you wish to run mptt on the PCIe (375-3487) card, remove the existing binding (likely to the "mpt" driver):
62: >
63: {{{
64: update_drv -d -i ’"pciex1000,58"’ mpt
65: }}}
66: 
67:  and add a binding for mptt
68: >
69: {{{
70: update_drv -a -i ’"pciex1000,58"’ mptt
71: }}}
72: 
73:  NOTE: If another driver is currently running on the card, a reboot will be required.
74: 1. Another possibility with later builds is to add a path-based binding for the specific instance of the card you wish to use. The device path can be found either from ’dmesg’ output, or from ’prtconf -v’ output. For example, the PCI-X HBA (375-3488) has a device ID of 0x3160. The device path can be found by doing:
75: >
76: {{{
77: -bash-3.2# prtconf -v|egrep ’dev_path.*3160’
78: dev_path=/pci@1d,0/pci1022,7450@1/pci1000,3160@1:mptt1
79: }}}
80: 
81:  The above controller is already being managed by the mptt driver, and there may be multiple lines of output depending on your system configuration, but the device path should be consistent per-HBA.
82:  You can add a binding for mptt to that specific instance by doing the following:
83: >
84: {{{
85: update_drv -a -i ’"/pci@1d,0/pci1022,7450@1/pci1000,3160@1"’ mptt
86: }}}
87: 
88: 1. Reboot the system if required.
89: 
90:  The mptt driver will now be attached and ready to run.
91: 
92: === Using mptt
93: 
94:  The svcadm(1M) command is used, among other things, to disable or enable the stmf service. When the stmf service is disabled, the mptt driver is taken off-line by means of resetting the IOC and releasing many of the driver’s resources. When the stmf service is enabled, the IOC is configured and communication is enabled.
95: 
96:  Although these cards are single-function cards, there are actually two physical ports. Thus, the mptt driver will register two target ports with the COMSTAR framework; one for each connector.
97: 
98:  For example, running "stmfadm list-target" will result in output similar to this:
99: 
100: >
101: {{{
102: -bash-3.2# stmfadm list-target
103: Target: wwn.500605B0000D9324
104: Target: wwn.500605B0000D9320
105: }}}
106: 
107:  Each target represents one physical connector on the HBA. This isn’t strictly necessary, but does allow for ease of administration specifically with respect to zoning. Logical units can be assigned/zoned to one individual port if desired.
108: 
109: === mptt.conf
110: 
111:  The mptt.conf file currently contains three entries. These are:
112: 
113: >  ddi-forceattach
114:  force-target-mode
115:  force-initiator-mode
116: 
117:  The ddi-forceattach entry is required and must not be modified.
118: 
119:  The force-target-mode and force-initiator-mode entries are used to tell mptt how to program the HBA. These parameters allow the user to ensure that the HBA is capable of operating either as a target or an initiator. This is required because these HBAs, by default, act only as an initiator. There is no way to allow the HBA to operate in both modes simultaneously.
120: 
121:  In order to allow the HBA to function as a target, the force-target-mode parameter must be set to "1". Similarly, to revert back to the original HBA behavior (i.e. "Initiator"), the force-initiator-mode value must be set to a "1".
122: 
123:  If both of these parameters are set to 0, no changes will be made to the current operating parameters of the HBA. If both are set to "1", target mode will take precedence and the HBA will be programmed to act in target mode (if it isn’t already doing so).
124: 
125: **NOTE**: The information below only pertains to versions of opensolaris prior to build 83. As of snv_83, [[this CR>>http://bugs.opensolaris.org/view_bug.do?bug_id=6638102]] will allow the mpt driver to put an HBA back into initiator mode if it is currently in target mode.
126: 
127:  If you wish to re-program an HBA that is currently being controlled by mptt in target mode back into initiator mode, you must perform the following steps:
128: 
129: >1. svcadm disable stmf ~-- Offline the HBA port
130: 1. modunload -i  ~-- Use modinfo to determine the module ID.
131: 1. Edit /kernel/drv/mptt.conf. Set force-target-mode to 0 and force-initiator-mode to 1.
132: 1. update_drv mptt ~-- This will reload mptt. The driver will re-program the HBA to operate as an initiator. After that occurs, mptt will no longer be able to use this HBA.
133: 1. rem_drv mptt ~-- This will uninstall the mptt driver (Optional)
134: 1. Use ’update_drv’ to modify the driver bindings as required.
135: 1. Reboot the system to allow mpt to reclaim that HBA.
OpenSolaris

Top Menu

Wiki code for Using the mptt SAS target driver in COMSTAR

Search

Collectives

Community Group

Project

User Group

Subsites

Project comstar Pages
