Deferred Accept
Hi, I wonder what statement form online help exactly means in relation to packet flow on BIG-IP (based on this image): Specifies, when checked (enabled), that the system defers allocation of the connection chain context until the system has received the payload from the client. When monitoring session table as well as tcp profile stats (after 3WHS finished but before first data packet send) only difference is in tcp profile stats: Deferred Accept enabled: show sys connection cs-client-addr 10.128.11.3 output: 10.128.11.3:12346 10.128.11.51:80 any6.any any6.any tcp 19 (tmm: 2) none show ltm profile tcp [profile used by VS] output: Open 1, Accepted 1 Deferred disbaled show sys connection cs-client-addr 10.128.11.3 output: as above show ltm profile tcp [profile used by VS] output: Open 0, Accepted 0 So in both cases entry in session table is created - what part then is deferred? What exactly is connection chain context? PiotrTCP profile stats for client and server context
Hi, Just did some test on VS without oneconnect and separate client and server TCP profile. I wonder what exactly means Open, Accepted and Established depending on context. Stats for client context profile: Connections Open 1 Current in CLOSE-WAIT/LAST-ACK 0 Current in FIN-WAIT-1/CLOSING 0 Current in FIN-WAIT-2 0 Current in TIME-WAIT 0 Accepted 1 Not Accepted 0 Established 0 Failed 0 Expired 0 Abandoned 0 server context: Connections Open 1 Current in CLOSE-WAIT/LAST-ACK 0 Current in FIN-WAIT-1/CLOSING 0 Current in FIN-WAIT-2 0 Current in TIME-WAIT 0 Accepted 0 Not Accepted 0 Established 1 Failed 0 Expired 0 Abandoned 0 For session table entries: Sys::Connections 10.128.11.3:12346 10.128.11.51:80 10.1.20.100:12346 10.1.20.11:80 tcp 29 (tmm: 2) none Total records returned: 1 Sys::Connections 10.128.11.3:12346 10.128.11.51:80 10.1.20.100:12346 10.1.20.11:80 tcp 29 (tmm: 2) None Why for: Client context Open and Accepted is reported Server context Open and Established is reported Accepted means only 3WHS performed in client context, never in server context? Established can be only for successful 3WHS between BIG-IP and member in server context, never in client context? Or only when there there are matching client and server flows in session table? Piotr
