07-18-2018 07:05 PM
Solved! Go to Solution.
07-19-2018 03:04 PM
Here is a link to some of the deployment guides...
http://docs.aerohive.com/330000/docs/help/english/ng/Content/reference/docs/deployment-guides.htm
07-19-2018 03:04 PM
Here is a link to some of the deployment guides...
http://docs.aerohive.com/330000/docs/help/english/ng/Content/reference/docs/deployment-guides.htm
07-19-2018 03:02 PM
Sure, can you be more specific about your environment? Which authentication method(s) do you plan to use? Are you integrating with AD? Are you able to configure VLANs on your network infrastructure or are you on a flat network? Any requirements for guest access?
07-18-2018 10:14 PM
Thank you for your response. Thank you for clarifying what I am wanting to implement. I really appreciate it. We are 1:1 in my district. Do you mind providing links to resources for this?
Thank you!!
07-18-2018 10:08 PM
Actually, as long as you're using the same authentication method, 802.1x, PPSK, etc, you can save airspace by utilizing a one or two SSIDs, then use policies to define VLANs, QoS, fire-walling, etc.
For example, we use 802.1x for authenticating our users and utilize certificates to authorize Enterprise devices vs. BYOD. IoT is placed in another group and separated from sensitive traffic via VLANs and firewall policies. We then use PPSK for guest traffic on another SSID. This greatly reduces the amount of competing traffic over the air.
There are multiple ways to accomplish what you're after, it just depends on your particular environment.
Best,
BJ