Layer 2 roaming - multiple VLANs

  • 1
  • Question
  • Updated 3 months ago
Hi All

We have a 11 floor building that is separated into 4 VLAN's for corp users, all the AP's are in the same management VLAN.

Not long time ago Aerohive advised to disable L3 roaming due to a fact that we are still missing some of AP's in staircase areas and needed information wouldn't propagate between AP's in order for clients to stay connected.

In this scenario I would expect a client who goes from the 1st floor to the 10th in an elevator to drop its IP address covering 1st floor and request a new one upon arrival on the 10th, it might take almost 10 minutes and multiple wireless card resets to even get an IP. Then very often clients would get limited connectivity notification.

I'm not sure where to start troubleshooting this issue, any advice would be much appreciatedĀ 
Photo of Patryk Szenfeld

Patryk Szenfeld

  • 38 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Patryk,

Where a client does not perform DHCP after associating and uses its existing lease, this is going to be invalid. There is no standards-based, consistent mechanism to compel a client to perform DHCP again, it thinks its existing lease is valid.

You would need to get Layer 3 working to manage this scenario properly, or use different SSIDs.

Regards,

Nick
(Edited)
Photo of Patryk Szenfeld

Patryk Szenfeld

  • 38 Posts
  • 0 Reply Likes
Thanks Nick, I have a strong urge to force client to get new IP once moved to different VLAN to see how that works, I will test it later and report back
Photo of Patryk Szenfeld

Patryk Szenfeld

  • 38 Posts
  • 0 Reply Likes
After testing the above the issue would persist. I got some captures from a few AP's and I suspect the problem to be with Microsoft NPS,