Configuring LACP (link aggregation) between HP 2920-48G and windows 2012 server

[smitha_k]

Hi,

I am trying to configure LACP between HP 2920-48G Switch and windows 2012 server.

I have configured LACP on HP Switch (on ports 1 and 2) using below command

                      int 1-2 lacp active

but when I try to add the respective ethernet ports on windows 2012 server into a NIC team then it shows that the state is "faulted" and the reason "not found" and the status as "degraded".

can anyone tell me is this the correct way to configure LACP for bandwidth aggregation on HP 2920-48G Switch.

Thanks.

P.S. This thread has been moved from Community Feedback & Suggestions to ProCurve / ProVision-Based. -HP Forum Moderator

[egodkin]

Procurve should be 

trunk 1-2 Trk# lacp 

not sure how you are connected on the server side.  are you using NIC Teaming with switch dependencie? 

[smitha_k]

I have also tried this command "trunk 1-2 trk1 lacp"....still same warning at the server end....

yes at server i am using NIC teaming with "switch dependence"...in that i tried both "static teaming" and "lacp" as well

[Chrisd131313]

Hi Smitha,

I have a 2012 server connected to 5406zl server with LACP and this is what I have set...

HP Switch side...

                  trunk port#1,port#2 trk<num> lacp

Server Side...

                  Teaming Mode: LACP

                   Load Balancing Mode: Address Hash

Do you get any error on the switch for the trunk you are using? or is it just errors on the Server? Also, are you using the latest NIC drivers on the server? I have seen soem peculiar behaviour with 2012 teaming and HP LACP/DT-LACP.

[smitha_k]

Hi Chris,

I am using the same instruction that u are using..

no i am not getting any error on the switch..instead at the switch it shows LACP has been configured successfully...in the "partner" column it shows "yes" when "LACP" is used in "NIC Teaming" at the server...

I only get errors at the server end..whenever i create a team even with 1NIC or 2 NICs..at server it shows that the interface is "faulted" and "not found"...

I am using the NIC drivers that came along with the installation...i am not sure whether they are the latest one or not...

But one strange thing is this NIC teaming works fine when i do it for Hyper-v VMs...at that time NIC teaming doesnt give any errors...

Thanks,

 - Smitha

[smitha_k]

Hi Chris,

You said that you tried to configure LACP between 2012 server and 5406zl switch right...

so just wanted to know..have you tried to create a NIC team in "Switch independent" mode with "Address Hash" as Load balancing mode?? Because when I tried to create a NIC team with these parameters I am getting a warning in 2012 server like its "Faulted" and "Not Found"...

Just wanted to confirm whether its the limitation at the server end or what is the reason..I tried by updating the NIC drivers as well...still no progress...can you tell me what are the type of NICs that you have in that 2012 server???

 Thanks,

Smitha

[Chrisd131313]

Hi Smitha,

We have had 2012 servers running  as switch independant and LACP, both set to address hash.

The servers we have are using Broadcom 57xx NICs (v16.0.0.17).

We are currently runing K.15.10.0009 on the 5400s.

The server is setup as DT-LACP on the two 5400s and LACP/ Address hash on the server.

HTH

[smitha_k]

Hi Chris,

Thanks for your reply.

I have one more doubt. After creating a NIC team (either switch independent or LACP) in the 2012 server I am getting a warning message (and it says that the link is "faulted" and "not found"). But once I create a Virtual switch of this NIC team through the Virtual Switch manager the NIC team goes active and i dont get warning any more.

So I wanted to confirm that we need to create Virtual Switch (in Virtual Switch Manager) only to use it in Hyper V VMs right??? and we dont have to create a virtual switch if we want to configure NIC teaming within the 2012 server right??

 - Smitha Koduri

[Chrisd131313]

On our 2012 Hyper-V hosts we have vSwitches setup and these work fine, but on our VMM server - which is a bare metal box - we just have straight LACP with address hash and this also works OK. I am no expert at Hyper-V vSwitches so I would need to confirm with our virtualisaiton guy, but I am pretty sure the vSwitch is the right way to go if you are using the server as a Hyper-V host.