- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Creating LACP active interface
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-19-2017 04:49 AM - edited 06-19-2017 04:50 AM
06-19-2017 04:49 AM - edited 06-19-2017 04:50 AM
Creating LACP active interface
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!
- Tags:
- lacp active
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-19-2017 05:15 PM
06-19-2017 05:15 PM
Re: Creating LACP active interface
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-21-2017 05:03 AM - edited 06-21-2017 06:08 AM
06-21-2017 05:03 AM - edited 06-21-2017 06:08 AM
Re: Creating LACP active interface
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?
I'm not an HPE Employee

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP