Bug ID 440154: When IKEv2 is in use, user can only associate one Traffic Selector object with the IKE Peer object

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5

Opened: Dec 09, 2013

Severity: 3-Major

Symptoms

Only one Traffic Selector can be associate with one IKE Peer when IKEv2 is in use.

Impact

User can only associate one Traffic Selector per IKE Peer

Conditions

When IKEv2 is selected to negotiate IPsec Tunnel

Workaround

None

Fix Information

User can associate multiple Traffic Selector MCP objects with one IKE Peer object

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips