Bug ID 723833: IPsec related routing changes can misfire, like changing tunnel mode to interface mode

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,, 15.0.0, 15.0.1,,,,

Fixed In:

Opened: Jun 11, 2018
Severity: 4-Minor


IPsec config changes that rely upon interface mode tunnels, which are driven by routes with associated tunnel VLANs, can sometimes fail to pass traffic after a config change altering routes, or altering the number of tunnels involved.


An IPsec tunnel outage may occur before a system restart, which looks like absence of proper routing config, but which is due to inconsistent update when changes affect routing used by IPsec tunnels in interface mode. In some cases, a tmm core can occur which interrupts service briefly until restarted.


- Changing tunnel mode to interface mode. - Adding or removing routes for interface mode IPsec tunnels. - Deleting an IPsec tunnel object.


Typically saving before bigstart restart gets routing config related to IPsec back into working order.

Fix Information

Tunnel and nexthop dependencies are now managed more exactly for routing changes that affect IPsec.

Behavior Change