BladeSystem - General
1748245
Members
3747
Online
108760
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-09-2009 09:32 AM
10-09-2009 09:32 AM
VC
Some discussion around whether the Virtual Connect "Private LAN" feature compares to the Cisco "Private VLAN" feature. From Mark in our VC engineering group: "HP Virtual Connect introduced “Private Networks” in Firmware Release 1.31 last year. While this is similar (isolation of Layer 2) to Cisco’s “proprietary” Private VLAN feature, it is not exactly the same. There are no future plans to implement Cisco’s Private VLAN within Virtual Connect. Our primary goal is to implement IEEE features. With Link Aggregation, VC chose IEEE 802.3ad (LACP) and not the proprietary Cisco PAGP. The same goes for IEEE 802.1q (Trunking) versus Cisco ISL. With Layer 2 isolation, since there is not an IEEE feature, we implemented what we found customers wanted. If there is some reason that Private Networks does not achieve the customer’s strategy, we would like to know more info."
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2010 06:42 PM
01-21-2010 06:42 PM
VC
The HPVC private network function is similar to Cisco Isolated Private VLAN. The is not equivalent to community VLANs, unfortunately.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP