Hi,

We are testing our new scale out file server and are having major issues with performance.  

We have 2 server clustered running the sofs attached to a shared jbod with 8x 4tb sas drives.  We have pooled and added the disks to a csv and begun hosting test vm's on the new share.

When testing the volumes locally we get 1,000mb/s of throughput read and write in a spanned volume.

When testing accessing the same volume via the sofs share we are seeing 400mb/s of read and 10-50mb/s of write!!!

This performance is completely unacceptable.  Is this due to the sofs forcing write through and no write caching?

All servers have quad port 10gb NIC's with SMB direct.  The NIC's and network infrastructure have been tested and all run at line speed.  The performance dip is clearly as a result of the sofs tech.

If we create a standard share and copy between servers we get full speeds again.

All servers have all the latest updates and hotfixes applied.  

Any suggestions as this is going to completely kill and hopes we had of using this technology.

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,

I am hoping someone would be able to help me as I have looked on the internet for an answer to this. We deploy a number of servers that are configured using Powershell. I am in the process of creating a clustered WIN2K8R2 cluster with MSMQ. I am able to do this successfully through the Failover Mgr with no issues.  In addition, I can do this via Powershell (code listed below) with one caveat.

However, when I create the same exact MSMQ in Powershell, I am unable to right click on the MSMQ service to manage it as the "Manage MSMQ" is missing when I right click on it. The settings are the same, including dependencies. The only difference I have been able to find is the icon in the Failover Manager shows the Service as a Generic Service icon when created in Powershell, but when it is created in the GUI it shows up as the MSMQ icon. I was able to verify this in the registry in HKLM\Cluster\Groups\<GUID>\: GroupType HEX: 68 for msmq icon. When it is the Generic Service icon it is HEX: 270f. When I change it from 270f to 68, the icon changes in Failover Manager and I am able to open, but then I get an invalid handle and I am unable to manage it.

This is causing an issue, because I want to automate this build and hand it over, but they would be unable to manage it except by programming which the operators are not ready for.

Here is the code which I have created in Powershell:

    Write-host "Configuring MS MSMQ Cluster Failover..."
    $CluName = "Cluster Name"
    $ClsMSMQName = $CluName.Name + "MSMQ"
    $ClsMSMQResourceName = "MSMQ-" + $ClsMSMQName
    $Response = Read-host "Enter the IP Address of the Clustered MSMQ"

    $ClsIpRes = get-clusterresource "Cluster IP Address"
    $MSMQIpAddr = New-Object Microsoft.FailoverClusters.PowerShell.ClusterParameter $ipres,Address,$Response

    Add-ClusterServerRole -Name $ClsMSMQName -Storage "Cluster Disk" -StaticAddress $MSMQIpAddr.value
    # Add the MSMSMQ Service to the new Server Role
    Get-ClusterGroup $ClsMSMQName | Add-ClusterResource -Name $ClsMSMQResourceName -ResourceType "MSMQ"
    # Create Dependencies for the MSMQ group
    Add-ClusterResourceDependency $ClsMSMQResourceName $ClsMSMQName
    Add-ClusterResourceDependency $ClsMSMQResourceName "Cluster Disk"
    # Start MSMQ group
    Start-ClusterGroup $ClsMSMQName

You would just have to change "Cluster Disk" and "Cluster Name".

Thank you

Hi,

Not sure if I'm in the correct forum. If I am I apologize.  I need some advice.  

I have created a 2-node failover cluster with 2 HP Blades.  I also currently have 2 NAS Servers (HP X1600 24tb servers running 2008 Storage server) -- The ultimate goal would be to combine all of the storage space from the NAS's into 1 volume addressable by the failover cluster. (As well as disk space from any additional NAS's added in the future.)

Right now, I can add the ISCSI disk space from the NAS Targets as different volumes under cluster shared volumes.  Because of the 16TB limit in the ISCSI target, I essentially have 2 ISCSI disks on each NAS. One for 16TB, and the other for 4TB (The NAS Drives are configured for RAID 5 so there's a 4TB Loss.)  So, I have 4 ISCSI disks in the cluster, each as their own volume.

Any thoughts on making the 4 drives addressable as one volume? 

Regards,

-Eric

I have a 8 node cluster with Hyper-V, which will be 10 nodes when it's finally done.
Recently I've been try to add nodes and though that went fine, after about a week I could not open the Failover Cluster Manager anymore.
After some checking I found out that the latest added node was giving problems.

VM's on the node still run and function properly, but most Powershell commands result in a "The requested object does not exist. (Exception from HRESULT: 0x80010114)".

I can suspend the node with Suspend-ClusterNode, but draining roles was unsuccesful in one case.
In the other there were no VM's on the node so suspending went fine.

What I did find out was that when I tried to ping the node from another, proper functioning node, it took a while before the pinging started. It felt like the interface had to come back online on the problem node.
After that, I could add the cluster to the Failover Cluster Manager. However, Powershell commands still give a 0x80010114 error or a CIM error for when I use Get-NetAdapter.

A reboot resolves the problem, but only for about a week.

I know there is a topic with the same title already, but the wbemtest en rollup update "answer" is totally unclear to me why I should change something with wbemtest, or why to install updates that to me have nothing to do with this problem.

Before I did the ping test from a functioning node I pinged my DC and another node from the problem node just fine.
No waiting at all.

The cluster has three networks. Management (host only), Live Migration and iSCSI (also a VMSwitch for certain VM's).

I have no idea where to look. Evenviewer doesn't give me anything I can work with that I can find...

Dear All,

Kindly help me for the above.

I have tried out the following:

1. time sync with DC - checked
2. Re-install the feature and restart the servers
3. check registry key value winreg - local service account read only and added domain admin account

2 days googling, no luck

Generate cluster report and error error_mod_not_found (126) reported.

Thanks

This is probably a silly question so i apologise in advance, but i have a clustered 2012 file server, and I want to enable Data Deduplication. I have the role installed on both servers in the cluster. I also know that to enable it on a single server, you right-click the volume in server manager and click 'configure data deduplication'. Do i need to enable it any differently when using a cluster so that it will work on the cluster across both members seemlessly? Or do i just select the cluster file server in server manager and right click the volume like before?

many thanks.

Hi Guys,

I am getting below error message while validate a configuration of failover cluster manager.

I have checked services and cluster services are started. I have rebooted both the cluster server, but still getting the same error message. Any further help will be appreciated.

Thanks

Hello,

I have recently deployed 2 node cluster based on Windows Server 2012 R2. CNO and corresponding IP is online but Microsoft DTC role name is not coming online.

Error / Warning Logs is pasted for your reference:

00000bc0.0000109c::2014/06/01-19:17:07.001 WARN  [RES] Network Name: [NNLIB] LogonUserCall fails for user xxxx$: (useSecondaryPassword: 0), password length is 0
00000bc0.0000109c::2014/06/01-19:17:07.064 WARN  [RES] Network Name: [NNLIB] LogonUserEx fails for user xxxx$: 1326 (useSecondaryPassword: 1)
00000bc0.00000c20::2014/06/01-19:17:07.065 WARN  [RES] Network Name <Cluster Name>: Identity: Get Token Request, currently doesnt have a token!
00000bc0.000011c4::2014/06/01-19:17:07.065 WARN  [RES] Network Name <xxx>: AccountAD: Slow operation has exception (6)' because of '::ImpersonateLoggedOnUser( GetToken() )'

00000bc0.00001330::2014/06/01-19:17:07.071 ERR   [RES] Network Name <xxx>: Online thread Failed: (0)' because of 'Initializing netname configuration for xxx failed with error 6.'
00000bc0.00001330::2014/06/01-19:17:07.071 ERR   [RHS] Online for resource xxx failed.
000006b4.000004d8::2014/06/01-19:17:07.071 WARN  [RCM] HandleMonitorReply: ONLINERESOURCE for 'xxx', gen(58) result 5018/0.
000006b4.000004d8::2014/06/01-19:17:07.071 ERR   [RCM] rcm::RcmResource::HandleFailure: (xxxx)
00000bc0.000011c4::2014/06/01-19:17:07.072 ERR   [RES] Network Name <xxxx>: AdminShare: OnCloseBase, Error Already Closing, previous state: Closing/Ending

Hello.

Ive just bought a new server for testing purposes, and i want to setup a Windows File Cluster - almost done :)

The File Cluster is a Two noded Windows Server 2012 R2 Standard Cluster. 

Now i want to know, when the next Windows Server edition ( Windows Server 2014 or Windows Server 2015) gets released - would i then be able to add 2 new nodes to the File Cluster, and remove the 2 old Windows Server 2012 R2 nodes - and let the cluster run?

Or do i have to create a new one?

Its also a requirement, that all the data remains intact on the .vhdx disk from the iSCSI host.

Datatechnician

Hi all!

I recently had to destroy my cluster.  I recreated the cluster ensuring that the previous cluster name was purged from AD.  I had no issues recreating the cluster.  I went through the validation of the second node, again, no issues.  However, when I try to finish the addition of the second node, the wizard hangs and displays "Waiting for notification that node mynode2 is a fully functional member of the cluster". 

The summary report shows the following:

Cluster service on node mynode2 did not reach the running state. The error code
is 0x5b4. For more information check the cluster log and the system event log
from node mynode2. This operation returned because the timeout period expired.

The Event log shows the following:

The firewall and Symantec endpoints have been disabled.  I have also tried cleaning up the nodes and re-installing the Failover Cluster but the issue persists.  Is there anything in particular I should be looking for in the Cluster Log? 

Help or hints would be much appreciated.

Dear All

we have problem with quorum drive.we facing bellow error while validating cluster configuration

Failed to write file data on cluster disk 0 partition 2, failure reason: The disk structure is corrupted and unreadable

pls help us we are stuck

sunil patel

SUNIL PATEL SYSTEM ADMINISTRATOR

I am very new to sever 2008 let alone clustering...

And i am having a problem....i dont even know if my questions are correct/valid

1. So, i have two machines (VMs actually) that run Windows Server 2008 R2 SP1 each with a single Network Interface card. Say M1 and M2

2. I want to make a two-node NLB Cluster out of these two machines

3.  I have turned on the NLB on both the machines from Servermanager.

4. On M1, i have opened the NLB Manager and started creating a new cluster.

     a. Right click on Network Load balancing clusters-->Create new cluster.

     b. First step is to connect a host. since i want this (machine on which i am setting NLB) to be a part of NLB, i gave the machine name and clicked connect

     c. able to connect and it gives me the option to choose the interface to use. I have only one NIC and therefore i have only one option to choose the local area connection.

     d. Next comes the host parameters to add, the dedicated IP Address. So, here i entered the same ip address of this machine. IS THIS CORRECT? (this is where non-clustered traffic comes in?)

     e. Next for the cluster parameters, i have added an unassigned static ip address (given by my admin) as the Cluster Ip Address. IS THIS CORRECT? (this is where the clustered traffic comes in?)

     f. i have chosen the multi-cast mode for NLB clustering and entered the FQDN of the cluster

    f. Now, when i hit next, i am able to setup the cluster BUT, i cannot use it. i mean i cannot add another host because it says un-identfied network

pinging the Dedicated IP Address on M1 is working

pinging the cluster IP Address on M1 is working. however ping -a <clusterIPAddress) doesn't resolve the name of the cluster

pinging the Dedicated IP Address of M1 from M2 is NOT working

ping the cluster IP Address form M2 is NOT working.

Basically my question is: For dedicated ip address i am using the same IP as of Machine M1 and for cluster IP address i am using some static IP Address..

is that right?

any help greatly appreciated....i have read a lot of documentation, but somehow i could not understand it...can anyone simplify this for me

Hi,

"Unexpectedly Mapped LUNs are disappeared, Then we have Installed Multi path driver after installation LUN disks are showing as unallocated and there was no data present in server."

Regards

Rajesh

Hi *.*

I'm experiencing a weird problem.

I've a Fujitsu CX420 S1, a sort of 2 blades server with a shared SAS controller, 4 900Gb SAS disks and 2 200GB SSD disks.

Installed 2012 R2 Std (the server is certified 2012 R2) on both blades, enabled Hyper-V role, configured SS, created a quorum volume without tiering, created a cluster, created a tiered volume, added to CSV, created a VM on it.

If the CSV is, for example on node1 and VM is on the same node, everything works at full speed (200MB/sec write & 300MB/sec read).

If I move the CSV on the opposite node the speed drop to near zero (600Byte/sec write & 20MB/sec read)

It looks like that the CSV is working always in redirected mode and using the HB for passing traffic but not even at 1GBit/sec

Please help!

I'm available for further info, just I'm running out of time to solve the problem (I've to deliver this cluster) before to fall back to the old method of a volume for every VM (no CSV).

Thanks,

Alessio

I have a two node NLB cluster configured. It all seems to be working fine (I can see requests being directed to both nodes) but soon after config is completed and convergence has taken place I get "host unreachable" errors in NLB manager on both nodes and I can no longer control a remote node in the cluster.

If I turn off the Windows firewall on both nodes in the cluster the errors stop and I can resume controlling remote nodes. This is strange as I have all the automatically created NLB firewall rules present (see below).

Unless I disable the firewalls this is stopping me from taking a node into "drainstop"

Anyone know what firewall rule I need to add to fix this?

Hibs Ya Bass!

We have a Windows Server 2008 R2 Cluster set up that hosts SQL Services. We need to move the backend storage for the SQL Data/Log Drives to another storage. Can I -

1. Shut down SQL (Drives:F,G) and Cluster services
2. Make new storage available with NEW Drive letters H, I
3. Copy all files from Drives F,G to Drives H,I
4. Rename old Drives F,G to R,S (essentially discard)
5. Rename new Drives H,I to F,G (original drive names)
6. Restart SQL and Cluster services

In other words, do SQL and the Cluster service operate purely on the Drive Letter where this might work? Or does it use some identifier behind the scenes which would cause the cluster to break inspite of the new Drives having the same Drive Letter?

If it will break, is there another way to do this?

Thanks in advance,
Jake.

Hi all;

This is my scenario:

I have installed Windows Server 2012 on two servers. Then enabled Windows Clustering feature on it. The shared storage is based on Fibre Channel technology. Each server has 4 NICs and I have splitted them as followis:

• One NIC for remote mangement of the servers with the range of 172.16.105.0/24.
• One NIC dedicated for heartbeat communication.
• Two NICs has been bundled together with NIC Teaming feature of the operating system.

But as you see in the following figure there are 4 Cluster Network links:

Is it normal?

Thanks

Please VOTE as HELPFUL if the post helps you and 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.

Hi,

We currently have a 4-node Server 2012 R2 Cluster witch hosts among other things, a 3 node Guest Cluster running a single clustered file service.  

Around once a week, the guest cluster node that is currently hosting the clustered file service will fail.  It's as if the VM is blue screening.  That in itself is fairly anoying and I'll be doing all the updates and checking event log for clues as to the cause.  

The problem then is that whichever physical cluster node that is hosting the VM when it fails,  will not unlock some of the VM's files.  The Virtual machine configuration lists as Online Pending.  This means that the failed VM cannot be restarted on any other cluster node.  The only fix is to drain the physical host it failed on, and reboot. 

Looking for suggestions on how to fix the following.

1. Crashing guest file cluster node

2. Failed VM with shared VHDX requiring Phyiscal host reboot.

Event messages for the physical host that was hosting the failed vm in order that they occured.

• Hyper-V-Worker: Event ID 18590 - 'FS-03' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x9E, ErrorCode1: 0x6C2A17C0, ErrorCode2: 0x3C, ErrorCode3: 0xA, ErrorCode4: 0x0.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID 36166B47-D003-4E51-AFB5-7B967A3EFD2D)
• FailoverClustering: Event ID 1069 - Cluster resource 'Virtual Machine FS-03' of type 'Virtual Machine' in clustered role 'FS-03' failed.
• Hyper-V-High-Availability: Event ID 21128 - 'Virtual Machine FS-03' failed to shutdown the virtual machine during the resource termination. The virtual machine will be forcefully stopped.
• Hyper-V-High-Availability: Event ID 21110 - 'Virtual Machine FS-03' failed to terminate.
• Hyper-V-VMMS: Event ID 20108 - The Virtual Machine Management Service failed to start the virtual machine '36166B47-D003-4E51-AFB5-7B967A3EFD2D': The group or resource is not in the correct state to perform the requested operation. (0x8007139F).
• Hyper-V-High-Availability: Event ID 21107 - 'Virtual Machine FS-03' failed to start.
• FailoverClustering: Event ID 1205 - The Cluster service failed to bring clustered role 'FS-03' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.