BGP RIB sharding is to split the BGP process across routes. Different routes are hashed into different threads to achieve concurrency. BGP RIB sharding splits a unified BGP RIB into several sub RIBs and each sub RIB handles a subset of BGP routes. Each sub RIB is served by a separate RPD thread to achieve concurrency. BGP RIB sharding is disabled by default. To enable, you need to explicitly configure it on a multicore routing engine. This feature is supported only on 64-bit routing protocol process (rpd) where the Routing Engine has more than one core. We recommend configuring this feature on a device with atleast 4CPU cores and 16GB of memory.

This KB shows basic configuration of RIB Sharding and how to check if any RE model supports it.

RIB Sharding can be configured as below:

[edit system processes routing bgp]

rib-sharding {

  number-of-shards;

}

Check your RE capacity, how many cores it has, how much memory it has.

Please note that:

• RPD would restart automatically when rib-sharding or update-threading configuration is changed.
• Sharding requires Update/IO thread. If rib-sharding is configured and update-threading is not configured, the commit check fails.

set system processes routing bgp rib-sharding number-of-shards 2

set system processes routing bgp update-threading number-of-threads 2

RE specification can be checked from the below link to confirm if your RE supports RIB sharding:

routing-engine-m-mx-t-series-specifications-by-model