<?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 How Best to Test ASA Configuration? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-best-to-test-asa-configuration/m-p/2104227#M392975</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess this mostly depends how complex each context is going to be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only thing I can think of at the moment would be the "packet-tracer" command on the CLI. Same can be found on the ASDM side also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What this command does is that it shows you what rules/configurations/translations the ASA would apply to the packet if it were to enter the&amp;nbsp; ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic command format is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input &lt;INTERFACE&gt; &lt;PROTOCOL&gt; &lt;SOURCE ip=""&gt; &lt;SOURCE port=""&gt; &lt;DESTINATION ip=""&gt; &lt;DESTINATION port=""&gt;&lt;/DESTINATION&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/SOURCE&gt;&lt;/PROTOCOL&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;interface = The source interface where the connection would come from&lt;/LI&gt;&lt;LI&gt;protocol = Usually TCP/UDP/ICMP&lt;/LI&gt;&lt;LI&gt;source IP = Source IP address for the connection&lt;/LI&gt;&lt;LI&gt;source port = Random source port for the connection&lt;/LI&gt;&lt;LI&gt;destination IP = Destination IP address for the connection&lt;/LI&gt;&lt;LI&gt;destination port = Destination port for the connection&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I personally use the above command to test NAT rules quite often after I've done some changes. I might also use it in cases where I have a large ACL on an interface and want to quickly test if a certain connection would pass the ACL and to which ACL line it would "hit".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used this command quite a lot in my biggest migration project from pre 8.2 environment to post 8.3 environment. This was mostly because I didnt use any tool to convert the NAT rules but just went through them one by one and when I was done I confirmed with "packet-tracer" that everything was working OK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the end I ended up with only 1 NAT that wasnt working but it was simply due to Copy/Paste problems. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; Had a wrong destination interface in a Static NAT command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are naturally alot of commands to go through the firewall when you have configured it but I would say that "packet-tracer" command gives the most information out of all of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please do rate if you found the information helpfull and/or ask more questions. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 13 Jan 2013 20:43:45 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-01-13T20:43:45Z</dc:date>
    <item>
      <title>How Best to Test ASA Configuration?</title>
      <link>https://community.cisco.com/t5/network-security/how-best-to-test-asa-configuration/m-p/2104226#M392974</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm about to set up as ASA configuration with GNS3 ASA's(see link/attachment). Can someone please show how to best test the configuration once complete?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need something like a verification plan to ensure that the configuration would perform if in production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively, if you could point me to sample ASA configurations that include a verification or test plan that would also be great.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Carlton&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808d2b63.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808d2b63.shtml&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:46:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-best-to-test-asa-configuration/m-p/2104226#M392974</guid>
      <dc:creator>Carlton Patterson</dc:creator>
      <dc:date>2019-03-12T00:46:25Z</dc:date>
    </item>
    <item>
      <title>How Best to Test ASA Configuration?</title>
      <link>https://community.cisco.com/t5/network-security/how-best-to-test-asa-configuration/m-p/2104227#M392975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess this mostly depends how complex each context is going to be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only thing I can think of at the moment would be the "packet-tracer" command on the CLI. Same can be found on the ASDM side also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What this command does is that it shows you what rules/configurations/translations the ASA would apply to the packet if it were to enter the&amp;nbsp; ASA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic command format is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;packet-tracer input &lt;INTERFACE&gt; &lt;PROTOCOL&gt; &lt;SOURCE ip=""&gt; &lt;SOURCE port=""&gt; &lt;DESTINATION ip=""&gt; &lt;DESTINATION port=""&gt;&lt;/DESTINATION&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/SOURCE&gt;&lt;/PROTOCOL&gt;&lt;/INTERFACE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;interface = The source interface where the connection would come from&lt;/LI&gt;&lt;LI&gt;protocol = Usually TCP/UDP/ICMP&lt;/LI&gt;&lt;LI&gt;source IP = Source IP address for the connection&lt;/LI&gt;&lt;LI&gt;source port = Random source port for the connection&lt;/LI&gt;&lt;LI&gt;destination IP = Destination IP address for the connection&lt;/LI&gt;&lt;LI&gt;destination port = Destination port for the connection&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I personally use the above command to test NAT rules quite often after I've done some changes. I might also use it in cases where I have a large ACL on an interface and want to quickly test if a certain connection would pass the ACL and to which ACL line it would "hit".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used this command quite a lot in my biggest migration project from pre 8.2 environment to post 8.3 environment. This was mostly because I didnt use any tool to convert the NAT rules but just went through them one by one and when I was done I confirmed with "packet-tracer" that everything was working OK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the end I ended up with only 1 NAT that wasnt working but it was simply due to Copy/Paste problems. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; Had a wrong destination interface in a Static NAT command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are naturally alot of commands to go through the firewall when you have configured it but I would say that "packet-tracer" command gives the most information out of all of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please do rate if you found the information helpfull and/or ask more questions. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 Jan 2013 20:43:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-best-to-test-asa-configuration/m-p/2104227#M392975</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-01-13T20:43:45Z</dc:date>
    </item>
  </channel>
</rss>

