Forum Discussion

chandra_66181's avatar
chandra_66181
Icon for Nimbostratus rankNimbostratus
Dec 30, 2008

TroubleShooting: Help Needed please

 

Hi,

 

 

We are using BIG-IP 9.1.2 Build 40.2.

 

 

we are load balancing 3 websphere servers with applications running on it. One of the major application is call center application which has 9 IVR servers that run on windows. This load balancer is used for some other appl too.

 

 

We are using IP based load balancing, one of this pool is related to IVR.

 

We are experiencing the issue of partial pages being delivered to the IVR servers. When ever partial pages are delivered, we need to restart the process on the IVR server to correct this.

 

For this i have req network traces between IVR<->F5<->Websphere servers. With our network team analyzation the complete file is delivered by WAS servers.The application runs fine for couple of days and again partial pages are delivered. I noted during the time of this error f5 forwards all the subsequent requests from that ivr server to only one websphere until we restart the process on IVR.Say( IVR1<-> F5<->Web1( we are using 3 webspheres)). why the requests are sent to one websphere only? What happens in the pool? Any ideas how to troubleshoot this kind of scenario Please???

 

 

Thanks,

 

Chandra

 

 

 

 

config
design
  • Pavel_Sestak_69's avatar
    Pavel_Sestak_69
    Icon for Nimbostratus rankNimbostratus
    Jan 09, 2009
    First of all - I would recommend upgrade to more recent version - let's say that 9.3 would be great - a LOT of things was fixed during last year.

     

     

    Regarding forwarding to one WAS instead of three - this might be caused by persistency profile keeping requests on single node (cookies, timeouts etc.) - but this is just a wild shot, because it is nearly impossible to say why this is happening without relevant data and knowledge of balanced application.

     

     

    I would check the dumps from the network, they should clearly see if the problem with partial pages is caused by server, client or balancer.