(hereafter called access points) provide a secure, affordable, and easy-to-use wireless LAN solution that combines mobility and flexibility with the enterprise-class features required by networking professionals. With a management system based on Cisco IOS software, Cisco s are Wi-Fi certified, 802.11b-compliant, 802.11g-compliant, and 802.11a-compliant wireless LAN transceivers.
An serves as the connection point between wireless and wired networks or as the center point of a stand-alone wireless network. In large installations, wireless users within radio range of an can roam throughout a facility while maintaining seamless, uninterrupted access to the network.
You can configure and monitor the wireless device using the command-line interface (CLI), the browser-based management system, or Simple Network Management Protocol (SNMP).
•The 1230AG series is pre-configured to include both an 802.11g and an 802.11a radio. It has antenna connectors for externally attached antennas for both radios.
•The 1240AG series access point uses externally connected antennas for each band instead of built-in antennas.
This chapter provides information on the following topics:
•Network Configuration Examples
•Network Configuration Examples
•How to Log-in to an Access Point
s running Cisco IOS software.
Note The proxy Mobile-IP feature is not supported in Cisco IOS Releases 12.3(2)JA and later.
Features Introduced in This Release
•Support for the Cisco Aironet 1240AG Series Access Point—This release fully supports the Cisco Aironet 1240AG Series Access Point.
•Access Point Link Role Flexibility—This feature provides bridge mode functionality support for access points having dual-band capability (1200, 1230, and 1240AG series). In the target configuration, the 802.11a radio is running in bridge mode while the 802.11g radio is in the access point mode.
Note The Access Point Link Role Flexibility is not supported on 350, 1100, and 1130AG series access points.
•QoS Basic Service Set (QBSS) support—This feature aligns Cisco QBSS implementation with the evolving 892.11e standard. The QBSS element of the access point's beacon advertises channel load instead of traffic load. A new configuration command, dot11 phone dot11e has been added in Release 12.3(7) that allows the standard QBSS Load element to be sent in the beacon. This command should be used when compatible phones are employed in the network.
•AAA Authentication/Authorization Cache and Profile—This feature reduces the authentication load on RADIUS/TACACS servers caused when loading GUI pages by caching the authentication locally on the access point so only one authentication with the RADIUS/TACACS server is performed.
Note The feature is supported only for administrative authentication on the access point. Other uses of this feature are not recommended and not supported.
•Secure Shell version 2 (SSHv2) support—SSH v2 is a standards-based protocol to provide secure Telnet capability for router configuration and administration.
•Support for Multiple BSSIDs—This feature permits a single access point to appear to the WLAN as multiple virtual access points. It does this by assigning an access point with multiple Basic Service Set IDs (MBSSIDs) or MAC addresses.
To determine whether a radio supports multiple basic SSIDs, enter the show controllers command for the radio interface. The radio supports multiple basic SSIDs if the results include this line:
Number of supported simultaneous BSSID on radio_interface: 8
•Support for Wi-Fi 802.11h and Dynamic Frequency Selection (DFS)—This feature allows Cisco Aironet access points configured at the factory for use in Europe and Singapore to detect radar signals such as military and weather sources and switch channels on the access points.
•Wireless IDS - Excess Management Frame Detection—This feature provides scanner access points the ability to detect that WLAN management and control frames exceeded a configurable threshold.
•Wireless IDS - Authentication Attack Detection—This feature requires Cisco Aironet access points to detect and report on excessive attempted or failed authentication attempts (Authentication failure detection and Excess EAPoL authentication).
•Frame Monitor Mode—This feature requires a Scan-only access point to forward all 802.11 frames seen to a protocol analysis station for network troubleshooting from remote sites via partner applications and/or partner Intrusion Detection companies.
•Location Based Services (LBS)—This feature allows a Cisco Aironet access point to detect frames from LBS tags and send them to a pre-configured IP destination, such as a third-party LBS server.
•SNMPv3—This feature enables SNMPv3 support on Cisco Aironet access points to provide an additional level of security.
•WGB Mode on 1200 Series Access Points—This feature allows 1200 series access points to support Work Group Bridge (WGB) functionality on either the 802.11b/g or 802.11a radio.
•World mode—Use this feature to communicate the regulatory setting information, including maximum transmit power and available channels, to world mode-enabled clients. Clients using world mode can be used in countries with different regulatory settings and automatically conform to local regulations.
•Multiple SSIDs—Create up to 16 SSIDs on the wireless device and assign any combination of these settings to each SSID:
–Broadcast SSID mode for guests on your network
–Client authentication methods
–Maximum number of client associations
–RADIUS accounting list identifier
•VLANs—Assign VLANs to the SSIDs on the wireless device (one VLAN per SSID) to differentiate policies and services among users.
•QoS—Use this feature to support quality of service for prioritizing traffic from the Ethernet to the . The also supports the voice-prioritization schemes used by 802.11b wireless phones such as Spectralink Netlink™ and Symbol Netvision™.
•RADIUS Accounting—Enable accounting on the to send accounting data about wireless client devices to a RADIUS server on your network.
•TACACS+ administrator authentication—Enable TACACS+ for server-based, detailed accounting information and flexible administrative control over authentication and authorization processes. It provides secure, centralized validation of administrators attempting to gain access to the wireless device.
•Enhanced security—Enable three advanced security features to protect against sophisticated attacks on your wireless network's WEP keys: Message Integrity Check (MIC), WEP key hashing, and broadcast WEP key rotation.
•Wi-Fi Protected Access (WPA)—Wi-Fi Protected Access is a standards-based, interoperable security enhancement that strongly increases the level of data protection and access control for existing and future wireless LAN systems. It is derived from and will be forward-compatible with the upcoming IEEE 802.11i standard. WPA leverages Temporal Key Integrity Protocol (TKIP) for data protection and 802.1X for authenticated key management.
•Access point as backup or stand-alone authentication server—You can configure an access point to act as a local authentication server to provide authentication service for small wireless LANs without a RADIUS server or to provide backup authentication service in case of a WAN link or a server failure. The access point can authenticate up to 50 LEAP-enabled wireless client devices and allow them to join your network. Access points can provide backup MAC-address authentication service for up to 50 addresses.
•HTTPS - HTTP with SSL 3.0—This feature supports a Secure Sockets Layer (SSL)/Secure Hypertext Transfer Protocol (HTTPS) method of managing Cisco s through a Web browser.
•AES-CCMP—This feature supports Advanced Encryption Standard-Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (AES-CCMP). AES-CCMP is required for Wi-Fi Protected Access 2 (WPA2) and IEEE 802.11i wireless LAN security.
•IEEE 802.1X Local Authentication Service for EAP-FAST—This feature expands wireless domain services (WDS) IEEE 802.1X local authentication to include support for Extensible Authentication Protocol-Flexible Authentication via Secure Tunneling (EAP-FAST). IEEE 802.1X local authentication was introduced in Cisco IOS Release 12.2(11)JA.
•Wi-Fi Multimedia (WMM) Required Elements—This feature supports the required elements of WMM. WMM is designed to improve the user experience for audio, video, and voice applications over a Wi-Fi wireless connection. WMM is a subset of the IEEE 802.11e Quality of Service (QoS) draft standard. WMM supports QoS prioritized media access via the Enhanced Distributed Channel Access (EDCA) method. Optional elements of the WMM specification including call admission control using traffic specifications (TSPEC) are not supported in this release.
•VLAN Assignment By Name—This feature allows the RADIUS server to assign a client to a virtual LAN (VLAN) identified by its VLAN name. In releases before Cisco IOS Release 12.3(2)JA, the RADIUS server identified the VLAN by ID. This feature is important for deployments where VLAN IDs are not used consistently throughout the network.
•HTTP Web Server v1.1—This feature provides a consistent interface for users and applications by implementing the HTTP 1.1 standard (see RFC 2616). In previous releases, Cisco software supported only a partial implementation of HTTP 1.0. The integrated HTTP Server API supports server application interfaces. When combined with the HTTPS and HTTP 1.1 Client features, provides a complete, secure solution for HTTP services to and from Cisco devices.
•IP-Redirect—This features provides the capability to redirect traffic intended for a particular destination to another IP address specified by the administrator.
You can use the wireless device management system through the following interfaces:
•The Cisco IOS command-line interface (CLI), which you use through a console port or Telnet session. Use the interface dot11radio global configuration command to place the wireless device into the radio configuration mode.
•A web-browser interface, which you use through a Web browser. Chapter 3 "Using the Web-Browser Interface," provides a detailed description of the web-browser interface.
•Simple Network Management Protocol (SNMP).
Network Configuration Examples
This section describes the access point role in common wireless network configurations. The access point default configuration is as a root unit connected to a wired LAN or as the central unit in an all-wireless network. Access points can also be configured as repeater access points, bridges, and workgroup bridges. These roles require specific configurations.
Root Access Point
An access point connected directly to a wired LAN provides a connection point for wireless users. If more than one access point is connected to the LAN, users can roam from one area of a facility to another without losing their connection to the network. As users move out of range of one access point, they automatically connect to the network (associate) through another access point. The roaming process is seamless and transparent to the user. Figure 1-1 shows access points acting as root units on a wired LAN.
Figure 1-1 Access Points as Root Units on a Wired LAN
The 1200 and 1240AG access points can be configured as root or non-root bridges. In this role, an access point establishes a wireless link with a non-root bridge. Traffic is passed over the link to the wired LAN. Access points in root and non-root bridge roles can be configured to accept associations from clients. Figure 1-2 shows an access point configured as a root bridge with clients. Figure 1-3 shows two access points configured as a root and non-root bridge, both accepting client associations. Consult the "Configuring the Role in Radio Network" section for instructions on setting up a 1200 or 1240AG series access point as a bridge.
Figure 1-2 Access Point as a Root Bridge with Clients
Figure 1-3 Access Points as Root and Non-root Bridges with Clients
You can configure access points as workgroup bridges. In workgroup bridge mode, the unit associates to another access point as a client and provides a network connection for the devices connected to its Ethernet port. For example, if you need to provide wireless connectivity for a group of network printers, you can connect the printers to a hub or to a switch, connect the hub or switch to the access point Ethernet port, and configure the access point as a workgroup bridge. The workgroup bridge associates to an access point on your network.
If your access point has two radios, either the 2.4-GHz radio or the 5-GHz radio can function in workgroup bridge mode. When you configure one radio interface as a workgroup bridge, the other radio interface is automatically disabled.
Figure 1-4 shows an access point configured as a workgroup bridge. Consult the "Understanding Workgroup Bridge Mode" section and the "Configuring Workgroup Bridge Mode" section for information on configuring your access point as a workgroup bridge.
Figure 1-4 Access Point as a Workgroup Bridge
Central Unit in an All-Wireless Network
In an all-wireless network, an access point acts as a stand-alone root unit. The access point is not attached to a wired LAN; it functions as a hub linking all stations together. The access point serves as the focal point for communications, increasing the communication range of wireless users. Figure 1-5 shows an access point in an all-wireless network.
Figure 1-5 Access Point as Central Unit in All-Wireless Network
How to Log-in to an Access Point
You can log-in to an access point by using one of these methods:
•Using the local console port—see the "Using the Local Console Port" section.
•Using a browser—see the "Using a Browser" section.
•Using Telnet—see the "Using Telnet" section.
Using the Local Console Port
The 1130, 1200, 1240, and 1250 series access points have a console port that can be used to log-in to the access point locally.
Note The 1100 and 1300 series access points do not have a console port. On the 1130 access point, you must open the access point cover to access the console port.
If you need to configure the access point locally (without connecting the access point to a wired LAN), you can connect a PC to its console port using a DB-9 to RJ-45 serial cable. The Cisco part number for the DB-9 to RJ-45 serial cable is AIR-CONCAB1200. To order a serial cable, browse to http://www.cisco.com/go/marketplace.
Follow these steps to open the console port and the access point CLI:
Step 1 Connect a nine-pin, female DB-9 to RJ-45 serial cable to the RJ-45 serial port on the access point and to the COM port on your PC.
Step 2 Set up a terminal emulator to communicate with the access point. Use the following settings for the terminal emulator connection: 9600 baud, 8 data bits, no parity, 1 stop bit, and no flow control.
Note If no flow control does not work, try Xon/Xoff flow control.
Step 3 Connect power to the access point. The access point displays the power up configuration sequence.
Step 4 When the power up sequence ends, press Enter and the access point CLI command prompt displays, such as AP>.
Step 5 When prompted, enter the username and password for the access point.
Note The access point default username is Cisco and the default password is Cisco.
You can now use the access point CLI to configure or revise the access point settings. For additional information on using the access point CLI, See the "Using the Command-Line Interface" section.
Note When your configuration changes are completed, you must remove the serial cable from the access point.
Using a Browser
You can use a Web browser and a Category 5 Ethernet cable to log-in to your access point locally or remotely. To connect to an access point locally, you use the Ethernet port on the access point. On the 1300 series access point, the Ethernet port is located on the power injector.
Note You do not need a special crossover cable to connect your PC to the access point; you can use either a straight-through cable or a crossover cable.
For local access to the 1100 series access point, if it is configured with default values and it does not receive an IP address from a DHCP server, it defaults to IP address 10.0.0.1 for five minutes. During that five minutes, you can browse to that IP address to configure the unit. If after five minutes the unit has not been reconfigured, it discards the 10.0.0.1 address and reverts to requesting an address from the DHCP server. If it does not receive an address, it sends requests indefinitely. If you miss the five-minute window for browsing to the access point at 10.0.0.1, you can power-cycle the access point to repeat the process.
Follow these steps to connect to the access point using your browser:
Step 1 For local access, follow these steps:
a. Make sure that the PC is configured with an IP address within the same subnet as the access point, such as 10.0.0.2 to 10.0.0.10 for an access point with an IP address of 10.0.0.1.
b. Connect a Category 5 Ethernet cable from your PC to the access point.
Note On the 1300 series access point, the Ethernet port is located on the power injector. On the 1130 series access point, you need to open the access point cover to access the Ethernet connector.
Step 2 For remote network access, follow these steps:
a. Make sure that your PC is configured to receive an IP address from a DHCP server.
b. Connect a Category 5 Ethernet cable from your PC to the network.
Step 3 PC Power up the access point.
Step 4 Turn on your PC and activate the Web browser.
Step 5 Enter the access point's IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer) and press Enter.
Step 6 When prompted, enter the username and password for the access point and click OK .
Note The access point default username is Cisco and the default password is Cisco.
The Summary Status page appears to enable you to configure or revise the access point settings.
Step 7 After configuring the access point using the local Ethernet port, remove your Ethernet cable from the access point or power injector and connect the access point to your wired LAN.
Note When you connect your PC to the access point or reconnect your PC to the wired LAN, you might need to release and renew the IP address on the PC. On most PCs, you can perform a release and renew by rebooting your PC or by entering ipconfig /release and ipconfig /renew commands in a command prompt window. Consult your PC operating instructions for detailed instructions.
Note On the 1300 series access point, communication takes place between the power injector and the access point using Ethernet Port 0. Do not change any of the Ethernet Port 0 settings.
For additional information, see the Using the "Using the Web-Browser Interface" section.
To use Telnet to log-on to an access point connected to the wired LAN, follow these instructions:
Step 1 Make sure that your PC is configured to receive an IP address from a DHCP server and is connected to the wired LAN.
Step 2 Click Start > Run > Telnet and click OK .
Step 3 In the Telnet window, type open and the IP address of the access point, for example, open 10.0.0.1. Press Enter.
Step 4 When prompted, enter the username for the access point and press Enter.
Note The access point default username is Cisco.
Step 5 When prompted, enter the password for the access point and press Enter. The access point CLI prompt appears, such as AP>.
Note The access point default password is Cisco.
You can now use CLI commands to configure or revise the access point settings.
For additional information, see the "Using the Web-Browser Interface" section.