Sunday, July 8, 2012

2 Hyper-V Lab Build note 3,4:Failover Cluster/iSCSI

1. Install Hyper-V 2008R2

2. Base configuration

  • Change computer name
  • Allow MMC Remote Management
  • Enable Windows PowerShell
  • Allow Server Manager Remote Management
  • Configure firewall
netsh advfirewall firewall add rule name="ICMP Allow Incoming V4 Echo" protocol=icmpv4:8,any dir=in action=allow
  • Enable remote volume management
sc query vds
sc config vds start= auto
net start vds
sc qc vds

Below firewall rule needs to be add on both client and server

netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
  • Change the DNS server point to the DC server. This is for adding the computer to the DC. without this step , the computer can not find the DC
netsh interface ipv4 show interfaces
netsh interface ipv4 add dnsserver "" 192.168.168.129 index=19

image

  • Join the domain
netdom join %computername% /domain:STAR.COM /userd:STAR\administrator /passwordd:XXXXX

3. Enable Cluster  Role

ocslist
start /w ocsetup FailoverCluster-Core

Before installed: oclist

image

After installed: oclist

image

4. Configure and Start the iSCSI initiator service

sc query msiscsi
sc config msiscsi start= auto
net start msiscsi
sc qc msiscsi

image

5. Connecting the Server Core to the iSCSI storage host

*I like to find the way to change the IQN name on the initiator from iscsicli. However, I could not find any command line reference to do so *

-- iSCSIcli QAddTargetPortal <Storage Box, Portal IP Address> 
iSCSIcli QAddTargetPortal SG31

Go to the storage box and refresh the IQN list and add the client in

image

iSCSIcli ListTargets 

image

-- iSCSIcli QloginTarget <Target IQN>
iSCSIcli QloginTarget iqn-sg31-disk1  

image

-- iSCSIcli PersistentLoginTarget <target_iqn> T * * * * * * * * * * * * * * * 0 
iSCSIcli PersistentLoginTarget iqn-sg31-disk1 T * * * * * * * * * * * * * * * 0 
iSCSIcli ListPersistentTargets 
image
iSCSIcli ReportTargetMappings 

image

6. Configuring the clustered disks

We can do this from command line diskpart. since we have configure the vds management from remote. It is doable from computer manager.

We need to bring 2 disks online. One for the quorum and the other one would store the actual share data. Quorum does not need to be big. one GB should be good enough. Format the NTFS and assign the disk letter.

image

image

Since the disk has been format and assign the letter. When the 2nd node add it in. it will show up in the disk manager just like the first node.

7. Configure the cluster

Validate the cluster configuration

image

image

Now, create the cluster …

image

image

image

image

Configure share storage. The share storage allow both nodes written to the same disk. It is only allow for the Hyper-V role.

image

image

Configure Cluster Quorum Settings

image

image

image

image

Reference

2 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. You can change the iSCSI node name with the following command:

    iscsicli nodename iqn.1991-05.com.microsoft:yourservername

    However, this only works once per host for me. I'm trying to discover whether this is a known bug.

    ReplyDelete

 

SQL Panda Copyright © 2011 - |- Template created by O Pregador - |- Powered by Blogger Templates