
Table 3: LPFC.conf Parameters (Continued)
| Property Name | Scope | Default | Min | Max | Dynamic | Comments | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Global | Inactive | N/A | N/A | No | Setup persistent FCP | |
| 
 | 
 | 
 | 
 | 
 | 
 | bindings based on a target | 
| 
 | 
 | 
 | 
 | 
 | 
 | device’s WWNN. This binding | 
| 
 | 
 | 
 | 
 | 
 | 
 | guarantees that target | 
| 
 | 
 | 
 | 
 | 
 | 
 | assignments will be preserved | 
| 
 | 
 | 
 | 
 | 
 | 
 | between reboots. The format | 
| 
 | 
 | 
 | 
 | 
 | 
 | for a bind entry is | 
| 
 | 
 | 
 | 
 | 
 | 
 | “NNNNNNNNNNNNNNNN:lpf | 
| 
 | 
 | 
 | 
 | 
 | 
 | cXtY” where | 
| 
 | 
 | 
 | 
 | 
 | 
 | NNNNNNNNNNNNNNNN is a | 
| 
 | 
 | 
 | 
 | 
 | 
 | 16 digit representation of the | 
| 
 | 
 | 
 | 
 | 
 | 
 | targets WorldWide Node | 
| 
 | 
 | 
 | 
 | 
 | 
 | Name, X is the driver instance | 
| 
 | 
 | 
 | 
 | 
 | 
 | number and Y is the target | 
| 
 | 
 | 
 | 
 | 
 | 
 | assignment. Multiple entries | 
| 
 | 
 | 
 | 
 | 
 | 
 | must be separated by a | 
| 
 | 
 | 
 | 
 | 
 | 
 | comma (,) with the last entry | 
| 
 | 
 | 
 | 
 | 
 | 
 | terminated with a  | 
| 
 | 
 | 
 | 
 | 
 | 
 | (;). A sample entry follows: | 
| 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | WWNN="20000020370c396f:l | 
| 
 | 
 | 
 | 
 | 
 | 
 | pfc1t0", | 
| 
 | 
 | 
 | 
 | 
 | 
 | "20000020370c27f7:lpfc0t2"; | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Global | Inactive | N/A | N/A | No | Setup persistent FCP | |
| 
 | 
 | 
 | 
 | 
 | 
 | bindings based on a target | 
| 
 | 
 | 
 | 
 | 
 | 
 | device’s WWPN. This binding | 
| 
 | 
 | 
 | 
 | 
 | 
 | guarantees that target | 
| 
 | 
 | 
 | 
 | 
 | 
 | assignments will be preserved | 
| 
 | 
 | 
 | 
 | 
 | 
 | between reboots. The format | 
| 
 | 
 | 
 | 
 | 
 | 
 | for a bind entry is | 
| 
 | 
 | 
 | 
 | 
 | 
 | “NNNNNNNNNNNNNNNN:lpf | 
| 
 | 
 | 
 | 
 | 
 | 
 | cXtY” where | 
| 
 | 
 | 
 | 
 | 
 | 
 | NNNNNNNNNNNNNNNN is a | 
| 
 | 
 | 
 | 
 | 
 | 
 | 16 digit representation of the | 
| 
 | 
 | 
 | 
 | 
 | 
 | targets WorldWide Port | 
| 
 | 
 | 
 | 
 | 
 | 
 | Name, X is the driver instance | 
| 
 | 
 | 
 | 
 | 
 | 
 | number and Y is the target | 
| 
 | 
 | 
 | 
 | 
 | 
 | assignment. Multiple entries | 
| 
 | 
 | 
 | 
 | 
 | 
 | must be separated by a | 
| 
 | 
 | 
 | 
 | 
 | 
 | comma (,) with the last entry | 
| 
 | 
 | 
 | 
 | 
 | 
 | terminated with a  | 
| 
 | 
 | 
 | 
 | 
 | 
 | (;). A sample entry follows: | 
| 
 | 
 | 
 | 
 | 
 | 
 | |
| 
 | 
 | 
 | 
 | 
 | 
 | WWPN="21000020370cf8263 | 
| 
 | 
 | 
 | 
 | 
 | 
 | :lpfc1t0"; | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| Controller | 3 | 2 | 3 | Yes | The LPFC driver is capable of | |
| 
 | Specific | 
 | 
 | 
 | 
 | transmitting FCP data in | 
| 
 | 
 | 
 | 
 | 
 | 
 | Class2 or Class 3. The LPFC | 
| 
 | 
 | 
 | 
 | 
 | 
 | driver defaults to using Class | 
| 
 | 
 | 
 | 
 | 
 | 
 | 3 transmission. | 
| 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
| The HBAnyware Utility User Manual | Page 67 | 
