a477dbb175
Why I did it Upgrade FRR to version 8.2.2. Build libyang2 required by FRR. How I did it Update FRR version and tag. How to verify it Following tests were performed on sonic-vs: BGP docker status check BGP configuration and session establishment Route redistribution and ping Issued show commands to check the bgp neighbor and routes Checked app-db to ensure bgp routes are installed with correct interface and nexthop. Create VRF and check FRR knows the VRF Check VRF routes are installed in app-db with correct Vrf name and next-hop Establish BGP Evpn session and check if Evpn routes (multicast, mac, prefix) are exchanged and installed correctly in app-db.
26 lines
682 B
Diff
26 lines
682 B
Diff
From 15274a197e4d3b7ac0f11ca63a5274f1168739f5 Mon Sep 17 00:00:00 2001
|
|
From: Pavel Shirshov <pavelsh@microsoft.com>
|
|
Date: Mon, 16 Nov 2020 18:11:47 -0800
|
|
Subject: [PATCH 2/8] Reduce severity of 'Vty connected from' message
|
|
|
|
---
|
|
lib/vty.c | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
diff --git a/lib/vty.c b/lib/vty.c
|
|
index 8eaf13619..7edeb5538 100644
|
|
--- a/lib/vty.c
|
|
+++ b/lib/vty.c
|
|
@@ -1814,7 +1814,7 @@ static int vty_accept(struct thread *thread)
|
|
zlog_info("can't set sockopt to vty_sock : %s",
|
|
safe_strerror(errno));
|
|
|
|
- zlog_info("Vty connection from %pSU", &su);
|
|
+ zlog_debug("Vty connection from %pSU", &su);
|
|
|
|
vty_create(vty_sock, &su);
|
|
|
|
--
|
|
2.12.2
|
|
|