User's Manual

Chapter 8 HiveManager Configuration Examples

100 Aerohive

Defining VLANs

You define three VLANs that you will later assign to various user profiles (see "Example 4: Creating User Profiles" on

page 113). By assigning different VLANs to different user roles, their traffic remains isolated from each other; that

is, voice traffic never shares a broadcast domain with data traffic; and data traffic from guests never shares the

same broadcast domain with employee data traffic. The result is that you can provide access for certain types of

traffic to select areas of the network while blocking unauthorized access to other areas.

The VLAN IDs and the user profiles to which you will assign them are as follows:

• VLAN ID 1 for the Emp and IT user profiles (and for users not yet registered through a captive web portal)

• VLAN ID 2 for the VoIP user profile

• VLAN ID 3 for the Guests user profile

1. Click Configuration > Network Objects > VLANs > New, enter the following, and then click Save:

• VLAN Name: VLAN-1-EmployeeData

• Enter the following, and then click Apply:

•VLAN ID: 1

•Type: Global

•Description: VLAN for Emp, IT, and unregistered CWP users

2. Click Configuration > Network Objects > VLANs > (check box) VLAN-1-EmployeeData > Clone, make the

following changes, and then click Save:

• VLAN Name: VLAN-2-EmployeeVoice

•VLAN ID: 2

•Type: Global

•Description: VLAN for VoIP traffic

3. Click Configuration > Network Objects > VLANs > (check box) VLAN-2-VoIP > Clone, make the following

changes, and then click Save:

• VLAN Name: VLAN-3-Guests

•VLAN ID: 2

•Type: Global

•Description: VLAN for guests visiting corporate

1. There is a predefined VLAN definition for VLAN ID 1, so it is not really necessary to create a new VLAN object for it. However,

because later examples in this chapter refer to VLAN 1 by the name defined here ("VLAN-1-EmployeeData"), its purpose will

hopefully be clearer than if it were referred to by the simpler name of the predefined VLAN ("1").

Note: When defining the following VLANs, choose Global as the VLAN type because you do not need to restrict

these VLANs to a particular set of HiveAPs, which is what the other three options allow you to do.