You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: WindowsServerDocs/failover-clustering/create-storage-spaces-direct-campus-cluster.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,18 +22,18 @@ For more information about campus cluster architecture, supported configurations
22
22
23
23
Before you create a campus cluster, ensure you meet the following requirements:
24
24
25
-
-**Windows Server 2025** with the 2025-12 Security Update (KB5072033) installed on every node in the failover cluster.
26
-
-**Flat S2D storage** - All capacity drives must be flash-based (SSD or NVMe). Don't use HDDs.
27
-
-**Exactly two RACK fault domains** - You must define exactly two rack-level fault domains and place the cluster nodes in these two racks.
28
-
-**Hardware OEM guidelines** - Follow your hardware OEM's guidelines for the deployment.
29
-
-**Cluster quorum resource** - Place the quorum resource (File Share Witness, Disk Witness, Cloud Witness, or USB Witness) in a third room, separate from the data rooms containing the racks.
25
+
- Windows Server 2025 with the 2025-12 Security Update (KB5072033) installed on every node in the failover cluster.
26
+
- All capacity drives must be flash-based (SSD or NVMe). Don't use HDDs.
27
+
- You must define exactly two rack-level fault domains and place the cluster nodes in these two racks.
28
+
- Follow your hardware OEM's guidelines for any shared or direct attached storage including driver versions.
29
+
- Place the quorum resource (File Share Witness, Disk Witness, Cloud Witness, or USB Witness) in a third location, separate from the campus cluster racks.
30
30
31
31
For optimal performance and resiliency, use the following configurations:
32
32
33
33
- Each rack has a separate network path to the cluster quorum resource.
34
34
- Use redundant top-of-rack (TOR) switches, core switches, and dedicated networks for S2D storage traffic to minimize single points of failure and maximize workload uptime and durability.
35
35
- Network latency of 1 ms or less between racks. Use the [PsPing](/sysinternals/downloads/psping) utility to measure network latency.
36
-
- RDMA NICs and switches, which can achieve up to 30% CPU savings.
36
+
- RDMA NICs and switches, which can achieve CPU savings on your cluster.
0 commit comments