Devices getting assigned IP address of the wrong VLAN

  • 2
  • Question
  • Updated 10 months ago
We have devices that are connecting and getting IP addresses from different pools then the VLAN they're supposed to be assigned to.
Photo of Joshua Pawlak

Joshua Pawlak

  • 2 Posts
  • 0 Reply Likes

Posted 10 months ago

  • 2
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Joshua,

In order to help you, we need more information:

- how is your vlan assignment configured? Static with 1 vlan per user profile, and 1 user profile per ssid? Or are you using any dynamic methods such as classification based vlan objects, client classification rules, user profile assignment based on radius attribute values, ... ? Please describe as detailed as possible!
- in Monitor, when you look at the list of all clients, is the vlan id correct but the ip is wrong? Or is the vlan id wring but the ip matches that vlan?
- please run the client monitor for a device in question, while connecting, and post the output here.

Thanks.
Photo of Joshua Pawlak

Joshua Pawlak

  • 2 Posts
  • 0 Reply Likes
We have static VLAN's with 1 assigned per user profile. For example, we have a 500Device VLAN associated with a Device user profile or a 600Admins VLAN associated with our Admins user profiles.

I haven't checked the client in the client monitor to see what IP it's showing, but we have had a few devices that are connecting to our Admins user profile and getting an IP from the 500Device VLAN.

I've triple-check our switches to make sure traffic is getting tagged as it's supposed to. The only thing that's weird to me is that if I do a VLAN probe on our AP's, only our PSK_Server AP's show the correct VLAN, all other AP's show the default VLAN 1.

We have several sites with the same setup and are only experiencing these issues at a couple of them.

Edit: Also, we can use a code for a device that works just fine, but another device doesn't
(Edited)