Announcement

Collapse
No announcement yet.

Failover cluster cannot failover automatically ?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Failover cluster cannot failover automatically ?

    Hi,

    I'm having problem with my failover cluster failed by itself so I had to manually failover it back to PrintServer01,
    in the Failover Cluster Management – Cluster Event I received the Critical error message 1135 and 1177:

    Code:
    Log Name: System
    Source: Microsoft-Windows-FailoverClustering
    Date: 15/06/2011 9:07:49 PM
    Event ID: 1177
    Task Category: None
    Level: Critical
    Keywords: 
    User: SYSTEM
    Computer: PrintServer01.domain.com
    Description:
    The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
    Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
    Code:
    Log Name: System
    Source: Microsoft-Windows-FailoverClustering
    Date: 15/06/2011 9:07:28 PM
    Event ID: 1135
    Task Category: None
    Level: Critical
    Keywords: 
    User: SYSTEM
    Computer: PrintServer01.domain.com
    Description:
    Cluster node 'PrintServer02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
    After further investigation, I found some interesting error here, from the very first critical error message logged in the Event viewer on PrintServer02:

    Code:
    Log Name: System
    Source: Tcpip
    Date: 15/06/2011 9:07:29 PM
    Event ID: 4199
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: PrintServer02-VM.domain.com
    Description:
    The system detected an address conflict for IP address 192.168.127.142 with the system having network hardware address 00-50-56-AE-29-23. Network operations on this system may be disrupted as a result.
    192.168.127.142 --> secondary IP of PrintServer01

    how come it conflict by one of the PrintServer01 node ? the detailed is as below:

    Code:
    From PrintServer01
    Ethernet adapter Local Area Connection* 8:
    
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
    Physical Address. . . . . . . . . : 02-50-56-AE-29-23
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 169.254.1.183(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Enabled
    I have double check in all of the cluster members that all IP addresses is now unique.

    Any help would be greatly appreciated.

    Thanks.

  • #2
    Re: Failover cluster cannot failover automatically ?

    many thanks for the reply mate,

    however I'm sure that I the IP is static not by DHCP as from the IPCONFIG results below:


    From PrintServer01 (the Active Node)
    Windows IP Configuration

    Host Name . . . . . . . . . . . . : PrintServer01
    Primary Dns Suffix . . . . . . . : domain.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : domain.com
    domain.com.au

    Ethernet adapter Local Area Connection* 8:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
    Physical Address. . . . . . . . . : 02-50-56-AE-29-23
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 169.254.1.183(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Cluster Public Network:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection
    Physical Address. . . . . . . . . : 00-50-56-AE-29-23
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.127.155(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IPv4 Address. . . . . . . . . . . : 192.168.127.88(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IPv4 Address. . . . . . . . . . . : 192.168.127.142(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IPv4 Address. . . . . . . . . . . : 192.168.127.143(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IPv4 Address. . . . . . . . . . . : 192.168.127.144(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.127.254
    DNS Servers . . . . . . . . . . . : 192.168.127.10
    192.168.127.11
    Primary WINS Server . . . . . . . : 192.168.127.10
    Secondary WINS Server . . . . . . : 192.168.127.11
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Cluster Private Network:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection #2
    Physical Address. . . . . . . . . : 00-50-56-AE-43-EC
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 10.184.2.2(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Code:
    From PrintServer02
    Windows IP Configuration
    
    Host Name . . . . . . . . . . . . : PrintServer02
     Primary Dns Suffix . . . . . . . : domain.com
     Node Type . . . . . . . . . . . . : Hybrid
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
     DNS Suffix Search List. . . . . . : domain.com
     domain.com.au
    
    Ethernet adapter Local Area Connection* 8:
    
    Connection-specific DNS Suffix . :
     Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
     Physical Address. . . . . . . . . : 02-50-56-AE-5F-E5
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv4 Address. . . . . . . . . . . : 169.254.2.86(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.0.0
     Default Gateway . . . . . . . . . :
     NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Cluster Public Network:
    
    Connection-specific DNS Suffix . :
     Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection
     Physical Address. . . . . . . . . : 00-50-56-AE-79-FA
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv4 Address. . . . . . . . . . . : 192.168.127.172(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     IPv4 Address. . . . . . . . . . . : 192.168.127.119(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Default Gateway . . . . . . . . . : 192.168.127.254
     DNS Servers . . . . . . . . . . . : 192.168.127.10
     192.168.127.11
     Primary WINS Server . . . . . . . : 192.168.127.11
     Secondary WINS Server . . . . . . : 192.168.127.10
     NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Cluster Private Network:
    
    Connection-specific DNS Suffix . :
     Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection #2
     Physical Address. . . . . . . . . : 00-50-56-AE-77-8D
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv4 Address. . . . . . . . . . . : 10.184.2.3(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Default Gateway . . . . . . . . . :
     NetBIOS over Tcpip. . . . . . . . : Disabled

    Comment


    • #3
      Re: Failover cluster cannot failover automatically ?

      It is a 2 node cluster? Is there also a witness disk for the cluster quorum? A even number of cluster host does need a witness disk.
      gerth

      MCITP sa, ea & va, [email protected]

      Comment


      • #4
        Re: Failover cluster cannot failover automatically ?

        Yes it is two servers clusters.

        Comment


        • #5
          Re: Failover cluster cannot failover automatically ?

          With or without a witness disk?
          gerth

          MCITP sa, ea & va, [email protected]

          Comment


          • #6
            Re: Failover cluster cannot failover automatically ?

            Originally posted by gerth View Post
            With or without a witness disk?
            with a witness (quorum) disk for sure.

            Comment


            • #7
              Re: Failover cluster cannot failover automatically ?

              Have you reviewed this through the Failover Cluster Manager? Is it 2008 or 2008 R2?

              Comment

              Working...
              X