Resolution:
Description:
==========
Configuring TWM to use a hardware load balancer.

Resolution:
===========

1). Configure load-balancer to ensure that each client is always re-routed to the same node it was first routed to. (Once ClientX first establishes communication with NodeA, then future packets coming from ClientX must always be routed to NodeA).

All HTTP requests coming from a client should be directed by the load balancer to the same gateway node unless the gateway node is down. This is important because for clients that do not have native WebSockets, emulation kicks in and generates multiple HTTP requests for the same WebSocket connection. All of these requests should end up on the same gateway node that is serving the WebSocket connection. If the gateway node is down, then pick a new node but still route all HTTP requests from the same client to the newly selected gateway node.

2). Use accept.options to configure protocol binds (ws.bind) to point to the internal network interface's IP address and port while setting the service's accept URL to the balancer's URL that the clients connect to.

Platforms:
=========
All

Keywords:
==========
TWM hardware load balancer F5