Processors must be at least 1.4 GHz and compatible with the x64 instruction set. Stretched clusters require at least two volumes: one for replicated data and one for log data. This section outlines some of the common fixes when an issue is encountered. Content excerpt: Azure Stack HCI is a hyperconverged infrastructure (HCI) cluster solution consists of windows servers (Hyper-V), Storage Spaces Direct, and Azure-inspired SDN. When you create an Azure Stack HCI cluster using Windows Admin Center, you have the option to deploy Network Controller to enable Software Defined Networking (SDN). Configuration of the LLDP Type-Length-Values (TLVs) must be dynamically enabled. The following sections provide consolidated lists of required and recommended URLs for the Azure Stack HCI core components, which include cluster creation, registration and billing, Microsoft Update, and cloud cluster witness. The following storage implementations are supported by AKS on Azure Stack HCI and Windows Server: For an Azure Stack HCI or Windows Server cluster, you've two supported storage configurations for running virtual machine workloads. Applies to: Azure Stack HCI, versions 22H2 and 21H2. These computer accounts need to be moved into their own dedicated organizational unit (OU). Before diving in, you may wonder, what is Azure Stack HCI anyway? Use the following steps to prepare the server hardware for deployment of the operating system. Static IP addresses: Azure Stack HCI requires static IP addresses for storage and workload (VM) traffic and doesn't support dynamic IP address assignment through DHCP for this high-speed network. In addition, Kubernetes uses the store for service discovery. For more information on adapter symmetry, see Switch Embedded Teaming (SET). 4. Solution: Upgrade the driver for the adapter. Consult your network administrator about the IP address you should use for each server in the cluster. Solution: We highly recommend using the Network ATC Default VLANs. To make sure your deployment is successful, review the Azure Stack HCI system requirements. Without flash storage, the lower levels of performance on HDDs may cause deployment issues and timeouts. In 21H2 and 22H2, Network HUD can help you identify misconfiguration of the physical network. To set up a proxy server for Azure Stack HCI, run the following PowerShell command as an administrator on each server in the cluster: Use the ProxySettingsPerUser 0 flag to make the proxy configuration server-wide instead of per user, which is the default. All systems that have been validated in the Azure Stack HCI catalog fall into one of the two supported storage configurations above. Management and compute adapters aren't managed by Network ATC. North-South traffic has the following characteristics: East-West traffic has the following characteristics: North-South traffic requires the use of switches. Site names: For stretched clusters, two sites are used for disaster recovery. Ensure that the following firewall rules are configured in your on-premises firewall for Failover Clustering. In this scenario the service provider would use a datacenter SPLA license "on top" of Azure Stack HCI to license all guests VMs. You must run AKS on an SSD. For more information you, Performance at etcd.io. Install the WinInetProxy module to run the commands in this section. Host-bus adapter (HBA) cards must implement simple pass-through mode for any storage devices used for Storage Spaces Direct. This could be locally via a keyboard and monitor, or using a remote management (headless or BMC) controller, or Remote Desktop.
Ensure each network adapter has an "Up" status, as verified by the PowerShell Get-NetAdapter cmdlet. See Install Windows Admin Center. For RoCE, also note the model of your top-of-rack switch. Since DCB can be used in both RoCE and iWARP RDMA scenarios, 802.1Qbb is required in all scenarios. As a coordinating component to the operation of Kubernetes and the workloads it supports, latency and throughput to etcd are critical. The first step in deploying Azure Stack HCI is to download Azure Stack HCI and install the operating system on each server that you want to cluster. This section lists industry standards that are mandatory for the specific roles of network switches used in Azure Stack HCI deployments. Systems that only have HDD-based storage aren't supported by Azure Stack HCI, and thus aren't recommended for running AKS on Azure Stack HCI and Windows Server. For additional feature-specific requirements for Hyper-V, see System requirements for Hyper-V on Windows Server. To prepare for deployment, you'll need to take note of the server names, domain names, computer account names, RDMA protocols and versions, and VLAN ID for your deployment. (Recommended) Enable dynamic DNS updates in your DNS environment to allow AKS on Azure Stack HCI and Windows Server to register the cloud agent generic cluster name in the DNS system for discovery.
azure-stack-docs/physical-network-requirements.md at main You'll need appropriate firewall rules to allow ICMP, SMB (port 445, plus port 5445 for SMB Direct if using iWARP RDMA), and WS-MAN (port 5985) bi-directional traffic between all servers in the cluster. This command creates a service principal with the Owner role and sets the scope at a subscription level. Each OS must use the EN-US region and language selections. These solutions are designed, assembled, and validated to run our reference architecture and to check compatibility and reliability so you get up and running quickly. With that created, in the Azure portal, under Subscriptions, Access Control, and then Role Assignments, you should see your new Service Principal. A minimum of three CoS priorities are required without downgrading the switch capabilities or port speed. Here are the requirements for the machine running the Windows Admin Center gateway: You'll need to connect to your Azure account. For more information about preparing for using SDN in Azure Stack HCI, see Plan a Software Defined Network infrastructure and Plan to deploy Network Controller. Visit the Azure Stack HCI solutions website for validated solutions. If you install Windows Admin Center on a server, tasks that require CredSSP, such as cluster creation and installing updates and extensions, require using an account that's a member of the Gateway Administrators group on the Windows Admin Center server. All Organizationally Specific TLVs start with an LLDP TLV Type value of 127. The physical NIC (or virtual NIC if necessary) is configured to use VLANs 711, 712, 713, and 714 respectively. To use Windows Admin Center with AKS on Azure Stack HCI and Windows Server, you must meet all the criteria in the list below. On the Which type of installation do you want? We do recommend turning on the Active Directory Recycle Bin feature as a general best practice, if you haven't already. Required to manage AKS hybrid clusters in Azure portal. For an overview of AKS on Azure Stack HCI and Windows Server, see AKS on Azure Stack HCI and Windows Server overview. AKS on Azure Stack HCI and Windows Server deployments that exceed the following specifications aren't supported: You can set up your AKS cluster in the following way, to run AKS on a single node Windows Server with limited RAM. On the Applicable notices and license terms page, review the license terms, select the I accept the license terms checkbox, and then select Next. The defaults are listed below: Network ATC establishes the following priorities and bandwidth reservations. Dec 28, 2022 Storage network capacity changes with Azure Stack HCI version 22H2 Network switch requirements with Azure Stack HCI version 22H2 Standard: IEEE 802.1Qaz Custom. Compliance and data residency can be strictly enforced with Azure Stack HCI as organizational data remains on-prem. This article discusses physical (fabric) network considerations and requirements for Azure Stack HCI, particularly for network switches.
PDF Microsoft HCI Solutions from Dell Technologies Deployment Guide Access is limited only to: This article describes how to optionally use a highly locked-down firewall configuration to block all traffic to all destinations except those included in your allowlist. The following vendors (in alphabetical order) have confirmed that their switches support Azure Stack HCI requirements: Click on a vendor tab to see validated switches for each of the Azure Stack HCI traffic types. Ensure that the following firewall rules are configured in your on-premises firewall for Storage Replica (stretched cluster). Traffic leaves the physical rack or crosses a Layer-3 boundary (IP). No switch purchase is necessary for East-West traffic. Each site must have the same number of servers and drives. There are no special domain functional-level requirements. 3. Create a service principal by running the New-AzADServicePrincipal PowerShell command. At Microsoft, our goal is to give businesses the ability to project Azure to wherever they need it, whether it be the cloud, a data center, or an edge location like a retail store. VLANs are required for several aspects of Azure Stack HCI and are required in all scenarios. On the Where do you want to install Azure Stack HCI? RFC 3046: DHCPv4 or RFC 6148: DHCPv4. If your account is assigned the User role, but the app registration setting is limited to admin users, ask your administrator either to assign you one of the administrator roles that can create and manage all aspects of app registrations, or to enable users to register apps. This data is stored within regional Microsoft-operated datacenters. To get started: Download and install the Windows ADK. Complete the installation process using the Server Configuration tool (SConfig) to prepare the server or servers for clustering. Updated: Deploying Network ATC in virtual machines may be used for test and validation purposes only. In addition, allow 4 GB of RAM per terabyte (TB) of cache drive capacity on each server for Storage Spaces Direct metadata. You should also review Azure Stack HCI URLs. The following table provides a list of required firewall URLs. Solution hardware ranges from 1 to 16 nodes and is tested and validated by Microsoft and partner vendors. The above URL list covers the minimum required URLs for you to connect your AKS on Azure Stack HCI service to Azure for billing. The following are requirements and best practices for using Network ATC in Azure Stack HCI: All servers in the cluster must be running Azure Stack HCI, version 22H2 with the November update (or later). Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. If you intend to use SDN on Azure Stack HCI: Make sure the host servers have at least 50-100 GB of free space to create the Network Controller VMs. This section lists some of the key default values used by Network ATC.