- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Virtual Connect
- >
- Can VLANs exist on more than 1 FlexNIC on a physi...
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-08-2011 12:31 PM
11-08-2011 12:31 PM
Can VLANs exist on more than 1 FlexNIC on a physical nic.?
Dan had a configuration question:
****************
HI Everyone, I need a REAL quick answer on this. With Virtual Connect - Can VLANs exist on more than 1 FlexNIC on a physical nic.? I know this was NOT supported earlier and it still may not be supported – however, I thought I heard or saw something that this will be supported in a FW upgrade…
********************
From Dan:
*********************
Still not supported.
Don't know in the future.
You can make it work if you use 2 diff uplinks and define the VLAN twice (or 4 times for active/active) Then VC sees them as diff VLANs internally.
*******************
Any other comments or suggestions for Dan? Part of what I heard is that this configuration can produce network loops and we don't want that as we are not part of the network Spanning Tree Protocol (STP).
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP