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

• 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

After installed: oclist

4. Configure and Start the iSCSI initiator service

sc query msiscsi

sc config msiscsi start= auto

net start msiscsi

sc qc msiscsi

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

iSCSIcli ListTargets 

-- iSCSIcli QloginTarget <Target IQN>

iSCSIcli QloginTarget iqn-sg31-disk1  

-- iSCSIcli PersistentLoginTarget <target_iqn> T * * * * * * * * * * * * * * * 0 

iSCSIcli PersistentLoginTarget iqn-sg31-disk1 T * * * * * * * * * * * * * * * 0 

iSCSIcli ListPersistentTargets 

iSCSIcli ReportTargetMappings 

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.

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

Now, create the cluster …

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

Configure Cluster Quorum Settings

Reference

• Building a Failover Cluster with Server Core Part 1 http://blogs.technet.com/b/aralves/archive/2008/03/31/building-a-failover-cluster-with-server-core-part-1.aspx
• Building a Failover Cluster with Server Core Part 2 http://blogs.technet.com/b/aralves/archive/2008/03/31/building-a-failover-cluster-with-server-core-part-2.aspx
• Building a Failover Cluster with Server Core Part 3 http://blogs.technet.com/b/aralves/archive/2008/03/31/building-a-failover-cluster-with-server-core-part-3.aspx