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
3 Click Storage Adapters.
All storage adapters installed on the host are listed under Storage Adapters.
4 Select the adapter from the list and click the Devices tab.
Storage devices that the host can access through the adapter are displayed.
Understanding Storage Device Naming
Each storage device, or LUN, is identied by several names.
Device Identifiers
Depending on the type of storage, the ESXi host uses dierent algorithms and conventions to generate an
identier for each storage device.
SCSI INQUIRY
identifiers.
The host uses the SCSI INQUIRY command to query a storage device and
uses the resulting data, in particular the Page 83 information, to generate a
unique identier. Device identiers that are based on Page 83 are unique
across all hosts, persistent, and have one of the following formats:
n
naa.number
n
t10.number
n
eui.number
These formats follow the T10 commiee standards. See the SCSI-3
documentation on the T10 commiee Web site.
Path-based identifier.
When the device does not provide the Page 83 information, the host
generates an mpx.path name, where path represents the rst path to the
device, for example, mpx.vmhba1:C0:T1:L3. This identier can be used in the
same way as the SCSI INQUIRY identies.
The mpx. identier is created for local devices on the assumption that their
path names are unique. However, this identier is neither unique nor
persistent and could change after every boot.
Typically, the path to the device has the following format:
vmhbaAdapter:CChannel:TTarget:LLUN
n
vmhbaAdapter is the name of the storage adapter. The name refers to the
physical adapter on the host, not to the SCSI controller used by the
virtual machines.
n
CChannel is the storage channel number.
Software iSCSI adapters and dependent hardware adapters use the
channel number to show multiple paths to the same target.
n
TTarget is the target number. Target numbering is determined by the
host and might change if the mappings of targets visible to the host
change. Targets that are shared by dierent hosts might not have the
same target number.
n
LLUN is the LUN number that shows the position of the LUN within the
target. The LUN number is provided by the storage system. If a target
has only one LUN, the LUN number is always zero (0).
For example, vmhba1:C0:T3:L1 represents LUN1 on target 3 accessed through
the storage adapter vmhba1 and channel 0.
Chapter 13 Managing Storage Devices
VMware, Inc. 123