dualtor_neighbor_check.py changed#3931
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
acaa441 to
5e72c89
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
zjswhhh
left a comment
There was a problem hiding this comment.
Also, please evaluate on the backward compatibility. This needs to check in with the no_host_route change.
Signed-off-by: Manas Kumar Mandal <manamand@cisco.com>
5e72c89 to
197fc05
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Manas Kumar Mandal <manamand@cisco.com>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@manamand2020 - can you please address the precommit failures. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Manas Kumar Mandal <manamand@cisco.com>
f49506a to
d4414d8
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
62a3c6b to
df62614
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
4b3d350 to
96b0157
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
@Ndancejic I fixed it. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
86c3c8c to
9ccc5ae
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Manas Kumar Mandal <manamand@cisco.com>
9ccc5ae to
3843ddb
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
What I did Port the fix from sonic-net/sonic-utilities#3931 How to verify it Verified original PR on hardware. Signed-off-by: Manas Kumar Mandal <manamand@cisco.com>
|
Hi @qiluo-msft - please help merge. |
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the dualtor neighbor check functionality by adding nexthop type verification to better identify neighbor routing inconsistencies. The change distinguishes between NEIGHBOR and TUNNEL nexthop types when validating neighbor entries against mux states.
- Adds nexthop table reading from ASIC_DB to capture nexthop type information
- Updates the consistency check logic to verify that active mux states use NEIGHBOR nexthops and standby states use TUNNEL nexthops
- Adds two new test cases to verify SOC IP neighbor handling and multiple neighbor scenarios
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| scripts/dualtor_neighbor_check.py | Implements nexthop table reading in Lua script, adds nexthop type tracking and validation logic in consistency checks |
| tests/dualtor_neighbor_check_test.py | Updates all existing tests with nexthop_table parameter and expected outputs, adds new tests for SOC IP neighbors |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
What I did dualtor_neighbor_check.py script needs this change based on changes in the following PR: sonic-net/sonic-swss#3722 neighbors are no more deleted during switchover to standby
|
@manamand2020 , @zjswhhh , is this backward compatible?. Is there an HLD? Need to see how the output was before and what is the output with this change |
What I did dualtor_neighbor_check.py script needs this change based on changes in the following PR: sonic-net/sonic-swss#3722 neighbors are no more deleted during switchover to standby
…t#4136) Reverts sonic-net#3931 Reverting for backward compatibility issues.

What I did
dualtor_neighbor_check.py script needs this change based on changes in the following PR:
sonic-net/sonic-swss#3722
neighbors are no more deleted during switchover to standby
How I did it
How to verify it
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)