Forum Discussion

Cirrostratus

Mar 18, 2015

SNAT, VS and multiple Idle Timeout setting

Hi, I am a bit lost how Idle Timeout (IT) is managed when there are different object involved for given connection. VS has Idle Timeout set via TCP profile (let's say it's Standard VS), SNA...

Historic F5 Account

Mar 24, 2015

I know for sure, that the Virtual Server's Idle timeout applies. Stop racking your head about this 🙂

I have tested it.

tmsh show sys conn all-properties
Sys::Connections
10.1.3.195:36055 - 10.1.3.170:80 - 10.1.3.177:36055 - 10.1.3.95:443
-------------------------------------------------------------------
  TMM           1
  Type          any
  Acceleration  none
  Protocol      tcp
  Idle Time     2
  Idle Timeout  300
  Unit ID       1
  Lasthop       /Common/vpersonal 00:23:e9:88:76:03
  Virtual Path  10.1.3.170:80
  Conn Id 0  

                     ClientSide        ServerSide
  Client Addr  10.1.3.195:36055  10.1.3.177:36055
  Server Addr     10.1.3.170:80     10.1.3.95:443
  Bits In                  3.9K             18.6K
  Bits Out                 9.6K              8.6K
  Packets In                  8                 5
  Packets Out                 7                 9

Total records returned: 1
[root@bigip:Active:Standalone] config  tmsh list ltm snat
ltm snat from195to199 {
    origins {
        10.1.3.195/32 { }
    }
    translation /Common/10.1.3.177
}

dragonflymr
Cirrostratus
Mar 24, 2015
Sorry for nit picking :-), promise to avoid. To summarize: 1. Setting of VS always wins 2. It's best to use SNAT pool (even with one translation IP) - then you have full control when SNAT is used, SNAT object has to be created explicitly or SNAT pool used with VS. No way to create some hole in LTM like with SNAT object not using SNAT pool 3. When using SNAT object it's advised to adjust IT - I guess leaving it at Indefinite is not best practice Thanks a lot for all help, I really appreciate your time and effort. Piotr
JWhitesPro_1928
Cirrostratus
Oct 10, 2017
does automap change any of this?