- Named VLAN support for MS120/125/210/225/250/350/355/390 series switches
This will ease a lot of installations! Great addition.
Indeed, but beware of this one:
Yes, no problem for me, I don't use firmware version < x.5 or so ... 😉 And I assume that one will get fixed quite soon.
So if anyone is brave enough to try this release, does named vlan support just mean that I can type VOICE in a vlan field instead of the number? Or will it be a dropdown selection? I guess this is just for ease of management? VLANs have to use numbers in the actual packets, as far as I'm aware.
I'm not seeing documentation yet that explains this.
@Mloraditch I think it will simply be an additional label you can add for ease of reading. So far I have only applied this firmware to my home switch and as that is an MS220, this feature isn't supported by the release...
This feature is for Named VLANs to VLAN ID mappings for RADIUS. We definitely do want to leverage this further down the road for more than just simplifying RADIUS deployments. Please use the feedback button at the bottom (that we for some reason renamed from make a wish) and let us know there if you wouldn't mind.
I currently have spreadsheets for each customer to keep track of every VLAN.
Names are going to make life MUCH easier.
For me the "inline documentation" of the VLANs are only the secondary but definitely a welcomed benefit. The main benefit is that (well, at least I expect that this feature will work that way similar to Catalyst switches) I can send the VLAN name from the RADIUS server and the "right" VLAN gets applied regardless of the VLAN ID. Yes, having consistent VLAN-IDs would be better, but is not always possible.