<?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: Interface in vsys in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/interface-in-vsys/m-p/188934#M57273</link>
    <description>&lt;P&gt;a single interface can only belong to one vsys, subinterfaces are counted as separate entities&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so in your scenario where you'll only have 2 interfaces per vsys and only 2 vsys, you'd be set with 4 interfaces in total, so there's plenty of room to work with&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but what does your network look like, are the 2 network environments also split up in vlans on one physical switching environment or are does each network have their own physical switch?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sharing a single physical interface over multiple sub-interfaces makes management more wasy as you'll only need to manage a trunk from the switch and add tagged subinterfaces, but may impose bandwidth restrictions as all the subinterfaces share the same physical interfaces (this in itself can be fixed by creating aggregate interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#1 is a viable option, option #2 is not possible, option #3 will require you to start using vlan tagging, but will spare the number of physical interfaces used and allows for easy future expansion&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2017 12:48:50 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2017-11-28T12:48:50Z</dc:date>
    <item>
      <title>Interface in vsys</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/interface-in-vsys/m-p/188927#M57272</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this may sound like a stupid question but i could not somehow find a definitive answer to this in the PAN OS Guide:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have to configure a 3050 iun multi-vsys configuration. We would be needing 2 interfaces per vsys and we wil be having 2 vsys only. All the interfaces wil be L3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding "physical" interface assignment, what is ALLOWED and recommended?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. One physical interface assigned to one vsys. No sharing of interfaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. One physical interface without subinterfaces added in both the vsys. (Not sure if it is allowed)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Subinterfaces created on one interface and then each subinterface to be assigned for each vsys. (We dont have any vlan tagging actually.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(P.S. Option 1 is feasible but we would also like to spare physical interfaces for future use.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;R&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 12:00:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/interface-in-vsys/m-p/188927#M57272</guid>
      <dc:creator>rjdahav163</dc:creator>
      <dc:date>2017-11-28T12:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Interface in vsys</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/interface-in-vsys/m-p/188934#M57273</link>
      <description>&lt;P&gt;a single interface can only belong to one vsys, subinterfaces are counted as separate entities&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;so in your scenario where you'll only have 2 interfaces per vsys and only 2 vsys, you'd be set with 4 interfaces in total, so there's plenty of room to work with&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but what does your network look like, are the 2 network environments also split up in vlans on one physical switching environment or are does each network have their own physical switch?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sharing a single physical interface over multiple sub-interfaces makes management more wasy as you'll only need to manage a trunk from the switch and add tagged subinterfaces, but may impose bandwidth restrictions as all the subinterfaces share the same physical interfaces (this in itself can be fixed by creating aggregate interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#1 is a viable option, option #2 is not possible, option #3 will require you to start using vlan tagging, but will spare the number of physical interfaces used and allows for easy future expansion&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 12:48:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/interface-in-vsys/m-p/188934#M57273</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-11-28T12:48:50Z</dc:date>
    </item>
  </channel>
</rss>

