Questions[microsoft-cluster-server](server)

Both servers run windows-server-2003 x64 in a Active/Standby Microsoft Cluster with shared Disk Resources. Server1 Server2

Server1 suffered hardware issues needing HBA SAS card replaced. Disk Management no longer detects the shared logical drives on it. These drives are part of Disk Resources in the cluster.

Based on my research, Microsoft Cluster uses Disk Signature to identify & attach to the Disk Resources.

https://support.microsoft.com/en-us/help/280425/recovering-from-an-event-id-1034-on-a-server-cluster

https://support.microsoft.com/en-us/help/886800/a-disk-signature-changes-unexpectedly-on-a-windows-server-2003-clustered-physical-disk-resource

An issue I see are missing REG_SZ DiskName entries in the registry.

Example:

reg query     HKLM\System\CurrentControlSet\Services\Clusdisk\Parameters\Signatures\D441B580
Listing of [System\CurrentControlSet\Services\Clusdisk\Parameters\Signatures\D484B580]
REG_SZ DiskName \Device\Harddisk1

Do I simply need to add the missing registry keys on Server1 to make it appear in Disk Management?

EDIT: Both servers run on Dell PowerEdge 6850.

Looking at Dell Modular Disk Storage Manager on each server the following looks correct. Configured Hosts Host Name : HBA Hosts Ports mapping

Host-to-virtual disk mappings

Windows Device Manager: SCSI and RAID controllers

DELL PERC 5/i Adapter RAID Controller Dell SAS 5/E Adapter Controller (I believe this is what connects to the shared storage)

LSI Logic PCI-x Ultra320 SCSI Host Adapter

LSI Logic PCI-x Ultra320 SCSI Host Adapter

MagicISO SCSI Host Controller

Multi-Path Support

A new observation is Windows Disk Mangement has Disk 0 assigned to Virtual CD ROM on Server1. On Server2, Disk 0 is the C:\ OS drive.

The logical drives needs to be presented as Disks 1,2,3,5. Since Disk 1 is already in use by Windows could this prevent entire Logical drives not to be presented to Windows?

I have a clustered Hyper-V environment with four nodes and three PowerVault MD3xxx storage arrays for shared storage.

The servers are using standard Ethernet connections for the iSCSI fabric (not HBAs). MPIO is configured via the Dell storage wizard.

The problem that I seem to be having is that upon rebooting a node, the Ethernet connections seem to be taken down before the iSCSI initiator is ready for it - so the connectivity to any of the LUNs that it happens to own is lost unexpectedly.

Is there a way of preventing this so that a shutdown will be more graceful? In future I will be making sure that a node that is going to be rebooted has any storage it owns shifted to another node first, but I was wondering if this should really happen automatically.

I've got an odd issue with a SQL 2012 cluster. The cluster itself uses FC shared storage, and generally works perfectly. The SQL service works, and failover occurs as expected.

The issue I have is that the inactive node occasionally tries to access the shared storage. This throws an eventlog error similar to:

MSSQLSERVER: 17058: initerrlog: Could not open error log file 'G:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.)

This error will sporadically occur between 8-12 times over a 3 second period and G: is one of the shared disks.

It looks like the inactive node is trying to start the service, and failing because it can't write to the shared storage, because it doesn't own it. What could be causing this?

Does anyone know how to make the second SQL instance Agent working on the same MSCS SQL Server 2008 R2 cluster?

In the clustered SQL Server service instance2 i have assigned the same service account to start all of the other service in for instance1

Log Name:      Application
Source:        SQLAgent$LYNC
Date:          26/08/2011 12:40:46 PM
Event ID:      103
Task Category: Service Control
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQLNode1-VM.DOMAIN.com
Description:
SQLServerAgent could not be started (reason: Unable to connect to server 'SQLNode1-VM\Instance1'; SQLServerAgent cannot start).

I always get the above error, therefore I cannot proceed in adding the secondary node for my second DB instance.

I'm having a mysterious problem with my Failover cluster,

Cluster name: PrintCluster01.domain.com
Members: PrintServer01.domain.com  andPrintServer02.domain.com

in the Failover Cluster Management – Cluster Event I received the Critical error message 1135 and 1177:

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.


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:

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 could that be possible it conflict by one of the PrintServer01 node ? the detailed is as below:

**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.

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


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

Any help would be greatly appreciated.

Thanks, AWT