vSphere Storage - ESXi 5.1 - Documentation - VMware
vSphere Storage - ESXi 5.1 - Documentation - VMware
vSphere Storage - ESXi 5.1 - Documentation - VMware
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>vSphere</strong> <strong>Storage</strong><br />
Configuring Advanced Parameters for iSCSI<br />
You might need to configure additional parameters for your iSCSI initiators. For example, some iSCSI storage<br />
systems require ARP (Address Resolution Protocol) redirection to move iSCSI traffic dynamically from one<br />
port to another. In this case, you must activate ARP redirection on your host.<br />
The following table lists advanced iSCSI parameters that you can configure using the <strong>vSphere</strong> Client and the<br />
<strong>vSphere</strong> Web Client. In addition, you can use the <strong>vSphere</strong> CLI commands to configure some of the advanced<br />
parameters. For information, see the Getting Started with <strong>vSphere</strong> Command-Line Interfaces documentation.<br />
IMPORTANT Do not make any changes to the advanced iSCSI settings unless you are directed by <strong>VMware</strong><br />
support or <strong>Storage</strong> Vendors.<br />
Table 11-5. Additional Parameters for iSCSI Initiators<br />
Advanced Parameter Description Configurable On<br />
Header Digest Increases data integrity. When header digest is enabled, the system<br />
performs a checksum over each iSCSI Protocol Data Unit’s (PDU’s)<br />
header part and verifies using the CRC32C algorithm.<br />
Data Digest Increases data integrity. When data digest is enabled, the system<br />
performs a checksum over each PDU's data part and verifies using<br />
the CRC32C algorithm.<br />
Maximum<br />
Outstanding R2T<br />
NOTE Systems that use Intel Nehalem processors offload the iSCSI<br />
digest calculations for software iSCSI, thus reducing the impact on<br />
performance.<br />
Defines the R2T (Ready to Transfer) PDUs that can be in transition<br />
before an acknowledge PDU is received.<br />
First Burst Length Specifies the maximum amount of unsolicited data an iSCSI initiator<br />
can send to the target during the execution of a single SCSI command,<br />
in bytes.<br />
Maximum Burst<br />
Length<br />
Maximum Receive<br />
Data Segment Length<br />
Session Recovery<br />
Timeout<br />
Maximum SCSI data payload in a Data-In or a solicited Data-Out<br />
iSCSI sequence, in bytes.<br />
Maximum data segment length, in bytes, that can be received in an<br />
iSCSI PDU.<br />
Specifies the amount of time, in seconds, that can lapse while a session<br />
recovery is performed. If the timeout exceeds its limit, the iSCSI<br />
initiator terminates the session.<br />
No-Op Interval Specifies the time interval, in seconds, between NOP-Out requests<br />
sent from your iSCSI initiator to an iSCSI target. The NOP-Out<br />
requests serve as the ping mechanism to verify that a connection<br />
between the iSCSI initiator and the iSCSI target is active.<br />
No-Op Timeout Specifies the amount of time, in seconds, that can lapse before your<br />
host receives a NOP-In message. The message is sent by the iSCSI<br />
target in response to the NOP-Out request. When the no-op timeout<br />
limit is exceeded, the initiator terminates the current session and starts<br />
a new one.<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
Software iSCSI<br />
Dependent Hardware<br />
iSCSI<br />
108 <strong>VMware</strong>, Inc.
Change language