
Table 3: LPFC.conf Parameters (Continued)
| Property Name | Scope | Default | Min | Max | Dynamic | Comments | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Controller | 0 | 0=Off | 1=On | Yes | This variable controls if I/O | |
| 
 | Specific | 
 | 
 | 
 | 
 | errors are held by the driver if | 
| 
 | 
 | 
 | 
 | 
 | 
 | a FCP device on the SAN | 
| 
 | 
 | 
 | 
 | 
 | 
 | disappears. If set, I/O errors | 
| 
 | 
 | 
 | 
 | 
 | 
 | will be held until the device | 
| 
 | 
 | 
 | 
 | 
 | 
 | returns back to the SAN | 
| 
 | 
 | 
 | 
 | 
 | 
 | (potentially indefinitely). This | 
| 
 | 
 | 
 | 
 | 
 | 
 | driver property is ignored, if | 
| 
 | 
 | 
 | 
 | 
 | 
 | SCSI commands are issued in | 
| 
 | 
 | 
 | 
 | 
 | 
 | polled mode. The upper layer | 
| 
 | 
 | 
 | 
 | 
 | 
 | may retry the command once | 
| 
 | 
 | 
 | 
 | 
 | 
 | the error is returned. | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Controller | 30 | 0 | 255 | Yes | This variable controls how | |
| 
 | Specific | 
 | 
 | 
 | 
 | long I/O will be held by the | 
| 
 | 
 | 
 | 
 | 
 | 
 | driver if a device on the SAN | 
| 
 | 
 | 
 | 
 | 
 | 
 | disappears. If set, I/O will be | 
| 
 | 
 | 
 | 
 | 
 | 
 | held for the specified number | 
| 
 | 
 | 
 | 
 | 
 | 
 | of seconds. If the device does | 
| 
 | 
 | 
 | 
 | 
 | 
 | not appear on the SAN before | 
| 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | driver will fail all held I/O and | 
| 
 | 
 | 
 | 
 | 
 | 
 | mark the device as | 
| 
 | 
 | 
 | 
 | 
 | 
 | unavailable. The upper layer | 
| 
 | 
 | 
 | 
 | 
 | 
 | may retry the command once | 
| 
 | 
 | 
 | 
 | 
 | 
 | the error is returned. | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Controller | 128 | 64 | 4096 | No | This variable specifies the | |
| 
 | Specific | 
 | 
 | 
 | 
 | number of command buffers | 
| 
 | 
 | 
 | 
 | 
 | 
 | to allocate. These buffers are | 
| 
 | 
 | 
 | 
 | 
 | 
 | used for FC Extended Link | 
| 
 | 
 | 
 | 
 | 
 | 
 | Services (ELS), and one for | 
| 
 | 
 | 
 | 
 | 
 | 
 | each FCP command issued in | 
| 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | queue lots of FCP commands | 
| 
 | 
 | 
 | 
 | 
 | 
 | to the HBA, then increase | 
| 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | performance. These buffers | 
| 
 | 
 | 
 | 
 | 
 | 
 | consume physical memory | 
| 
 | 
 | 
 | 
 | 
 | 
 | and are also used by the | 
| 
 | 
 | 
 | 
 | 
 | 
 | device driver to process loop | 
| 
 | 
 | 
 | 
 | 
 | 
 | initialization and  | 
| 
 | 
 | 
 | 
 | 
 | 
 | activities. Important: The | 
| 
 | 
 | 
 | 
 | 
 | 
 | driver must always be | 
| 
 | 
 | 
 | 
 | 
 | 
 | configured with at least | 
| 
 | 
 | 
 | 
 | 
 | 
 | several dozen ELS command | 
| 
 | 
 | 
 | 
 | 
 | 
 | buffers; Emulex recommends | 
| 
 | 
 | 
 | 
 | 
 | 
 | at least 128. | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| The HBAnyware Utility User Manual | Page 71 | 
