For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

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

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
Feb 01, 2016

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?

IanB's avatar
IanB
Icon for Employee rankEmployee
Mar 19, 2016
Sorry about the delay. I can confirm that this is expected behaviour when using FastL4 + HTTP. The HTTP profile was enhanced to allow it be added to a fastL4 to support the PEM product, but it is currently quite limited in what it can do (see SOL16446), as the intended use was only with the PEM. module. As a result, in this scenario, HTTP_REQUEST fires after LB_SELECTED, at which point it is too late to change the selected pool member. As you've noted, modifying the virtual server to be of type 'standard' resolves the issue.