Updated network validator section

Author: Manika Dhiman

azure-local/manage/media/use-environment-checker/network-validator-sample-failed.png

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack-hci
-ms.date: 10/29/2024
+ms.date: 12/26/2024
 ---
 
 # Evaluate the deployment readiness of your environment for Azure Local, version 23H2
@@ -406,46 +406,67 @@ To remediate the blocking issues in this output, open the Active Directory tool
 
 ### [Network](#tab/network)
 
-It is possible that the IP addresses allocated to Azure Local may already be active on the network. The network validator validates your network infrastructure for valid IP ranges reserved for deployment. It attempts to ping and connect to WinRM and SSH ports to ensure there's no active host using the IP address from the reserved IP range.
+The IP addresses allocated to Azure Local might already be in use on the network. The network validator checks your network infrastructure to ensure the IP ranges reserved for deployment are valid. It attempts to ping and connect to WinRM and SSH ports to ensure there's no active host using the IP address from the reserved IP range. It also checks storage connection, adapter driver readiness, and other host network configuration readiness.
 
-You provide the network IP range reserved for Azure Local deployment as part of the answer file JSON, which you can use during network validation. Or, you can manually provide the starting and ending IP addresses when running the validator cmdlet.
+You provide the network IP range reserved for Azure Local deployment as part of the answer file JSON, which you can use during network validation. Or, you can manually provide the individual parameters when running the validator cmdlet.
 
-### Run the network validator
-
-To run the network validator locally on the Azure Local machine node, the workstation, or the staging server with the answer file, follow these steps.
-
-1. Run one of the following cmdlets:
-
-    
-   - If using the answer file:
-   
-      ```powershell
-      Invoke-AzStackHciNetworkValidation -AnswerFile <Answerfilename>.json
-      ```
-   
-   - If entering the starting and ending IP addresses manually:
-       
-      ```powershell
-      Invoke-AzStackHciNetworkValidation -StartingAddress <StartingIPRangeAddress> -EndingAddress <EndingIPRangeAddress> 
-      ```
-
-### Network validator output
+> [!NOTE]
+> You must run the network validator on the final hardware that you want to use for the Azure local instance deployment.
 
-The following samples are the output from successful and unsuccessful runs of the network validator.
+### Run the network validator
 
-To learn more about different sections in the readiness check report, see [Understand readiness check report](#understand-readiness-check-report).
+To run the network validator locally on the Azure Local node with the answer file, use the following commands:
 
-**Sample output: Successful test**
+```powershell
+$allServers = "<ARRAY OF SERVERS' IP>" # you need to use IP for the connection 
+$userName = "<LOCALADMIN>" 
+$secPassWord = ConvertTo-SecureString "<LOCALADMINPASSWORD>" -AsPlainText -Force 
+$hostCred = New-Object System.Management.Automation.PSCredential($userName, $secPassWord) 
+[System.Management.Automation.Runspaces.PSSession[]] $allServerSessions = @() 
+foreach ($currentServer in $allServers) { 
+   $currentSession = Microsoft.PowerShell.Core\New-PSSession -ComputerName $currentServer -Credential $hostCred -ErrorAction Stop 
+   $allServerSessions += $currentSession 
+} 
+$answerFilePath = "<ANSWERFILELOCATION>" # Like C:\MASLogs\Unattended-2024-07-18-20-44-48.json 
+Invoke-AzStackHciNetworkValidation -DeployAnswerFile $answerFilePath -PSSession $allServerSessions -ProxyEnabled $false 
+```
 
-The following sample is the output from a successful run of the network validator. The output indicates no active host is using an IP address from the reserved IP range.
+To run the network validator locally on the Azure Local node using individual parameters, use the following commands:
 
-   :::image type="content" source="./media/use-environment-checker/network-validator-sample-passed.png" alt-text="Screenshot of a passed report after running the network validator." lightbox="./media/use-environment-checker/network-validator-sample-passed.png":::
+```powershell
+$answerFilePath = "<ANSWERFILELOCATION>" 
+$managementSubnetCIDR = "<CIDR string for management subnet>" 
+$logOutputPath = "<LOGFILELOCATION>" 
+$userName = "<LOCALADMIN>" 
+$secPassWord = ConvertTo-SecureString "<LOCALADMINPASSWORD>" -AsPlainText -Force 
+$sessionCredential = New-Object System.Management.Automation.PSCredential($userName, $secPassWord) 
+$answerFileContent = Get-Content $answerFilePath -Raw | ConvertFrom-Json 
+$ipPools = New-Object System.Collections.ArrayList 
+[System.Management.Automation.Runspaces.PSSession[]] $allServerSessions = @() 
+foreach ($ipPool in $answerFileContent.scaleUnits[0].deploymentData.infrastructureNetwork[0].ipPools) { 
+   $currentPoolObject = [PSCustomObject] @{ 
+     StartingAddress = $ipPool.StartingAddress 
+     EndingAddress = $ipPool.EndingAddress 
+   } 
+   $ipPools.Add($currentPoolObject) 
+} 
+[PSObject[]] $atcHostIntentsInfo = $answerFileContent.scaleUnits[0].deploymentData.hostNetwork.intents 
+[System.String[]] $allServers = $answerFileContent.scaleUnits[0].deploymentData.physicalNodes.Name 
+[System.Management.Automation.Runspaces.PSSession[]] $allServerSessions = @() 
+foreach ($currentServer in $allServers) { 
+   $currentSession = Microsoft.PowerShell.Core\New-PSSession -ComputerName $currentServer -Credential $sessionCredential -ErrorAction Stop 
+   $allServerSessions += $currentSession 
+} 
+Invoke-AzStackHciNetworkValidation -IpPools $ipPools -ManagementSubnetValue $managementSubnetCIDR -PSSession $allServerSessions -SessionCredential $sessionCredential -OutputPath $logOutputPath -AtcHostIntents $atcHostIntentsInfo 
+```
+  
+### Network validator sample output
 
-**Sample output: Failed test**
+Here's a sample output of an unsuccessful run of the network validator. The failure occurs because the network adapter has two IP addresses, when it should have only one.  
 
-The following sample is the output from a failed run of the network validator. This output shows two active hosts are using IP address from the reserved IP range.
+:::image type="content" source="./media/use-environment-checker/network-validator-sample-failed.png" alt-text="Screenshot of a failed report after running the network validator." lightbox="./media/use-environment-checker/network-validator-sample-failed.png":::
 
-   :::image type="content" source="./media/use-environment-checker/network-validator-sample-failed.png" alt-text="Screenshot of a failed report after running the network validator." lightbox="./media/use-environment-checker/network-validator-sample-failed.png":::
+To learn more about different sections in the readiness check report, see [Understand readiness check report](#understand-readiness-check-report).
 
 ### [Arc integration](#tab/arc-integration)