- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect sanity check in regards to private...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2013 06:03 AM
05-29-2013 06:03 AM
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.
- Tags:
- VLAN