Table 1: Storport Miniport Driver Parameters (Continued)
Parameter | Definitions | Activation | |
Requirement | |||
|
| ||
|
|
| |
LogErrors=n | LogErrors determine the minimum severity level required to enable | Dynamic | |
| entry of a logged error into the system event log. Errors are classified |
| |
| as severe, malfunction or command level. A severe error requires |
| |
| user intervention to correct a firmware or HBA problem. An invalid link |
| |
| speed selection is an example of a severe error. A malfunction error |
| |
| indicates that the system has problems, but user intervention is not |
| |
| required. An invalid fabric command type is an example of a |
| |
| malfunction error. A command level error: an object allocation failure |
| |
| is an example of a command error. |
| |
| If set to 0, all errors regardless of severity are logged. |
| |
| If set to 1, command level errors are logged. |
| |
| If set to 2, malfunction errors are logged. |
| |
| If set to 3, severe errors are logged. |
| |
| Value: 0 - 3 |
| |
| Default = 3 |
| |
|
|
| |
NetworkOption=n | NetworkOption controls whether IP over FC is disabled or enabled. |
| |
| A value of 1 will enable IP over FC and will allow first time installation |
| |
| or startup of the FC LAN driver. |
| |
| Value: 0 - 1 |
| |
| Default = 0 |
| |
|
|
| |
NodeTimeout=n | The node timer starts when a node (i.e. discovered target or initiator) | Dynamic | |
| becomes unavailable. If the node fails to become available before the |
| |
| NodeTimeout interval expires, the OS is notified so that any |
| |
| associated devices (if the node is a target) can be removed. If the |
| |
| node becomes available before NodeTimeout expires the timer is |
| |
| canceled and no notification is made. |
| |
| Value: 1 - 255 seconds or 0x0 - 0xFF (hex) |
| |
| Default = 30 (0x1E) |
| |
|
|
| |
QueueDepth=n | QueueDepth requests per LUN/target (see QueueTarget parameter). | Dynamic | |
| If you expect the number of outstanding I/Os per device to exceed 32, |
| |
| then you must increase to a value greater than the number of |
| |
| expected I/Os per device (up to a value of 254). If the QueueDepth |
| |
| value is set too low, a performance degradation can occur due to |
| |
| driver throttling of its device queue. |
| |
| Value: 1 - 254 or 0x1 - 0xFE (hex) |
| |
| Default = 32 (0x20) |
| |
|
|
| |
QueueTarget=n | QueueTarget controls I/O depth limiting on a per target or per LUN | Dynamic | |
| basis. |
| |
| If set to 0 = depth limitation is applied to individual LUNs. |
| |
| If set to 1 = depth limitation is applied across the entire target. |
| |
| Value: 0 |
| |
| Default = 0 (0x0) |
| |
|
|
|
The HBAnyware Utility User Manual | Page 57 |
