Using a VNXe System with Microsoft Windows Hyper-V - EMC ...
Using a VNXe System with Microsoft Windows Hyper-V - EMC ... Using a VNXe System with Microsoft Windows Hyper-V - EMC ...
Setting Up a Host to Use VNXe Hyper-V StorageConfiguring the host to connect to a VNXe iSCSI ServerBefore an initiator can establish a session with a target, the initiator must discover wherethe targets are located and the names of the targets available to it. To obtain thisinformation the initiator uses the iSCSI discovery process. The VNXe iSCSI Servers supportdiscovery with or without an iSNS server. Without iSNS discovery, you must add the targetinformation to the Microsoft iSCSI Initiator. With iSNS discovery, the initiator queries theiSNS server where all iSCSI initiators and targets register themselves, and the serverresponds with a list of available targets. When the target information is available to theMicrosoft iSCSI Initiator, you can connect the host initiator to the target so the host canaccess the virtual disks in its Hyper-V datastores.To configure the Windows host initiators:Unless you are using VNXe iSCSI targets in a clustered environment, do not give more thanone initiator access to the same Hyper-V disk. Conflicts can occur if more than one initiatortries to write to the Hyper-V disk. If the Hyper-V disk is formatted with the NTFS file systemin Windows, simultaneous writes can corrupt the NTFS file system on the Hyper-V disk.As a best practice, do not give an initiator access to a Hyper-V disk that does not exist.For VNXe iSCSI servers configured with multiple IP addresses, you need to add targetportals for each of the IPs configured for each server.Each VNXe iSCSI Server is a target. If a VNXe system has two iSCSI Servers, it has twotargets. Each target has one session. Each IP address associated with a VNXe iSCSI Serveris a target portal. If a VNXe iSCSI Server has two IP addresses associated with it, it has twotarget portals. For multiple paths to the host, a VNXe iSCSI Server must have two IPaddresses (two target portals) associated with it. You must add each target portal, whichyou want to connect to the host, to the Microsoft iSCSI Initiator on the host when youconfigure an initiator to connect to an iSCSI Server. For a single-path configuration withthe host, you add one target portal. For a multi-path configuration, you add the two targetportals.For a single-path configuration, each session has one connection. For a multi-pathconfiguration, each session has two connections — one connection for each IP address(target portal).Go to the section below for the host’s configuration:For Windows Server 2008 SP2 or earlier:◆◆◆Single-path configuration“Configuring a Windows Server 2008 SP2 or earlier initiator to connect to a VNXeiSCSI Server — single-path configuration” on page 19Multipath configuration with iSCSI Multiple Connections per Session (MCS):“Configuring a Windows Server 2008 SP2 or earlier initiator to connect to a VNXeiSCSI Server — multi-path configuration with MCS” on page 21Multi-path configuration with PowerPath“Configuring a Windows Server 2008 SP2 or earlier initiator to connect to a VNXeiSCSI Server — multi-path configuration with PowerPath” on page 2518 Using a VNXe System with Microsoft Windows Hyper-V
Setting Up a Host to Use VNXe Hyper-V StorageFor Windows Server 2008 R2:◆◆◆Single-path configuration“Configuring a Windows Server 2008 R2 initiator to connect to a VNXe iSCSI Server —single-path configuration” on page 28Multi-path configuration with iSCSI Multiple Connections per Session (MCS):“Configuring a Windows Server 2008 R2 initiator to connect to a VNXe iSCSI Server —multi-path configuration with MCS” on page 31Multi-path configuration with PowerPath“Configuring a Windows Server 2008 R2 initiator to connect to a VNXe iSCSI Server —multi-path configuration with PowerPath” on page 34Appendix A, “Setting Up MPIO for a Windows Hyper-V Cluster Using a VNXe System,” givesan end-to-end example of setting up a two-node Windows Server 2008 R2 Exchangecluster in an MPIO multi-path configuration with a VNXe system.Configuring a Windows Server 2008 SP2 or earlier initiator to connect to a VNXeiSCSI Server — single-path configurationTo configure a Windows Server 2008 SP2 or earlier initiator to connect to a VNXe iSCSIServer in a single-path configuration, perform these tasks:◆Task 1: Setup optional mutual CHAP — Windows Server 2008 SP2 or earlier in asingle-path configuration (page 19).◆ Task 2: Discover the VNXe iSCSI Server in an environment — Windows Server 2008SP2 or earlier in a single-path configuration (page 19).Task 1: Setup optional mutual CHAP — Windows Server 2008 SP2 or earlier in a single-path configurationTo configure optional mutual Challenge Handshake Authentication Protocol (CHAP) youneed the mutual CHAP secret specified for the VNXe iSCSI Server.For the VNXe iSCSI Server to which you want the host iSCSI initiator to access:1. On the host, start the Microsoft iSCSI Initiator.2. If mutual CHAP authentication is configured on the VNXe iSCSI Server, then in theMicrosoft iSCSI Initiator:a. Click the General tab and select Secret.b. In the CHAP Secret Setup dialog box, enter the mutual CHAP secret for the VNXeiSCSI Server.If the VNXe system has multiple iSCSI Servers, this secret is the same for all. Youcan find this secret in the CHAP Security section on the iSCSI Server Settings pagein Unisphere (Settings > iSCSI Server Settings).c. Click OK.Task 2: Discover the VNXe iSCSI Server in an environment — Windows Server 2008 SP2 or earlier in a single-pathconfigurationIf the host initiator is configured for optional initiator Challenge Handshake AuthenticationProtocol (CHAP) on the VNXe iSCSI Server, you need the secret (password) specified forthe initiator on the VNXe system.Configuring the host to connect to a VNXe iSCSI Server 19
- Page 1: EMC ® VNXe SeriesUsing a VNXe Sys
- Page 4 and 5: Contents4 Using a VNXe System with
- Page 7 and 8: PrefaceCourierUsed for:• System o
- Page 9 and 10: CHAPTER 1Setting Up a Host to Use V
- Page 11 and 12: Setting Up a Host to Use VNXe Hyper
- Page 13: Setting Up a Host to Use VNXe Hyper
- Page 16 and 17: Setting Up a Host to Use VNXe Hyper
- Page 20 and 21: Setting Up a Host to Use VNXe Hyper
- Page 23 and 24: Setting Up a Host to Use VNXe Hyper
- Page 25 and 26: Setting Up a Host to Use VNXe Hyper
- Page 27 and 28: Setting Up a Host to Use VNXe Hyper
- Page 29 and 30: Setting Up a Host to Use VNXe Hyper
- Page 31 and 32: Setting Up a Host to Use VNXe Hyper
- Page 33 and 34: Setting Up a Host to Use VNXe Hyper
- Page 35 and 36: Setting Up a Host to Use VNXe Hyper
- Page 37 and 38: Setting Up a Host to Use VNXe Hyper
- Page 39 and 40: Setting Up a Host to Use VNXe Hyper
- Page 41 and 42: Setting Up a Host to Use VNXe Hyper
- Page 43 and 44: CHAPTER 2Migrating Hyper-V Virtual
- Page 45 and 46: Migrating Hyper-V Virtual Machines
- Page 47 and 48: APPENDIX ASetting Up MPIO for a Win
- Page 49 and 50: Setting Up MPIO for a Windows Hyper
- Page 51 and 52: Setting Up MPIO for a Windows Hyper
Setting Up a Host to Use <strong>VNXe</strong> <strong>Hyper</strong>-V StorageFor <strong>Windows</strong> Server 2008 R2:◆◆◆Single-path configuration“Configuring a <strong>Windows</strong> Server 2008 R2 initiator to connect to a <strong>VNXe</strong> iSCSI Server —single-path configuration” on page 28Multi-path configuration <strong>with</strong> iSCSI Multiple Connections per Session (MCS):“Configuring a <strong>Windows</strong> Server 2008 R2 initiator to connect to a <strong>VNXe</strong> iSCSI Server —multi-path configuration <strong>with</strong> MCS” on page 31Multi-path configuration <strong>with</strong> PowerPath“Configuring a <strong>Windows</strong> Server 2008 R2 initiator to connect to a <strong>VNXe</strong> iSCSI Server —multi-path configuration <strong>with</strong> PowerPath” on page 34Appendix A, “Setting Up MPIO for a <strong>Windows</strong> <strong>Hyper</strong>-V Cluster <strong>Using</strong> a <strong>VNXe</strong> <strong>System</strong>,” givesan end-to-end example of setting up a two-node <strong>Windows</strong> Server 2008 R2 Exchangecluster in an MPIO multi-path configuration <strong>with</strong> a <strong>VNXe</strong> system.Configuring a <strong>Windows</strong> Server 2008 SP2 or earlier initiator to connect to a <strong>VNXe</strong>iSCSI Server — single-path configurationTo configure a <strong>Windows</strong> Server 2008 SP2 or earlier initiator to connect to a <strong>VNXe</strong> iSCSIServer in a single-path configuration, perform these tasks:◆Task 1: Setup optional mutual CHAP — <strong>Windows</strong> Server 2008 SP2 or earlier in asingle-path configuration (page 19).◆ Task 2: Discover the <strong>VNXe</strong> iSCSI Server in an environment — <strong>Windows</strong> Server 2008SP2 or earlier in a single-path configuration (page 19).Task 1: Setup optional mutual CHAP — <strong>Windows</strong> Server 2008 SP2 or earlier in a single-path configurationTo configure optional mutual Challenge Handshake Authentication Protocol (CHAP) youneed the mutual CHAP secret specified for the <strong>VNXe</strong> iSCSI Server.For the <strong>VNXe</strong> iSCSI Server to which you want the host iSCSI initiator to access:1. On the host, start the <strong>Microsoft</strong> iSCSI Initiator.2. If mutual CHAP authentication is configured on the <strong>VNXe</strong> iSCSI Server, then in the<strong>Microsoft</strong> iSCSI Initiator:a. Click the General tab and select Secret.b. In the CHAP Secret Setup dialog box, enter the mutual CHAP secret for the <strong>VNXe</strong>iSCSI Server.If the <strong>VNXe</strong> system has multiple iSCSI Servers, this secret is the same for all. Youcan find this secret in the CHAP Security section on the iSCSI Server Settings pagein Unisphere (Settings > iSCSI Server Settings).c. Click OK.Task 2: Discover the <strong>VNXe</strong> iSCSI Server in an environment — <strong>Windows</strong> Server 2008 SP2 or earlier in a single-pathconfigurationIf the host initiator is configured for optional initiator Challenge Handshake AuthenticationProtocol (CHAP) on the <strong>VNXe</strong> iSCSI Server, you need the secret (password) specified forthe initiator on the <strong>VNXe</strong> system.Configuring the host to connect to a <strong>VNXe</strong> iSCSI Server 19
Change language