[dualtor] Add neighbor entry orchagent testcase#3031
Conversation
f1e8bb6 to
8006bc4
Compare
8006bc4 to
5f16a54
Compare
|
depends on #3098 |
|
/AZP run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
5f16a54 to
b30f474
Compare
|
/AZP run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AZP run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tests/dualtor/test_t1_to_standby.py
Outdated
There was a problem hiding this comment.
Would it not be better if we send traffic to all/multiple servers, and then verify that the traffic is dropped only for the server whose neighbor entry has been removed?
tests/dualtor/test_t1_to_standby.py
Outdated
There was a problem hiding this comment.
How did we decide to send 10 packets and not more? I think 10 packets are too less to verify close to real operational scenario.
|
Please change the filename to be more specific than just |
Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
b30f474 to
6812e0b
Compare
| testutils.send(ptfadapter, int(ptf_t1_intf.strip("eth")), pkt, count=10) | ||
|
|
||
| logging.info("send traffic to server %s after removing neighbor entry", server_ipv4) | ||
| tunnel_monitor.existing = False |
There was a problem hiding this comment.
Is there a reason we did this instead of just creating a new tunnel_traffic_monitor?
Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
|
Hi @theasianpianist, could you please give another look at the new changes? |
900e7e4 to
4cd0ed8
Compare
Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
4cd0ed8 to
bb574a7
Compare
Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
|
|
This pull request fixes 1 alert when merging 1c065b1 into 94ffb11 - view on LGTM.com fixed alerts:
|
|
lgtm |
|
/Azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Approach What is the motivation for this PR? Verify that, for standby ToR, the traffic to the server will be dropped if the neighbor entry of server is removed. How did you do it? Verify that the traffic to server is neither passed to server directly by standby ToR or encapsulated to the active ToR. Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
Approach What is the motivation for this PR? Verify that, for standby ToR, the traffic to the server will be dropped if the neighbor entry of server is removed. How did you do it? Verify that the traffic to server is neither passed to server directly by standby ToR or encapsulated to the active ToR. Signed-off-by: Longxiang Lyu <lolv@microsoft.com>
…atically (sonic-net#17849) src/sonic-utilities * 7a7305e9 - (HEAD -> 202205, origin/202205) Fix issue: out of range sflow polling interval is accepted and stored in config_db (sonic-net#2847) (sonic-net#3123) (3 hours ago) [Stephen Sun] * 06d11339 - [config] config reload should generate sysinfo if missing (sonic-net#3031) (sonic-net#3126) (21 hours ago) [jingwenxie] * bef96a1d - [202205] Allow using latest sonic-swss-common build even if tests failed (sonic-net#3127) (4 days ago) [Saikrishna Arcot]
Verify that, for standby ToR, the traffic to the server will be dropped if the neighbor entry of server is removed.
Signed-off-by: Longxiang Lyu lolv@microsoft.com
Description of PR
Summary:
Fixes #2805
Type of change
Approach
What is the motivation for this PR?
Verify that, for standby ToR, the traffic to the server will be dropped if the neighbor entry of server is removed.
How did you do it?
Verify that the traffic to server is neither passed to server directly by standby ToR or encapsulated to the active ToR.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation