summaryrefslogtreecommitdiffstats
path: root/bfdd
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2019-02-14 05:24:05 +0100
committerDonald Sharp <sharpd@cumulusnetworks.com>2019-02-14 05:24:05 +0100
commita244e59954caa0f51b0496adfd6e247cd90ffe6f (patch)
treef96b6a3bd1a6dab4d9969b36913c3fd19438733e /bfdd
parentbfdd: Add some code so we can compile from w/ in the bfdd dir (diff)
downloadfrr-a244e59954caa0f51b0496adfd6e247cd90ffe6f.tar.xz
frr-a244e59954caa0f51b0496adfd6e247cd90ffe6f.zip
bfdd: Add `show debugging [bfd]` command
This will prevent vtysh from displaying `command imcomplete` for a `show debugging` issued and we are running this bfd daemon. A quick look showed me that there was not really the ability to turn on/off debugging like other daemons. I imagine future work can be focused here. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'bfdd')
-rw-r--r--bfdd/bfdd_vty.c13
1 files changed, 13 insertions, 0 deletions
diff --git a/bfdd/bfdd_vty.c b/bfdd/bfdd_vty.c
index 8f8fff6b1..3476e1621 100644
--- a/bfdd/bfdd_vty.c
+++ b/bfdd/bfdd_vty.c
@@ -968,6 +968,18 @@ static void _bfdd_peer_write_config(struct hash_backet *hb, void *arg)
vty_out(vty, " !\n");
}
+DEFUN_NOSH(show_debugging_bfd,
+ show_debugging_bfd_cmd,
+ "show debugging [bfd]",
+ SHOW_STR
+ DEBUG_STR
+ "BFD daemon\n")
+{
+ vty_out(vty, "BFD debugging status:\n");
+
+ return CMD_SUCCESS;
+}
+
static int bfdd_peer_write_config(struct vty *vty)
{
bfd_id_iterate(_bfdd_peer_write_config, vty);
@@ -993,6 +1005,7 @@ void bfdd_vty_init(void)
install_element(ENABLE_NODE, &bfd_show_peers_cmd);
install_element(ENABLE_NODE, &bfd_show_peer_cmd);
install_element(CONFIG_NODE, &bfd_enter_cmd);
+ install_element(ENABLE_NODE, &show_debugging_bfd_cmd);
/* Install BFD node and commands. */
install_node(&bfd_node, bfdd_write_config);