V-Wire in VMware.

[RobinClayton]

I am trying to trial V-Wire for an upcoming requirement .

The final goal is to secure a number of VMware VM's on their original IP's [differing subnets ] behind a v-wire. 

So I have a VM100 which I have assigned 2 interfaces

one   to a vswitch connected to a virtual PC 192.x.x.5 

other to a vswtich connected to a virtual server 192.x.x.10

there's rules in both directions to pass all traffic.

But a simple ping either way fails, does not even show up in the log.

I am not sure if it's a VMWare related issue or some thing on the PA.

[OwenFuller]

Is this an NSX-integrated deployment from Panorama, or just a stand-alone VM?  Also, how many virtual interfaces did you add to the VM?  The first will go the the management port, the second to first Ethernet interface, third to the second Ethernet interface, etc.

[RobinClayton · Accepted solution]

It's not NSX, that would solve my issue full stop.

The VM100 works fine for normal test traffic, been in place for a few years. 

Just V-Wire I am having difficulty with. 

The SUBNET on the V-Wire is on the same IP range as the management interface, but should that be an issue???

[RobinClayton]

Sorted I think.

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.

 

[OwenFuller]

---

@RobinClayton wrote:

The SUBNET on the V-Wire is on the same IP range as the management interface, but should that be an issue???

---

No, I've done several VMs where the mgmt inerface is in the same range, though w/ L3 interfaces, not v-wire.  I was just assuming it was a new VM, and wanting to make sure you took that into account when adding virtual interfaces.  Glad you got it sorted.