Bug ID 1709689: BGP 'no bgp default ipv4-unicast' might lead to config load problems and crashes.

Last Modified: Oct 29, 2025

Affected Product(s):
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2

Fixed In:
17.5.1.3

Opened: Oct 25, 2024

Severity: 4-Minor

Symptoms

BGP 'no bgp default ipv4-unicast' might lead to config load problems and/or BGPd daemon crashes.

Impact

Configuration cannot be loaded. BGPd might experience a crash/core.

Conditions

'no bgp default ipv4-unicast' statement is used in BGP configuration.

Workaround

None

Fix Information

Alter the config to get rid of 'no bgp default ipv4-unicast' statement. Without this statement configured neighbors will by default be enabled for IPv4, but they can later be disabled with 'no activate' statement: router bgp 1111 neighbor 10.12.12.12 remote-as 2222 (optionally) no neighbor 10.12.12.12 activate

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips