This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Legacy
- Aerohive Migrated Content
- Re: Do we need to be, or should we be on HM NG to ...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
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).
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-05-2018 03:12 PM
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
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-05-2018 04:31 PM
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.
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
07-31-2019 01:50 PM
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-18-2018 03:01 PM
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!!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-17-2018 08:45 PM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
09-17-2018 06:54 PM
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..
