User's Guide

Table Of Contents
hwc_vnsintro.fm
Virtual Network Services concepts
Setting up a VNS checklist
9034530-02,
March 2010
HiPath Wireless Controller, Access Points and Convergence Software V7.11, User Guide 229
Proper definition and selection of the user Policy would define the filters to be
applied to the users and user groups in order to control network access.
The quality of service (QoS) definition is part of the WLAN Services
requirements.
The privacy mechanisms that should be employed between the Wireless APs
and the wireless devices are also configurable at the level of WLAN services.
Classification list for traffic priority. For example, whether the VNS is to be
used for voice traffic and if voice traffic is to be given priority.
User access plan
The user access plan should analyze the enterprise network and identify which
users should have access to which areas of the network. What areas of the
network should be separated? Which users can go out to the World Wide Web?
The HiPath Wireless Controller, Access Points and Convergence Software
system relies on authenticating users via a RADIUS server (or other
authentication server). To make use of this feature, an authentication server on
the network is required. Make sure that the server's database of registered users,
with login identification and passwords, is current.
In the case of certificate-based installations, you must ensure that the proper user
certificate profiles are setup on the RADIUS server and mobile user.
Note: Deploying Controller, Access Points and Convergence Software without a
RADIUS server (and without authentication of users on the network) is also
possible.
The user access plan should also identify the user groups in your enterprise, and
the business structure of the enterprise network, such as:
Department (such as Engineering, Sales, Finance)
Role (such as student, teacher, library user)
Status (such as guest, administration, technician)
For each user group, you should set up a filter ID attribute in the RADIUS server,
and then associate each user in the RADIUS server to at least one filter ID name.
You can define specific filtering rules, by filter ID attribute, that will be applied to
user groups to control network access. Filtering is applied by the controller. The
controller checks if there is a Policy with a matching name (Filter ID = Policy
name) and applies the set of filter rules from that policy to the session.
Filter ID assignments is a configuration option, and not a requirement to setup per
user filter ID definitions. If a filter is not returned as an attribute in the RADIUS
server’s confirmation (Access-Accept packet) for a particular user, the controller
uses the default filter policy as the applicable filter set.