From fd8d42099953f4b589f08d5ef1b5890c278f51be Mon Sep 17 00:00:00 2001 From: rathorepo Date: Thu, 18 Apr 2024 09:53:36 +0000 Subject: [PATCH] bgpd : Ensure logging for dynamic neighbor listen limit reached Dynamic neighbors exceeding the listen limit were rejected without appropriate logging. Previously, only rejection logs were generated, leaving users unaware of when the limit being reached. Adding a log message for when the listen limit is reached Signed-off-by: Pooja Rathore --- bgpd/bgpd.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c index d98df754ef..dbf8c3121d 100644 --- a/bgpd/bgpd.c +++ b/bgpd/bgpd.c @@ -4403,6 +4403,11 @@ struct peer *peer_lookup_dynamic_neighbor(struct bgp *bgp, union sockunion *su) zlog_debug("%s Dynamic Neighbor added, group %s count %d", peer->host, group->name, dncount); + if (dncount == gbgp->dynamic_neighbors_limit) { + zlog_warn("Dynamic Neighbor %s added as last connection. Peer-group %s reached maximum listen limit %d", + peer->host, group->name, + gbgp->dynamic_neighbors_limit); + } return peer; }