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/upgrade-packet-core-arm-template.md
+8-22Lines changed: 8 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,35 +125,21 @@ Once the upgrade completes, check if your deployment is operating normally.
125
125
126
126
If you encountered issues after the upgrade, you can roll back the packet core instance to the previous version.
127
127
128
+
In this step, you'll roll back your packet core using a REST API request. Follow [Rollback - Azure portal](upgrade-packet-core-azure-portal.md#rollback) if you want to roll back using the Azure portal instead.
129
+
128
130
If any of the configuration you set while your packet core instance was running a newer version isn't supported in the version that you want to roll back to, you'll need to revert to the previous configuration before you're able to perform a rollback. Check the packet core release notes for information on when new features were introduced.
129
131
130
132
> [!NOTE]
131
133
> You can roll back your packet core instance to version [PMN-2211-0](azure-private-5g-core-release-notes-2211.md) or later.
132
134
133
135
1. Ensure you have a backup of your deployment information. If you need to back up again, follow [Back up deployment information](#back-up-deployment-information).
134
-
1. TODO
135
-
<!--
136
-
1. Select the following link to sign in to Azure and open the template.
137
-
138
-
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.mobilenetwork%2Fmobilenetwork-update-packet-core-control-plane%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.mobilenetwork%2Fmobilenetwork-update-packet-core-control-plane%2FcreateUiDefinition.json)
139
-
140
-
1. Select or enter the following values, using the information you retrieved in [Prerequisites](#prerequisites).
141
-
142
-
- **Subscription:** select the Azure subscription you used to create your private mobile network.
143
-
- **Resource group:** select the resource group containing the mobile network resource representing your private mobile network.
144
-
- **Region:** select **East US**.
145
-
- **Existing packet core:** select the name of the packet core instance you want to upgrade.
146
-
- **New version:** enter the packet core version you want to downgrade to. This value can be version PMN-4-18-0 or later.
147
-
148
-
:::image type="content" source="media/upgrade-packet-core-arm-template/upgrade-arm-template-configuration-fields.png" alt-text="Screenshot of the Azure portal showing the configuration fields for the upgrade ARM template.":::
149
-
150
-
1. Select **Review + create**.
151
-
1. Azure will now validate the configuration values you've entered. You should see a message indicating that your values have passed validation.
152
-
153
-
If the validation fails, you'll see an error message and the **Configuration** tab(s) containing the invalid configuration will be flagged. Select the flagged tab(s) and use the error messages to correct invalid configuration before returning to the **Review + create** tab.
136
+
1. Perform a [rollback POST request](/rest/api/mobilenetwork/packet-core-control-planes/rollback?tabs=HTTP).
137
+
138
+
> [!TIP]
139
+
> For more information on how to use REST APIs, see [Azure REST API reference](/rest/api/azure/).
154
140
155
-
1. Once your configuration has been validated, select **Create** to upgrade the packet core instance. The Azure portal will display a confirmation screen when the packet core instance has been downgraded.
156
-
1. Follow the steps in [Verify upgrade](#verify-upgrade) to check if the rollback was successful.-->
141
+
1.Follow the steps in [Restore backed up deployment information](#restore-backed-up-deployment-information) to reconfigure your deployment.
142
+
1. Follow the steps in [Verify upgrade](#verify-upgrade) to check if the rollback was successful.
0 commit comments