Configuring VSphere

2012 VMware Inc.
All rights reserved

Configuring and Managing Virtual Storage
Module 6
6-2
2012 VMware Inc. All rights reserved
VMware vSphere: Install, Configure, Manage Revision A
Course Introduction
Introduction to Virtualization
Creating Virtual Machines
VMware vCenter Server
Configuring and Managing Virtual Networks
Configuring and Managing vSphere Storage
Virtual Machine Management
Data Protection
Access and Authentication Control
Resource Management and Monitoring
High Availability and Fault Tolerance
Host Scalability
Patch Management
Installing VMware vSphere Components
You Are Here
6-3
Storage options give you the flexibility to set up your storage based
on your cost, performance, and manageability requirements.
Shared storage is useful for disaster recovery, high availability, and
moving virtual machines between hosts.
Importance
6-4
Lesson 1: Storage Concepts
Lesson 2: Configuring iSCSI Storage
Lesson 3: Configuring NAS/NFS Storage
Lesson 4: Fibre Channel SAN Storage
Lesson 5: VMFS Datastores
Lesson 6: VSA

Module Lessons
6-5
Lesson 1:
Storage Concepts
6-6
After this lesson, you should be able to do the following:
Describe VMware vSphere storage technologies and datastores.
Describe the storage device naming convention.
Learner Objectives
6-7
Storage Overview
storage
technology
datastore
types
FCoE
iSCSI
Fibre
Channel
direct
attached
file
system
NAS
NFS
VMware vSphere VMFS
VMware
vSphere
ESXi
hosts
6-8
Storage Protocol Overview
Storage
protocol
Supports
boot from
SAN
Supports
VMware
vSphere
vMotion
Supports
VMware
vSphere
High
Availability
(vSphere
HA)
Supports
VMware
vSphere
Distributed
Resource
Scheduler
(DRS)
Supports
raw device
mapping
(RDM)
Fibre
Channel

FCoE

iSCSI

NFS

DAS

6-9
A datastore is a logical storage
unit that can use disk space on
one physical device or span
several physical devices.
Types of datastores:
VMFS
NFS
Datastores are used to hold
virtual machine files, templates,
and ISO images.

Datastore
host host
datastore
6-10
VMFS-5:
Allows concurrent access to
shared storage
Can be dynamically expanded
Uses a 1MB block size, good for
storing large virtual disk files
Uses subblock addressing, good
for storing small files:
The subblock size is 8KB.
Provides on-disk, block-level
locking

VMFS-5
host host
VMFS datastore
6-11
NFS:
Is storage shared over the
network at the file system level
Supports NFS version 3 over
TCP/IP

NFS
host host
NFS datastore
6-12
Storage devices are identified in several ways:
SCSI ID Unique SCSI identifier
Canonical name The Network Address Authority ID is a unique logical
unit number (LUN) identifier, guaranteed to be persistent across
reboots.
In addition to NAA IDs, devices can also be identified with mpx or T10
identifiers.
Runtime name Uses the convention vmhbaN:C:T:L. This name is not
persistent through reboots.
Storage Device Naming Conventions
6-13
Viewing Storage Maps
target
HBA
LUN
6-14
Discuss vSphere storage needs with your storage administration
team, including:
LUN sizes
I/O bandwidth
I/O requests per second that a LUN is capable of
Disk cache parameters
Zoning and masking
Identical LUN presentation to each ESXi host
Active-active or active-passive arrays
Export properties for NFS datastores
Physical Storage Considerations
6-15
You should be able to do the following:
Describe vSphere storage technologies and datastores.
Describe the storage device naming convention.
Review of Learner Objectives
6-16
Lesson 2:
Configuring iSCSI Storage
6-17
Describe uses of IP storage with ESXi.
Describe iSCSI components and addressing.
Configure iSCSI initiators.
Learner Objectives
6-18
iSCSI Components
6-19
iSCSI Addressing
iSCSI target name:
iqn.1992-08.com.mycompany:stor1-47cf3c25
or
eui.fedcba9876543210
iSCSI alias: stor1
IP address: 192.168.36.101

iSCSI initiator name:
iqn.1998-01.com.vmware:train1-64ad4c29
or
eui.1234567890abcdef
iSCSI alias: train1
IP address: 192.168.36.88

6-20
iSCSI Initiators
6-21
To configure the iSCSI software initiator:
1. Configure a VMkernel port for accessing IP storage.
2. Enable the iSCSI software adapter.
3. Configure the iSCSI qualified name (IQN) and alias (if required)
4. Configure iSCSI software adapter properties, such as static/dynamic
discovery addresses and iSCSI port binding
5. Configure iSCSI security (Challenge Handshake Authentication
Protocol (CHAP)).
Configuring Software iSCSI
6-22
A VMkernel port must be created for ESXi to access software iSCSI.
The same port can be used to access NAS/NFS storage.

To optimize your vSphere networking setup:
Separate iSCSI networks from NAS/NFS networks.
Physical separation is preferred.
If physical separation is not possible, use VLANs.

ESXi Network Configuration for IP Storage
6-23
Two discovery methods are
supported:
Static
Dynamic (also known as
SendTargets)
The SendTargets response returns
IQN and all available IP addresses.
iSCSI Target-Discovery Methods
iSCSI target
192.168.36.101:3260
SendTargets
request
SendTargets
response
192.168.36.101:3260
6-24
iSCSI initiators use CHAP for
authentication purposes.
By default, CHAP is not configured.
ESXi supports two types of CHAP
authentication:
Unidirectional
Bidirectional:
Software iSCSI only
ESXi also supports per-target CHAP
authentication.
Software iSCSI only
Different credentials for each target

iSCSI Security: CHAP
Software iSCSI properties > General tab
Target
authenticates
host.
Host
authenticates
target.
6-25
To configure the iSCSI hardware initiator:
1. Install the iSCSI hardware adapter.
a. For independent hardware iSCSI adapters, verify properly formatted IP
address and IQN names.
b. For dependent hardware iSCSI adapters, determine the name of the
physical NIC associated with the adapter so that port binding is properly
configured.
2. Modify the iSCSI name and configure the iSCSI alias.
3. Configure iSCSI target addresses.
4. Configure iSCSI security (CHAP).

Configuring Hardware iSCSI
6-26
Hardware iSCSI:
Use two or more hardware iSCSI
adapters.
Software or dependent
hardware iSCSI:
Use multiple network interface
cards (NICs).
Connect each NIC to a separate
VMkernel port.
Associate VMkernel ports with
iSCSI initiator.
Multipathing with iSCSI Storage
Configure port binding in
the Properties window of
the iSCSI adapter.
6-27
Describe uses of IP storage with ESXi.
Describe iSCSI components and addressing.
Configure iSCSI initiators.
6-28
Lesson 3:
Configuring NAS/NFS Storage
6-29
Describe NFS components and addressing.
Create an NFS datastore.

Learner Objectives
6-30
NFS Components
directory to share
with the ESXi host
over the network
VMkernel port
defined on virtual
switch
ESXi host with
NIC mapped to
virtual switch
NAS device or a
server with
storage
6-31
Addressing and Access Control with NFS
192.168.81.72
VMkernel port
configured with
IP address
192.168.81.33
6-32
Create a VMkernel port:
For better performance and security, separate it from the iSCSI
network.
Provide the following information:
NFS server name (or IP address)
Folder on the NFS server, for example, /LUN1 and /LUN2
Whether to mount the NFS file system read-only:
Default is to mount read/write
NFS datastore name

Configuring an NFS Datastore
6-33
Viewing IP Storage Information
Datastores view > Storage Views tab
Hosts and Clusters view > Configuration tab > Storage link

6-34
Click the Storage link in the Configuration tab to unmount an NFS
datastore.
Unmounting or deleting an NFS datastore causes the files on the
datastore to become inaccessible.
Unmounting or Deleting an NFS Datastore
6-35
A recommended configuration for
NFS multipathing:
Configure one VMkernel port.
Use adapters attached to the same
physical switch to configure NIC
teaming.
Configure the NFS server with
multiple IP addresses.
IP addresses can be on the same
subnet.
To use multiple links, configure NIC
teams with the IP hash load-
balancing policy.
Multipathing and NFS Storage

NIC

NIC

physical
switch

ESXi host

vmnic0

vmnic1
6-36
In this lab, you will configure access to an iSCSI and NFS datastore.
1. Add a VMkernel port group to a standard virtual switch.
2. Configure the iSCSI software adapter.
Lab 6
6-37
In this lab, you will configure access to an iSCSI and NFS datastore.
1. Configure access to NFS datastores.
2. View iSCSI and NFS storage information.
Lab 7
6-38
Describe NFS components and addressing.
Create an NFS datastore.
6-39
Lesson 4:
Fibre Channel SAN Storage
6-40
Describe uses of Fibre Channel with ESXi.
Describe Fibre Channel components and addressing.
Access Fibre Channel storage.
Learner Objectives
6-41
ESXi supports:
16Gb Fibre Channel
Fibre Channel over Ethernet (FCoE)
Using Fibre Channel with ESXi
6-42
Fibre Channel SAN Components
6-43
Fibre Channel Addressing and Access Control
6-44
Install one or more supported Fibre Channel adapters in the ESXi host.
The Fibre Channel adapters are recognized by the host during the boot
sequence.

Accessing Fibre Channel Storage
6-45
The Storage Views tab provides
information about all SCSI adapters
and NAS mounts.
Viewing Fibre Channel Storage Information
6-46
FCoE Adapters
converged
network
adapter
network
driver
FC
driver
ESXi host
network
driver
software
FC
ESXi 5.x host
NIC
with FCoE
support
FCoE switch
hardware FCoE
software FCoE*
* New in vSphere 5.0
LAN
FC
SAN
10 Gigabit
Ethernet
Ethernet IP frames
to LAN devices
FC frames to FC
storage arrays
6-47
Step 1: Connect the VMkernel to
physical FCoE NICs that are installed on
your host.
The VLAN ID and the priority class are
discovered during FCoE initialization.
The priority class is not configured in
vSphere.
ESXi supports the maximum of four
network adapter ports used for software
FCoE.

Configuring Software FCoE: Create a VMkernel Port
Physical adapter: vmnic2
VMkernel label: FCoE-2
VLAN ID: 20
IP address: 172.17.12.150
Subnet mask: 255.255.255.0
VMkernel port
vmnic2
NIC with
FCoE support
6-48
Step 2: Add the software
FCoE adapter.
Configuring Software FCoE: Activate the Software FCoE Adapter
Select host > Configuration tab > Storage Adapters link > Add.
6-49
Multipathing enables continued
access to SAN LUNs if hardware
fails. It also provides load
balancing.
Multipathing with Fibre Channel
6-50
Multipathing with Software FCoE
VMkernel ports
vmnic2 vmnic3
VLAN ID: 20
IP address: 172.17.12.150
Subnet mask:
255.255.255.0
VLAN ID: 20
IP address: 172.17.12.151
Subnet mask:
255.255.255.0
NICs with
FCoE support
6-51
Describe uses of Fibre Channel with ESXi.
Describe Fibre Channel components and addressing.
Access Fibre Channel storage.
6-52
Lesson 5:
VMFS Datastores
6-53
Create a VMFS datastore.
Increase the size of a VMFS datastore.
Delete a VMFS datastore.
Learner Objectives
6-54
Use VMFS datastores whenever possible:
VMFS is optimized for storing and accessing large files.
A VMFS datastore can have a maximum volume size of 64TB.
NFS datastores are good for storing virtual machines. But some
functions are not supported.
Use RDMs if the following conditions are true of your virtual machine:
It is taking Storage Array level snapshots.
It is clustered to a physical machine.
It has large amounts of data that you do not want to convert into a virtual
disk.
Using a VMFS Datastore with ESXi
6-55
To create a VMFS datastore, start the Add Storage wizard:
1. Select the storage type Disk/LUN.
2. Select an available LUN.

3. Specify a datastore name.
4. Specify the datastore size: use full or partial LUN.

Creating a VMFS Datastore
6-56
Click the Storage link in the Configuration tab
Viewing VMFS Datastores
6-57
Right-click the datastore in the hosts Summary tab, or click the
Storage link in the Configuration tab.
Browsing Datastore Contents
6-58
An overcommitted datastore can occur when the total provisioned
space of thin-provisioned disks is greater than the size of the
datastore.
Actively monitor your datastore capacity:
Alarms assist through notifications:
Datastore disk overallocation
Virtual machine disk usage
Use reporting to view space usage.
Actively manage your datastore capacity:
Increase datastore capacity when necessary.
Use VMware vSphere Storage vMotion to mitigate space usage
issues on a particular datastore.
Managing Overcommitted Datastores
6-59
Increase a VMFS datastores
size to give it more space or
possibly to improve
performance.
Two ways to dynamically
increase the size of a VMFS
datastore:
Add an extent (LUN).
Expand the datastore within its
extent.
Increasing the Size of a VMFS Datastore
6-60
Comparing Methods for Increasing VMFS Datastore Size
Adding an extent to the
datastore
Expanding the
datastore in the extent
Virtual machine power state On On
SAN administrator tasks
Add one or more LUNs
(extents).
Increase the size of the
LUN.
Limits
A datastore can have up to
32 LUNs (extents), with
each extent up to 64TB
A LUN can be expanded
any number of times, up to
64TB.
6-61
In general, before making any changes to your storage allocation:
Perform a rescan to ensure that all hosts see the most current storage.
Quiesce I/O on all disks involved.
Record the unique identifier (for example, the NAA ID of the volume
that you want to expand).
Before Increasing the Size of a VMFS Datastore
6-62
Deleting/Unmounting a VMFS Datastore
Deleting a VMFS datastore:

Unmounting a VMFS datastore:
6-63
Arrays provide different features.
Some offer active-active storage
processors. Others offer active-
passive SPs.
vSphere 5.1 offers native path
selection, load-balancing, and
failover mechanisms.
Third-party vendors can create
their own software to be installed
on your ESXi host that will allow
the ESXi host to properly interact
with the storage arrays that it uses.

Multipathing Algorithms
storage array

SP A
1 0

SP B
1 0
ESXi
hosts
SPs
switches
6-64
To modify the number of storage paths to use, select the datastore to
modify and click that datastores Properties link.
Click Manage Paths in the Properties window.
Managing Multiple Storage Paths
6-65
Path selection policies exist for:
Scalability:
Round Robin A multipathing policy that performs load balancing across
paths
Availability:
Most Recently Used (MRU) and Fixed
Configuring Storage Load Balancing
6-66
In this lab, you will create and manage VMFS datastores.
1. Review your shared storage configuration.
2. Change the name of a VMFS datastore.
3. Create a VMFS datastore.
4. Expand a VMFS datastore to consume unused space on a LUN.
5. Remove a VMFS datastore.
6. Extend a VMFS datastore.
Ask your instructor which LUNs contain VMFS datastores that
should not be removed or reformatted.

Lab 8
6-67
Create a VMFS datastore.
Increase the size of a VMFS datastore.
Delete a VMFS datastore.
6-68
Lesson 6:
VSA
6-69
Describe the architecture and requirements of the VMware vSphere
Storage Appliance (VSA) cluster configuration.
Discuss how a VSA cluster handles failures.
Learner Objectives
6-70
Cost-effective, easy-to-deploy shared storage that enables high
availability for any small environment
What Is VSA?
6-71
Provides storage framework for vMotion, vSphere HA, and
DRS
VSA Benefits
Creates shared
storage
Simple
manageability
Abstraction from underlying hardware
Resilient to server failures
Highly available during disk (spindle) failure
Pools local server disk capacity to form shared storage
Leverages vSphere Thin Provisioning for space utilization
Enables storage scalability
Installed, configured, and managed in VMware vCenter
Server
Delivers
high availability
6-72
Features of VSA
VSA for Essentials Plus VSA
Nodes per cluster 3 3
Raid 5/6/10 Support Yes Yes
vCenter running on VSA Yes Yes
Add/replace hard disk drives
non-disruptively
Yes Yes
Centralized management of
multiple VSA Clusters
Yes
6-73
Central Management of VSA
VMware vCenter Server
Central Office
VSA Cluster 3
Branch Office 3
Branch Office 1
VSA Cluster 1
Branch Office 4
VSA Cluster 4
Branch Office 2
VSA Cluster 2
6-74
NFS
NFS NFS
VSA Architecture
vSphere vSphere vSphere
VSA VSA
VSA
vSphere Client
VSA Manager
NFS exports that can be
mounted by client ESXi
hosts
Enables advanced
features like vMotion,
vSphere HA, DRS
vCenter Server
6-75
Ensure that your environment meets the following requirements:
Physical or virtual machine that runs vCenter Server
vCenter can run on one of the ESXi hosts in the cluster.
Two or three physical hosts with ESXi installed
All hosts must use the same type of ESXi installation.
One Gigabit Ethernet or one 10Gigabit Ethernet switch
Two switches can be used to eliminate single points of failure.
Switches must be configured to support the front-end and back-end
networks of the VSA Cluster.
VSA Cluster Requirements
6-76
VSA Cluster Configuration Requirements
VSA
vCenter Server 5.0

VSA Manager VSA cluster service
VSA Manager 10.10.120.3
NFS Volume IP 10.10.120.5
vMotion IP 192.168.1.1
10.15.20.100
VSA Cluster IP 10.10.120.200
VSA cluster
front end
back end
ESXi host 10.15.20.150
10.15.20.201
Recommended:
24GB of RAM,
4 hard disks,
RAID controller,
Gigabit Ethernet switches
The VSA
Manager is used
to install the VSA
cluster.
6-77
VSA Manager
6-78

vCenter Server

Manage

VSA Manager

VSA cluster service

VSA
Datastore 2
VSA
Datastore 1
Volume 1
(Replica)
Volume 2
Volume 1
Volume 2
(Replica)
Configure RAID 1+0
on local system disks.
VSA Cluster with Two ESXi 5.1 Hosts
6-79

vCenter Server

Manage

VSA Manager

Volume 1
Volume 3
(Replica)
Volume 2
(Replica)
Volume 3
Volume 1
(Replica)
Volume 2
VSA
Datastore 2
VSA
Datastore 3
VSA
Datastore 1
VSA Cluster with Three ESXi 5.1 Hosts
6-80
VSA Resilience

vCenter Server

Manage

VSA Manager

Volume 1
Volume 2
(Replica)
Volume 1
(Replica)
Volume 2

VSA cluster service

VSA
Datastore 2
VSA
Datastore 1
6-81
Differences Between VSA Clusters and SANs
Storage Area Network
Volume replica placement across spindles
VSA Cluster
Server 1 Server 2
Redundant
Network
Volume replica placement across
servers
direct
attached
direct
attached
6-82
Describe the architecture and requirements of the VSA cluster
configuration.
Discuss how a VSA cluster handles failures.
6-83
Use VMFS datastores to hold virtual machine files.
NFS datastores are useful as a repository for ISO images.
Shared storage is integral to vSphere features like vMotion, vSphere
HA, and DRS.
VSA enables low-end configurations to use vSphere HA, vMotion, and
VMware vSphere Storage vMotion without requiring external shared
storage.
Questions?

Key Points

Configuring VSphere

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Configuring VSphere

Загружено:

Авторское право:

Доступные форматы

2012 VMware Inc.

All rights reserved

Вам также может понравиться