Do we need to be, or should we be on HM NG to utilize ax APs?...for example the AP630?? We are still on the HiveManager "Classic" I guess you can call it (cloud version).

[dtopo]

Also, it's my understanding that there is no real migration from HM to HM NG...it's more of a total rebuild and then move your APs over. Correct ?? Thanks for any insight! ...Dennis

[samantha_lynn]

You'd want to use LDAP mapping to accomplish that in HiveManager (formerly NG). But to do that, the main gotchas with LDAP mapping are organization unit names in your AD that are either longer than 32 characters or have a space in the name somewhere. Can you tell me if your AD organizational unit names are longer than 32 characters or have a space in them?

[dtopojr]

Sam....one more question..I promise! Just to clarify, in regards to your last reply, this would in affect, NOT be able to take into account the group membership of user like we do now....which maps them to a user profile. In our case, we would NOT be able to distinguish between say a student user and a faculty user?? For example, ALL users hitting AP A, would get mapped to Subnet A via the location map regardless of user typegroup membership?

[samantha_lynn]

I think the closest we can get is to route users to different user profiles (and therefore different VLANs) using Client Location as the assignment criteria. This would mean you need a map for each subnet in your setup, then you would need to place the appropriate APs in there respective locations on those maps, then create an assignment rule stating X location gets Y user profile. You would have this set up in addition to your Radius SSID, so users would also authenticate through the AD with this setup.

The other assignment rules available in HiveManager are Client OS type, Client MAC address (which would technically work for you, but would require a list of all allowed MAC addresses and what location they belong to ahead of time, so it's a heavy setup workload), and Schedule.

[dtopojr]

Sam.... we do use AP device tags to "mark" each APs location. (buildingfloor in some cases)

Those tags in turn map to dynamic vlans- representing the respective subnets for that location. Then, based on a users AD group, they are mapped to a user profile and attribute number under AH AAA Server database settings. Then the final tie-in is at the user profile of course, where the dynamic vlan is assigned to the user...based previously on AD group membership, and AP Tags.

For example, a student (member of a AD student group) gets a student profilevlan, faculty, a faculty profilevlan and so on.

So, you're saying this can't be easily achieved in the new HM?? Hmmmm....how do schools vlan steer with the new HM??

Also, thanks for your input on all this.....very valuable for us!

Dennis

[samantha_lynn]

Hey Dennis, we can do social log in and Radius tied in to an AD in HiveManager no problem, the guides for that are below. The only thing you might run in to difficulty with is your client classification to steer users on to different VLANs. We don't have the ability to set attributes in HiveManager, and we don't have device tags. Could you elaborate a little more on how you move clients to different subnets so I can make sure we can replicate this for you in HiveManager?

Social Login in HiveManager- https://thehivecommunity.aerohive.com/s/article/Social-Login

Radius in HiveManager- https://thehivecommunity.aerohive.com/s/article/Radius-SSID-in-NG