User's Guide

available as a subscribeable event. Programmers can leverage the Extreme Campus Controller Python
SDK as a method to access and subscribe to such events. Each station event contains the following
information:
• MULOG_TYPE_LOCATION
• AP MAC address
• Floor ID
• EID_LOCATOR_POINT_SET (This binary payload contains one set of X/Y coordinates and the
probability as 32-bit integers.)
Python SDK is required to access the Location Update messages. For programmable access to Extreme
Campus Controller Python SDK, see Python SDK for Extreme Campus Controller. The messages are not
visible in the Extreme Campus Controller user interface.
To suppress Location Update messages, access the Positioning Profile within the device group
configuration Profile, and set the Collection setting to O.
Client Location Tracking is supported on AP39xx, AP3xx, AP4xx, and AP5xx. Estimating location using
readings from multiple APs provides a more accurate location estimate. Estimating location using RSS
from a single AP is sucient to determine the location of client in terms of proximity to the associated
AP. The client location is indicated on the map with an icon that is representative of the specific client
type. The Positioning Engine tracks location of multiple clients simultaneously and returns position
relative to the floor plan. The Positioning Engine can be configured to track associated users (active
clients) or all users. When Positioning is configured for all clients, Location Update messages are sent
for all tracked MAC addresses — both associated clients and non-associated clients.
• Associated User. An associated user is an authenticated client. An associated user joins the SSID
provided by the AP by simply associating to the open or protected SSID. Positioning Engine can
track location for every associated client up to the Extreme Campus Controller model limit of
associated clients.
• Un-Associated User. An unassociated user is a client that is not authenticated but is in the
designated area. Positioning Engine can track these clients.
Related Topics
Positioning Profile Settings on page 154
Position Aware Deployment on page 25
ExtremeLocation Profile Settings on page 148
Position Aware Deployment
Deploying APs for location tracking requires additional consideration above the standard AP
deployment guidelines for coverage and capacity. The following are best practices for AP deployment:
• Minimum Received RSS. No fewer than three APs should be detecting and reporting the RSS of any
client station. Only RSS readings stronger than -75 dBm are used by the Location Engine.
• Use the same AP model for the entire floor plan.
• Design your floor plan with the APs installed at the corners of the floor plan, along the perimeter of
the location area. (An area is considered a closed polygon.) Do not cluster APs in the center of the
location area. The following illustration shows a recommended AP placement.
Welcome to Extreme Campus Controller
Floor Plans
Extreme Campus Controller User Guide for version 5.46.03 25