topic Virtual connect cannot use LACP from internal blade in BladeSystem - General

Virtual connect cannot use LACP from internal blade

fransl — Tue, 28 Apr 2009 07:38:00 GMT

Hello All, Can somebody help me, We have blade using virtual connect and want to use LACP from internal blade connected to the virtual connect? Do this supported by virtual connect?

Virtual connect cannot use LACP from internal blade

vcblades — Tue, 28 Apr 2009 08:36:00 GMT

Downstream LACP is not supported on VC- best way to go with is VC Flex 10 & NC532 Mezzanines if you are looking for more bandwidth

Virtual connect cannot use LACP from internal blade

fransl — Tue, 28 Apr 2009 09:58:00 GMT

thank You for your reply, what is virtual connect Flex 10 & NC532? Thank you.

Virtual connect cannot use LACP from internal blade

chuckk281 — Tue, 28 Apr 2009 16:23:00 GMT

Go to www.hp.com/go/virtualconnect All the info is there.

Virtual connect cannot use LACP from internal blade

smanta — Wed, 01 Jul 2009 03:37:00 GMT

Chuck, Can you provide me a formal document where is stated that the VC FC 1GB modules does not supoport LACP downstream into the server blades. We have migrated a large number of servers from DL380Gx into BL460c and we had almost a war started between the server and network groups when we had to drop 802.3ad teaming on the blades with VC in c7000 enclosure. what will take for HP to address this or there is something in the midplane or VC crossconnects that will never allow this to be poassible ? Thank you

Virtual connect cannot use LACP from internal blade

vcblades — Wed, 01 Jul 2009 05:01:00 GMT

Sorry to jump in but here is the info you may need - http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01598869/c01598869.pdf Last Question: Q27: Does Virtual Connect support EtherChannel/802.3ad/SLB on the downlinks to the server NICs? Can I use LACP port trunking on the server NICs connected to Virtual Connect? A27: No, Virtual Connect does not support EtherChannel/802.3ad on the downlinks to server NIC ports. http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01598869/c01598869.pdf Page 25 http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf Page 19

Re: Virtual connect cannot use LACP from internal blade

Geert Nijs — Mon, 01 Feb 2010 10:06:16 GMT

Simple, because your two NICs of the server terminate on different VC modules (different "switches"), you can't bundle them anymore. HP doesn't support LACP across VC modules. One of the disadvantages of using blade servers or HP modules. You could use Cisco blade switches. They support real stacking (VBS) and cross-stack LACP bundles (although there are other disadvantages at that time: by joining slot1 & slot2 into the same stack, you can't upgrade anymore without downtime).