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
The 16-hexadecimal digits are text representations of a 64-bit number of an IEEE EUI (extended unique
identier) format. The top 24 bits are a company ID that IEEE registers with a particular company. The lower
40 bits are assigned by the entity holding that company ID and must be unique.
iSCSI Initiators
To access iSCSI targets, your host uses iSCSI initiators. The initiators transport SCSI requests and responses,
encapsulated into the iSCSI protocol, between the host and the iSCSI target.
Your host supports dierent types of initiators.
For information on conguring and using iSCSI adapters, see Chapter 10, “Conguring iSCSI Adapters and
Storage,” on page 69.
Software iSCSI Adapter
A software iSCSI adapter is a VMware code built into the VMkernel. It allows your host to connect to the
iSCSI storage device through standard network adapters. The software iSCSI adapter handles iSCSI
processing while communicating with the network adapter. With the software iSCSI adapter, you can use
iSCSI technology without purchasing specialized hardware.
Hardware iSCSI Adapter
A hardware iSCSI adapter is a third-party adapter that ooads iSCSI and network processing from your
host. Hardware iSCSI adapters are divided into categories.
Dependent Hardware
iSCSI Adapter
Depends on VMware networking, and iSCSI conguration and management
interfaces provided by VMware.
This type of adapter can be a card that presents a standard network adapter
and iSCSI ooad functionality for the same port. The iSCSI ooad
functionality depends on the host's network conguration to obtain the IP,
MAC, and other parameters used for iSCSI sessions. An example of a
dependent adapter is the iSCSI licensed Broadcom 5709 NIC.
Independent Hardware
iSCSI Adapter
Implements its own networking and iSCSI conguration and management
interfaces.
An example of an independent hardware iSCSI adapter is a card that either
presents only iSCSI ooad functionality or iSCSI ooad functionality and
standard NIC functionality. The iSCSI ooad functionality has independent
conguration management that assigns the IP, MAC, and other parameters
used for the iSCSI sessions. An example of a independent adapter is the
QLogic QLA4052 adapter.
Hardware iSCSI adapters might need to be licensed. Otherwise, they will not appear in the client or vSphere
CLI. Contact your vendor for licensing information.
Establishing iSCSI Connections
In the ESXi context, the term target identies a single storage unit that your host can access. The terms
storage device and LUN describe a logical volume that represents storage space on a target. Typically, the
terms device and LUN, in the ESXi context, mean a SCSI volume presented to your host from a storage
target and available for formaing.
Dierent iSCSI storage vendors present storage to servers in dierent ways. Some vendors present multiple
LUNs on a single target, while others present multiple targets with one LUN each. While the way the
storage is used by ESXi is similar, the way the information is presented through administrative tools is
dierent.
Chapter 9 Using ESXi with iSCSI SAN
VMware, Inc. 65