For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

nituinusa_14613's avatar
nituinusa_14613
Icon for Nimbostratus rankNimbostratus
Oct 13, 2016

Routing traffic when some of the pool members stop working

We are using Big IP to load balance our PeopleSoft application. Two web servers are part of a pool on the Big IP. Our problem is that when we shut down one of the web servers all the traffic does not get routed to the second one right away. There is a 30-40 sec lag before big IP realizes that the member is down and stops sending traffic. Users get page not found error. I am not a Big IP professional but I have seen it work without any hiccup in previous implementations. Is there any specific set up within Big IP that we could be missing?

 

application delivery
BIG-IP
LTM

1 Reply

  • Vijay_E's avatar
    Vijay_E
    Icon for Cirrus rankCirrus
    Oct 13, 2016

    That is the intended behavior as the monitor takes about the 16-20s just to realize that the pool member has failed health-check.

     

    You can explore the following options - SOL13310

     

    Disabled or Forced Offline options provide you with the ability to retain existing connections and in the 2nd case, it removes all connections from the server.

     

    You can utilize "disabled string" in the HTTP monitor to send information to the F5 that the pool member needs to be disabled - this makes the F5 realize that the member is going down immediately.

     

    If you utilize OneConnect with 255.255.255.255 netmask, the VS will make the load balancing decision per-HTTP request rather than the default per-TCP connection and this will enable the F5 to make a load balancing decision for every incoming HTTP request and not just for the initial TCP connection.

     

    I am not sure if I answered all your questions but a bit more detail on how you take a serverd down would be helpful. Also, it is essential to have a "process" within your team/organization that defines the method to take down a pool member :-)