suzieq
suzieq copied to clipboard
Published
20 hours ago •
netenglabs
netenglabs
Path doesn't work for IPv6 when starting node is a Linux server
Describe the bug
jpiet> path show src='2001:db8:0:1::101' dest='2001:db8:0:4::104' namespace=dual-bgp
pathid hopCount namespace hostname iif vrf overlay mtuMatch mtu timestamp
0 1 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
1 1 1 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
Expected behavior v4 looks from the same src and dest servers
jpiet> path show src='172.16.1.101' dest='172.16.4.104' namespace=dual-bgp
pathid hopCount namespace hostname iif vrf overlay mtuMatch mtu timestamp
0 1 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
1 1 1 dual-bgp leaf01 vlan13 default False True 1500 2020-06-13 03:45:52.015
2 1 2 dual-bgp spine02 swp1 default False True 1500 2020-06-13 03:45:07.440
3 1 3 dual-bgp leaf04 swp2 default False True 1500 2020-06-13 03:45:07.440
4 1 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
5 2 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
6 2 1 dual-bgp leaf01 vlan13 default False True 1500 2020-06-13 03:45:52.015
7 2 2 dual-bgp spine02 swp1 default False True 1500 2020-06-13 03:45:07.440
8 2 3 dual-bgp leaf03 swp2 default False True 1500 2020-06-13 03:45:07.440
9 2 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
10 3 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
11 3 1 dual-bgp leaf02 vlan13 default False True 1500 2020-06-13 03:45:52.015
12 3 2 dual-bgp spine02 swp2 default False True 1500 2020-06-13 03:45:07.440
13 3 3 dual-bgp leaf04 swp2 default False True 1500 2020-06-13 03:45:07.440
14 3 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
15 4 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
16 4 1 dual-bgp leaf02 vlan13 default False True 1500 2020-06-13 03:45:52.015
17 4 2 dual-bgp spine02 swp2 default False True 1500 2020-06-13 03:45:07.440
18 4 3 dual-bgp leaf03 swp2 default False True 1500 2020-06-13 03:45:07.440
19 4 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
20 5 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
21 5 1 dual-bgp leaf01 vlan13 default False True 1500 2020-06-13 03:45:52.015
22 5 2 dual-bgp spine01 swp1 default False True 1500 2020-06-13 03:45:07.440
23 5 3 dual-bgp leaf03 swp1 default False True 1500 2020-06-13 03:45:07.259
24 5 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
25 6 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
26 6 1 dual-bgp leaf01 vlan13 default False True 1500 2020-06-13 03:45:52.015
27 6 2 dual-bgp spine01 swp1 default False True 1500 2020-06-13 03:45:07.440
28 6 3 dual-bgp leaf04 swp1 default False True 1500 2020-06-13 03:45:07.259
29 6 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
30 7 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
31 7 1 dual-bgp leaf02 vlan13 default False True 1500 2020-06-13 03:45:52.015
32 7 2 dual-bgp spine01 swp2 default False True 1500 2020-06-13 03:45:07.440
33 7 3 dual-bgp leaf03 swp1 default False True 1500 2020-06-13 03:45:07.259
34 7 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
35 8 0 dual-bgp server101 bond0 default False NaN 1500 2020-06-13 03:45:37.112
36 8 1 dual-bgp leaf02 vlan13 default False True 1500 2020-06-13 03:45:52.015
37 8 2 dual-bgp spine01 swp2 default False True 1500 2020-06-13 03:45:07.440
38 8 3 dual-bgp leaf04 swp1 default False True 1500 2020-06-13 03:45:07.259
39 8 4 dual-bgp server104 bond0 default False NaN 1500 2020-06-13 03:45:51.630
This is because there's no ND entry associated with the host in the ARP table of any leaf (or we're not capturing the ND info) and the servers don't run LLDP.
Can you please verify that there's an ND entry on the leaves associated with server101/server104 IPv6 addresses, but Suzieq doesn't capture that data?
I'm still getting that same result as before, though now I see the addresses in the arpnd table
jpiet> arpnd show hostname=leaf04
namespace hostname ipAddress oif macaddr state remote timestamp
0 dual-bgp leaf04 169.254.0.1 swp1 52:54:00:5a:37:5e permanent False 2020-06-15 23:10:36.602
1 dual-bgp leaf04 169.254.0.1 swp2 52:54:00:ad:6e:e2 permanent False 2020-06-15 23:10:36.602
2 dual-bgp leaf04 169.254.1.1 peerlink.4094 52:54:00:ce:bd:0d reachable False 2020-06-15 23:10:36.602
3 dual-bgp leaf04 172.16.3.1 vlan13 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
4 dual-bgp leaf04 172.16.4.1 vlan24 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
5 dual-bgp leaf04 192.168.121.1 eth0 52:54:00:55:a0:ff reachable False 2020-06-15 23:10:36.602
6 dual-bgp leaf04 2001:db8:0:3::1 vlan13 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
7 dual-bgp leaf04 2001:db8:0:4::1 vlan24 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
8 dual-bgp leaf04 fe80::5054:ff:fe25:bdc4 vlan13 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
9 dual-bgp leaf04 fe80::5054:ff:fe25:bdc4 vlan24 52:54:00:25:bd:c4 permanent False 2020-06-15 23:10:36.602
10 dual-bgp leaf04 fe80::5054:ff:fe30:e7b3 vlan13 52:54:00:30:e7:b3 reachable False 2020-06-15 23:10:36.602
11 dual-bgp leaf04 fe80::5054:ff:fe5a:375e swp1 52:54:00:5a:37:5e router False 2020-06-15 23:10:36.602
12 dual-bgp leaf04 fe80::5054:ff:fe68:8cdd vlan24 52:54:00:68:8c:dd reachable False 2020-06-15 23:10:36.602
13 dual-bgp leaf04 fe80::5054:ff:fead:6ee2 swp2 52:54:00:ad:6e:e2 router False 2020-06-15 23:10:36.602
can we print an error if LLDP does not exist, rather than returning source and dest
The main reason for this is that the ARPND entry is based off of LLA, not the global nexthop IP shown in the route table. This seems a Linux server-specific issue. If we run path trace between routers, it works fine.