ā08-24-2020 07:57 AM - edited ā07-05-2021 12:26 PM
The docs on 5508 controllers say radius can assign vlans by vlan ID (see https://community.cisco.com/legacyfs/online/legacy/3/3/0/55033-AAA-overide-ACS52.pdf). Radius servers actually return a string, and the vlans are all associated with an interface name, so I'd rather use the name, like you can with cisco's ethernet switches (by using the vlan name). Does the software allow this? We're on 8.5.140.0.
Solved! Go to Solution.
ā08-24-2020 10:31 AM
ā08-24-2020 08:53 AM
ā08-24-2020 09:01 AM
If you can use the name, you can provision clients who move from one environment to another. VLAN numbers are less portable due to the way our environment has been built (not because they are less portable in theory). And yes, I could test, probably will, but if it's not possible how do I know if something isn't quite right or I'm trying something that just doesn't work?
Thanks,
Ted
ā08-24-2020 10:31 AM
ā08-24-2020 11:19 AM
Kind of what I've been trying to avoid, since it would mean programming in VLAN information for a bunch of stuff that are not WLCs to account for the fact that the WLCs won't do names. Probably have to code it in a way that will use the name for the bulk of the devices and will use a vlan-id for the smaller set of devices that have to have the number. Thanks.
ā08-24-2020 12:12 PM
ā08-24-2020 01:07 PM
Cool, thanks. That does look promising.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide