Bug ID 754132: A NLRI with a default route information is not propagated on 'clear ip bgp <neighbor router-id> soft out' command

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,

Fixed In:
15.0.0, 14.1.4,

Opened: Dec 26, 2018

Severity: 3-Major


A default route is not propagated in Network Layer Reachability Information (NLRI) by a routing framework on a command: 'clear ip bgp <neighbor router-id> soft out'. -- Enter to imi(Integrated Management Interface) shell. [root@hostname:Active:Standalone] config # imish hostname[0]> -- Issue a command inside imish. is neighbor BGP router-id. hostname[0]>clear ip bgp soft out


A default-route is not propagated in NLRI by 'soft out' request, even with default-originate configured.


-- There is a BIG-IP system with the following routing configuration: imish output: hostname[0]#sh run ! no service password-encryption ! interface lo ! ... <skip other default information, like interfaces.> ! router bgp 1 bgp router-id bgp graceful-restart restart-time 120 neighbor remote-as 1 ! -- There is a default route, which is advertised by this BGP configuration. Here is one way to check it: hostname[0]:sh ip ospf database ... <skip less important info> AS External Link States Link ID ADV Router Age Seq# CkSum Route Tag 273 0x80000002 0x5c4e E2 0 The 'clear ip bgp soft out' command is issued, and there is no NLRI with a default route generated. You can confirm that by running tcpdump and reading what is in the generated Link-state advertisement (LSA), messages or by watching OSPF debug logs. Note: The source from which you gather the default route and advertise it to the neighbors does not matter. It might be the usual BGP route learned from another router, a locally created route, or it might be configured by 'neighbor <neighbor router-id> default-originate'.


There is no specific workaround for 'clear ip bgp <neighbor router-id> soft out' command, but if you want to make routing protocol propagate a NLRI with a default route, you can do either of the following: -- Remove the default route from advertised routes. This workaround is configuration-specific, so there there are no common steps. + If you have default-originate configured for your neighbor, then delete that part of the configuration and re-add it. + If you create a default route as a static route, recreate it. + And so on. The idea is to remove a root of default route generation and then add it back. -- Run a 'soft in' command from your neighbor. If a neighbor you want to propagate a NLRI is a BIG-IP device, or is capable of running this type of command, you can issue a imish command on the neighbor: # neighbor-hostname[0]: clear ip bgp <neighbor router-id> soft in Note: This time, the 'soft in' command requests the NLRIs.

Fix Information

A NLRI with default route information is successfully propagated on 'clear ip bgp <neighbor router-id> soft out' command.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips