Quantcast
Channel: VMware Communities: Message List - vSphere™ vNetwork
Viewing all articles
Browse latest Browse all 4189

Problem with PVLANs

$
0
0

Hello,

 

We have set up two types of PvLANs:

 

1.-Promiscuous, primary. The devices integrated in this PvLAN can connect with any other device in that vlan or in any of its secondary vlan, regardless of their nature.

2.- Isolated, secondary. The devices in this PvLAN can only communicate with the devices in the primary vLAN, they don’t see each other.

 

VMware has a PortGroup associated for each of these two PvLANs, apart from the other VLANs’ PortGroups.

 

The problem is:

 

When we make a vMotion to another Host from a virtual machine connected to any of the PvLANs, it loses connectivity to the PvLAN. But if we take the virtual machine back to the original device, it recovers the connectivity with the PvLAN.

If we change the PvLAN’s vNIC, either primary or secondary, to another VLAN (regular VLAN) and back; in other words, you leave it in the PvLAN where it was originally, it won’t have connectivity.

 

However

 

If we change the PvLAN’s vNIC to the other PvLAN (from primary to secondary or from the secondary to the primary and back; in other words, we leave it in the PvLAN where it was at first, it will have connectivity again)

All these issues regardless the machine being connected to the secondary PvLAN, isolated, comunity or connected to the primary, promiscuous.

 

Moreover, from the outside connectivity is not lost. From my machine (physical) I contact a primary VM, we run vmotion and communication continues, but within vSphere platform, that VM (PvLANs) stops communicating unless you perform the procedure explained above.

 

We areusing:

vCenter-Server-Appliance-5.5.0.10000-1624811 andESXi-5.5.0-1623387


Any ideas?


Any help is greatly appreciated. Thanks in advance!


Viewing all articles
Browse latest Browse all 4189

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>