Hardware Requirements
DOCUMENT CATEGORY: Runbook SCOPE: Hardware specifications for Azure Local PURPOSE: Define hardware requirements for cluster deployment MASTER REFERENCE: Microsoft Learn - Hardware Requirements
Status: Active
Overview
This document defines hardware requirements and specifications for Azure Local cluster deployments. It covers:
- Supported Hardware Platforms - Dell integrated systems and validated nodes
- Minimum Requirements - CPU, memory, storage, and network specifications
- Firmware Baselines - Required BIOS, iDRAC, NIC, and controller versions
- Hardware Discovery - Automated inventory collection via iDRAC Redfish API
- Node Inventory Worksheets - Per-site hardware documentation
Azure Local Cloud deploys Dell AX-series integrated systems for Azure Local. All hardware must meet Microsoft Azure Local certification requirements.
Supported Hardware Platforms
Dell Integrated Systems (AX-Series)
Dell AX-series nodes are purpose-built for Azure Local with pre-validated configurations:
| Model | CPU | Max RAM | Storage | Network | Use Case |
|---|---|---|---|---|---|
| Dell AX-760 | Intel Xeon Scalable 5th Gen | 4TB | NVMe + SSD | 4x 100GbE | General purpose |
| Dell AX-770 | Intel Xeon Scalable 5th Gen | 4TB | NVMe + SSD | 4x 100GbE | High-performance |
Minimum Hardware Requirements
Azure Local System Requirements
Microsoft publishes the following minimums. Microsoft Support may only be provided for Azure Local running on hardware in the Azure Local catalog. The "Cloud Standard baseline" column is the sizing this site assumes for production clusters, which is higher than the Microsoft minimum.
| Component | Microsoft minimum | Cloud Standard baseline | Notes |
|---|---|---|---|
| Machines per instance | 1 to 16 (hyperconverged). Up to 64 for disaggregated (SAN) | 2 to 16 | Single-node is a supported size, with no node-level failover. All machines must match (model, processor, NICs, drive count and type) |
| CPU | 64-bit Intel Nehalem grade or AMD EPYC or later with SLAT | 16+ cores per node, 32+ recommended | Processor properties (family, clock, core and thread counts) must match across nodes at deployment |
| Memory | 32 GB per machine, ECC | 128 GB or more per node, 256+ GB recommended | Add capacity for Arc VM management and workloads |
| Boot drive | 200 GB | 480+ GB SSD | 400 GB or more for machines with more than 768 GB RAM. BOSS card or M.2 recommended |
| Data drives | At least 2 drives per machine, 500 GB or more each | 4+ NVMe | All-flash recommended. Same count, type, capacity, and firmware at deployment |
| Host network adapters | At least 2 adapters from the Windows Server Catalog, qualified for the traffic type they carry (management, compute, storage). Inbox drivers are not supported | 4+ NICs | RDMA-capable adapters for the storage intent. Intent patterns use 2, 4, 6 or 8 ports per node |
| TPM, Secure Boot, BIOS | TPM 2.0 present and enabled, Secure Boot enabled, Intel VT or AMD-V on | Same | Required for deployment |
Maximums: 512 logical processors per host, 24 TB RAM per host, and 2,048 virtual processors per host. GPU memory up to 192 GB per machine is supported.
See System requirements for Azure Local. The 16 core and 128 GB figures used by the validation script below are the Cloud Standard baseline, not Microsoft requirements. Machines that cannot meet the memory and ECC requirement can use a virtual deployment for testing.
Storage Requirements
| Storage Tier | Drive Type | Minimum Count | Purpose |
|---|---|---|---|
| Cache Tier | NVMe SSD | 2 per node | High-speed caching (hybrid HDD plus flash layouts only: cache devices of 32 GB or more, cache-to-capacity ratio of 15% or more) |
| Capacity Tier | SSD or HDD | 4 per node | Data storage |
| Boot Drive | SSD (BOSS/M.2) | 1 per node | OS installation |
- Minimum 2 capacity drives required for Storage Spaces Direct resiliency
- Cache-to-capacity ratio: 1:4 to 1:8 recommended
- Total raw capacity: Plan for 2-3x usable capacity (mirroring overhead)
Network Requirements
| Interface | Speed | RDMA | Purpose |
|---|---|---|---|
| Management | 1 GbE or 10 GbE | No | Cluster management, iDRAC |
| Storage | 25 GbE or 100 GbE (10 Gb is the minimum for RDMA) | Required for S2D storage traffic (RoCEv2 or iWARP) | Storage Spaces Direct (S2D). Disaggregated SAN deployments have no RDMA storage intent |
| Compute/VM | 25 GbE or 100 GbE | No (guest RDMA is not supported) | VM traffic, SDN |
RDMA Technologies Supported:
- RoCEv2 (RDMA over Converged Ethernet v2) - Preferred; requires PFC and ETS on every port including the switches
- iWARP - Alternative for environments without DCB; the choice Learn gives for teams that don't manage ToR switches
RDMA adapters only work with adapters that use the same RDMA protocol, InfiniBand isn't supported, and Learn's RDMA vendor table lists Broadcom and Nvidia as RoCE only, Intel and Marvell (Qlogic) as iWARP and RoCE (some Intel models). Jumbo frames: Learn recommends an MTU of 9216 bytes on the physical switches for RDMA storage traffic.
Firmware Baseline Requirements
Azure Local Cloud Standard Firmware Versions
| Component | Minimum Version | Target Version | Notes |
|---|---|---|---|
| Dell BIOS | 2.0.0 | Latest stable | Check Dell support matrix |
| iDRAC Firmware | 7.0.0 | Latest stable | iDRAC 9 required |
| NIC Firmware | Varies by model | Latest validated | Check Azure Local catalog |
| RAID Controller | Varies by model | Latest stable | PERC/HBA firmware |
| Dell SBE Package | 4.2.2512 | 4.2.2512.1616+ | Solution Builder Extension. The package is a requirement: download it before you start (see the SBE package). Only the build-time side-load is opt-in |
Dell Gold Image
Azure Local Cloud standard Dell Gold Image specifications:
| Component | Version | Notes |
|---|---|---|
| Windows Server Build | 2510 | Azure Local OS (value from earlier engagements; the 2610 release runs OS build 26100.33650, so confirm the gold image for the 2610 media with Dell) |
| SBE Version | 4.2.2512.1616 | Dell Solution Builder Extension |
| Dell Solution Version | 12.2510.0.3165 | Integrated solution package |
| Azure Local Build | 2601 | Running version after Arc registration (earlier engagement value; the latest release is 12.2610.1004.50, see Releases and Support Lifecycle) |
Firmware Validation
Validate firmware versions match across all cluster nodes:
# Check BIOS version consistency
$discovery = Get-Content discovery/idrac-inventory.json | ConvertFrom-Json
foreach ($server in $discovery.servers.PSObject.Properties.Value) {
Write-Host "Server: $($server.service_tag)"
Write-Host " BIOS: $($server.firmware.bios_version)"
Write-Host " iDRAC: $($server.firmware.idrac_version)"
}
Hardware Discovery Process
Overview
Hardware discovery automates collection of Dell server specifications via iDRAC Redfish API, enabling:
- Accurate hardware inventory for deployment planning
- Validation that hardware meets Azure Local requirements
- Documentation of firmware versions and configurations
- Change tracking for hardware lifecycle management
Primary Script: Invoke-HardwareDiscovery.ps1 (Phase 04, Task 02)
Output: one <ServiceTag>.json per server and a discovery-summary.json, in the discovery folder
Prerequisites
iDRAC Access Requirements:
- iDRAC 9 or later with Redfish API enabled
- Network connectivity to iDRAC management interface (HTTPS/443)
- iDRAC administrator credentials
Verify iDRAC Accessibility:
# Test network connectivity
Test-NetConnection -ComputerName "10.10.10.11" -Port 443
# Verify Redfish API endpoint
Invoke-RestMethod -Uri "https://10.10.10.11/redfish/v1/" -SkipCertificateCheck
What Gets Discovered
| Category | Details Captured |
|---|---|
| System | Model, service tag, asset tag, BIOS version |
| CPU | Model, core count, thread count, max speed |
| Memory | Total capacity, DIMM count, speed, type |
| Storage | NVMe/SSD/HDD count, capacity, controller firmware |
| Network | Adapter model, MAC addresses, firmware version |
| Firmware | BIOS, iDRAC, NIC, controller versions |
Running Discovery
All servers (the iDRAC address of each server comes from nodes[].bmc.ip_address in infrastructure.yml):
cd C:\git\azurelocal-toolkit
# The BMC login comes from hardware.bmc (or nodes[].bmc) of infrastructure.yml. The password is a secret reference.
# The script never prompts. To use another login, pass -Credential.
.\scripts\deploy\04-cluster-deployment\phase-01-hardware-provisioning\task-02-hardware-discovery-via-dell-redfish-api\powershell\Invoke-HardwareDiscovery.ps1 -InfrastructureFile .\infrastructure.yml
One server:
.\scripts\deploy\04-cluster-deployment\phase-01-hardware-provisioning\task-02-hardware-discovery-via-dell-redfish-api\powershell\Invoke-HardwareDiscovery.ps1 -InfrastructureFile .\infrastructure.yml -TargetNode "<node-name>"
The script reads each BMC through the standard Redfish API (read only) and writes one JSON file per server, so you can keep the files of each run to track firmware changes.
Validate Hardware Requirements
After discovery, validate hardware meets Azure Local requirements:
- Open
discovery-summary.jsonand the<ServiceTag>.jsonfile of each server. - Compare each server with the minimums in the tables above: CPU cores, memory, drives with their media type (NVMe, SSD or HDD) and role (cache or capacity), and network ports with their MAC addresses.
- Write down every gap. Fix it before the hardware goes to the next phase.
Node Inventory Worksheet (Per-Site)
Site Hardware Summary
| Field | Value |
|---|---|
| Site Name/ID | ________________________ |
| Number of Nodes | ☐ 2 ☐ 3 ☐ 4 ☐ 8 ☐ 16 |
| Node Model | ________________________ (e.g., Dell AX-7525) |
| Cluster Configuration | ☐ 2-node ☐ 3-node ☐ 4+ node |
Node Details
Complete for each node in the cluster:
Node 1
| Field | Value |
|---|---|
| Hostname | ________________________ (e.g., CONAX01) |
| Service Tag | ________________________ |
| Asset Tag | ________________________ |
Compute:
| Component | Specification |
|---|---|
| CPU Model | ________________________ |
| CPU Cores | ______ |
| CPU Speed | ______ GHz |
| RAM Total | ______ GB |
| DIMM Configuration | ________________________ |
Storage:
| Drive Type | Model | Capacity | Count | Purpose |
|---|---|---|---|---|
| Boot (BOSS/M.2) | ____________ | ____ GB | __ | OS |
| NVMe (Cache) | ____________ | ____ GB | __ | S2D Cache |
| SSD (Capacity) | ____________ | ____ GB | __ | S2D Capacity |
| HDD (Capacity) | ____________ | ____ GB | __ | S2D Capacity |
Network:
| Adapter | Model | Ports | Speed | RDMA | Purpose |
|---|---|---|---|---|---|
| NIC 1 | ____________ | __ | ____ GbE | ☐ Yes ☐ No | ________ |
| NIC 2 | ____________ | __ | ____ GbE | ☐ Yes ☐ No | ________ |
| NIC 3 | ____________ | __ | ____ GbE | ☐ Yes ☐ No | ________ |
| NIC 4 | ____________ | __ | ____ GbE | ☐ Yes ☐ No | ________ |
Firmware:
| Component | Current Version | Target Version | Status |
|---|---|---|---|
| BIOS | ____________ | ____________ | ☐ Current ☐ Update needed |
| iDRAC | ____________ | ____________ | ☐ Current ☐ Update needed |
| NIC Firmware | ____________ | ____________ | ☐ Current ☐ Update needed |
| RAID Controller | ____________ | ____________ | ☐ Current ☐ Update needed |
Node 2
(Repeat the Node 1 table structure)
| Field | Value |
|---|---|
| Hostname | ________________________ |
| Service Tag | ________________________ |
| Asset Tag | ________________________ |
(Continue for additional nodes)
iDRAC Access and Credentials
| Node | iDRAC IP | Username | Password Location | Access Verified |
|---|---|---|---|---|
| Node 1 | ____________ | ________ | Key Vault: ________ | ☐ Yes ☐ No |
| Node 2 | ____________ | ________ | Key Vault: ________ | ☐ Yes ☐ No |
| Node 3 | ____________ | ________ | Key Vault: ________ | ☐ Yes ☐ No |
| Node 4 | ____________ | ________ | Key Vault: ________ | ☐ Yes ☐ No |
iDRAC Verification:
- iDRAC firmware version matches baseline: ☐ Yes ☐ No
- iDRAC web interface accessible: ☐ Yes ☐ No
- Redfish API enabled and accessible: ☐ Yes ☐ No
- Virtual console (KVM) functional: ☐ Yes ☐ No
- Virtual media mount tested: ☐ Yes ☐ No
NIC Mapping and Labeling
Document the physical NIC identification for each node:
| Slot | Port | MAC Address | PCI Address | Purpose | VLAN(s) |
|---|---|---|---|---|---|
| Embedded | 1 | __:__:__:__:__:__ | ____ | Management | ____ |
| Embedded | 2 | __:__:__:__:__:__ | ____ | Management | ____ |
| Slot 1 | 1 | __:__:__:__:__:__ | ____ | Storage 1 | ____ |
| Slot 1 | 2 | __:__:__:__:__:__ | ____ | Storage 2 | ____ |
| Slot 2 | 1 | __:__:__:__:__:__ | ____ | Compute | Trunk |
| Slot 2 | 2 | __:__:__:__:__:__ | ____ | Compute | Trunk |
RDMA Configuration:
| Setting | Value |
|---|---|
| RDMA Technology | ☐ RoCEv2 ☐ iWARP ☐ N/A |
| RDMA NICs per Node | ☐ 2 ☐ 4 ☐ Other: ____ |
| RDMA Network Isolation | ☐ Dedicated VLANs ☐ Separate physical NICs |
| DCB/PFC Configured | ☐ Yes ☐ No |
Hardware Assessment Checklist
Pre-Deployment Validation
- All nodes are same model or validated compatible
- All nodes have identical hardware configuration
- Firmware versions match across all nodes
- Firmware meets minimum baseline requirements
- CPU cores meet minimum requirements (16+)
- RAM meets minimum requirements (128 GB+)
- Storage drives meet minimum requirements (2+ NVMe)
- Network adapters are RDMA-capable (for storage)
- iDRAC accessible from deployment workstation
- Service tags documented
- Hardware warranty verified and documented
Discovery Outputs
-
discovery/idrac-inventory.jsongenerated - Hardware validation script run with all checks passing
- Firmware update plan created (if updates needed)
- NIC mapping documented for all nodes
- RDMA configuration plan documented
Fibre Channel HBA Requirements (SAN Deployments)
This section applies only to disaggregated SAN deployments. Skip if using Storage Spaces Direct.
Disaggregated Azure Local clusters require Fibre Channel Host Bus Adapters (HBAs) in each node to connect to the external SAN array. HBAs must be validated for the Azure Local node model in use.
HBA Specifications
| Requirement | Details |
|---|---|
| Ports per node | Minimum 2 (one per fabric for redundancy) |
| Dual-fabric | Two independent FC switches strongly recommended |
| Driver support | Windows Server driver available from vendor |
| Certification | Validated against Microsoft Azure Local hardware catalog |
Azure Local nodes are validated with specific HBA models. Consult your server vendor's Azure Local configuration guide for the supported HBA list. The HBA driver must be installed before Arc registration — see Phase 03 Task 12.
FC Switch Port Planning
Each node contributes HBA ports to both fabrics. Use the following formula to determine the number of switch ports required:
Ports per fabric = (Number of nodes × HBA ports per node per fabric) + SAN array target ports
Example: 4-node cluster, 1 HBA port per node per fabric, 2 SAN target ports per fabric:
- Ports per fabric = (4 × 1) + 2 = 6 FC switch ports per fabric
Pre-Installation Checklist
- HBA model validated for the Azure Local node model
- FC switch ports allocated per formula above
- Vendor driver package downloaded
- SAN array FC target port WWPNs documented
- Dual-fabric FC switch inventory confirmed
References:
- Storage Architecture Planning
- Microsoft Learn — FC planning pattern without backup
- Microsoft Learn — FC planning pattern with backup
Next Steps
After completing hardware requirements documentation:
- For multi-site deployments, see Multi-Site Planning
- Proceed to Stage 11 - Hardware Provisioning
- Review Site Assessment - Ensure Site Assessment is complete