- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Opinions on Virtual Connect design
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
тАО01-09-2011 08:34 PM
тАО01-09-2011 08:34 PM
Opinions on Virtual Connect design
I have based it around page 156 of the HP Virtual Connect Ethernet Cookbook.
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf
We will be using multiple defined Ethernet networks and shared uplink sets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2011 08:36 PM
тАО01-09-2011 08:36 PM
Re: Opinions on Virtual Connect design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2011 12:52 AM
тАО01-10-2011 12:52 AM
Re: Opinions on Virtual Connect design
for me this looks fine.
We have a similiar VC design on two stacked c7000 and it works like a charme with ESX and and dedicated Blades mixed either.
Tested all kinds of failure szenarios and bandwidth usage, all worked fine for us.
kind regards
Markus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2011 08:44 PM
тАО01-10-2011 08:44 PM
Re: Opinions on Virtual Connect design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2011 10:51 PM
тАО01-10-2011 10:51 PM
Re: Opinions on Virtual Connect design
your are right (cannot present a VLAN more than one time to a LOM); but you can assign to another LOM, and i.e. in my setup this is for traffic shaping and failover.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 04:27 PM
тАО01-11-2011 04:27 PM
Re: Opinions on Virtual Connect design
Flex module firmware: 2.32
OA Firmware: 2.60
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 10:44 PM
тАО01-11-2011 10:44 PM
Re: Opinions on Virtual Connect design
this way you CAN bind the same VLAN to one LOM - if you take "multiple networks" it works.
VLAN1,2,3 => LOM1:a
VLAN1,2,3 => LOM1:b
works!
Network1 => LOM1:a
Network1 => LOM1:b
does not work!
So your setup is quiet good, IHMO.
No need to change anything.
KR
Markus