BGP: Fix warning message when interface has IPv4 address for unnumbered

Ticket: CM-6192
Reviewed By: Donald, Daniel, Vipin
Testing Done:

In the presence of an IPv4 address that is not a /30 or /31 and the user
is trying to use BGP unnumbered, a warning message is printed which
seems confusing to the user. Fixing the warning message to indicate that
its only a v4 session isn't coming up makes it clearer.

Signed-off-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
Acked-by: Donald Sharp <sharpd@cumulusnetworks.com>
Acked-by: Daniel Walton <dwalton@cumulusnetworks.com>
Acked-by: Vipin Kumar <vipin@cumulusnetworks.com>

diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c
index 3d6553cac27663e89fffe1a6b96f1a4aa6fd3f4f..d0ebbe88e02d9f51d223779ab9aa491eb4bd7134 100644 (file)
--- a/bgpd/bgpd.c
+++ b/bgpd/bgpd.c
@@ -1218,7 +1218,7 @@ bgp_peer_conf_if_to_su_update (struct peer *peer)
                  return;
                }
              else
-               zlog_warn("%s neighbor interface with IPv4 numbered links used without /30 or /31",
+               zlog_warn("%s: IPv4 interface address is not /30 or /31, v4 session not started",
                          peer->conf_if);
            }