Bobcares

NFS TCP Keepalive: Prevent Connection Drops

by | May 19, 2024

Learn how to enable NFS TCP Keepalive for stable connections. Our NFS Support team is here to help you with your questions and concerns.

NFS TCP Keepalive: Prevent Connection Drops

NFS keepalive helps us maintain and monitor NFS connections. It periodically transmits messages on a connected socket to keep the connection active and operational.

NFS TCP Keepalive: Prevent Connection Drops

Today, we will look closer at the workings of NFS keepalive, its features, and how to enable and configure it on our system.

NFS keepalive helps maintain connections by periodically sending keepalive probe packets. These packets, which contain no data but have enabled ACK flags, are sent once the keepalive timer expires.

If the peer responds, it confirms that the connection is still active. This mechanism helps detect inactive connections and ensures the stability of NFS servers.

Here are some of the features of NFS Keepalive:

  • Periodic Transmission: Sends regular messages to maintain NFS connections.
  • Failure Detection: Identifies when an NFS server stops responding.
  • Connection Re-establishment: Attempts to re-establish connections if they are found to be inactive.
  • Integration with Keepalived: Can be used to detect NFS server failures and switch to a backup node if necessary.

How to enable TCP Keepalive for NFS

  1. Before making any changes, check the current status of the TCP keepalive parameters:

    sysctl -a | grep tcp_keepalive

  2. Then, modify the parameter values. For example, to set the keepalive time to 600 seconds, the number of probes to 4, and the interval between probes to 25 seconds, use these commands:

    sysctl -w net.ipv4.tcp_keepalive_time=600
    sysctl -w net.ipv4.tcp_keepalive_probes=4
    sysctl -w net.ipv4.tcp_keepalive_intvl=25

    These commands configure the TCP keepalive mechanism in the Linux kernel.

  3. Now, add the commands to a startup script or modify the `/etc/sysctl.conf` file to ensure these changes persist across reboots. In other words, add these lines to `/etc/sysctl.conf`:

    net.ipv4.tcp_keepalive_time=600
    net.ipv4.tcp_keepalive_probes=4
    net.ipv4.tcp_keepalive_intvl=25

  4. After modifying the `/etc/sysctl.conf` file, apply the changes by running:

    sysctl -p

NFS keepalive is not enabled by default, and TCP keepalive parameters are set to their default values. We can maintain reliable NFS connections and quickly detect server failures by enabling and fine-tuning these parameters.

Proper configuration of NFS servers, along with the use of Keepalived for failover management, leads to a stable and dependable NFS environment.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to enable NFS TCP Keepalive for stable connections.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF