Extending explanation about port exclusions#7927
Extending explanation about port exclusions#7927DBAlberto wants to merge 6 commits intoMicrosoftDocs:livefrom
Conversation
Extending explanation about port exclusions, adding how to verify if this is configured, how to avoid one common error during exclusion configuration, and one scenario when another process is using the same port defined as probe port in the IP cluster resource in the AG role. It is added reference to “cluster core IP resource” since there is a reference using port 58888 on: sql-docs/azure-sql/includes/virtual-machines-ag-listener-configure.md
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Docs Build status updates of commit bc6743b:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md | Details |
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md
- Line 77, Column 8: [Warning: file-not-found - See documentation]
Invalid file link: 'win32/desktop-src/WinSock/windows-sockets-error-codes-2.md'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
|
@adbadram - Can you review this PR? IMPORTANT: When this content is ready to merge, you must add #label:"aq-pr-triaged" |
bluefooted
left a comment
There was a problem hiding this comment.
Thanks @DBAlberto ! Made some suggestions to make it a bit clearer.
Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Docs Build status updates of commit ab3f466:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md | Details |
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md
- Line 73, Column 8: [Warning: file-not-found - See documentation]
Invalid file link: 'win32/desktop-src/WinSock/windows-sockets-error-codes-2.md'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
|
Docs Build status updates of commit 0c82143:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md | Details |
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md
- Line 73, Column 8: [Warning: file-not-found - See documentation]
Invalid file link: 'win32/desktop-src/WinSock/windows-sockets-error-codes-2.md'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
Fixing broken link for Windows Sockets Error Code 10048 reference
|
@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit b7d3782: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
extending explanation about port exclusions when SQL server or cluster core resources are using ports from dynamic pool range This replaces MicrosoftDocs#7927 due to this is too much content for the checklist.
Extending explanation about port exclusions, adding how to verify if this is configured, how to avoid one common error during exclusion configuration, and one scenario when another process is using the same port defined as probe port in the IP cluster resource in the AG role.
It is added reference to “cluster core IP resource” since there is a reference using port 58888 on:
sql-docs/azure-sql/includes/virtual-machines-ag-listener-configure.md