tag:blogger.com,1999:blog-1040476408272754799.post2752048268706139528..comments2024-02-15T04:35:09.937+11:00Comments on Virtualcloudz: Steps to configure PVLANs in combination of Cisco, HP VC, and VMware dVS virtualcloudzhttp://www.blogger.com/profile/00298699104880791462noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1040476408272754799.post-18009594348540334152017-10-28T03:08:30.829+11:002017-10-28T03:08:30.829+11:00This seems to work fine in an all VMware enclosure...This seems to work fine in an all VMware enclosure, but what about if you have a mix of VMware hosts, and a few blades running a full OS (such as RHEL) in the enclosure? Virtual Connect seems to hijack the isolated VLAN and still allow it between the other blade servers since VC knows nothing about the PVLAN configuration. This is our situation. I'm going to try to set up the SUS in tunnel mode and see if that works. According to the VC documentation, VC prevents hair-pinning, so this may not work as desired either. PVLANs are tricky when you are running a mix of VMware, Hyper-V, and non-hypervisor OSs all running in the same enclosure, and all of them need to respect the PVLAN isolation!Anonymousnoreply@blogger.com