Bug ID 680856: IPsec config via REST scripts may require post-definition touch of both policy and traffic selector

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3

Fixed In:
14.0.0, 13.1.1.4, 12.1.3.6

Opened: Aug 30, 2017
Severity: 4-Minor

Symptoms

A new IPsec tunnel may not work after being configured over REST. While the configuration is correct, a log message similar to the following may appear in ipsec.log (IKEv2 example): info tmm[24203]: 017c0000 [0.0] [IKE] [INTERNAL_ERR]: selector index (/Common/Peer_172.16.4.1) does not have corresponding policy

Impact

The newly configured IPsec tunnel does not start.

Conditions

A new IPsec tunnel is configured over REST.

Workaround

The following methods cause the traffic-selector and ipsec-policy to be correctly related to one another: -- Restart tmm. -- Change the configuration, for example the Description field, of both the policy and the traffic selector. This may also be done using REST.

Fix Information

A traffic selector can no longer use a deleted policy by name, and if recreated after deletion, the policy is correctly constructed.

Behavior Change