<?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 Remark/Description increasing exponentially in asa 8.2(5) - ASA5 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795719#M494207</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;-------------------------------------------------------------------------------------------------------------------------------------------------&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CSCtn88072&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access rule description replication issue&lt;/P&gt;&lt;P&gt;Symptom:&lt;/P&gt;&lt;P&gt;description (remark) line for rule is replicated multiple times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conditions:&lt;/P&gt;&lt;P&gt;using same text on multiple lines of the description (remark) field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workaround:&lt;/P&gt;&lt;P&gt;don't use same text on multiple lines of the rule description (remark).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--------------------------------------------------------------------------------------------------------------------------------------------------&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: 0.25in;"&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;•1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Delete all the repeated remarks from the configuration&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;•2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Reconfigure the remark in such a way that for each acl it should be different.&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P style="margin-left: 1in;"&gt;For ex.&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS_1&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in extended permit tcp object-group NOC_TS_GROUP object-group AXIS_PTC_SRVR_GRP_1 eq 3389&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS_2&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in extended permit udp host 192.168.x.x host 192.168.y.y eq 9996&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;•3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You can configure according to your way differently but it should be different for each ACL.&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Nov 2011 07:41:47 GMT</pubDate>
    <dc:creator>amitmarathe</dc:creator>
    <dc:date>2011-11-04T07:41:47Z</dc:date>
    <item>
      <title>Remark/Description increasing exponentially in asa 8.2(5) - ASA5550</title>
      <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795716#M494189</link>
      <description>&lt;P&gt;Remark/Description are increasing exponentially in ASA firewall and it is increasing configuration file size. Also observation is that it is happening for only one access list. Following are some of the remark which are repeating...&lt;/P&gt;&lt;P&gt;I try to find out any bug related to this but could not find.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is observed in ASDM and in the CLI as well. Approx. more that 3000 lines has been created and it is still increasing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please revert how to address and resolve this case....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Device Manager Version 6.4(5)&lt;/P&gt;&lt;P&gt;disk0:/asa825-k8.bin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal ATA Compact Flash, 256MB&lt;BR /&gt;BIOS Flash M50FW080 @ 0xffe00000, 1024KB&lt;/P&gt;&lt;P&gt;Encryption hardware device : Cisco ASA-55x0 on-board accelerator (revision 0x0)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Boot microcode&amp;nbsp;&amp;nbsp; : CN1000-MC-BOOT-2.00 &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IPSec microcode&amp;nbsp; : CNlite-MC-IPSECm-MAIN-2.05&lt;/P&gt;&lt;P&gt;0: Ext: GigabitEthernet0/0&amp;nbsp; : address is 0021.a09a.b3d2, irq 9&lt;BR /&gt;1: Ext: GigabitEthernet0/1&amp;nbsp; : address is 0021.a09a.b3d3, irq 9&lt;BR /&gt;2: Ext: GigabitEthernet0/2&amp;nbsp; : address is 0021.a09a.b3d4, irq 9&lt;BR /&gt;3: Ext: GigabitEthernet0/3&amp;nbsp; : address is 0021.a09a.b3d5, irq 9&lt;BR /&gt;4: Ext: Management0/0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0021.a09a.b3d6, irq 11&lt;BR /&gt;5: Int: Internal-Data0/0&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0000.0001.0002, irq 11&lt;BR /&gt;6: Int: Not used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : irq 5&lt;BR /&gt;7: Ext: GigabitEthernet1/0&amp;nbsp; : address is 0021.a09a.ca90, irq 255&lt;BR /&gt;8: Ext: GigabitEthernet1/1&amp;nbsp; : address is 0021.a09a.ca91, irq 255&lt;BR /&gt;9: Ext: GigabitEthernet1/2&amp;nbsp; : address is 0021.a09a.ca92, irq 255&lt;BR /&gt;10: Ext: GigabitEthernet1/3&amp;nbsp; : address is 0021.a09a.ca93, irq 255&lt;BR /&gt;11: Int: Internal-Data1/0&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0000.0003.0002, irq 255&lt;/P&gt;&lt;P&gt;Licensed features for this platform:&lt;BR /&gt;Maximum Physical Interfaces&amp;nbsp;&amp;nbsp;&amp;nbsp; : Unlimited &lt;BR /&gt;Maximum VLANs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 250&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Inside Hosts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Unlimited &lt;BR /&gt;Failover&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Active/Active&lt;BR /&gt;VPN-DES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;BR /&gt;VPN-3DES-AES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Security Contexts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 5&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;GTP/GPRS&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;BR /&gt;SSL VPN Peers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Total VPN Peers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 5000&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Shared License&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;BR /&gt;AnyConnect for Mobile&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;BR /&gt;AnyConnect for Cisco VPN Phone : Disabled&amp;nbsp; &lt;BR /&gt;AnyConnect Essentials&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;BR /&gt;Advanced Endpoint Assessment&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;BR /&gt;UC Phone Proxy Sessions&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Total UC Proxy Sessions&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;Botnet Traffic Filter&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;/P&gt;&lt;P&gt;This platform has an ASA 5550 VPN Premium license.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amit Marathe&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:45:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795716#M494189</guid>
      <dc:creator>amitmarathe</dc:creator>
      <dc:date>2019-03-11T21:45:41Z</dc:date>
    </item>
    <item>
      <title>Remark/Description increasing exponentially in asa 8.2(5) - ASA5</title>
      <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795717#M494191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For what it's worth, I've run into this when using the wrong version of ASDM.&amp;nbsp; For example, ASDM 6.4(5) with ASA 8.2(5).&amp;nbsp; The correct version of ASDM would be 6.4(3).&amp;nbsp; This has also caused me some other problems, like mysterios disappearing ACL entries. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's my fault for having some ASA's in the 8.3/8.4 train and some back in 8.2.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Still, it's such a pain.&amp;nbsp; It would be helpful if Cisco would simply match up the ASA and ASDM version numbers! I'm sure there is a good reason for them not doing this. Or at least there better be.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2011 14:48:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795717#M494191</guid>
      <dc:creator>rrfield</dc:creator>
      <dc:date>2011-11-03T14:48:35Z</dc:date>
    </item>
    <item>
      <title>Remark/Description increasing exponentially in asa 8.2(5) - ASA5</title>
      <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795718#M494201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stick with the command line &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2011 19:44:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795718#M494201</guid>
      <dc:creator>caseth0102</dc:creator>
      <dc:date>2011-11-03T19:44:07Z</dc:date>
    </item>
    <item>
      <title>Remark/Description increasing exponentially in asa 8.2(5) - ASA5</title>
      <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795719#M494207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;-------------------------------------------------------------------------------------------------------------------------------------------------&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CSCtn88072&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access rule description replication issue&lt;/P&gt;&lt;P&gt;Symptom:&lt;/P&gt;&lt;P&gt;description (remark) line for rule is replicated multiple times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conditions:&lt;/P&gt;&lt;P&gt;using same text on multiple lines of the description (remark) field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workaround:&lt;/P&gt;&lt;P&gt;don't use same text on multiple lines of the rule description (remark).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--------------------------------------------------------------------------------------------------------------------------------------------------&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: 0.25in;"&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;•1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Delete all the repeated remarks from the configuration&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;•2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Reconfigure the remark in such a way that for each acl it should be different.&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P style="margin-left: 1in;"&gt;For ex.&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS_1&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in extended permit tcp object-group NOC_TS_GROUP object-group AXIS_PTC_SRVR_GRP_1 eq 3389&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in remark AXIS ROUTERS MONITORING ACCESS and NETFLOW ACCESS_2&lt;/P&gt;&lt;P style="margin-left: 1in;"&gt;access-list FSL_WHITE_ZONE_access_in extended permit udp host 192.168.x.x host 192.168.y.y eq 9996&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;•3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You can configure according to your way differently but it should be different for each ACL.&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2011 07:41:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795719#M494207</guid>
      <dc:creator>amitmarathe</dc:creator>
      <dc:date>2011-11-04T07:41:47Z</dc:date>
    </item>
    <item>
      <title>Remark/Description increasing exponentially in asa 8.2(5) - ASA5</title>
      <link>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795720#M494214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for sharing this information. I assume that was the bug, I just saw it on versions 8.4. I am sure this will help a lot of people. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Nov 2011 05:40:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remark-description-increasing-exponentially-in-asa-8-2-5-asa5550/m-p/1795720#M494214</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-11-05T05:40:35Z</dc:date>
    </item>
  </channel>
</rss>

