Identity PSK VLAN assignment bug on MR42 30.7?

yaypingworks
Conversationalist

Identity PSK VLAN assignment bug on MR42 30.7?

We use iPSK with group policies assigned to specific VLANs for our various wireless devices. Today I saw that at two locations devices that were supposed to be a part of VLAN 200 were actually assigned to VLAN 300, even though they still had the IP for VLAN 200 subnet (using DHCP) ... 

 

VLAN 300 is the native vlan trunk port that the APs connect to, why it put devices in that VLAN i dont know. Trying to connect to the SSID on a new device would fail saying 'cant connect to this network'

I had to end up rebuilding the SSID and then things started working and getting the correct VLAN assignment. Its like that specific SSID setup just broke.

 

Has anyone experienced this issue?

 

 

0 Replies 0
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels