Filter
Top Products
Working with autonomous APs
Working with third-party autonomous APs
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 segment. 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 service 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 service controller in the same
way as for MSM APs. See Using multiple VSCs on page 2-24. 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 ProCurve Networking 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 Service controller >>
Authentication > RADIUS server page.
14-6