Cisco Aironet 700W Series User manual

GETTING STARTED GUIDE
Cisco Aironet 700W Series Access Points
1About this Guide
2Introduction to the Access Point
3Safety Instructions
4Unpacking
5Configurations
6Access Point Ports and Connectors
7Configuring the Access Point
8Mounting the Access Point
9Deploying the Access Point on the Wireless Network
10 Troubleshooting
11 Access Point Specifications Data Sheet
12 Declarations of Conformity and Regulatory Information
13 Configuring DHCP Option 43 and DHCP Option 60
14 Obtaining Documentation and Submitting a Service Request

2
OL-31342-01, May 7, 2014

3
1 About this Guide
This Guide provides instructions on how to install and configure your Cisco Aironet 700W Series Access Point. The 700W Series
Access Point is referred to as the 700W series or the access point in this document.
2 Introduction to the Access Point
The 700W series supports high-performing two spatial stream rates over a deployable distance with high reliability when serving
clients. The 700W series provides high reliability and overall wireless performance.
The 700W series offers dual-band radios (2.4 GHz and 5 GHz) with integrated internal antennas. The access point supports full
inter-operability with leading 802.11n clients.
The 700W series access point is available in the controller-based configuration and supports:
•Simultaneous dual-band (2.4 GHz/5 GHz) radios
•Integrated internal antennas only
Note The 700W series access points will have the model number AIR-CAP702W-x-K9, where the ‘x’ represents the
regulatory domain. Refer to “Regulatory Domains” section on page 5 for a list of supported regulatory domains.
The features of the 700W series are:
•Processing sub-systems (including CPUs and memory) and radio hardware which supports:
– Unified
– FlexConnect
– Monitor-mode
– VideoStream
– Location (not available on autonomous or standalone models)
– WIDS/WIPS (not available on autonomous or standalone models)
– Security
– Radio Resource Management (RRM) (not available on autonomous or standalone models)
– Rogue detection (not available on autonomous or standalone models)
– Management Frame Protection (MFP) (not available on autonomous or standalone models)
– BandSelect (not available on autonomous or standalone models)
Note Enhanced Local Mode (ELM) is not supported.
•The following processor features:
– 128 MB NAND flash size
– 1 MB NOR flash size
– 128 MB DDR2 memory bus, x32
•2.4 GHz and 5 GHz 802.11n radios with the following features:
– 802.11n standard compliant
– A-MPDU TX
– HT Duplicate Mode
– 2TX x 2RX
– 2-spatial streams, 300 Mbps PHY rate
– Maximal ratio combining (MRC)
– Cyclic Shift Diversity (CSD)

4
– MCS0-MCS15; Short or Long Guard Intervals
– DFS for UNII-2 and UNII-2 Extended channels, including 0.5us radar pulse detection
3 Safety Instructions
Translated versions of the following safety warnings are provided in the translated safety warnings document that is shipped
with your access point. The translated warnings are also in the Translated Safety Warnings for Cisco Aironet Access Points,
which is available on Cisco.com.
Warning IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any
equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for
preventing accidents. Use the statement number provided at the end of each warning to locate its translation in
the translated safety warnings that accompanied this device.
Statement 1071
SAVE THESE INSTRUCTIONS
Warning Read the installation instructions before you connect the system to its power source. Statement 1004
Warning Installation of the equipment must comply with local and national electrical codes. Statement 1074
Warning This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that the
protective device is rated not greater than:
20A. Statement 1005
Warning Do not operate your wireless network device near unshielded blasting caps or in an explosive environment unless
the device has been modified to be especially qualified for such use. Statement 245B
Warning In order to comply with FCC radio frequency (RF) exposure limits, antennas should be located at a minimum of 7.9
inches (20 cm) or more from the body of all persons.
Statement 332
Caution The fasteners you use to mount the access point must be capable of maintaining a minimum pullout force of 20 lbs
(9 kg) and must use a minimum of 2 holes on the mounting bracket.
Caution This product and all interconnected equipment must be installed indoors within the same building, including the
associated LAN connections as defined by Environment A of the IEEE 802.af/at Standard.
Note Use only with listed ITE equipment.

5
4 Unpacking
To unpack the access point, follow these steps:
Step 1 Unpack and remove the access point and the accessory kit from the shipping box.
Step 2 Return any packing material to the shipping container and save it for future use.
Step 3 Verify that you have received the items listed below. If any item is missing or damaged, contact your Cisco representative
or reseller for instructions.
•The access point
•Mounting bracket
•Mounting screws
•Tamper resistant screw
•Mylar label for tamper resistant screw
5 Configurations
The 700W series access point contains two simultaneous dual-band radios, the 2.4 GHz and 5 GHz 802.11n MIMO radios, in
a controller-based mode.
The 700W series access point configuration is AIR-CAP702W-x-K9—two 2.4 GHz/5 GHz dual-band radios, with two
integrated dual-band antennas.
For information on the regulatory domains (shown as “x” in the model numbers) see “Regulatory Domains” section on page 5.
Internal Antennas
The 700W series access points are configured with two dual-band antennas (two 2.4 GHz and two 5 GHz). The two antennas,
deployed inside the access point, are inside the top housing. The basic features are as follows:
•Dual-Band antennas.
•Antenna elements integrated into 700W access point top housing.
•Peak gains are approximately 2 dBi in the 2.4 GHz band and 4 dBi in the 5 GHz band.
Regulatory Domains
The 700W series supports the following regulatory domains (shown as “x” in the model numbers):
•-A, -C, -D, -E, -H, -I, -K, -N, -Q, -R, -S, -T, -Z
Countries Supported
Click this URL to browse to a list of countries and regulatory domains supported by the 700W:
www.cisco.com/go/aironet/compliance
6 Access Point Ports and Connectors
The 700W series access points have integrated antennas and do not have external connectors on the top of the unit. In addition
to the integrated antennas the 700W series access points has the following interfaces and connectors:
•LED

6
•Four LAN ports
•Uplink port and Console port
•Mode button
•DC power connector
•Kensington lock slot
Figure 1 Access Point 700W (Front View)
Figure 2 Access Point 700W (Top View)
1Security Screw Hole
352543
352509
1

7
Figure 3 Access Point LED (Bottom View)
1LED Indicator 2From left to right, LAN Ports 1 to 4. The right most port
(LAN 4) is PoE-out.
2
352541
1

8
Figure 4 Access Point Ports and Connections (Rear View)
1Console port 3Mounting bracket slot
2Uplink (Ethernet WAN) port 4Mode button
352544
1
4
2
3

9
Figure 5 Access Point DC Power Connector (Side View)
7 Configuring the Access Point
This section describes how to connect the access point to a wireless LAN controller. Because the configuration process takes
place on the controller, see the Cisco Wireless LAN Controller Configuration Guide for additional information. This guide is
available on Cisco.com.
The Controller Discovery Process
The access point uses standard Control and Provisioning of Wireless Access Points Protocol (CAPWAP) to communicate
between the controller and other wireless access points on the network. CAPWAP is a standard, interoperable protocol which
enables an access controller to manage a collection of wireless termination points. The discovery process using CAPWAP is
identical to the Lightweight Access Point Protocol (LWAPP) used with previous Cisco Aironet access points. LWAPP-enabled
access points are compatible with CAPWAP, and conversion to a CAPWAP controller is seamless. Deployments can combine
CAPWAP and LWAPP software on the controllers.
Customers who have Layer 2 deployments should note that CAPWAP is not supported on Layer 2 as the CAPWAP packets are
routed through Layer 3 only.
In a CAPWAP environment, a wireless access point discovers a controller by using CAPWAP discovery mechanisms and then
sends it a CAPWAP join request. The controller sends the access point a CAPWAP join response allowing the access point to
join the controller. When the access point joins the controller, the controller manages its configuration, firmware, control
transactions, and data transactions.
Note For additional information about the discovery process and CAPWAP, see the Cisco Wireless LAN Controller Software
Configuration Guide. This document is available on Cisco.com.
Note CAPWAP support is provided in controller software release 5.2 or later. However, your controller must be running
release 8.0.x.x or later to support 700W series access points.
1DC Power Connector Port
2Kensington Lock Slot
1
2
352542

10
Note Make sure that the controller is set to the current time. If the controller is set to a time that has already occurred, the
access point might not join the controller because its certificate may not be valid for that time.
Access points must discovered a controller before they can become an active part of the network. The access point supports
these controller discovery processes:
•Layer 3 CAPWAP discovery—The access point performs a local broadcast (255.255.255.255) discovery request to find any
contollers on the same subnet/vlan. The request can be forwarded to other networks by the IP helper featuer that is present
on switches and router.
•Locally stored controller IP address discovery—If the access point was previously joined to a controller, the IP addresses of
the primary, secondary, and tertiary controllers are stored in the access point’s non-volatile memory. This process of storing
controller IP addresses on an access point for later deployment is called priming the access point. For more information
about priming, see the “Performing a Pre-Installation Configuration” section on page 11.
•DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses to the access points. Cisco
switches support a DHCP server option that is typically used for this capability. For more information about DHCP option
43, see the “Configuring DHCP Option 43 and DHCP Option 60” section on page 29.
•DNS discovery—The access point can discover controllers through your domain name server (DNS). For the access point
to do so, you must configure your DNS to return controller IP addresses in response to
CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain is the access point domain name. Configuring the
CISCO-CAPWAP-CONTROLLER provides backwards compatibility in an existing customer deployment. When an access
point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve
CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the access point
sends discovery requests to the controllers.
Preparing the Access Point
Before you mount and deploy your access point, we recommend that you perform a site survey (or use the site planning tool) to
determine the best location to install your access point.
You should have the following information about your wireless network available:
•Access point locations
•Access point mounting options (Wall and Junction Box mounting only)
•Access point power options: power supplied by the recommended external power supply (with power adapter
AIR-PWR-C=), a DC power supply, PoE from a network device (802.3af/at), or a PoE power injector/hub (the
Cisco-recommended injector is the AIR-PWRINJ4=), usually located in a wiring closet.
Note PoE-Out is available via LAN port 4
Cisco recommends that you make a site map showing access point locations so that you can record the device MAC addresses
from each location and return them to the person who is planning or managing your wireless network.
Table 1 Access Point Power Sources and PoE-Out Levels
Power Input Source Maximum PoE-Out Power
802.3af / AIR-PWRINJ5 No power available for the PoE-out port
802.3at/AIR-PWRINJ4 Class 2, 6.49W (7W with cable losses)
AIR-PWR-C Class 0, 12.95W (15.4W with cable losses)

11
Installation Summary
Installing the access point involves these operations:
•Performing a pre-installation configuration (optional)
•Mounting the access point
•Deploying the access point on the wireless network
Performing a Pre-Installation Configuration
The following procedures ensure that your access point installation and initial operation go as expected. A pre-installation
configuration is also known as priming the access point. This procedure is optional.
Note Performing a pre-installation configuration is an optional procedure. If your network controller is properly configured,
you can install your access point in its final location and connect it to the network from there. See the “Deploying the
Access Point on the Wireless Network” section on page 15 for details.
Pre-Installation Configuration Setup
The pre-installation configuration setup is shown in Figure 6.
Figure 6 Pre-Installation Configuration Setup
To perform pre-installation configuration, perform the following steps:
Step 1 Make sure that the Cisco wireless LAN controller DS port is connected to the network. Use the CLI, web-browser
interface, or Cisco Prime Infrastructure procedures as described in the appropriate Cisco wireless LAN controller guide.
a. Make sure that access points have Layer 3 connectivity to the Cisco wireless LAN controller Management.
b. Configure the switch to which your access point is attach to. See the Cisco Unified Wireless Network WLAN Controller
Configuration Guide for additional information.
c. Set the Cisco wireless LAN controller as the master so that new access points always join with it.
Controller
Layer 3
devices
Cisco Aironet
access points
272488

12
d. Make sure DHCP is enabled on the network. The access point must receive its IP address through DHCP.
e. CAPWAP UDP ports ( ports 5246 and 5247) must not be blocked in the network.
f. The access point must be able to find the IP address of the controller. This can be accomplished using DHCP, DNS, or
IP subnet broadcast. This guide describes the DHCP method to convey the controller IP address. For other methods,
refer to the product documentation. See also the “Using DHCP Option 43” section on page 16 for more information.
Step 2 Apply power to the access point:
a. The access point is 802.3af (15.4 W) compliant and can be powered by any 802.3af compliant device. However, with
an 802.3af PSE (Power Source Equipment) there will not be any power available for the PoE out port on the AP.
The access point is also 802.3at (34.2 W) complaint (see Table 1).
Note The 700W series access point requires a Gigabit Ethernet link to prevent the Ethernet port from becoming a
bottleneck for traffic because wireless traffic speeds exceed transmit speeds of a 10/100 Ethernet port.
b. As the access point attempts to connect to the controller, the LEDs cycle through a green, red, and amber sequence, which
can take up to 5 minutes.
Note When the access point has joined a controller, then all the LEDs - the AP's LED and the Ethernet port LEDs - will be
turned off. Using the controller's CLI commands you can turn the LEDs on, if necessary.
Note If the access point remains in this mode for more than five minutes, the access point is unable to find the Master
Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN
controller and be sure that they are on the same subnet.
c. If the access point shuts down, check the power source.
d. After the access point finds the Cisco wireless LAN controller, it attempts to download the new operating system code
if the access point code version differs from the Cisco wireless LAN controller code version. While this is happening, the
Status LED blinks amber.
e. If the operating system download is successful, the access point reboots.
Step 3 Configure the access point if required. Use the controller CLI, controller GUI, or Cisco Prime Infrastructure to
customize the access-point-specific 802.11n network settings.
Step 4 If the pre-installation configuration is successful, the Status LED is green indicating normal operation. Disconnect the
access point and mount it at the location at which you intend to deploy it on the wireless network.
Step 5 If your access point does not indicate normal operation, turn it off and repeat the pre-installation configuration.
Note When you are installing a Layer 3 access point on a different subnet than the Cisco wireless LAN controller,
be sure that a DHCP server is reachable from the subnet on which you will be installing the access point, and
that the subnet has a route back to the Cisco wireless LAN controller. Also be sure that the route back to the
Cisco wireless LAN controller has destination UDP ports 5246 and 5247 open for CAPWAP communications.
Ensure that the route back to the primary, secondary, and tertiary wireless LAN controller allows IP packet
fragments. Finally, be sure that if address translation is used, that the access point and the Cisco wireless LAN
controller have a static 1-to-1 NAT to an outside address.

13
8 Mounting the Access Point
Cisco Aironet 700W series access points can be mounted on walls and junction boxes, in the vertical orientation with the
security screw on the top and the LED indicator at the bottom.
Step 1 If you are mounting the AP directly to a junction box, go to Step 3.
For wall mounting, use the mounting bracket as a template to mark the locations of the mounting holes on the bracket.
Figure 7 shows the dimensions of the mounting bracket.
Caution To ensure a safe and secure installation, make sure you are using adequate screws and mount the access point using
no less than two screws.
Figure 7 Mounting Bracket Dimensions
352465

14
Step 2 For wall mounting, drill pilot holes at the mounting hole locations you have marked, and use appropriate anchors as
required.
Note The pilot hole size varies according to the material, and its thickness, you are fastening. Cisco recommends that you
test the material to determine the ideal hole size for your mounting application.
Step 3 Feed the cable(s) from the junction box / wall through the large center cable access hole in the bracket, with the words
“MOUNT ARROWS UP” facing you as shown in Figure 8.
Figure 8 Bracket Mounting Direction
Step 4 Position the mounting bracket mounting holes (with the words “MOUNT ARROWS UP” facing you) over the screw
holes.
Step 5 Insert a screw into each mounting hole and tighten.
Note Screws supplied in kit may not be appropriate for all mounting options.
1Security Screw Hole on Wall Mounting Bracket 2Kensington Lock Slot on Wall Mounting Bracket
1
352508
2

15
Note Make sure all cables are clear and the bracket sits flush against the wall / junction box. The joint created with the screws
must have a minimum pullout force of 20 lbs (9 kg).
Step 6 Connect the Ethernet cable and the power cable (optional) to the access point.
Step 7 With the access point’s LED facing down and the rear metal side of the access point facing the bracket, gently slide the
access point downwards onto the bracket, until it bottoms out on the bracket, and the center tab is engaged. If properly
done, the Kensington lock slots on the AP and the mounting bracket will be aligned.
Step 8 Insert the included security screw (see Figure 2) into the hole on the top of the access point and tighten it till the screw
head is flush with the access point's body.
Step 9 Fix the security screw label over the screw head to cover it completely.
Step 10 If required, use Kensington slot on the side to secure the access point
9 Deploying the Access Point on the Wireless Network
After you have mounted the access point, follow these steps to deploy it on the wireless network:
Step 1 Connect and power up the access point.
Step 2 Observe the access point LED (for LED descriptions, see “Checking the Access Point LED” section on page 16).
a. When you power up the access point, it begins a power-up sequence that you can verify by observing the access point
LED. If the power-up sequence is successful, the discovery and join process begins. During this process, the LED blinks
sequentially green, red, and amber. When the access point has joined a controller, the all the LEDs – the AP’s LED and
the Ethernet port LEDs – will be turned off. Using the controller’s CLI commands you can turn the LEDs on, if necessary.
b. If the LED blinks sequentially for more than 5 minutes, the access point is unable to find its primary, secondary, and
tertiary Cisco wireless LAN controller. Check the connection between the access point and the Cisco wireless LAN
controller, and be sure the access point and the Cisco wireless LAN controller are either on the same subnet or that the
access point has a route back to its primary, secondary, and tertiary Cisco wireless LAN controller. Also, if the access
point is not on the same subnet as the Cisco wireless LAN controller, be sure that there is a properly configured DHCP
server on the same subnet as the access point. See the “Configuring DHCP Option 43 and DHCP Option 60” section
on page 29 for additional information.
Step 3 Reconfigure the Cisco wireless LAN controller so that it is not the Master.
Note A Master Cisco wireless LAN controller should be used only for configuring access points and not in a working
network.

16
10 Troubleshooting
If you experience difficulty getting your access point installed and running, look for a solution to your problem in this guide or
in additional access point documentation. These, and other documents, are available on Cisco.com.
Guidelines for Using Cisco Aironet Lightweight Access Points
Keep these guidelines in mind when you use 700W series lightweight access points:
•The access point can only communicate with Cisco wireless LAN controllers, such as 2500 series, 5500 series, 7500 series,
8500 series, virtual Wireless LAN Controllers, and WiSM2 controllers.
•The access point does not support Wireless Domain Services (WDS) and cannot communicate with WDS devices. However,
the controller provides functionality equivalent to WDS when the access point joins it.
•CAPWAP does not support Layer 2. The access point must get an IP address and discover the controller using Layer 3,
DHCP, DNS, or IP subnet broadcast.
•The access point console port is enabled for monitoring and debug purposes. All configuration commands are disabled when
the access point is connected to a controller.
Using DHCP Option 43
You can use DHCP Option 43 to provide a list of controller IP addresses to the access points, enabling them to find and join a
controller. For additional information, refer to the “Configuring DHCP Option 43 and DHCP Option 60” section on page 29.
Checking the Access Point LED
The location of the access point status LED is shown in Figure 3.
Note When the access point has joined a controller, then all the LEDs - the AP's LED and the Ethernet port LEDs - will be
turned off. Using the controller's CLI commands you can turn the LEDs on, if necessary.
Note Regarding LED status colors, it is expected that there will be small variations in color intensity and hue from unit to
unit. This is within the normal range of the LED manufacturer’s specifications and is not a defect.
The access point status LED indicates various conditions and are described in Table 2.
Table 2 LED Status Indications
Message
Type
Status
LED
Message
Meaning
Boot loader status
sequence
Blinking green DRAM memory test in progress
DRAM memory test OK
Board initialization in progress
Initializing FLASH file system
FLASH memory test OK
Initializing Ethernet
Ethernet OK
Starting Cisco IOS
Initialization successful

17
Troubleshooting the Access Point Join Process
Access points can fail to join a controller for many reasons: a RADIUS authorization is pending; self-signed certificates are not
enabled on the controller; the access point’s and controller’s regulatory domains don’t match, and so on.
Controller software enables you to configure the access points to send all CAPWAP-related errors to a syslog server. You do not
need to enable any debug commands on the controller because all of the CAPWAP error messages can be viewed from the syslog
server itself.
The state of the access point is not maintained on the controller until it receives a CAPWAP join request from the access point.
Therefore, it can be difficult to determine why the CAPWAP discovery request from a certain access point was rejected. In order
to troubleshoot such joining problems without enabling CAPWAP debug commands on the controller, the controller collects
information for all access points that send a discovery message to it and maintains information for any access points that have
successfully joined it.
The controller collects all join-related information for each access point that sends a CAPWAP discovery request to the
controller. Collection begins with the first discovery message received from the access point and ends with the last configuration
payload sent from the controller to the access point.
Association status Chirping Green Normal operating condition, but no wireless
client associated
Green Normal operating condition, at least one wireless
client association
Operating status Blinking amber Software upgrade in progress
Cycling through green,
red, and amber
Discovery/join process in progress
Rapidly cycling
through red, green, and
amber
Access point location command invoked
Blinking red Ethernet link not operational
Boot loader warnings Blinking amber Configuration recovery in progress (MODE
button pushed for 2 to 3 seconds)
Red Ethernet failure or image recovery (MODE
button pushed for 20 to 30 seconds)
Blinking green Image recovery in progress (MODE button
released)
Boot loader errors Red DRAM memory test failure
Blinking red and amber FLASH file system failure
Blinking red and off Environment variable failure
Bad MAC address
Ethernet failure during image recovery
Boot environment failure
No Cisco image file
Boot failure
Cisco IOS errors Red Software failure; try disconnecting and
reconnecting unit power
Cycling through red,
green, amber, and off
General warning; insufficient inline power
Table 2 LED Status Indications (continued)
Message
Type
Status
LED
Message
Meaning

18
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the following conditions are
met:
•An access point running software release 5.2 or later has been newly deployed.
•An existing access point running software release 5.2 or later has been reset after clearing the configuration.
If any of these conditions are met and the access point has not yet joined a controller, you can also configure a DHCP server to
return a syslog server IP address to the access point using option 7 on the server. The access point then starts sending all syslog
messages to this IP address.
When the access point joins a controller for the first time, the controller sends the global syslog server IP address (the default is
255.255.255.255) to the access point. After that, the access point sends all syslog messages to this IP address until it is
overridden by one of the following scenarios:
•The access point is still connected to the same controller, and the global syslog server IP address configuration on the
controller has been changed using the config ap syslog host global syslog_server_IP_address command. In this case, the
controller sends the new global syslog server IP address to the access point.
•The access point is still connected to the same controller, and a specific syslog server IP address has been configured for the
access point on the controller using the config ap syslog host specific Cisco_AP syslog_server_IP_address command. In this
case, the controller sends the new specific syslog server IP address to the access point.
•The access point is disconnected from the controller and joins another controller. In this case, the new controller sends its
global syslog server IP address to the access point.
•Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address is erased from
persistent storage, and the new address is stored in its place. The access point also starts sending all syslog messages to the
new IP address provided the access point can reach the syslog server IP address.
You can configure the syslog server for access points and view the access point join information only from the controller CLI.
A detailed explanation of the join process is on Cisco.com at the following URL:
http://www.Cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml
11 Access Point Specifications Data Sheet
You can access the full data sheet of the Cisco Aironet 700W Series Access Point at the following URL:
https://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps12968/data_sheet_c78-728968.html

19
12 Declarations of Conformity and Regulatory Information
This section provides declarations of conformity and regulatory information for Cisco Aironet 700W Series Access Points. You
can find additional information at this URL:
www.cisco.com/go/aironet/compliance
Manufacturers Federal Communication Commission Declaration of Conformity
Statement
Manufacturer:
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
This device complies with Part 15 rules. Operation is subject to the following two conditions:
1. This device may not cause harmful interference, and
2. This device must accept any interference received, including interference that may cause undesired operation.
This device operates in the 5150-5250MHz and 5470-5725MHz bands and is therefore restricted to indoor operation only per
FCC guidance.
This equipment has been tested and found to comply with the limits of a Class B digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a residential environment. This equipment generates, uses, and radiates radio frequency energy, and if not installed and used
in accordance with the instructions, may cause harmful interference. However, there is no guarantee that interference will not
occur. If this equipment does cause interference to radio or television reception, which can be determined by turning the
equipment off and on, the user is encouraged to correct the interference by one of the following measures:
•Reorient or relocate the receiving antenna.
•Increase separation between the equipment and receiver.
•Connect the equipment to an outlet on a circuit different from which the receiver is connected.
•Consult the dealer or an experienced radio/TV technician.
Caution The Part 15 radio device operates on a non-interference basis with other devices operating at this frequency when
using the integrated antennas. Any changes or modification to the product not expressly approved by Cisco could
void the user’s authority to operate this device.
Models Certification Numbers
AIR-CAP702W-A-K9 LDK102092

20
Caution Within the 5.15 to 5.25 GHz and 5.47-5.725 GHz bands, this device is restricted to indoor operations to reduce
any potential for harmful interference to co-channel Mobile Satellite System (MSS) operations.
VCCI Statement for Japan
Guidelines for Operating Cisco Aironet Access Points in Japan
This section provides guidelines for avoiding interference when operating Cisco Aironet access points in Japan. These guidelines
are provided in both Japanese and English.
Japanese Translation
Warning
This is a Class B product based on the standard of the Voluntary Control
Council for Interference from Information Technology Equipment (VCCI). If this
is used near a radio or television receiver in a domestic environment, it may
cause radio interference. Install and use the equipment according to the
instruction manual.
03-6434-6500
208697