Forum Discussion
jgranieri
May 24, 2011Nimbostratus
irule tcp payload persistence
Here is what is currently working:
I have 2 issues/questions. I cant seem to get logging to work whether I use remote syslog IP and or change local0 ot local7 etc.
2nd question - ...
hooleylist
May 27, 2011Cirrostratus
Hi,
I don't have much experience parsing TCP for persistence and load balancing, but let's give it a go. Do you have a CLIENT_ACCEPTED event where you're calling TCP::collect? This is required in order to tell TMM to buffer the TCP payload.
http://devcentral.f5.com/wiki/default.aspx/iRules/tcp__collect
when CLIENT_ACCEPTED {
TCP::collect 250
}
when CLIENT_DATA {
log local0. "in CLIENT_DATA"
set clientData [TCP::payload 250]
log local0. "Client Data raw: $clientData"
switch -glob $clientData {
"@int3*" {
node 10.35.22.33 9820
log local0. "Entity @int3* being Loadbalanced"
}
"@int4*" {
node 10.35.22.32 9820
log local0. "Entity @int4* being Loadbalanced"
}
}
TCP::release
}
What are you trying to persist on? The current iRule is manually selecting a node based on the @int value. Do you want the client IP to be sent to the corresponding node for multiple TCP packets even if they don't have the same @int value on each connection?
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects