Bug ID 473527: IPsec interop problem when using AES-GCM.

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: Jul 29, 2014

Severity: 2-Critical

Symptoms

BIG-IP AES-GCM negotiation through IKEv2 does not accept the case of no integrity algorithm. This can happen with the tunnel configured to use AES-GCM.

Impact

The IPsec tunnel will not be established.

Conditions

When configuring IPsec tunnel to use AES-GCM to inter-operate between two BIG-IPs of version 11.6 and 12.0, or configuring IPsec tunnel on a BIG-IP of 11.6 to inter-operate with another vendor using AES-GCM.

Workaround

For BIG-IP only, ensure both sides of the tunnel are the same release level.

Fix Information

Do not include integrity algorithm for AES-GCM.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips