The RFC 1122 sets down a method of checking the availability of TCP connections, called TCP keepalive. An inactive transmitter queries the receive status from the remote station. If the TCP session to the remote site is available, then the remote responds with its receive status. If the TCP session to the remote site is not available, then the query is repeated for as long as it takes for the remote to respond with its receive status (after which a longer interval comes into play). As long as the basic connection functions, but the TCP session to the remote station is not available, then the remote station sends an RST packet which triggers the establishment of the TCP session by the requesting application.
Note: The setting "active" is recommended for server applications.
- SNMP ID:
- 2.52.2.3.14
- Console path:
- Setup > COM-Ports > COM-Port-Server > Network-Settings
- Possible values:
- Inactive
- TCP keepalive is not used.
- Active
- TCP keepalive is active; only RST packets cause the disconnection of TCP sessions.
- Proactive
- TCP keepalive is active, but the request for the receive status from the remote site is only repeated for the number of times defined under "TCP retry count". If this number of requests expires without a response with the receive status, then the TCP sessions is classified as "not available" and the application is informed. If an RST packet is received during the wait time, the TCP session will be disconnected prematurely.
- Default:
- Inactive
