Bug ID 660196: Sys connection behavior change

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Apr 24, 2017
Severity: 3-Major

Symptoms

tmm/mcpd might restart when retrieving a large number of flows in response to running the command 'show sys connection' without any connection specifiers.

Impact

Possible disruption of traffic while tmm/mcps restarts.

Conditions

-- Execution of command: show sys connection. -- Large number of flows.

Workaround

None.

Fix Information

This issue is fixed with the addition of the keyword: max-result-limit. In previous releases, running the command 'show sys connection' without any connection specifiers returned all current active flows/connections, irrespective of the number of connections. With the new default behavior, the system limits the results to the first 1000 currently active flows/connections. To change this number of results returned, you can set the new keyword: max-result-limit. If there is no 'max-result-limit' specified, the system uses the default value. You can also specify 'infinite' to return all results (the previous behavior); however, you might encounter tmm/mcpd crashes depending on platform and number of active flows/connections. The 'max-result-limit' keyword may be used along with other connection specifiers. In addition, in previous releases, the system posted the following confirmation question: Really display all connections? Now, this is the confirmation question: Really display x connections? (where x is either the default value 1000 or user-specified value). Examples: show sys connection max-result-limit 7500 show sys connection max-result-limit 300 cs-client-addr 10.10.62.64

Behavior Change

In previous releases, running the command 'show sys connection' without any connection specifiers returned all current active flows/connections, irrespective of the number of connections. With the new default behavior, the system limits the results to the first 1000 currently active flows/connections. To change this number of results returned, you can set the new keyword: max-result-limit. If there is no 'max-result-limit' specified, the system uses the default value. You can also specify 'infinite' to return all results (the previous behavior); however, you might encounter tmm/mcpd crashes depending on platform and number of active flows/connections. The 'max-result-limit' keyword may be used along with other connection specifiers. In addition, in previous releases, the system posted the following confirmation question: Really display all connections? Now, this is the confirmation question: Really display x connections? (where x is either the default value 1000 or user-specified value). Examples: show sys connection max-result-limit 7500 show sys connection max-result-limit 300 cs-client-addr 10.10.62.64