Matthew,
I think that's close, but I am actually looking more for the opposite. subnets are set geographically with seperate buildings getting different subnets. So the goal is:
VLAN 10 - Building 1 wired traffic and wireless CLIENT traffic 10.10.0.0
VLAN 20 - Building 2 wired traffic and wireless CLIENT traffic 10.20.0.0
VLAN 30 - Building 3 wired traffic and wireless CLIENT traffic 10.30.0.0
VLAN 50 - AP management for all three buildings so that the IAPS can see each other and be managed as a single network - 10.50.0.0 .
I can dive into the reasons for this if needed but will hold off for space.
This is where I get things close but kind of get out of my depth.
At the edges, the current config for switch 1 has two VLANS:
VLAN 1 - Default VLAN - NO PORTS - Primary VLAN
VLAN 10 - all ports untagged - Default gateway 10.10.1.1
This is repeated for switch 2:
VLAN 1 - Default VLAN - NO PORTS - Primary VLAN
VLAN 20 - all ports untagged - Default gateway 10.20.1.1
And switch 3 w/ VLAN 30 and 10.30.1.1. My actual network has a couple of tougher spots, but for the purpose of this, I think they are not worth diving into. Obviously, they all come back to the core which lists all the VLANS. Why the network engineer set it up that way at the edges, I am not sure though I supose he had his reasons.
In my mind, if I can ADD a VLAN 50 at the three edges and/or (not sure which) the core, and have the AP management on VLAN 50, then the IAP's all see themselves and create one wireless network instead of three, but all SSID's stay set to default and therefore continue to dump client traffic onto the subnet that is local / default / assigned for that switch. I just lose out on how to make that happen.