Windows Server Failover Clustering : Clustering outside AD2019/07/09 |
|
It's possible to configure WSFC Cluster if Nodes are not in Active Directory domain.
This example is based on the environment like follows.
Prepare 2 Nodes for clustering and they have 2 shared storages for clustering, for Data and for Quorum.
|
+----------------------+ | +----------------------+
| [ 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] | |
| [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 2020.09.28 At 18.45.40.htm Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 9/28/2020 6:48 PM 648854 Validation Report 2020.09.28 At 18.45.40.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 : 0 AutoBalancerMode : 2 AutoBalancerLevel : 1 BackupInProgress : 0 BlockCacheSize : 1024 DetectedCloudPlatform : None DetectManagedEvents : 1 DetectManagedEventsThreshold : 60 ClusSvcHangTimeout : 135 ClusSvcRegroupStageTimeout : 15 ClusSvcRegroupTickInMilliseconds : 300 ClusterEnforcedAntiAffinity : 0 ClusterFunctionalLevel : 10 ClusterUpgradeVersion : 3 ClusterGroupWaitDelay : 120 ClusterLogLevel : 3 ClusterLogSize : 1536 CrossSiteDelay : 1000 CrossSiteThreshold : 20 CrossSubnetDelay : 1000 CrossSubnetThreshold : 20 CsvBalancer : 1 DatabaseReadWriteMode : 0 DefaultNetworkRole : 3 Description : Domain : srv.world DrainOnShutdown : 1 DumpPolicy : 1376850201 DynamicQuorum : 1 EnableSharedVolumes : Enabled FixQuorum : 0 GroupDependencyTimeout : 600 HangRecoveryAction : 6 Id : 1d82da30-1301-4646-a87a-3a7c02546ef6 IgnorePersistentStateOnStartup : 0 LogResourceControls : 0 LowerQuorumPriorityNodeId : 0 MessageBufferLength : 50 MinimumNeverPreemptPriority : 3000 MinimumPreemptorPriority : 1 Name : Cluster01 NetftIPSecEnabled : 1 PlacementOptions : 0 PlumbAllCrossSubnetRoutes : 0 PreferredSite : PreventQuorum : 0 QuarantineDuration : 7200 QuarantineThreshold : 3 QuorumArbitrationTimeMax : 20 RecentEventsResetTime : 9/29/2020 1:56:28 AM RequestReplyTimeout : 60 ResiliencyDefaultPeriod : 240 ResiliencyLevel : AlwaysIsolate RouteHistoryLength : 40 S2DBusTypes : 0 S2DCacheBehavior : Default S2DCacheDesiredState : Enabled S2DCacheMetadataReserveBytes : 34359738368 S2DCachePageSizeKBytes : 16 S2DEnabled : 0 S2DIOLatencyThreshold : 10000 S2DOptimizations : 0 SameSubnetDelay : 1000 SameSubnetThreshold : 20 SecurityLevel : 1 SecurityLevelForStorage : 0 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-SMBDirect/Debug,4, Microsoft-Windows-SMBServer/Analytic, Microsoft-Windows-Kernel-LiveDump/Analytic} |
| [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 [root@desktop ~]# ssh Administrator@10.0.0.111 Administrator@10.0.0.111's password: Microsoft Windows [Version 10.0.17763.1490] (c) 2018 Microsoft Corporation. All rights reserved. Administrator@RX-8 C:\Users\Administrator> powershell Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. 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 514.32 MB 549 MB C NTFS Fixed Healthy OK 64.53 GB 79.46 GB D NTFS Fixed Healthy OK 463.75 MB 495.93 MB E NTFS Fixed Healthy OK 29.88 GB 29.98 GB # restart computer to verify failover runs normally PS C:\Users\Administrator> Restart-Computer -Force PS C:\Users\Administrator> exit # access to Cluster again [root@desktop ~]# ssh administrator@10.0.0.111 Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. 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 514.32 MB 549 MB C NTFS Fixed Healthy OK 64.2 GB 79.46 GB D NTFS Fixed Healthy OK 463.75 MB 495.93 MB E NTFS Fixed Healthy OK 29.88 GB 29.98 GB |
|
Windows Server Failover Clustering : Clustering outside AD (GUI)
|
|
|
| Sponsored Link |