Windows Server Failover Clustering : Clustering outside AD2024/12/23 |
|
It's possible to configure WSFC Cluster if Nodes are not in Active Directory domain.
This example is based on the environment like follows.
|
+----------------------+ | +----------------------+
| [ iSCSI Target ] |10.0.0.110 | 10.0.0.101| [ Cluster Node#1 ] |
| tgt01.srv.world +-----------+-----------+ rx-7.srv.world |
| | | | |
+----------------------+ | +----------------------+
|
| +----------------------+
| 10.0.0.102| [ Cluster Node#2 ] |
+-----------+ rx-8.srv.world |
| |
+----------------------+
|
|
On CUI Configuration, run PowerShell and Set like follows. |
|
| [1] |
Install [Failover Clustering] feature on all Nodes, refer to here. |
| [2] | |
| [3] | Logon to a Node that has cluster administration tools and Test to create cluster to verify each Nodes settings. On WorkGroup environment, it needs Administrator passwords on all Nodes are the same for creating Cluster. If some errors are shown, improve your System and retry Test Job. For [WARNING] items, you should care them but they are not essential requisites, so if [ClusterConditionallyApproved] is shown, it's possible to create a Cluster. |
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. # [-Node] ⇒ specify Nodes PS C:\Users\Administrator> Test-Cluster -Node "RX-7", "RX-8" WARNING: System Configuration - Validate Active Directory Configuration: The test reported some warnings.. WARNING: Network - Validate Network Communication: The test reported some warnings.. WARNING: Test Result: HadUnselectedTests, ClusterConditionallyApproved Testing has completed for the tests you selected. You should review the warnings in the Report. A cluster solution is supported by Microsoft only if you run all cluster validation tests, and all tests succeed (with or without warnings). Test report file path: C:\Users\Administrator\AppData\Local\Temp\Validation Report 2024.12.22 At 19.52.10.htm Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 12/22/2024 7:55 PM 736820 Validation Report 2024.12.22 At 19.52.10.htm |
| [4] | Configure Cluster. On WorkGroup environment, it needs to add Cluster name and IP address on DNS server each Nodes bind before creating Cluster. (on following example, it is [Cluster01/10.0.0.111] - if you allow dynamic update on target zone on DNS server, it's not required manually) |
# [-Name] ⇒ any Cluster Name # [-Node] ⇒ specify Nodes for Cluster # [-AdministrativeAccessPoint] ⇒ Administrative Access Point # [-StaticAddress] ⇒ IP address for Cluster access PS C:\Users\Administrator> New-Cluster -Name Cluster01 -Node "RX-7", "RX-8" ` -AdministrativeAccessPoint DNS ` -StaticAddress 10.0.0.111 Name ---- Cluster01 # confirm settings PS C:\Users\Administrator> Get-Cluster | Format-List -Property * AddEvictDelay : 60 AdministrativeAccessPoint : Dns AutoAssignNodeSite : 1 AutoBalancerMode : 2 AutoBalancerLevel : 1 BackupInProgress : 0 BlockCacheSize : 0 DetectedCloudPlatform : None DetectManagedEvents : 1 DetectManagedEventsThreshold : 60 ClusSvcHangTimeout : 135 ClusSvcRegroupStageTimeout : 15 ClusSvcRegroupTickInMilliseconds : 300 ClusterEnforcedAntiAffinity : 0 ClusterFunctionalLevel : 12 ClusterUpgradeVersion : 6 ClusterGroupWaitDelay : 120 ClusterLogLevel : 3 ClusterLogSize : 1536 CrossSiteDelay : 1000 CrossSiteThreshold : 20 CrossSubnetDelay : 1000 CrossSubnetThreshold : 20 CsvBalancer : 1 CsvTimeToWait : 600000 DatabaseReadWriteMode : 0 DefaultNetworkRole : 3 Description : Domain : srv.world DrainOnShutdown : 1 DumpPolicy : 1375801625 DynamicQuorum : 1 EnableSharedVolumes : Enabled FixQuorum : 0 GroupDependencyTimeout : 600 HangRecoveryAction : 6 Id : 4475d69f-b62c-4388-9d74-a875a608e4e2 IgnorePersistentStateOnStartup : 0 LogResourceControls : 0 LowerQuorumPriorityNodeId : 0 MaximumParallelMigrations : 1 MessageBufferLength : 50 MinimumNeverPreemptPriority : 3000 MinimumPreemptorPriority : 1 Name : Cluster01 NetftIPSecEnabled : 1 PlacementOptions : 0 PlumbAllCrossSubnetRoutes : 0 PreferredSite : PreventQuorum : 0 QuarantineDuration : 7200 QuarantineThreshold : 3 QuorumArbitrationTimeMax : 20 RecentEventsResetTime : 12/23/2024 3:56:42 AM RequestReplyTimeout : 15 ResiliencyDefaultPeriod : 240 ResiliencyLevel : AlwaysIsolate RouteHistoryLength : 40 S2DBusTypes : 0 S2DCacheBehavior : Default S2DCacheDesiredState : Enabled S2DCacheMetadataReserveBytes : 34359738368 S2DCachePageSizeKBytes : 16 S2DEnabled : 0 S2DIOLatencyThreshold : 10000 S2DOptimizations : 0 WprSessionCount : 2 WprSessionCoolOffTime : 600 RolloutAudience : 3 DpcWatchdogProfileSingleDpcThreshold : 5000 DpcWatchdogProfileCumulativeDpcThreshold : 5000 GlobalWprSessionConfig : {} SameSubnetDelay : 1000 SameSubnetThreshold : 20 SecurityLevel : 1 SecurityLevelForStorage : 0 SetSMBBandwidthLimit : 1 SMBBandwidthLimitFactor : 2500 SharedVolumeCompatibleFilters : {} SharedVolumeIncompatibleFilters : {} SharedVolumeSecurityDescriptor : {1, 0, 4, 128...} SharedVolumesRoot : C:\ClusterStorage SharedVolumeVssWriterOperationTimeout : 1800 ShutdownTimeoutInMinutes : 20 UseClientAccessNetworksForSharedVolumes : 2 WitnessDatabaseWriteTimeout : 300 WitnessDynamicWeight : 1 WitnessRestartInterval : 15 EnabledEventLogs : {Microsoft-Windows-Hyper-V-VmSwitch-Diagnostic,4,0xFFFFFFFD, Microsoft-Windows-SMBServer/Analytic, Microsoft-Windows-Kernel-LiveDump/Analytic} UseRdmaForStorage : 1 RdmaConnectionsPerInterfaceForStorage : 4 AcceleratedNetworkingNodeReserve : 0 AcceleratedNetworkingEnabled : 0 |
| [5] | Verify it's possible to access to Cluster IP address from an any Computer in your Network. |
# for example, access via SSH to Cluster IP address PS C:\Users\Administrator> ssh Administrator@10.0.0.111 Administrator@10.0.0.111's password: Microsoft Windows [Version 10.0.26100.2605] (c) Microsoft Corporation. All rights reserved. administrator@RX-7 C:\Users\Administrator> powershell Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Users\Administrator> Get-ClusterNode Name State Type ---- ----- ---- rx-7 Up Node rx-8 Up Node PS C:\Users\Administrator> hostname rx-7 PS C:\Users\Administrator> Get-Volume DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size ----------- ------------ -------------- --------- ------------ ----------------- ------------- ---- NTFS Fixed Healthy OK 145.48 MB 674 MB C NTFS Fixed Healthy OK 66.16 GB 79.23 GB FAT32 Fixed Healthy OK 62.81 MB 96 MB D NTFS Fixed Healthy OK 459.24 MB 495.93 MB E NTFS Fixed Healthy OK 29.89 GB 29.98 GB # restart computer to verify failover runs normally PS C:\Users\Administrator> Restart-Computer -Force # access to Cluster again PS C:\Users\Administrator> ssh Administrator@10.0.0.111 Administrator@10.0.0.111's password: Microsoft Windows [Version 10.0.26100.2605] (c) Microsoft Corporation. All rights reserved. administrator@RX-8 C:\Users\Administrator> powershell Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Users\Administrator> Get-ClusterNode Name State Type ---- ----- ---- rx-7 Up Node rx-8 Up Node PS C:\Users\Administrator> hostname rx-8 PS C:\Users\Administrator> Get-Volume DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size ----------- ------------ -------------- --------- ------------ ----------------- ------------- ---- NTFS Fixed Healthy OK 145.48 MB 674 MB C NTFS Fixed Healthy OK 65.61 GB 79.23 GB FAT32 Fixed Healthy OK 62.81 MB 96 MB D NTFS Fixed Healthy OK 459.24 MB 495.93 MB E NTFS Fixed Healthy OK 29.89 GB 29.98 GB |
|
Windows Server Failover Clustering : Clustering outside AD (GUI)
|
|
On GUI configuration, it's the same procedure with AD environment, so refer to here. |
| Sponsored Link |
|
|