HASH Carp Persistence

And idea where the Hash value is stored is it part of the TCP header, will i be able to see it in a tcpdump?

carp hash is calculated on the fly. it is not kept inside a packet.

And idea where the Hash value is stored is it part of the TCP header, will i be able to see it in a tcpdump?

but my question is when we use HASH CARP where will be the record stored if not in the persistence table?

i understand key (e.g. source ip) and pool member information (e.g. pool member ip and port) are included in the algorithm. if key is same, it will end up to the same pool member. so, it does not utilize persistence table.

Since SSL offloading is not an option for me, i am using Source ip for persistence, but my question is when we use HASH CARP where will be the record stored if not in the persistence table?

So i will be able to support an SSL passthrough application which is required to be persisted to a server through a duration of a session with the below config paramteres

i think you had better find what information you want to persist on first. then you find how to configure it.

So i will be able to support an SSL passthrough application which is required to be persisted to a server through a duration of a session with the below config paramteres

1. Fast l4 profile, with RST on timeout disabled and loose intiation enabled
2. Using HASH CARP persistance.

is loose initiation feature availabe on a standard tcp profile?

no, it is only available on fastl4 profile.

is loose initiation feature availabe on a standard tcp profile? and with regard to viprions i think fastl4 profile has a bug

http://support.f5.com/kb/en-us/solutions/public/14000/100/sol14187

But if this setting is disabled, will the user face any impact, since a RST packet is not sent?

if reset on timeout is disabled, tcp reset won't be sent but connection entry is still removed from connection table. so, subsequent packet will be reset anyway (since no entry in connection table) unless loose initiation is enabled.

Enabling the Loose Initiation option allows the system to initialize a connection when it receives any TCP packet, rather than requiring a SYN packet for connection initiation.

sol7595: Overview of IP forwarding virtual servers

WOW!!, Thanks for the quick turnaround , Nitass

So if RST on timeout is enabled, The connection will be reset and hence the session will be terminated. But if this setting is disabled, will the user face any impact, since a RST packet is not sent?