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

jasonabbott_407's avatar
jasonabbott_407
Icon for Nimbostratus rankNimbostratus
Jun 10, 2013

IBM Traveler HA configuration

With IBM Traveler 8.5.1 there now exists the capabilites to run traveler in a true HA fashion. Unfortunately for everyone, IBM only has docs for using Mobile Connect as the Proxy/IP Sprayer.

 

Knowing, however, that anything LMC can do, my LTM can do better; does anyone have any insight on appropriate configurations? I currently have it set up simply as a basic round robin between the both with a long timeout (based on the Traveler Admin's settings).

 

Should I be concerned with anything else? Performance is acceptable, but I'm always on the lookout for more.

 

 

ibm
partner

2 Replies

  • Nojan_Moshiri_4's avatar
    Nojan_Moshiri_4
    Historic F5 Account
    Jun 10, 2013
    Hi Jason, I haven't see any Traveler 8.5 solutions, let me research this for you and get back to you.
  • Nojan_Moshiri_4's avatar
    Nojan_Moshiri_4
    Historic F5 Account
    Jun 11, 2013
    I found this document that describes the architecture: http://www-01.ibm.com/support/docview.wss?uid=swg27036151&aid=1

     

     

    A couple of points. They say any load balancer is supported. And specifically, they say "Round robin" and "no or limited session affinity". This is a bit unclear but at the end of the document (Page 38) they have a page on "Load Balance Considerations". The points are not spelled out that clearly, but it highlights the usual points:

     

     

    1) Check your configuration for the type of monitoring you are using. Perhaps there's a better way to monitor your servers for better outage detection. Explore using an HTTP/S monitor if you are not already and incorporate a send and receive string, instead of using a plain TCP monitor.

     

    2) Check your persistence/affinity rules to make sure you are going to properly distribute connections. What persistence rule are you using right now?

     

    3) Make sure your BIG-IPs are properly configure for device to device failover (Generic for any BIG-IP deployment, but they make a point to highlight this several times).

     

     

    Finally, in terms of other optimizations, it's often useful to have a TCP client and server profile applied to your Virtual Server if your users are remote. For example, TCP WAN optimized profile on the client side and TCP LAN optimized profile on the server side.