Clients are not getting IP when placed on same VLAN as Aerohive AP

  • 1
  • Question
  • Updated 2 years ago
I've encountered a strange problem. We are replacing some Cisco AP's with Aerohive AP's
On small locations, we don't have a management VLAN, so we usually put the AP's in the same subnet/VLAN as the clients.
But we usually have 2 VLANs/subnets on all locations; one production and one for guests.
So the (Cisco) switch ports are set up with trunk configuration like this:
switchport trunk native vlan 42 (this is the production VLAN)
switchport mode trunk

The AP's themselves gets IP in VLAN 42 and becomes available in Hivemanager.
But all other clients, like computers or phones that connects to this AP does not get IP in VLAN 42. I can see in Hivemanager that the client has been assigned VLAN 42, but they do not get an IP address.
The other VLANs that the AP servers, works fine.
With the Cisco AP's (with Flexconnect configuration) this worked fine, but not with Aerohive AP's.

Any tips?
Photo of gaasdal


  • 26 Posts
  • 1 Reply Like

Posted 2 years ago

  • 1
Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
If your user profile is assigning users to VLAN 42, have you also set the management and native VLANs (in the network policy) to be 42 as well?

If management/native VLAN is left at its default value (1), then the AP will still function from a management perspective because if management VLAN and native VLAN are the same value, regardless of what that value is, management traffic will be untagged so will hit the native VLAN on the switch.

However if the user VLAN is set to 42, user traffic will be tagged with VLAN 42 and be dropped by the switch as it's the native VLAN and traffic for the native VLAN must be untagged.
Photo of gaasdal


  • 26 Posts
  • 1 Reply Like
I set the management and native VLANs to VLAN 42 in the network policy, and all seem to work well.
Thank you very much for the clarification.