HP MSM313, Deployment Manual

Page: 47 / 78

HP MSM313/MSM323 Deployment Guide 45 2 Public/guest networks
Scenario 5: Custom HTML pages on each AP
This scenario describes how to create a customized user experience based on the AP with which a
user is associated. This scenario uses locally configured attributes and does not require a RADIUS
server.
How it works
In this scenario wireless networking for a condo complex is deployed using multiple APs and a
single service controller. The complex features three buildings, each with several condos serviced
by a single AP.
Since tenant turnover is low, and network access is included in the monthly condo fee, accounting
support is not needed. Therefore this scenario does not use a RADIUS server. Instead, all logins
are validated by the service controller using a locally defined user list.
To offer personalized service for each building, a set of custom web pages are created for each
building and stored in a separate folder on a web server. (A third-party server on the Internet is
used to keep costs down.) Users are redirected to the appropriate set of pages based on the
location-aware group name assigned to each AP.
About the location-aware feature
This feature, which is enabled by default, permits the service controller to determine the physical
location where users are logging into the network (as well as other information which can used for
user tracking). See the
HP MSM313/MSM323 Network Access Configuration Guide
for more
information on this feature.
This scenario uses the location-aware group name feature to assign a unique name to each AP.
When a user logs in, the AP reports this name to the service controller. The name is then used to
create a URL to a custom set of pages on the web server.