F5 Sites
  • F5.com
  • LearnF5
  • NGINX
  • MyF5
  • Partner Central
Contact
  • Under Attack?
  • F5 Support
  • DevCentral Support
  • F5 Sales
  • NGINX Sales
  • F5 Professional Services
Skip to contentBrand Logo
Forums
CrowdSRC
Articles
Groups
EventsSuggestionsHow Do I...?
RegisterSign In
  1. DevCentral
  2. CrowdSRC
  3. CodeShare

Single Node Persistence

Problem this snippet solves: A really slick & reliable way to stick to one and only one server in a pool. Requirement: Direct traffic to only a single node in a pool at a time. Initially, traffic ...
Published Mar 18, 2015
Version 1.0
application delivery
devops
iRules
persistence
CodeCentral_194's avatar
CodeCentral_194
Icon for Cirrus rankCirrus
Joined May 05, 2019
View Profile
CodeCentral_194's avatar
CodeCentral_194
Icon for Cirrus rankCirrus
Joined May 05, 2019
View Profile
Dominique_Peti1's avatar
Dominique_Peti1
Icon for Nimbostratus rankNimbostratus
Mar 13, 2019

Could someone be more explicit about how to configure "Destination address affinity" like suggested by Stephan Manthey? It is not clear to me if one should

  • just replace
    persist uie 1
    by
    persist dest_addr
    in the iRule code example above?
  • or configure "Destination address affinity" persistence on the Default Persistence Profile of the virtual server?
  • or still something else?

Also,in a case where the connections are in principle permanent (e.g. to a database master node):

  • should the timeout be unset (Indefinite)?
  • In case a server node is temporarily inaccessible or administratively forced offline, the TCP connections to that node might survive, but during that time new connections could be established with other nodes thus resulting, when the node is accessible again, in a state where there are active connections to more than one node. How can it be avoided ? e.g how to cut all connections to other nodes when a new server node is chosen by the persistence?

  • would a custom destination affinity persistence with a CARP Hash Algorithm work like for source address persistence, i.e. it would always select the same server node when all nodes are available, even for the very first connection (e.g after a reboot)? cf. How Carp algorithm with source address persistence works?

Thanks in advance for your explanations!

ABOUT DEVCENTRAL

DevCentral NewsTechnical ForumTechnical ArticlesTechnical CrowdSRCCommunity GuidelinesDevCentral EULAGet a Developer Lab LicenseBecome a DevCentral MVP

RESOURCES

Product DocumentationWhite PapersGlossaryCustomer StoriesWebinarsFree Online CoursesF5 CertificationLearnF5 Training

SUPPORT

Manage SubscriptionsProfessional ServicesProfessional ServicesCreate a Service RequestSoftware DownloadsSupport Portal

PARTNERS

Find a Reseller PartnerTechnology AlliancesBecome an F5 PartnerLogin to Partner Central

F5 logo©2024 F5, Inc. All rights reserved.
TrademarksPoliciesPrivacyCalifornia PrivacyDo Not Sell My Personal Information