Dell AX System for Azure Local
Deployment and Operations Guide for Single-node Cluster
Notes, cautions, and warnings
|
|
NOTE: A NOTE indicates important information that helps you make better use of your product.
|
|
|
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
|
|
|
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
|
Copyright
About copying commands from this guide
|
|
CAUTION: Many PDF editors and viewers add a line break to the end of each line of text in a PDF. As a result, when you copy commands that wrap across multiple lines in a PDF, the copied command is in the wrong format. It contains erroneous line breaks that might cause the script to fail.
|
To address this known limitation, do one of the following:
- Paste the copied commands into a text editor and remove the line breaks.
- Use the HTML version of this document when you are copying commands.
Revision history
The revision history of the document is listed in the following table.
| Date | Document revision | Description of changes |
|---|---|---|
| October 2026 | 12 |
|
| June 2026 | 8 | Minor updates across the document for 2606 |
| April 2026 | 7 |
|
| April 2026 | 6 |
|
|
||
| October 2025 | 5 |
|
| August 2025 | 4 |
|
| May 2025 | 3 |
|
| May 2025 | 2 |
|
| September 2024 | 1 | Removed the "Create a Storage Account" section. |
| May 2024 | 0 | Initial publication |
Deployment Introduction
Document overview
The Dell AX Solutions for Microsoft product family includes:
- Dell AX System for Azure Local (based on Azure Stack HCI operating system)
- Dell AX System for Windows Server (not described in this guide)
This deployment and operations guide provides an overview of Dell AX System for Azure Local with a single-node cluster configuration. The guide includes:
- Guidance on how to integrate solution components
- Instructions for preparing and deploying the solution infrastructure
|
|
NOTE: This guide only applies to infrastructure that is built using the validated and certified AX nodes from Dell Technologies and the Azure Stack HCI operating system.
|
Audience and scope
The audience for this document includes systems engineers, field consultants, partner engineering team members, and customers with knowledge about deploying hyperconverged infrastructures (HCIs) with the Azure Stack HCI operating system, Hyper-V, and Storage Spaces Direct. Customers who do not have Volume License agreements with Microsoft can order AX nodes from Dell Technologies with a factory-installed operating system and OEM license or as a bare-metal installation.
An Azure Local instance can be deployed in the following ways:
- Dell Technologies Services-led—Certified deployment engineers ensure accuracy, speed, and reduced risk and downtime.
- Customer led—Customers who have the qualified level of technical expertise follow the instructions in this guide.
Assumptions
This guide assumes that deployment personnel understand the following technologies and tasks:
- AX nodes from Dell Technologies
- Deploying and configuring BIOS and integrated Dell Remote Access Controller (iDRAC) settings
Known issues
Before starting the cluster deployment, see Azure Local release information.
Solution Overview
Single-node cluster configuration overview
Dell AX System for Azure Local include various configurations of AX nodes from Dell Technologies. These nodes power the primary compute and storage cluster that is deployed as a hyperconverged infrastructure (HCI). The HCI uses a flexible solution architecture rather than a fixed component design.
Microsoft provides a feature to support a single-node cluster on an Azure Stack HCI operating system.
Single-node clusters are similar to standalone Storage Spaces nodes but are delivered as a Microsoft Azure service. Single‑node Azure Local instances support most Azure Local capabilities, except features requiring node‑level fault tolerance.
On a single-node cluster, there is no automatic provision of failover to another node. A hard drive is the fault domain in a single-node cluster, and only a single-tier configuration (All-Flash or All-NVMe) is supported.
|
|
NOTE: Node-level high availability cannot be supported on a single-node cluster. However, you can choose application-level or VM-level replication to maintain high availability in your infrastructure.
|
Single-node configuration
Like a multi-node cluster with Azure Stack HCI OS, a single-node cluster is delivered as a Microsoft Azure service and has all the hybrid-cloud features. Because the disk is the fault domain for a single-node cluster, it does not have to replicate any data over the network.
Dell Technologies recommends that you include an RDMA NIC in the setup. The RDMA NIC can help in future expansions or be used in VM traffic.
You can also use 25 GbE or 100 GbE adapters with Hyper-V Replica for application replication or Shared-Nothing Live Migration to move VMs to other clusters.
Solution Deployment
Solution deployment introduction
You can deploy Dell AX System for Azure Local by manually installing the operating system on AX nodes from Dell Technologies.
Each deployment has its own prerequisites, including configuring network switches, as described in this guide.
|
|
NOTE: Instructions in this deployment guide are applicable to the Azure Stack HCI operating system, version 24H2.
Each task in this deployment guide requires running one or more PowerShell commands. Dell Technologies recommends using these commands to complete the deployment tasks. |
Deployment prerequisites
Dell Technologies assumes that the management services that are required for the operating system deployment and Azure Local instance configuration are in the existing infrastructure where the instance is being deployed.
The following table describes the management services:
| Management service | Purpose | Required or optional |
|---|---|---|
| Active Directory | User authentication | Required only for AD-based deployments. |
| Domain Name System | Name resolution | Required |
| Azure | Deploy and manage | Required |
| DHCP | Hosts get IPs before and after host configuration using Network ATC | Optional |
Registering a Partner Admin Link (PAL) for Azure related solutions
Partner Admin Link (PAL) is a simple telemetry-based capability that is built into Microsoft Azure. PAL enables Microsoft to track partner involvement in Azure related technical engagements.
Adding a Dell Partner ID to the Service Principal does not provide Dell with additional access to the customer system and does not change any Azure Role-Based Account Controls (RBACs).
|
|
NOTE: Adding a Dell Partner ID to the Service Principal associates Dell to the customer entity, which is persistent. This means that changes in customer system administrators do not break this association.
|
Dell Technologies employees can add a PAL using the user ID associated with either the subscription or Service Principal that is used for Arc or for Azure Local registrations. During a deployment, the customer creates the Service Principal for their system.
Dell Technologies recommends that you use the user ID associated with the Service Principal for the registration as described in Add a PAL through the Azure portal by using Azure PowerShell with Service Principal user ID.
Alternatively, you can follow the procedure that is described in Add a PAL through the Azure portal using the subscription user ID.
Add a PAL through the Azure portal by using PowerShell
Dell Technologies recommends that you use the Azure portal and PowerShell with the Service Principal user ID to register the Partner Admin Link (PAL).
Before you begin
Before you begin, install the Microsoft Azure CLI extension to your local system where you run the registration. Run the following command:
az extension add --name managementpartner
|
|
NOTE: The CLI-based update is audit-log tracked.
|
To add a PAL to a customer account, do the following:
Procedure
Results
Add a PAL through the Azure portal using the subscription user ID
You can register the Partner Admin Link (PAL) with the subscription user ID through the Azure portal.
|
|
NOTE: Portal-based registrations tie the PAL association with the customer user entering the information. If the customer user changes roles, the portal-based PAL association also ends.
|
To add a PAL to a customer user account using the subscription user ID, do the following:
Procedure
Dell Technologies Partner IDs for Partner Admin Link
The following table provides a list of Microsoft Partner Network (MPN) partner IDs for Dell Technologies that can be used for Partner Admin Link (PAL) registration with Microsoft.
|
|
NOTE: For a country whose MPN partner ID is not listed in the following table, contact the applicable Strategic Partnerships email for help:
|
| Country | MPN ID |
|---|---|
| Argentina | 1973856 |
| Australia | 1576776 |
| Austria | 1444496 |
| Belgium | 1447258 |
| Brazil | 1563635 |
| Canada | 742767 |
| Chile | 2389235 |
| China | 2580218 |
| Colombia | 1736279 |
| Czech Republic | 1980606 |
| Denmark | 1449600 |
| Finland | 1993462 |
| France | 892181 |
| Germany | 1449416 |
| Greece | 3679221 |
| Hong Kong Sar | 2790298 |
| India | 2419713 |
| Indonesia | 2834572 |
| Ireland | 1447272 |
| Italy | 1446223 |
| Japan | 578508 |
| Korea | 2153293 |
| Malaysia | 2731874 |
| Mexico | 724848 |
| Netherlands | 1446198 |
| New Zealand | 1872429 |
| Norway | 1446238 |
| Panama | 1477223 |
| Poland | 3697305 |
| Portugal | 1552205 |
| Romania | 1735552 |
| Russia | 4543982 |
| Singapore | 2773797 |
| Slovakia | 3812320 |
| South Africa | 1970176 |
| Spain | 1004323 |
| Sweden | 1449417 |
| Switzerland | 1449592 |
| Taiwan | 5097219 |
| Thailand | 2345177 |
| Turkey | 3396579 |
| United Arab Emirates | 3159758 |
| United Kingdom | 1447267 |
| United States | 913990 |
Install Windows Admin Center
Microsoft Windows Admin Center is a browser-based management tool that enables you to monitor and manage Windows Servers, failover clusters, and hyperconverged clusters.
You can download the latest version of Windows Admin Center from Microsoft Windows Admin Center and install it on a supported operating system.
You can install Windows Admin Center directly on a managed node to manage itself. You can also install Windows Admin Center on a separate management station to manage the AX nodes remotely.
The Windows Admin Center installer wizard performs the configuration tasks that are required for Windows Admin Center functionality. These tasks include creating a self-signed certificate and configuring trusted hosts for remote node access. Optionally, you can supply the certificate thumbprint that is already present in the target node local certificate store. By default, Windows Admin Center listens on port 443, but you can change the port during the installation process.
|
|
NOTE: The automatically generated self-signed certificate expires in 60 days. If you intend to use Windows Admin Center in a production environment, ensure that you use a certificate-authority-provided SSL certificate.
|
For complete guidance on installing Windows Admin Center on supported operating systems, see the Microsoft article Install Windows Admin Center.
After the installation is complete, you can access Windows Admin Center at either https://ManagementStationName or https://ManagementStationName:<PortNumber>, as shown in the following figure.
Windows Admin Center All Connections window
Install Dell OpenManage Integration with Microsoft Windows Admin Center
You can install Dell OpenManage Integration with Microsoft Windows Admin Center.
Before you begin
Microsoft Windows Admin Center must already be installed.
Procedure
- In Windows Admin Center, go to .
- Under the Available extensions tab, select and install Dell OpenManage Integration.
Results
Predeployment configuration
Before deploying AX nodes, complete the required predeployment configuration tasks.
Complete the following predeployment configuration before deploying the Dell AX System for Azure Local solution.
Configuring iDRAC and BIOS
AX nodes from Dell Technologies are factory-configured with optimized system BIOS and iDRAC settings.
|
|
NOTE: Dell Technologies recommends that you verify that the settings you want to use for iDRAC and BIOS align with the configuration recommendations. You can do this verification either before deployment through the iDRAC and BIOS settings or after deployment through the Compliance window in the Dell OpenManage Integration extension.
|
|
|
CAUTION: Do not enable the Automatic Update feature in iDRAC or manually perform out-of-band component firmware updates through iDRAC. All firmware, BIOS, and drivers must align with the Support Matrix and be applied strictly through supported update workflows.
|
The iDRAC in AX nodes can be configured to obtain an IP address from a DHCP server or can be assigned a static IP address. When the Out-of-band (OOB) network is not configured to obtain IP addresses from a DHCP server, you must manually set a static IPv4 address on each iDRAC network interface. You can use KVM or other means to access the physical server console and set the addresses.
|
|
NOTE: For more details about BIOS and iDRAC settings, see BIOS and iDRAC configuration recommendations.
|
Verify iDRAC pass-through IP address subnet mask on AX-670 and AX-770 servers
Verify and configure the OS to iDRAC Pass-through USB NIC subnet mask on 17th-generation servers, including Dell AX-670 and Dell AX-770, to ensure proper in-band communication between the host operating system and Integrated Dell Remote Access Controller (iDRAC).
To verify the correct setting of the USB NIC, do the following:
Procedure
Configure BIOS settings including the IPv4 address for iDRAC
Perform these steps to configure the IPv4 address for iDRAC. You can also perform these steps to configure any additional BIOS settings.
Procedure
- During the system boot, press F2.
- At System Setup Main Menu, press iDRAC Settings.
- Under iDRAC Settings, select Network.
- Under IPV4 SETTINGS, at Enable IPv4, select Enabled.
- Enter the static IPv4 address details.
- Click Back, and then click Finish.
Configure Intel E810 or E823 NICs
The Intel E810 or E823 network adapter supports both iWARP and RoCE v2 RDMA protocols.
Before you begin
Ensure that the network card or port is enabled for RDMA traffic.
Procedure
Configure NVIDIA (Mellanox) ConnectX-6 NICs
To enable support for SR-IOV in the operating system and virtual machines, you must configure the NVIDIA (Mellanox) ConnectX-6 NICs for each port.
Before you begin
Procedure
Configure Broadcom NICs
The Broadcom 57504 and 57416 NICs support only RoCE v2 RDMA protocol and can be configured on both converged and hyperconverged deployments. Both OCP and PCIe cards are available.
Before you begin
Ensure that the network card or port is enabled for RDMA traffic.
Procedure
Operating system deployment
The following instructions are for manual deployment of the Microsoft Azure Stack HCI OS version 24H2 on AX nodes from Dell Technologies. Unless otherwise specified, perform the steps on the physical machine in the infrastructure that is part of Azure Local.
|
|
NOTE:
|
Adapter requirements
Azure Local requires using the same adapter card vendor and model for the machines in an instance that support instance operations. The ports that are used by the same Network ATC intent must use the same vendor, model, and speed.
Starting with Azure Local Solution version 2603, Azure Local instances that require NIC-level high availability can use the Azure portal or ARM templates to configure Network ATC intents using NIC ports from adapters that share the same PCIe Vendor ID and PCIe Device ID. This capability enables ports from both an OCP NIC and a PCIe riser NIC to be included within a single Network ATC intent, provided the adapters are of the same NIC model.
|
|
CAUTION: If you use optics or cables from one vendor with an adapter card from another vendor, Dell cannot guarantee that your configuration will work as expected. Before you mix vendor equipment in an Azure Local instance, consult the Dell Technologies cable and optics in the Support Matrix.
|
Manually deploy operating system using Dell golden-image ISO
You must use a Dell provided Azure Local golden-image ISO to install the baseline operating system image for Azure Local instances.
For an Azure Local solution version 2503 and later, you must use a Dell provided Azure Local golden-image ISO. To download the latest Dell provided golden-image ISO, go to Azure Local Support Matrix, and then click .
|
|
NOTE: To access any of the Dell provided Azure Local golden-image ISOs, you must have a Dell Support account.
|
Before you begin
Procedure
Configure host networking
Identify the network interface cards to be used for the management or compute traffic and assign the IP address to the first port.
Before you begin
|
|
NOTE: If you have a DHCP server in your environment, skip the procedure.
|
Ensure that the host is assigned to an IP address in the correct VLAN.
|
|
NOTE: The host IP, DNS, and gateway addresses that are used throughout the guide are examples. You must use the relevant IPs that are based on your environment.
|
|
|
NOTE: You can use the optional 1_AzLocal.ps1 script from Dell ProSupport GSE on GitHub to automate the operating-system configurations for host networking, rename the system name, and register with Azure. You must still do firmware updates before the deployment. Dell Technologies Solutions Engineering has not validated this code. Use at your own risk.
|
To log in to the host console of each system using the iDRAC virtual console and assign host IPs and respective VLANs, do the following:
Procedure
Change the hostname
By default, the operating system deployment assigns a random name as the host system name. For easier identification and uniform configuration, Dell Technologies recommends that you change the hostname to something that is relevant and easily identifiable.
|
|
CAUTION: The computer and cluster names cannot be more than 15 characters. If the name exceeds the character limit, the deployment will fail when the system tries to encrypt the volume.
|
Rename-Computer -NewName <NewHostName> -Restart
|
|
NOTE: The command induces an automatic restart at the end of the renaming operation.
|
Registry settings
Configuration to prepare nodes
#Enable Remote Desktop Set-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name "fDenyTSConnections" -Value 0 Enable-NetFirewallRule -DisplayGroup "Remote Desktop" #Configure time source using NTP server FQDN address w32tm /config /manualpeerlist:"<NTP Server 1 FQDN> <NTP Server 2 FQDN>" /syncfromflags:manual /update #Check time source w32tm /query /status #Optionally configure the machine to accept remote management and allow pings for troubleshooting purposes. #Enable ICMP firewall rule netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow
Configuring firewall settings
For Azure Stack HCI operating system, configure firewall settings for outbound endpoints and internal rules and ports. For more information about configuring the firewall settings, see Firewall requirements for Azure Local | Microsoft Learn.
Deploying an Azure Local instance
Azure Local instance deployment prerequisites
Before deploying Azure Local instance, you must ensure that the deployment prerequisites are met.
Deployment prerequisites
Prerequisites
Review requirements and complete the deployment prerequisites that are described in Prerequisites to deploy Azure Local - Azure Local | Microsoft Learn are met.
|
|
NOTE: Ensure that you unmount any virtual media from the iDRAC.
|
Management services
Dell Technologies assumes that the management services that are required for the operating-system deployment and cluster configuration are in the existing infrastructure where the Azure Local instance is being deployed.
The following table describes the management services:
| Management service | Purpose | Required or optional |
|---|---|---|
| Azure | Deploy and manage | Required |
| Active Directory | User authentication | Required only for AD-based deployments |
| Domain Name System | Name resolution | Required |
| DHCP | Hosts get IPs before and after host configuration | Optional |
Review requirements
- Ensure that the network configuration is in order.
- Ensure good Internet connectivity on the nodes.
- Ensure that your Azure subscription is registered with the required resource providers. Only the owner or contributor of the subscription can register the resources provider. For the most up-to-date list, see Assign required permissions for Azure Local deployment.
NOTE: For more information, see Assign required permissions for Azure Local deployment > Azure Local machine prerequisites.
Assigning required permissions for Azure Local deployment
To assign the required permissions for user roles, see Assign required permissions for Azure Local deployment.
Register machine with Azure Arc
Before registering the machine with Azure Arc:
- Ensure that the machine has the correct permissions assigned. To assign the relevant permissions, see Assign required permissions for deployment.
- If you have an Azure Arc gateway requirement in your environment, to understand the prerequisite requirements, see About Azure Arc gateway for Azure Local.
NOTE: Azure Arc gateway is only available in Azure Local version 2506 or later.
|
|
NOTE: Manual installation of PowerShell modules is no longer required. The registration procedure changed with the introduction of golden images (10.2503) or Microsoft-provided composed images.
|
You can use one of the following options to register the Azure Local machines with Azure Arc using PowerShell commands. For details, see:
- Register Azure Local with Azure Arc > With proxy
- Register Azure Local with Azure Arc > Without proxy
- Register Azure Local with Azure Arc using Arc Gateway > With proxy
- Register Azure Local with Azure Arc using Arc gateway > Without proxy
(Optional)
If you prefer to use a guided UI-based workflow instead of the Arc script, you can select the Via Configurator App tab on the Microsoft pages that are listed above.
|
|
NOTE: Dell Technologies has validated the registration of machines using the Configurator app. However, Dell Technologies does not officially support this functionality. If users encounter any issues, they must contact Microsoft directly.
|
Drift detection for Azure Local
For identifying configuration related deviations or troubleshooting issues in your Azure Local environment, see Drift Detection for Azure Local. You can run drift detection either before or after the cluster is created.
Check Azure Arc registration after reboot
During Azure Arc registration, when the update phase completes, if the system reboots, check the Arc registration status on the system after the reboot completes.
To check the Azure Arc registration, do the following:
|
|
NOTE: If you are using the latest Dell Golden-image ISO, you can ignore the following message if the message appears during the ARC registration process: "You are not running the latest Azure Local version. Older versions can only be deployed using the ARM template. Deployment using the Azure Portal cloud wizard is not supported."
|
Procedure
Prepare Active Directory for Azure Local instance
You must set up an Active Directory environment before deploying Azure Local instance. To prepare your Active Directory environment, see Prepare Active Directory for Azure Local deployment.
SBE package installation
When you use the Dell provided golden image to image a node, the SBE files are automatically placed in the C:\SBE directory. The SBE package is installed as part of the cluster deployment.
Deploy the Azure Local Instance
You can deploy an Azure Local instance in the following ways:
- Azure portal deployment without ARM templates, which only uses the UI in the Azure portal to deploy an Azure Local instance. For more information, see Deploy an Azure Local instance using the Azure portal.
- Manual ARM template deployment, which allows you to manually create an ARM template (JSON file) and deploy it using Azure CLI, PowerShell, or REST APIs. For more information, see: Deploy Azure Local via Azure Resource Manager deployment template.
|
|
NOTE: The creation of a storage intent is optional for single-machine deployments.
|
Deploy an Azure Local instance using Azure portal
The deployment wizard guides you through the creation of an Azure Local instance.
You can use the wizard to define all instance‑level and machine‑level configuration settings. The wizard guides you through the following windows:
- Basics
- Configuration
- Networking
- Management
- Security
- Advanced
- Tags (optional)
- Validation
- Review and create
To create an Azure Local instance:
Procedure
Deploy an Azure Local instance using the Microsoft ARM template
Deploy an Azure Local instance using the Microsoft Azure Resource Manager (ARM) template.
Before you begin
Before using the Microsoft Azure Resource Manager (ARM) template to deploy an Azure Local instance, you must complete the prerequisite procedures. Procedures are correct at publication but are subject to change without notice. For the most current details, see Deploy Azure Local via Azure Resource Manager deployment template > Prerequisites.
For more information about creating a service principal, service secret, and client secret for Azure Local release 2507 onwards, see Deploy Azure Local via Azure Resource Manager deployment template.
To deploy an Azure Local instance using the ARM template, do the following:
|
|
NOTE: Procedures are correct at publication but are subject to change without notice. For the most up-to-date details, see Deploy an Azure Local via Azure Resource Manager deployment template.
|
Procedure
External SAN support for Azure Local
Explains how Azure Local integrates with external SAN storage and describes supported deployment architectures, storage protocols, and configuration workflows.
Overview
External SAN support enables hybrid deployments that combine Storage Spaces Direct (S2D) local storage with external SAN storage. This architecture allows organizations to reuse existing SAN investments while running Azure Local workloads.
The hybrid deployment model provides flexibility to place workloads on either local Storage Spaces Direct storage or external SAN storage based on performance, capacity, and operational requirements.
This documentation applies to post-deployment integration of external SAN storage with Azure Local clusters.
External SAN support deployment workflow
To integrate external SAN storage with Azure Local:
- Review supported SAN solutions.
- Verify system requirements.
- Plan SAN integration.
- Configure Fibre Channel or iSCSI connectivity.
- Configure MPIO.
- Verify SAN connectivity.
- Create Cluster Shared Volumes.
- Configure workload storage paths.
- Validate operations.
For more information, see Enable External Storage on Azure Local.
Hybrid Deployment Architecture for Azure Local
Explains how Storage Spaces Direct and external SAN storage are used together in a hybrid Azure Local deployment.
Overview
A hybrid deployment combines local Storage Spaces Direct storage with external SAN storage.
In a hybrid deployment:
- Compute nodes run the Azure Local operating system and host virtual machines.
- Local storage is provided by Storage Spaces Direct.
- External SAN storage is presented to cluster nodes through Fibre Channel or iSCSI.
- Cluster Shared Volumes can consume storage from either Storage Spaces Direct or SAN LUNs.
- Workloads allows choosing the right storage tier for each workload.
Benefits of using hybrid deployment architecture
- Reuse existing SAN infrastructure.
- Scale storage independently from compute.
- Maintain existing SAN operational practices.
- Provide enterprise-class performance and reliability.
- Support dual-fabric redundancy and multipath failover.
Supported SAN solutions for Azure Local
Lists supported storage arrays and storage protocols for Azure Local external SAN deployments.
Supported storage vendors
Azure Local currently supports:
- Dell PowerStore T appliances
- Dell PowerStore Q appliances
|
|
NOTE: PowerStore systems must run PowerStoreOS version 3.0 or later.
|
Supported storage protocols
- Fibre Channel (FC): FC provides low-latency block storage connectivity through dedicated storage fabrics.
- iSCSI: iSCSI provides block storage connectivity over Ethernet networks using TCP/IP.
For more information, see Supported SAN solutions on Azure Local.
External SAN requirements
Lists requirements for Azure Local external SAN deployments.
Azure Local requirements for external SAN deployments
Lists the Azure Local requirements for integrating external SAN storage.
System requirements
To use external SAN storage with Azure Local, the environment must meet the following requirements:
- Azure Local version 2604 or later
- Fully deployed and operational Azure Local cluster
- Multipath I/O (MPIO) enabled
- High-bandwidth, low-latency connectivity between Azure Local nodes and the SAN array
Fibre Channel requirements for Azure Local external SAN deployments
Lists the Fibre Channel (FC) infrastructure and hardware requirements for connecting Azure Local to external SAN storage.
System requirements
To use FC connectivity with Azure Local, the environment must meet the following requirements:
- Windows Server 2025-certified FC host bus adapters (HBAs) installed on all nodes
- Certified and supported HBA drivers are installed on all nodes. For information about the supported component models, see Dell AX System for Azure Local Support Matrix.
- Properly configured FC fabrics
- Independent vSAN configured for each fabric
- Dual-fabric deployment recommended for redundancy and high availability
iSCSI requirements for Azure Local external SAN deployments
Lists the networking and adapter requirements for connecting Azure Local to external SAN storage using iSCSI.
System requirements
To use iSCSI connectivity with Azure Local, the environment must meet the following requirements:
- Dedicated physical network adapters for iSCSI traffic
- Matching NIC firmware and driver versions are installed across all nodes. For information about the supported component models, see Dell AX System for Azure Local Support Matrix.
- Consistent network adapter configuration on all nodes
- Reliable, high-bandwidth, low-latency iSCSI network connectivity
- Optional CHAP authentication for additional security
SAN array requirements for Azure Local external SAN deployments
Lists the storage array requirements for integrating external SAN storage with Azure Local.
System requirements
To use external SAN storage with Azure Local, the SAN array must meet the following requirements:
- LUNs presented to all cluster nodes
- NTFS-formatted volumes for Cluster Shared Volumes (CSVs)
- Consistent MPIO configuration across all nodes
- Dedicated LUNs assigned to individual Cluster Shared Volumes
Planning considerations for Azure Local external SAN deployments
Describes the planning activities that should be completed before integrating external SAN storage with an Azure Local cluster.
Overview
Proper planning helps ensure a successful external SAN integration and reduces deployment issues. Before connecting SAN storage to an Azure Local cluster, review storage, network, and infrastructure requirements.
Planning activities
Before integrating external SAN storage with Azure Local:
- Verify cluster deployment: Ensure that the Azure Local cluster is fully deployed and operational.
- Plan the storage architecture: Determine which workloads will use Storage Spaces Direct (S2D) storage and which workloads will use external SAN storage.
- Assess SAN capacity: Verify that sufficient LUN capacity is available to meet workload requirements.
- Review SAN documentation: Consult SAN vendor documentation for LUN creation, zoning, masking, and connectivity requirements.
- Prepare network infrastructure: Verify that Fibre Channel or iSCSI networking is configured and operational.
- Document WWNs or IQNs: Collect initiator identifiers that will be used for zoning and LUN masking configuration.
Configuration considerations for Azure Local external SAN deployments
Describes deployment and configuration considerations for integrating external SAN storage with Azure Local.
External SAN deployments require consistent configuration across all cluster nodes and supporting infrastructure. Review the following considerations before configuring SAN connectivity:
- Delay Fibre Channel zoning until after deployment: Do not zone Fibre Channel host bus adapter (HBA) World Wide Names (WWNs) to the SAN array until Azure Local deployment is complete. This helps prevent deployment and discovery issues.
- Use identical HBA configurations: Configure all cluster nodes with the same HBA model, firmware version, and driver version.
- Maintain MPIO consistency: Apply identical MPIO settings across all cluster nodes.
- Plan for node reboots: Changes to MPIO policies require a rolling reboot of all cluster nodes.
Configure Fibre Channel SAN connectivity for Azure Local
Describes how to connect an Azure Local cluster to external SAN storage using Fibre Channel.
Before you begin
Before configuring Fibre Channel connectivity, ensure that the following requirements are met:
- Azure Local cluster is fully deployed and running version 2604 or later.
- Fibre Channel host bus adapters (HBAs) are installed on all cluster nodes.
- Fibre Channel fabrics are configured with independent VSANs.
- SAN array is accessible on the FC fabric with management access configured.
Procedure
Results
All cluster nodes can access the Fibre Channel SAN LUNs, and the storage is ready for CSV configuration.
Configure iSCSI SAN connectivity for Azure Local
Describes how to connect an Azure Local cluster to external SAN storage by using iSCSI.
Before you begin
Before configuring iSCSI connectivity, ensure that the following requirements are met:
- Azure Local cluster is fully deployed and running version 2604 or later.
- Dedicated physical network adapters are available for iSCSI traffic. Virtual network adapters (vNICs) are not supported.
- Network adapter firmware and drivers comply with Azure Local hardware catalog requirements.
- The iSCSI target array is accessible on the network with management access.
Procedure
Results
All cluster nodes can access the iSCSI SAN LUNs through the configured network paths, and the storage is ready for multipath validation and Cluster Shared Volume (CSV) configuration.
MPIO for Azure Local external SAN deployments
Explains the role of Multipath I/O (MPIO) in Azure Local external SAN deployments.
Overview
Multipath I/O (MPIO) provides redundancy and load balancing for SAN storage connections. MPIO must be configured consistently across all Azure Local cluster nodes.
To integrate MPIO with Azure Local external SAN deployments, complete the folowing:
Default MPIO settings for Azure Local
Lists the default Multipath I/O (MPIO) settings included with Azure Local version 2604 and later.
| Setting | Default value |
|---|---|
| PathVerificationState | Enabled |
| PathVerificationPeriod | 30 |
| PDORemovePeriod | 20 |
| RetryCount | 6 |
| RetryInterval | 3 |
| CustomPathRecovery | Disabled |
| CustomPathRecoveryTime | 20 |
| DiskTimeoutValue | 60 |
| Load Balance Policy | Round Robin (RR) |
| NewDiskPolicy | OfflineShared |
Register storage vendor with MPIO
Describes how to register your storage vendor with Microsoft Device Specific Module (MSDSM) for MPIO management.
Before MPIO can manage storage array LUNs, your storage vendor must be registered with Microsoft Device Specific Module (MSDSM). Registering your storage vendor allows MPIO to claim and manage the storage devices presented to Azure Local.
Procedure
Results
The Dell PowerStore storage array is registered with MSDSM, allowing MPIO to claim and manage the presented SAN LUNs.
Configure the MPIO load-balancing policy
Describes how to configure the MPIO load-balancing policy for SAN-connected storage.
Procedure
Set-MSDSMGlobalDefaultLoadBalancePolicy -Policy RR
Results
MPIO uses the Round Robin load-balancing policy to distribute storage traffic across available paths on all cluster nodes.
Configure Dell PowerStore MPIO timers
Apply Dell PowerStore MPIO timer settings and perform the required rolling reboot on Azure Local cluster nodes.
After configuring the Dell PowerStore MPIO timer settings and the MPIO load-balancing policy, perform a rolling reboot of each cluster node to ensure that the configuration changes take effect.
Perform this procedure on one node at a time to maintain cluster availability.
Procedure
Results
The Dell PowerStore MPIO timer settings and load-balancing policy are applied consistently across all cluster nodes, and storage is synchronized and healthy before workloads resume.
Verify the MPIO configuration
Describes how to verify MPIO devices, path availability, and load-balancing configuration on Azure Local nodes.
After configuring MPIO, verify that all SAN LUNs are claimed by MPIO, multiple storage paths are available, and the configured load-balancing policy is applied consistently across all cluster nodes.
Procedure
Results
MPIO devices, storage paths, SAN disks, and load-balancing policies are verified and operating as expected.
Post-deployment verification for Azure Local external SAN deployments
Explains the validation and monitoring activities that should be performed after integrating external SAN storage with Azure Local.
After configuring external SAN connectivity, verify that the SAN LUNs are visible to all cluster nodes, that Multipath I/O (MPIO) is operating correctly, and that storage paths remain healthy during normal cluster operations.
Complete the following activities after configuring Fibre Channel or iSCSI SAN connectivity:
Verify SAN connectivity for Azure Local external SAN deployments
Describes how to verify that all Azure Local cluster nodes can access the SAN LUNs presented by the storage array.
Before using external SAN storage for workloads, verify that all cluster nodes can detect and access the presented SAN LUNs.
Procedure
Results
All cluster nodes can access the expected SAN LUNs, and the presented storage is healthy and available for workload use.
Verify MPIO path availability for SAN storage
Describes how to verify that SAN LUNs are accessible through multiple active MPIO paths on Azure Local cluster nodes.
After configuring Multipath I/O (MPIO), verify that each SAN LUN has multiple active paths and that path failover protection is functioning as expected.
Procedure
Results
All SAN LUNs are accessible through multiple active MPIO paths, providing redundancy and load balancing for storage traffic.
Monitor SAN path health for Azure Local external SAN deployments
Describes how to monitor SAN path health, failover events, and cluster health in an Azure Local external SAN environment.
After configuring SAN connectivity and MPIO, regularly monitor storage paths to identify path failures, failover events, and cluster health issues before they affect workload availability.
Procedure
Results
SAN path health, failover activity, storage performance, and cluster health are monitored and operating as expected.
Create and use external SAN storage in Azure Local
Explains how to provision external SAN storage and make it available for Azure Local workloads.
After verifying SAN connectivity and Multipath I/O (MPIO) configuration, you can provision external SAN storage for Azure Local workloads. Using SAN-backed Cluster Shared Volumes allows virtual machines and applications to consume external SAN storage while remaining highly available across the cluster.
To provision and use external SAN storage:
Create Cluster Shared Volumes from SAN LUNs
Describes how to create Cluster Shared Volumes (CSVs) from SAN-provided LUNs.
After verifying SAN connectivity and MPIO configuration, create Cluster Shared Volumes from the SAN LUNs before using the storage for workloads.
Procedure
Results
The SAN LUN is available as a Cluster Shared Volume and can be used by Azure Local workloads.
Configure workload storage paths on SAN-backed Cluster Shared Volumes
Describes how to configure workload storage locations on SAN-backed Cluster Shared Volumes.
After creating Cluster Shared Volumes, configure workload storage locations so that virtual machines and applications use SAN-backed storage.
Procedure
Results
Virtual machines and applications store data on SAN-backed Cluster Shared Volumes.
Troubleshoot Azure Local external SAN deployments
Provides troubleshooting guidance for common issues encountered when integrating external SAN storage with Azure Local.
External SAN storage integration issues typically involve storage path visibility, LUN presentation, or multipath failover. When troubleshooting SAN connectivity, verify storage connectivity, MPIO configuration, zoning, masking, and hardware health.
Troubleshoot MPIO paths not visible
Describes how to diagnose and resolve issues where MPIO paths are not visible or are not functioning correctly.
Use the following steps when you observe any of these symptoms:
- SAN LUNs are visible, but expected MPIO paths are missing.
- Storage devices do not appear to be managed by MPIO.
- Storage path redundancy is unavailable.
Procedure
Results
MPIO paths are visible and operating correctly.
Troubleshoot SAN LUN masking issues
Describes how to diagnose and resolve SAN LUN masking issues that prevent LUN visibility across cluster nodes.
Use the following steps when you observe any of these symptoms:
- SAN LUNs are visible on some nodes but not others.
- Newly presented LUNs do not appear on cluster nodes.
- Inconsistent storage visibility across the cluster.
Procedure
Results
All SAN LUNs are visible to all cluster nodes.
Troubleshoot SAN path failover issues
Describes how to diagnose and resolve SAN storage path failover issues.
Use the following steps when you observe any of these symptoms:
- Storage traffic does not fail over to alternate paths.
- MPIO path recovery does not occur.
- Storage connectivity is lost during path failures.
Procedure
Results
Storage paths fail over and recover correctly when path failures occur.
Deploy Azure Local using Local Identity with Azure Key Vault
This chapter does not replace the standard Azure Local deployment workflow. Unless explicitly stated otherwise, all deployment steps follow the procedures that are described in:
- Chapter 3: Solution Deployment
- Chapter 4: Deploying Azure Local Instance with Azure Stack HCI OS, version 24H2 or later
About Local Identity with Azure Key Vault
Overview
Azure Local can be deployed without Active Directory by using a local identity model with Azure Key Vault, previously known as AD-less deployment. This deployment option is available starting with Azure Local version 2411 and later.
In a local identity deployment:
- A dedicated local administrator account is used on each machine.
- Certificate‑based authentication is configured cluster‑wide.
- Azure Key Vault is used to securely back up secrets such as BitLocker keys and other critical configuration data that is required for secure cluster operation.
Benefits of local identity with Azure Key Vault (without Active Directory)
- Minimal edge infrastructure: Enables secure identity and secret handling in environments that do not use Active Directory.
- Secure secret store: Azure Key Vault stores sensitive items such as BitLocker keys and node passwords, reducing the risk of unauthorized access and improving overall security.
- Simplified management: Consolidates deployment and local identity secrets in a single vault, making them easier to manage and retrieve.
- Simplified deployment: Azure portal workflows store required secrets in Azure Key Vault, reducing reliance on Active Directory and helping simplify Operational Technology network firewall configurations.
Most deployment steps are identical for Active Directory–based Azure Local deployments and deployments that use local identity with Azure Key Vault. For more information, see Deploy Azure Local using local identity with Azure Key Vault.
Key differences from Active Directory–based deployments
| Area | Active Directory deployment | Local Identity deployment |
|---|---|---|
| Identity provider | Active Directory | Local administrator account |
| Authentication | AD objects | Certificate‑based authentication |
| Secret storage | Cluster and AD | Azure Key Vault |
| Domain join | Required | Not supported |
| AD preparation | Required | Not applicable |
Deployment prerequisites for Azure Local deployment using local identity
Dell Technologies assumes that the management services that are required for the operating system deployment and Azure Local instance configuration are in the existing infrastructure where the instance is deployed.
For more information, see Prerequisites for cluster deployment using local identity.
The following table describes the management services:
| Management service | Purpose | Required or optional |
|---|---|---|
| Domain Name System | Name resolution | Required |
| DNS suffix | Enables workgroup cluster nodes to communicate using fully qualified domain names. | Required |
| Azure | Deploy and manage | Required |
| Static IP addresses for management | Assign IP addresses to hosts before and after host configuration using Network ATC | Required |
| New local non–built‑in user in the local Administrators group | Administrative user account for deployment and management | Required |
Prepare Azure Local machines for Local Identity
Before deploying AX nodes, complete the required predeployment configuration tasks.
Perform all machine preparation procedures described in Chapter 3: Solution Deployment, including:
- Host network configuration
- Hostname configuration
- Node preparation configuration
These procedures are identical for Active Directory and Local Identity deployments.
Local identity-specific machine configuration procedures
Create DNS A records for hosts and cluster
Create DNS A records for the hosts and cluster to enable name resolution for individual machines and the cluster name object (CNO).
Procedure
- Create a DNS A record for each machine.
- Create a DNS A record for the cluster name (CNO).
- (Optional) Create PTR records.
Create a local user and add to the local Administrators group
Create a dedicated local administrative user on each Azure Local node for deployment and cluster management operations.
Before you begin
- Azure Local deployments that use local identity require a non built-in local administrator account. This account is used for cluster-wide management operations, such as adding or repairing nodes, and must be consistent across all nodes in the Azure Local instance.
NOTE: You are responsible for life cycle management of this account, including expiration, rotation, and security. The default local policy sets a maximum password age of 42 days. This can be modified using PowerShell or by changing the underlying password policy configuration.
- Use the same username and password on all machines. The password must meet Azure complexity requirements and include at least 14 characters with a combination of lowercase letters, uppercase letters, numbers, and special characters.
Procedure
|
|
NOTE: Do not use the built-in Administrator account.
|
# Create new dedicated user $AdminUser = '<DedicatedAdminUser>' # Sample data: # $AdminUser = 'adless-admin' $Credentials = Get-Credential -UserName $AdminUser -Message 'Enter password:' $Description = 'Local AD-less user' New-LocalUser -Name $AdminUser -Password $Credentials.Password -FullName $AdminUser -Description $Description # Add user to local admin group Add-LocalGroupMember -Group 'Administrators' -Member $AdminUser # Optional: Validate the new user account Get-LocalGroupMember -Group administrators # The output should include the user account specified by $AdminUser. # If it is not listed, the account was not created or added successfully.
Deploy the Azure Local instance using local identity with Azure Key Vault
You can deploy an Azure Local instance in the following ways:
- Azure portal deployment without ARM templates, which only uses the UI in the Azure portal to deploy an Azure Local instance. For more information, see Deploy an Azure Local instance using the Azure portal.
- Manual ARM Template deployment, which allows you to manually create an ARM template (JSON file) and deploy it using Azure CLI, PowerShell, or REST APIs. For more information, see: Deploy Azure Local via Azure Resource Manager deployment template.
- Azure portal deployment with Quickstart Template (template deployment), which uses the UI in the Azure portal to deploy ARM templates. This method is not documented in this guide.
Deploy Azure Local Instance using Azure portal
The Azure portal wizard guides you through steps to create an Azure Local instance.
You can use the wizard to define all instance‑level and machine‑level configuration settings. The wizard guides you through the following windows:
- Basics
- Configuration
- Networking
- Management
- Security
- Advanced
- Tags (optional)
- Validation
- Review and create
To create an Azure Local instance:
- To start the wizard from , select Deploy Azure Local.
- Under Get Started, in Deploy Azure Local, select Create instance.
- Specify the Subscription name, Resource group, and Instance name.
Instance name = Cluster Name Object (CNO)
- For Cluster options, select either Standard or Rack aware.
- For Identity provider, select Local identity with Azure Key Vault.
- Select the machines to be added to the Azure local Instance. Click Add machines.
The required extensions are automatically installed during this step.
- When the extensions are installed and the status shows as Ready, click Validate selected machines.
- To create a new key vault, enter a Key vault name, and then click Create a new key vault.
NOTE:
- If a previously created key vault for a decommissioned instance with the same name exists, you must first delete and purge the old key vault before creating one.
- Azure Local does not support deploying a cluster by using an existing Azure key vault that has private endpoints enabled.
Create a new key vault
- To go to the next window, click Next: Configuration.
- In the Configuration window, enter details about the instance.
- To go to the next window, click Next: Networking, shown in the following figure.
Deployment wizard - Networking window
- In the Networking window, for Storage connectivity, choose whether you use a network switch for the storage network.
- Under Group network traffic types by intent, based on your network topology, select the Networking pattern. For a single- machine instance, Dell Technologies recommends that you select Group Management and Compute (no storage).
The following table shows the Quality of Service (QoS) flow priorities for each network type:
QoS priorities for network intents. The table shows the QoS flow priorities that are based on traffic class for each network type. Traffic class Purpose QoS flow ETS bandwidth allocation 3 RDMA (SMB Direct) Enabled 50 percent 7 Cluster network Disabled - 10 GbE equals 2 percent
- Greater than 25 GbE equals 1 percent
0-2, 4-6 0 - Best-effort traffic Disabled Remaining percentage distributed across the traffic classes - Under Provide intent details, for management-network-intent creation, select the network adapters.
- Under Allocate IP addresses to the system and services, provide the required details as shown in the following figure.
Allocate IP addresses
- Under Compute_Management, to update information such as network intent, data center bridging, and adapter properties including Jumbo Frame size and RDMA protocol, click Customize network settings.
NOTE: For management network intents, RDMA must be disabled, as shown in the following figure.
Customize network values window with disabled RDMA protocol
NOTE: Microsoft recommends that you set System Traffic Priority to 7 for new cluster deployments. A priority value of 5 is also supported and acceptable. Ensure that the QoS settings on the top‑of‑rack (ToR) switches match the QoS settings that are configured in the host operating system.For more information about this step, see Specify network settings.
- Under Management shown in the following figure, to identify this system when creating resources, enter the Custom location name.
Management window
- Continue to specify Local Administrator details. Use the same account that was created earlier. See Create a local user and add to the local Administrators group. Do not use the built-in Administrator account.
- Click Next: Security.
- Under Security shown in the following figure, Dell Technologies and Microsoft recommends that you choose Recommended security settings, which offers the highest level of security settings.
Deployment wizard - Security window
- Click Next: Advanced.
- Under Advanced, choose Create workload volumes and required infrastructure volumes.
For more information, see Optionally change advanced settings and apply tags.
- Click Next: Tags.
- Under Tags, enter tag information (optional).
- Click Next: Validation.
- Under Validation, click Start validation, as shown in the following figure.
Validation of system readiness
For more information, see Validate the system.
The system creates a resource object and its components for the instance. The validation process typically completes within 15 minutes for a single-server deployment, though it may take longer depending on system conditions or environmental factors. This process assesses the system readiness for cluster deployment.
- Click Next: Review + create.
- The Review + create window shows the configuration information that you entered or selected in the previous steps for creating the instance. To return to a previous step to change any settings, click Previous.
- To start the instance creation process, review and confirm your settings, and then click Create .
When the deployment is complete, all tasks display a status of Success.
Validation of deployment creation success
- To access your Azure Local instance remotely, enable Remote Desktop Protocol (RDP).
For more information about deploying an instance, see Deploy Azure Local using the Azure portal.
For more information about enabling RDP, see Enable RDP.
Deploy an Azure Local instance using the Microsoft ARM template
Deploy an Azure Local instance using the Microsoft Azure Resource Manager (ARM) template.
Before you begin
Before using the Microsoft Azure Resource Manager (ARM) template to deploy an Azure Local instance, you must complete the prerequisite procedures. Procedures are correct at publication but are subject to change without notice. For the most current details, see Deploy Azure Local via Azure Resource Manager deployment template > Prerequisites.
For more information about creating a service principal, service secret, and client secret for Azure Local release 2507 onwards, see Deploy Azure Local via Azure Resource Manager deployment template.
To deploy an Azure Local instance using the ARM template, do the following:
|
|
NOTE: Procedures are correct at publication but are subject to change without notice. For the most up-to-date details, see Deploy an Azure Local via Azure Resource Manager deployment template.
|
Procedure
Post-deployment tasks
Perform necessary post-deployment tasks including verifying BitLocker keys in Azure Key Vault, updating configurations, recovering deleted Key Vaults, and monitoring Key Vault integration health.
- To verify BitLocker keys and recovery administrator passwords are securely backed up to Azure Key Vault, see Verify secrets back up to Key Vault.
- To update a new Key Vault with configurations, see Update Key Vault on Azure Local.
- To recover a deleted Key Vault and resume backups, see Recover a deleted Key Vault.
- To monitor the health of Key Vault integration, see Alerts for Key Vault extension.
Management tool compatibility for Azure Local with Azure Key Vault
Management tooling support varies across the Azure Local ecosystem for environments that use Azure Key Vault for identity management.
Management tools
The following table provides the management tools that are supported for Azure Local environments that use Azure Key Vault for identity management:
| Category | Tools | Notes |
|---|---|---|
| Supported |
|
Fully supported for typical management and monitoring workflows. |
| Unsupported/Limited support |
|
Not supported or only partially supported - avoid relying on these as primary management tools. |
| Mixed compatibility | Microsoft Management Consoles (MMCs) |
|
Post-deployment Updates and Maintenance
Post-deployment best practices
Dell Technologies recommends that you follow the guidelines that are described in this section.
Antivirus exclusions
As part of best practices, Dell Technologies and Microsoft recommend that you plan appropriate antivirus exclusions.
Azure Local instance machines by default are deployed and configured with security features including Microsoft Defender Antivirus.
If you prefer to use non-Microsoft antivirus and security software, Dell Technologies and Microsoft recommend that your vendor has validated your preferred software for Azure Local.
Follow the guidance and antivirus exclusions on Security features for Azure Local.
|
|
CAUTION: If your antivirus software is not cluster-aware, see Antivirus software that isn't cluster-aware may cause problems with Cluster Services.
|
Suspend and resume a cluster node
Before you begin
- You have local administrator privileges to access the cluster node
- Cluster node is running Azure Local version 2311.2 or later
- Client used to connect to Azure Local has PowerShell installed
- Suspend or resume the cluster node in Windows Failover Clustering
|
|
NOTE: Verify the health status of the cluster and volumes before and after the process using the relevant PowerShell commands.
|
Procedure
Suspend node
Resume node
Results
Update Azure Local instances using SBE package
Download Connector
Download Connector is a component in the Solution Builder Extension (SBE) package that automates the download of new SBE bundles as they become available for your Azure Local instance.
When an SBE that includes the Download Connector is installed on your instance, manual downloading and importing of subsequent versions is no longer required. The update service automatically retrieves the next available SBE, similar to how solution updates are handled.
Download Connector is part of SBE version 4.1.2505.1501 and later. These versions also feature system and update health checks that proactively verify connectivity to the required remote resource before downloading the next SBE. System health checks run daily, while update health checks occur at the beginning of the update process.
Download Connector firewall requirements
The Solution Builder Extension (SBE) Download Connector requires outbound Internet access to retrieve update bundles and catalogs.
The SBE Download Connector that runs on the Azure Local instance must periodically connect to Internet resources to enable Download Connector to download SBE bundles for your instance. The following table lists the outbound connectivity that is required:
| Endpoint description | Endpoint URL | Port |
|---|---|---|
| SBE bundle download | dl.dell.com/* | 443 |
| SBE download catalog | downloads.dell.com/filestore/Prod/SbeDownloadCatalog/AX_SBE_Download_Catalog.xml | 443 |
| SBE download catalog redirection | aka.ms/DellAzureLocalSBEDownloadCatalog | 443 |
| Digicert Certificate Revocation Status | http://crl3.digicert.com/* | 80 |
| Digicert Certificate Revocation Status | http://crl4.digicert.com/* | 80 |
For more information about SBE packages with Download Connector capability and installation procedure, see Solution Builder Extensions for Azure Local - Integrated System AX Server Release Notes.
SBE package update prerequisites
You can apply solution updates to your Azure Local instance using the Dell Solutions Builder Extensions (SBE) package. You can update your instance either by:
- Downloading offline solution updates
- Discovering online solution updates and then applying the updates
You must ensure that:
- You have a functioning Azure Local instance with Azure Stack HCI operating system, version 24H2. The instance is registered to Azure.
- You have access to the online solution update package or offline solution update package download.
You can do these updates either by:
- Using PowerShell
- Using Azure Update Manager service from the Azure portal
|
|
NOTE: You must run the Get-SolutionUpdateEnvironment PowerShell command. If the SBE package (latest version is 4.0.0.0) is only partially installed, complete the installation by following the procedures that are outlined in Download Connector – Automated download of future SBE release > Installation in the Azure Local Dell Solution Builder Extensions Release Notes (Dell 2512) on GitHub.
|
Update SBE package using PowerShell (online)
The process for updating the SBE package using PowerShell in online mode can be used for both multi-machine or single-machine Azure Local instances.
Procedure
Updating SBE package using PowerShell (offline)
The process for updating the SBE package using PowerShell in offline mode can be used for both multi-machine or single-machine Azure Local instances.
|
|
CAUTION: Before proceeding, verify that sufficient space is available on the selected Cluster Shared Volume (CSV).
|
To do an offline solution update, follow the steps that are described in Azure Local Dell Solution Builder Extensions Release Notes > Installation
Update SBE package using Azure portal
Azure Update Manager allows you to apply, view, and manage updates for your cluster node (also known as Azure Local instance machine).
To identify and install updates, do the following:
Procedure
GPU Integration
Installing and configuring GPUs on AX platforms
You can install and configure GPUs on AX platforms. For a list of GPUs that are supported on AX nodes from Dell Technologies, see the Dell Solutions for Microsoft Azure > Azure Local Support Matrix.
|
|
NOTE: You must order AX nodes that are preconfigured for GPU integration, or converted for GPU use, including the required components.
|
Guidelines for installing GPU hardware
For deployed Azure Local instance, or Windows Server 2025 (or later instance before performing any GPU hardware changes, place the target machine into maintenance mode (pause and drain).
Use Dell Support to follow the platform-specific GPU installation procedure for your server model.
For model-specific GPU slot or riser matrices and riser configuration options, see the applicable Dell installation and service manual sections for your platform, including:
- Expansion card riser specifications
- Expansion card installation guidelines
- GPU kit (if available)
- GPU specifications
For the most up-to-date list of supported GPUs for AX nodes, see the Dell Solutions for Microsoft Azure > Azure Local Support Matrix.
GPU Discrete Device Assignment (DDA)
You can use Discrete Device Assignment (DDA) on supported GPUs so that the Azure Stack HCI and Windows Server 2025 and later operating system servers contain GPU-enabled clustered VMs.
For a list of supported GPUs, see the latest version of the Dell Technologies Solutions for Microsoft Azure Local > Support Matrix.
Download and install guest drivers
Download and install guest drivers from NVIDIA Application Hub.
To download and install a guest driver, do the following:
Procedure
Results
GPU partitioning
On the Azure Stack HCI or Windows Server 2025 or later operating-system servers, you can use GPU partitioning (GPU-P) for different workloads, such as artificial intelligence. To avoid mistakes and for a streamlined visual experience, Dell Technologies recommends that you use Windows Admin Center (WAC) for GPU-P.
For the latest supported GPU-P enabled GPUs, see Dell Technologies for Microsoft Azure Local > Support Matrix.
Dell Technologies servers do not come with a GPU-P driver. The GPU-P driver requires separate licensing from NVIDIA. For more information about licensing options and the benefits of GPU-P, see: NVIDIA Virtual GPUs.
|
|
NOTE: For GPU-P to work, you must have both a host driver and a GPU-P enabled guest (VM) driver and the correct activated license.
|
Download and install host and guest drivers
For GPU partitioning (GPU-P) to work, you must have both a host driver and a GPU-P enabled guest (VM) driver and the correct activated license.
Procedure
Dell OpenManage Integration with Windows Admin Center
Overview of Dell OpenManage Integration with Windows Admin Center
Dell OpenManage Integration with Windows Admin Center (OMIMSWAC) enables IT administrators to manage the HCI that is created by using Dell AX System for Azure Local. OMIMSWAC simplifies the tasks of IT administrators by remotely managing the AX nodes and clusters throughout their life cycle.
For more information about the features, benefits, and installation of OMIMSWAC, see the Dell Technologies documentation at Dell OpenManage Integration with Microsoft Windows Admin Center.
Managing Microsoft HCI-based clusters
Procedure
- In the upper left of Windows Admin Center, from the menu, select Cluster Manager.
- In the Cluster Connections window, click the cluster name.
- In the left pane of Windows Admin Center, under EXTENSIONS, click Dell OpenManage Integration.
- Review the Dell Software License Agreement and Customer Notice, and select the checkbox to accept the terms of the license agreement.
Validate and remediate a cluster
By using the HCI Configuration Profile (HCP) Compliance feature, you can see the cluster compliance by using HCP checks, see the recommendations, and remediate noncompliant components.
Before you begin
Before you begin, the cluster:
- Must be Dell AX System for Azure Local, version 24H2.
- Nodes must have a valid Dell OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) premium license installed.
- Supported node models are listed in the Azure Local Support Matrix.
Procedure
View HCI compliance summary
Dell OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) computes the compliance using different types of Dell HCI Configuration Profile policies that are mentioned and displays the report.
The following table provides information about each Dell policy:
| Policy name | Description |
|---|---|
| Dell Infrastructure LockDown | Checks whether the HCI cluster infrastructure is locked. |
| Dell Hardware Symmetry | Checks whether cluster nodes have validated and supported hardware components and have symmetrical hardware configurations.
For more information about checks, see Dell OpenManage Integration with Microsoft Windows Admin Center |
| Dell HCI Hardware Configuration | Checks whether cluster nodes have Dell Technologies recommended BIOS, NIC, and iDRAC configurations |
| Dell OS Configuration | Checks whether cluster nodes have Dell Technologies, and Microsoft recommended operating-system configurations
|
| Policy Summary | Displays compliance of each cluster node and its components for each policy type. For a description of each policy type, see the Details of Policy Summary sections table. |
The compliance summary is divided into several sections as described in the following table:
| Compliance summary section | Description |
|---|---|
| Overall Compliance | Displays the overall compliance of the cluster such as compliance percentage, number of policies compliant, and total number of policies from the displayed policy types |
| Overall Compliance State | Displays overall compliance of the cluster using a doughnut chart and color codes. The color codes indicate different compliance types. You can select different color codes, if any, to filter the respective policy details and its cluster nodes.
For example, when you select the red color code, policies that are not compliant and their respective cluster nodes are displayed. For a description of each color code, see the Icons shapes and color codes for Overall Compliance State options table. |
The table lists the Overall Compliance State options and provides a description of the relevant icon shape and color code for the compliant state options:
| Compliance state | Description and color code |
|---|---|
| Compliant | Displays that all cluster nodes are compliant with all Dell policies. Icon is a checkmark in a green circle. |
| Errors | Displays if any cluster machine is not compliant with Dell Hardware Symmetry policy. Icon is an exclamation mark in a red hexagon. |
| Warnings | Displays if any cluster machine is not compliant with any optional policies.
Icon is an exclamation mark in an orange triangle. |
| Unknown | Displays if any cluster machine inventory could not be retrieved when the machine is down or not reachable.
Icon is a question mark inside a gray circle. |
The following table describes each section of the Policy Summary and what it contains:
| Policy component | Description |
|---|---|
| Policy Name | Name of Dell Technologies policies |
| Description | Description of Dell Technologies policies |
| Overall Status | Displays overall status of compliance of the cluster for each policy type |
| Overall State | Displays how many policies are compliant out of the total number of policies and its percentage |
| Errors | Displays several policies that are noncompliant and must be fixed |
| Warnings | Displays several policies that are noncompliant and must be fixed |
| Unknown | Displays several unknown issues, or unable to run or fetch the data |
| Details | Displays additional information about each node and its components and their compliance status |
Onboard Dell policies to Azure Arc from Windows Admin Center to monitor HCI clusters
In the Dell OpenManage Integration extension, you can deploy the Dell HCI Configuration Profile (HCP) policies onto Azure Arc, and then use these policies in Azure Arc to monitor your Azure Stack HCI clusters. This feature is supported for single-node HCI clusters.
Before you begin
- The single-node HCI cluster must be Dell AX System for Azure Local, version 24H2.
- Dell OpenManage Integration with Microsoft Windows Admin Center (OMIMSWAC) premium license must be installed on each cluster node.
- To monitor the policies from Azure, the Internet must be available on Windows Admin Center and target nodes.
- Ensure that you have the necessary permission to create, write, or read policies into Azure. Also, you must be a member of the Gateway users role.
- Azure Stack HCI Cluster and WAC gateway must be registered on Azure and use the same account to sign in. For more information about Azure registration, see Register Windows Admin Center with Azure.
- Cluster nodes must be Arc-enabled and onboarded to Azure Arc. See Azure Arc-enabled servers. Ensure that all nodes are registered to the same resource group.
- In the cluster node, ensure that all RDMA enabled network adapters are connected to the same NIC ports as recommended by Dell Technologies. For more information, see the relevant deployment and operations guide at Technical Guides for Dell AX Solutions for Microsoft .
Procedure
Results
Secure connect gateway
Secure connect gateway (SCG) is an enterprise monitoring technology that is delivered as an appliance and a stand-alone application. It monitors your devices and proactively detects hardware issues that may occur. Depending on your service contract, it also automates support request creation for issues that are detected on the monitored devices. When a hardware issue is detected, SCG automatically collects the telemetry that is required for troubleshooting the issue. The collected telemetry helps technical support to provide a proactive and personalized support experience.
For more information about SCG, see Secure Connect Gateway - Application Edition.
References
Dell Technologies documentation
These links provide more information from Dell Technologies:
- Dell AX Solutions for Microsoft documentation
- Dell AX System for Azure Local specification sheet
- iDRAC documentation
- Azure Local Support Matrix
- For more information about manually configuring iDRAC, see PowerEdge: Support Articles for the iDRAC and the CMC.