Instance Association - Cisco WAP571 Administration Manual

Captive Portal

Instance Association

STEP 6
Instance Association
STEP 1
STEP 2
Cisco WAP571/E Administration Guide
When the first wireless client tries to authenticate with a VAP, the WAP
device sends an authentication request to the primary server. If the primary
server responds to the authentication request, the WAP device continues to
use this RADIUS server as the primary server, and the authentication
requests are sent to the specified address.
• Server IP Address 2 through 4 or Server IPv6 Address 2 through 4—Enter
up to three IPv4 or IPv6 backup RADIUS server addresses. If authentication
fails with the primary server, each configured backup server is tried in
sequence.
• Key 1—Enter the shared secret key that the WAP device uses to
authenticate to the primary RADIUS server. You can use up to 63 standard
alphanumeric and special characters. The key is case sensitive and must
match the key configured on the RADIUS server. The text you enter is shown
as asterisks.
• Key 2 to Key 4—Enter the RADIUS key associated with the configured
backup RADIUS servers. The server at Server IP (IPv6) Address 1uses Key
1, the server at Server IP (IPv6) Address 2uses Key 2, and so on.
• Locale Count—The number of locales associated with the instance. You can
create and assign up to three different locales to each CP instance from the
Web Customization page.
• Delete Instance—Check to delete the current instance.
Click Save. Your changes are saved to the Startup Configuration.
After you create an instance, use the Instance Association page to associate a CP
instance to a VAP. The associated CP instance settings applies to users who
attempt to authenticate on the VAP.
To associate an instance to a VAP:
Select Captive Portal > Instance Association.
Choose the radio that you want to configure.
11
162