<?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 Re: Enabling the Asymmetric mode processing, IPS 6.0(4)E1 Releas in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/enabling-the-asymmetric-mode-processing-ips-6-0-4-e1-release/m-p/996791#M79693</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I never implemented it, but I'm assuming it works because they have introduced this as a CLI command in 6.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the readme text:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"To support inline asymmetric traffic in earlier 6.0(x) releases, a&lt;/P&gt;&lt;P&gt;  manual workaround was documented in the 6.0(4) readme file (refer &lt;/P&gt;&lt;P&gt;  to the Resolved Caveats section of the  6.0(4) readme for details). &lt;/P&gt;&lt;P&gt;  In the IPS 6.1 release, this functionality is now configurable via &lt;/P&gt;&lt;P&gt;  the sensor CLI or IDM.  If you utilized the workaround to enable &lt;/P&gt;&lt;P&gt;  asymmetric traffic, the manual setting should be removed and &lt;/P&gt;&lt;P&gt;  asymmetric traffic should be re-enabled as in the following example &lt;/P&gt;&lt;P&gt;  using the CLI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  sensor-xyz(config)# ser analysis-engine&lt;/P&gt;&lt;P&gt;  sensor-xyz(config-ana)# vi vs0&lt;/P&gt;&lt;P&gt;  sensor-xyz(config-ana-vir)# inline-TCP-evasion-protection-mode ?&lt;/P&gt;&lt;P&gt;  strict Full TCP ordering and sequence checking will be applied to &lt;/P&gt;&lt;P&gt;         all TCP sessions on this virtual sensor.&lt;/P&gt;&lt;P&gt;  asymmetric   Relaxed TCP ordering and sequence checking will be &lt;/P&gt;&lt;P&gt;         applied to all TCP sessions on this virtual sensor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  For more details regarding asymmetric traffic, refer to the &lt;/P&gt;&lt;P&gt;  "Configuring the Cisco IPS Sensor Using the CLI IPS 6.1" on-line &lt;/P&gt;&lt;P&gt;  user guide available at:&lt;/P&gt;&lt;P&gt;  &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Note: If the manual entry in the sensorApp.conf file is not removed,&lt;/P&gt;&lt;P&gt;  the following main.log warning will be generated each time the sensor&lt;/P&gt;&lt;P&gt;  is rebooted:&lt;/P&gt;&lt;P&gt;  NormalizerSettings in sensorApp.conf (AsynchMode and AsymmetricFlows)&lt;/P&gt;&lt;P&gt;  have been removed.  Use Service AnalysisEngine - VS - &lt;/P&gt;&lt;P&gt;  inline-TCP-evasion-protection-mode."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2008 12:56:26 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2008-06-19T12:56:26Z</dc:date>
    <item>
      <title>Enabling the Asymmetric mode processing, IPS 6.0(4)E1 Release</title>
      <link>https://community.cisco.com/t5/network-security/enabling-the-asymmetric-mode-processing-ips-6-0-4-e1-release/m-p/996790#M79691</link>
      <description>&lt;P&gt;I was wondering if someone tried to implement this fix provided in 6.0.4 to relax the normilizer engine for asymmetric mode processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this fix impact the functionality of active signatures ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Allow inline Asymmetric traffic (CSCsi72263)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AnalysisEngine was modified to allow asymmetric traffic to be tracked and analyzed &lt;/P&gt;&lt;P&gt;by allowing for a relaxed Normalization process versus using the standard Normalizer. &lt;/P&gt;&lt;P&gt;This results in the ability to install the sensor inline in situations where the Normalizer would block or delay traffic due to the strict nature of stream processing and â&amp;#128;&amp;#156;normalizationâ&amp;#128;&amp;#157; by not doing any protocol checking or packet reordering.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:09:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-the-asymmetric-mode-processing-ips-6-0-4-e1-release/m-p/996790#M79691</guid>
      <dc:creator>cmhcsecurity</dc:creator>
      <dc:date>2019-03-10T11:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling the Asymmetric mode processing, IPS 6.0(4)E1 Releas</title>
      <link>https://community.cisco.com/t5/network-security/enabling-the-asymmetric-mode-processing-ips-6-0-4-e1-release/m-p/996791#M79693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I never implemented it, but I'm assuming it works because they have introduced this as a CLI command in 6.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the readme text:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"To support inline asymmetric traffic in earlier 6.0(x) releases, a&lt;/P&gt;&lt;P&gt;  manual workaround was documented in the 6.0(4) readme file (refer &lt;/P&gt;&lt;P&gt;  to the Resolved Caveats section of the  6.0(4) readme for details). &lt;/P&gt;&lt;P&gt;  In the IPS 6.1 release, this functionality is now configurable via &lt;/P&gt;&lt;P&gt;  the sensor CLI or IDM.  If you utilized the workaround to enable &lt;/P&gt;&lt;P&gt;  asymmetric traffic, the manual setting should be removed and &lt;/P&gt;&lt;P&gt;  asymmetric traffic should be re-enabled as in the following example &lt;/P&gt;&lt;P&gt;  using the CLI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  sensor-xyz(config)# ser analysis-engine&lt;/P&gt;&lt;P&gt;  sensor-xyz(config-ana)# vi vs0&lt;/P&gt;&lt;P&gt;  sensor-xyz(config-ana-vir)# inline-TCP-evasion-protection-mode ?&lt;/P&gt;&lt;P&gt;  strict Full TCP ordering and sequence checking will be applied to &lt;/P&gt;&lt;P&gt;         all TCP sessions on this virtual sensor.&lt;/P&gt;&lt;P&gt;  asymmetric   Relaxed TCP ordering and sequence checking will be &lt;/P&gt;&lt;P&gt;         applied to all TCP sessions on this virtual sensor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  For more details regarding asymmetric traffic, refer to the &lt;/P&gt;&lt;P&gt;  "Configuring the Cisco IPS Sensor Using the CLI IPS 6.1" on-line &lt;/P&gt;&lt;P&gt;  user guide available at:&lt;/P&gt;&lt;P&gt;  &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/tsd_products_support_series_home.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Note: If the manual entry in the sensorApp.conf file is not removed,&lt;/P&gt;&lt;P&gt;  the following main.log warning will be generated each time the sensor&lt;/P&gt;&lt;P&gt;  is rebooted:&lt;/P&gt;&lt;P&gt;  NormalizerSettings in sensorApp.conf (AsynchMode and AsymmetricFlows)&lt;/P&gt;&lt;P&gt;  have been removed.  Use Service AnalysisEngine - VS - &lt;/P&gt;&lt;P&gt;  inline-TCP-evasion-protection-mode."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2008 12:56:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-the-asymmetric-mode-processing-ips-6-0-4-e1-release/m-p/996791#M79693</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-19T12:56:26Z</dc:date>
    </item>
  </channel>
</rss>

