GIR with F5 Load Balancer

General Discussion
1

Hi Experts,

Anybody here deploy GIR with F5 LB instead Apache ?

We do have F5, and want to utilize F5 for GIR LB. But I cant find any documentation of Genesys where they say how it will be deploy or work like SIP-F5 document have. From Genesys, Its confirmed that we can use F5 for GIR.

Anybody here have experience of using F5 with GIR, and can share the bottle neck or challenges of using F5 for GIR LB ?

2

I have successfully deployed a few env where F5 was used as LB for GIR. It is just about HTTP/HTTPS balancing, so nothing special. You just have to follow documentation in respect to used cookies or session identifiers.

3

How many data centres involved?

Sent from my Redmi Note 3 using Tapatalk

4

What I understood is that just configure both server physical IP with VIP but the important thing is to configure cookies or session identifiers. Some applications require stickiness and some cookies which I can take reference from GIR Solution Deployment Documentation.

5

2 DC ..

6

The only components that need to have sticky sessions are the RWS (htcc) and the RCS (Recording Crypto Server). Also the Speechminer Web if you want to do the load balancing between two of them or more.

The other components only need to have a simple load balancing, when for example a POST is done, it points to the F5 and it redirects the POST to the component. The F5 listen in one port for each “cluster” of component (also it can be recognized by the first part of the URL, for example http://IP/component1): one port for WebDAV, one port for RPS, one port for Interaction Receiver, and the mentioned before that needs extra configuration. Then the F5 simply do a round robin between the members (ip:port of the application), because them don’t requires stickyness.

The RCS and RWS “extra” configuration of httpd load balancer is (red):

Web Services

<Proxy balancer://htcc>
BalancerMember http://htcc1:8080 route=HTCC1
BalancerMember http://htcc2:8080 route=HTCC2
BalancerMember http://htcc3:8080 route=HTCC3
Header add Set-Cookie “ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/” env=BALANCER_ROUTE_CHANGED
ProxySet stickysession=ROUTEID

ProxyPass /api balancer://htcc/api
ProxyPass /internal-api balancer://htcc/internal-api
ProxyPass /ui balancer://htcc/ui

RCS

<Proxy balancer://rcs>
BalancerMember http://rcs1:8008 disablereuse=On connectiontimeout=10000ms route=RCS1_Application_Name
BalancerMember http://rcs2:8008 disablereuse=On connectiontimeout=10000ms route=RCS2_Application_Name
ProxySet stickysession=JSESSIONID

ProxyPass /rcs balancer://rcs/rcs

You’ll need to “translate” this extra configuration to F5 “language”. I’ve never done it, but httpd and F5 are very used so I think there is a lot of information

7

Thank nconiglio .. :slight_smile:

8

Glad to help ;D

9

Hi, any chance that you could attach an example of such F5 configuraion? or send via email? I would greatly appreciate that :wink:

thanks