1fcip(7D) Devices fcip(7D)
2
6 fcip - IP/ARP over Fibre Channel datagram encapsulation driver
7
9 /dev/fcip
10
13 The fcip driver is a Fibre Channel upper layer protocol module for
14 encapsulating IP (IPv4) and ARP datagrams over Fibre Channel. The fcip
15 driver is a loadable, clonable, STREAMS driver supporting the con‐
16 nectionless Data Link Provider Interface, dlpi(7P) over any Sun Fibre
17 Channel transport layer-compliant host adapter.
18 The fcip driver complies with the RFC 2625 specification for encapsu‐
21 lating IP/ARP datagrams over Fibre Channel, and allows encapsulation of
22 IPv4 only, as specified in RFC 2625. The fcip driver interfaces with
23 the fp(7d) Sun Fibre Channel port driver.
24
26 The cloning character-special device /dev/fcip is used to access
27 all Fibre Channel ports capable of supporting IP/ARP traffic on the
28 system.
29 fcip and DLPI
31 The fcip driver is a "style 2" Data Link Service Provider. All M_PROTO
32 and M_PCPROTO type messages are interpreted as DLPI primitives. Valid
33 DLPI primitives are defined in <sys/dlpi.h>. Refer to dlpi(7P) for
34 more information on DLPI primitives.
35 An explicit DL_ATTACH_REQ message must be sent to associate the opened
38 stream with a particular Fibre Channel port (ppa). The ppa ID is
39 interpreted as an unsigned long data type and indicates the correspond‐
40 ing Fibre Channel port driver instance number. An error (DL_ERROR_ACK)
41 is returned by the driver if the ppa field value does not correspond
42 to a valid port driver instance number or if the Fibre Channel port is
43 not ONLINE. Refer to fp(7d) for more details on the Fibre Channel
44 port driver.
45 The values returned by the driver in the DL_INFO_ACK primitive in
48 response to a DL_INFO_REQ from the user are as follows:
49 o Maximum SDU is 65280 (defined in RFC 2625).
51 o Minimum SDU is 0.
53 o DLSAP address length is 8.
55 o MAC type is DL_ETHER.
57 o SAP length is -2.
59 o Service mode is DL_CLDLS.
61 o Optional quality of service (QOS) fields are set to 0.
63 o Provider style is DL_STYLE2.
65 o Provider version is DL_VERSION_2.
67 o Broadcast address value is 0xFFFFFFFF.
69 Once in DL_ATTACHED state, the user must send a DL_BIND_REQ to asso‐
72 ciate a particular SAP (Service Access Point) with the stream. The fcip
73 driver DLSAP address format consists of the 6-byte physical address
74 component followed immediately by the 2-byte SAP component producing
75 an 8-byte DLSAP address. Applications should not be programmed to use
76 this implementation-specific DLSAP address format, but use information
77 returned in the DL_INFO_ACK primitive to compose and decompose DLSAP
78 addresses. The SAP length, full DLSAP length, and SAP/physical order‐
79 ing are included within the DL_INFO_ACK. The physical address length
80 is the full DLSAP address length minus the SAP length. The physical
81 address length can also be computed by issuing the DL_PHYS_ADDR_REQ
82 primitive to obtain the current physical address associated with the
83 stream.
84 Once in the DL_BOUND state, the user can transmit frames on the fibre
87 by sending DL_UNITDATA_REQ messages to the fcip driver. The fcip
88 driver will route received frames up any of the open and bound
89 streams having a SAP which matches the received frame's SAP type as
90 DL_UNITDATA_IND messages. Received Fibre Channel frames are duplicated
91 and routed up multiple open streams if necessary. The DLSAP address
92 contained within the DL_UNITDATA_REQ and DL_UNITDATA_IND messages con‐
93 sists of both the SAP (type) and physical address (WorldWideName) com‐
94 ponents.
95 Other Primitives
97 In Fibre Channel, multicasting is defined as an optional service for
98 Fibre Channel classes three and six only. If required, the Fibre Chan‐
99 nel broadcast service can be used for multicasting. The RFC 2625 speci‐
100 fication does not support IP multicasting or promiscuous mode.
101 fcip Fibre Channel ELS
103 The fcip driver will use the FARP Fibre Channel Extended Link Service
104 (ELS), where supported, to resolve WorldWide Names (MAC address) to FC
105 Port Identifiers(Port_ID). The fcip driver also supports InARP to
106 resolve WorldWide Name and Port_ID to an IP address.
107
109 /dev/fcip fcip character-special device
110 /kernel/drv/fcip 32-bit ELF kernel driver (x86)
113 /kernel/drv/amd64/fcip 64-bit ELF kernel driver (x86)
116 /kernel/drv/sparcv9/fcip 64-bit ELF kernel driver (SPARC)
119 /kernel/drv/fcip.conf fcip driver configuration file
122
125 See attributes(5) for descriptions of the following attributes:
126 ┌─────────────────────────────┬─────────────────────────────┐
131 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
132 ├─────────────────────────────┼─────────────────────────────┤
133 │Architecture │SPARC │
134 ├─────────────────────────────┼─────────────────────────────┤
135 │Availability │SUNWfcip │
136 └─────────────────────────────┴─────────────────────────────┘
137
139 netstat(1M), prtconf(1M), driver.conf(4), fp(7d), dlpi(7P)
140 Writing Device Drivers
143 IP and ARP over Fibre Channel, RFC 2625 M. Rajagopal, R. Bhagwat, W.
146 Rickard. Gadzoox Networks, June 1999
147 ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-
150 PH)
151 ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
154
156 If you use a Fibre Channel adapter with two or more ports that each
157 share a common Node WorldWideName, the fcip driver will likely attach
158 to the first port on the adapter.
159 RFC 2625 requires that both source and destination WorldWideNames have
162 their 4 bit NAA identifiers set to binary '0001,' indicating that an
163 IEEE 48-bit MAC address is contained in the lower 48 bits of the net‐
164 work address fields. For additional details, see the RFC 2625 specifi‐
165 cation.
166SunOS 5.11 18 Oct 2004 fcip(7D)