support for dut single stack ipv6 mgmt ip#20292
Merged
wangxin merged 10 commits intosonic-net:masterfrom Nov 3, 2025
Merged
Conversation
- fix test cases to support ipv6 mgmt ip - skip test cases that do not support dut ipv6 yet
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nhe-NV
approved these changes
Aug 20, 2025
Collaborator
|
@wangxin Can you please help review? |
bingwang-ms
reviewed
Aug 21, 2025
| skip: | ||
| reason: "ipv6 mgmt ip is not supported" | ||
| conditions: | ||
| - "is_mgmt_ipv6_only==True" |
Collaborator
There was a problem hiding this comment.
Is SNMP supported after snmp_fact change in this PR?
Contributor
Author
There was a problem hiding this comment.
Hi @bingwang-ms, this case will still fail with the changes in this PR. This is becasue the key "lldpLocManAddrLen" does not exist in snmp_facts['snmp_lldp']. This still needs further analysis so I skipped it for now
bingwang-ms
reviewed
Aug 21, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
… type and update certificate creation function to utilize it.
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
…upported conditions
Collaborator
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
…to unsupported DUT IPv6 management IP.
Collaborator
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Aharon Malkin <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
vrajeshe
pushed a commit
to Akshath-17/sonic-mgmt
that referenced
this pull request
Jan 4, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Venkata Gouri Rajesh Etla <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
yifan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 14, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: YiFan Wang <[email protected]>
yifan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 14, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: YiFan Wang <[email protected]>
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 20, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
11 tasks
PriyanshTratiya
pushed a commit
to PriyanshTratiya/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Priyansh Tratiya <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Guy Shemesh <[email protected]>
lakshmi-nexthop
pushed a commit
to lakshmi-nexthop/sonic-mgmt
that referenced
this pull request
Jan 28, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Lakshmi Yarramaneni <[email protected]>
lakshmi-nexthop
pushed a commit
to lakshmi-nexthop/sonic-mgmt
that referenced
this pull request
Jan 28, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Lakshmi Yarramaneni <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Jan 29, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Jan 29, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Yael Tzur <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Yael Tzur <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Raghavendran Ramanathan <[email protected]>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Raghavendran Ramanathan <[email protected]>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 18, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups Signed-off-by: Raghavendran Ramanathan <[email protected]>
anilal-amd
pushed a commit
to anilal-amd/anilal-forked-sonic-mgmt
that referenced
this pull request
Feb 19, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Zhuohui Tan <[email protected]>
mssonicbld
pushed a commit
that referenced
this pull request
Feb 23, 2026
In PR #21045, I made mistakes while resolving the conflicts with #20292. Some code added in #20292 was accidentally reverted. This change is to add back the code introduced in #20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Mar 17, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]> Signed-off-by: Abhishek <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
fix test cases to support ipv6 mgmt ip skip test cases that do not support dut ipv6 yet What is the motivation for this PR? We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases How did you do it? update test cases and also skip condition files, etc... How did you verify/test it? run regression with ipv6 mgmt ip in physical setups
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
In PR sonic-net#21045, I made mistakes while resolving the conflicts with sonic-net#20292. Some code added in sonic-net#20292 was accidentally reverted. This change is to add back the code introduced in sonic-net#20292 for creating SNMP UdpTransportTarget. Then the snmp_facts module will work with IPv6 only scenario again. Signed-off-by: Xin Wang <[email protected]>
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
5 participants
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.
Description of PR
Summary: Enhancement of test cases to support dut single stack mgmt ipv6
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
We now enabled single stack ipv6 address for switch management port, some test cases do not support it yet, this PR fixed some of the cases or skiped for the remaining cases
How did you do it?
update test cases and also skip condition files, etc...
How did you verify/test it?
run regression with ipv6 mgmt ip in physical setups
Any platform specific information?
NA
Supported testbed topology if it's a new test case?
Documentation