
Table 3: LPFC.conf Parameters (Continued)
Property Name | Scope | Default | Min | Max | Dynamic | Comments |
|
|
|
|
|
|
|
|
|
|
|
|
| |
topology | Controller | 0x0 | 0x0=loop , then | No | This variable controls the FC | |
| Specific |
| P2P |
|
| topology expected by LPFC at |
|
|
| 0x2=P2P only |
| boot time. FC offers | |
|
|
| 0x4=loop only |
| point, fabric, and arbitrated | |
|
|
| 0x6=P2P, then |
| loop topologies.To make the | |
|
|
| loop |
|
| HBA operate as an N_Port, |
|
|
|
|
|
| select |
|
|
|
|
|
| (used for N_Port to F_Port, |
|
|
|
|
|
| and N_Port to N_Port |
|
|
|
|
|
| connections). To make the |
|
|
|
|
|
| HBA operate in a FC loop as |
|
|
|
|
|
| an NL_Port, select loop mode |
|
|
|
|
|
| (used for private loop and |
|
|
|
|
|
| public loop topologies). The |
|
|
|
|
|
| driver will reject an attempt to |
|
|
|
|
|
| set the topology to a value not |
|
|
|
|
|
| in the above list. The auto- |
|
|
|
|
|
| topology settings 0 and 6 will |
|
|
|
|
|
| not work unless the HBA is |
|
|
|
|
|
| using firmware version 3.20 or |
|
|
|
|
|
| higher. |
|
|
|
|
|
|
|
Controller | 0 | 0=Off | 1=On | Yes | This variable controls the ELS | |
| Specific |
|
|
|
| command used for address |
|
|
|
|
|
| authentication during re- |
|
|
|
|
|
| discovery upon |
|
|
|
|
|
| ADISC is used, otherwise, |
|
|
|
|
|
| PLOGI is used. For |
|
|
|
|
|
| devices, the driver will always |
|
|
|
|
|
| use ADISC. For |
|
|
|
|
|
| due to a RSCN, the driver will |
|
|
|
|
|
| always use ADISC. |
|
|
|
|
|
|
|
Controller | 256 | 128 | 10,240 | No | This variable specifies the | |
| Specific |
|
|
|
| number of network packets |
|
|
|
|
|
| that can be queued or |
|
|
|
|
|
| outstanding at any time in the |
|
|
|
|
|
| driver. Increase this setting for |
|
|
|
|
|
| better IP performance under |
|
|
|
|
|
| heavy loading. |
|
|
|
|
|
|
|
The HBAnyware Utility User Manual | Page 73 |