Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

TvL2386
Visitor

link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Hi guys,

 

I've tried to create a link-aggregation but it does not seem to work. Microsoft Windows Server 2012 tells me on all 4x10G NICS that the status is "faulted lacp negotiation". The server is a HP ProLiant DL380 G7 and has 2 NC500SFP network cards resulting in 4 10G NICS. 

I have 2 5900AF-48XG-4QSFP+ switches that are stacked.

 

The configuration on the switch is:

interface Bridge-Aggregation3
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
undo stp enable
stp edged-port
#
interface Ten-GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan all
port link-aggregation group 3
#
interface Ten-GigabitEthernet1/0/4
port link-type trunk
port trunk permit vlan all
port link-aggregation group 3
#
interface Ten-GigabitEthernet2/0/3
port link-type trunk
port trunk permit vlan all
port link-aggregation group 3
#
interface Ten-GigabitEthernet2/0/4
port link-type trunk
port trunk permit vlan all
port link-aggregation group 3
#

 

This is what the "display link-aggregation verbose Bridge-Aggregation 3" command tells me:

[switch]display link-aggregation verbose Bridge-Aggregation 3
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing 
Port Status: S -- Selected, U -- Unselected 
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation, 
        D -- Synchronization, E -- Collecting, F -- Distributing,  
        G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation3
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, d07e-2870-c040
Local: 
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/3         U       32768    3         {AC}
  XGE1/0/4         U       32768    3         {AC}
  XGE2/0/3         U       32768    3         {AC}
  XGE2/0/4         U       32768    3         {AC}
Remote: 
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/3         512     0        0         0x0   , b499-ba26-754c {ABCDE}
  XGE1/0/4         1024    0        0         0x0   , b499-ba26-754c {ABCDE}
  XGE2/0/3         256     0        0         0x0   , b499-ba26-754c {ABCDE}
  XGE2/0/4         768     0        0         0x0   , b499-ba26-754c {ABCDE}

I have no idea why it won't bring up the bridge aggregation.

 

Any help is highly appreciated!

 

Regards,

Tom

 

 

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to Comware-Based. - Hp froum moderator

 

 

9 REPLIES
3comold
Advisor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

First review this http://technet.microsoft.com/en-us/library/hh831648.aspx then configure accordingly your bridge aggregation.

 

Kind regards

 

TvL2386
Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Just to let you guys know, both HP and Microsoft are able to reproduce the issue I am having and they are investigating.

It seems that a lacp bond between HP5900 and MS Windows Server 2012 is not possible right now.

 

There's not a lot you can do wrong.

 

I've confirmed the following working lacp setups (cisco & hp are stacks):

mswin2012 - cisco nexus 5548p

linux - cisco nexus 5548p

hp5900 - cisco nexus5548p

linux - hp5900

 

The only setup that is not working:

mswin2012 - hp5900

 

Kind regards,

Tom van Leeuwen

 

 

alexandere
Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Hi..

 

Any updates on this issue?

 

We recently bought two 5900AF switches for use with Windows Server 2012 and Hyper-V over SMB3.

We need to use WS2012 NIC Team in LACP mode.

damogill
Occasional Advisor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Have you tried specifying the load-sharing mode on the Bridge-Aggregation on the switch and then matching it on the HP teaming settings?

 

link-aggregation load-sharing mode source-ip

TvL2386
Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Hi,

 

Very long investigation process (months) by both HP & MS has shown that there is a bug in the HP5900 firmware that prevents LACP from working with Windows Server 2012.

 

HP told me they have found the solution and are on-track to have this software available in the mid-June timeframe.

 

Regards,

Tom

TvL2386
Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

load-sharing mode doesn't have anything to do with lacp negotation. Since it fails on negotiation, it does not matter what load-sharing mode you select.
rajdude
Occasional Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

I can confirm that this issue has bee fixed in a newer firmware.... R2209

 

I have two 5900 switches stacked via IRF. A windows 2012 R2 server is able to team a 2 port NIC over LACP.

My switches are running HP Comware Software, Version 7.1.045, Release 2311P01

 

My settings:

 

interface Bridge-Aggregation2
 description myservername Teamed NIC
 port access vlan 4
 link-aggregation mode dynamic
 link-aggregation load-sharing mode source-mac

 

Notes:

1. I was getting LACP faulted until I changed strom static to dynamic on the switch.

2. On the server, both Address Hash and Dynamic work fine.

 

 

Also look at:

http://h20564.www2.hp.com/hpsc/doc/public/display?docId=mmr_kc-0107390

 

 

 

TvL2000
Occasional Visitor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

Yup I can confirm HP has found the bug and resolved it in their r2209.

VoIP-Buddy
Trusted Contributor

Re: link aggregation between Windows Server 2012 and HP 5900AF-48XG-4QSFP+ (stack)

@Tvl2000 - Yes, you are correct.  If you are not at least running R2209 on the 5900's then you have the LACP hashing issue and only one of your LACP BAGG ports should be running. 

 

FYI... If you were to disconnect the active running link, the BAGG will pick another link and continue on.

 

The latest version available on the My Networking portal is R2416-C.   The latest US-built code is R2311P01-US.

 

Regards,

 

David