Application Delivery (ADX)

Reply
Occasional Visitor
Posts: 1
Registered: ‎03-28-2017

ADX1000 Connection Persistence

We have client connections (from a single IP) that have multiple sessions hitting a VIP. I'd like to be able to spread those sessions across the real servers in the VIP. Currently, we have the VIP predictor as least-conn and sticky (15 min age), with 2 real servers bound to it.

 

Example: Customer A has 10 application sessions connecting to the VIP from a single public IP. How can each of those 10 sessions be balanced across the 2 real servers?

 

Currently, all 10 sessions are placed on the same real server. The sessions are constantly active so if we take RS1 out of the VIP for maintenance, RS2 will load up on sessions. When RS1 is returned to the VIP, it does not balance out the sessions.

The client sessions from that single IP are stuck to RS2, and as long as they remain active and their session does not timeout, they will remain on RS2 in definitely.

 

Running version: 12.4.00vT403

 

Virtual Server:

---------------------------------------------------

server virtual vserver1
 description "Production"
 predictor least-conn
 port ssl sticky
 port ssl ssl-terminate www.someurl.org
 bind ssl RS2 http RS2 http

Brocade Moderator
Posts: 235
Registered: ‎06-30-2010

Re: ADX1000 Connection Persistence

Hi,

 

Do you know if the client are using HTTP 1.1 pipelining, if they are then most likely the client will only create a single TCP connection to the VIP and as such this will result in all requests going to the same server as there is only one session.

 

Also have you tried round-robing predictor, as long as new TCP session is established for each connection (SYN) then this mean that each new session will be sent to the next real server

 

It may be useful to try running debug-filter on the ADX then you should be able to capture the sessions to the VIP and to real servers this may give you a better idea what exactly is going on and if each new connection creates a new session (SYN, SYN ACK, ACK)

 

Hope this helps

Mick


If my response has solved your query please click the "Accept as Solution" button.

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers.

All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.