StarQuest: keeping data in motion

 

StarQuest Technical Documents

SQDR & SQDR Plus: TCP KeepAlive Settings

Last Update: 12 November 2021
Product: SQDR Plus
Version: 4.50 and later
Article ID: SQV00PL061

Abstract

In order for SQDR to react quickly to loss of connectivity to a source or destination system, or between tier 2 and 3 in a split-tier environment, we recommend examining and adjusting the TCP KeepAlive parameters. These recommendations apply to both Tier 2 and Tier 3 systems in a split-tier environment.

Solution

The following are our recommendations for Windows.

  1. Use regedit and open the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
  2. Examine the following values, noting the original value(s). If there are registries that don't exist, these will be created later by running the keepAliveParams.ps1 PowerShell script
    • KeepAliveInterval: REG_DWORD = Interval between KeepAlive packets when one is dropped.
    • KeepAliveTime: REG_DWORD = How often TCP attempts to verify the connection.
    • TcpMaxDataRetransmissions: REG_DWORD = Number of retries TCP does for a packet before giving up.

  3. Download the keepAliveParams.ps1 onto the Windows machine
  4. Open a PowerShell Window as an administrator
  5. Relocate to the directory where the keepAliveParams.ps1 script resides.
  6. Run the script by running ".\keepAliveParams.ps1"
  7. Return to the regedit window and refresh the screen. Ensure that the registry entries have been created and their corresponding values set.
  8. Reboot the system for the changes to take effect.

Note: Modifying the KeepAlive parameter settings may affect the operation of other applications on the computer.

For more information, see Configuring TCP KeepAlive Parameters.

DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.