<?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: Testing Firewall before cutover from production in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129152#M1113518</link>
    <description>&lt;P&gt;are you joking? if have a 10000 line firewall config.. you want to wait for the maint window and mess it up... use packet-tracer to verify if your firewall rules are going to work.. atleast check the heavy hitters.. a great way to test out the rules..&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2024 16:43:31 GMT</pubDate>
    <dc:creator>ccieexpert</dc:creator>
    <dc:date>2024-06-12T16:43:31Z</dc:date>
    <item>
      <title>Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5128854#M1113497</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;I have a brand new Firewall 3105 and we have completed the initial setup and inside and outside interface,route and nat configs. Before the cutover of production traffic from existing firewall I need to test the traffic with Sample policy in the new firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Inside interface is connected to Nexus switch which has a P2P vlan which connects between switch and firewall-inside and all the traffic are pointed towards the firewall inside. I am in plan of creating a Test network and do a PBR for that network alone to get to next hop pointed towards the Inside of new firewall.&lt;/P&gt;&lt;P&gt;But not sure if this will work as expected, any suggestions from your side..?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 06:35:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5128854#M1113497</guid>
      <dc:creator>titusroz03</dc:creator>
      <dc:date>2024-06-12T06:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129030#M1113506</link>
      <description>&lt;P&gt;you have two side&lt;BR /&gt;the IN you can solve as you mention by PBR&amp;nbsp;&lt;BR /&gt;the OUT how you can solve it ?&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 13:45:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129030#M1113506</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-06-12T13:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129135#M1113513</link>
      <description>&lt;P&gt;yes PBR should work as long as you can send the traffic to the firewall inside.. and the outside interface of the firewall is connect to the internet ..maybe using a temporary public ip... Also if the interface is just up both inside and inside.. you can do packet-tracer and will show if a specific policy is working and what policy is matching. this way you dont have to have actual traffic source... &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212474-working-with-firepower-threat-defense-f.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212474-working-with-firepower-threat-defense-f.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 16:12:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129135#M1113513</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-06-12T16:12:45Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129147#M1113516</link>
      <description>&lt;P&gt;dont use packet tracer to test because the always you will get drop for last phase since the ARP is missing from FW.&amp;nbsp;&lt;BR /&gt;test new FW in maintenance window it better&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 16:28:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129147#M1113516</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-06-12T16:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129152#M1113518</link>
      <description>&lt;P&gt;are you joking? if have a 10000 line firewall config.. you want to wait for the maint window and mess it up... use packet-tracer to verify if your firewall rules are going to work.. atleast check the heavy hitters.. a great way to test out the rules..&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 16:43:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5129152#M1113518</guid>
      <dc:creator>ccieexpert</dc:creator>
      <dc:date>2024-06-12T16:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133011#M1113597</link>
      <description>&lt;P&gt;Packet tracer Shows allow for any IP since the traffic is inspected on Snort engine.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 07:25:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133011#M1113597</guid>
      <dc:creator>titusroz03</dc:creator>
      <dc:date>2024-06-18T07:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133013#M1113598</link>
      <description>&lt;P&gt;OUT has default route to exit internet in Firewall. PBR is only on inside switch to allow the test subnet&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 07:26:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133013#M1113598</guid>
      <dc:creator>titusroz03</dc:creator>
      <dc:date>2024-06-18T07:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: Testing Firewall before cutover from production</title>
      <link>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133082#M1113599</link>
      <description>&lt;P&gt;i.e. the New FW have connect to internet ?&lt;/P&gt;
&lt;P&gt;if Yes then in window redirect traffic to new FW and check&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 09:45:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-firewall-before-cutover-from-production/m-p/5133082#M1113599</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-06-18T09:45:31Z</dc:date>
    </item>
  </channel>
</rss>

