1sf(7D)                              Devices                             sf(7D)
2
3
4

NAME

6       sf - SOC+ FC-AL FCP Driver
7

SYNOPSIS

9       sf@port,0
10
11

DESCRIPTION

13       The   sf  driver  is  a  SCSA compliant nexus driver which supports the
14       Fibre Channel Protocol for SCSI on  Private  Fibre  Channel  Arbitrated
15       loops. An SBus card called the  SOC+ card (see  socal(7D)) connects the
16       Fibre Channel loop to the host system.
17
18
19       The  sf driver interfaces with the  SOC+ device driver, socal(7D),  the
20       SCSI  disk  target  driver,  ssd(7D), and the SCSI-3 Enclosure Services
21       driver,  ses(7D). It only supports SCSI devices of type disk and ses.
22
23
24       The  sf driver supports the standard functions  provided  by  the  SCSA
25       interface.   The driver supports auto request sense and tagged queueing
26       by default.
27
28
29       The driver requires that all devices have unique hard addresses defined
30       by   switch  settings  in  hardware.   Devices  with  conflicting  hard
31       addresses will not be accessible.
32

FILES

34       /platform/architecture/kernel/drv/sf
35
36           ELF kernel module
37
38
39       /platform/architecture/kernel/drv/sf.conf
40
41           sf driver configuration file
42
43

ATTRIBUTES

45       See attributes(5) for descriptions of the following attributes:
46
47
48
49
50       ┌─────────────────────────────┬─────────────────────────────┐
51       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
52       ├─────────────────────────────┼─────────────────────────────┤
53       │Architecture                 │SPARC                        │
54       └─────────────────────────────┴─────────────────────────────┘
55

SEE ALSO

57       luxadm(1M), prtconf(1M), driver.conf(4), socal(7D), ssd(7D)
58
59
60       Writing Device Drivers
61
62
63       ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
64
65
66       ANSI X3.269-1996, Fibre Channel Protocol for SCSI (FCP)
67
68
69       ANSI X3.270-1996, SCSI-3 Architecture Model (SAM)
70
71
72       Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
73

DIAGNOSTICS

75       In addition to being logged, the messages below may display on the sys‐
76       tem console.
77
78
79       The  first  set of messages indicate that the attachment was unsuccess‐
80       ful, and will only display while the  sf driver is initially attempting
81       to  attach.   Each  message  is  preceded  by   sf%d , where  %d is the
82       instance number of the  sf device.
83
84       Failed to alloc soft state
85
86           Driver was unable to allocate space for the internal  state  struc‐
87           ture.   Driver did not attach to device, SCSI devices will be inac‐
88           cessible.
89
90
91       Bad soft state
92
93           Driver requested an invalid internal state  structure.  Driver  did
94           not attach to device, SCSI devices will be inaccessible.
95
96
97       Failed to obtain transport handle
98
99           Driver  was unable to obtain a transport handle to communicate with
100           the socal driver. Driver did not attach  to  device,  SCSI  devices
101           will be inaccessible
102
103
104       Failed to allocate command/response pool
105
106           Driver  was  unable  to  allocate space for commands and responses.
107           Driver did not attach to device, SCSI devices will be inaccessible.
108
109
110       Failed to allocate kmem cache
111
112           Driver was unable to allocate space for the  packet  cache.  Driver
113           did not attach to device, SCSI devices will be inaccessible.
114
115
116       Failed to allocate dma handle for
117
118           Driver was unable to allocate a dma handle for the loop map. Driver
119           did not attach to device, SCSI devices will be inaccessible.
120
121
122       Failed to allocate lilp map
123
124           Driver was unable to allocate space for the loop  map.  Driver  did
125           not attach to device, SCSI devices will be inaccessible.
126
127
128       Failed to bind dma handle for
129
130           Driver was unable to bind a dma handle for the loop map. Driver did
131           not attach to device, SCSI devices will be inaccessible.
132
133
134       Failed to attach
135
136           Driver was unable to attach for some reason that  may  be  printed.
137           Driver did not attach to device, SCSI devices will be inaccessible.
138
139
140
141       The  next  set  of  messages  may display at any time.  The full device
142       pathname,  followed by the shorter form described above,  will  precede
143       the message.
144
145       Invalid lilp map
146
147           The  driver  did not obtain a valid lilp map from the socal driver.
148           SCSI device will be inaccessible.
149
150
151       Target t, AL-PA x and hard
152
153           The device with a switch setting t has an AL-PA x  which  does  not
154           match its hard address y. The device will not be accessible.
155
156
157       Duplicate switch settings
158
159           The  driver detected devices with the same switch setting. All such
160           devices will be inaccessible.
161
162
163       WWN changed on target t
164
165           The World Wide Name (WWN) has changed on  the  device  with  switch
166           setting t.
167
168
169       Target t, unknown device type
170
171           The  driver  does  not  know the device type reported by the device
172           with switch setting t.
173
174
175
176
177SunOS 5.11                        27 Mar 1997                           sf(7D)