Skip to content
New issue

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

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

Already on GitHub? # to your account

[src/ptf update]: Submodule update #652

Merged
merged 4 commits into from
May 31, 2017
Merged

[src/ptf update]: Submodule update #652

merged 4 commits into from
May 31, 2017

Conversation

pavel-shirshov
Copy link
Contributor

This update fixes ptf_nn_agent race condition. The race condition occurs, when a physical interface starts working later then a nanomsg socket receive a packet for the physical interface.

@pavel-shirshov pavel-shirshov merged commit 01a716c into sonic-net:master May 31, 2017
@pavel-shirshov pavel-shirshov deleted the pavelsh/ptf_update branch May 31, 2017 17:48
yxieca added a commit to yxieca/sonic-buildimage that referenced this pull request Sep 19, 2019
Submodule src/sonic-swss 24fcbb6..3cee6b8:
  > [aclorch]: Fix table name in counter table for mirror rules (sonic-net#1060)
  > Cannot ping to link-local ipv6 interface address of the switch. (sonic-net#774)
  > [MirrorOrch]: Mirror Session Retention across Warm Reboot (sonic-net#1062)

Submodule src/sonic-utilities afaedb7..a06bee7:
  > [201811][config] Add '-h' and '-?' as help options to unify with show/sonic-clear cmds (sonic-net#654)
  > Revert "Fixed config Asym PFC CLI. (sonic-net#632)" (sonic-net#652)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
yxieca added a commit that referenced this pull request Sep 19, 2019
Submodule src/sonic-swss 24fcbb6..3cee6b8:
  > [aclorch]: Fix table name in counter table for mirror rules (#1060)
  > Cannot ping to link-local ipv6 interface address of the switch. (#774)
  > [MirrorOrch]: Mirror Session Retention across Warm Reboot (#1062)

Submodule src/sonic-utilities afaedb7..a06bee7:
  > [201811][config] Add '-h' and '-?' as help options to unify with show/sonic-clear cmds (#654)
  > Revert "Fixed config Asym PFC CLI. (#632)" (#652)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
yxieca added a commit to yxieca/sonic-buildimage that referenced this pull request Oct 2, 2019
Submodule src/sonic-swss fcd091c..9585be4:
  > [teamsyncd]: Check if LAG exists before removing (sonic-net#1069)
  > [mirrororch]: Toggle the mirror session when moving between VLAN/non-VLAN (sonic-net#1078)

Submodule src/sonic-utilities 7bb6ffb..2d721de:
  > [show] Properly replace port name with alias in command output (sonic-net#664)
  > [neighbor_advertiser] hand pick partial change from sonic-net#525 (sonic-net#689)
  > Revert "Revert "Fixed config Asym PFC CLI. (sonic-net#632)" (sonic-net#652)"

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
yxieca added a commit that referenced this pull request Oct 3, 2019
* [201811][swss][utilities] advance sub module head

Submodule src/sonic-swss fcd091c..9585be4:
  > [teamsyncd]: Check if LAG exists before removing (#1069)
  > [mirrororch]: Toggle the mirror session when moving between VLAN/non-VLAN (#1078)

Submodule src/sonic-utilities 7bb6ffb..2d721de:
  > [show] Properly replace port name with alias in command output (#664)
  > [neighbor_advertiser] hand pick partial change from #525 (#689)
  > Revert "Revert "Fixed config Asym PFC CLI. (#632)" (#652)"

Signed-off-by: Ying Xie <ying.xie@microsoft.com>

* address compile issue

Submodule src/sonic-swss 9585be4..2529d79:
  > [mirrororch]: Address compiler switch issue (#1079)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
AidanCopeland pushed a commit to Metaswitch/sonic-buildimage that referenced this pull request Apr 14, 2022
mlok-nokia pushed a commit to mlok-nokia/sonic-buildimage that referenced this pull request Feb 27, 2025
… LC (sonic-net#652)

What/Why I did:
Initially I made the change that Fallback Route [routes from AH on Upstream LC] not to get programmed [mark them as deny] on Downstream LC's as reasoning was that on Downstream LC's can forward them based on Default-route. However that assumption is correct for example we have topology like this:

RH is connected to ASIC0 of Upstream LC
AH is connected to ASIC1 of Upstream LC

Downstream LC will learn route from RH [including default-route] and will only forward to ASIC0 of upstream LC . Above assumption was fine if we always have AH and RH connected to same ASIC of Upstream LC.

How I verify:
UT updated
Manual Verification.
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants