<?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: Palo Alto consolidate interface and Panorama connection in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530247#M109426</link>
    <description>Thanks for the clarification, which mean while Panorama pushing config down to Palo Alto it like normal commit process that the Palo Alto still continue commit new configuration, just that I require to disable the auto commit recovery to avoid Palo Alto rollback to old configuration when it lost connection with Panorama.&lt;BR /&gt;</description>
    <pubDate>Wed, 08 Feb 2023 06:20:16 GMT</pubDate>
    <dc:creator>VLim</dc:creator>
    <dc:date>2023-02-08T06:20:16Z</dc:date>
    <item>
      <title>Palo Alto consolidate interface and Panorama connection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530039#M109393</link>
      <description>&lt;P&gt;refer picture below , client plan to consolidate their existing 1gig link to 10 gig link&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Migration.jpg" style="width: 900px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47685i9F765C72F1CED300/image-dimensions/900x312/is-moderation-mode/true?v=v2" width="900" height="312" role="button" title="Migration.jpg" alt="Migration.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Information&lt;/P&gt;
&lt;P&gt;1. Palo Alto is manage by Panorama&lt;/P&gt;
&lt;P&gt;2. Palo Alto configure using default service route which is management IP 10.2.1.0/24&lt;/P&gt;
&lt;P&gt;3. Client would like to consolidate the transit and Mgmt interface&lt;/P&gt;
&lt;P&gt;4. Traffic from Panorama to Palo Alto management is via the transit interface at Palo Alto&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question&lt;/P&gt;
&lt;P&gt;1. When perform consolidation, Panorama midst pushing configuration to Palo Alto and interface changed will this cause the connection between Panorama and Palo Alto break ? The configuration cant completely deploy will cause the connection interuptted&lt;/P&gt;
&lt;P&gt;2. If will cause outages, what is the best solution to consolidate the interface ?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 01:40:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530039#M109393</guid>
      <dc:creator>VLim</dc:creator>
      <dc:date>2023-02-07T01:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto consolidate interface and Panorama connection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530152#M109408</link>
      <description>&lt;P&gt;Good Day&lt;/P&gt;
&lt;P&gt;If I understand your question correctly, you are concerned that if/when you change interfaces (to consolidate them) that this will break connectivity and perhaps get a failure.&amp;nbsp; Allow me to explain that the Panorama will push the updated template information to the FW.&amp;nbsp; You could ensure that the auto commit recovery parameters are changed, to allow for the push to be completed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me give example. I did a project where a remote FW was only accessible via a site to site VPN.&amp;nbsp; When we needed to change the key, it would disconnect the FW, break the VPN, and then the FW would auto commit recover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have unchecked this box before, disconnected my FW from Panorma due to the change and then established my VPN, and then activated the Enable automated commit recovery button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SteveCantwell_0-1675789414842.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47698iE8288C706A38410F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SteveCantwell_0-1675789414842.png" alt="SteveCantwell_0-1675789414842.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I think this is what you need to do for your config as well.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 17:06:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530152#M109408</guid>
      <dc:creator>S.Cantwell</dc:creator>
      <dc:date>2023-02-07T17:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto consolidate interface and Panorama connection</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530247#M109426</link>
      <description>Thanks for the clarification, which mean while Panorama pushing config down to Palo Alto it like normal commit process that the Palo Alto still continue commit new configuration, just that I require to disable the auto commit recovery to avoid Palo Alto rollback to old configuration when it lost connection with Panorama.&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Feb 2023 06:20:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-consolidate-interface-and-panorama-connection/m-p/530247#M109426</guid>
      <dc:creator>VLim</dc:creator>
      <dc:date>2023-02-08T06:20:16Z</dc:date>
    </item>
  </channel>
</rss>

