Forum Discussion

al_kabeer_2905's avatar
al_kabeer_2905
Icon for Nimbostratus rankNimbostratus
Dec 09, 2012

Slow Response on webserver

Hi, I have BigIP ltm, with Virtual server , this VS contain 2 nodes (web application) one of them priority = 1 and the other = 0, http health monitor is configured ( Get xyz ....) response (200 OK) time interval 5 and timeout 16,

 

 

I have experience slowness on the web application, health monitor still shows green but application is slow,

 

I want BigIP to sense if the application is slow and shift to the other node ( priority = 0), Can i do it with IRule or any other good solution ???

 

thanksssssss

 

 

5 Replies

  • The only solution that I was able to use was monitoring the monitor. We have monitors in my company that measure slowness from the client's perspective. Thus we pointed F5 monitors to the results of those monitors. Based on that we determine whether the APP is up or down.

     

     

    I hope that helps,

     

    Bhattman
  • Hi Bhattman,

     

     

    How i am going to monitor the monitor ????, i did not get it, is this feature in BigIP or do i need to create monitor ??

     

     

    thanksss
  • Hi, The Bhattman is suggesting using an external monitoring system entirely, not something available with BIG-IP, to monitor client or server performance and then having the BIG-IP health monitor point to something on that system.

     

     

    Other options might include;

     

     

    1) Lowering your health monitor timers?

     

    2) Having the web server generate and update a specific page related to it's performance and using that with a health monitor

     

    3) Using a iRule sideband connection somehow

     

    4) Using an iRule with a Statistics profile
  • Brian_Deitch_11's avatar
    Brian_Deitch_11
    Historic F5 Account

    From experience, if one virtual is slow and none of the other virtuals are slow, then it's not the BIG-IP.

     

    Troubleshooting steps outside of the F5:

     

    Download and install fiddler2. If you need to decrypt SSL traffic, check the help page on setting that up.

     

    Open fiddler2, clear your web cache, and hit the website on the virtual server IP. Highlight the transactions and click the timeline. You can see what is taking so long to load.

     

     

    Next, modify your local host file to bypass the F5 and go directly to the server.

     

    Clear your webcache, and hit the website again. If it's stil slow, then you know it's the server. Gather the timeline info and foward to your dev/server team. It's on them at this point.

     

    Do this for every server in the pool. It's possible that you have a single webserver that is the culprit.

     

     

    Good luck.