HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

Opinions on Virtual Connect design

 
Amana Living
Occasional Advisor

Opinions on Virtual Connect design

Hello all, I'm after some opinions on my Virtual connect (re)design. Please see the attached file.

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.

6 REPLIES
Amana Living
Occasional Advisor

Re: Opinions on Virtual Connect design

Screen shot of VC Domain.
Markus M.
Trusted Contributor

Re: Opinions on Virtual Connect design

Hi Amana,

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
DerekS_1
Frequent Advisor

Re: Opinions on Virtual Connect design

I could be wrong, but I thought you could NOT present a VLAN more than once to a Flex-10 LOM (set of 4 vNICs). The rationale is that you can customize the bandwidth for each Flex-NIC so you don't need to present it multiple times to a LOM.

Markus M.
Trusted Contributor

Re: Opinions on Virtual Connect design

DerekS,

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.
Amana Living
Occasional Advisor

Re: Opinions on Virtual Connect design

See attached for what I am correcting. This is currently in operation, so it does appear you can assign the same VLAN to the same LOM provided you create different Ethernet networks connected to shared uplink sets. I'll see if that is still the case when I start making configuration changes.

Flex module firmware: 2.32
OA Firmware: 2.60
Markus M.
Trusted Contributor

Re: Opinions on Virtual Connect design

Hi Amana,

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