Forum Discussion

sohail_mahmood_'s avatar
sohail_mahmood_
Icon for Nimbostratus rankNimbostratus
Mar 27, 2015

one pool member having very less traffic

hi

 

LTM:BIG-IP Version 9.2.4 13.1 we observed there is very less traffic on one of the pool member, only we can see client (XXX.20.84.2 ) (Client:XXX.20.84.2:33475 <-> LB-VS XXX.24.26.126:10011 <-> Pool Member having less traffic (XXX.24.53.182:10011) there iare no irules , its simple round robin pool . plz find below the details

 

[root@lb2:Active] config b conn|grep 10011|grep XXX.24.53.182 XXX.20.84.2:33475 <-> XXX.24.26.126:10011 <-> XXX.24.53.182:10011 tcp [root@stclb2:Active] config b conn|grep 10011|grep XXX.24.20

 

XXX.24.20.175:38964 <-> XXX.24.26.126:10011 <-> XXX.24.158.16:10011 tcp XXX.24.20.175:39132 <-> XXX.24.26.126:10011 <-> XXX.22.114.169:10011 tcp XXX.24.20.175:39134 <-> XXX.24.26.126:10011 <-> XXX.24.158.16:10011 tcp XXX.24.20.175:39136 <-> XXX.24.26.126:10011 <-> XXX.22.201.70:10011 tcp XXX.24.20.175:39137 <-> XXX.24.26.126:10011 <-> XXX.24.158.16:10011 tcp XXX.24.20.175:39138 <-> XXX.24.26.126:10011 <-> XXX.22.114.169:10011 tcp XXX.24.20.175:39255 <-> XXX.24.26.126:10011 <-> XXX.22.201.70:10011 tcp [root@lb2:Active]

 

4 Replies

  • Hi Sohail,

     

    did you apply some kind of persistence to your virtual server?

     

    Thanks, Stephan

     

  • Hi,

     

    Maybe there is priority group activation used? Or there is some flapping caused by monitor for one pool member?

     

    Piotr

     

  • Hi Sohail,

    there are very few current connections only at all on your virtual server.

    (The bigpipe dump is showing the current connection table only.)

    How does the pool statistics page look like?
    tmsh show ltm pool  members
    

    Thanks, Stephan

  • Hi Sohail,

    your are right "
    tmsh
    " was introduced with TMOS v10 and "
    bigpipe
    " is the TMOS v9 equivalent.

    Based on the provided statistics data I see a relatively even distribution of traffic across all pool members in "
    session enabled
    " state.

    Pool members in state "
    session disabled
    " will not receive new connections (except for new connections matching persistence table entries [which is not the case in your setup as you wrote]).

    Make sure to set all pool members to "
    enabled
    " state via the WebUI configuration utility or via "bigpipe" command (can´t tell the syntax out of my head, sorry).

    Thanks, Stephan