Change tcp port range to support telemetry and gnmi #17907
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ganglyu
requested review from
qiluo-msft,
liuh-80 and
zbud-msft
and removed request for
lguohan
liuh-80
reviewed
Jan 26, 2024
| @@ -15,6 +15,7 @@ net.ipv4.conf.all.arp_announce=1 | |||
| net.ipv4.conf.all.arp_filter=0 | |||
| net.ipv4.conf.all.arp_notify=1 | |||
| net.ipv4.conf.all.arp_ignore=2 | |||
| net.ipv4.ip_local_reserved_ports=50051,50052 | |||
There was a problem hiding this comment.
Here is current SONiC auto allocate port range: 32768 60999
If any other SONiC service in this range, also need add to here.
admin@vlab-01:$ sudo sysctl -a | grep ip_local_$
net.ipv4.ip_local_port_range = 32768 60999
net.ipv4.ip_local_reserved_ports =
admin@vlab-01:
liuh-80
approved these changes
Jan 26, 2024
liuh-80
approved these changes
Jan 26, 2024
ganglyu
changed the title
zbud-msft
approved these changes
Jan 26, 2024
qiluo-msft
approved these changes
Jan 26, 2024
mssonicbld
pushed a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jan 26, 2024
* Reserve tcp port for telemetry and gnmi * Use ip_local_port_range instead * Fix sysctl config
|
Cherry-pick PR to 202311: #17916 |
mssonicbld
pushed a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jan 29, 2024
* Reserve tcp port for telemetry and gnmi * Use ip_local_port_range instead * Fix sysctl config
|
Cherry-pick PR to 202305: #17923 |
11 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Jan 29, 2024
* Reserve tcp port for telemetry and gnmi * Use ip_local_port_range instead * Fix sysctl config
mssonicbld
added
Included in 202305 Branch
and removed
Created PR to 202305 Branch
labels
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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)