[sflow] Update version of hsflowd#7137
Merged
Conversation
* Updating version of hsflow daemon to apply fix, which resolves problem of switching between IPv4 and IPv6, in case when the IPv4 has deleted for the interface. Signed-off-by: Maksym Belei <Maksym_Belei@jabil.com>
ghost
requested review from
Collaborator
|
/azp run |
1 similar comment
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
lguohan
approved these changes
Mar 28, 2021
raphaelt-nvidia
pushed a commit
to raphaelt-nvidia/sonic-buildimage
that referenced
this pull request
May 23, 2021
* Updating version of hsflow daemon to apply fix, which resolves problem of switching between IPv4 and IPv6, in case when the IPv4 has deleted for the interface. The new release of hsflowd contains the fix for the issue: sflow/host-sflow@2703ecb How I did it HSFLOWD_VERSION env variable has changed in the rules to be pointed to the latest release of hsflowd. How to verify it sudo config sflow enable sudo config loopback add Loopback1 sudo config int ip add Loopback1 a84f:97ff:fea7:33a5::fe80/64 sudo config int ip add Loopback1 192.168.101.1/24 sudo config sflow agent-id add Loopback1 sudo config sflow collector add Collector1 192.168.101.1 sudo config sflow collector add Collector2 a84f:97ff:fea7:33a5::fe80 use sudo sflowtool -p 6343 -l for checking sflow data remove and add again the ipv4 entry of Loopback1. hsflowd should change agent ip from IPv4 to IPv6 and wise versa, depending on IPv4 entry present or not. Switching between IPs is being performed by hsflowd, based on IP address priority ranking. Signed-off-by: Maksym Belei <Maksym_Belei@jabil.com>
carl-nokia
pushed a commit
to carl-nokia/sonic-buildimage
that referenced
this pull request
Aug 7, 2021
* Updating version of hsflow daemon to apply fix, which resolves problem of switching between IPv4 and IPv6, in case when the IPv4 has deleted for the interface. The new release of hsflowd contains the fix for the issue: sflow/host-sflow@2703ecb How I did it HSFLOWD_VERSION env variable has changed in the rules to be pointed to the latest release of hsflowd. How to verify it sudo config sflow enable sudo config loopback add Loopback1 sudo config int ip add Loopback1 a84f:97ff:fea7:33a5::fe80/64 sudo config int ip add Loopback1 192.168.101.1/24 sudo config sflow agent-id add Loopback1 sudo config sflow collector add Collector1 192.168.101.1 sudo config sflow collector add Collector2 a84f:97ff:fea7:33a5::fe80 use sudo sflowtool -p 6343 -l for checking sflow data remove and add again the ipv4 entry of Loopback1. hsflowd should change agent ip from IPv4 to IPv6 and wise versa, depending on IPv4 entry present or not. Switching between IPs is being performed by hsflowd, based on IP address priority ranking. Signed-off-by: Maksym Belei <Maksym_Belei@jabil.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
fix, which resolves problem of switching
between IPv4 and IPv6, in case when the
IPv4 has deleted for the interface.
Signed-off-by: Maksym Belei Maksym_Belei@jabil.com
Why I did it
Resolves #6951
The new release of
hsflowdcontains the fix for the issue: sflow/host-sflow@2703ecbHow I did it
HSFLOWD_VERSIONenv variable has changed in the rules to be pointed to the latest release ofhsflowd.How to verify it
sudo config sflow enablesudo config loopback add Loopback1sudo config int ip add Loopback1 a84f:97ff:fea7:33a5::fe80/64sudo config int ip add Loopback1 192.168.101.1/24sudo config sflow agent-id add Loopback1sudo config sflow collector add Collector1 192.168.101.1sudo config sflow collector add Collector2 a84f:97ff:fea7:33a5::fe80sudo sflowtool -p 6343 -lfor checking sflow datahsflowdshould change agent ip from IPv4 to IPv6 and wise versa, depending on IPv4 entry present or not.Switching between IPs is being performed by
hsflowd, based on IP address priority ranking.Which release branch to backport (provide reason below if selected)
The issue has reported on 202012, but is reproducible on master branch too.
Description for the changelog
Update of hsflowd to the latest release version.