TOI Author :: Abhiram Kalluru

EOS SDK and its RPC counterpart traditionally offer two separate calls for configuring static routes. These calls are ip_route_set/ip_route_via_set and mpls_route_set/mpls_route_via_set. When calling the SDK API directly the calling latency is negligible, since it is a simple function call. However, the time of each of those calls can become a considerable factor with the adoption of RPC. To reduce the overall latency associated with creating and updating numerous routes, EOS SDK RPC now supports bulk calls.

This feature allows FDB export through the OpenConfig AFT YANG models. The streaming behavior of mac addresses are  Entries associated with SVI or L3 port have an associated VRF name. The VRF name is used to specify which network instance the FDB entry belongs to. 

This feature allows exporting IP-in-IP tunnel counters through the OpenConfig AFT YANG models.This exporting IP-in-IP counters feature is supported on all platforms, however counting the IP-in-IP tunnel packets is supported only on DCS-7500R3, DCS-7280R3 and DCS-7800R3 series. 

This feature introduces a flag to indicate to a gNMI client that the FIB (forwarding information base) or IPv4/IPv6 unicast AFT (abstract forwarding table) have converged and the snapshot is consistent with the device.

This feature allows LFIB (Label Forwarding Information Base) & associated counters export through OpenConfig mpls AFT (Abstract Forwarding Tree) YANG model.

gRIBI (gRPC Routing Information Base Interface) defines an interface through which OpenConfig AFT (Abstract

Prior to this release, BGP in “ribd” mode (when routing protocols are configured in

Nexthop Groups is a feature that allows users to manually configure a set of nexthops by specifying their nexthop