Table Of Contents
Configuring Non-IOS Access Points
Configuration Methods
Setting Up Non-IOS APs and Bridges—Using the Web Interface
Setting Up Non-IOS APs and Bridges—Using a WLSE Startup Template
Configuring Non-IOS Access Points
This chapter provides procedures to prepare non-IOS access points for basic network management by the WLSE.
Configuration Methods
You can perform initial setup of non-IOS access points in two ways:
•
By opening a web browser session on each access point—See Setting Up Non-IOS APs and Bridges—Using the Web Interface.
•
By using the WLSE startup configuration to apply a configuration template to a number of access points—See Setting Up Non-IOS APs and Bridges—Using a WLSE Startup Template.
After discovering and managing devices, you can use WLSE configuration templates for configuration changes—See the online help or the user guide at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/index.htm on Cisco.com.
Setting Up Non-IOS APs and Bridges—Using the Web Interface
To use this method, you must first configure each access point or bridge for web browsing.
Procedure
Step 1
Log in to the Web interface of the AP to be configured and click Setup in the Summary Status screen.
The Express Setup screen (Figure 2-1) is displayed.
Figure 2-1 Express Setup
Step 2
Enable Cisco Discovery Protocol (CDP).
This step is required for the WLSE to use CDP to discover the device. If you are not using CDP, you can add all APs as seed devices or import devices. See the online help or the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.11 on Cisco.com.
Figure 2-2 CDP Setup
a.
In the Summary Status page, click Setup.
b.
Under Services: Cisco Services, click Cisco Discovery Protocol.
The CDP Setup screen (Figure 2-2) is displayed.
c.
Select Enabled.
d.
Click Apply or OK.
Note
Do not run CDP on radio ports.
Step 3
Enable SNMP.
SNMP is supported on version 11.08T and later non-IOS APs.
SNMP is required for the WLSE to discover devices, populate reports, use configuration templates and configuration archives, and upgrade device firmware.
Setting the system name, system contact, and system location ensures that this information is included in device detail displays.
Figure 2-3 SNMP Setup
a.
In the Summary Status page, click Setup.
b.
Under Services, click SNMP.
The SNMP Setup screen (Figure 2-3) is displayed.
c.
Select Enabled.
d.
(Optional) Enter a System Name, System Location, and System Contact.
e.
Click Apply or OK.
Step 4
Set the read/write community string by adding a user or configuring an existing user.
The community string is required for device discovery, reports, configuration jobs, and firmware jobs.
The username is the AP read/write community. For example, if the AP has a user "lab" with password "cisco", its SNMP credential is lab::10:1:::lab. If the SNMP credential is set incorrectly, jobs on the AP will fail.
You must also enter all community strings on the WLSE. See the online help or the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.11.
Figure 2-4 User Information
a.
In the Summary Status page, click Setup.
b.
Under Services, click Security.
The User Information screen (Figure 2-4) is displayed.
c.
Click User Information; then click Add New User or select an existing user. The User Management screen is displayed.
d.
If adding a new user, enter the username and check all capability settings.
e.
If modifying an existing user, check all capabilities.
Note
Ident privileges are required only for APs that are running a firmware version earlier than 12.01T.
f.
Click Apply or OK.
Step 5
Add an HTTP user and enable the User Manager.
This step enables configuration uploads from the WLSE to access points.
You can use the same user that you used in Step 4 if the user has write, firmware, admin, and ident capabilities. The username and password become the HTTP username and password.
You can use a non-standard HTTP port. If HTTP browsing is not enabled on the AP, you must enable it. Enter the console and navigate to Security > Web Server. Enable Allow Non-Console Browsing. In the Summary Status page, click Setup.
You must also enter HTTP users and passwords on the WLSE. See the online help or the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.11.
Figure 2-5 User Manager
a.
In the Summary Status page, click Setup.
b.
Click Security.
c.
Click User Information.
The User Manager Setup screen (Figure 2-4) is displayed.
d.
Click Add New User or select an existing user.
e.
Enter a username and password and select Firmware; then click Apply.
f.
Return to the Security Setup page and click User Manager.
The screen in Figure 2-5 is displayed.
g.
Select Enabled; then click Apply or OK.
Step 6
If you use HTTP to initiate configuration or firmware downloads, select TFTP as the transfer protocol between the WLSE and APs.
TFTP is used for transferring configuration and firmware changes to access points.
If you use SNMP as the protocol for configuration and firmware update (instead of HTTP), you do not have to select the WLSE as the TFTP server on the access point. The SNMP MIB takes care of this part of the process.
Figure 2-6 FTP Setup
a.
In the Summary Status page, click Setup.
b.
Under Services, click FTP.
The FTP Setup screen (Figure 2-6) is displayed.
c.
Select TFTP as the file transfer protocol.
d.
In the Default File Server text box, enter the IP address of the WLSE.
e.
Click Apply or OK.
Setting Up Non-IOS APs and Bridges—Using a WLSE Startup Template
You can perform initial configuration on access points by using the WLSE's startup template feature.
Startup configuration works in conjunction with a DHCP server. The access points get their IP addresses from the DHCP server. If you prefer static IP addressing, you can either configure the DHCP server like a BOOTP server (using MAC address-to-IP address mapping) or configure the static IP address individually on each access point afterwards.
For information on using a startup template, see the online help or the "Managing Device Configuration" chapter in the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.11.