Symptoms

An iRule which utilized the clientside or serverside command might operate on the incorrect peer flow.

Impact

iRules might utilize information from the wrong peer flow for connection within a clientside or serverside command. Note: The affected clientside or serverside command might not actually park. The issue could be triggered by a different iRule that does park multiple times in the clientside or serverside command.

Conditions

An iRule contains a script that parks multiple times in a clientside or serverside command. Examples of parking commands include "table" and "persist".

Workaround

Avoid using commands that park inside the clientside or serverside command.

Fix Information

None

Behavior Change