Forum Discussion
dennypayne
Jun 17, 2008Employee
From the 9.3 release notes:
Timeout values for SNAT pool members (CR53064)
When adding a member to a SNAT pool, the system no longer removes the timeout values that are currently set for the other members of the SNAT pool. Now, the system leaves the timeout values as you set them for the pool members.
This could apply as well, depending on the PVA settings:
PVA and timeout values (CR69775, CR70547)
In previous releases, the FastL4 profile did not restrict a maximum timeout value; however, the Packet Velocity® ASIC (PVA) daemon could not handle timeout values over certain amounts. (The exact timeout value depends on the PVA version.) When the PVA timeout value was exceeded, idle connections could close prematurely. With this release, if the maximum timeout is exceeded, the system demotes the PVA to Assisted mode, which allows the system to control the timeout value.
And if you are using OneConnect this might apply:
Persistent HTTP connections and TMM (CR71998)
Now, the system correctly handles persistent HTTP connections on a OneConnect™ virtual server using secure network address translation (SNAT).
Anyway, definitely worth getting onto the 9.3 maintenance branch.
Denny