Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

 
nhphong
Occasional Contributor

Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

Hi guys,

I've searched google awhile but still can't configure LACP on Windows Server 2012 R2,

My current configure:

HPE Switch: nterface 17-18 LACP Active, Untagged Vlan 1

Server 2012 R2: Teaming Mode: LACP, Load Balacinng Mode: Dynamic;

Result:
HPE Switch: Show LACP Interface 17-18 (Trunk type Dyn2, Port Up,  Partner Yes, LACP Success)

2012 R2: One port Fault LACP Negotiation

But When i changed teaming mode to Switch Independent, Load Dynamic then both port is Active.

Any idea to solve this problem ?

Thanks.

 

 

 

 

5 REPLIES 5
parnassus
Honored Contributor

Re: Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

Try using Static LACP port trunking Switch side (I suspect the usage of term Dynamic Server side means Active), to proceed:

  1. shutdown involved interfaces (shutdown interface 17, shutdown interface 18)
  2. remove their Dynamic LACP membership reference (no interface 17 lacp active, no interface 18 lacp active)
  3. create a new logical trunk port assigning freed interfaces as members (trunk 17,18 trkX lacp ...where X is a free/unused/available trunk id - a positve integer - within your Switch)
  4. finally enable interfaces (prepending no to shutdown commands cited on above at step1)
  5. eventually, if required, adjust at VLAN contexts levels, trkX untagged VLAN membership (it's on Default VLAN Id 1) and/or tagged VLANs memberships.

    Check result Switch side with show lacp (You will notice that logical trunk port was previously shown as DynY now is shown as TrkX) and show trunks.
nhphong
Occasional Contributor

Re: Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

Thank you for reply,

So i need to add int 17-18 to trunk group right ?

I'm confuse, becuase i've 4 interfaces connect to NAS (bonding NIC), and those port on switch don't need add to trunk group.

Is there any difference between LACP on switch connect to NAS bonding and AD NIC Teaming ?

Thanks.

parnassus
Honored Contributor

Re: Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

Well, bonding and teaming are, in this particular context, synonyms.

So it's a matter of understanding what type of NIC ports' bonding/teaming your switch is dealing with.

Provide us the outputs of show lacp and show trunks to let us understand what type of Ports Trunking you configured for your NAS and Server...also a snapshot of how the NAS is configured would be of help...to undertand differencies between both implementations.
nhphong
Occasional Contributor

Re: Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

Thanks for reply,

On HPE Switch: (17-18 are Server's Port, 19-22 NAS' port)

LACP:

17 Active 17 Up No Success 0 0
18 Active 18 Up No Success 0 0
19 Active Dyn1 Up Yes Success 0 0
20 Active Dyn1 Up Yes Success 0 0
21 Active Dyn1 Up Yes Success 0 0
22 Active Dyn1 Up Yes Success 0 0

Trunk

Port | Name Type | Group Type
19 | 100/1000T | Dyn1 LACP
20 | 100/1000T | Dyn1 LACP
21 | 100/1000T | Dyn1 LACP
22 | 100/1000T | Dyn1 LACP

NAS bonding configure:

Zalo_ScreenShot_10_7_2019_237409.png

 

 

Highlighted
parnassus
Honored Contributor

Re: Configuring LACP between Aruba 2930F (JL259A) HPE Switch and Windows Server 2012 R2 NiC TEAMING

I'm pretty much sure that if you change, switch side, ports 19-22 from Dynamic LACP (DynX) to Static LACP (TrkX), the connection to NAS will continue to function (apart from a brief traffic disruption due to the undergoing changes)...I strongly suspect that "Dynamic LACP" NAS side (Synology?) meaning is not what HP/Aruba means for its Port Trunking...a simple Static LACP should suffice.