RIB/FIB API configuration overview

About this task

Configuration related to the RIB/FIB API service on the router is spread across two general areas:

system-level GRPC configuration (config>system>grpc or config>system>security>profile>grpc)
routing instance configuration (config>router or config>service>vprn)

To enable the router to receive and process RIB API requests from a client perform the following steps.

Procedure

The RIB API service must be enabled at the gRPC system level: config>system>grpc>rib-api>no shutdown.
Optionally, a non-zero purge-timeout can be configured: config>system>grpc>rib-api>purge-timeout.
The purge-timeout applies to all gRPC clients participating in the RIB API service.
Optionally, the sending of TCP keepalives can be enabled toward all gRPC clients by configuring values under the config>system>grpc>tcp-keepalive context.
One or more gRPC user accounts should be created, and these user accounts should be attached to a profile that authorizes the GetVersion and Modify RPCs associated with the RIB API service. Clients need to send a valid username and password when initiating any RPC.
Nokia recommends using TLS-based encryption between the client and server. This involves associating a tls-server-profile with the gPRC server. For more information, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR System Management Guide.
If you want to use the RIB API service to program MPLS label entries then a reserved-label-block must be configured using the config>router>rib-api>mpls>reserved-label-block command and MPLS programming functionality must be enabled using the config>router>rib-api>mpls>no shutdown command.

What to do next

To enable the router to use RIB API tunnel entries for resolving specific types of static and BGP routes, additional configuration is needed. For more information, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR Unicast Routing Protocols Guide.