Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event 1135, 7031, or 7036 when the cluster service stops in Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • One of the network adapters fails in a Windows Server 2012 cluster that has built-in load balancing and failover (LBFO) to switch independent teaming and active-standby mode.
  • The server that has the network adapter is removed from the cluster membership after five seconds.
  • The cluster service on the server is automatically restarted after 60 seconds.
In this scenario, the server continues to work as expected even without the un-recovered network adapter. Meanwhile, packet loss occurs on the server.

Note This issue does not occur in Windows Server 2012 R2.

Events that resemble the following are logged when this issue occurs:

↑ Back to the top


Cause

Failover is known to be less graceful in active-standby mode, and this is a known issue in a Windows Server 2012 environment that has LBFO teaming.

↑ Back to the top


Workaround

Because the active-standby mode provides no benefits over the active-active mode, from the Microsoft Windows Clustering stand-point, we do not recommend an active-standby configuration. There are currently no changes to the current version as running active-active mode is the recommended teaming configuration.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kbsurveynew, kbexpertiseadvanced, kbprb, kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 3010460
Revision : 1
Created on : 1/7/2017
Published on : 11/11/2014
Exists online : False
Views : 208