Pool round Robin not working with standard virtual server
I have a standard HTTPS virtual server configured with two nodes in the pool. There is no persistence setting enabled and the load balancing method is round robin. For some reason, after I browse to the site and establish a connection with a backend server in the pool, all my future requests go to the same server and it behaves in a way that indicates some persistence is enabled. For example, when I refresh my browser, open the site in a new browser, and open the site in an incognito browser, all my requests keep going to the same node. You can see below that I tried this multiple times and kept getting connected to one server and the number of connections on that server was increasing. According to my research, because there is no persistence profile setting, the load balancing method is round robin, and both servers are available and able to accept traffic, every time I refresh or open the site in a new tab or browser, I should be randomly assigned to a server for that connection via round robin load balancing. But this is not what I observe. Is there a reason that my virtual servers are showing persistence by default? Any ideas? Here are some images of my config:
F5 Not sending traffic to Pool Members
Hello guys, I have an issue with our F5 devices, we have 2 devices in a cluster in an Active and standby state. we noticed the issue started about two weeks ago, the active F5 just stops sending traffic to the pool member behind the VS, we tried some couple of troubleshooting whenever this occurs we check the var/log/ltm and var/log/monitor logs for the pool affected but we cant see any stating a failure. we changed the health monitor and it is still the same. we can confirm that it is not the network because the other pools are working fine and checkup was done on the affected server to confirm all services and functions are working as should. Even after deleting and adding the pool member back to the pool, F5 doesn't send traffic to it. what i noticed is the statistics page show bits in without any bits outs also for packets Please what can cause this as it is an intermittent issue that occurs almost daily. we have to failover to the secondary device before F5 starts sending traffic out to pool member, this is a production issue as application server stops working(stops recieving traffic) until an administrator is able to do this.
Redirect to pool member based on URI with persistence
We are implementing Kronos 8 with SSL offloading on our LTM. The SSL offload options in Kronos forces all traffic through the LTM so our Kronos admin can no longer hit the application directly on the individual servers. To accomplish this I need to direct traffic directly to the pool member based on URI. I also need to append /wfc/logon to all URIs. I have built an iRule based on examples I have found here, but it doesn't work correctly. It lands on the initial logon page correctly, but after the logon doesn't persist to the pool member. Process I am trying to accomplish: http://kronos.xxx.edu/ap1 -> https://kronos.xxx.edu/wfc/logon on pool member 1 http://kronos.xxx.edu/ap2 -> https://kronos.xxx.edu/wfc/logon on pool member 2 http://kronos.xxx.edu/ -> https://kronos.xxx.edu/wfc/logon default LB for clients Allow server selection via uri when HTTP_REQUEST { if {[HTTP::uri] contains "ap1" } { HTTP::uri "/wfc/logon" pool Kronos member 192.168.1.121 80 } elseif {[HTTP::uri] contains "ap2"} { HTTP::uri "/wfc/logon" pool Kronos member 192.168.1.122 80 } elseif {[HTTP::uri] eq "/"} { HTTP::uri "/wfc/logon" pool Kronos } } Any suggestions are greatly appreciated.tmsh script modify pool member status
Hi, I am trying to modify pool member admin status via tmsh script using such command: tmsh::modify /ltm pool lamp_opi_pl members modify {lamp12_nd:http {session user-disabled}} but every time script is executed I've got such errors: pool-status.tcl: script failed to complete: can't eval proc: "script::run" members: required brace is missing "{" while executing "tmsh::modify /ltm pool "lamp_opi_pl" members modify {"lamp12_nd:http" {session user-disabled}}" (procedure "script::run" line 35) invoked from within "script::run" line:1 script did not successfully complete, status:1 What is wrong with my command? Is that not possible to change admin status for pool member in script? Piotr
Question on Priority Group Activation
Hi, I want to make my virtual server with 9 pool member automatically disabled when four of its pool member are down. Can I achieve this with below settings : 1. Put all the pool members to the same priority group for example 5 2. Under Priority Group Activation, I would select 6 viz., traffic should be processed by the pool members of group 5 till the pool have 6 minimum active members failing which the group shall not process the traffic. Now, as all the pool members belong to same priority group 5 and when PGA conditions fails would the virtual server would be down as there are no more pool members to accept the traffic ?? Please provide your inputs. Thanks, MSKDisable Multiple Pools Members At Once
Making a single rest call, has anyone been able to disable multiple pool members? I'm running into a problem where I want to only disable 2 of the 4 members, but every time I use the PATCH or PUT method, it wipes out the members that are not referenced in the JSON data. I should mention that I'm also using the latest version of iControlRest. Example: URL: https://myf5.foobar.com/mgmt/tm/ltm/pool/testpool/ Method: PATCH Current Pool Members: member1,member2,member3,member4 Data: { "members":[ {"name":"member1:80","state": "user-up", "session": "user-disabled"}, {"name":"member2:80","state": "user-up", "session": "user-disabled"} ] } Expected Result: Half of the pool members will be disabled (1 and 2), while the other half are enabled (3 and 4) Actual Result: Pool members 3 and 4 are wiped out and only 1 and 2 are showing as part of the pool.iRule for combination of FQDN pool member and route domains
I'm trying to configure an FQDN pool member for consuming a web service. The FQDN changes it's IP addreses resolution periodically. I configured the pool member inside its non-default Partition and Route Domain. That means the pool member is not in the default 'Common' partition and not in the default route domain '0'. As soon as I created the FQDN pool member, I noticed that the dynamically created node, created as a result of the FQDN resolution IP, was assigned the default route domain '0'. I opened a case with support to get some clarification on this and got the following response: "Unfortunately, Route domains are not supported with fqdn. We have logged in a Request For Enhancement, this, however, has no release date as of yet. 522465 RFE: Route domain support for FQDN nodes The most I can offer you is to request that this service request be added to that RFE. This will let our product development team that another customer is requesting this. Please let me know if you are interested in this." After doing some research I found the following iRules on Codeshare: https://devcentral.f5.com/s/articles/dynamic-ephemeral-node-fqdn-resolution-with-route-domains-with-dns-caching-irule-1148 https://devcentral.f5.com/s/question/0D51T00006j3E1I/fqdn-node-with-route-domains I've tried both iRules on versions 12.1.2 and 14.1.2, but am getting different TCL errors. Has anyone been able to get the combination of FQDN pool members with a non-default route domain?
specific pool member based on URI reruns causing failure
I have an iRule that runs to allow me to test a specific pool member provided I put a special word in the uri; the application is a java app, and the Java part works fine. The problem is when the application comes back to run a report, it changes the uri and the HTTP_REQUEST runs again putting me in the wrong pool. I thought the cookie would prevent this from happening, but it's not. Here's the code when HTTP_REQUEST { if {not [HTTP::cookie exists "admintest"]} { if {[string tolower [HTTP::uri]] ends_with "admin"} { pool Test_Pool member 192.168.2.100:80 ; log local0. "WELCOME [HTTP::uri]" } else { pool TEST_Pool member 192.168.2.200:80 ; log local0. "This is not the right place" } } } when HTTP_RESPONSE { HTTP::cookie insert name "admintest" value "IamTesting" }tmsh script and pool members
Hi, Probably easy one but not for me 😞 I am looking for simplest and fastest way to verify settings of pool member in given pool/s - for example description. Right now I have such code that is working but maybe there is simpler way? set pool_names [lrange $tmsh::argv 1 end] foreach pn1 $pool_names { foreach obj1 [tmsh::get_config /ltm pool $pn1] { puts $obj1 tmsh::modify /ltm pool $pn1 description "Orange" tmsh::log "Description is [tmsh::get_field_value $obj1 description]" foreach member1 [tmsh::get_field_value $obj1 members] { puts $member1 puts "Pool member desc: \"[tmsh::get_field_value $member1 description ]\"" } } } puts are just for testing of course. So last puts returns description for each pool member in a pool. What puzzles me as well is why after using tmsh::modify /ltm pool $pn1 description "Orange" tmsh::log reports previous value. After script is finished value is set to "Orange" but inside script even after modify old value is reported. I assume as well that there is no need for tmsh save sys config to permanently save changes? Piotr
Can F5 use virtual server of another F5 as pool member?
Hi I have F5 in two separate zone (ie. zone internal,DMZ) i want to use F5 internal zone LB to different virtual server in different F5 DMZ zone (pool member is VS_1 of F5_1 DMZ & VS_2 of F5_2 DMZ ) network Flow is Client >> VS F5 internal LB >>>> LB between VS_1 of F5_1 DMZ & VS_2 of F5_2 DMZ >>> then each F5 DMZ will LB to their pool member respectively F5 internal zone will LB virtual server of another F5 can this doable? Is this will have issue? or prerequisite? Kridsana
