Routing

20.4R3-S3.4

The problem started with version 19

Good afternoon When the peer falls, the route does not change, that is, it also remains active and, accordingly, is not available.

In the example below, the session has been lying for 16 minutes, and the route is present in the table. To correct the situation (that is, so that the route with the inactive nexthop disappears from the table), you have to deactivate the peer in the configuration and then activate, and only after that the inactive route leaves the table. What could be the problem?

> show bgp summary

46.61.215.233 12389 2435870 15014 0 0 4d 18:21:08 Establ

inet.0: 606679/808958/807813/1145

83.102.160.57 3216 905752 14939 0 1 16:15 Idle

show route 188.190.159.99

inet.0: 812964 destinations, 2424195 routes (812265 active, 0 holddown, 43216 hidden)

+ = Active Route, - = Last Active, * = Both

188.190.156.0/22 *[BGP/170] 3d 19:49:49, localpref 120

AS path: 3216 60764 56407 I, validation-state: unverified

> to 83.102.160.57 via xe-0/1/1.0

[BGP/170] 1d 15:10:25, localpref 120

AS path: 12389 20764 60764 56407 I, validation-state: unverified

> to 46.61.215.233 via xe-0/1/3.0

------------------------------
Nikolai Ermakovich
------------------------------

Might be either a received route from another iBGP peer, or some longlived gracefulrestart session ?

Some

show bgp neigb 83.102.160.57 | match options

while the sessions is established, and some

show route 188.190.159.99 extensive

while the peer is down, would be useful.