- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Expanded Vlan in the virtual connect V3.30
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-22-2012 05:54 AM
05-22-2012 05:54 AM
Expanded Vlan in the virtual connect V3.30
The virtual connect configured in Legacy VLAN, allow me to mapped 28 VLANs per interfaces => in total: 168
In the documentation I found that with the Expanded VLAN I will mapped 162 VLANs MAX.
How will be divide? By server Profile or By interfaces on a server profile?
What’s append if we mapped 163? It’s possible to do or the Virtual Connect will say “I cannot map because there are to many VLANs mapped”?
For the implementation, Is that possible to do this without an interruption of the service?
What is the best procedure? DO I have only to check the option?
For the future I’ve you got a view? Will HP upgrade the total of VLANs mapped in a next upgrade?
And for the VLAN Trunking option, what is the procedure to pass from our configuration VC domain + Share Uplink to a vlan Trunking configuration?
Thanks
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2012 11:25 PM
05-31-2012 11:25 PM
Re: Expanded Vlan in the virtual connect V3.30
162 is the limitation per physical port. Assuming your 10G port has a/b/c/d 4 flexNICs, the sum of vnets on all these 4 flexnics can't exceed 162.
I assume you should get error. at least that's the case before with 28 vnets per flexNIC.
i'm not aware of any short term plan to increase this number. if you want more than that, maybe tunnel vnet can fit your requirement.
not sure what you mean by last question for vlan trunking config.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2012 04:28 PM
06-01-2012 04:28 PM
Re: Expanded Vlan in the virtual connect V3.30
If you want to go from an SUS (Shared Uplink Set) to a Tunnel you effectively need to remove the Uplink ports from the SUS and then create a new "Ethernet Network", enable the VLAN Tunneling checkbox and assign it directly to the Uplink ports.
I *think* thats what you were asking.
I work for HPE