Category: ISCSI Initiator
-
Resolving Cluster Shared Volume “Redirected Access Mode” Error.
A while ago, I encountered a Cluster Shared Volume error in my lab. I logged into the Failover Cluster Manager and noticed multiple error status messages in the Cluster Events log. The System Log Event ID 5125 kept showing up every three minutes: Error Event id 5125 with details: Cluster Shared Volume ‘Volume1’ (‘Cluster Disk…
-
Configuring multiple ISCSI Connections for Multipath IO using PowerShell.
This post will be focused mainly on the ISCSI Initiator host and configuring multipath IO paths to an ISCSI Target. The ISCSI Target portal has already been configured with 2 network paths for ISCSI. The ISCSI Service by default is in a ‘Stopped’ state. So, we’ll begin by starting the service: [hyperv00]: PS C:\Users\admin\Documents> Start-Service…
-
Configuring Hyper-v Host Network Adapters for ISCSI Storage Connectivity with Powershell .
Windows Server 2012 R2 with PowerShell 4.0 has hugely expanded support for configuring multiple NICs on a Cluster/ISCSI Initiator node via command line. After deploying multiple Network Interface Cards on my Hyper-v host, it took me a while to figure out how to properly configure the NICS with PowerShell . Prior to Windows Server 2012,…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 5
As it turns out, I already have two Virtual machines running on one of the cluster nodes. I set these up before the cluster creation. The VMs are currently not cluster roles/resources. I will go ahead and make one of the VMs (WK7) a cluster role by adding it to the cluster. PS C:\> Get-VM…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 4
Here we go over my steps for the actual cluster creation, cluster and node validation, quorum setup and cluster shared volume configuration.We have by running a cluster validation on each node. This can be achieved with the following cmdlets: Test-Cluster -Node hyperv01 Test-Cluster -Node hyperv03 In this case, the test passed. The process basically gives…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 3
In the next part of the series, we will create a simple 1GB iSCSI virtual disk, assign it to the already configured target and verify the disk is visible to the iSCSI initiators. New-IscsiVirtualDisk -Description “Witness Disk” -Path g:\iscsivirtualdisks\Witness00.vhd -Size 1GB -ComputerName labtarget -Verbose (Create the 1GB iSCSI virtual disk) Add-IscsiVirtualDiskTargetMapping -TargetName Target00 -Path g:\iscsivirtualdisks\Witness00.vhd…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 2
In this part of the series, we will configure two hosts as iSCSI initiators. The hosts have already been defined at the Target and ready to log on. Both hosts are running WS 2012 Hyper-v Core and I made sure to install the Failover Clustering and Hyper-v windows features. Following is a snapshot of the cmdlets available…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 1
We’re currently working on virtualizing a large number of our servers and going through the process of deciding whether to deploy a 3rd party SAN or WS 2012 iSCSI Target in production. In the meantime, I have gone ahead and deployed a basic iSCSI Target and Two host WS 2012 Failover cluster in the lab…
Chinny Chukwudozie, Cloud Solutions. 