Last Modified: Apr 10, 2019
See more info
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, 11.6.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 11.6.4
Opened: Nov 12, 2014
Related AskF5 Article: K13744192
When an iRule throws an error, the default is to abort the connection. When the error occurs in the CLIENT_ACCEPTED event and the Virtual Server is using source-address-translation type LSN, the source address translation may be executed before the connection is aborted. The address translation may succeed even though the connection fails.
There are a number of possible side effects depending on configuration: - Any LSN commands in the failing iRule may be ignored. - LSN Pool translation statistics may be incremented. - A log message indicating a successful translation may be output. - Multiple RSTs may be sent for the aborted connection. - PBA port blocks may be allocated. - Persistence mapping entries may be created. - Inbound mapping entries may be created.
A Virtual Server is using source-address-translation type LSN and has an iRule that does not handle errors.
Use the Tcl catch command to handle Tcl errors. When an error occurs, use the LSN::disable command to prevent the translation.
When an unhandled error occurs in a iRule, the connection will be aborted withoot executing LSN address translation.