HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect Ethernet traffic between servers

Trusted Contributor

Virtual Connect Ethernet traffic between servers

Chad had a Virtual Connect question:




I know that when not defining an uplink port, either directly or via a SUS, that traffic will stay within the VC domain. What about for traffic between two networks that are isolated from each other via VLANs? It needs to go back to the uplink port correct? Or can VC remove the tag and pass the traffic locally as well, say in Mapped Mode?




Cullen replied:




Virtual Connect will not bridge or route traffic between two networks.  Any traffic on “network a” destined for “network b” would have to go through an uplink and through some external device (bridge, switch, or router as needed) then go back to the Virtual Connect domain through the appropriate uplinks.  Note that this is true even if two networks have the same VLAN ID – for example, if you’ve created “network a” which transmits VLAN 200 through one shared uplink set and “network b” which transmits VLAN 200 through a second shared uplink set.




Comments or other suggestions or input?