<?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 in VMware. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302104#M78768</link>
    <description>&lt;P&gt;Sorted I think.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Combination of not having the "promiscuous mode enabled" on the v-switch port group, and one of the two endpoints havign windows firewall on for some obscure reason.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rp.png" style="width: 955px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/22828iACA1781E4E2903A5/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="rp.png" alt="rp.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Dec 2019 12:02:09 GMT</pubDate>
    <dc:creator>RobinClayton</dc:creator>
    <dc:date>2019-12-04T12:02:09Z</dc:date>
    <item>
      <title>V-Wire in VMware.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/301907#M78735</link>
      <description>&lt;P&gt;I am trying to trial V-Wire for an upcoming requirement .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The final goal is to secure a number of VMware VM's on their original IP's [differing subnets ] behind a v-wire.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I have a VM100 which I have assigned 2 interfaces&lt;/P&gt;&lt;P&gt;one&amp;nbsp; &amp;nbsp;to a vswitch connected to a virtual PC 192.x.x.5&amp;nbsp;&lt;/P&gt;&lt;P&gt;other to a vswtich connected to a virtual server 192.x.x.10&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;there's rules in both directions to pass all traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But a simple ping either way fails, does not even show up in the log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not sure if it's a VMWare related issue or some thing on the PA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2019 17:16:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/301907#M78735</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2019-12-03T17:16:10Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire in VMware.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/301930#M78739</link>
      <description>&lt;P&gt;Is this an NSX-integrated deployment from Panorama, or just a stand-alone VM?&amp;nbsp; Also, how many virtual interfaces did you add to the VM?&amp;nbsp; The first will go the the management port, the second to first Ethernet interface, third to the second Ethernet interface, etc.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2019 17:48:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/301930#M78739</guid>
      <dc:creator>OwenFuller</dc:creator>
      <dc:date>2019-12-03T17:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire in VMware.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302042#M78760</link>
      <description>&lt;P&gt;It's not NSX, that would solve my issue full stop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The VM100 works fine for normal test traffic, been in place for a few years.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just V-Wire I am having difficulty with.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SUBNET on the V-Wire is on the same IP range as the management interface, but should that be an issue???&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 08:25:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302042#M78760</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2019-12-04T08:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire in VMware.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302104#M78768</link>
      <description>&lt;P&gt;Sorted I think.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Combination of not having the "promiscuous mode enabled" on the v-switch port group, and one of the two endpoints havign windows firewall on for some obscure reason.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rp.png" style="width: 955px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/22828iACA1781E4E2903A5/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="rp.png" alt="rp.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 12:02:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302104#M78768</guid>
      <dc:creator>RobinClayton</dc:creator>
      <dc:date>2019-12-04T12:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: V-Wire in VMware.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302130#M78778</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71756"&gt;@RobinClayton&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;The SUBNET on the V-Wire is on the same IP range as the management interface, but should that be an issue???&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;No, I've done several VMs where the mgmt inerface is in the same range, though w/ L3 interfaces, not v-wire.&amp;nbsp; I was just assuming it was a new VM, and wanting to make sure you took that into account when adding virtual interfaces.&amp;nbsp; Glad you got it sorted.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 14:30:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/v-wire-in-vmware/m-p/302130#M78778</guid>
      <dc:creator>OwenFuller</dc:creator>
      <dc:date>2019-12-04T14:30:17Z</dc:date>
    </item>
  </channel>
</rss>

