Example 2: Defining Network Objects - Aerohive HiveAP 20 ag Deployment Manual

Multi-channel
Table of Contents

Advertisement

Chapter 4 HiveManager Examples
E
2: D
XAMPLE
EFINING
Network objects are the most basic elements that you can configure through the HiveManager and only function
when other configured items such as QoS classifiers, SSID profiles, and hive profiles make reference to them. IP
addresses, MAC addresses, MAC OUIs (organizationally unique identifiers), and network services (HTTP, SMTP,
FTP, ...) are network objects that make no reference to any other previously defined object. The HiveManager also
classifies MAC filters as a type of network object; however, you must first create a MAC address or MAC OUI that you
then use when defining the MAC filter, so it is not quite as basic as the others.
In this example, you define a MAC OUI object for the type of VoIP (Voice over IP) phones in use in the network and
assign it to Aerohive class 6. After you configure QoS (Quality of Service) settings for voice traffic, HiveAPs can then
use the OUI to distinguish voice traffic so that they can prioritize it (see
Settings" on page
45).
You also define a MAC filter using the same OUI for use when configuring an SSID to which you only want VoIP clients
with that OUI to associate (see
Other critical IP telephony services are DHCP and DNS for address and domain name assignments, and TFTP and
HTTP for configuration downloads and software updates. You map traffic using destination port numbers 53 (DNS)
and 67 (DHCP) to Aerohive class 5. You map traffic using destination port numbers 69 (TFTP) and 80 (HTTP) to
Aerohive class 2. HiveAPs check if an incoming packet matches a classifier map by checking for matches in the
following order. They then use the first match found:
1. Service
2. MAC OUI
3. Ingress interface
4. Existing priorities used by various standard QoS classification systems (802.11e, 802.1p, and DSCP)
After VoIP clients associate with the SSID, the HiveAP maps all DNS and DHCP traffic to class 5, all TFTP and HTTP
traffic to class 2, and all remaining traffic—VoIP traffic in this case—to class 6 (see
Figure 6 MAC OUI and Service Classifier Maps for VoIP Phones
42
N
ETWORK
"Example 4: Setting SSID Profiles" on page
O
BJECTS
"Example 3: Defining User Profiles and QoS
49).
Figure
6).
Aerohive

Advertisement

Table of Contents
loading

Table of Contents