- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Using Cisco AP with HP2920 POE switch
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Report Inappropriate Content
09-09-2016 12:38 PM
09-09-2016 12:38 PM
I have an HP 2920-48G-POE+ that I am trying to use to power a Aironet 1140 series AP. The AP is running our native VLAN 1 and our gest VLAN 100. The problem I have is the trunking on the switch.
There are three options, no trunking, tunking or LACP. I don't believe I need LACP since I am not aggregating the ports. If I enable trunking and put VLAN1 untagged with VLAN100 tagged into trk1 I kill the switch. As soon as I have live traffic on a link with trunking I lose management to the switch. Traffic continues to pass slowly through on the other ports but switch does not respond to ping or gui. I assume it is pegging out the CPU. This happens even when I try to trunk to my Dell switches.
To connect the AP should I leave the trunking off and just mark the port itself with with VLAN1 untagged and VLAN100 tagged? I have not tried that yet, I need to wait untill I can set another maintenance window with my users.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2016 01:12 PM
09-09-2016 01:12 PM
SolutionHello,
Short answer - Yes, vlan 1 untagged - vlan 100 tagged - no trunk.
Longer answer
Once upon a time "trunking", and this is according to the IETF IIRC, was the aggregation of physical links bonded together. This is the naming convention that HP now HPE adopted. Adding multiple vlans to a link and using "tagged" and "untagged" did not make a trunk.
Other vendors, notably Cisco, decided that "VLAN trunking" was the use of multiple vlans on a single link and aggregation of physical links was to be called an "etherchannel".
I tend to call any kind of link aggregation a "LAGG" these days as everyone gets that.
You will see port-channel interfaces in Cisco IOS, bagg and ragg in Comware and trk in AOS/Procurve
Aruba-OS / Procurve - on this platform trunks are aggregates - just add the port to vlans as a combo of tagged and untagged for the equivalent of a "trunk" on every other platform. :-)
Hope that clears things up. Don't for get "solved" and "kudos" buttons to let people know if this was helpful
Thanks
Ian
## ---------------------------------------------------------------------------##
Which is the only cheese that is made backwards?
Edam!
Tweets: @2techie4me