<?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: PVLAN with Palo Alto? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242727#M69417</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You are correct on burning ip's by subnetting. I think its a good question to reach out to your SE to see what they suggest. I'd be interested in the answer myself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Mon, 10 Dec 2018 16:31:22 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2018-12-10T16:31:22Z</dc:date>
    <item>
      <title>PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242629#M69390</link>
      <description>&lt;P&gt;I'm looking at doing some re-design for our DC networks and wanted to investigate some further segmentation.&amp;nbsp; Since we aren't really large enough for NSX or ACI I wanted to look at PVLAN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got some Nexus9K switches with Layer 3 licensing in HA and had originally thought to use them as the gateway for the DC networks.&amp;nbsp; Now though I'm wondering if it wouldn't be just as easy to keep them strictly as Layer 2 and use the Palo Alto A/S HA as the Layer 3 gateway.&amp;nbsp; What I'm not sure on is whether I can do this with a PVLAN configuration?&amp;nbsp; My research on the Cisco whitepaper for PVLAN indicates the container VLAN and all of the isolated/community/etc VLANs have to be tagged to the device with the PVLAN gateway.&amp;nbsp; If that is the case, how to I tell my PAN boxes to treat those as PVLAN and not require an interface or subinterface with IP for anything but the container VLAN?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 09 Dec 2018 04:43:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242629#M69390</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2018-12-09T04:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242680#M69399</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/39461"&gt;@jsalmans&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Are your switches licensed to do VRFs? That might be an easier setup than what you are proposing here while keeping everything isolated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 04:00:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242680#M69399</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-12-10T04:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242685#M69404</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;VRFs are possible and may be an option but I would imagine I'd need to create one per server for true DC host isolation.&amp;nbsp; PVLANs seem much easier to scale since it seems to mostly be a one-and-done configuration on the Layer 2 side.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 06:08:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242685#M69404</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2018-12-10T06:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242724#M69415</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have also worked with this hardware in the past and here is what we did. We created a zone and assigned a subnet to it 192.168.0.0/24. We then carved up the subnet into /29's but kept them in the same zone. Since we have a DENY ALL policy at the bottom of our list prior to the intra zone policy, Unless we explicity allow the traffic between two /29's in the same zone, all traffic is blocked. We found this to be easier than the pvlan option with similar results.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We wanted as close to a zero trust scenario as possible and this was the best one we can up with. All traffic into and out of hte zone /29 is inspected and monitored. and the 9k's only trunk up to the PAN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if you would like additional details.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 15:55:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242724#M69415</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-12-10T15:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242725#M69416</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&amp;nbsp;thanks for the reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe that still burns some exrtra IP addresses... not a big deal on privates but some of these networks may end up on publics.&amp;nbsp; I did see another way to do something like that... OVH has an article on how to configure hosts on their network using network bridging.&amp;nbsp; It looks like they have you assign /32 addresses to each host and the gateway exists outside of that subnet so you have to create a static route for it.&amp;nbsp; I wasn't crazy about that solution because it requires extra config on the hosts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also found this but I'm not clear from the replies if someone got it to work or not:&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/Has-anyone-had-success-using-Cisco-Systems-Private-VLANs-and/m-p/30641#M22429" target="_self"&gt;https://live.paloaltonetworks.com/t5/General-Topics/Has-anyone-had-success-using-Cisco-Systems-Private-VLANs-and/m-p/30641#M22429&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If PVLAN won't work directly on the firewall, my fallback option is to put the SVIs on our Nexus9K and then use policy-based routing to push the traffic the rest of the way to the firewall.&amp;nbsp; It's an extra hop but the Cisco equipment can handle the traffic isolation and push the traffic to the firewall when it receives it.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 16:23:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242725#M69416</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2018-12-10T16:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: PVLAN with Palo Alto?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242727#M69417</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You are correct on burning ip's by subnetting. I think its a good question to reach out to your SE to see what they suggest. I'd be interested in the answer myself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 16:31:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pvlan-with-palo-alto/m-p/242727#M69417</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-12-10T16:31:22Z</dc:date>
    </item>
  </channel>
</rss>

