Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarification of use and semantics of metric and preference of next-h… #1240

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 31 additions & 10 deletions release/models/local-routing/openconfig-local-routing.yang
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,14 @@ module openconfig-local-routing {
protocol-specific policy after importing the route into the
protocol for distribution (again via routing policy).";

oc-ext:openconfig-version "2.0.1";
oc-ext:openconfig-version "2.0.2";

revision "2025-01-03" {
description
"Update static route nexthop's and aggregate route
description of metric and preference attributes.";
reference "2.0.2";
}

revision "2022-11-01" {
description
Expand Down Expand Up @@ -163,24 +170,38 @@ module openconfig-local-routing {
selection of the next-hop entry. The lower the metric, the more
preferable the prefix entry is. When this value is not
specified, the metric is inherited from the default metric of
the implementation for static route entries. When multiple
the implementation for static/aggregate route entries. When multiple
next-hops are specified for a static route, the metric is
utilized to determine which of the next-hops to be installed in
the RIB. When multiple next-hops have the same metric (be it
specified, or simply the default) then these next-hops should
all be installed in the RIB.";
utilized to determine which of the next-hops to be used in best
static route for given prefix, and conseqently be eligable for
installation in RIB (provided static route is selected as best
route against routes lerned form other protocols - see preference).
When multiple next-hops have the same metric (be it
specified, or simply the default) then akk these next-hops should
be used in best static route for given prefix, hence be eligable for
installation in RIB.
The value of metric is carried form static/aggregate to other
protocol in process of redistribution, provided that such behaviour
is enabled in configuration of redistributions (table-connection)";
}

leaf preference {
type uint32;
description
"Administrative Distance (preference) of the entry. The
preference defines the order of selection when multiple
sources (protocols, static, etc.) contribute to the same
prefix entry. The lower the preference, the more preferable the
prefix is. When this value is not specified, the preference is
sources (protocols, gRIBI, static, aggregate etc.) contribute to
the same prefix entry. The lower the preference, the more preferable
the route is. When this value is not specified, the preference is
inherited from the default preference of the implementation for
static routes.";
static/aggregate routes.
The preference must not be utilized to specify the order of
selection of the next-hop entry of static route. The value of preference of
next-hop of best static route is used to compare with routes for
the same prefix lerned form other protocols. In case when best
static route has multiple next-hops (due to eqial metric), and
this next-hops has disticnt value of preference, lowest value is
utilized to compare with routes form other protocols.";
}
}

Expand Down
Loading