User's Guide

Table Of Contents
Virtual Network Services concepts
hwc_vnsintro.fm
Setting up a VNS checklist
9034530-02, March 2010
228 HiPath Wireless Controller, Access Points and Convergence Software V7.11, User Guide
5.2 Setting up a VNS checklist
When you set up a VNS on the HiPath Wireless Controller, you are defining a
topology, policies, and WLAN services for a group of wireless device users.
The checklist suggested in this section is focused on strictly necessary
parameters and selections an administrator has to consider. Proper full contexts
(such as topology, policy, WLAN services) are further described in Chapter 6,
“Configuring a VNS”.
The HiPath Wireless Controller provides the option to define a topology as locally
bridged to a VLAN at the controller. To support that configuration, you must define
which VLAN ID should be used. The network port on which the VLAN is assigned
must be configured on the switch, and the corresponding HiPath Wireless
Controller port must match the correct configuration. With this configuration, it is
possible that the controller is not involved in the IP address assignment for user
addresses. Instead, the IP addresses for users are assigned directly by the
DHCP infrastructure that services the VLAN.
Note: In a VLAN-bridged topology, the default configuration dictates that the
controller is not the DHCP server for that segment. However, DHCP services can
selectively be enabled, including DHCP Relay, allowing you to use the controller
to become the default DHCP server for the VLAN, if applicable.
Before defining a VNS, the following properties must be determined across
topology, policy, and WLAN services:
A user access plan for both individual users and user groups.
The RADIUS attribute values that support the user access plan.
The location and identity of the Wireless APs that will be used on the VNS.
The routing mechanism to be used on the associated topology.
For tunneled configurations mostly, the network addresses that the topology
will use.
A bridge traffic locally at the HWC topology optionally needs the specification
of the IP address for the controller's own interface point on that VLAN.
Alternatively, other modes for topology can be used (bridged at AP, routed,
3rd Part AP).
In addition, if you elect to have the controller operate as the default DHCP
server for the VLAN, the corresponding IP subnet for that subnet must also
be specified.
The type of authentication for wireless device users on the associated WLAN
service mapped to the desired VNS.