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?

     

Michele_Cereda_'s avatar
Michele_Cereda_
Icon for Nimbostratus rankNimbostratus

The problem seemed to be caused by the Type parameter of the VS, that was set on Performance (Layer 4) instead of Standard.

Now the code is working. Thanks for your advices.

The thing that seems strange to me about this particular topic is that the editor warned me that the VS needed a different profile in case I tried to set something like that. Do you have any ideas why it didn't this time?

Michele_Cereda_'s avatar
Michele_Cereda_
Icon for Nimbostratus rankNimbostratus
Feb 08, 2016
It seems to be like you say, since the log in the LB_SELECTED block is recorded **before** the ones in the HTTP_REQUEST block. I was wondering.. I found out that multiple `node` or `pool` commands just overwrite the final destination selection, so that only the last one is considered valid. If the LB_SELECTED happens before the HTTP_REQUEST, and it should since the log commands in the latter were executed after the selection, shouldn't the HTTP_REQUEST block reselect the destination node or pool invalidating the selection made in the LB_SELECTED block? Because it seems they are just ignored. Is the selection in the LB_SELECTED block final?