L
l4mpoz
Hi guys,
i have setup Windows 2016 Failover Cluster.
Scenario:
- Two nodes running VM Windows 2016 full patche 2019-02 on VMware ESXi, 6.5.0, 8294253 and vcenter 6.5.0 8815520
- ESXi 6.5 and later (VM version 13)
- ISCSI Controller Vmware paravirtual Physical
- All vDisk configured Compatibility Mode Physical
- Shared Storage & Quorum are presented in RDM mode from the IBM V5030 (4 nodes) and SVC storage.
- I got this error first Event on node 2 , the node 2 up & running but RDP coneection fails, im connect from vmware console and node 2 back screen... forced reboot...
Cluster physical disk resource failed periodic health check.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 04/04/2019 18:26:03
Event ID: 1792
Task Category: Physical Disk Resource
Level: Error
Keywords:
User: SYSTEM
Computer: xxxxxxxxxxx
Description:
Cluster physical disk resource failed periodic health check.
Physical Disk resource name: Cluster Disk 6
Device Number: 2
Device Guid: {ae52fb6a-84b4-a34d-23d3-6f732de9e349}
Error Code: 170
Additional reason: ClusDiskReportedFailure
If the reason is ReattachTimeout, it means attaching a new RHS process to the disk resource took too long.
If the reason is ClusDiskReportedFailure, it means the underlying disk device was removed from the system.
If the reason is QuorumResourceFailure, it means this is a Spaces quorum resource.
If the reason is VolumeNotHealthy, it means one of the volumes is not healthy and may need repair.
- All 6 disk RDM failed periodic health check
- After
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 04/04/2019 18:26:20
Event ID: 1135
Task Category: Node Mgr
Level: Critical
Keywords:
User: SYSTEM
Computer: xxxxxxxxxxxxx
Description:
Cluster node 'xxxxx' 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1135</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-04-04T16:26:20.991581600Z" />
<EventRecordID>35800</EventRecordID>
<Correlation />
<Execution ProcessID="3000" ThreadID="4400" />
<Channel>System</Channel>
<Computer>xxxx</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">xxxxx</Data>
</EventData>
</Event>
Anyone have same issue?
Continue reading...
i have setup Windows 2016 Failover Cluster.
Scenario:
- Two nodes running VM Windows 2016 full patche 2019-02 on VMware ESXi, 6.5.0, 8294253 and vcenter 6.5.0 8815520
- ESXi 6.5 and later (VM version 13)
- ISCSI Controller Vmware paravirtual Physical
- All vDisk configured Compatibility Mode Physical
- Shared Storage & Quorum are presented in RDM mode from the IBM V5030 (4 nodes) and SVC storage.
- I got this error first Event on node 2 , the node 2 up & running but RDP coneection fails, im connect from vmware console and node 2 back screen... forced reboot...
Cluster physical disk resource failed periodic health check.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 04/04/2019 18:26:03
Event ID: 1792
Task Category: Physical Disk Resource
Level: Error
Keywords:
User: SYSTEM
Computer: xxxxxxxxxxx
Description:
Cluster physical disk resource failed periodic health check.
Physical Disk resource name: Cluster Disk 6
Device Number: 2
Device Guid: {ae52fb6a-84b4-a34d-23d3-6f732de9e349}
Error Code: 170
Additional reason: ClusDiskReportedFailure
If the reason is ReattachTimeout, it means attaching a new RHS process to the disk resource took too long.
If the reason is ClusDiskReportedFailure, it means the underlying disk device was removed from the system.
If the reason is QuorumResourceFailure, it means this is a Spaces quorum resource.
If the reason is VolumeNotHealthy, it means one of the volumes is not healthy and may need repair.
- All 6 disk RDM failed periodic health check
- After
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 04/04/2019 18:26:20
Event ID: 1135
Task Category: Node Mgr
Level: Critical
Keywords:
User: SYSTEM
Computer: xxxxxxxxxxxxx
Description:
Cluster node 'xxxxx' 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
<EventID>1135</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-04-04T16:26:20.991581600Z" />
<EventRecordID>35800</EventRecordID>
<Correlation />
<Execution ProcessID="3000" ThreadID="4400" />
<Channel>System</Channel>
<Computer>xxxx</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="NodeName">xxxxx</Data>
</EventData>
</Event>
Anyone have same issue?
Continue reading...