You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/private-5g-core/commission-cluster.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,15 +154,9 @@ In the local Azure Stack Edge UI, go to the **Kubernetes (Preview)** page. You'l
154
154
1. Select **Modify** at the bottom of the panel to save the configuration.
155
155
1. Select **Apply** at the bottom of the page and wait for the settings to be applied. Applying the settings will take approximately 5 minutes.
156
156
157
-
The page should now look like the following image:
158
-
__DIFFERENT IMAGE FOR VLAN TRUNKING MODE__
157
+
The page should now look like the following image (in VLAN-trunking mode):
159
158
160
-
:::zone pivot="ase-pro-2"
161
-
:::image type="content" source="media/commission-cluster/commission-cluster-kubernetes-preview-enabled-ase-2.png" alt-text="Screenshot showing Kubernetes (Preview) with two tables. The first table is called Compute virtual switch and the second is called Virtual network. A green tick shows that the virtual networks are enabled for Kubernetes.":::
162
-
:::zone-end
163
-
:::zone pivot="ase-pro-gpu"
164
159
:::image type="content" source="media/commission-cluster/commission-cluster-kubernetes-preview-enabled.png" alt-text="Screenshot showing Kubernetes (Preview) with two tables. The first table is called Compute virtual switch and the second is called Virtual network. A green tick shows that the virtual networks are enabled for Kubernetes.":::
Copy file name to clipboardExpand all lines: articles/private-5g-core/create-a-site.md
+1-9Lines changed: 1 addition & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,11 +40,7 @@ In this step, you'll create the mobile network site resource representing the ph
40
40
41
41
:::image type="content" source="media/create-a-site/create-site-basics-tab.png" alt-text="Screenshot of the Azure portal showing the Basics configuration tab for a site resource.":::
42
42
43
-
1. You'll now see the **Packet core** configuration tab.
44
-
45
-
:::image type="content" source="media/create-a-site/create-site-packet-core-tab.png" alt-text="Screenshot of the Azure portal showing the Packet core configuration tab for a site resource."::: __REPLACE IMAGE__
46
-
47
-
1. In the **Packet core** section, set the fields as follows:
43
+
1. You'll now see the **Packet core** configuration tab. Set the fields as follows:
48
44
49
45
- Use the information you collected in [Collect packet core configuration values](collect-required-information-for-a-site.md#collect-packet-core-configuration-values) to fill out the **Technology type**, **Azure Stack Edge device**, and **Custom location** fields.
50
46
- For a Highly Available (HA) deployment, specify the ASE two node cluster as the Azure Stack Edge device.
@@ -67,8 +63,6 @@ In this step, you'll create the mobile network site resource representing the ph
67
63
- If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.
68
64
- 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.
69
65
70
-
:::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."::: __REPLACE IMAGE__
71
-
72
66
Once you've finished filling out the fields, select **Attach**.
73
67
:::zone-end
74
68
:::zone pivot="ase-pro-2"
@@ -82,8 +76,6 @@ In this step, you'll create the mobile network site resource representing the ph
82
76
- If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.
83
77
- 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.
84
78
85
-
:::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.":::
86
-
87
79
Once you've finished filling out the fields, select **Attach**.
Copy file name to clipboardExpand all lines: articles/private-5g-core/modify-packet-core.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,8 +12,6 @@ ms.custom: template-how-to
12
12
13
13
# Modify a packet core instance
14
14
15
-
__UPDATE SCREENSHOTS TO ATTACHED DATA NETWORKS FROM VLAN TRUNKING MODE__
16
-
17
15
Each Azure Private 5G Core site contains a packet core instance, which is a cloud-native implementation of the 3GPP standards-defined 5G Next Generation Core (5G NGC or 5GC). In this how-to guide, you'll learn how to modify a packet core instance using the Azure portal; this includes modifying the packet core's custom location, connected Azure Stack Edge (ASE) device, and access network configuration. You'll also learn how to add, modify and remove the data networks attached to the packet core instance.
18
16
19
17
If you want to modify a packet core instance's local access configuration, follow [Modify the local access configuration in a site](modify-local-access-configuration.md).
@@ -127,9 +125,6 @@ To configure a new or existing data network and attach it to your packet core in
127
125
:::image type="content" source="media/modify-packet-core/modify-packet-core-data-networks-attach.png" alt-text="Screenshot of the Azure portal showing the Modify packet core Data networks tab. The option to attach a data network is highlighted.":::
128
126
129
127
1. In the **Data network** field, choose an existing data network from the dropdown or select **Create new** to create a new one. 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 remaining fields.
130
-
131
-
:::image type="content" source="media/modify-packet-core/modify-packet-core-attach-data-network.png" alt-text="Screenshot of the Azure portal showing the Attach data network screen.":::
132
-
133
128
1. Select **Attach**.
134
129
1. Repeat the steps above for each additional data network you want to configure.
135
130
1. Choose the next step:
@@ -147,9 +142,6 @@ To make changes to a data network attached to your packet core instance:
147
142
:::image type="content" source="media/modify-packet-core/modify-packet-core-data-networks-modify.png" alt-text="Screenshot of the Azure portal showing the Modify packet core Data networks tab. A data network is highlighted.":::
148
143
149
144
1. 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 in the **Modify attached data network** window.
150
-
151
-
:::image type="content" source="media/modify-packet-core/modify-packet-core-modify-data-network.png" alt-text="Screenshot of the Azure portal showing the Modify attached data network screen.":::
152
-
153
145
1. Select **Modify**. You should see your changes under the **Data networks** tab.
154
146
1. Go to [Submit and verify changes](#submit-and-verify-changes).
0 commit comments