Merge pull request #225351 from b-branco/ase-vm-sizing

ASE VM sizing + fixes

Author: v-dirichards

articles/private-5g-core/azure-stack-edge-virtual-machine-sizing.md

@@ -0,0 +1,19 @@
+---
+title: Azure Stack Edge virtual machine sizing
+description: Learn about the VMs that Azure Private 5G Core uses when running on an Azure Stack Edge device.
+author: b-branco
+ms.author: biancabranco
+ms.service: private-5g-core
+ms.topic: reference
+ms.date: 01/27/2023
+---
+
+# Azure Stack Edge virtual machine sizing
+
+The following table contains information about the VMs that Azure Private 5G Core (AP5GC) uses when running on an Azure Stack Edge (ASE) device. You can use this information, for example, to check how much space you'll have remaining on your ASE device after installing Azure Private 5G Core.
+
+| VM detail | Flavor name | vCPUs | Memory (GB) | Disk size | VM function |
+|---|---|---|---|---|---|
+| Management Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 80 GB | Management Control Plane to create Kubernetes clusters |
+| AP5GC Cluster Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 128 GB | Master Node of the Kubernetes cluster used for AP5GC |
+| AP5GC Cluster Worker Node VM | Standard_F16s_HPN | 16 | 32 | Ephemeral - 128 GB <br>Persistent - 102 GB | Worker node - AP5GC workload |

articles/private-5g-core/collect-required-information-for-a-site.md

@@ -68,7 +68,7 @@ For each data network that you want to configure, collect all the values in the
    | The network address of the subnet from which dynamic IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You won't need this address if you don't want to support dynamic IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`192.0.2.0/24` </br></br>Note that the UE subnets aren't related to the access subnet.    |**Dynamic UE IP pool prefixes**|
    | The network address of the subnet from which static IP addresses must be allocated to user equipment (UEs), given in CIDR notation. You won't need this address if you don't want to support static IP address allocation for this site. You identified this in [Allocate user equipment (UE) IP address pools](complete-private-mobile-network-prerequisites.md#allocate-user-equipment-ue-ip-address-pools). The following example shows the network address format. </br></br>`203.0.113.0/24` </br></br>Note that the UE subnets aren't related to the access subnet.    |**Static UE IP pool prefixes**|
    | The Domain Name System (DNS) server addresses to be provided to the UEs connected to this data network. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses). </br></br>This value may be an empty list if you don't want to configure a DNS server for the data network. In this case, UEs in this data network will be unable to resolve domain names. | **DNS Addresses** |
-   |Whether Network Address and Port Translation (NAPT) should be enabled for this data network. NAPT allows you to translate a large pool of private IP addresses for UEs to a small number of public IP addresses. The translation is performed at the point where traffic enters the data network, maximizing the utility of a limited supply of public IP addresses.</br></br>If you want to use [UE-to-UE traffic](private-5g-core-overview.md#ue-to-ue-traffic) in this data network, keep NAPT disabled.  |**NAPT**|
+   |Whether Network Address and Port Translation (NAPT) should be enabled for this data network. NAPT allows you to translate a large pool of private IP addresses for UEs to a small number of public IP addresses. The translation is performed at the point where traffic enters the data network, maximizing the utility of a limited supply of public IP addresses. </br></br>When NAPT is disabled, static routes to the UE IP pools via the appropriate user plane data IP address for the corresponding attached data network must be configured in the data network router. </br></br>If you want to use [UE-to-UE traffic](private-5g-core-overview.md#ue-to-ue-traffic) in this data network, keep NAPT disabled.   |**NAPT**|
 
 ## Collect values for diagnostics package gathering
 

articles/private-5g-core/create-a-site.md

@@ -60,6 +60,7 @@ In this step, you'll create the mobile network site resource representing the ph
 1. In the **Attached data networks** section, select **Attach data network**. Choose whether you want to use an existing data network or create a new one, then use the information you collected in [Collect data network values](collect-required-information-for-a-site.md#collect-data-network-values) to fill out the fields. Note the following:
     - **ASE N6 virtual subnet** (if this site will support 5G UEs) or **ASE SGi virtual subnet** (if this site will support 4G UEs) must match the corresponding virtual network name on port 6 on your Azure Stack Edge Pro device.
     - If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.
+    - If you decided to keep NAPT disabled, ensure you configure your data network router with static routes to the UE IP pools via the appropriate user plane data IP address for the corresponding attached data network.
 
     :::image type="content" source="media/create-a-site/create-site-attach-data-network.png" alt-text="Screenshot of the Azure portal showing the Attach data network screen.":::
 

articles/private-5g-core/index.yml

@@ -142,3 +142,12 @@ landingContent:
           - text: Gather diagnostics
             url: gather-diagnostics.md
 
+  # Card
+  - title: Learn about Azure Private 5G Core architecture
+    linkLists:
+      - linkListType: architecture
+        links:
+          - text: Deploy private 5G networks on Azure
+            url: /azure/architecture/industries/telecommunications/deploy-private-mobile-network
+          - text: Build a private 5G network
+            url: /azure/architecture/industries/telecommunications/build-private-5g-network

articles/private-5g-core/toc.yml

@@ -142,6 +142,8 @@ items:
      href: /rest/api/mobilenetwork
    - name: Region code names
      href: region-code-names.md
+   - name: ASE VM sizing
+     href: azure-stack-edge-virtual-machine-sizing.md
 - name: Resources
   items:
   - name: Azure Private 5G Core product page