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 User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.9.

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.

Log in to the Web interface of the AP to be configured and set the following parameters.

Table 2-1 Set Up Procedures for Non-IOS Access Points and Bridges 

Tasks	Procedure	Notes
1. Enable Cisco Discovery Protocol (CDP).1	1. In the Summary Status page, click Setup. 2. Under Services: Cisco Services, click Cisco Discovery Protocol and select Enabled. 3. Click Apply or OK.	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.9.
2. Enable SNMP. SNMP is supported on version 11.08T and later non-IOS APs.	1. In the Summary Status page, click Setup. 2. Under Services, click SNMP. 3. Select Enabled. 4. (Optional) Enter a System Name, System Location, and System Contact. 5. Click Apply or OK.	SNMP is required for the WLSE to discover devices, populate reports, transfer configuration information to devices, and upgrade device firmware. Setting the system name, system contact, and system location ensures that this information is included in device detail displays.
3. Set the read/write community string.	1. In the Summary Status page, click Setup. 2. Under Services, click Security. 3. Click User Information; then click Add New User or select an existing user. 4. Check all capabilities. Ident privileges are required only for APs that are running a firmware version earlier than 12.01T. 5. Click Apply or OK.	The community string is required for device discovery, reports, and for configuration and firmware jobs. The username is the AP read/write community.2 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.9.
4. Add an HTTP user and enable the User Manager.3 You can use the same user that you created in Task 3, if the user has write, firmware, admin, and ident capabilities.	1. In the Summary Status page, click Setup. 2. Click Security. 3. Click User Information; then click Add New User or select an existing user. 4. Enter a username and password and select Firmware; then click Apply. 5. Return to the Security Setup page and click User Manager. 6. Select Enabled; then click Apply or OK.	Allows configuration uploads from the WLSE to access points. 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.9.
5. If you use HTTP to initiate configuration or firmware downloads, select TFTP as the transfer protocol between the WLSE and APs.	1. In the Summary Status page, click Setup. 2. Under Services, click FTP. 3. Select TFTP as the file transfer protocol. 4. In the Default File Server text box, enter the IP address of the WLSE. 5. Click Apply or OK.	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.

1 Do not run CDP on radio ports. 2 For example, if the AP has a user "lab" with password "cisco", its SNMP credential is lab::10:1:::lab. Its HTTP username/password is lab/cisco. If the SNMP credential is set incorrectly, jobs on the AP will fail. 3 You can use a non-standard HTTP port. If HTTP browsing is not enabled, you must enable it. Enter the console and navigate to Security > Web Server. Enable Allow Non-Console Browsing.

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.9.