Procurve Trunk Ports for Wireless

[timberdoodle]

We have Procurve switches hooked up to Aerohive wireless access points. We are a school so there are multiple access points per switch.

I know best practice is to make the AP port a trunk port. My question is, on the switches, a trunk would be an arbitrary group 1-50 or whatever it can handle. Do I make all the ports in one trunk group? Do I break them up into individual trunk groups? How does this all work?

 

[/usr/home]

You are confusing Cisco trunks or "tagged" ports in HP terminology.

Each AP should be on a port tagged with the appropriate wireless VLANs.

 

[feffrey]

On Procurve trunking is different from trunking on Cisco.
A port can be tagged for multiple vlans and untagged for 1 vlan
For example if your APs are plugged into ports 1-5 on the switch and the AP management vlan is vlan 10, and your ssids are on vlans 20, and 30, it would look like this
conf
vlan 10
untagged int 1-5
exit
vlan 20
tagged int 1-5
exit
vlan 30
tagged int 1-5
exit
exit

Then on your uplink ports the untagged vlan would be your switch vlan, and all your vlans that switch needs would be tagged for that int.

 

[RocketTech]

Sounds like the equivalent of switchport mode general