Load Balancing ISO-8583 transactions received through a single tcp connection on the virtual server
We're trying to load balance ISO 8583 transactions between multiple pool members. The client platform sends all of it's transactions through a single permenent tcp connection to the F5 tcp virtual server. Currently this connection gets balanced to a single pool member. We're looking for a way to load balance those transactions among all available pool members. Does anyone have a working setup to load balance this type of traffic? We tried Stanislas_Piro2 's iRule on a test environment with a tcp virtual server with the oneconnect profile with 2 pool members but it didn't work. https://community.f5.com/t5/technical-forum/iso-8583-load-balancing/m-p/38922
Virtual Server requirements for ISO 8583 traffic
We are configuring a virtual server to handle ISO 8583 traffic and send it to a pool member (no load balancing, just one server) but we are seeing TCP RST being sent from the F5 SelfIP (which is also the Virtual Server IP address) to the destination Pool member/Port configured and connections are unsuccesful. I read some articles requiring special config when you need to load balance based on messages (MRF) but we are not load balancing at this time, we are just trying to establish a connection between client and server through the F5 (client to server directly works fine) Is there any special config/profile that needs to be configured to establish connections with no load balancing?
Packet based load balancing instead of connection based (default)
Hi everyone, I have a requirement to load balance iso 8583 echo messages across two servers in a pool. I used a performance Layer 4 virtual server to attempt achieving this because I reckon that is the type of virtual server that could fulfill the requirements of load balancing all the requests across the 2 servers in the pool. However, requests are only being sent to one pool member. I also tried to craft an iRule (see below) to do this, still requests are only sent to one pool member. when CLIENT_ACCEPTED { log local0. "ACCEPTED !!" TCP::collect } when CLIENT_DATA { log local0. "DATA !!" #to get the length of messagein hexadecimal,the length info can be get from the first 2 byte binary scan [TCP::payload] H4 len log local0. $len #convertlentodecimal scan $len %x len log local0. $len #totalmessage length is length + 2 set len [expr { $len + 2} ] if {[TCP::payload length] < $len} { TCP::collect [expr {$len - [TCP::payload length]}] return } TCP::release $len TCP::notify request TCP::collect } when LB_SELECTED { log local0. [LB::server] } when SERVER_CONNECTED { log local0. "Server Connected !!" TCP::collect } when SERVER_DATA { log local0. "response: [TCP::payload]" TCP::release TCP::notify response TCP::collect } Has anyone done packet-based load balancing before? Any ideas?