CirrostratusI would normally construct some sort of test to verify this, but I'm having some difficulty with that so I just thought I'd ask. Can anyone tell me what action will cause the timeout value on a source_addr persistence record to get reset? Does any traffic on a persistent connection reset the timer, or do only NEW connections reset the timer?
Adminthe timer expires either when a) a client has not made a connection in the allocated persistence time or b) the server with which the connection was attached to is marked down.
AdminZero is expired, so I guess I'm not sure wahat you are requesting.
EmployeeDoes any traffic on a persistent connection reset the timer, or do only NEW connections reset the timer?
it seems traffic on persistent connection also reset the timer.
e.g.
ssh client's keep-alive is set to 60 seconds
[root@ve11a:Active:In Sync] config tcpdump -nni 0.0 not host 172.28.24.11 and port 22
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
20:55:31.123793 IP 192.168.206.35.63215 > 172.28.24.10.22: P 36:72(36) ack 1 win 64732
20:55:31.123817 IP 200.200.200.14.63215 > 200.200.200.101.22: P 36:72(36) ack 1 win 7020
20:55:31.123823 IP 172.28.24.10.22 > 192.168.206.35.63215: . ack 72 win 5808
20:55:31.125789 IP 200.200.200.101.22 > 200.200.200.14.63215: . ack 72 win 9648
persistence record age is reset about the time keep-alive is received
Wed Apr 30 20:55:40 PDT 2014
Sys::Persistent Connections
source-address - 172.28.24.10:22 - 200.200.200.101:22
-----------------------------------------------------
TMM 1
Mode source-address
Value 192.168.206.35
Age (sec.) 5
Virtual Name /Common/bar
Virtual Addr 172.28.24.10:22
Node Addr 200.200.200.101:22
Pool Name /Common/foo
Client Addr 192.168.206.35
Owner entry
Total records returned: 1
Cirrostratus
NoctilucentDoes any traffic on a persistent connection reset the timer, or do only NEW connections reset the timer?
it seems traffic on persistent connection also reset the timer.
e.g.
ssh client's keep-alive is set to 60 seconds
[root@ve11a:Active:In Sync] config tcpdump -nni 0.0 not host 172.28.24.11 and port 22
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
20:55:31.123793 IP 192.168.206.35.63215 > 172.28.24.10.22: P 36:72(36) ack 1 win 64732
20:55:31.123817 IP 200.200.200.14.63215 > 200.200.200.101.22: P 36:72(36) ack 1 win 7020
20:55:31.123823 IP 172.28.24.10.22 > 192.168.206.35.63215: . ack 72 win 5808
20:55:31.125789 IP 200.200.200.101.22 > 200.200.200.14.63215: . ack 72 win 9648
persistence record age is reset about the time keep-alive is received
Wed Apr 30 20:55:40 PDT 2014
Sys::Persistent Connections
source-address - 172.28.24.10:22 - 200.200.200.101:22
-----------------------------------------------------
TMM 1
Mode source-address
Value 192.168.206.35
Age (sec.) 5
Virtual Name /Common/bar
Virtual Addr 172.28.24.10:22
Node Addr 200.200.200.101:22
Pool Name /Common/foo
Client Addr 192.168.206.35
Owner entry
Total records returned: 1