<?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: Aggregated port over Vsys (AE1 over...) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129236#M46750</link>
    <description>&lt;P&gt;correct&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the AE itself&amp;nbsp;is set in a vsys because that is how the configuration works (interfaces are placed in a vsys xpath in the XML config file so the firewall knows they exist) but the ae does not need a configuration for itself, it can be left completely blank while you configure all the subinterfaces in any vsys you like&lt;/P&gt;</description>
    <pubDate>Mon, 28 Nov 2016 10:32:37 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2016-11-28T10:32:37Z</dc:date>
    <item>
      <title>Aggregated port over Vsys (AE1 over...)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/126899#M46567</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm thinking about put som vlans inside and Aggregate, and distribitute over various Vsys, as far I know, reading here in the community, it's possible use subAEinterfaces on different VSYS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then, the question is, on wich VSYS must be the physical interface AE1? AE1.1, AE2.3 will be distributed over Vsys, and no need to put IP on AE1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 00:02:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/126899#M46567</guid>
      <dc:creator>nanukanu</dc:creator>
      <dc:date>2016-11-17T00:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: Aggregated port over Vsys (AE1 over...)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/126997#M46578</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The physical interface does not need to be on any vsys and does not require an IP address&lt;/P&gt;
&lt;P&gt;Since you will be using tagged sub interfaces, there would normally not be untagged traffic hitting this interface and the physical interface would remain unused&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in the case you do have untagged packets, you would need to choose which vsys will receive these&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 10:41:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/126997#M46578</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-11-17T10:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: Aggregated port over Vsys (AE1 over...)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129022#M46739</link>
      <description>Hi,&lt;BR /&gt;Ok, but I can't separate ae1 from vsys, seems mandatory to be attached to one vsys...!&lt;BR /&gt;&lt;BR /&gt;Regards!</description>
      <pubDate>Fri, 25 Nov 2016 17:25:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129022#M46739</guid>
      <dc:creator>nanukanu</dc:creator>
      <dc:date>2016-11-25T17:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Aggregated port over Vsys (AE1 over...)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129025#M46741</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think what reaper was saying is that the interfaces that make up the ae do not need to be assigned a vsys, which they don't. When making an ae you do need it assigned to a vsys just like you would if you configured an additional 'single' interface. You can assigne ae1.2 or whatever other subinterfaces you configure to different vsys and you can import ae1 into whatever vsys you wish but it needs to be assigned somewhere.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Nov 2016 17:57:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129025#M46741</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2016-11-25T17:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: Aggregated port over Vsys (AE1 over...)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129236#M46750</link>
      <description>&lt;P&gt;correct&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the AE itself&amp;nbsp;is set in a vsys because that is how the configuration works (interfaces are placed in a vsys xpath in the XML config file so the firewall knows they exist) but the ae does not need a configuration for itself, it can be left completely blank while you configure all the subinterfaces in any vsys you like&lt;/P&gt;</description>
      <pubDate>Mon, 28 Nov 2016 10:32:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aggregated-port-over-vsys-ae1-over/m-p/129236#M46750</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-11-28T10:32:37Z</dc:date>
    </item>
  </channel>
</rss>

