<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'><span style="font-size: 13.3333px;">It shows the desired result.</span><br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br>Midwest-IX<br>http://www.midwest-ix.com<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Matthew Huff" <mhuff@ox.com><br><b>To: </b>"Mike Hammett" <nanog@ics-il.net>, "NANOG" <nanog@nanog.org><br><b>Sent: </b>Monday, April 3, 2023 5:38:23 AM<br><b>Subject: </b>RE: Cisco Nexus 3k Route Selection\Packet Forwarding Debugging<br><br>switch-core1# sh forwarding route x.x.x.x<br><br>slot 1<br>=======<br><br><br>IPv4 routes for table default/base<br><br>------------------+-----------------------------------------+----------------------+-----------------+-----------------<br>Prefix | Next-hop | Interface | Labels | Partial Install <br>------------------+-----------------------------------------+----------------------+-----------------+-----------------<br>x.x.x.x/24 x.x.x.250 Ethernet1/29 <br><br><br>switch-core1# show routing hash x.x.x.x y.y.y.y<br>Load-share parameters used for software forwarding:<br>load-share mode: address source-destination port source-destination<br>Hash for VRF "default"<br>Hashing to path *y.y.y.y Eth1/29<br>For route:<br>y.y.y.0/24, ubest/mbest: 1/0<br> *via z.z.z.z, Eth1/29, [90/3072], 1w2d, eigrp-100, internal<br><br><br><br><br>From: NANOG <nanog-bounces+mhuff=ox.com@nanog.org> On Behalf Of Mike Hammett<br>Sent: Monday, April 3, 2023 1:21 AM<br>To: NANOG <nanog@nanog.org><br>Subject: Cisco Nexus 3k Route Selection\Packet Forwarding Debugging<br><br>We have a Nexus 3064 that is setup with partial BGP tables and is routing based on that. <br><br><br>I've done a show ip bgp for an IP of interest and it has an expected next hop IP. I show ip arp on that next hop IP and it has the expected interface. <br><br><br>However, sFlows show the packets leaving on a different interface, the one that would carry the default route for routes not otherwise known. <br><br><br>If the next hop IP is expected and the ARP of that next hop IP is expected, why are packets leaving out an unexpected interface? <br><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br>Midwest-IX<br>http://www.midwest-ix.com<br><br></div><br></div></body></html>