03-15-2015 03:14 AM - edited 03-11-2019 10:38 PM
Hallo,
in my Cisco ASA configuration I have the following (default) command:
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
Based on this configuration I would expect to see all UDP connection to timeout after 2 minutes and ICMP connections after only 2 seconds. Yet I see alot of ICMP- and UDP-connections in my connection table that are alot older than these limits. In fact all these connections do time out after 1 hour exactly. I don't believe this is expected behaviour, but I am not sure. However I get close to the platform connection limit, so I would prefer the UDP and ICMP connections to ageout more aggressively.
Do you have any idea if this the correct behaviour?
Best regards
pille
Solved! Go to Solution.
03-16-2015 12:12 PM
Hi Pille,
I haven't tried but logically that should be the way forward.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-15-2015 05:06 PM
Hi Pille,
The timeout command is global command and the values should take effect globally to all traffic unless you have configured other timeout values for traffic using "set connection timeout". Kindly check on that.
http://www.cisco.com/c/en/us/td/docs/security/asa/asa82/configuration/guide/config/conns_connlimits.html
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-16-2015 01:48 AM
Hi,
thank you for your response. I do have configured the following global policy:
class-map global-class
match any
policy-map global_policy
class global-class
set connection timeout idle 1:00:00 reset dcd 0:15:00 5
set connection decrement-ttl
Does this configuration change the behaviour of UDP connections? It was my understanding that DCD is only working for TCP and not UDP or ICMP, but looking at the CLI commands I am not sure anymore.
Regards Pille
03-16-2015 07:15 AM
Hi Pille,
You have selected idle which will apply to all protocols. You need to specifiy TCP if you want it to take effect only on TCP. From the link i sent:
The idle hh:mm:ss keyword sets the idle timeout for all protocols between 0:5:0 and 1193:00:00. The default is 1:0:0. You can also set this value to 0, which means the connection never times out. For TCP traffic, the reset keyword sends a reset to TCP endpoints when the connection times out.
You should use something like:
hostname(config-pmap-c)# set connection timeout tcp x:x:x
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-16-2015 09:56 AM
Hallo,
the keyword tcp is not available with ASA 9.1(5):
ASA/pri/act/CONTEXT(config-pmap-c)# set connection timeout ? mpf-policy-map-class mode commands/options: dcd Configure dead-connection-detection retry interval. embryonic Configure absolute time after which an embryonic TCP connection will be closed, default is 0:00:30. half-closed Configure idle time after which a TCP half-closed connection will be freed, default is 0:10:00 idle Configure idle time after which a connection state will be closed. ASA/pri/act/CONTEXT(config-pmap-c)# set connection timeout
As a workaround I probably have to surrender the global class and use separte classes for UDP, TCP and ICMP, do you agree?
Regards Pille
03-16-2015 12:12 PM
Hi Pille,
I haven't tried but logically that should be the way forward.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-16-2015 01:39 PM
Thanks for your help.
Regards Pille
05-01-2020 08:51 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide