Bug ID 643777: LTM policies with more than one IP address in TCP address match may fail

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3

Fixed In:
13.1.0, 13.0.1, 12.1.3, 11.6.3

Opened: Feb 08, 2017
Severity: 3-Major
Related AskF5 Article:
K27629542

Symptoms

An LTM policy using a rule that attempts to match based on a list of IP addresses may fail if more than one IP address is used.

Impact

The action configured with the match may not be taken.

Conditions

LTM policy rule with a 'tcp match address' statement that attempts to match against more than one IP address.

Workaround

Use one of the following workarounds: - Use a subnet instead of single IP addresses. - Use a datagroup with the list of IP addresses to match. * Datagroup option available beginning in v13.0.0.

Fix Information

The BIG-IP system now correctly matches several IP addresses in LTM policies.

Behavior Change