From: Donald Sharp <sharpd@cumulusnetworks.com>
Date: Wed, 22 Jul 2015 19:35:37 +0000 (-0700)
Subject: The last BGP peer down reason code "PEER_DOWN_V6ONLY_CHANGE" has no corresponding... 
X-Git-Tag: frr-2.0-rc1~1310
X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=cceb0bfce42425c784ab9371873c5a2eec18d3fd;p=matthieu%2Ffrr.git

The last BGP peer down reason code "PEER_DOWN_V6ONLY_CHANGE" has no corresponding logging/display string defined in "peer_down_str". This will cause incorrect or empty down reason to get logged when the peer is brought down because of interface based v6only config change.
---

diff --git a/bgpd/bgp_fsm.c b/bgpd/bgp_fsm.c
index 9b0595b0e6..6948a6defb 100644
--- a/bgpd/bgp_fsm.c
+++ b/bgpd/bgp_fsm.c
@@ -474,7 +474,8 @@ const char *peer_down_str[] =
   "Capability changed",
   "Passive config change",
   "Multihop config change",
-  "NSF peer closed the session"
+  "NSF peer closed the session",
+  "Intf peering v6only config change"
 };
 
 static int