Virtual Connect sanity check in regards to private \ non-private network (227 Views)
Neighborhood Admin
Posts: 4,021
Registered: ‎01-09-2007
Message 1 of 1 (227 Views)

Virtual Connect sanity check in regards to private \ non-private network

Eirik had a customer question:




I had a customer ask me a question the other day that I am not entirely sure about, hopefully someone knows the capabilities of the VC.



Scenario :


Server X (Fileserver) speaks to server Y (Terminalserver), server X speaks on vlan 1110, server Y speaks on vlan 1120, for the communication to happen, does the traffic leave the VC-module ?



None of the Ethernet networks are defined as private.


In other words, does the VC do routing on the VLAN level or does the communication have to leave the VC, go upstream, come back, pass the VC and return to the neighbor blade?




Input from Kant:




Virtual Connect is pure L2 bridge with East/West aka local switching based on L2. All routing  level  requirements should be addressed by L3 switch or router. This has been documented in “HP Virtual Connect: Common Myths, Misperceptions, and Objections”,  look for #18 VC Ethernet doesn’t provide Layer 3 routing capabilities.




So, in Eirik's customer case, the traffic would have to travel to the upstream switch. If the customer had just a single VLAN defined, say VLAN#1120 and both servers used this VLAN for communication and the VLAN#1120 never went to an upstream switch, then the 2 servers would communicate without the need of an upstream switch.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.