Replies: 2 comments
-
|
c4c3989cc2da# show running-config Current configuration: |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried http://docs.frrouting.org/en/latest/bgp.html#clicmd-bgp-update-delay-MAX-DELAY? |
Beta Was this translation helpful? Give feedback.
-
c4c3989cc2da# show version
FRRouting 9.1-dev-my-manual-build (c4c3989cc2da) on Linux(5.4.0-166-generic).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
'--prefix=/usr' '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr' '--sysconfdir=/etc/frr' '--enable-sharpd' '--enable-multipath=64' '--enable-user=frr' '--enable-group=frr' '--enable-config-rollbacks' '--enable-vty-group=frrvty' '--enable-snmp=agentx' '--enable-scripting' '--with-pkg-extra-version=-my-manual-build'
c4c3989cc2da#
Related:
#11337
(closed)
R1===R2
Between two DUTs where e-bgp was configured, I configured advertisement-interval as 30 in both the devices.
Prefixes are appearing almost immediately in R2 (show ip bgp) after I added the network commands in R1.
'routeadv timer expired' message is seen in R2 as soon as I add the network in R1 (within 1-2 seconds)
2023-11-22 08:25:19.518 [DEBG] bgpd: [P3D3N-3277A] 172.18.0.2 [FSM] Timer (routeadv timer expire)Note that this is not only for the 'first' advertisement.
i.e.,
add 11.11.11.0/24 network in R1, R2 immediately receives it
add 12.12.12.0/24 network in R1 (within 5 sec interval of adding the first prefix 11.11.11.0/24), R2 immediately receives it
However, this issue is not seen when I set a higher value for advertisement-interval, say, 300 sec (5 min). in that case, after I add the network commands in R1, it is appearing in R2 almost after 300 sec.
There is inconsistency in lower values of advertisement-interval
(NOTE: when I withdraw the routes in R1 using 'no network', it is getting withdrawn in R2 immediately, I think it's the expected behavior)
Please let me know
Thanks
Beta Was this translation helpful? Give feedback.
All reactions