Nexthop-lb-weight is used for load-balancing.
Each list member MUST be assigned a weight
between 1 and 99. The weight determines the
proportion of traffic to be sent over a nexthop
used for forwarding as a ratio of the weight of
this nexthop divided by th...

Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99. Lower
values are more preferred. To download N
nexthops to the FIB, the N nexthops with the lowest
value are selected. If there are more than N
nexthops that have ...

This represents the list of interfaces associated
with this routing instance. The interface list helps
constrain the boundaries of packet forwarding.
Packets coming on these interfaces are directly
associated with the given routing instance. The
interface...

Each RIB can be optionally associated with a
ENABLE_IP_RPF_CHECK attribute that enables Reverse
path forwarding (RPF) checks on all IP routes in that
RIB. Reverse path forwarding (RPF) check is used to
prevent spoofing and limit malicious traffic.

This can be an encap representing an IP tunnel or
MPLS tunnel or others as defined in info model.
An optional egress interface can be chained to the
tunnel encap to indicate which interface to send
the packet out on. The egress interface is useful
when t...

Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99. Lower
values are more preferred. To download a
primary/standby/tertiary group to the FIB, the
nexthops that are resolved and are most preferred
are selected.

To indicate whether a nexthop is sharable
or non-sharable.
true - sharable, means the nexthop can be shared
with other routes
false - non-sharable, means the nexthop can not
be shared with other routes.

ROUTE_PREFERENCE: This is a numerical value that
allows for comparing routes from different
protocols. Static configuration is also
considered a protocol for the purpose of this
field. It is also known as administrative-distance.
The lower the value, th...

To update a route or a list of route of a rib.
The inputs:
1. The match conditions, could be:
a. route prefix, or
b. route attributes, or
c. nexthop;
2. The update parameters to be used:
a. new nexthop;
b. new route attributes;next...