-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Do not pass the option "device" in rsyslog.conf by default when syslog server's source address is configured #17616
Conversation
Signed-off-by: Stephen Sun <stephens@nvidia.com>
@StormLiangMS,@liushilongbuaa PR: #17616 is conflict with MS internal repo |
/azp run ms_conflict |
No pipelines are associated with this pull request. |
/azpw ms_conflict |
hi @qiluo-msft could you have expert to take a look at this PR? And there is an internal conflict. |
/azpw ms_conflict |
Is it covered by sonic-mgmt testcases? #Closed |
I do not think so. this was found by our internal QA test. |
Could you add a test for the behavior "an in-band syslog server will not receive any syslog if it is configured without a VRF specified"? #Closed |
I'm not sure whether there is infra for such test cases. So, I need to check the details and get back to you |
@prsunny Could you help review? |
This is still applicable. We could not approve this PR if testcase is not implemented. In reply to: 1890853775 |
Test plan ready for review sonic-net/sonic-mgmt#11803 |
ADO 27353460 |
hi @stephenxs @wen587 pls have test with 202305 on brcm/mellanox/cisco/marvell platform, would like to avoid regression. |
@StormLiangMS this is platform independent feature. It was tested on 202305 on mellanox platform. |
Hi @StormLiangMS , I tested the rsyslog.conf generation in 202305 PROD. I tried with one MGMTdevice and one non-MGMTdevice patching the PR.
|
…g server's source address is configured (sonic-net#17616) ### Why I did it An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address. ### How I did it Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF #### How to verify it Manually test: 1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf` 2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf`
…g server's source address is configured (#17616) (#18514) ### Why I did it An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address. ### How I did it Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF #### How to verify it Manually test: 1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf` 2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf` Co-authored-by: Stephen Sun <5379172+stephenxs@users.noreply.github.com>
…g server's source address is configured (sonic-net#17616) ### Why I did it An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address. ### How I did it Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF #### How to verify it Manually test: 1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf` 2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf`
Cherry-pick PR to 202311: #18518 |
…g server's source address is configured (#17616) ### Why I did it An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address. ### How I did it Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF #### How to verify it Manually test: 1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf` 2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf`
Why I did it
An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because
eth0
is always specified as thedevice
of a syslog server and the syslog packets will be sent toeth0
regardless of its destination IP address.Work item tracking
How I did it
Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF
How to verify it
Manually test:
default
as the VRF: nodevice
passed inrsyslog.conf
device
inrsyslog.conf
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)