- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Connection between Virtual NICS on Virtual Connect...
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
08-11-2010 07:10 AM
08-11-2010 07:10 AM
Connection between Virtual NICS on Virtual Connect Flex-10
Fabio had a Virtual Connect question:
***************************************************************
Specialists,
One question...it is possible to connect two Virtual NICS created on profiles assigned to different blade servers ( on a single Virtual Connect Flex-10 module ), without accessing the external networks ( through the module ) ?
***********************************************************
We had some of the specialists jump into the conversation:
******************************************************************
Rick asked:
Wouldn't you just assign each of the two flexnics to their own vNet (right term?) without an uplink defined?
Steve answered:
Yes, If you have two servers in an enclosure and they do see each other, you can create a vNet with no uplinks, then place one NIC from each server in that vNet. Comms between servers will remain on that module.
Cullen agreed:
If two NICs are attached to the same Virtual Connect network they communicate without the traffic leaving the enclosure. If they are connected two different networks, then the traffic must leave the enclosure and go through a router/gateway.
************************************************************************
A good way to shorten latency and not have to involve the switch infrastructure. And it can be a good way to segment server-to-server traffic.