topic Re: 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). in Aerohive Migrated Content

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 — Wed, 05 Sep 2018 22:12:08 GMT

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

Re: 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).

samantha_lynn — Wed, 05 Sep 2018 23:31:20 GMT

Any new devices will be HiveManager only (formerly NG), so you would want to move off of Classic when you can if you want to use the newer devices. All new features and hardware will be HiveManager focused, rather than geared toward HiveManager Classic.

HiveManager is a totally separate platform so there is no way to move directly from Classic to HiveManager. However, you can import your device list and Maps by exporting a backup of your Classic instance and importing it in to the HiveManager instance. We have several how-to guides that can help you rebuild your SSIDs in HiveManager, or you can always open a case to request assistance with this. Overall if you'd like help migrating from Classic to HiveManager, you can reach out to our professional services team and they will set you up with a technician to help you through the migration.

Re: 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).

dtopojr — Fri, 07 Sep 2018 02:54:54 GMT

Thanks Sam ....appreciate your concise answers. What about the Social Login service...we also utilize that. Does that also work with HM NG? Yes, if you have any guides available, that would be helpful. We utilize RADIUS enabled APs with AD as our database along with dynamic vlans to steer our uses to appropriate subnet...so anything on that would be very useful.

Thanks again!!

Re: 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).

samantha_lynn — Fri, 07 Sep 2018 22:23:56 GMT

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

Re: 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).

dtopojr — Sat, 08 Sep 2018 01:17:24 GMT

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

Re: 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).

samantha_lynn — Tue, 11 Sep 2018 20:06:09 GMT

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.

Re: 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).

dtopojr — Fri, 14 Sep 2018 07:13:37 GMT

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?

Re: 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).

samantha_lynn — Sat, 15 Sep 2018 04:01:52 GMT

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?

Re: 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).

dtopojr — Tue, 18 Sep 2018 01:54:36 GMT

Ok Sam...which is what we are doing now via Aerohive AAA server settings- Database settings:

Here's an example of a mapping of a group to a user profile:

CN=Faculty_Wireless,OU=Groups,OU=Mydomain Users,dc=Mydomain,dc=LOCAL

So, Mydomain Users has a space " ".

This would restrict me from doing ldap mappings like I do now?

Why the limitation in NG? Seems things are moving in the wrong direction with this platform...unfortunately..

Re: 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).

samantha_lynn — Tue, 18 Sep 2018 03:45:56 GMT

Unfortunately that space would cause problems, we've seen it a few times. We can submit a feature request to allow the use of spaces in the organization name in future releases, but at this time I think that might be a critical point of failure for your current set up in NG.

Re: 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).

dtopojr — Tue, 18 Sep 2018 22:01:51 GMT

Ok Sam.....we'll cross that bridge when we get there. Renaming the OU wouldn't be too impactful. Surprised that the space would be a limitation since either HM platform is only pushing out a change to APs running an OS that hasn't changed. Anyway...you've been super helpful...thank you!!

Re: 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 — Wed, 31 Jul 2019 20:50:39 GMT

Hello Sam.... it's been going on a year since our discussion here in this thread...and we are now looking to migrate sooner rather than later. I was wondering if having a space in the OU names is still a factor when when using LDAP mappings in the current (new) Hive Manager?? Appreciate any feed back-- thanks ....Dennis