Add new TSG for network infra connection validator failure due to exception#250
Add new TSG for network infra connection validator failure due to exception#250fangfei wants to merge 1 commit intoAzure:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request adds a new troubleshooting guide (TSG) for handling exceptions that occur during network infrastructure connection validation in Azure Local deployments. The document provides guidance for diagnosing and resolving unexpected errors in the Test-NwkInfraConnectionValidator_InfraIpPoolConnection validator.
Changes:
- Added new TSG document for exception handling during infrastructure IP pool connection validation
- Updated the Networking README.md table of contents to include the new troubleshooting guide
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| TSG/EnvironmentValidator/Networking/Troubleshoot-Network-Test-Infra-IP-Connection-ExceptionFound.md | New TSG document providing comprehensive troubleshooting steps for the AzureLocal_NetworkInfraConnection_Test_Infra_IP_Connection_ExceptionFound validator, including exception analysis, system prerequisites checks, and Hyper-V reinstallation guidance |
| TSG/EnvironmentValidator/Networking/README.md | Updated table of contents to add a link to the new Infrastructure IP Connection Exception Found troubleshooting guide |
| ```powershell | ||
| Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V | ||
| # reboot machine | ||
| Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V | ||
| # reboot machine again | ||
| ``` |
There was a problem hiding this comment.
The PowerShell commands to disable and enable Hyper-V will cause system reboots and could disrupt workloads. According to the PowerShell code guidelines, commands that change environment state should include clear warnings about disruptions. Consider adding a warning callout before this code block to alert users that these commands will require reboots and may impact running workloads or VMs.
| ``` | ||
|
|
||
| ##### 4. Re-install Hyper-V | ||
| If the exception is complaining something like below: |
There was a problem hiding this comment.
Grammatical issue: "If the exception is complaining something like below" should be "If the exception message looks like the following" or "If the exception complains about something like below".
| If the exception is complaining something like below: | |
| If the exception message looks like the following: |
|
|
||
| ### When This Validator is Skipped | ||
|
|
||
| The infrastructure IP connectivity validator (including all endpoint tests) is **skipped** when **ArcGateway enabled**. ArcGateway provides alternative connectivity. |
There was a problem hiding this comment.
Grammatical issue: "when ArcGateway enabled" should be "when ArcGateway is enabled".
| The infrastructure IP connectivity validator (including all endpoint tests) is **skipped** when **ArcGateway enabled**. ArcGateway provides alternative connectivity. | |
| The infrastructure IP connectivity validator (including all endpoint tests) is **skipped** when **ArcGateway is enabled**. ArcGateway provides alternative connectivity. |
| </tr> | ||
| <tr> | ||
| <th style="text-align:left; width: 180px;">Severity</th> | ||
| <td><strong>Critical</strong></td> |
There was a problem hiding this comment.
The Severity field should include an explanation after "Critical". Based on the template and other TSG documents in this directory (e.g., Troubleshoot-Network-Test-InfraIP-Hyper-V-Readiness.md, Troubleshoot-Network-Test-InfraIP-vNIC-Readiness.md), the format should be: "Critical: This validator will block operations until remediated."
Add new TSG for network infra connection validator failure due to exception.
During execution of validator "Test-NwkInfraConnectionValidator_InfraIpPoolConnection", if the validator failed with "AzureLocal_NetworkInfraConnection_Test_Infra_IP_Connection_ExceptionFound", it might means that something wrong with the system itself. So will need to ask the end user to fix the problems and retry validator.