Merge pull request #17190 from MicrosoftDocs/main

2/25/2025 PM Publish

Author: Taojunshen

AKS-Arc/aks-edge-howto-multi-nic.md

@@ -4,7 +4,7 @@ description: Learn how to attach multiple network interfaces to an AKS Edge Esse
 author: sethmanheim
 ms.author: sethm
 ms.topic: how-to
-ms.date: 07/12/2024
+ms.date: 02/25/2025
 ms.custom: template-how-to, linux-related-content
 ---
 
@@ -61,19 +61,11 @@ To deploy a Linux node with multiple NICs, you must add your secondary interface
 
 ## Verify multiple NIC network configuration settings
 
-After you successfully install and deploy the AKS Edge Essentials node, follow these steps to make sure both primary, and secondary interfaces were created and added to the Linux node:
+After you successfully install and deploy the AKS Edge Essentials node, follow these steps to make sure both the primary and secondary interfaces were created and added to the Linux node. To check the interfaces, run the following command:
 
-1. Check the primary interface:
-
-   ```powershell
-   Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "sudo ip addr eth0"
-   ```
-
-1. Check the secondary network interface. If you added more than one extra interface, it appears as **ethX** with **X** being the number of extra network interfaces:
-
-   ```powershell
-   Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "sudo ip addr eth1"
-   ```
+```powershell
+Invoke-AksEdgeNodeCommand -NodeType "Linux" -command "sudo ip addr"
+```
 
 ## Configure Multus CNI plugin
 

azure-stack/operator/operator-access-workstation.md

@@ -66,7 +66,7 @@ param(
     [string]
     $DownloadedOAWZipFilePath
 )
-$expectedHash = '4B5CE0EA6FA12C4A95EBDE4223BEED5B9D98D7D9FC7DA1D5C72D3620725E5119'
+$expectedHash = 'F5172B3A97248826C73A3D7ABC0440CFA1EC3B31CAC6A1BC1100B9E241099780'
 $actualHash = (Get-FileHash -Path $DownloadedOAWZipFilePath).Hash
 Write-Host "Expected hash: $expectedHash"
 if ($expectedHash -eq $actualHash)
@@ -90,7 +90,7 @@ Another way to copy this script to your environment is to use the Test-FileHash
 2. After you import the Test-FileHash module, verify the hash of the OAW.zip file:
 
    ```powershell
-   Test-FileHash -ExpectedHash "4B5CE0EA6FA12C4A95EBDE4223BEED5B9D98D7D9FC7DA1D5C72D3620725E5119" -FilePath "<path to the OAW.zip file>"
+   Test-FileHash -ExpectedHash "F5172B3A97248826C73A3D7ABC0440CFA1EC3B31CAC6A1BC1100B9E241099780" -FilePath "<path to the OAW.zip file>"
    ```
 
 ## Check HLH version