You might need to configure additional parameters for iSCSI initiators on your ESXi host. For example, some iSCSI storage systems require ARP (Address Resolution Protocol) redirection to move iSCSI traffic dynamically from one port to another. In this case, you must activate the ARP redirection on your host.
The following table lists advanced iSCSI parameters that you can configure using the vSphere Client. In addition, you can use the vSphere CLI commands to configure some of the advanced parameters. For information, see the Getting Started with ESXCLI documentation.
Depending on the type of your adapters, certain parameters might not be available.
|Header Digest||Increases data integrity. When the header digest parameter is enabled, the system performs a checksum over each header part of the iSCSI Protocol Data Unit (PDU). The system verifies the data using the CRC32C algorithm.|
|Data Digest||Increases data integrity. When the data digest parameter is enabled, the system performs a checksum over each PDU data part. The system verifies the data using the CRC32C algorithm.
Note: Systems that use the Intel Nehalem processors offload the iSCSI digest calculations for software iSCSI. This offload helps to reduce the impact on performance.
|ErrorRecoveryLevel||iSCSI Error Recovery Level (ERL) value that the iSCSI initiator on the host negotiates during a login.|
|LoginRetryMax||Maximum number of times the ESXi iSCSI initiator attempts to log into a target before ending the attempts.|
|MaxOutstandingR2T||Defines the R2T (Ready to Transfer) PDUs that can be in transition before an acknowledge PDU is received.|
|FirstBurstLength||Specifies the maximum amount of unsolicited data an iSCSI initiator can send to the target during the execution of a single SCSI command, in bytes.|
|MaxBurstLength||Maximum SCSI data payload in a Data-In or a solicited Data-Out iSCSI sequence, in bytes.|
|MaxRecvDataSegLength||Maximum data segment length, in bytes, that can be received in an iSCSI PDU.|
|MaxCommands||Maximum SCSI commands that can be queued on the iSCSI adapter.|
|DefaultTimeToWait||Minimum time in seconds to wait before attempting a logout or an active task reassignment after an unexpected connection termination or reset.|
|DefautTimeToRetain||Maximum time in seconds, during which reassigning the active task is still possible after a connection termination or reset.|
|LoginTimeout||Time in seconds the initiator will wait for the login response to finish.|
|LogoutTimeout||Time in seconds initiator will wait to get a response for Logout request PDU.|
|RecoveryTimeout||Specifies the amount of time, in seconds, that can lapse while a session recovery is performed. If the timeout exceeds its limit, the iSCSI initiator ends the session.|
|No-Op Interval||Specifies the time interval, in seconds, between NOP-Out requests sent from your iSCSI initiator to an iSCSI target. The NOP-Out requests serve as the ping mechanism to verify that a connection between the iSCSI initiator and the iSCSI target is active.|
|No-Op Timeout||Specifies the amount of time, in seconds, that can lapse before your host receives a NOP-In message. The iSCSI target sends the message in response to the NOP-Out request. When the no-op timeout limit is exceeded, the initiator ends the current session and starts a new one.|
|ARP Redirect||With this parameter enabled, storage systems can move iSCSI traffic dynamically from one port to another. Storage systems that perform array-based failovers require the ARP parameter.|
|Delayed ACK||With this parameter enabled, storage systems can delay an acknowledgment of received data packets.|