6.0.1
Table Of Contents
- vSphere Storage
- Contents
- About vSphere Storage
- Updated Information
- Introduction to Storage
- Overview of Using ESXi with a SAN
- Using ESXi with Fibre Channel SAN
- Configuring Fibre Channel Storage
- Configuring Fibre Channel over Ethernet
- Booting ESXi from Fibre Channel SAN
- Booting ESXi with Software FCoE
- Best Practices for Fibre Channel Storage
- Using ESXi with iSCSI SAN
- Configuring iSCSI Adapters and Storage
- ESXi iSCSI SAN Requirements
- ESXi iSCSI SAN Restrictions
- Setting LUN Allocations for iSCSI
- Network Configuration and Authentication
- Set Up Independent Hardware iSCSI Adapters
- About Dependent Hardware iSCSI Adapters
- Dependent Hardware iSCSI Considerations
- Configure Dependent Hardware iSCSI Adapters
- About the Software iSCSI Adapter
- Modify General Properties for iSCSI Adapters
- Setting Up iSCSI Network
- Using Jumbo Frames with iSCSI
- Configuring Discovery Addresses for iSCSI Adapters
- Configuring CHAP Parameters for iSCSI Adapters
- Configuring Advanced Parameters for iSCSI
- iSCSI Session Management
- Booting from iSCSI SAN
- Best Practices for iSCSI Storage
- Managing Storage Devices
- Storage Device Characteristics
- Understanding Storage Device Naming
- Storage Refresh and Rescan Operations
- Identifying Device Connectivity Problems
- Edit Configuration File Parameters
- Enable or Disable the Locator LED on Storage Devices
- Working with Flash Devices
- About VMware vSphere Flash Read Cache
- Working with Datastores
- Understanding VMFS Datastores
- Understanding Network File System Datastores
- Creating Datastores
- Managing Duplicate VMFS Datastores
- Upgrading VMFS Datastores
- Increasing VMFS Datastore Capacity
- Administrative Operations for Datastores
- Set Up Dynamic Disk Mirroring
- Collecting Diagnostic Information for ESXi Hosts on a Storage Device
- Checking Metadata Consistency with VOMA
- Configuring VMFS Pointer Block Cache
- Understanding Multipathing and Failover
- Raw Device Mapping
- Working with Virtual Volumes
- Virtual Machine Storage Policies
- Upgrading Legacy Storage Profiles
- Understanding Virtual Machine Storage Policies
- Working with Virtual Machine Storage Policies
- Creating and Managing VM Storage Policies
- Storage Policies and Virtual Machines
- Default Storage Policies
- Assign Storage Policies to Virtual Machines
- Change Storage Policy Assignment for Virtual Machine Files and Disks
- Monitor Storage Compliance for Virtual Machines
- Check Compliance for a VM Storage Policy
- Find Compatible Storage Resource for Noncompliant Virtual Machine
- Reapply Virtual Machine Storage Policy
- Filtering Virtual Machine I/O
- VMkernel and Storage
- Storage Hardware Acceleration
- Hardware Acceleration Benefits
- Hardware Acceleration Requirements
- Hardware Acceleration Support Status
- Hardware Acceleration for Block Storage Devices
- Hardware Acceleration on NAS Devices
- Hardware Acceleration Considerations
- Storage Thick and Thin Provisioning
- Using Storage Providers
- Using vmkfstools
- vmkfstools Command Syntax
- vmkfstools Options
- -v Suboption
- File System Options
- Virtual Disk Options
- Supported Disk Formats
- Creating a Virtual Disk
- Example for Creating a Virtual Disk
- Initializing a Virtual Disk
- Inflating a Thin Virtual Disk
- Removing Zeroed Blocks
- Converting a Zeroedthick Virtual Disk to an Eagerzeroedthick Disk
- Deleting a Virtual Disk
- Renaming a Virtual Disk
- Cloning or Converting a Virtual Disk or RDM
- Example for Cloning or Converting a Virtual Disk
- Migrate Virtual Machines Between DifferentVMware Products
- Extending a Virtual Disk
- Upgrading Virtual Disks
- Creating a Virtual Compatibility Mode Raw Device Mapping
- Example for Creating a Virtual Compatibility Mode RDM
- Creating a Physical Compatibility Mode Raw Device Mapping
- Listing Attributes of an RDM
- Displaying Virtual Disk Geometry
- Checking and Repairing Virtual Disks
- Checking Disk Chain for Consistency
- Storage Device Options
- Index
Configuring Advanced Parameters for iSCSI
You might need to congure additional parameters for your iSCSI initiators. For example, some iSCSI
storage systems require ARP (Address Resolution Protocol) redirection to move iSCSI trac dynamically
from one port to another. In this case, you must activate ARP redirection on your host.
The following table lists advanced iSCSI parameters that you can congure using the vSphere Web Client. In
addition, you can use the vSphere CLI commands to congure some of the advanced parameters. For
information, see the Geing Started with vSphere Command-Line Interfaces documentation.
I Do not make any changes to the advanced iSCSI seings unless you are directed by VMware
support or Storage Vendors.
Table 10‑5. Additional Parameters for iSCSI Initiators
Advanced Parameter Description Configurable On
Header Digest Increases data integrity. When header digest is enabled, the system
performs a checksum over each iSCSI Protocol Data Unit’s (PDU’s)
header part and veries using the CRC32C algorithm.
Software iSCSI
Dependent Hardware
iSCSI
Data Digest Increases data integrity. When data digest is enabled, the system
performs a checksum over each PDU's data part and veries using
the CRC32C algorithm.
N Systems that use Intel Nehalem processors ooad the iSCSI
digest calculations for software iSCSI, thus reducing the impact on
performance.
Software iSCSI
Dependent Hardware
iSCSI
Maximum
Outstanding R2T
Denes the R2T (Ready to Transfer) PDUs that can be in transition
before an acknowledge PDU is received.
Software iSCSI
Dependent Hardware
iSCSI
First Burst Length Species the maximum amount of unsolicited data an iSCSI
initiator can send to the target during the execution of a single SCSI
command, in bytes.
Software iSCSI
Dependent Hardware
iSCSI
Maximum Burst
Length
Maximum SCSI data payload in a Data-In or a solicited Data-Out
iSCSI sequence, in bytes.
Software iSCSI
Dependent Hardware
iSCSI
Maximum Receive
Data Segment Length
Maximum data segment length, in bytes, that can be received in an
iSCSI PDU.
Software iSCSI
Dependent Hardware
iSCSI
Session Recovery
Timeout
Species the amount of time, in seconds, that can lapse while a
session recovery is performed. If the timeout exceeds its limit, the
iSCSI initiator terminates the session.
Software iSCSI
Dependent Hardware
iSCSI
No-Op Interval Species 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.
Software iSCSI
Dependent Hardware
iSCSI
No-Op Timeout Species the amount of time, in seconds, that can lapse before your
host receives a NOP-In message. The message is sent by the iSCSI
target in response to the NOP-Out request. When the no-op timeout
limit is exceeded, the initiator terminates the current session and
starts a new one.
Software iSCSI
Dependent Hardware
iSCSI
vSphere Storage
102 VMware, Inc.