Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.4, 184.108.40.206, 13.1.5, 220.127.116.11, 14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.0.1, 220.127.116.11
Opened: Jan 30, 2018
When One-Connect profile is created or modified in TMSH and help is invoked by typing the '?' character, description for the limit-type option is missing.
Command line help missing.
A One-Connect profile is created or modified in TMSH.
TMSH help is similar to the following: limit-type: Connection limits with OneConnect are different from straight TCP connection limits. Three options are supported: 'none' (the default), 'idle', and 'strict'. -- When the limit is "none", simultaneous in-flight requests and responses over TCP connections to a pool member are counted toward the limit. There may be more TCP connections open to support new requests than there can be simultaneous in-flight requests and responses. This is particularly true when SNAT pools and narrow source address masks are used. -- When the limit is 'idle', idle connections are dropped as the TCP connection limit is reached. For short intervals, during the overlap of the idle connection being dropped and the new connection being established, the TCP connection limit may be exceeded. -- When the limit is 'strict', the TCP connection limit is honored with no exceptions. This means that idle connections prevent new TCP connections from being made until they expire, even if they might otherwise be reused. This is not a recommended configuration except in very special cases with short expiration timeouts.
Missing help in TMSH added.