User's Guide

Table Of Contents
hwc_mobility.fm
Configuring Mobility
Mobility overview
9034530-02, March 2010
HiPath Wireless Controller, Access Points and Convergence Software V7.11, User Guide 405
8 Configuring Mobility
This chapter describes the mobility concept, including:
Mobility overview
Mobility domain topologies
Configuring mobility domain
8.1 Mobility overview
The HiPath Wireless Controller, Access Points and Convergence Software
system allows multiple HiPath Wireless Controllers (up to 12) on a network to
discover each other and exchange information about a client session. This
technique enables a wireless device user to roam seamlessly between different
Wireless APs on different HiPath Wireless Controllers.
The solution introduces the concept of a mobility manager; one HiPath Wireless
Controller on the network is designated as the mobility manager and all others
are designated as mobility agents.
The wireless device keeps the IP address, and the service assignments it
received from its home HiPath Wireless Controller—the HiPath Wireless
Controller that it first connected to. The WLAN Service on each HiPath Wireless
Controller must have the same SSID and RF privacy parameter settings.
You have two options for choosing the mobility manager:
Rely on SLP with DHCP Option 78
Define at the agent the IP address of the mobility manager. By explicitly
defining the IP address, the agent and the mobility manager are able to find
each other directly without using the SLP discovery mechanisms. Direct IP
definition is recommended in order to provide tighter control of the registration
steps for multi-domain installations.
The HiPath Wireless Controller designated as the mobility manager:
Is explicitly identified as the manager for a specific mobility domain. Agents
will connect to this manager to establish a mobility domain.
Defines at the agent the IP address of the mobility manager, which allows for
the bypass of SLP. Agents directly find and attempt to register with the
mobility manager.
Uses SLP, if this method is preferred, to register itself with the SLP Directory
Agent as SiemensNet.
Defines the registration behavior for a multi-controller mobility domain set: