[SmartSwitch] [HA] disable northbound route zmq flag for ha topology #23329
[SmartSwitch] [HA] disable northbound route zmq flag for ha topology #23329prsunny merged 1 commit intosonic-net:masterfrom
Conversation
Signed-off-by: Jing Zhang <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
zjswhhh
added
the
smartswitch-ha
yxieca
left a comment
yxieca
left a comment
There was a problem hiding this comment.
AI agent on behalf of Ying. Reviewed; no issues found.
|
@zjswhhh , can you provide details on why this must be disabled and what if its enabled? How is this related to NPU loopback pinging. |
|
@prabhataravind to review |
Hi @prsunny - created an issue item to track, details are included: #23328 I don't have the root cause yet, but since it's 100% reproducible, just wanted to add this workaround to unblock test development. |
|
@yue-fred-gao @vivekrnv for viz. |
@zjswhhh peer loopback0 shouldn't be any different from other routes. Is the issue seen for all routes? |
Only for loopback IP. |
| if "orch_northbond_route_zmq_enabled" in out: | ||
| ori_config_db["DEVICE_METADATA"]["localhost"]["orch_northbond_route_zmq_enabled"] = "true" | ||
| if self.topo_name == "t1-smartswitch-ha": | ||
| ori_config_db["DEVICE_METADATA"]["localhost"]["orch_northbond_route_zmq_enabled"] = "false" |
prsunny
changed the title
Description of PR Summary: Fixes # (issue) In smartswitch ha topology, noticed peer loopback0 (npu pa ip) is not pingable if orch_northbond_route_zmq_enabled is set to true - the route failed to install. This is not a ha specific problem, but it's impacting HA tests as NPU-DPU BFD probing requires loopback reachability. Also, we don't need to enable northbond_route_zmq on NPU config. Hence, adding this change to explicitly disable. In golden config gen, check the topo name, if matching ha, set the flag to false.
5 participants
Description of PR
Summary:
Fixes # (issue)
In smartswitch ha topology, noticed peer loopback0 (npu pa ip) is not pingable if orch_northbond_route_zmq_enabled is set to true - the route failed to install.
This is not a ha specific problem, but it's impacting HA tests as NPU-DPU BFD probing requires loopback reachability. Also, we don't need to enable northbond_route_zmq on NPU config. Hence, adding this change to explicitly disable.
sign-off: Jing Zhang [email protected]
Type of change
Back port request
Approach
What is the motivation for this PR?
To make sure npu - dpu works (BFD), so HA tests can pass.
How did you do it?
In golden config gen, check the topo name, if matching ha, set the flag to false.
How did you verify/test it?
Once the flag is set to false, loopback became reachable.
Any platform specific information?
NA.
Supported testbed topology if it's a new test case?
Na.
Documentation