Hi,

I have two physical servers (Windows 2012 R2) both running a single Apache HTTP Server instance. Can I use Microsoft Network Load Balancing service to load balance the Apache instances? This mean colocating NLB with the Apache instances.

Thanks,

Eddie

 im planning to make Hyper V cluster with low cost by using current multi old servers as passive and only one new server with high resources as active with one HP storage that accept both SAN and ISCASI connectivity

i will connect primary server with SAS and old servers with ISCASI i this possible

please note i will collect old servers to be same cores and ram for primary server?

Dear Team,

I have a question, I have two web servers converged with NLB and:

1- I need to know what is the physical server that I am connected to from PC itself.

2- I need to know from each server who are the clients (IP) that uses each one.

I need the answers for troubleshooting purpose...

Environment and problem:

2 servers 2012 in a Microsoft failover clustering which is going to be used for SQL AlwaysON. There is no common storage between the servers, since I do not need one. These are both virtual servers running on ESXi environment 5.5

The servers are using a heartbeat network - 10.0.160.51 (node A) and 10.0.160.52 (node B) . Servers are across datacenters and we are using OTV to extend the heartbeat network from one site to another. The cluster validation report is all Green. But I am getting errors for heartbeat network cannot be reached by another node and heartbeat network partitioned errors - Event ID 1126, 1127 And 1129.

The errors are coming every 10-15 min interval. Here is the cluster.log events at one particular time when I got those errors (11:33:49 and 11:33:54 am - 8/25/2015)

Any help will be greatly appreciated. I also have another cluster using the same heartbeat network and I do not get these errors in the other cluster.

John M. Couch

Hi All,

I am facing one issue in my existing Fail over clustering, as we have two node clustering.

both the server showing the IP conflict for virtual IP (Cluster IP) and failover is not happening.

Error :

Cluster IP address resource 'Cluster IP Address' cannot be brought online because a duplicate IP address '192.168.17.179' was detected on the network.  Please ensure all IP addresses are unique.

192.168.17.179 is my virtual IP.

"Ethernet adapter Private:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Citrix PV Network Adapter #0
   Physical Address. . . . . . . . . : 1A-54-16-4F-D2-F8
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.17.178(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.17.179(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled"

(This is my one of the private network adapter setting for heartbeat)

here i see the 179 ip, and only this is the network adapter where i get 179.

Please suggest.

Thanks,

rizwan

Hi Guys,

NLB is having issue after power trip on hyper v server. Primary node status turns to "Converging".
We did try to remove and re-add note into NLB cluster, it is seem same as screen below. 
Troubleshooting had been done as below:
1. Add and remove Node.
2. Repair Network.
3. Restart server and services.
4. Each each node can ping to each node's NLB and Public IP.

We found all the outlook connection establish via UGROEXCH02, UGROEXCHT03 is idle.

Any idea?

Darren Lee

Hi Guys,

I know this might sound basic to most of you.

We are having a single site, having a single DC, we don't have any redundancy for our DC. Can you please suggest, if we implement a  secondary Domain controller will it automatically take over  in case of the primary server down. 

If any of you have the disaster recovery procedures for this kind of scenario , please share it to me.

Thanks in advance,

R.Kalaiselvan

Hi

we have the server geting rebooted by a bugchk error for netft.sysPlease let me know if we have any fix for this issue. i am not sure wht is causing the issue on the server

the server is windows 2008 R2 Datacenter and it is on the HyperV cluster

Thanks in advance

On this posting, I detailed a simple two node Server 2012 R2 cluster configured with a single file server role.  Both nodes accessing shared iSCSI storage.  Client system is performing a simple looped 64 KB read on a file share from the clustered server.  This test applet will fail any time the ReadFile() API fails.

When one node experiences a complete power loss, the other node will take over and no failure will occur on the client system (other than an ~30 second delay where the synchronous ReadFile() API does not return).  This was detailed in the other post. The key point is that failover completed successfully and NO failure was seen on the client PC.

I want to test out a different failover scenario so with Node 1 being the current host, and the owner node for the file server role, quorum disk, and shared storage, I simulate a catastrophic failure of Node 1’s iSCSI storage.  The OS itself boots from a virtual ATA drive so the OS drive will remain alive.  What I do is go into device manager, find the NIC(s) that are configured for the iSCSI network, and then I disable them.  This causes all iSCSI I/O activity to fail.  When I perform this test, the following is seen from the client PC:

• 11:20:01 - Node 1 loss of iSCSI shared storage
• 11:22:01 - Synchronous ReadFile() returns after 120 seconds with ERROR_INVALID_HANDLE
• 11:22:20 - CloseHandle() completes successfully after 19 seconds

I understand the 120 second delay.  It’s a combination of the iSCSI link down timer as well as the MPIO PDO remove period timer.  What I don’t understand is why the request failed.  I expected a failover and successful completion of the ReadFile like I saw when I did a power loss of Node 1.

What’s interesting is that Windows did move the host server, file server, and disk storage, to Node 2.  So a failover did occur.  At least this time it did. Other times, I have seen the file server role stopped.  It appears that the failover occurred immediately after the client PC received the read failure.  Why not complete the failoverbefore failing the client ReadFile request?  Are there timeout adjustments I could experiment with?

Here is Node 1's event log which shows the failover sequence from Node 1's perspective starting just after the catastrophic iSCSI loss on Node 1:

   ProviderName: Microsoft-Windows-FailoverClustering

TimeCreated                     Id LevelDisplayName Message
-----------                     -- ---------------- -------
7/29/2015 11:20:06 AM         1132 Information      Cluster network interface 'TESTCLUSTER1 - Ethernet 2' for node 'TESTCLUSTER1' on network 'Cluster Network 1' was removed.
7/29/2015 11:21:38 AM         1649 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has taken more than one minute to respond to a control code. The control code was 'STORAGE_GET_DISK_INFO_EX'.
7/29/2015 11:22:01 AM         5264 Information      Physical Disk resource 'd47df305-c3a6-4bbe-8475-48e1398bbee6' has been disconnected from this node.
7/29/2015 11:22:01 AM         5264 Information      Physical Disk resource 'b543b5ab-67c9-4836-89a1-ae5636916de5' has been disconnected from this node.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state Online to state ProcessingFailure.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state ProcessingFailure to state WaitingToTerminate. Cluster resource 'Cluster Disk 1' is waiting on the following resources: .
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state WaitingToTerminate to state Terminating.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state Terminating to state DelayRestartingResource.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state Online to state ProcessingFailure.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state ProcessingFailure to state WaitingToTerminate. Cluster resource 'Cluster Disk 2' is waiting on the following resources: File Server (\\DATAFS).
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'File Server (\\DATAFS)' in clustered role 'DATAFS' has transitioned from state Online to state WaitingToTerminate. Cluster resource 'File Server (\\DATAFS)' is waiting on the following resources: .
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'File Server (\\DATAFS)' in clustered role 'DATAFS' has transitioned from state WaitingToTerminate to state Terminating.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'File Server (\\DATAFS)' in clustered role 'DATAFS' has transitioned from state Terminating to state WaitingToComeOnline. Cluster resource 'File Server (\\DATAFS)' is waiting on the following resources: Cluster Disk 2.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state WaitingToTerminate to state Terminating.
7/29/2015 11:22:01 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state Terminating to state DelayRestartingResource.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state DelayRestartingResource to state OnlineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state OnlineCallIssued to state ProcessingFailure.
7/29/2015 11:22:02 AM         1633 Information      The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed or an offline state. This may impact the availability of the clustered role.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state ProcessingFailure to state WaitingToTerminate. Cluster resource 'Cluster Disk 1' is waiting on the following resources: .
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state WaitingToTerminate to state Terminating.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 1' in clustered role 'Cluster Group' has transitioned from state Terminating to state CannotComeOnlineOnThisNode.
7/29/2015 11:22:02 AM         1153 Information      The Cluster service is attempting to fail over the clustered role 'Cluster Group' from node 'TESTCLUSTER1' to node 'TESTCLUSTER2'.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state DelayRestartingResource to state OnlineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state OnlineCallIssued to state ProcessingFailure.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state ProcessingFailure to state WaitingToTerminate. Cluster resource 'Cluster Disk 2' is waiting on the following resources: File Server (\\DATAFS).
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state WaitingToTerminate to state Terminating.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'File Server (\\DATAFS)' in clustered role 'DATAFS' has transitioned from state WaitingToComeOnline to state OfflineDueToProvider. Cluster resource 'File Server (\\DATAFS)' is waiting on the following resources: Cluster Disk 2.
7/29/2015 11:22:02 AM         1203 Information      The Cluster service is attempting to bring the clustered role 'Cluster Group' offline.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster IP Address' in clustered role 'Cluster Group' has transitioned from state Online to state WaitingToGoOffline. Cluster resource 'Cluster IP Address' is waiting on the following resources: Cluster Name.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Name' in clustered role 'Cluster Group' has transitioned from state Online to state WaitingToGoOffline. Cluster resource 'Cluster Name' is waiting on the following resources: .
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Name' in clustered role 'Cluster Group' has transitioned from state WaitingToGoOffline to state OfflineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Disk 2' in clustered role 'DATAFS' has transitioned from state Terminating to state CannotComeOnlineOnThisNode.
7/29/2015 11:22:02 AM         1204 Information      The Cluster service successfully brought the clustered role 'DATAFS' offline.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Name' in clustered role 'Cluster Group' has transitioned from state OfflineCallIssued to state OfflinePending.
7/29/2015 11:22:02 AM         1153 Information      The Cluster service is attempting to fail over the clustered role 'DATAFS' from node 'TESTCLUSTER1' to node 'TESTCLUSTER2'.
7/29/2015 11:22:02 AM         1203 Information      The Cluster service is attempting to bring the clustered role 'DATAFS' offline.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'DATAFS' in clustered role 'DATAFS' has transitioned from state Online to state WaitingToGoOffline. Cluster resource 'DATAFS' is waiting on the following resources: .
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'DATAFS' in clustered role 'DATAFS' has transitioned from state WaitingToGoOffline to state OfflineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'IP Address 10.18.236.0' in clustered role 'DATAFS' has transitioned from state Online to state WaitingToGoOffline. Cluster resource 'IP Address 10.18.236.0' is waiting on the following resources: DATAFS.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'DATAFS' in clustered role 'DATAFS' has transitioned from state OfflineCallIssued to state OfflinePending.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Name' in clustered role 'Cluster Group' has transitioned from state OfflinePending to state OfflineSavingCheckpoints.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster Name' in clustered role 'Cluster Group' has transitioned from state OfflineSavingCheckpoints to state Offline.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster IP Address' in clustered role 'Cluster Group' has transitioned from state WaitingToGoOffline to state OfflineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster IP Address' in clustered role 'Cluster Group' has transitioned from state OfflineCallIssued to state OfflineSavingCheckpoints.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'Cluster IP Address' in clustered role 'Cluster Group' has transitioned from state OfflineSavingCheckpoints to state Offline.
7/29/2015 11:22:02 AM         1204 Information      The Cluster service successfully brought the clustered role 'Cluster Group' offline.
7/29/2015 11:22:02 AM         1641 Information      Clustered role 'Cluster Group' is moving to cluster node 'TESTCLUSTER2'.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'DATAFS' in clustered role 'DATAFS' has transitioned from state OfflinePending to state OfflineSavingCheckpoints.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'DATAFS' in clustered role 'DATAFS' has transitioned from state OfflineSavingCheckpoints to state Offline.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'IP Address 10.18.236.0' in clustered role 'DATAFS' has transitioned from state WaitingToGoOffline to state OfflineCallIssued.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'IP Address 10.18.236.0' in clustered role 'DATAFS' has transitioned from state OfflineCallIssued to state OfflineSavingCheckpoints.
7/29/2015 11:22:02 AM         1637 Information      Cluster resource 'IP Address 10.18.236.0' in clustered role 'DATAFS' has transitioned from state OfflineSavingCheckpoints to state Offline.
7/29/2015 11:22:02 AM         1204 Information      The Cluster service successfully brought the clustered role 'DATAFS' offline.
7/29/2015 11:22:02 AM         1641 Information      Clustered role 'DATAFS' is moving to cluster node 'TESTCLUSTER2'.

Hi,

WE HAVE A WINDOWS IIS SERVER with windows 2008 R2.We want to create a failover for the same which is member of some domain.We want the data sync between these two and failover is required.

Can some body explain how could i achieve this.

Thanx in advance

I am running a powershell script to get cluster information.  The script works perfectly sometimes but sometimes fails on the get-cluster -domain command.  It will fail and then maybe a half hour later it will work.  Here is the exact error:

Message: Could not retrieve the list of clusters on the network.  A remote API error occurred.

ErrorCode: -2147022769

Any ideas on how to track down exactly what the problem is and correct it?

I am in the process of building a new physical cluster nodes using Windows 2012r2.

We have 1 Raid1 Volume for OS and 1 Raid1 Volume for pagefile. We also have 2 Xterme IO cards installed in the system. I notice in disk manager the OS and PF drive are coming up as disk 21 and 22. The Xterme IO drives are disk 0 and 1 and the rest of the SAN attached drivers are disk 2-20. 

My question is does the drive with the OS installed need to be disk 0? Does it matter? Does it matter to the Cluster?

Before the SAN drivers were visible to the server the OS drive was disk 2 once the SAN drives were scanned and became visible the OS drive became disk 21.

Thanks for the help on this.

HI,

IS IT POSSIBLE TO CREATE A THIN CLIENT ARCHITECTURE UNDER A DOMAIN.BASICALLY I WANT TO KNOW THE COMPLETE CONFIGURATION OF SERVERS AND CLIENTS CONFIGURATION FOR THIN CLIENTS WITHOUT VMs.

CAN ANYBODY SUGGEST ME THE ARCHITECTURE AND CONFIGURATION MANUALS FOR THE ABOVE SAID.

THANKS IN ADVANCE>

Hi,

I have a failover cluster running Windows 2012 and hosting a DC and an Exchange 2010. Both VMs are running Windows 2008 R2.

I have several errors in the event viewer. Some errors recommend running the Cluster Validation Wizard.

My question is:

Is safe to run the Cluster Validation Wizard in a production environment?

I don't want to lose or corrupt data.

Thanks in advanced.

Dear Support team, I have two server and NLB is installed on them.

Everything was working fine until one day i got this error message and I don't know why.

Now I can find my two servers under my cluster, and also can't ping the between two servers using IP or Name!!!

Both server are on same switch and both can ping domain server, Firewall is off and there is no antivirus to block any traffic.

can you please advice on how to return NLB the way it was installed...?

hi, 

I wnat to setup a 3/4 node cluster.

I know how to do 2 node fail over cluster with windows server 2012 R2.

I just want to know how to make a cluster node always as standby in case of any node failure in a 4/8 node cluster environment.

where to do the configurations or settings to make a node as standby node for fail over.

thanks in advance

Hi All,

I'm new to clustering,and having a two node cluster. I need write a piece of code to get the Cluster IP address. Below is the way i'm following

1) Read all resource entries from the registry path "HKLM\Cluster\Resources"

2) Parse through all the entries and check for the 'Name' key

3) Get the 'Address' property of the resource name "Cluster IP address"

This works fine for me. But now the same code has to work for other languages also(Japanese) and my code is failing with this string comparision of "Cluset IP Address". I cann't hard code it for every language.

 Is there any other way/ any API  to get the Cluster IP address? Please help me to get the solution.

Thanks in advance

Regards

Sree

Hi,

We have a two node Hyper-V cluster. ~ once a week either one of the cluster nodes hangs during a backup (Backup Exec 2014 Vray edition) causing all VM's to restart to the other node. When a node hangs the console is just black and mouse moving. Ctrl-alt-del does nothing, only option is to reboot the server.
And almost always if I just let the node to boot up it boots up to the same state, black screen only mouse visible.
I have to boot it first to safe mode and then reboot it again to get it up.

Hardware:

2 x IBM x3550 (2 x CPU, 320 GB RAM, addtional cards: 4-port intel net card + 2 port SAS-card ) as Hyper-V nodes
1 x IBM V3700 as SAN-storage, connected to both nodes with redundant SAS-cables.

Software used:
Windows Server 2012 R2 datacenter OS with Hyper-V roles in cluster nodes
Windows failover clustering
4 x 2TB Shared CSV-disks for Virtual-machines
Backup Exec 2014 V-ray edition
SDDDSM driver for V3700

Configuration:
1 network team of two interfaces for VM-traffic only
1 network interface for VM-traffic only for DMZ traffic for selected VM's
1 network team of two interfaces for Cluster traffic only
1 management interface

ODX (Offloaded Data Transfers) is disabled from both nodes as V3700 does not support it.
~30 virtual machines, mostly windows server versions from 2003 to 2012 R2, couple of Ubuntu VMs and four Windows 7 VMs.

We have all the latest Windows updates and HW firmwares installed in our Cluster nodes.
The problem is that the nodes won't generate any kind of dumps when they hang, so we can't pinpoint where the problem is.

Also system logs don't reveal anything that would tell the actual cause of the hang.

For example according to System log one of the nodes hung at 21:17:44:
The previous system shutdown at 9:17:44 PM on ‎12/‎10/‎2014 was unexpected.

From the even viewer I have found following errors, but these are not near the crash time.

17:06:08 
ERROR VSS
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetAsrMetadata.  hr = 0x80070037, The specified network resource or device is no longer available.


Operation:
   PrepareForBackup event

Context:
   Execution Context: ASR Writer
   Execution Context: Writer
   Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Name: ASR Writer
   Writer Instance ID: {d2d37e37-99d1-446d-a840-5390af00616e}

Error-specific details:
   ASR Writer: The specified network resource or device is no longer available. (0x80070037)



17:06:08 
Warning VSS
Volume Shadow Copy Service warning: ASR writer Error 0x80070037.  hr = 0x00000000, The operation completed successfully.
. 

Operation:
   PrepareForBackup event

Context:
   Execution Context: ASR Writer
   Execution Context: Writer
   Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Name: ASR Writer
   Writer Instance ID: {d2d37e37-99d1-446d-a840-5390af00616e}

Error-specific details:
   ASR Writer: The specified network resource or device is no longer available. (0x80070037)


We also have these errors showing up in the Event viewer multiple times during backups, but according to info released
by Microsoft these seem to be related to VM's with IDE root-disks:

ERROR: VDS Basic Provider
Unexpected failure. Error code: 48F@01000003

We will need help to find out what is causing these hangs. Anyone have any hints or should I just open a case to Symantec or Microsoft?

Br,
Antti Kiiski