- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Private Network Option in VirtualConnect
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
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
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
тАО06-25-2009 07:07 AM
тАО06-25-2009 07:07 AM
Is this a behaviour by design or am I missing something?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 07:45 AM
тАО06-25-2009 07:45 AM
Re: Private Network Option in VirtualConnect
Similar to Private VLANs in Cisco.
Private Network option is good for server hosting for example.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 08:07 AM
тАО06-25-2009 08:07 AM
Re: Private Network Option in VirtualConnect
It is still not clear. What stops network to send the network traffic back, if destination IP is on the same vNet (in the same enclosure), when it can send the traffic to other blades in other enclosures?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 10:56 AM
тАО06-25-2009 10:56 AM
SolutionWhat stops it from being able to communicate out the uplink and then back in is simple bridging/switching.
Quick example, with 2 servers A and B connected to vNET1 with the private network option checked. These 2 servers can't communicate with each other inside the enclosure (private network is working as designed). But these 2 servers are on the same subnet, why can't they communicate? Well, if server A ARPs for the MAC address of Server B, that ARP will be flooded and go out the uplink for vnet1. In switching, any traffic that goes out 1 port will not be received back on that port (that's a loop). So server B will never see the ARP request from server A. Server A will never learn the MAC address for server B. Even if server A knew the MAC address for server B it would still not be able to communicate because as the traffic exited the enclosure through vnet1's uplink, it would not come back in to that uplink because of the same bridging/switching principle as above.
I hope this helps... For a more eloquent description of Private VLANs, I'm sure Cisco has some good documentation...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2009 11:57 AM
тАО06-25-2009 11:57 AM
Re: Private Network Option in VirtualConnect
That is a good explanation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2009 07:57 AM
тАО06-26-2009 07:57 AM