Skip to content

Extending explanation about port exclusions#7927

Closed
DBAlberto wants to merge 6 commits intoMicrosoftDocs:livefrom
DBAlberto:patch-11
Closed

Extending explanation about port exclusions#7927
DBAlberto wants to merge 6 commits intoMicrosoftDocs:livefrom
DBAlberto:patch-11

Conversation

@DBAlberto
Copy link
Copy Markdown
Contributor

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

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
@PRMerger8
Copy link
Copy Markdown
Contributor

@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@opbld31
Copy link
Copy Markdown

opbld31 commented Aug 10, 2022

Docs Build status updates of commit bc6743b:

⚠️ Validation status: warnings

File Status Preview URL Details
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md ⚠️Warning 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:

@Jak-MS
Copy link
Copy Markdown
Contributor

Jak-MS commented Aug 11, 2022

@adbadram - Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@PRMerger13 PRMerger13 added the aq-pr-triaged tracking label for the PR review team label Aug 11, 2022
Copy link
Copy Markdown
Contributor

@bluefooted bluefooted left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @DBAlberto ! Made some suggestions to make it a bit clearer.

Comment thread azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md Outdated
Comment thread azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md Outdated
Comment thread azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md Outdated
Comment thread azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md Outdated
Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>
@prmerger-automator
Copy link
Copy Markdown
Contributor

@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>
@prmerger-automator
Copy link
Copy Markdown
Contributor

@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>
@prmerger-automator
Copy link
Copy Markdown
Contributor

@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>
@prmerger-automator
Copy link
Copy Markdown
Contributor

@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@opbld32
Copy link
Copy Markdown

opbld32 commented Sep 22, 2022

Docs Build status updates of commit ab3f466:

⚠️ Validation status: warnings

File Status Preview URL Details
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md ⚠️Warning 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:

@opbld31
Copy link
Copy Markdown

opbld31 commented Sep 22, 2022

Docs Build status updates of commit 0c82143:

⚠️ Validation status: warnings

File Status Preview URL Details
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md ⚠️Warning 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:

Fixing broken link for Windows Sockets Error Code 10048 reference
@prmerger-automator
Copy link
Copy Markdown
Contributor

@DBAlberto : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@opbld31
Copy link
Copy Markdown

opbld31 commented Sep 29, 2022

Learn Build status updates of commit b7d3782:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/virtual-machines/windows/hadr-cluster-best-practices.md ✅Succeeded

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:

DBAlberto added a commit to DBAlberto/sql-docs that referenced this pull request Oct 3, 2022
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.
@DBAlberto DBAlberto closed this Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants