Specifications

Availability and Mobility configuration
Summit WM Getting Started Guide, Software Version 5.1118
Viewing the active Wireless APs report
To view the active Wireless APs report:
1 From the main menu, click Reports & Displays. The Reports & Display screen is displayed.
2 In the List of Displays, click Active Wireless APs. The Active Wireless APs display appears.
Mobility overview
The Summit WM Wireless LAN (WLAN) Solution allows multiple Summit WM Controllers (up to 12)
on a network to discover each other and exchange information about a client session. This feature
enables a wireless device user to roam seamlessly between Wireless APs that are registered with
separate Summit WM Controllers.
The solution introduces the concept of a mobility manager and mobility agents; the concept requires
designating one Summit WM Controller as the mobility manager and other Summit WM Controllers as
mobility agents.
The wireless device keeps the IP address, WM-AD assignment, and filtering rules it received from its
home Summit WM Controller — the Summit WM Controller to which it was first connected.
The WM-AD on each Summit WM Controller must have the same SSID and RF privacy parameter
settings for seamless roaming to occur.
The mobility manager and the mobility agents use the following two options for the discovery process.
● SLP with DHCP Option 78. The mobility agent on each Summit WM Controller will discover the
address of the mobility manager using Option 78.
● Direct IP address option: Defined while configuring the mobility agent. By explicitly defining the
manager’s IP address while configuring the agents, enables the manager and agents to find each
other directly without using the SLP discovery mechanisms.
NOTE
In order to provide tighter control of the registration steps for multi-domain installations, direct IP address
definition option is recommended.
The mobility manager:
● Defines the registration behavior for a multi-Summit WM Controller mobility domain set:
● Open mode – A new agent automatically registers itself with the mobility manager and
immediately becomes part of the mobility domain.
● Secure mode – The 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
connection.
● Listens for connection attempts from mobility agents.
● Establishes connection and sends a message to the mobility agent specifying the heartbeat interval
and the IP address in Mobility Permission List.
● Sends regular Heartbeat messages containing wireless device session changes and waits for a return
update message.