User's Manual

Availability, mobility, and controller functionality
hwc_controlleravailmobility.fm
Mobility manager
A31003-W1050-U100-2-7619
, March 2008
260 HiPath Wireless Controller, Access Points and Convergence Software V5 R1 , C20/C2400 User Guide
• 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:
• Open mode – A new agent is automatically able to register itself with the
mobility manager and immediately becomes part of the mobility domain
• Secure mode – The mobility manager does not allow a new agent to
automatically register. Instead, the connection with the new agent is
placed in pending state until the administrator approves the new device.
• Listens for connection attempts from mobility agents
• Establishes connection and sends a message to the mobility agent specifying
the Heartbeat interval, and the mobility manager's IP address if it receives a
connection attempt from the agent
• Sends regular Heartbeat messages containing wireless device session
changes and agent changes to the mobility agents and waits for a returned
update message
The HiPath Wireless Controller designated as a mobility agent:
• Uses SLP or a statically configured IP address to locate the mobility manager
• 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.
• Attempts to establish a TCP/IP connection with the mobility manager
• Updates its tables, and sets up data tunnels to and between all HiPath
Wireless Controllers it has been informed of when it receives the connection-
established message
• Uses the information from every Heartbeat message received to update its
own tables and updates the mobility manager with information on the wireless
device users and data tunnels it is managing
If a controller configured as the mobility manager is lost, the following occurs:
• Agent to agent connections will remain active.
• Mobility agents will continue to operate based on the mobility information last
coordinated before the manager link was lost. The mobility location list
remains relatively unaffected by the controller failure. Only entries associated
with the failed controller are cleared from the registration list, and users that