Load Balancing based off TCP Payload entity
Hello, I believe I constructed an irule to properly a variable from text captured from two distinct points in the TCP Payload but I am not 100% certain the Irule will is persisting off this entity. can someone take a look below and see if this looks correct? I added the message load balancing profile on as well. The expectations are tat after collecting tcp payload for a new connection search for a string and then persists that string to a certain pool ( contains 2 servers). all subsequent matches for that same string in payload need to go to that pool. I also want the pool to load balance diverse entities so not everything is on the same pool member. Does this look correct ? when CLIENT_ACCEPTED { TCP::collect } when CLIENT_DATA { set payload [TCP::payload] set entityID [findstr $payload "@" 1 ","] log local0. "$entityID: $entityID" pool XYZ persist uie $entityID log local4.info " Entity Session routing $entityID and setting persistence" TCP::release TCP::notify request }
Load Balancing based off TCP Payload entity
Hello, I believe I constructed an irule to properly a variable from text captured from two distinct points in the TCP Payload but I am not 100% certain the Irule will is persisting off this entity. can someone take a look below and see if this looks correct? I added the message load balancing profile on as well. The expectations are tat after collecting tcp payload for a new connection search for a string and then persists that string to a certain pool ( contains 2 servers). all subsequent matches for that same string in payload need to go to that pool. I also want the pool to load balance diverse entities so not everything is on the same pool member. Does this look correct ? when CLIENT_ACCEPTED { TCP::collect } when CLIENT_DATA { set payload [TCP::payload] set entityID [findstr $payload "@" 1 ","] log local0. "$entityID: $entityID" pool XYZ persist uie $entityID log local4.info " Entity Session routing $entityID and setting persistence" TCP::release TCP::notify request }