Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

vokhoa_96970's avatar
vokhoa_96970
Icon for Nimbostratus rankNimbostratus
Oct 10, 2011

Loadbalance connection problem (Urgent!)

Hi all,

 

 

I'm facing with urgent problem when the initial connection from internal client to outside load-balance via three ISPs cause of dropped. The server refuse any connection from 2-3 addresses. So I must keep only one default gateway pool by disable others.

 

 

I'm not familiar with iRule, but I think it can result this issue. My idea is:

 

 

When Connnection Request= (domaina:3000 or http://mail.domaina.com)

 

{For each client_add

 

-> use only a gateway in default_gateway_pool

 

}

 

 

Any idea for this case or represent to iRule for me. Note that my device is LinkController so Layer_7 feature hasn't licensed.

 

 

Thanks so much,

 

Khoa

 

7 Replies

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Oct 10, 2011
    u want to use specific default gateway when requesting to specific destination, don't u?

    if so, can u try this? 1.1.1.1 is the destination and 2.2.2.2 is the gateway. 

    when CLIENT_ACCEPTED {
   if {[IP::addr [IP::local_addr] equals 1.1.1.1]} {
      node 2.2.2.2
   }   
}

    IP::addr wiki

    http://devcentral.f5.com/wiki/iRules.IP__addr.ashx

    iRules IP Comparison Considerations with IP::addr Command by Jason

    http://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/1086449/iRules-IP-Comparison-Considerations-with-IPaddr-Command.aspx
  • vokhoa_96970's avatar
    vokhoa_96970
    Icon for Nimbostratus rankNimbostratus
    Oct 11, 2011
    Thanks Nitass,

     

    But with your rule, I think it's not a feature of load-balancer.And also lost all connection to dest 1.1.1.1 when note 2.2.2.2 down.

     

    My ideas for this situation are:

     

    - For each IP client to server 1.1.1.1 with port 3000, LC will forward to a gateway:

     

    (Ex: PC1 -> Server:3000 -> ISP1 ; PC2 -> Server:3000 -> ISP2; PC3 -> Server:3000 -> ISP1)

     

    - Any configuration forward to gateway pool sticky/ persistence

     

     

    Thanks,

     

    Khoa

     

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Oct 11, 2011
    thanks, it appears i misunderstood your question. :-)

     

     

    - Any configuration forward to gateway pool sticky/ persistence have you ever tried source address persistence?
  • vokhoa_96970's avatar
    vokhoa_96970
    Icon for Nimbostratus rankNimbostratus
    Oct 11, 2011
    I've tried with source address persistence but it still load to all gateway pool member.

     

    Could u help me with the first solution by iRule?

     

     

    Thanks,

     

    Khoa
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Oct 11, 2011
    i don't think you need an irule. persistence should be able to do what you want.

     

     

    can you post virtual server configuration here?
  • vokhoa_96970's avatar
    vokhoa_96970
    Icon for Nimbostratus rankNimbostratus
    Oct 11, 2011
    This is my configuration about this VS, pls check it for me

     

    pool mail_pool {

     

    monitor all gateway_icmp

     

    members 210.211.108.119:any {}

     

    }

     

     

    virtual vs_mail {

     

    pool mail_pool

     

    destination 210.211.108.119:hbci

     

    ip protocol tcp

     

    persist source_addr

     

    profiles {

     

    http {}

     

    tcp {}

     

    }

     

  • vokhoa_96970's avatar
    vokhoa_96970
    Icon for Nimbostratus rankNimbostratus
    Oct 12, 2011
    This case have been solved by source address persistence configuration.

     

    Thanks Nitass for supporting.