Bug ID 677322: PCP Inbound connections logging is not supported

Last Modified: Aug 05, 2020

Bug Tracker

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

Known Affected Versions:
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, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Fixed In:
14.1.0

Opened: Aug 07, 2017
Severity: 3-Major

Symptoms

PCP inbound connections logs are not generated even if logging is enabled under NAT Policy and LTM.

Impact

Logs are not generated.

Conditions

-- Configure PCP inbound in AFM Source translation object and attach it to a NAT Policy. -- Configure logging in NAT Policy.

Workaround

None.

Fix Information

The default global-network profile is now configured to have inbound session logging. An auxiliary change prevents memory leaks containing 'tm_opaque' and 'fw_nat_connflow_opaque' objects.

Behavior Change