Cisco Troubleshooting Connectivity in a Wireless LAN Netw

Cisco Troubleshooting Connectivity in a Wireless LAN Network

Table of Contents
Troubleshooting Connectivity in a Wireless LAN Network...........................................................................1 To get Cisco Aironet drivers, firmware and utility software, follow this link to the Cisco Wireless Software Center......................................................................................................................................1 Introduction..........................................................................................................................................................1 Before You Begin................................................................................................................................................1 Conventions............................................................................................................................................2 Prerequisites............................................................................................................................................2 Components Used...................................................................................................................................2 Basic Connectivity Issues....................................................................................................................................2 Console Connection................................................................................................................................2 IP Address Assignment...........................................................................................................................2 Cable.......................................................................................................................................................2 Radio Interference ...................................................................................................................................3 Client Adapter......................................................................................................................................................5 Resource Conflict...................................................................................................................................5 . Indicator LEDs........................................................................................................................................5 Verify Client Communications...............................................................................................................6 Access Points.......................................................................................................................................................7 Root Mode..............................................................................................................................................7 Indicator LEDs........................................................................................................................................7 SSID........................................................................................................................................................8 WEP Keys...............................................................................................................................................8 Reset.......................................................................................................................................................9 . Bridge...................................................................................................................................................................9 Indicator LEDs........................................................................................................................................9 SSID......................................................................................................................................................10 WEP Keys.............................................................................................................................................10 Line of Sight and Fresnel Zone .............................................................................................................10 Spanning Tree Protocol........................................................................................................................11 . Related Information...........................................................................................................................................11

Troubleshooting Connectivity in a Wireless LAN Network

To get Cisco Aironet drivers, firmware and utility software, follow this link to the Cisco Wireless Software Center.
Introduction Before You Begin Conventions Prerequisites Components Used Basic Connectivity Issues Console Connection IP Address Assignment Cable Radio Interference Client Adapter Resource Conflict Indicator LEDs Verify Client Communications Access Points Root Mode Indicator LEDs SSID WEP Keys Reset Bridge Indicator LEDs SSID WEP Keys Line of Sight and Fresnel Zone Spanning Tree Protocol Related Information

Introduction
This document provides information to help identify and troubleshoot common connectivity problems in areas such as configuration, interference, and cable in a wireless network. Note: Cisco Aironet equipment operates best when all components are loaded with the most current version of the software. Upgrading to the latest versions of the software is advisable early in the troubleshooting process. You can download the latest software and drivers at the Cisco Software Center.

Before You Begin

Cisco Troubleshooting Connectivity in a Wireless LAN Network

Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites
There are no specific prerequisites for this document.

Components Used
This document is not restricted to specific software and hardware versions. The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.

Basic Connectivity Issues

Console Connection
Use a straightthrough DB9 male/female cable for console connection. In a terminal program like HyperTerminal, set the session to: 9600 baud 8 data bits no parity 1 stop bit Xon/Xoff flow control

IP Address Assignment
If you cannot ping the Access Point (AP) or the bridge, check the IP addresses assigned to the AP, bridge, and client adapter. They should be in the same subnet. For example, if the AP's IP address is 10.12.60.5 with a mask of 255.255.255.0, then the client adapter's IP address should be similar to 10.12.60.X with mask of 255.255.255.0. Remember that the AP and the bridge are Layer 2 devices. If you need two or more networks, a router should be on the network. For more help on IP address and the design of subnets, refer to the IP subnet calculation and design tool.

Cable
If you have intermittent connectivity or connectivity with errors, the cable length may be greater than the recommended Ethernet segment length. Do not exceed the Ethernet cable length recommended in the table below: Cable Type Coax 10 Base 2 Cat 5 10 Base T Length 185 meters / 607 feet 100 meters / 328 feet

Cisco Troubleshooting Connectivity in a Wireless LAN Network

If the distance from the switch exceeds the recommended segment length, consider using a fiber or a wireless hop, such as a repeater. Interference occurs when network cables are run near high power equipment. This is especially common when the cables run in warehouses and factories. When interference occurs because of cable length, and a cable tester shows a positive result, remember that you should use the cable tester only to find a break in the cable. To verify the presence of a cable problem, test the connection to the AP or bridge with a shorter cable and see if the problem is still there.

Radio Interference
A site survey is necessary to install a wireless network and should be done on the actual site under normal operating conditions with all inventory present. Such a survey is critical because the radio frequency (RF) behavior varies with the physical properties of the site and cannot be predicted accurately without doing a site survey. If you are facing intermittent connectivity at certain areas and during certain environmental conditionsfor instance, when a wooden roof is wet after a rainthen perhaps a site survey was not done or a bad site survey did not consider these factors. If a client adapter on a PC with the Aironet Client Utility (ACU) is used to check the signal strength, run the Site Survey option in ACU at the point of interest. Remember that construction materials such as steel and wood absorb RF energy, as do objects with water content. Consider interference from devices such as microwave ovens and cordless phones when you place the APs. An example of the signal strength test is shown below:

Cisco Troubleshooting Connectivity in a Wireless LAN Network

It's also a good idea to perform the carrier test to see activity in the RF spectrum. The carrier test is available on bridges and enables you to view the radio spectrum. The carrier test on the BR500 is shown below:

The numbers 12, 17, and so on represent the 11 frequencies that the bridge uses. For example, 12 represents the frequency 2412 MHz. The astericks (*) indicate the activity on each frequency. Whenever possible, choose the frequency with the least activity to reduce chances of interference. Cisco Troubleshooting Connectivity in a Wireless LAN Network

Client Adapter
Resource Conflict
If the Client Adapter card does not communicate, see if any resource conflict exists with other devices. The card should set at Interrupt Levels (IRQ) not used by other devices. Windows 95, 98, ME, and 2000 are "plug and play," so no resource conflicts should exist. If conflict does exist, deselect the Use Automatic Settings box in the Properties display within the Windows Device Manager, then enter the IRQ and I/O address manually. If there is a resource conflict, Windows NT must be set manually, as explained below. You may also want to disable the IR Port using Windows Device Manager. To identify the free resource in Windows NT, follow these steps: 1. From the Start menu, select Programs > Administrative Tools (Common) > Windows NT Diagnostics. 2. From the Windows NT Diagnostics window select, the Resources tab. 3. From the Resources window, note the IRQ column and check which IRQ numbers are not listed. 4. From the Resources window, click I/O Port. 5. From the Resource window, note the Address column and make note of several different open addresses. The card needs 64 contiguous I/O addresses. Example: 0100 through 013f hexadecimal. To set the correct values in Windows NT, follow these steps: 1. From the Start menu, select Settings > Control Panel. 2. From the Control Panel window, doubleclick the Network icon. 3. From the Network window, select the Adapters tab. 4. From the Adapters Panel, select the Aironet Adapter. 5. Click Properties. 6. In the Adapter Setup window, select Interrupt in the Property column panel. In the Value column, select an IRQ value that is not listed in the Resources tab of the Windows NT Diagnostics window. 7. In the Adapter Setup window, select the I/O Base Address in the Property column panel. In the Value column, select an I/O address not listed in the Resources window of the Windows NT Diagnostics Window. 8. Click OK in the Adapter Setup window and again in the Network window. Close all open windows and do an orderly shutdown of Windows. If the client adapter still shows errors, try another I/O address. Windows NT 4.0 does not always do a reasonable job of reporting used resources and might say that a resource is available when it is not.

Indicator LEDs
Check the status of the Cisco Aironet 340 series client adapter LED to see if it matches the device configuration. The client adapter shows messages and error conditions through two LEDs: Link Integrity/Power LED (green) This LED lights when the client adapter is receiving power and blinks slowly when the adapter is linked with the network. Cisco Troubleshooting Connectivity in a Wireless LAN Network

 Link Activity LED (amber) This LED blinks when the client adapter is receiving or transmitting data and blinks quickly to indicate an error condition. Refer to the table below to determine the condition that a specific LED message indicates. Green LED Amber LED Off Condition Client adapter is not receiving power or an error has occurred. Power is on, selftest is OK, and client adapter is scanning for a network. Client adapter is associated to an AP. Client adapter is transmitting or receiving data while associated to an AP. Client adapter is in power save mode. Client adapter is in ad hoc mode.

Off

Blinking quickly

Blinking quickly Blinking quickly

Blinking slowly Continuously on or blinking slowly Off On Off Off

Blinking Blinking quickly Blinking quickly

On Driver installed incorrectly. Blinking in Indicates an error condition. a pattern

Verify Client Communications

Use the following methods to verify that the card is communicating with the AP: Check the AP Association table through the console screen. Use the ACU diagnostic and configuration utility to verify that the card is associated with AP.

Cisco Troubleshooting Connectivity in a Wireless LAN Network

If the Card is associating to an AP but is not talking to the network, check the Ethernet side and see if the AP is talking properly to the LAN. Use the ping option in the AP to ping the device on the LAN. Note: The problem could be an outdated driver. Refer to Upgrading the Cisco Aironet 340 Series Access Point Firmware from the Console for more information.

Access Points
Root Mode
Check the root mode to see if it is set appropriately on the AP. An AP configured as a root device: Accepts association and communicates only with clients and repeaters. Does not communicate with other root devices. Can be one of many root devices per RF system. An AP configured as a nonroot or repeater device: Associates and communicates to a root or another nonroot associated to a root. Accepts association and communicates only with clients and repeaters, as long as it is registered to a root.

Indicator LEDs
The indicator lights of Aironet 340 series AP have the following meanings: The Ethernet indicator signals traffic on the wired LAN or Ethernet infrastructure. This indicator blinks green when a packet is received or transmitted over the Ethernet infrastructure. The status indicator signals operational status. Blinking green indicates that the AP is operating normally but is not associated with any wireless devices. Steady green indicates that the AP is associated with a wireless client. When repeater APs blink 50% on and 50% off, this indicates that the repeater is not associated with the root AP. When the repeater APs blink 7/8 on and 1/8 off, this indicates that the repeater is associated with the root AP but that no client devices are associated with the repeater. When the repeater AP blinks green steadily, this indicates that the repeater is associated with the root AP and that client devices are associated with the repeater. The radio indicator blinks green to indicate radio traffic activity. The light is normally off, but it blinks green whenever a packet is received or transmitted over the AP's radio. Refer to the table below to determine the condition that a specific LED message indicates. Message type Radio Status Infrastructure indicator indicator indicator Steady green Meaning At least one wireless client device is associated with the unit

Association status

Cisco Troubleshooting Connectivity in a Wireless LAN Network

Blinking green Blinking green Steady green Steady green Blinking amber Steady green Error/warning Steady green Blinking amber Blinking red Blinking amber Failure Steady red Steady red Blinking green No client devices are associated; check the unit's SSID and WEP settings Transmitting/receiving packets over Ethernet Maximum retries or buffer full occurred on the radio Transmit/receive errors Ethernet cable is disconnected General warning Firmware failure; disconnect power from the unit and reapply power Unit is loading new firmware

Operational

Steady red

Firmware upgrade

Steady red

SSID
Wireless clients that attempt to associate with the AP must use the same SSID as the AP. The default SSID is tsunami. Allow "Broadcast" SSID to Associate? This setting allows you to choose whether devices that do not specify a SSID (devices that are "broadcasting" in search of an AP to associate with) are allowed to associate with the AP. Yes This is the default setting. It allows devices that do not specify an SSID to associate with the AP. No Devices that do not specify an SSID are not allowed to associate with the AP. The SSID used by the client device must match that of the AP. If you have communication problem and the device it is set to "No", change the setting to "Yes" to see if the device can communicate. Leave the setting as "Yes" for the duration of troubleshooting.

WEP Keys
The Wired Equivalent Privacy (WEP) key you use to transmit data must be set up exactly the same on your AP and on any wireless devices with which it associates.

Cisco Troubleshooting Connectivity in a Wireless LAN Network

For example, if you set WEP Key 3 on your wireless LAN adapter to 0987654321 and select it as the transmit key, you must also set WEP Key 3 on the AP to the same value. However, the AP does not need to use Key 3 as its transmit key. Check the WEP Key. Here are some points to remember about WEP keys. Open Authorization allows authorization and associations with or without a WEP key. If a WEP key is used, both the client and the AP must have matching WEP keys. If one or the other does not have a matching WEP key, data traffic cannot be passed because the data is encrypted. Do not use the WEP key to see if the problem persists. Leave the WEP key inactive until the connectivity problem is identified.

Reset
Sometimes the problem with misconfigured SSIDs or WEP keys is difficult to identify. For example, the WEP key could have one digit mistyped. To overcome such problems, note the configurations and reenter them after a reset.

Bridge
There can only be one bridge with the Root ON in a RF network; all other bridges should be set to Root OFF.

Indicator LEDs
The indicator lights of an Aironet 340 series bridge have the following meanings: The Ethernet indicator signals traffic on the wired LAN or Ethernet infrastructure. This indicator blinks green when a packet is received or transmitted over the Ethernet infrastructure. The status indicator signals operational status. Blinking green indicates that the bridge is operating normally, but is not communicating with an AP. Steady green indicates that the bridge is communicating with an AP. The radio indicator blinks green to indicate radio traffic activity. The light is normally off, but it blinks green whenever a packet is received or transmitted over the bridge's radio. Refer to the table below to determine the condition that a specific LED message indicates. Message type Radio Status Infrastructure indicator indicator indicator Steady green Blinking green Blinking green Steady green Meaning Linked to the wireless LAN Not linked to the wireless LAN; check the unit's SSID and WEP settings Transmitting/receiving radio packets

Association status

Cisco Troubleshooting Connectivity in a Wireless LAN Network Operational

Steady green

Blinking green

Transmitting/receiving packets Maximum retries or buffer full occurred on the radio. The AP that the bridge is communicating with might be overloaded, or radio reception may be poor. Try changing the bridge's SSID to communicate with another AP, or reposition the bridge to improve connectivity.

Blinking amber Steady green

Error/warning

Steady green

Blinking amber Blinking red

Transmit/receive errors Ethernet cable is disconnected General warning Firmware failure; disconnect power from the unit and reapply power Unit is loading new firmware

Blinking amber Failure Steady red Steady red

Steady red

Firmware upgrade

Steady red

SSID
The bridge's SSID must match the SSID of a Cisco Aironet AP on your wireless LAN. The AP must be within radio range of the bridge.

WEP Keys
The WEP key you use to transmit data must be set up exactly the same on your AP and on your bridge. For example, if you set WEP Key 3 on your bridge to 0987654321 and select it as the transmit key, you must also set WEP Key 3 on the AP to exactly the same value.

Line of Sight and Fresnel Zone

For longdistance communications, consider the Fresnel zone in addition to Line of Sight (LOS). The Fresnel zone is an elliptical area immediately surrounding the visual path. This area varies depending on the length of the signal path and the frequency of the signal. Take into account the Fresnel zone calculating property when you are designing a wireless link. The Fresnel effect is overcome by raising the antenna height. The distance calculation spreadsheet gives the height of the antenna for the given radio distance and with no obstruction. Cisco Troubleshooting Connectivity in a Wireless LAN Network

The maximum radio distance for a given antenna and cable length can be calculated using the antenna calculation spreadsheet (in Microsoft Excel format).

Spanning Tree Protocol

See if the bridge is blocked by Spanning Tree Protocol (STP). There might be a leased line or an alternate path between the points bridged by the RF network. STP might put one of the links in the blocking mode to avoid loops.

Related Information
Cisco Software Center for Wireless Products Cisco Aironet Access Point Software Configuration Guide Cisco Aironet 340 and 350 Series Wireless LAN Support Page Wireless LAN Support Page Technical Support Cisco Systems

All contents are Copyright 19922003 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Cisco Troubleshooting Connectivity in a Wireless LAN Network