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
What to do next
Although the dependent iSCSI adapter is enabled by default, to make it functional, you must set up
networking for the iSCSI trac and bind the adapter to the appropriate VMkernel iSCSI port. You then
congure discovery addresses and CHAP parameters.
Modify General Properties for iSCSI Adapters
You can change the default iSCSI name and alias assigned to your iSCSI adapters. For the for independent
hardware iSCSI adapters, you can also change the default IP seings.
I When you modify any default properties for your iSCSI adapters, make sure to correctly
format their names and IP addresses.
Prerequisites
Required privilege: Host ..Storage Partition
Procedure
1 Browse to the host in the vSphere Web Client navigator.
2 Click the Manage tab, and click Storage.
3 Click Storage Adapters, and select the adapter (vmhba#) to congure.
4 Under Adapter Details, click the Properties tab and click Edit in the General panel.
5 To change the default iSCSI name for your adapter, enter the new name.
Make sure the name you enter is worldwide unique and properly formaed or some storage devices
might not recognize the iSCSI adapter.
6 (Optional) Enter the iSCSI alias.
The alias is a name that you use to identify the iSCSI adapter.
If you change the iSCSI name, it will be used for new iSCSI sessions. For existing sessions, new seings will
not be used until logout and re-login.
Determine Association Between iSCSI and Network Adapters
You create network connections to bind dependent iSCSI and physical network adapters. To create the
connections correctly, you must determine the name of the physical NIC with which the dependent
hardware iSCSI adapter is associated.
Prerequisites
In the vSphere Web Client, browse to the dependent hardware iSCSI adapter (vmhba#). See “View
Dependent Hardware iSCSI Adapters,” on page 75.
Procedure
1 Select the iSCSI adapter (vmhba#) and click the Network Port Binding tab under Adapter Details.
2 Click Add.
The network adapter (vmnic#) that corresponds to the dependent iSCSI adapter is listed in the Physical
Network Adapter column.
What to do next
If the VMkernel Adapter column is empty, create a VMkernel adapter (vmk#) for the physical network
adapter (vmnic#) and then bind them to the associated dependent hardware iSCSI. See “Seing Up iSCSI
Network,” on page 88.
vSphere Storage
76 VMware, Inc.