Forum Discussion

munish_64882's avatar
munish_64882
Icon for Nimbostratus rankNimbostratus
Aug 17, 2012

Pool not working

I am facing an issues with the pool members.

 

I have two pool members listening on port 80

 

1. 192.168.2.36 and

 

2. 192.168.2.37

 

 

When pool member 192.168.2.36 was down, I was not able to access the website even when 192.168.2.37 was up. But as soon as 192.168.2.36 came up, the website was accessible.

 

 

If I see the pool statictics on my load balancer, it shows ZERO out packets/bits for 192.168.2.37.

 

 

Please refere to attachment for statistics.

 

 

I don't think that there is any issue in the configuration and if one server works, other should also work.

 

 

I have configured it as round robin.

 

 

Any ideas, why isn't it working.

 

 

management
monitoring

10 Replies

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Aug 17, 2012
    Hi Munish,

     

     

    That sounds odd. Was the 192.168.2.37 member marked down by a monitor? Do you have persistence configured and was the 192.168.2.36 member not marked down by a monitor?

     

     

    Aaron
  • munish_64882's avatar
    munish_64882
    Icon for Nimbostratus rankNimbostratus
    Aug 21, 2012
    the more wierd thing is that 192.168.2.37 is also up and green. Still Its not passing traffic.

     

    I see 6.0 M in packets but 0 out packets.
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Aug 21, 2012
    can you post the virtual server and pool configuration?

     

     

    b virtual (name) list

     

    b pool (name) list
  • munish_64882's avatar
    munish_64882
    Icon for Nimbostratus rankNimbostratus
    Aug 21, 2012
    Here are the outputs..

     

     

    [root@ULFINPG-LB001:Active] config b virtual list

     

    virtual WEB_VS {

     

    pool WEB_POOL

     

    destination 192.168.2.6:http

     

    ip protocol tcp

     

    }

     

     

     

    [root@ULFINPG-LB001:Active] config b pool list

     

    pool WEB_POOL {

     

    monitor all http

     

    members {

     

    192.168.2.36:http {}

     

    192.168.2.37:http {}

     

    }

     

    }

     

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Aug 21, 2012
    can you try to enable "snat automap" under the WEB_VS virtual?
  • munish_64882's avatar
    munish_64882
    Icon for Nimbostratus rankNimbostratus
    Aug 21, 2012
    what will SNAT achive at this point?

     

    It will NAT the traffic behind VIP... If this would have been the issue, other pool memeber should not have worked..

     

     

    Anyways.. I can give it a try... I will post the update.
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Aug 21, 2012
    do both servers use same default gateway? i suspect they might use different gateway.
  • munish_64882's avatar
    munish_64882
    Icon for Nimbostratus rankNimbostratus
    Aug 21, 2012
    probably yes.. I cannot be sure as I am not managing these web servers.

     

     

    But does default gateway comes in picture?

     

     

    May be I m confused between IN packets and OUT packets when we see statistics?
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Aug 21, 2012
    But does default gateway comes in picture?i guess it does not work since server responds directly to client i.e. client -> bigip -> server (192.168.2.37) -> client.

     

     

    May be I m confused between IN packets and OUT packets when we see statistics?have you seen this one?

     

     

    sol9077: Overview of BIG-IP traffic flow

     

    http://support.f5.com/kb/en-us/solutions/public/9000/000/sol9077.html

     

     

    hope this helps.