bgpd: debug protect a log message

With the addition of RA being turned on by default.
Spewing this error message when unable to connect
doesn't make much sense anymore.

Ticket: CM-10494
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Reviewed-by: Don Slice <dslice@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Radhika Mahankali <radhika@cumulusnetworks.com>

diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c
index adcfd66d4557d9db7b5e635932f68b697e63f461..b6ca70b0d2ee695798569ce824faec24ff7b4f8c 100644 (file)
--- a/bgpd/bgpd.c
+++ b/bgpd/bgpd.c
@@ -1290,8 +1290,9 @@ bgp_peer_conf_if_to_su_update_v4 (struct peer *peer, struct interface *ifp)
               return 1;
             }
           else
-            zlog_warn("%s: IPv4 interface address is not /30 or /31, v4 session not started",
-                      peer->conf_if);
+            if (bgp_debug_neighbor_events(peer))
+              zlog_debug("%s: IPv4 interface address is not /30 or /31, v4 session not started",
+                         peer->conf_if);
         }
     }