topic Re: Untagged and VLAN in Wireless

Untagged and VLAN

ibrydon — Sat, 03 Jul 2021 23:14:32 GMT

I have a 4402 wireless controller whose management and ap management interfaces are connected to VLAN1 with the WAPs on VLAN17.

When I confiigure the 4402 I have to assign the ap manager interface to VLAN1; however, if I try to assign the management interface to VLAN1 I cannot telnet or https to the 4402. In order to do that I have to mark the management interface as 'untagged. Why can't I explicitly assign the management interface to VLAN1 since in fact it is on VLAN1??

Re: Untagged and VLAN

Scott Fella — Thu, 31 Jul 2008 01:54:00 GMT

Best practice is to not tag the management and ap-managers interface. vlan 1 on a switch is untagged so you need to set the management and ap-manager to vlan '0'. It is just how it has to work. Even if you have the management and ap-manager on vlan 50, you need to set the native vlan on the trunk port to vlan 50.

Re: Untagged and VLAN

robetrem — Thu, 11 Sep 2008 17:57:43 GMT

Installation of the WISM place automatically

mls trust cos on the Gigabit link making the Etherchannel. If the AP-Manager is not tag the "QOS to wire" won't work.

Have you noticed that and have you worked around that issues !