Forum Discussion
CirrusSource_Addr Persistence Problems
Shadow This article has a nice short description of the checkboxes as well as the gotchas on them. I believe based on what you stated your issue was is that the match across pools was the problem checkbox. Without being able to troubleshoot it myself I cannot say with absolute certainty that the match across pools was the cause of the odd behavior.
MVPShadow What was the reasoning behind enabling those 4 settings? Do you have an iRule that forces traffic to a particular node and port or is this all handled by the default load balancing of a virtual server to the associated pool and pool members? If you do not have a need to balance across pools then I would disable those settings.
CirrusHonestly, there was no real good reason. I thought I knew what the settings were supposed to do and thought I was being proactive for some eventuality. That was my fault. I've since disabled those settings. However, end user confidence has eroded and I have to find out if those settings are truly what is responsible for the behavior we've observed.
I did not create an iRule. We are using a default lb profile.
- Paulius
Shadow This article has a nice short description of the checkboxes as well as the gotchas on them. I believe based on what you stated your issue was is that the match across pools was the problem checkbox. Without being able to troubleshoot it myself I cannot say with absolute certainty that the match across pools was the cause of the odd behavior.
