HP LACP configuration

[LolekUK]

Hi,

 

I have HP 2530 switch and Buffalo TS3400 NAS.

 

NAS is able to aggregate NICs (LACP) which I have configured and plugged in to switch port 23-24.

 

I'm having trouble configuring LACP on HP.

 

I have tried:

 

int 23-24 lacp active

 

and also:

trunk 23-24 trk1

 

HP is accepting both commands (separately) but after patching NAS back in to the switch I don't get any pings back.

When lacp or trunk is removed, NAS is back on the network.

 

Any suggestions?

 

Thanks

[Blue_Cookeh]

I'm using this to bond two ports with our Synology NAS on 2530 switches:

 

trunk 23-24 trk1 lacp

 

You can use "show trunk-statistics trk1" to see how the network load is spread across the two ports.

Edited April 11, 2016 by Blue_Cookeh

[glen_j]

have you tried setting the lacp on the switch as passive?

[rrrrr]

Make sure you are applying the vlan/ipconfig that was applying to port 23/24 now to the trk1 port

[LolekUK]

Thank you Blue_Cookeh for command and rrrrr for reminding about assigning vlan to trk1.

 

All working now, happy days

 

Thanks

[LolekUK]

Said it too early, NAS worked but other connections on the switch have dropped (no ip address, unidentified network), wonder if setting up trk1 on edge switch broke the rest. Unfortunately as NAS worked I have quickly overwritten the config without checking the rest. Reversing step by step setting trk1 up didn't fix the problem. Eeeeek.

 

Thank you Blue_Cookeh for command and rrrrr for reminding about assigning vlan to trk1.

 

All working now, happy days

 

Thanks

[LolekUK]

False alarm, tested it on some dodgy devices - one with faulty NIC and one with static IP - no wonder I was getting error messages.

All working

 

Said it too early, NAS worked but other connections on the switch have dropped (no ip address, unidentified network), wonder if setting up trk1 on edge switch broke the rest. Unfortunately as NAS worked I have quickly overwritten the config without checking the rest. Reversing step by step setting trk1 up didn't fix the problem. Eeeeek.