<?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: V-Wire Mode with trunk in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/80#M62</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I setup v-wire with q tag trunk ports on the 5000 series for a data center deployment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this can be as simple as outlined in this document.&amp;nbsp; Where there is only two zones and all tags are just permitted through the v-wire.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-2729"&gt;Trunked Traffic in a V-Wire&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want more control, you can create a subinterface for each q tag on the v-wire.&amp;nbsp; These can then be placed onto their own v-wire pipe and assigned zones separately from the other q tags on the trunk port.&amp;nbsp; This also prevents the automatic passing of additional tagged frames on the trunk without the explicit configuration of the sub-interface and v-wire pair.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create the v-wire for the tag &lt;/LI&gt;&lt;LI&gt;Create the sub-interface on both physical interfaces and assign the tag and the v-wire&lt;/LI&gt;&lt;LI&gt;Assign each side of the v-wire to the desired zones&lt;/LI&gt;&lt;LI&gt;Rules will then apply by zone assignment of the particular v-wire pairs&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Aug 2014 21:52:06 GMT</pubDate>
    <dc:creator>pulukas</dc:creator>
    <dc:date>2014-08-05T21:52:06Z</dc:date>
    <item>
      <title>V-Wire Mode with trunk</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/78#M60</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i am about to deploy PaloAlto 5020 in a v-wire mode with trunk on them, does any one has any known issues that i may encounter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here is the topology&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Current: switch ====(trunk)===== cisco firewall&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;new: switch======(trunk)=====PaloAlto (vwire)=====(trunk)====Cisco firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;~Harry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2014 18:56:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/78#M60</guid>
      <dc:creator>Harshit</dc:creator>
      <dc:date>2014-08-05T18:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire Mode with trunk</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/79#M61</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Harshit,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Few related information for you: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-1098"&gt;Cisco Link Aggregation Traffic Through a PAN Device&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-3594"&gt;Which Link Aggregation Protocols are Supported?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/26986"&gt;LACP LAG&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/message/33156"&gt;LACP support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2014 20:04:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/79#M61</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-08-05T20:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire Mode with trunk</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/80#M62</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I setup v-wire with q tag trunk ports on the 5000 series for a data center deployment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this can be as simple as outlined in this document.&amp;nbsp; Where there is only two zones and all tags are just permitted through the v-wire.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-2729"&gt;Trunked Traffic in a V-Wire&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want more control, you can create a subinterface for each q tag on the v-wire.&amp;nbsp; These can then be placed onto their own v-wire pipe and assigned zones separately from the other q tags on the trunk port.&amp;nbsp; This also prevents the automatic passing of additional tagged frames on the trunk without the explicit configuration of the sub-interface and v-wire pair.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create the v-wire for the tag &lt;/LI&gt;&lt;LI&gt;Create the sub-interface on both physical interfaces and assign the tag and the v-wire&lt;/LI&gt;&lt;LI&gt;Assign each side of the v-wire to the desired zones&lt;/LI&gt;&lt;LI&gt;Rules will then apply by zone assignment of the particular v-wire pairs&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2014 21:52:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-mode-with-trunk/m-p/80#M62</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-08-05T21:52:06Z</dc:date>
    </item>
  </channel>
</rss>

