Creating LACP active interface

[cauliflower]

Hi,

I'm used to Cisco LACP config, and am confused by what is required to set up an LACP active port on an HP switch (in this case a 3500 series).

It needs to be LACP active because an access point is being pugged into it that requires this.

As far as I can see:

trunk 1-2 trk1 lacp    doesn't work because it creates a passive interface

and

interface 1-2 lacp active    doesn't work because I can't set the native vlan to be anything other than vlan 1 without enabling GVRP

Is it me or is this a bit mental? Am I missing something?

Thanks!

[Vince-Whirlwind]

The "native VLAN" is whichever VLAN you add to the "trk1" interface as untagged. I've never come across any issue where LACP imposes any restriction on the trunk interface config.

Unlike Cisco, you can have *no* VLAN untagged on the interface.

You shouldn't be using any untagged/native VLAN on any trunks anyway, for security reasons.

[parnassus]

It's not clear, you wrote: "It needs to be LACP active because an access point is being pugged into it that requires this." so a question: do you really have a Wireless Access Point that needs to be connected via a Port Trunk logical interface (so using two or more concurrently aggregated physical ports) implemented using LACP?