LACP – Configuring LACP from Server to Switch

hpieee-802.1ax

I am trying to configure link aggregation (LACP) from a server to a HP 2920-48G switch. The server has a 4 port Intel NIC that supports LACP, and a OS that natively supports LACP as well.

The switch has three modes for LACP, Passive, Active, and a separate "LACP Trunk" which appears to be primarily a proprietary option for trunking HP switches together. I have tried all three options on the two ports I am attempting to aggregate with no success. I have also read that I must have GVRP enabled on the ports, then forbid those ports from joining the default VLAN (as I am attempting to aggregate on a different VLAN then the default) to get dynamic LACP working. I have tried that with all three previous options and I still cannot get a working connection.

Any ideas on where I am failing?

Best Answer

Sounds like you're almost there.

You'll need to create a "team" on the server using two or more of the Intel ports. Use the Configure option in the NIC settings to choose 802.3ad.

Let's say you're using a team with two server NIC ports into two ports (47 and 48) on the same switch.

On the HP switch,

HP Procurve 2920> config
HP Procurve 2920(config)# int 47-48 lacp active
HP Procurve 2920(config)# show lacp

Check to be sure lacp status is "success"

Now patch in your server, each Intel NIC port to an HP port. Come back to the CLI and

HP Procurve 2920(config)# show lacp

to check if it's successful. Look for LACP partner = yes on both interfaces 47 and 48 and be sure all interfaces in your team are "up" Check your server to be sure traffic is flowing through both NIC ports. If so,

HP Procurve 2920(config)# write mem

to save configuration to memory.

Related Solutions

Routing – HP V1910, VLAN routing – what did I miss

Your problem is, indeed, with routing. Things in VLAN 1 are using 5.1 as the gateway, right? 5.1 doesn't know about any other internal networks. (i.e. VLAN 10) Likewise, the hosts in VLAN 1 don't know about VLAN 10.

When clientA tries to ping serverA, the packets go to the ASA and die as it doesn't know where to send them. (it's default route would send them to the internet!) When serverA tries to ping clientA, the packets go to the switch and then to clientA, but then the replies, as before, go away.

For this reason, it's common to keep the "routing hardware" and "hosts" in different networks. VLAN 1 being just the ASA and Switch. And then VLANs 10 and 11 for the two internal networks. The switch would then be the gateway for VLAN 10&11, with it's default being the ASA. The ASA would have to have static routes added telling it about the internal networks -- routed to the switch. Without this, either the ASA has to "hairpin" traffic back to the switch to reach VLAN 10, or every host in VLAN 1 needs its own route to VLAN 10 (via the switch.)

LACP on stacked HP 2920-48G

If you're just using 1 10Gb port to connect them, you only have to add that link into the VLANs you want to share between the switches, if any. Out of the box, there'd be no configuration on your side w/ 1 link

With 2 links, you will want to form a link aggregation in one of 2 ways. Say you're going to link over 1/49 and 2/49 (first 10Gb on both switches in the stack) to ports 1/50 and 2/50 on the 2nd stack (second 10Gb on both switches in the stack). It's like this:

Stack 1:

trunk 1/49,2/49 trk1 lacp

Stack 2:

trunk 1/50,2/50 trk1 lacp

The name 'trk1' becomes the virtual port name. It doesn't have to match on both sides.

The last keyword lacp can also be trunk. The difference is that lacp is a more stateful connection, trunk being static port bundle.

Finally, if you have VLANs that need to transit the trunk, you have to allow those across. Just like the other ports are set up, but with the 'trk1' port. If you had, say VLANs 10 and 20, you'd do this on both stacks:

vlan 10

tagged trk1

vlan 20

tagged trk1

Best Answer

Related Solutions

Routing – HP V1910, VLAN routing – what did I miss

LACP on stacked HP 2920-48G

Related Topic