<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic switch-mode or no normalization for assymetric traffic and what about inactivity timeout? in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/switch-mode-or-no-normalization-for-assymetric-traffic-and-what/m-p/2097140#M39271</link>
    <description>&lt;P&gt;We have to use no normalization, no icmp-guard on ACE 5(2.0) to allow a One-Arm config to allow asymmetric traffic, i.e. everything of some rservers needs to go through the alias ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now this works but the connection table fills up pretty quickly and could reach the maximum within a minute. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I don't know what happens if the concurrent connection table is full, i.e. reaches the max -&amp;gt; some aggressive timout?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The connections have all the standard default 3600 seconds. I have a case open but the TAC engineer says the timeout of those connections cannot be controlled. And I just saw on this forum someone talking about a switch-mode and it's default timeout of 2 hours 15 minutes for everything, but it is configurable. And I read something about that normalization is disabled on those connections if switch-mode is enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So can I use either "no normalization, no icmp-guard" OR "switch-mode"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are the differences, what are the other effects, if any?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if using switch-mode I could configure "switch-mode timeout 30" or less? But I don't really know which long lasting connections we might face.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would it be possible to set up some class-map that matches traffic of the alias IP and assign a different inactivity timeout?&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jan 2013 10:11:35 GMT</pubDate>
    <dc:creator>pweichmann</dc:creator>
    <dc:date>2013-01-21T10:11:35Z</dc:date>
    <item>
      <title>switch-mode or no normalization for assymetric traffic and what about inactivity timeout?</title>
      <link>https://community.cisco.com/t5/application-networking/switch-mode-or-no-normalization-for-assymetric-traffic-and-what/m-p/2097140#M39271</link>
      <description>&lt;P&gt;We have to use no normalization, no icmp-guard on ACE 5(2.0) to allow a One-Arm config to allow asymmetric traffic, i.e. everything of some rservers needs to go through the alias ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now this works but the connection table fills up pretty quickly and could reach the maximum within a minute. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I don't know what happens if the concurrent connection table is full, i.e. reaches the max -&amp;gt; some aggressive timout?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The connections have all the standard default 3600 seconds. I have a case open but the TAC engineer says the timeout of those connections cannot be controlled. And I just saw on this forum someone talking about a switch-mode and it's default timeout of 2 hours 15 minutes for everything, but it is configurable. And I read something about that normalization is disabled on those connections if switch-mode is enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So can I use either "no normalization, no icmp-guard" OR "switch-mode"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are the differences, what are the other effects, if any?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if using switch-mode I could configure "switch-mode timeout 30" or less? But I don't really know which long lasting connections we might face.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would it be possible to set up some class-map that matches traffic of the alias IP and assign a different inactivity timeout?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jan 2013 10:11:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/switch-mode-or-no-normalization-for-assymetric-traffic-and-what/m-p/2097140#M39271</guid>
      <dc:creator>pweichmann</dc:creator>
      <dc:date>2013-01-21T10:11:35Z</dc:date>
    </item>
    <item>
      <title>switch-mode or no normalization for assymetric traffic and what</title>
      <link>https://community.cisco.com/t5/application-networking/switch-mode-or-no-normalization-for-assymetric-traffic-and-what/m-p/2097141#M39272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patrick, switch-mode is specifically for connections that do match any class-maps (vips). I see no problem with setting the timeout low (30s). I haven't tested in the lab, but I would expect that any packet (not just the 3 way handshake) would create an entry. ie: if a connection under the control of switch-mode was cleared by timeout, the next packet would create a new entry. You can setup class-map to match on various trafifc types and assign a different timeout. Can you share the config and the conection details (src/dst ip and port) that you are concerned about. Matthew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2013 13:13:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/switch-mode-or-no-normalization-for-assymetric-traffic-and-what/m-p/2097141#M39272</guid>
      <dc:creator>mwinnett</dc:creator>
      <dc:date>2013-02-14T13:13:10Z</dc:date>
    </item>
  </channel>
</rss>

