$ ip table add 1
-or the default table, comprises 2 *ip4_fib_t* objects.
+or the default table, comprises 2 *ip4_fib_t* objects.
The 'non-forwarding' *ip4_fib_t* contains all the entries in the table
and, the 'forwarding' contains the entries that are matched against in
the data-plane. The difference between the two sets are the entries
To see the amount of memory consumed by the IPv4 tables use:
.. code-block:: console
-
+
vpp# sh ip fib mem
ipv4-VRF:0 mtrie:335744 hash:4663
ipv4-VRF:1 mtrie:333056 hash:3499
.. code-block:: console
- vpp# sh ip6 fib mem
+ vpp# sh ip6 fib mem
IPv6 Non-Forwarding Hash Table:
Hash table ip6 FIB non-fwding table
7 active elements 7 active buckets
0 linear search buckets
arena: base 7f2fe48bf000, next 803c0
used 525248 b (0 Mbytes) of 33554432 b (32 Mbytes)
-
+
as we scale to 128k IPv6 entries:
.. code-block:: console
vpp# sh fib mem
FIB memory
Tables:
- SAFI Number Bytes
- IPv4 unicast 1 33619968
- IPv6 unicast 2 118502784
- MPLS 0 0
- IPv4 multicast 1 1175
- IPv6 multicast 1 525312
+ SAFI Number Bytes
+ IPv4 unicast 1 33619968
+ IPv6 unicast 2 118502784
+ MPLS 0 0
+ IPv4 multicast 1 1175
+ IPv6 multicast 1 525312
Nodes:
Name Size in-use /allocated totals
- Entry 72 1048589/ 1048589 75498408/75498408
- Entry Source 40 1048589/ 1048589 41943560/41943560
- Entry Path-Extensions 76 0 / 0 0/0
- multicast-Entry 192 6 / 6 1152/1152
- Path-list 40 18 / 18 720/720
- uRPF-list 16 14 / 14 224/224
- Path 72 22 / 22 1584/1584
- Node-list elements 20 1048602/ 1048602 20972040/20972040
- Node-list heads 8 24 / 24 192/192
+ Entry 72 1048589/ 1048589 75498408/75498408
+ Entry Source 40 1048589/ 1048589 41943560/41943560
+ Entry Path-Extensions 76 0 / 0 0/0
+ multicast-Entry 192 6 / 6 1152/1152
+ Path-list 40 18 / 18 720/720
+ uRPF-list 16 14 / 14 224/224
+ Path 72 22 / 22 1584/1584
+ Node-list elements 20 1048602/ 1048602 20972040/20972040
+ Node-list heads 8 24 / 24 192/192
and with 2M
.. code-block:: console
-
- vpp# sh fib mem
+
+ vpp# sh fib mem
FIB memory
Tables:
- SAFI Number Bytes
- IPv4 unicast 1 33619968
- IPv6 unicast 2 252743040
- MPLS 0 0
- IPv4 multicast 1 1175
- IPv6 multicast 1 525312
+ SAFI Number Bytes
+ IPv4 unicast 1 33619968
+ IPv6 unicast 2 252743040
+ MPLS 0 0
+ IPv4 multicast 1 1175
+ IPv6 multicast 1 525312
Nodes:
Name Size in-use /allocated totals
- Entry 72 2097165/ 2097165 150995880/150995880
- Entry Source 40 2097165/ 2097165 83886600/83886600
- Entry Path-Extensions 76 0 / 0 0/0
- multicast-Entry 192 6 / 6 1152/1152
- Path-list 40 18 / 19 720/760
- uRPF-list 16 18 / 18 288/288
- Path 72 22 / 23 1584/1656
- Node-list elements 20 2097178/ 2097178 41943560/41943560
- Node-list heads 8 24 / 24 192/192
+ Entry 72 2097165/ 2097165 150995880/150995880
+ Entry Source 40 2097165/ 2097165 83886600/83886600
+ Entry Path-Extensions 76 0 / 0 0/0
+ multicast-Entry 192 6 / 6 1152/1152
+ Path-list 40 18 / 19 720/760
+ uRPF-list 16 18 / 18 288/288
+ Path 72 22 / 23 1584/1656
+ Node-list elements 20 2097178/ 2097178 41943560/41943560
+ Node-list heads 8 24 / 24 192/192
However, the situation is not a simple as that. All of the 1M prefixes
added above were reachable via the same next-hop, so the path-list