MSM7xx Controllers Configuration Guide v6.4.0

In this example, the traffic for each wireless network is carried on its own VLAN. This leaves only
management traffic from the autonomous AP on VLAN 10. A static IP is assigned on both ends to
permit the two devices to communicate.
Working with third-party autonomous APs
Third-party APs can be used with a controller with both access controlled and non-access-controlled
VSCs.
VSC selection
User traffic from third-party APs is mapped to a VSC on the controller in the same way as for MSM
APs. See “Using multiple VSCs” (page 138). This means that traffic is assigned to the default VSC,
unless it is on a VLAN, in which case it is assigned to the VSC with matching VLAN ingress
definition.
Because the HP location-aware feature is not available on third-party APs, support for VSC selection
using an SSID requires that the following additional configuration be performed:
• Configure the AP to send its SSID as the NAS ID in all authentication and accounting requests.
• Enable the Detect SSID from NAS-Id option on the Controller >> Authentication > RADIUS
server page.
536 Working with autonomous APs