Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[action] [PR:17907] Change tcp port range to support telemetry and gnmi #17923

Merged
merged 1 commit into from
Jan 29, 2024

Conversation

mssonicbld
Copy link
Collaborator

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
  • Microsoft ADO (number only): 26538971

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)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

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)

* Reserve tcp port for telemetry and gnmi

* Use ip_local_port_range instead

* Fix sysctl config
@mssonicbld
Copy link
Collaborator Author

Original PR: #17907

@mssonicbld mssonicbld merged commit 6a76a73 into sonic-net:202305 Jan 29, 2024
18 checks passed
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.

2 participants