F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

PPawar_309940's avatar
PPawar_309940
Icon for Nimbostratus rankNimbostratus
Feb 28, 2019

iRULE: forwarding virtual for sql ports

Hi Guys,   We have been reported about several issues from our clients getting 504 gateway time out error since we have migrated the services from ACE to F5.   Anything to the VS is fine, but I...
application delivery
BIG-IP
iRules
uzair_95552's avatar
uzair_95552
Icon for Altocumulus rankAltocumulus
Feb 28, 2019

Virtual server protocol is configured as All protocols. So this iRule is giving the appropriate error.

In virtual server' Protocol setting change All to tcp and then apply the same iRule. Make sure your F5 software version is >=11.6 as TCP::idletime is introduced in 11.6

If you need to create UDP forwarding vs also, you can create the same virtual server with protocol as udp.

After modifying the protocol VS configuration will look like this

ltm virtual forwarding_virtual {
destination 0.0.0.0:any
ip-forward
ip-protocol tcp
mask any
profiles {
    forwarding_fastL4 { }
}
source 0.0.0.0/0
translate-address disabled
translate-port disabled
  • PPawar_309940's avatar
    PPawar_309940
    Icon for Nimbostratus rankNimbostratus
    Feb 28, 2019

    I dont think that it does matter if I use protocol as tcp/udp or any. I wont be able to apply iRULE as it requires a tcp profile and when we create forwarding VS then it uses fastl4 profile.

     

    I can create forwarding virtual for single port like below and change the tcp timeout vlaue to indefinite. But problem is I have multiple range of ports and I dont want to create that many forwarding VS.

     

    0.0.0.0/0:1521

     

  • PPawar_309940's avatar
    PPawar_309940
    Icon for Nimbostratus rankNimbostratus
    Mar 01, 2019

    Guys,

     

    Anyone has got any other brilliant idea, or some of you still think that this is not required at all.

     

    But I am sure after we migrated to F5 the users sessions are more sporadically timing out which I think because of tcp idle time.Pressure is building on us we don't want to fail back to ACE which is not at all desirable.