CirrostratusAnother one for you all. The TCP Profile Zero Window Timeout setting description states "If the Zero Window Timeout timer elapses, the BIG-IP system terminates the connection."
Does this mean a RST is sent or will this depend on the 'Reset on Timeout' setting?
Employeee.g.
config
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual bar
ltm virtual bar {
destination 172.28.24.10:80
ip-protocol tcp
mask 255.255.255.255
pool foo
profiles {
mytcp { }
}
source 0.0.0.0/0
source-address-translation {
type automap
}
vs-index 63
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm pool foo
ltm pool foo {
members {
200.200.200.101:80 {
address 200.200.200.101
}
}
}
root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm profile tcp mytcp
ltm profile tcp mytcp {
app-service none
defaults-from tcp
reset-on-timeout disabled
zero-window-timeout 1000
}
trace
...snipped...
03:17:33.167785 IP 200.200.200.14.54494 > 200.200.200.101.80: . ack 8202039 win 0 out slot1/tmm0 lis=/Common/bar flowtype=128 flowid=5700010E3000 peerid=5700010E4A00 conflags=8124 inslot=63 inport=55 haunit=1 priority=0 peerremote=00000000:00000000:0000FFFF:AC1C1801 peerlocal=00000000:00000000:0000FFFF:AC1C180A remoteport=54494 localport=80 proto=6 vlan=4093
03:17:35.000161 IP 200.200.200.14.54494 > 200.200.200.101.80: R 163:218(55) ack 8202039 win 0 out slot1/tmm0 lis=/Common/bar flowtype=128 flowid=5700010E3000 peerid=5700010E4A00 conflags=808124 inslot=63 inport=55 haunit=1 priority=0 rst_cause="[0x1a06ef2:8794] {peer} TCP zero window timeout" peerremote=00000000:00000000:0000FFFF:AC1C1801 peerlocal=00000000:00000000:0000FFFF:AC1C180A remoteport=54494 localport=80 proto=6 vlan=4093
03:17:35.000188 IP 172.28.24.10.80 > 172.28.24.1.54494: R 8164016:8164064(48) ack 163 win 4542 out slot1/tmm0 lis=/Common/bar flowtype=64 flowid=5700010E4A00 peerid=0 conflags=808124 inslot=63 inport=55 haunit=1 priority=0 rst_cause="[0x1a06ef2:8794] TCP zero window timeout" peerremote=00000000:00000000:00000000:00000000 peerlocal=00000000:00000000:00000000:00000000 remoteport=0 localport=0 proto=0 vlan=0
Cirrostratus
AltostratusCirrostratusThe TMOS v11.6 release notes mention this as a new feature: "Modification of TCP profile parameters via iRules." (https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.html)
It doesn't look like the iRules wiki has been updated yet though so you'll have to play around and try stuff to see what's now possible, if you have a v11.6 device available.