WAP 321 Management VLAN

[bbeaudry]

HI, I want to use the management VLAN254 for my 4 WAP321. but after changing the management vlan in the unit from 20 th 254 I lost contact with the unit.

The switch I use is a Cisco 2960. Here's the config of the port :

interface FastEthernet0/23
switchport trunk native vlan 254
switchport trunk allowed vlan 5,20,254,1002-1005
switchport mode trunk
spanning-tree portfast

Vlan 5 and 20 are my two SSID Vlan

I was able to connect to the unit when the management vlan was set to 20  with an IP of 192.168.254.51 but since I chaged the vlan in the unit can't connect to it, I can't even ping it from the switch ...

Any ideas ?

[Tom Watts]

Hi Bbeaudry, did you power down the AP at any point? Did you save the running config of the AP to the start up config?

So long as you're on the same subnet and the vlans match (which they look like they do) it shouldn't be a problem.

-Tom
Please mark answered for helpful posts

[bbeaudry]

HI Tom,

Yes I did power it down, and the modification was done thru the web interface so I guess the config is applied by default

Regards,

Ben

[Tom Watts]

Hi B, if the device was powered down without writing the config it behaves just like that 2960, won't be there

-Tom
Please mark answered for helpful posts

[bbeaudry]

Hi Tom,

Got it back to work by setting the native Vlan in my 2960 to vlan 20

I also have an issue with my 2nd wireless network, vlan 20 if I don't set the untagged vlan to 20 I can't reach that network. but no problem with my wireless network with vlan 5 which is the first one. It looks like the vlan tagging only work for the first network. Is this a normal behaviour of that AP ?

Ben

[Tom Watts]

Ben, the AP supports up to 8 VLAN.

Change your vlan configuration on the switch

switchport trunk native vlan 20

switchport trunk allowed vlan add 5,254,1002-1005

Also verify the config upstream to whatever is connecting matches.

-Tom
Please mark answered for helpful posts