scottlaird
commented
4 years ago Comments on my previous routes-not-propagating bug had questions about next-hop entries. I'm not sure how those are supposed to work with IPv6, but I don't see any v6 next hops in either DB.
$ redis-dump -d 0 -y
...
"ROUTE_TABLE:2001:470:e959:eeee::/64": {
"expireat": 1595699202.551358,
"ttl": -0.001,
"type": "hash",
"value": {
"ifname": "Ethernet116",
"nexthop": "fe80::9a03:9bff:fe77:95e6"
}
},
...
$ redis-dump -d 0 -y | grep fe80::9a03:9bff:fe77:95e6
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
"nexthop": "fe80::9a03:9bff:fe77:95e6"
$ redis-dump -d 1 -y | grep fe80::9a03:9bff:fe77:95e6
$By comparison, my IPv4 route next-hops have NEIGH_TABLE entries in DB 0 and ASIC_STATE:SAI_OBJECT_TYPE_NEIGHBOR_ENTRY entries in DB 1. So perhaps this is an issue with fpmsyncd not generating neighbor entries for v6?
yxieca
Tison-Liu
Description
Kernel IPv6 routes aren't consistently propagating from the APPL_DB to the ASIC_DB. This is seen on two different devices running recent(ish) Jenkins builds.
I'm using OSPFv6 to propagate IPv6 routes. They're appearing in the kernel just fine:
And they're in the APPL DB:
But they're not in the ASIC DB:
There is nothing useful in
/var/log/syslogor/var/log/swssLooking deeper, there are only 4 IPv6 routes in the ASIC DB:
For comparison,
ip -6 addr show | wcgives 66 lines, although a few of those are ECMP routes.Oddly, the default route in the ASIC DB (::/0) isn't actually correct, either. Here's what's in the ASIC DB:
That's listed as SAI_PACKET_ACTION_DROP. However, the kernel has a default route:
The APPL DB version matches the kernel:
I'm not sure where the default drop is coming from.
Steps to reproduce the issue:
ip route add 2001:470:e959:ffff::/64 via fe80::ba6a:97ff:fe8a:7168 dev Ethernet120redis-dump -d 0 -y | grep ffffredis-dump -d 1 -y | grep ffffDescribe the results you received:
No route for 2001:470:e959:ffff::/64 in the ASIC DB.
Describe the results you expected:
One route for 2001:470:e959:ffff::/64 in the ASIC DB.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
show version:Attach debug file
sudo generate_dump:sonic_dump_sw100_20200725_060652.tar.gz