Slide 20
Slide 20 text
Next Hop Group on SONiC | Twitter: @ebiken | 2022/11/23
Next Hop Group on FRR
sonic# show ip route nexthop-group
Codes: K - kernel route, C - connected, S - static, R - RIP,
...snip...
S>* 10.88.0.0/24 [1/0] (26) via 10.0.0.100, Ethernet0, weight 1, 00:01:39
* via 10.0.0.101, Ethernet0, weight 1, 00:01:39
S>* 10.99.0.0/24 [1/0] (26) via 10.0.0.100, Ethernet0, weight 1, 04:56:29
* via 10.0.0.101, Ethernet0, weight 1, 04:56:29
sonic# show nexthop-group rib 26
ID: 26 (zebra)
RefCnt: 2
Uptime: 01:08:01
VRF: default
Valid, Installed
Depends: (22) (27)
via 10.0.0.100, Ethernet0 (vrf default), weight 1
via 10.0.0.101, Ethernet0 (vrf default), weight 1
sonic# show nexthop-group rib 22
ID: 22 (zebra)
RefCnt: 3
Uptime: 02:27:13
VRF: default
Valid, Installed
Interface Index: 8
via 10.0.0.100, Ethernet0 (vrf default), weight 1
Dependents: (26)
sonic# show nexthop-group rib 27
ID: 27 (zebra)
RefCnt: 3
Uptime: 07:19:32
VRF: default
Valid, Installed
Interface Index: 8
via 10.0.0.101, Ethernet0 (vrf default), weight 1
Dependents: (26)
Use “vtysh” command on SONiC host to access FRR CLI
admin@sonic:~$ vtysh
Hello, this is FRRouting (version 8.2.2).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
sonic#
As of today, FRR do NOT use NHA_GROUP (Next Hop
Attribute Group) when communicating with fpmsyncd.
Thus, it will be same as when configured via CLI.
In other words, APPL_DB will only have ROUTE_TABLE
entry and NEXT_HOP_GROUP_TABLE entry would not
be created.