Does Microsoft support configuring 2012 R2 failover cluster using nfs mounts?
↧
NFS mounts
↧
Change Subnet mask in Windows 2012/SQL 2012 Always On Cluster
Hello,
We have a three node Windows 2012 cluster and it has SQL 2012 Always on configured on it. Three nodes have incorrect subnet mask values and we would like to change it.
Can anyone please provide the steps to change the subnet mask values ? i saw some blogs and they mention to shutdown or take the cluster offline and change the values as below but the roles in the cluster will still have the old subnet mask value after changing the values using below steps ? I'm kind of confused on how to change and its affect on the whole cluster as this is production.
Any help would be appreciated. Thanks in advance.
Steps to change IP address/Subnet mask:
- Go to Control Panel\All Control Panel Items\Network and Sharing Center\Change adapter settings\
- Right-click Local Area Connection, and then click Properties.
- In the Local Area Connection Properties dialog box, double-click Internet Protocol (TCP/IP).
- In the Internet Protocol (TCP/IP) Properties dialog box, in the IP address box, type the new address.
- In the Subnet mask box, type the subnet mask to 255.255.252.0
↧
↧
Storage spaces direct - STATUS_IO_TIMEOUT
Hi Everyone,
I configured cluster of 4 Supermicro X10DRIservers to test storage spaces direct. Supermicro server configuration:
- 2 x Intel Xeon E5-2640v3 CPU
- 10 x 32GB 2133MHz DDR4 RAM
- 2 x SSD 400GB SATA Intel S3610
- 2 x HDD 2TB SATA Seagate ST2000NX0253
- 6 x SSD 800GB SATA Intel S3610
- Intel X520-DA2 E10G42BTDA Network adapter
All was fine, cluster and S2D were working without any problems. But after a month, I replaced Intel X520-DA2 E10G42BTDA Network adapter on Mellanox ConnectX-3 Pro Ethernet Adapter. After that, I started receiving Warnings in Cluster Events log:
"Cluster Shared Volume 'VD1' ('Cluster Virtual Disk (VD1)') has entered a paused state because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished."
I checked health of physical disks - they fine, also I checked network and found I had about 500K Received Discarded Packets per server. Itlookspretty bad, but I'm not sure. Is it a problem? Orshould I continue my investigation?
↧
How to Activate DR site when Preferredsite Goes Down
We're testing the two site scenario where you have a primary and a DR site using the Site-aware FC. How do you bring up the DR site when the preferredsite goes down? I've tried using fq switch for the cluster service with no success. Is there another process
to bring the cluster up on the DR site in 2016?
↧
Error validating cluster computer resource name (Server 2016 Datacenter Cluster)
An error occurred while executing the test.
The operation has failed. An error occurred while checking the Active Directory organizational unit for the cluster name resource.
The parameter is incorrect
Interesting enough the cluster name was created successfully in the Computers OU and the cluster can be taken offline and brought back online with no problem. The DNS entry is correct and the cluster name pings to the correct IP.
↧
↧
WSFC Virtual IPs and GARP
Where I work we are setting up a new system and I am experiencing a problem I am hoping others have experienced and can offer some recommendations on.
I have setup a new Windows Server 2012 R2 2-node WSFC that is hosting a SQL Server AlwaysOn Availability Group. I have setup AGs before and have never really had problems with them, however now I am starting to see an issue. Our WSFC nodes are on one VLAN and subnet and the clients that connect to SQL (SharePoint servers in this case) are in another VLAN and subnet. Whenever a failover of the AG occurs the SharePoint servers lose connectivity to the AG for approximately 13-15 minutes before connectivity is restored. It is not a routing issue as continuous pings to the WSFC nodes and the WSFC IP never fail, just pings and other connection attempts to the AG listener. It is also not a problem with SQL as I can verify connectivity to a specific AG node.
After looking at this problem with our networking guys the problem appears to be related to gratuitous ARP (GARP). When failover of the AG occurs a GARP request is supposed to update devices on the local network of updated IP/MAC information so that requests to that IP are sent to the right network interface. However I work in a federal government environment and DISA STIGs mandate that infrastructure routers disable GARP (V-5618 for those that are interested https://www.stigviewer.com/stig/infrastructure_router__cisco/2013-10-08/finding/V-5618). This seems to have the effect of traffic outside of the local network timing out after a failover until the entry in the VLANs ARP table expires and gets updated. Disabling that setting for testing showed AG failovers being near instantaneous.
Has anyone encountered this or have any recommendations? I am trying to make the case for multiple NICs on the SharePoint servers so that they can communicate with the SQL servers on the same VLAN, but I am getting push back and am trying to see if there is an alternate solution that can be researched.
I have setup a new Windows Server 2012 R2 2-node WSFC that is hosting a SQL Server AlwaysOn Availability Group. I have setup AGs before and have never really had problems with them, however now I am starting to see an issue. Our WSFC nodes are on one VLAN and subnet and the clients that connect to SQL (SharePoint servers in this case) are in another VLAN and subnet. Whenever a failover of the AG occurs the SharePoint servers lose connectivity to the AG for approximately 13-15 minutes before connectivity is restored. It is not a routing issue as continuous pings to the WSFC nodes and the WSFC IP never fail, just pings and other connection attempts to the AG listener. It is also not a problem with SQL as I can verify connectivity to a specific AG node.
After looking at this problem with our networking guys the problem appears to be related to gratuitous ARP (GARP). When failover of the AG occurs a GARP request is supposed to update devices on the local network of updated IP/MAC information so that requests to that IP are sent to the right network interface. However I work in a federal government environment and DISA STIGs mandate that infrastructure routers disable GARP (V-5618 for those that are interested https://www.stigviewer.com/stig/infrastructure_router__cisco/2013-10-08/finding/V-5618). This seems to have the effect of traffic outside of the local network timing out after a failover until the entry in the VLANs ARP table expires and gets updated. Disabling that setting for testing showed AG failovers being near instantaneous.
Has anyone encountered this or have any recommendations? I am trying to make the case for multiple NICs on the SharePoint servers so that they can communicate with the SQL servers on the same VLAN, but I am getting push back and am trying to see if there is an alternate solution that can be researched.
Joie Andrew "Since 1982"
↧
Windows Hyper-V cluster goes down if one node is up
Hi,We have a two
node Hyper-V CSV Cluster, node 1 is down. As soon as this server comes up all cluster goes down. Currently all VMs are working on Node 2.
What possibly could be the issue?
↧
Cannot validate cluster "You do not have administrative privileges on the server "
Hi
Let me describe the problem:
I have to build a two-node failover cluster. I have this two nodes in a domain which is installed on the third computer. I am log on with domain admin. when running validation tests it gives a message that I do not have administrative privileges on other node.
Please show me a way to fix this.
Regards.
↧
Locked down DNS
Created a 2012 Cluster on Server 2012 R2 Hyper-V and an Availability Group in SQL 2012.
Getting errors that the cluster cannot update DNS.
Cluster is in locked-down environment and cannot update DNS Server (Bind).
Looking for a work-around. Any ideas?
TiA
↧
↧
FCM not loading Properties for configured Hyper-V shares
We have 3 nodes, 2 of which are part of a hyper-v cluster. Many moons ago I configured network shares within FCM, for the last few days when attempting to select properties for specific shares it displays the below:
I have restarted all nodes.
I have confirmed i can PSSession to the server from my PC.
I have confirmed WinRM can communicate to the remote Nodes with:
winrm id -r:ComputerNameI can confirm i do not have a loopback ip configured:
netsh http show ip listenI have confirmed i do not have a proxy configured:
netsh winhttp show proxyI have confirmed that WMI is also working as to be expected.
The issue is happening on certain pc’s in the network, other PC’s in the network can still access it, when using my credentials on the working PC's i am able to view the properties.
Can anyone help me out with this?
↧
Cannot create checkpoint when shared vhdset (.vhds) is used by VM - 'not part of a checkpoint collection' error
We are trying to deploy 'guest cluster' scenario over HyperV with shared disks set over SOFS. By design .vhds format should fully support backup feature.
All machines (HyperV, guest, SOFS) are installed with Windows Server 2016 Datacenter. Two HyperV virtual machines are configured to use shared disk in .vhds format (located on SOFS cluster formed of two nodes). SOFS cluster has a share configured for applications
and HyperV uses \\sofs_server\share_name\disk.vhds path to SOFS remote storage). Guest cluster is configured with 'File server' role and 'Failover clustering' feature to form a guest cluster. There are two disks configured on each of guest cluster nodes: 1
- private system disk in .vhdx format (OS) and 2 - shared .vhds disk on SOFS.
While trying to make a checkpoint for guest machine, I get following error:
Cannot take checkpoint for 'guest-cluster-node0' because one or more sharable VHDX are attached and this is not part of a checkpoint collection.
Production checkpoints are enabled for VM + 'Create standard checkpoint if it's not possible to create a production checkpoint' option is set. All integration services (including backup) are enabled for VM.
When I delete .vhds disk of shared drive from SCSI controller of VM, checkpoints are created normally (for private OS disk).
It is not clear what is 'checkpoint collection' and how to add shared .vhds disk to this collection. Please advise.
Thanks.
↧
Software Updates missing on Node B
Hello,
When running the cluster validation I have "Software Updates missing on Node B" Windows Server 2008 R2 Service Pack 1.
e.g.:
KB3087985 requested by the cluster validation but see below refused by the installation
KB3045645 seems to be only for Windows 7!!!
KB3020338 !!!
When trying to install ie11-Windows6.1-kb3087985-
it seems to be a conflict!!!
Any idea?
Thanks,Dom
Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager
↧
Failover Clustering Fails to Start
Good day all,
Hopefully someone can assist. Ive been running around in circles.
We had a 2 Node cluster configured, then the cluster was destroyed (not the correct way) the 2 servers were shutdown and formatted. Now Im tyring to re-configure a 2 node Cluster again and am running into numerous issues.
Both servers have been rebuilt with Server 2008 Enterprise SP2. - Identical Servers as well as connected to a SAN for Disk Quorum.
Clustering Services were installed successfully on both Nodes and Validation comes back 100% on both Nodes. however when tyring to start the cluster Service it fails with Event ID: 7024 and 1090.
Event ID 7024: Service Specific Error 2
Event ID: 1090: Cluster Service cannot be started on this node because a registry operation failed with error '2'
The user account has admin rights on the computer and network domain.
Ive tried uninstalling the Failover Clustering services.
Even when setting the service to Automatic then trying to create the cluster - it says the computer is already part of a cluster.
Hopefully someone can assist. Ive been running around in circles.
We had a 2 Node cluster configured, then the cluster was destroyed (not the correct way) the 2 servers were shutdown and formatted. Now Im tyring to re-configure a 2 node Cluster again and am running into numerous issues.
Both servers have been rebuilt with Server 2008 Enterprise SP2. - Identical Servers as well as connected to a SAN for Disk Quorum.
Clustering Services were installed successfully on both Nodes and Validation comes back 100% on both Nodes. however when tyring to start the cluster Service it fails with Event ID: 7024 and 1090.
Event ID 7024: Service Specific Error 2
Event ID: 1090: Cluster Service cannot be started on this node because a registry operation failed with error '2'
The user account has admin rights on the computer and network domain.
Ive tried uninstalling the Failover Clustering services.
Even when setting the service to Automatic then trying to create the cluster - it says the computer is already part of a cluster.
↧
↧
Unable to configure server 2016 cluster aware updating.
Initially got a WinRM error when trying to set options in the CAU gui so ran test-causetup which reported the same errors after rule 11 below. It's also reporting several other failures though which are bogus. Rule 3 is giving an error saying PSRemoting is not enabled yet it is and I've even tried "enabling" it using -force. Rule 2 not positive about but know winrm is running and configured and firewall is off. Rule 11 is failing on the cluster name its not a server...
To test PSRemoting I ran this command on the other cluster node and it works BUT if you run it and target the same machine you are on it fails. This happens on both nodes and both nodes are giving all the same errors.
Invoke-Command -ComputerName 90vmhost5 -ScriptBlock { Get-ChildItem c:\ } -credential CM
PS C:\Windows\system32> Test-CauSetup
RuleId : 1
Title : The failover cluster must be available
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 1
RuleId : 1
Title : The failover cluster must be available
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 5
RuleId : 2
Title : The failover cluster nodes must be enabled for remote management via WMIv2
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 6
RuleId : 2
Title : The failover cluster nodes must be enabled for remote management via WMIv2
State : Failed
Severity : Error
FailedMachines : {90VMHost5}
PercentComplete : 11
RuleId : 3
Title : Windows PowerShell remoting should be enabled on each failover cluster node
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 12
RuleId : 3
Title : Windows PowerShell remoting should be enabled on each failover cluster node
State : Failed
Severity : Error
FailedMachines : {90VMHost5}
PercentComplete : 16
RuleId : 4
Title : The failover cluster must be running Windows Server 2012
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 17
RuleId : 4
Title : The failover cluster must be running Windows Server 2012
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 21
RuleId : 5
Title : The required versions of .NET Framework and Windows PowerShell must be installed on all
failover cluster nodes
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 22
RuleId : 5
Title : The required versions of .NET Framework and Windows PowerShell must be installed on all
failover cluster nodes
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 45
RuleId : 6
Title : The Cluster service should be running on all cluster nodes
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 46
RuleId : 6
Title : The Cluster service should be running on all cluster nodes
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 55
RuleId : 7
Title : Automatic Updates must not be configured to automatically install updates on any failover
cluster node
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 56
RuleId : 7
Title : Automatic Updates must not be configured to automatically install updates on any failover
cluster node
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 64
RuleId : 8
Title : The failover cluster nodes should use the same update source
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 65
RuleId : 8
Title : The failover cluster nodes should use the same update source
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 73
RuleId : 9
Title : A firewall rule that allows remote shutdown should be enabled on each node in the failover
cluster
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 74
RuleId : 9
Title : A firewall rule that allows remote shutdown should be enabled on each node in the failover
cluster
State : Succeeded
Severity : Info
FailedMachines : {}
PercentComplete : 82
RuleId : 10
Title : The machine proxy on each failover cluster node should be set to a local proxy server
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 83
RuleId : 10
Title : The machine proxy on each failover cluster node should be set to a local proxy server
State : Failed
Severity : Warning
FailedMachines : {90VMHost5, 90VMHost6}
PercentComplete : 91
RuleId : 11
Title : The CAU clustered role should be installed on the failover cluster to enable self-updating
mode
State : Started
Severity : Info
FailedMachines : {}
PercentComplete : 92
RuleId : 11
Title : The CAU clustered role should be installed on the failover cluster to enable self-updating
mode
State : Failed
Severity : Warning
FailedMachines : {VMCluster}
PercentComplete : 100
WARNING: <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859027" Machin
e="90VMHost5.pacific.local"><f:Message>The WinRM client sent a request to an HTTP server and got a response sa
ying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support
the WS-Management protocol. </f:Message></f:WSManFault>
WARNING: Connecting to remote server 90VMHost5 failed with the following error message : The WinRM client sent
a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usual
ly returned by a HTTP server that does not support the WS-Management protocol. For more information, see the a
bout_Remote_Troubleshooting Help topic.
WARNING: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL wa
s not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
ModelId : Microsoft/Windows/ClusterAwareUpdating
SubModelId :
Success : True
ScanTime : 2/1/2017 4:10:32 PM
ScanTimeUtcOffset : -08:00:00
Detail : {90VMHOST5, 90VMHOST5}↧
Access denied in Failover Cluster manager for non-domain admin with read-only or full control on cluster
Hello all,
I observe the following:
When giving a user explicitely permissions to the cluster with Grant-ClusterAccess <domain>/<user>
The user cannot connect to the cluster in the failover cluster manager.
Managing the cluster via PowerShell commandlets does work, no messages about administrative privileges is shown. Only FOCM cannot connect for this user. What can I do to fix this?
You know you're an engineer when you have no life and can prove it mathematically
↧
Cluster Group Failed after Network Lost
hi all,
I have a two node cluster with Windows Server 2008 Enterprise and SQL Server 2008.
the problem is when active node lost the LAN connection, the "cluster group" in Cluster Core Resources not automatically transfer to other node.
Event ID-1205 Resource Control Manager The Cluster service failed to bring clustered service or application 'DTC01-A' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Event ID-1069 Resource Control Manager Cluster resource 'IP Address 10.20.51.122' in clustered service or application 'DTC01-A' failed.
any help and possible solution.
Thanks,
k.rijal
I have a two node cluster with Windows Server 2008 Enterprise and SQL Server 2008.
the problem is when active node lost the LAN connection, the "cluster group" in Cluster Core Resources not automatically transfer to other node.
Event ID-1205 Resource Control Manager The Cluster service failed to bring clustered service or application 'DTC01-A' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Event ID-1069 Resource Control Manager Cluster resource 'IP Address 10.20.51.122' in clustered service or application 'DTC01-A' failed.
any help and possible solution.
Thanks,
k.rijal
↧
Cluster-Aware Updating Readiness "Errors"
I have a two-node Windows Server 2012 failover cluster. The Windows firewall is disabled on both nodes.
When I log on to one of the nodes (bcs-vmhyperv2), and run the Cluster-Aware Updating tool to analyze the cluster readiness, I receive this result:
When I log on to the other node and run the tool, I received the same two errors. The problem computer is always the local computer.
I know that PowerShell remoting and WINRM are enabled! So, the "resolution" steps don't help.
Here's proof:
If I log on to a different Windows Server 2012 system (not one of the cluster nodes), and run the tool, I receive no errors:
In fact, I setup CAU and used it to apply the latest set of Windows Updates from the third computer.
Why can't I use it from the cluster nodes? How do I fix it?
-Tony
↧
↧
2 node failover clustering
please explain , how to make 2 node failover cluster , both nodes are directly connected to 5nos 60 bay HGST JBODs .
Thanks
Muhammed Rashid
↧
Windows NLB cluster only one node remains active always even after rebooting
Hi Team,
I have server A and server B running in windows NLB cluster ,running exchange 2013 CAS roles,anti virus is runing on server A and not installed on server B,the cluster IP is currently getting connected to server A which has anti virus.
For troubleshooting an issue i want to make the server B active to confirm if anti virus is casuing the issue,but the problem is even if i restart server A ,server B becomes the active node only untill server A restarts sucessfully,once server A is up it becomes the active node again,how do i make node B active?
I have server A and server B running in windows NLB cluster ,running exchange 2013 CAS roles,anti virus is runing on server A and not installed on server B,the cluster IP is currently getting connected to server A which has anti virus.
For troubleshooting an issue i want to make the server B active to confirm if anti virus is casuing the issue,but the problem is even if i restart server A ,server B becomes the active node only untill server A restarts sucessfully,once server A is up it becomes the active node again,how do i make node B active?
TechGUy,System Administrator.
↧
Three VMs are "stuck" (locked) on one node.
I'm trying to do maintenance on one node running ws2012dc. All but three VMs moved over successfully. I think this is related to a failed DPM backup job since I hadn't enable serialized CSV backups. I tried restarting volume shadow services but it's stuck in the "stopping" state in services.msc. I see the VSSVC.exe is still running but i'm not sure how dangerous it is to kill this process? The VM's have a status as running (locked) in failover cluster manager. I tried turning off one of the VMs but i still wasn't able to override the locked status of it. Hyper-v manager reports the VM as stopped, but failover manager reports it as still running (locked).
[Main Instruction]
Failed to Live migrate virtual machine 'SCVMM sql2 Resources'
[Expanded Information]
The action 'Move' did not complete.
Error Code: 0x80070057
The parameter is incorrect
Not sure on how to solve this. Any suggestions?
↧