|
BGPD crashes are observed when FortiGate receives a large number of routes from its EBGP neighbours (ISPs, etc)
The issue is only observed if the 'route-map-in' filters are applied in the BGP neighbour config. 'Route-map-out' configuration does not generate this crash
To identify the issue, check the crashlogs and look for the following output
diagnose debug crashlog read
7805: 2025-01-22 09:39:14 <08069> fortidev 6.0.2.0008
7806: 2025-01-22 09:39:52 <08100> firmware FortiGate-3201F v7.4.5,build2702b2702,240916 (GA.M) (Release)
7807: 2025-01-22 09:39:52 <08100> application bgpd
7808: 2025-01-22 09:39:52 <08100> *** signal 11 (Segmentation fault) received ***
7809: 2025-01-22 09:39:52 <08100> Register dump:
The output above is only a portion of the BGPD crash extracted from the crash logs. To confirm if it matches the issue, collect the complete BGPD crash log output and submit it to a support ticket.
Additionally, collect the below output:
get router info bgp summary
get router info bgp neighbor
diagnose ip router command show-vrf root show run router bgp
This is a known issue and reported under the engineering issue ID 1119119. A fix for this issue has already been released in v7.2.11, v7.4.8, and v7.6.3
To fix 1119119: The inadvertent behavior observed in BGPD due to erroneous memory freeing when applying route-maps. This can be verified from the FortiOS firmware release notes:
Resolved issues 7.6.3
Resolved issues 7.4.8
Resolved issues 7.2.11
'local-as-no-prepend' may be tried as a workaround under the BGP neighbor config.
config router bgp
config neighbor
edit <neighbor ip>
set local-as-no-prepend enable
next
end
end
Another possible workaround is to enable prefix-list-in instead of the route-map-in: Prefix lists
Related article:
Troubleshooting Tip: How to identify and fix memory leak Issues caused by BGP daemon on the FortiGat...
|
