<?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 Enabling multi vsys on a prod firewall. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398307#M91511</link>
    <description>&lt;P&gt;I’m planning to create multi vsys on my palo alto. I just wanted to know if my existing configuration (interfaces, aggregate interfaces and rulebase) will be moved as it is to vsys1 or they need to be mived manually?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have aggregate interfaces layer 2 in my environment so I need to assign vlan interfaces to vsys and keep parent port in no vsys or an admin vsys. Will that work?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Apr 2021 04:33:09 GMT</pubDate>
    <dc:creator>mudassar216</dc:creator>
    <dc:date>2021-04-15T04:33:09Z</dc:date>
    <item>
      <title>Enabling multi vsys on a prod firewall.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398307#M91511</link>
      <description>&lt;P&gt;I’m planning to create multi vsys on my palo alto. I just wanted to know if my existing configuration (interfaces, aggregate interfaces and rulebase) will be moved as it is to vsys1 or they need to be mived manually?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have aggregate interfaces layer 2 in my environment so I need to assign vlan interfaces to vsys and keep parent port in no vsys or an admin vsys. Will that work?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 04:33:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398307#M91511</guid>
      <dc:creator>mudassar216</dc:creator>
      <dc:date>2021-04-15T04:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling multi vsys on a prod firewall.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398412#M91517</link>
      <description>&lt;P&gt;I checked and my assumption about rulebase and configuration part was correct. Everything is under same vsys i.e vsys1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But i’m not sure about assigning aggregate interface with no Vsys, as Every interface needs vsys configuration.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 11:29:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398412#M91517</guid>
      <dc:creator>mudassar216</dc:creator>
      <dc:date>2021-04-15T11:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling multi vsys on a prod firewall.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398833#M91538</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/178581"&gt;@mudassar216&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;So everything you already have configured is technically already in vsys1 outside of shared objects, so nothing really "moves" when you enable multi-vsys as it's already present in the default vsys1. So every interface you have configured, including your aggregate, is already technically in vsys1.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your aggregate interface &lt;EM&gt;needs&lt;/EM&gt; to be assigned to a vsys and can't be left unassigned. I've never honestly tried having the VLANs split out between vsys coming across an AE assigned to another vsys, but I would &lt;EM&gt;guess&lt;/EM&gt; that this would be an invalid configuration.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 23:14:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398833#M91538</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-04-15T23:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling multi vsys on a prod firewall.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398865#M91543</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes the first part is correct. I already tried it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For the aggregate interface, what I did is removed the agg interface itself from under vsys and kept it’s vlan interfaces in required vsys. I was able to do that but I couldn’t test if the setup was working. Will check and confirm.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 01:16:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/enabling-multi-vsys-on-a-prod-firewall/m-p/398865#M91543</guid>
      <dc:creator>mudassar216</dc:creator>
      <dc:date>2021-04-16T01:16:13Z</dc:date>
    </item>
  </channel>
</rss>

