Disable default route in dpu#21393
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @bingwang-ms - can you help merge please? |
Signed-off-by: Yue Gao <yuega2@cisco.com>
513d655 to
ab0e43d
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Nishanth Sampath Kumar <nissampa@cisco.com>
|
Hi @yue-fred-gao , the show dhcp info command is not working without gateway: |
Thanks for pointing this out. I have raised PR sonic-net/sonic-buildimage#24801. Please take a look. |
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
Signed-off-by: Yue Gao <yuega2@cisco.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Saravanan <saravanan@nexthop.ai>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
|
Hi @yue-fred-gao , I have find another issue caused by this PR. Since the default route is removed, we are not able to ssh to the DPU from the switch, because there is no route to the NPU mgmt IP: admin@sonic:~$ sudo tcpdump -i eth0-midplane tcp dst port 22 -vvv admin@r-SN4280-10:~$ show ip interface | grep eth0 May I ask where do you configure the route to the NPU mgmt IP? |
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Venkata Gouri Rajesh Etla <vrajeshe@cisco.com>
|
From the switch, you should have a subnet route 169.254.200.0/24 over eth0-midplane. So when you ssh to a DPU, eth0-midplane should be picked as the outgoing interface and its ip address (165.254.200.254) should be used as source IP, not the NPU mgmt IP. I think you can check in your setup why NPU mgmt IP is used instead. |
Signed-off-by: Yue Gao <yuega2@cisco.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: YiFan Wang <yifan@nexthop.ai>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Priyansh Tratiya <ptratiya@microsoft.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Lakshmi Yarramaneni <lakshmi@nexthop.ai>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Yael Tzur <ytzur@nvidia.com>
Signed-off-by: Yue Gao <yuega2@cisco.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: mssonicbld <sonicbld@microsoft.com>
|
Cherry-pick PR to 202511: #22413 |
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Zhuohui Tan <zhuohui.tan@amd.com>
Signed-off-by: Yue Gao <yuega2@cisco.com> Signed-off-by: Abhishek <abhishek@nexthop.ai>
Description of PR
Summary:
Fixes #21392
Type of change
Back port request
Approach
What is the motivation for this PR?
minigraph for smartswitch topo should not have gateway in DHCP_IPV4_SERVER table. f gateway is not present, "router" dhcp option won't be included in the response and client won't install default route. Please see PR sonic-net/sonic-buildimage#21462 for the design.
How did you do it?
Remove gateway option from generated golden config
How did you verify/test it?
Run "./testbed-cli.sh deploy-mg vms-kvm-t1-smartswitch-ha ./lab ./password.txt"
Verify "gateway" option is not in DHCP_IPV4_SERVER
Verified no default route over midplane in DPU by show ip route.
`admin@dpu00:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR, f - OpenFabric,
> - selected route, * - FIB route, q - queued route, r - rejected route
S>*0.0.0.0/0 [1/0] via 20.0.200.14, Ethernet0, 17:04:20
C>*20.0.200.0/28 is directly connected, Ethernet0, 17:04:20
K 20.0.200.0/28 [0/0] is directly connected, Ethernet0, 17:04:23
C>*169.254.200.0/24 [0/1024] is directly connected, eth0-midplane, 17:04:27
K 240.127.1.0/24 [0/0] is directly connected, docker0, inactive 17:04:27
admin@dpu00:~$ Connection to 169.254.200.1 closed by remote host.
`
Any platform specific information?
Specific to SmartSwitch
Supported testbed topology if it's a new test case?
Documentation