Bug ID 930393: IPsec tunnel does not start after an upgrade, first configuration, or reconfiguration

Last Modified: May 29, 2024

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

Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 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, 17.0.0, 17.0.0.1, 17.0.0.2

Fixed In:
17.1.0, 16.1.4, 15.1.10

Opened: Jul 23, 2020

Severity: 3-Major

Symptoms

-- IPsec tunnel does not start. -- Remote IPsec networks unavailable.

Impact

IPsec tunnel is down permanently.

Conditions

-- Using IKEv1 and one of the following: + Performing an upgrade. + IPsec tunnel reconfiguration generally involving a change to, or addition of, a traffic-selector.

Workaround

-- Reconfigure or delete and re-create the traffic selectors associated with the IPsec tunnel that does not start. Special Notes: -- This occurs rarely and does not happen spontaneously, without intentional changes (reconfiguration or upgrade). -- A BIG-IP reboot or a restart of tmipsecd does not resolve this condition. -- This symptom might also occur due to a genuine misconfiguration. -- After major version upgrades, default ciphers can change, double-check the encryption and authentication ciphers for the tunnel.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips