2012r2 iSCSI Cluster SAS MPIO

Hi,
we are building a iSCSI failover cluster for Hyper-V and vmWare. We use 3 JBODS directly connected to 2 nodes with dual-SAS. There will be a tiered StorrageSpace with Enclosure-Awarenes. My question now is, which SAS-HDD MPIO policy do i have to set inside
the disk settings of the hardwaremanager? Failover or Round-Robin? I think this should be Failover??
Thanks for helping!
cm3c
Clustered Storage Spaces are going to hide this from you completely. Also spawning MSFT iSCSI on top of a CSS-created CSV is not a good idea: MSFT iSCSI target is failover only (no performance boost with multiple heads involved) and does not cache data in
RAM so will trash your flash cache quite a lot (CSV cache is read-only so does not adsorb writes) with a slow I/O response time. Consider using something else, heck, even a failover NFS share may work better talking about MSFT built-in tools.
In general setup us flaky. Talking about VMware you definitely need to look @ VMware Virtual SAN approach as resulting solution would be cheaper and faster compared to what you do now (flash is local, on server-side and not hiding behind slow Ethernet, heavy
log-structuring and reduced I/O pass). + MSFT iSCSI target is NOT on VMware HCL and Virtual SAN is coming from a hypervisor vendor so config you build is UNSUPPORTED compared to 200% OK one with VMware Virtual SAN (no fingerprinting in case of an issue - HUGE
benefit).
Your choice either way... Good luck! :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

SAS MPIO Driver Server 2012 HCT Fails with "make sure two ports are connected" error even with two ports connect

We are running the Server 2012 HCT against a SAS MPIO driver for a server platform with dual redundant storage controllers. The test fails with this error:
(x) For non-iSCSI test environment, please make sure at least two HBA ports are connected to the storage target.
File=testsrc\driverstest\storage\wdk\mpiotest\logotest\devicelib\mpiodevice.cpp Line=2772
Error: 0x0, Error 0x00000000
The system does have two ports connected so the cause of the error is unclear to us. We do not have any problems when running the 2008R2 HCT. Are there any known issues or fixed or workarounds for this problem?

Sorry, maybe I should say WLK rather than HCT. We are trying to submit the SAS MPIO driver for WHQL signing.
Here is a sample MPIO snapshot where you can see our driver is controlling five drives each with two paths.
MPIO Storage Snapshot on Wednesday, 17 April 2013, at 18:31:40.275
Registered DSMs: 2
================
+--------------------------------|-------------------|----|----|----|---|-----+
|DSM Name | Version |PRP | RC | RI |PVP| PVE |
|--------------------------------|-------------------|----|----|----|---|-----|
|Microsoft DSM |006.0002.09200.16384|0120|0003|0001|030| True|
|Intel(R) Storage Controller MPIO|004.0001.00140.0002|0120|0003|0001|030| True|
+--------------------------------|-------------------|----|----|----|---|-----+
Microsoft DSM
=============
No devices controlled by this DSM at this time!
Intel(R) Storage Controller MPIO Driver
=======================================
MPIO Disk4: 02 Paths, Fail Over Only, Explicit Only
SN: 2263015539BAB
Supported Load Balance Policies: FOO RR RRWS LQD
Path ID State SCSI Address Weight
0000000077000001 Standby 000|000|001|004 0
TPG_State: Standby , TPG_Id: 1, TP_Id: 6
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: EBF4115500000000 (State: No Controller)
0000000077000000 Active/Optimized 000|000|000|004 0
* TPG_State: Active/Optimized , TPG_Id: 0, TP_Id: 3
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: D1FBD25300000000 (State: No Controller)
MPIO Disk3: 02 Paths, Fail Over Only, Explicit Only
SN: 22201556966AB
Supported Load Balance Policies: FOO RR RRWS LQD
Path ID State SCSI Address Weight
0000000077000001 Active/Optimized 000|000|001|003 0
* TPG_State: Active/Optimized , TPG_Id: 1, TP_Id: 6
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: EBF4115500000000 (State: No Controller)
0000000077000000 Standby 000|000|000|003 0
TPG_State: Standby , TPG_Id: 0, TP_Id: 3
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: D1FBD25300000000 (State: No Controller)
MPIO Disk2: 02 Paths, Fail Over Only, Explicit Only
SN: 226E01556E6C5F
Supported Load Balance Policies: FOO RR RRWS LQD
Path ID State SCSI Address Weight
0000000077000001 Active/Optimized 000|000|001|002 0
* TPG_State: Active/Optimized , TPG_Id: 1, TP_Id: 6
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: EBF4115500000000 (State: No Controller)
0000000077000000 Standby 000|000|000|002 0
TPG_State: Standby , TPG_Id: 0, TP_Id: 3
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: D1FBD25300000000 (State: No Controller)
MPIO Disk1: 02 Paths, Fail Over Only, Explicit Only
SN: 227C01558F689E
Supported Load Balance Policies: FOO RR RRWS LQD
Path ID State SCSI Address Weight
0000000077000001 Standby 000|000|001|001 0
TPG_State: Standby , TPG_Id: 1, TP_Id: 6
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: D1FBD25300000000 (State: No Controller)
0000000077000000 Active/Optimized 000|000|000|001 0
* TPG_State: Active/Optimized , TPG_Id: 0, TP_Id: 3
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: 6E9AD05300000000 (State: No Controller)
MPIO Disk0: 02 Paths, Fail Over Only, Explicit Only
SN: 22F10155FB941D
Supported Load Balance Policies: FOO RR RRWS LQD
Path ID State SCSI Address Weight
0000000077000001 Standby 000|000|001|000 0
TPG_State: Standby , TPG_Id: 1, TP_Id: 6
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: D1FBD25300000000 (State: No Controller)
0000000077000000 Active/Optimized 000|000|000|000 0
* TPG_State: Active/Optimized , TPG_Id: 0, TP_Id: 3
Adapter: LSI Adapter, SAS 3000 series, 4-port ... (B|D|F: 004|000|000)
Controller: 6E9AD05300000000 (State: No Controller)
MSDSM-wide default load balance policy: N\A
No target-level default load balance policies have been set.
================================================================================

Does the 2012r2 failover cluster support the Linux system high ability

Hi,
Can i install the CentOS highability in Hyper-V? Does Hyper-V support it?
Thanks.

Hi,
Can i install the CentOS highability in Hyper-V? Does Hyper-V support it?
Thanks.
There are two possible ways to go and you're referenced both. First is HA VM. If physical host would fail VM marked as "HA" would be re-booted on another physical host in the cluster. That approach is completely OS-agnostic and would work with Linux (or
any other supported OS) inside a VM. See:
Configure VM for HA
http://technet.microsoft.com/en-us/library/cc753787.aspx
Second one is guest VM cluster which is actually job of an inside-the-VM OS, Hyper-V just provides a platform (and possibly shared storage). In this case you do configure your Linux cluster as it would run bare metal. See:
Guest
VM Cluster
http://blogs.technet.com/b/keithmayer/archive/2013/03/21/virtual-machine-guest-clustering-with-windows-server-2012-become-a-virtualization-expert-in-20-days-part-14-of-20.aspx
You just need to pick up proper shared storage for your cluster, would it be shared SAS (provided by Hyper-V as "shared VHDX" emulation) or iSCSI or FC.
Good luck :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Windows Server 2012R2 Failover Cluster error with mounted volumes

Hi all,
I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
M: is the volume hosting mounting points
disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
I'm going crazy!

I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
Cluster stops to get problems.
Now we have opened a support call with VMware.

Windows Server 2012r2 Failover Cluster Event Trace Log files

Hi
The only documentation I can find regarding event trace log files (Diagnostic.etl.*) for Failover Clustering relate to Server 2008/2008r2, which state that the etl files should be in C:\Windows\System32\winevt\Logs.
I have been exploring a clustering lab for Server 2012r2 and cannot find these files in that folder.
Strangely the PS cmdlet Get-ClusterLog still works!
Where are the etl files?
TIA

Hi,
Please check if the log is available in C:\ProgramData\Microsoft\Windows\WER\ReportQueue\.
If not, you can use Get-ClusterLog with the Destination parameter to get the log file.
Destination
Specifies the location to copy the cluster log(s) to. To copy to the current folder use "-Destination ." for this parameter.
http://technet.microsoft.com/en-us/library/ee461045.aspx
Thanks.
Jeremy Wu
TechNet Community Support

2008R2 to 2012R2 = Failover Cluster Manager not found ..gray out feature.

Hello everyone,
I just upgraded from our Hyper-V host running Windows Server 2008R2 to 2012R2,
I didn't get any errors during the upgrade and everything looked fine except that the failover cluster manager is no longer exist ..I went to add it from the server manager and found that the feature already exist but it is grayed out, I can not remove it and
add it again!
how to get the failover manager cluster working again ?
Thanks
Misbah

ok, the fix seems simple,
I needed to go from server manager and select remove role/features and then re-add it.
going to add roles/feature will not allow me to remove any feature ..it is just for adding features.

DPM Storage Pool on Windows Server 2012R2 iSCSI target Storage Spaces - supported?

Hi,
for migration purpose we need more space for one of our DPM 2012R2 Servers.
And we cannot buy more space for our NetAPPs..
So our idea was to use an Windows Server 2012R2 as an iSCSI target and use Storage Spaces.
I remember something that using an iSCSI target on Windows 2008 was not supported.
Is this configuration supported when usinf DPM 2012R2 on Win 2012R2 and the target is Win2012R2 aswell?
Thanks in advance
regards
/bkpfast
My postings are provided "AS IS" with no warranties and confer no rights

Hi,
This talks about
Virtual DPM servers, but the same is true for Physical DPM servers when it comes to using .VHD(x) files for DPM storage pool.
Virtual DPM installations do not support the following:
Windows 2012 Storage Spaces.
Virtual hard drives built on top of storage spaces.
Local or remote hosting of VHDX files on Windows 2012 storage spaces.
Enabling Disk Dedupe on volumes hosting virtual hard drives.
Using synthetic FC to connect to tape drives.
Windows 2012 iSCSI targets (which use virtual hard drives) as a DPM storage pool.
NTFS compression for volumes hosting VHD files used in the DPM storage pool.
Bitlocker on volumes hosting VHD files used for the storage pool.
A native 4K sector size of physical disks for VHDX files in the DPM storage pool.
Virtual hard drives hosted on Windows 2008 servers.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Should one use MPIO and/or CSV in a Windows 2012 R2 guest cluster?

Should one use MPIO and/or CSV in a Windows 2012 R2 guest cluster using VMware ESXi 5.5 presented Fiber LUN RDMs.
If MPIO were implemented is there a preference for HW manufacturer DISM vs. MS DISM in a guest cluster?
What partition size/offset is recommended for the MSR partition (currently set to 1000 MB) - unfortunately seeing storage validation error with failing block write at block 2048 (which in return may be related to VMware ESXi 5.5. disk partition layout)
The current setup works without using MPIO (question is would it help overcome the current failing persistent SCSI-3 reservation warning.)
What were the benefit of using CSV if any in a guest cluster? The Luns in scope would eventually hold SQL data and log files.
Thanks for your input already.
Sassan Karai

Hi,
Regardless of what type of the shared storage is failover cluster have to use the shared storage, the shared storage can redirect the failed node data to others node, accordingly
the failover cluster can get the high availability.
From you descripted error there must you choose the VMware® unsupported storage with failover cluster, please refer the following VMware® official KB then reconfirm your topology
design is supported.
Third party KB:
VMware vSphere support for Microsoft clustering solutions on VMware products
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
The related KB:
Failover Clustering Hardware Requirements and Storage Options
http://technet.microsoft.com/zh-cn/library/jj612869.aspx
More information:
Validate Storage Spaces Persistent Reservation Test Results with Warning
http://blogs.msdn.com/b/clustering/archive/2013/05/24/10421247.aspx
Understanding Cluster Validation Tests: Storage
http://technet.microsoft.com/en-us/library/cc771259.aspx#PersistentReservation
Shared storage for Windows Failover Cluster with MPIO
http://blogs.technet.com/b/storageserver/archive/2011/05/31/shared-storage-for-windows-failover-cluster-with-mpio.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Subnet config and switch layout for windows 2012 ISCSI server

I would like to ask about subnet design and switch layout in regards to using a Windows 2012 ISCSI solution. When you guys design subnets for ISCSI configurations do you use one subnet or multiple subnets? Also do you link the switches together when
designing your ISCSI layouts? These types of things are normally discussed in vendor deployment guides. However, I have not come across a best practices guide for deploying Server 2012 ISCSI.

I would like to ask about subnet design and switch layout in regards to using a Windows 2012 ISCSI solution. When you guys design subnets for ISCSI configurations do you use one subnet or multiple subnets? Also do you link the switches together
when designing your ISCSI layouts? These types of things are normally discussed in vendor deployment guides. However, I have not come across a best practices guide for deploying Server 2012 ISCSI.
For iSCSI you typically create a separate subnets around physical NICs you use for iSCSI traffic (assuming they are used by iSCSI target for MPIO of course). Here are few guides on how to do that (some for Windows Server 2008 R2 but you can ignore that fact
as target itself did not change much and concepts are still the same). See:
Configure iSCSI MPIO on Windows (full)
http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx
(make sure you have at leas one connection before you try to enable MPIO)
Setting up a Target and Initiator
http://www.server-log.com/blog/2011/7/26/setting-up-an-microsoft-iscsi-target-and-initiator-using-mpi.html
You need however be aware of a couple of facts...
1) MSFT does not see much future in iSCSI and is replacing it with SMB3 where it can. So if you want to use iSCSI to provide shared storage to your guest VMs you need to use shared VHDX hosted on SMB3 share, see:
Shared VHDX for guest VM Cluster
http://technet.microsoft.com/en-us/library/dn265980.aspx
If you plan to use iSCSI to host CSV and VM images there you again can use SMB3 share, see:
Hyper-V over SMB
http://technet.microsoft.com/en-us/library/jj134187.aspx
That's both simpler to manage (you don't configure anything except teaming for NICs to enable SMB Multichannel and create a shared folder in a few clicks) and faster: MSFT iSCSI target is not cached @ server side while (OK, Hyper-V ovens VMs in a pass-thru
mode but other users typically don't do that). SQL Server is the same as Hyper-V in terms of SMB3 support, Windows clusters support SMB3 share as a witness and so on.
2) That's a single point of failure. Think about using SoFS instead of a single SMB3 share and think about clustering your target (you'll need a separate fault tolerant back end of that) to increase uptime. See:
MSFT iSCSI Target Failover Cluster
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
Good luck! :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

How to sync the data between the two iSCSI target server

Hi experts:
I have double HP dl380g8 server, i plan to install the server 2012r2 iSCSI target as storage, i know the iSCSI storage can setup as high ability too, but after some research i doesn't find out how to sync the data between the two iSCSI target server, can
any body help me?
Thanks

Hi experts:
I have double HP dl380g8 server, i plan to install the server 2012r2 iSCSI target as storage, i know the iSCSI storage can setup as high ability too, but after some research i doesn't find out how to sync the data between the two iSCSI target server, can
any body help me?
Thanks
There are basically three ways to go:
1) Get compatible software. Microsoft iSCSI target cannot do what you want out-of-box but good news third-party software (there are even free versions with a set of limitations) can do what you want. See:
StarWind Virtual SAN [VSAN]
http://www.starwindsoftware.com/native-san-for-hyper-v-free-edition
DataCore SANxxx
http://datacore.com/products/SANsymphony-V.aspx
SteelEye DataKeeper
http://us.sios.com/what-we-do/windows/
All of them do basically the same: mirror set of LUs between Windows hosts to emulate a high performance and fault tolerant virtual SAN. All of them do this in active-active mode (all nodes handle I/O) and at least StarWind and DataCore have sophisticated
distributed cache implementations (RAM and flash).
2) Get incompatible software (MSFT iSCSI target) and run it in generic Windows cluster. That would require you to have CSV so physical shared storage (FC or SAS, iSCSI obviously has zero sense as you can feed THAT iSCSI target directly to your block storage
consumers). This is doable and is supported by MSFS but has numerous drawbacks. First of all it's SLOW as a) MSFT target does no caching and even does not use file system cache (at all, VHDX it uses as a containers are opened and I/O-ed in a "pass-thru" mode)
b) it's only active-passive (one node will handle I/O @ a time with other one just doing nothing in standby mode) and c) long I/O route (iSCSI initiator -> MSFT iSCSI target -> clustered block back end). For reference see:
Configuring iSCSI Storage for High Availability
http://technet.microsoft.com/en-us/library/gg232621(v=ws.10).aspx
MSFT iSCSI Target Cluster
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Re-think what you do. Except iSCSI target from MSFT you can use newer technologies like SoFS (obviously faster but requires a set of a dedicated servers) or just a shared VHDX if you have a fault tolerant SAS or FC back end and want to spawn a guest VM
cluster. See:
Scale-Out File Servers
http://technet.microsoft.com/en-us/library/hh831349.aspx
Deploy a Guest Cluster Using a Shared Virtual Hard Disk
http://technet.microsoft.com/en-us/library/dn265980.aspx
With Windows Server 2012 R2 release virtual FC and clustered MSFT target are both really deprecated features as shared VHDX is both faster and easier to setup and use if you have FC or SAS block back end and need to have guest VM cluster.
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Windows 2012 Nodes - Slow CSV Performance - Need help to resolve my iSCSI issue configuration

I spent weeks going over the forums and the net for any publications and advice on how to optimize iSCSI connections and i'm about to give up. I really need some help in determining if its something i'm not configuring right or maybe its an equipment
issue.
Hardware:
2x Windows 2012 Hosts with 10 Nics (same NIC configuration) in a Failover Cluster sharing a CSV LUN.
3x NICs Teamed for Host/Live Migration (192.168.0.x)
2x NICS teamed for Hyper-V Switch 1 (192.168.0.x)
1x NIC teamed for Hyper-V Switch 2 (192.168.10.x)
4x NICs for iSCSI traffic (192.168.0.x, 192.168.10.x, 192.168.20.x 192.168.30.x)
Jumbo frames and flow control turned on all the NICs on the host. IpV6 disabled. Client for Microsoft Network, File/Printing Sharing Disabled on iSCSI NICs.
MPIO Least Queue selected. Round Robin gives me an error message saying "The parameter is incorrect. The round robin policy attempts to evenly distribute incoming requests to all processing paths. "
Netgear ReadyNas 3200
4x NICs for iSCSI traffic ((192.168.0.x, 192.168.10.x, 192.168.20.x 192.168.30.x)
Network Hardware:
Cisco 2960S managed switch - Flow control on, Spanning Tree on, Jumbo Frames at 9k - this is for the .0 subnet
Netgear unmanaged switch - Flow control on, Jumbo Frames at 9k - this is for .10 subnet
Netgear unmanaged switch - Flow control on, Jumbo Frames at 9k - this is for .20 subnet
Netgear unmanaged switch - Flow control on, Jumbo Frames at 9k - this is for .30 subnet
Host Configuration (things I tried turning on and off):
Autotuning
RSS
Chimney Offload
I have 8 VMs stored in the CSV. When try to load all 8 up at the same time, they bog down.  Each VM loads very slowly and when they eventually come up, most of the important services did not start. I have to load
them up 1 or 2 at a time. Even then the performance is nothing like if they were loading up on the Host itself (VHD stored on the host's hdd). This is what prompted me to add in more iSCSI connections to see if I can improve the VM's
performance.  Even with 4 iSCSI connections, I feel nothing has changed. The VMs still start up slowly and services do not load right. If I distribute the load with 4 VMs on Host 1 and 4 VMs on Host 2, the load up
times do not change.
As a manual test for file copy speed, I moved the cluster resources to Host 1 and copied a VM from the CSV and onto the Host.   The speed would start out around 250megs/sec and then eventually drop down to about 50/60 megs/sec. If I turn
off all iSCSI connections except one, it get the same speed. I can verify from the Windows Performance Tab under Task Manager that all the NICS are distributing traffic evenly, but something is just limiting the flow. Like what I stated on top,
I played around with autotuning, RSS and chimney offload and none of it makes a difference.
The VMs have been converted to VHDx and to fixed size. That did not help.
Is there something I'm not doing right? I am working with Netgear support and they are puzzled as well. The ReadyNas device should easily be able to handle it.
Please help! I pulled my hair out over this for the past two months and I'm about to give up and just ditch clustering all together and just run the VMs off the hosts themselves.
George

A few things...
For starters, I recommend opening a case with Microsoft support. They will be able to dig in and help you...
Turn on the CSV Cache, it will boost your performance
http://blogs.msdn.com/b/clustering/archive/2012/03/22/10286676.aspx
A file copy has no resemblance of the unbuffered I/O a VM does... so don't use that as a comparison, as you are comparing apples to oranges.
Do you see any I/O performance difference between the coordinator node and the non-coordinator nodes? Basically, see which node owns the cluster Physical Disk resource... measure the performance. Then move the Physical Disk resource for the
CSV volume to another node, and repeat the same measure of performance... then compare them.
Your IP addressing seems odd... you show multiple networks on 192.168.0.x and also on 192.168.10.x.   Remember that clustering only recognizes and uses 1 logical interface per IP subnet. I would triple check all your IP schemes...
to ensure they are all different logical networks.
Check you binding order
Make sure you NIC drivers and NIC firmware are updated
Make sure you don't have IPsec enabled, that will significantly impact your network performance
For the iSCSI Software Initiator, when you did your connection... make sure you didn't do a 'Quick Connect'... that will do a wildcard and connect over any network. You want to specify your dedicated iSCSI network
No idea what the performance capabilities of the ReadyNas is... this could all likely be associated with the shared storage.
What speed NIC's are you using?   I hope at least 10 GB...
Hope that helps...
Elden
Hi Elden,
2. CSV is turned on, I have 4GB dedicated from each host to it. With IOmeter running within the VMs, I do see the read speed jumped up 4-5x fold but the write speed stays the same (which according to the doc it should). But even with the read
speed that high, the VMs are not starting up quickly.
4. I do not see any difference with IO with coordinator and non coordinator nodes.
5. I'm not 100% sure what your saying about my IPs. Maybe if I list it out, you can help explain further.
Host 1 - 192.168.0.241 (Host/LM IP), Undefined IP on the 192.168.0.x network (Hyper-V Port 1), Undefined IP on the 192.168.10.x network (Hyper- V port 2), 192.168.0.220 (iSCSI 1), 192.168.10.10 (iSCSI2), 192.168.20.10(iSCSI 3), 192.168.30.10 (iSCSI 4)
The Hyper-V ports are undefined because the VMs themselves have static ips.
0.220 host NIC connects with the .231 NIC of the NAS
10.10 host NIC connects with the 10.100 NIC of the NAS
20.10 host NIC connects with the 20.100 NIC of the NAS
30.10 host NIC connects with the 30.100 NIC of the NAS
Host 2 - 192.168.0.245 (Host/LM IP), Undefined IP on the 192.168.0.x network (Hyper-V Port 1), Undefined IP on the 192.168.10.x network (Hyper- V port 2), 192.168.0.221 (iSCSI 1), 192.168.10.20 (iSCSI2), 192.168.20.20(iSCSI 3), 192.168.30.20 (iSCSI 4)
The Hyper-V ports are undefined because the VMs themselves have static ips.
0.221 host NIC connects with the .231 NIC of the NAS
10.20 host NIC connects with the 10.100 NIC of the NAS
20.20 host NIC connects with the 20.100 NIC of the NAS
30.20 host NIC connects with the 30.100 NIC of the NAS
6. Binding orders are all correct.
7. Nic drivers are all updated. Didn't check the firmware.
8. I do not know about IPSec...let me look into it.
9. I did not do quick connect, each iscsi connection is defined using a specific source ip and specific target ip.
These are all 1gigabit nics, which is the reason why I have so many NICs...otherwise there would be no reason for me to have 4 iscsi connections.

How to Find the Latest Version of Cluster Binary Files available at Microsoft website

How we can find the latest version of Cluster binary files available for download at Microsoft Website and which Cluster Binaries should be update to make the Cluster services stable healthy.

@AnatolySV : I believe you need to put some efforts to understand what he is asking.
You may find the latest version of Cluster Binaries by entering the required keywords for Microsoft Failover Clustering. Some of the main Cluster binaries(Keywords) are:-
Clusres.dll (For Cluster Resources like Disk, Application or Service, Cluster IP)
Clussvc.exe (Cluster Service)
TCPIP.sys (If the Storage is presented to the cluster Nodes via ISCSI Network).
MPIO.sys / ISCSIprt.sys (If we are using Multipathing for the disks to be presented).
RHS.exe (Resource Host Subsystem)
So, the Answer to your question is: You need to enter the binary name "Clusres.dll" and mention the Operating System you want to install your binaries to "Windows Server 2008 R2 Sp1" on Bing (Preferred for Microsoft Hotfixes). In Result you will get the
list of hotfixes for clusres.dll
You need to try this multiple times in order to get the latest version as Microsoft does not have a single Link.
Hope this answers your query. Feel free to leave a message incase you need more help.
Maybe)
But hey, you`ve got +1 from me for clarification)
Anyway, I still think that the initial question could be more clear and exact.

Configuring MPIO for 2012 R2 SOFS

Setting up a 2 node 2012 R2 SOFS. I have 2 2012 R2 nodes,each with 3 - dual port LSI SAS HBAs and 3 Data-On Jbods. All HBAs, jbods certified for storage spaces.
I have enabaled MPIO on both nodes and enabled SAS device support in MPIO CPL and rebooted. Is that all there is to it? How can I tell if MPIO is setup and running properly? Here are some of the commands if tried
PS C:\Users\administrator> Get-MSDSMAutomaticClaimSettings
Name Value
iSCSI False
SAS True
PS C:\Users\administrator> Get-MSDSMGlobalDefaultLoadBalancePolicy
None
VendorId ProductId IsMultipathed IsSPC3Supported BusType
HGST HUS726060ALS640 True False SAS
STEC S842E400M2 True False SAS
PS C:\Users\administrator> Get-MPIOSetting
PathVerificationState : Disabled
PathVerificationPeriod : 30
PDORemovePeriod : 20
RetryCount : 3
RetryInterval : 1
UseCustomPathRecoveryTime : Disabled
CustomPathRecoveryTime : 40
DiskTimeoutValue : 60
Also not sure if this relates or not, when I run get-storageenclosure I get this: I have 3 Jbods
PS C:\Users\administrator> Get-StorageEnclosure
FriendlyName HealthStatus NumberOfSlots ElementTypesInError
StorageEnclosure0 Healthy 24
StorageEnclosure2 Healthy 24
StorageEnclosure1 Healthy 24
StorageEnclosure3 Healthy 24
StorageEnclosure5 Healthy 24
StorageEnclosure4 Healthy 24
Thank you for your time

Hi!
But is this really normal? We have 3 enclosures and Get-StorageEnclosure shows 6 enclosures with different names. We have created virtual disk with EnclosureAware option set to true and tried to switch one enclosure off. Virtual disk had failed after this.
Looks like Storage Spaces think, that I really have 6 enclosures and 2 of them went down, so enclosure aware is not working properly.
We use Supermicro's servers as an enclosures. Here are one of them (this must be one enclosure, but it is duplicated):
PS C:\Windows\system32> Get-StorageEnclosure | ? UniqueId -like '5003048001F59E*' | fl
ObjectId                           : {1}\\hvCluster1\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageEnclosure.ObjectId="{edef0cc0-4167-4dfc-82b5-76b644951a6e}:SE:{31c404d2-8f68-d78e-be38-29f4b2f7a1ac}"
PassThroughClass                   :
PassThroughIds                     :
PassThroughNamespace               :
PassThroughServer                  :
UniqueId                           : 5003048001F59E7D
CurrentSensorOperationalStatus     : {OK, OK}
DeviceId                           : {31c404d2-8f68-d78e-be38-29f4b2f7a1ac}
FanOperationalStatus               : {Unknown, Unknown, Unknown}
FirmwareVersion                    : 0717
FriendlyName                       : StorageEnclosure1
HealthStatus                       : Healthy
IOControllerOperationalStatus      :
Manufacturer                       : LSI CORP
Model                              : SAS2X36
NumberOfSlots                      : 24
PowerSupplyOperationalStatus       : {Not Installed, Not Installed}
SerialNumber                       :
TemperatureSensorOperationalStatus : OK
VoltageSensorOperationalStatus     : {OK, OK}
PSComputerName                     :
ObjectId                           : {1}\\hvCluster1\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageEnclosure.ObjectId="{edef0cc0-4167-4dfc-82b5-76b644951a6e}:SE:{f4b6a80c-ff2f-12f8-4e73-2bfea1e64d81}"
PassThroughClass                   :
PassThroughIds                     :
PassThroughNamespace               :
PassThroughServer                  :
UniqueId                           : 5003048001F59EFD
CurrentSensorOperationalStatus     : {OK, OK}
DeviceId                           : {f4b6a80c-ff2f-12f8-4e73-2bfea1e64d81}
FanOperationalStatus               : {Unknown, Unknown, Unknown}
FirmwareVersion                    : 0717
FriendlyName                       : StorageEnclosure4
HealthStatus                       : Healthy
IOControllerOperationalStatus      :
Manufacturer                       : LSI CORP
Model                              : SAS2X36
NumberOfSlots                      : 24
PowerSupplyOperationalStatus       : {Not Installed, Not Installed}
SerialNumber                       :
TemperatureSensorOperationalStatus : OK
VoltageSensorOperationalStatus     : {OK, OK}
PSComputerName                     :

Failover Cluster - GHOST VMS / ROLES

I mean Ghost as in mysterious non-existent machine, not the old Norton program. I've periodically had random cluster crashes, mainly due to my own negligence. 99%
of the time everything comes back up normally. However periodically a machine will have very strange symptoms that i'm unable to resolve. The only resolution I've found is to create a new VM and link to the the old VHD. A description of the
machines with this issue:
Shown in Failover Cluster role as Running but cannot Connect, turn off, shutdown, etc.
Login to Host machine for the VM and open Hyper-V Manager the machine does not exist. The only place this machine seems to exist is in Failover cluster.
No details available on the Summary Tab, machine doesn't actually appear to be running despite what the console says.
Under the resources tab for that Machine is shows the VM as running, but the VM Configuration as failed.
Unable to bring the configuration back online. Error is "The group or resource is not the correct state to perform the requested operation"
I've seen other vague areas about null context pointers or something alone those lines. I've tried researching the users methods to no avail. How can I fix these? Or at least remove them when i've recreated the machine.

Hi,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior.Could you provide more information about your environment. The server version of the problem on, when this problem occurs the system log record information,
screenshots is the best information.
If you are using Server 2012R2 failover cluster please install the following update:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
More information:
Event Logs
http://technet.microsoft.com/en-us/library/cc722404.aspx
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cluster approch

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
 <META content="MSHTML 6.00.2900.2668" name=GENERATOR>
 <STYLE></STYLE>
 </HEAD>
 <BODY bgColor=#ffffff>
 <DIV>
 Here is my situation:- 
 <?xml:namespace prefix = o ns =
 "urn:schemas-microsoft-com:office:office" /><o:p> </o:p>
 I have 2 box say server1 and server2. On server1 I have 1 admin (admin on
 port 7001) server, 1 proxy server (proxy1 on 7005) and 1 managed server (man1 on
 7010). 
 On second box I have 1 proxy server (proxy2 on 7005) and 1 managed server
 (man2 on 7010). Servers man1 and
 man2 are in cluster (cluster address is comma separated IP’s like 10.10.10.1,
 10.10.10.2).
 <o:p> </o:p>
 I am always going on http://10.10.10.1:7005 for the access of my application. But it is a
 single point of failure so our server administrator run a script on both servers
 which checks the state of servers (If one box itself is down or man1 or man 2 is
 down) and assign one unique IP (10.10.10.5) to the box. So if server 1 is down
 server 2 can be access by this IP or if server 2 is down server 1 can be access
 with this IP. That is why I have 2
 proxies here. This IP rollover takes around 60 seconds. 
 <o:p> </o:p>
 Now I will always need to go to <A
 href="http://10.10.10.5:7005/">http://10.10.10.5:7005</A> to access my application. 
 <o:p> </o:p>
 Is it the right approach? 
 What should be the best way to do it? I need failover but can compromise
 over load balancing.
 
 We do not want to have extra box for DNS server etc. So I can not have
 DNSName for my cluster.
 <o:p> </o:p>
 Sanjeev </DIV></BODY></HTML>

Hi,
You can create the Server 2012r2 failover cluster first, then import the vms to the cluster CSV.
More information:
Hyper-V: Using Hyper-V and Failover Clustering
http://technet.microsoft.com/zh-cn/library/cc732181(v=ws.10).aspx
Windows Hyper-V 2012 & 8.1 Hyper-V Did Not Find Virtual Machine to Import
http://blogs.technet.com/b/rmilne/archive/2013/10/22/windows-hyper-v-2012-amp-8-1-hyper-v-did-not-find-virtual-machine-to-import.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

2012r2 iSCSI Cluster SAS MPIO

Similar Messages

Maybe you are looking for