Forum Discussion

Michele_Cereda_'s avatar
Michele_Cereda_
Icon for Nimbostratus rankNimbostratus
Jan 29, 2016

Load balancing not bypassed by 'node' nor 'pool' commands in iRule

Hi all, I'm trying to force a packet forward to a specific pool member when the pool receives a HTTP_REQUEST with a specific URI, but it seems the iRule commands to bypass balancing (namely, node a...
application delivery
iRules
TMSH
  • Salim_83682's avatar
    Salim_83682
    Feb 01, 2016

    Try with a oneconnect profile on your VS to see if it changes anything?

     

IanB's avatar
IanB
Icon for Employee rankEmployee
Jan 29, 2016

In my lab, your irule worked as expected - that is to say:

  • When I request "/refresh", the node selected is 192.168.1.20:80
  • When I request "/" (or any other URI), the pool member selected is 192.168.1.10:80

Because your rule explicitly sets the node/member for every request, you should not be seeing normal load balancing (round robin in your case) at all.

I'm not able to tell from the information here why it's not working for you. It might help to add logging in an LB_SELECTED event, for example:

 

when LB_SELECTED {
     log local0. "[LB::server] was selected"
}

 

Then make some curl requests from the LTM itself, to eliminate anything else that might be getting in the way

 

ltm  curl -v http://x.x.x.x/refresh

 

Also, make sure you're working with the active member of the HA pair, and that the pair is in config sync