| title | description | services | author | ms.service | ms.subservice | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|
Microsoft Azure Stack Edge Pro R system requirements| Microsoft Docs |
Learn about the software and networking requirements for your Azure Stack Edge Pro R |
databox |
alkohli |
databox |
edge |
conceptual |
06/26/2024 |
alkohli |
This article describes the important system requirements for your Azure Stack Edge Pro R solution and for the clients connecting to Azure Stack Edge Pro R. We recommend that you review the information carefully before you deploy your Azure Stack Edge Pro R. You can refer back to this information as necessary during the deployment and subsequent operation.
The system requirements for the Azure Stack Edge Pro R include:
- Software requirements for hosts - describes the supported platforms, browsers for the local configuration UI, SMB clients, and any additional requirements for the clients that access the device.
- Networking requirements for the device - provides information about any networking requirements for the operation of the physical device.
[!INCLUDE Supported OS for clients connected to device]
[!INCLUDE Supported protocols for clients accessing device]
[!INCLUDE Supported storage accounts]
When managed from Azure Stack, the following tiered storage accounts are supported with SMB/NFS/REST interfaces.
| Type | Storage account | Comments |
|---|---|---|
| Standard | GPv1: Block Blob | |
| Blob storage: Block Blob | Supported only for NAS |
*Page blobs and Azure Files are currently not supported in Azure Stack. **Hot and cold tier do not exist in Azure Stack. Use the Azure PowerShell to move the data to the archive tier once the data is uploaded. For step-by-step instructions, go to Use Azure PowerShell to set the blob tier
[!INCLUDE Supported storage types]
[!INCLUDE Supported browsers for local web UI]
The following table lists the ports that need to be opened in your firewall to allow for SMB, cloud, or management traffic. In this table, in or inbound refers to the direction from which incoming client requests access to your device. Out or outbound refers to the direction in which your Azure Stack Edge Pro R device sends data externally, beyond the deployment, for example, outbound to the internet.
[!INCLUDE Port configuration for device]
Azure IoT Edge allows outbound communication from an on-premises Edge device to Azure cloud using supported IoT Hub protocols. Inbound communication is only required for specific scenarios where Azure IoT Hub needs to push down messages to the Azure IoT Edge device (for example, Cloud To Device messaging).
Use the following table for port configuration for the servers hosting Azure IoT Edge runtime:
| Port no. | In or out | Port scope | Required | Guidance |
|---|---|---|---|---|
| TCP 443 (HTTPS) | Out | WAN | Yes | Outbound open for IoT Edge provisioning. This configuration is required when using manual scripts or Azure IoT Device Provisioning Service (DPS). |
For complete information, go to Firewall and port configuration rules for IoT Edge deployment.
Network administrators can often configure advanced firewall rules based on the URL patterns to filter the inbound and the outbound traffic. Your Azure Stack Edge Pro R device and the service depend on other Microsoft applications such as Azure Service Bus, Microsoft Entra Access Control, storage accounts, and Microsoft Update servers. The URL patterns associated with these applications can be used to configure firewall rules. It is important to understand that the URL patterns associated with these applications can change. These changes require the network administrator to monitor and update firewall rules for your Azure Stack Edge Pro R as and when needed.
We recommend that you set your firewall rules for outbound traffic, based on Azure Stack Edge Pro R fixed IP addresses, liberally in most cases. However, you can use the information below to set advanced firewall rules that are needed to create secure environments.
Note
- The device (source) IPs should always be set to all the cloud-enabled network interfaces.
- The destination IPs should be set to Azure datacenter IP ranges.
[!INCLUDE URL patterns for firewall]
| URL pattern | Component or functionality |
|---|---|
| https://mcr.microsoft.com https://*.cdn.mscr.io |
Microsoft container registry (required) |
| https://*.azurecr.io | Personal and third-party container registries (optional) |
| https://*.azure-devices.net | IoT Hub access (required) |
[!INCLUDE Azure Government URL patterns for firewall]
| URL pattern | Component or functionality |
|---|---|
| https://mcr.microsoft.com https://*.cdn.mscr.com |
Microsoft container registry (required) |
| https://*.azure-devices.us | IoT Hub access (required) |
| https://*.azurecr.us | Personal and third-party container registries (optional) |
| https://*.docker.com | StorageClass (required) |
[!INCLUDE Internet bandwidth]
Use your experience while developing and testing your solution to ensure there is enough capacity on your Azure Stack Edge Pro R device and you get the optimal performance from your device.
Factors you should consider include:
-
Container specifics - Think about the following.
- How many containers are in your workload? You could have a lot of lightweight containers versus a few resource-intensive ones.
- What are the resources allocated to these containers versus what are the resources they are consuming?
- How many layers do your containers share?
- Are there unused containers? A stopped container still takes up disk space.
- In which language are your containers written?
-
Size of the data processed - How much data will your containers be processing? Will this data consume disk space or the data will be processed in the memory?
-
Expected performance - What are the desired performance characteristics of your solution?
To understand and refine the performance of your solution, you could use:
- The compute metrics available in the Azure portal. Go to your Azure Stack Edge Pro R resource and then go to Monitoring > Metrics. Look at the Edge compute - Memory usage and Edge compute - Percentage CPU to understand the available resources and how are the resources getting consumed.
- The Monitoring commands available via the PowerShell interface of the device.
Finally, make sure that you validate your solution on your dataset and quantify the performance on Azure Stack Edge Pro R before deploying in production.