Bug ID 555818: Bait failure alerts do not give details of the cause of failure

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP FPS(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

Fixed In:
12.1.0, 11.6.1

Opened: Nov 02, 2015
Severity: 3-Major

Symptoms

Bait fail alert details are always the same.

Impact

Difficult to find cause of failures due to poor granularity of error alert

Conditions

Honeypot mechanism failed due to http error, clientside error, timeout, etc.

Workaround

None

Fix Information

The following details were added to the Bait Failure alert: bf_malformed : Malformed bait response bf_jserror : Bait checks errored bf_timeout : Bait request timed out bf_<status_code> : Bait response was not 200 OK. Eg bf_404 bf_unknown : Other failure

Behavior Change