[action] [PR:17907] Change tcp port range to support telemetry and gnmi #17923
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
A common cause of failure for the telemetry and gnmi server is port conflict. If other processes are using tcp ports 50051 and 50052, the server cannot start.
Work item tracking
How I did it
Change local port range in sysctl, new port range is from 32768 to 50001.
And then service ports for telemetry and gnmi will not be used by automatic port assignments.
https://www.kernel.org/doc/html/latest/networking/ip-sysctl.html
How to verify it
Stop telemetry and gnmi service, and create new tcp connections, and they will not use 50051 and 50052.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)