Merge pull request #173069 from alkohli/3-2109

2110 release notes (Merge to release branch ASAP)

Author: Court72

articles/databox-online/TOC.yml

@@ -184,7 +184,7 @@
       - name: Troubleshoot certificate errors
         href: azure-stack-edge-gpu-certificate-troubleshooting.md 
 
-    - name: Virtual machines
+    - name: Virtual machines (Preview)
       items:
       - name: What are VMs?
         href: azure-stack-edge-gpu-virtual-machine-overview.md
@@ -299,7 +299,7 @@
             href: azure-stack-edge-gpu-deploy-iot-edge-gpu-sharing.md  
           - name: Develop C# module
             href: azure-stack-edge-gpu-create-iot-edge-module.md 
-        - name: Via Azure Arc (Preview)
+        - name: Via Azure Arc
           items:
           - name: Enable Arc on Kubernetes cluster
             href: azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md 
@@ -416,7 +416,9 @@
         href: azure-stack-edge-contact-microsoft-support.md 
   - name: Shared release notes
     items:
-    - name: 2106 - Current
+    - name: 2110 - Current
+      href: azure-stack-edge-gpu-2110-release-notes.md
+    - name: 2106
       href: azure-stack-edge-gpu-2106-release-notes.md
     - name: 2105 
       href: azure-stack-edge-gpu-2105-release-notes.md

articles/databox-online/azure-stack-edge-gpu-2110-release-notes.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 06/01/2021
+ms.date: 10/01/2021
 ms.author: alkohli
 ---
 
@@ -123,7 +123,7 @@ The certificate files that you get from your certificate authority (CA) must be
 
 - To import the certificates, follow the steps in [Import certificates on the clients accessing your Azure Stack Edge Pro device](azure-stack-edge-gpu-manage-certificates.md#import-certificates-on-the-client-accessing-the-device).
 
-- To export the certificates, follow the steps in [Export certificates from the client accessing the Azure Stack Edge Pro device](azure-stack-edge-gpu-manage-certificates.md#import-certificates-on-the-client-accessing-the-device).
+- To export the certificates, follow the steps in [Export certificates from the client accessing the Azure Stack Edge Pro device](azure-stack-edge-gpu-prepare-certificates-device-upload.md#export-certificates-as-pfx-format-with-private-key).
 
 
 ## Validate certificates

articles/databox-online/azure-stack-edge-gpu-create-certificates-tool.md

@@ -7,11 +7,11 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: conceptual
-ms.date: 07/30/2021
+ms.date: 10/01/2021
 ms.author: alkohli
 ---
 
-# Data residency and resiliency for Azure Stack Edge (Preview)
+# Data residency and resiliency for Azure Stack Edge 
 
 [!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
 

articles/databox-online/azure-stack-edge-gpu-data-residency.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 09/27/2021
+ms.date: 10/26/2021
 ms.author: alkohli
 ---
 # Update your Azure Stack Edge Pro GPU 
@@ -22,15 +22,15 @@ The procedure described in this article was performed using a different version
 
 The current update is Update 2110. This update installs two updates, the device update followed by Kubernetes updates. The associated versions for this update are:
 
-- Device software version - **2.2.1726.3923**
+- Device software version - **2.2.1758.4034**
 - Kubernetes server version - **v1.20.9**
 - IoT Edge version: **0.1.0-beta15**
 - GPU driver version: **460.32.03**
 - CUDA version: **11.2**
 
-For information on what's new in this update, go to [Release notes](azure-stack-edge-placeholder.md).
+For information on what's new in this update, go to [Release notes](azure-stack-edge-gpu-2110-release-notes.md).
 
-To apply 2110 update, your device must be running 2106. 
+**To apply 2110 update, your device must be running 2106.** 
 
 - If you are not running the minimal supported version, you'll see this error: *Update package cannot be installed as its dependencies are not met*. 
 - You can update to 2106 from an older version and then install 2110.
@@ -176,7 +176,7 @@ Do the following steps to download the update from the Microsoft Update Catalog.
 
 2. In the search box of the Microsoft Update Catalog, enter the Knowledge Base (KB) number of the hotfix or terms for the update you want to download. For example, enter **Azure Stack Edge**, and then click **Search**.
 
-    The update listing appears as **Azure Stack Edge Update 2105**.
+    The update listing appears as **Azure Stack Edge Update 2110**.
 
     <!--![Search catalog 2](./media/azure-stack-edge-gpu-install-update/download-update-2-b.png)-->
 
@@ -201,32 +201,33 @@ This procedure takes around 20 minutes to complete. Perform the following steps
 
    ![update device 3](./media/azure-stack-edge-gpu-install-update/local-ui-update-3-a.png)
 
-3. Select **Apply**.
+3. Select **Apply update**.
 
-   ![update device 4](./media/azure-stack-edge-gpu-install-update/local-ui-update-4.png)
+   <!--![update device 4](./media/azure-stack-edge-gpu-install-update/local-ui-update-4.png)-->
 
 4. When prompted for confirmation, select **Yes** to proceed. Given the device is a single node device, after the update is applied, the device restarts and there is downtime. 
 
    ![update device 5](./media/azure-stack-edge-gpu-install-update/local-ui-update-5.png)
 
 5. The update starts. After the device is successfully updated, it restarts. The local UI is not accessible in this duration.
 
-6. After the restart is complete, you are taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2105**. 
+6. After the restart is complete, you are taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2110**. 
 
-   <!--![update device 6](./media/azure-stack-edge-gpu-install-update/local-ui-update-6.png)-->
 
 7. You will now update the Kubernetes software version. Repeat the above steps. Provide a path to the Kubernetes update file with the *Kubernetes_Package.exe* suffix.  
 
    <!--![update device](./media/azure-stack-edge-gpu-install-update/local-ui-update-7.png)-->
 
 8. Select **Apply Update**.
 
-   ![update device 7](./media/azure-stack-edge-gpu-install-update/local-ui-update-8.png)
+   <!--![update device 7](./media/azure-stack-edge-gpu-install-update/local-ui-update-8.png)-->
 
 9. When prompted for confirmation, select **Yes** to proceed.
 
 10. After the Kubernetes update is successfully installed, there is no change to the displayed software in **Maintenance** > **Software update**.
 
+    ![update device 6](./media/azure-stack-edge-gpu-install-update/portal-update-16.png)
+
 
 ## Next steps
 

articles/databox-online/azure-stack-edge-gpu-install-update.md

@@ -81,6 +81,17 @@ Use the following table for port configuration for the servers hosting Azure IoT
 
 For complete information, go to [Firewall and port configuration rules for IoT Edge deployment](../iot-edge/troubleshoot.md).
 
+
+### Port requirements for Kubernetes on Azure Stack Edge
+
+| Port no. | In or out | Port scope | Required | Guidance |
+|----------|-----------|------------|----------|----------|
+| TCP 31000 (HTTPS)| In       | LAN        | In some cases. <br> See notes.      |This port is required only if you are connecting to the Kubernetes dashboard to monitor your device. |
+| TCP 6443 (HTTPS)| In       | LAN        | In some cases. <br> See notes.       |This port is required by Kubernetes API server only if you are using `kubectl` to access your device. |
+
+> [!IMPORTANT]
+> If your datacenter firewall is restricting or filtering traffic based on source IPs or MAC addresses, make sure that the compute IPs (Kubernetes node IPs) and MAC addresses are in the allowed list. The MAC addresses can be specified by running the `Set-HcsMacAddressPool` cmdlet on the PowerShell interface of the device.
+
 ## URL patterns for firewall rules
 
 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 device and the service depend on other Microsoft applications such as Azure Service Bus, Azure Active Directory 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 as and when needed.