summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2018-05-02 16:50:37 -0400
committerDonald Sharp <sharpd@cumulusnetworks.com>2018-05-02 16:50:37 -0400
commitf03098f979fe084ebc89b7ca8cc0e40b0a8f061d (patch)
treeca940b7bb6fae903b991e078f5e278563addc4ae
parentd71b0564c29fdd21c0461c04e616f3f0c82964e2 (diff)
zebra: Add a few more breadcrumbs
re->status and re->flags both influence our decision states for rib processing. Yet it's impossible to see them. Add a tiny bit of code to allow us to look at them when things are not behaving like we would expect. Additionally dump the nexthop->flags at the same time for the same reasons. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
-rw-r--r--zebra/zebra_vty.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/zebra/zebra_vty.c b/zebra/zebra_vty.c
index 16aece9747..2ae9ac5082 100644
--- a/zebra/zebra_vty.c
+++ b/zebra/zebra_vty.c
@@ -1215,6 +1215,10 @@ static void vty_show_ip_route(struct vty *vty, struct route_node *rn,
json_object_int_add(json_route, "metric", re->metric);
}
+ json_object_int_add(json_route, "internalStatus",
+ re->status);
+ json_object_int_add(json_route, "internalFlags",
+ re->flags);
if (uptime < ONE_DAY_SECOND)
sprintf(buf, "%02d:%02d:%02d", tm->tm_hour, tm->tm_min,
tm->tm_sec);
@@ -1231,6 +1235,9 @@ static void vty_show_ip_route(struct vty *vty, struct route_node *rn,
for (ALL_NEXTHOPS(re->ng, nexthop)) {
json_nexthop = json_object_new_object();
+ json_object_int_add(json_nexthop, "flags",
+ nexthop->flags);
+
if (CHECK_FLAG(nexthop->flags, NEXTHOP_FLAG_DUPLICATE))
json_object_boolean_true_add(json_nexthop,
"duplicate");