Announcement

Collapse
No announcement yet.

Cluster fails after network failure.

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

  • Cluster fails after network failure.

    We have a 2 node cluster in a separate domain using windows Server 2003 Enterprise with Service pack 2.

    The problem is that we had some network failures during this season (summer) due to power outtage, and UPS failure. The real problem lies that the cluster cannot recover itself after a network failure. The configuration is as follows.

    Domain: website.local
    Domain controller: Windows Server 2003 Standard.
    Cluster computer: 2 node cluster Active/Passive with Windows Server 2003 Enterprise with SP2.

    Node A

    Name: nodea.website.local
    Public IP address: 192.168.2.51
    Mask : 255.255.255.0
    Gateway: 192.168.2.1

    Heartbeat IP Address: 10.10.10.10
    Mask : 255.255.255.0
    Gateway: N/A

    Node B

    Name: nodeb.website.local
    Public IP address: 192.168.2.52
    Mask : 255.255.255.0
    Gateway: 192.168.2.1

    Heartbeat IP Address: 10.10.10.11
    Mask : 255.255.255.0
    Gateway: N/A

    Virtual node:

    Name: cluster.website.local
    IP add: 192.168.2.60
    Mask : 255.255.255.0
    Gateway: 192.168.2.1


    When i typed ipconfig in the cluster virtual node the output was that:

    Windows IP Configuration
    Host Name . . . . . . . . . . . . : nodea
    Primary Dns Suffix . . . . . . . : WEBSITE.LOCAL
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : WEBSITE.LOCAL

    Ethernet adapter PRIVATE(1):
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
    Physical Address. . . . . . . . . : xx-xx-xx-xx-8A-92
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 10.10.10.10
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter PUBLIC:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2
    Physical Address. . . . . . . . . : xx-xx-xx-xx-8A-90
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.2.61
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 192.168.2.54
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 192.168.2.51
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.2.1
    DNS Servers . . . . . . . . . . . : 192.168.2.55

    The cluster has 2 groups: the "cluster group" and the "SQL" group.
    It has IIS, and MS SQL Server v.8.0 installed.


    We have tried simulating the metwork failure by removing both nodes public ethernet adapters. The cluster failed to reconnect by itself.

    The cluster service under Services was configured to run as \WEBSITE\cluster
    When we manually stopped and started the cluster service in nodea the virtual node appeared again with no problem.

    *Note*
    We have our old Windows 2000 Server cluster in the same network in another separate domain. When the network failures occurred, the cluster was recoverred successfully.

    Thanx in advance.
Working...
X