we bought 45 AeroHive 250 Access Points and we use 35 of it for our Location in Town A.
I would like to use the other 10 Access Points for our second Location in Town B.
The configuration and SSIDS are complete different.
What is the best solution for it ?? do i have to create a new Hive Manager online instance ?
And if yes, how do i do it ??
Thanks for help..
Make sure you structure the topology (maps) accordingly, e.g. use your company or country name for the root folder, and then one subfolder for each town etc.
This way you have them both clearly separated, but you can still use common configuration and resources where it might make sense. For example, you might want to use the same radio profiles as well as the same already configured objects for snmp, ntp, lldp, dns, management console, syslog, qos, etc. Same for Radius servers, if it might apply. And if you use PPSK for authentication, you can choose if some groups might be valid for both towns or not. Up to you. You could even use the same user profiles and overwrite certain settings (VLAN, DNS server, ...) based on the location (Town) or device tag. This is very powerful, and again, you decide what you want to share / re-use or configure completely independently.
You can create reports for both towns together, or for each separately - just filter on the location.
Now... If you want administrative separation, where administrators of one town cannot see at all anything from the other town, you could indeed consider creating a new VHM. But it's a bit complicated, as you would have to have your license key split - for this you must contact your Aerohive reseller.
With NG there is now a better way to do this: Hierarchical HiveManager (HHM). This allows you to create organizations inside the same VHM, and you can assign role-based access for administrators to specific organizations (= towns) only.
Hope this helps...
thanks for your fast detailed response.
i was wondering if a second nps is the right way. now i know it.
If you have people in your organisation who regularly attend in both Town A and Town B you might want to have an SSID that exists in both network policies, so the experience and policies applied to this group of users is consistent no matter which location they are in.