Last Modified: Jun 07, 2022
See more info
Known Affected Versions:
16.1.0, 18.104.22.168, 22.214.171.124, 15.1.5, 15.1.4, 126.96.36.199, 15.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.4
17.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Jul 05, 2021
A fix for ID 945265 (https://cdn.f5.com/product/bugtracker/ID945265.html) introduced strict checking of a peer-id. This check might be not desired in some configurations.
BIG-IP will not pass the NLRIs between two eBGP peers. The following message can be seen in debug logs: 172.20.10.18-Outgoing [RIB] Announce Check: 0.0.0.0/0 Route Remote Router-ID is same as Remote Router-ID
EBGP peering with two routers in the same autonomous system, configured with the same peer-id.
Change peer-ids to be unique on eBGP peers.
New, neighbor-specific, af-specific configuration option is provided to allow routes to be passed to external peers sharing the same router-id. The check is done on egress, so the configuration should be changed towards the peer that is supposed to receive a route. router bgp 100 bgp graceful-restart restart-time 120 neighbor as200 peer-group neighbor as200 remote-as 200 neighbor as200 disable-peerid-check neighbor 172.20.8.16 peer-group as200 neighbor 172.20.8.16 disable-peerid-check neighbor 172.20.10.18 peer-group as200 neighbor 172.20.10.18 disable-peerid-check ! address-family ipv6 neighbor as200 activate neighbor as200 disable-peerid-check neighbor 172.20.8.16 activate neighbor 172.20.8.16 disable-peerid-check neighbor 172.20.10.18 activate neighbor 172.20.10.18 disable-peerid-check exit-address-family When configured on a single neighbor it will cause session to be re-established. When configured on a peer-group a manual session restart is required for changes to take effect.