User's Guide

Overview of the HiPath Wireless Controller, Access Points and Convergence Software solution
hwc_intro.fm
HiPath Wireless Controller, Access Points and Convergence Software and your network
9034530-02, March 2010
34 HiPath Wireless Controller, Access Points and Convergence Software V7.11, User Guide
As mentioned previously, policies can be configured using the NetSight Policy
Manager and pushed to the HiPath Wireless Controller, or they can be configured
directly on the controller. When using Policy Manager, you should note that the
HiPath Wireless Controller implements most of the Policy Manager concept of
Policy except for QoS assignment. The HiPath Wireless Controller implements
per policy inbound and outbound rate limits, but not policy-based DSCP
remarking or queue assignment.
2.3.4.3 WLAN Services
A WLAN Service represents all the RF, authentication and QoS attributes of a
wireless access service offered by the HiPath Wireless Controller and its APs. A
WLAN Service can be one of three basic types:
• Standard — A conventional service. Only APs running HiPath Wireless
software can be part of this WLAN Service. This type of service is useable as
a Bridged at Controller, Bridged at AP, or Routed Topology. This type of
service provides access for mobile stations. Policies can be associated with
this type of WLAN service to create a VNS.
• Third Party AP — A Wireless Service offered by third party APs. This type of
service provides access for mobile stations. Policies can be assigned to this
type of WLAN service to create a VNS.
• WDS — This represent a group of APs organized into a hierarchy for
purposes of providing a Wireless Distribution Service. This type of service is
in essence a wireless trunking service rather than a service that provides
access for stations. As such, this type of service cannot have policies
attached to it.
In release V7.0, the components of a WLAN Service map to the corresponding
components of a VNS in previous releases. The exception is that WLAN Services
are not classified as SSID-based or AAA-based, as was the case in previous
releases. Instead, the administrator makes an explicit choice of the type of
authentication to use on the WLAN Service. If his choice of authentication option
conflicts with any of his other authentication or privacy choices, the WLAN
Service cannot be enabled.
2.3.5 Static routing and routing protocols
Routing can be used on the HiPath Wireless Controller to support the VNS
definitions. Through the user interface you can configure routing on the HiPath
Wireless Controller to use one of the following routing techniques:
•Static routes – Use static routes to set the default route of a HiPath Wireless
Controller so that legitimate wireless device traffic can be forwarded to the
default gateway.