Troubleshooting

This chapter provides troubleshooting procedures for basic problems with the access point. For the most up-to-date, detailed troubleshooting information, refer to the Cisco Technical Support and Documentation website at the following URL:

http://www.cisco.com/cisco/web/support/index.html

Sections in this chapter include:

Guidelines for Using the Access Points

You should keep these guidelines in mind when you use the access points:

  • The access point only supports Layer 3 CAPWAP communications with the controllers.

In Layer 3 operation, the access point and the controller can be on the same or different subnets. The access point communicates with the controller using standard IP packets. A Layer 3 access point on a different subnet than the controller requires a DHCP server on the access point subnet and a route to the controller. The route to the controller must have destination UDP ports 12222 and 12223 open for CAPWAP communications. The route to the primary, secondary, and tertiary controllers must allow IP packet fragments.

  • Before deploying your access points, ensure that the following has been done:

–blank.gif Your controllers are connected to switch ports that are configured as trunk ports.

–blank.gif Your access points are connected to switch ports that are configured as untagged access ports.

–blank.gif A DHCP server is reachable by your access points and has been configured with Option 43. Option 43 provides the IP addresses of the management interfaces of your controllers. Typically, a DHCP server can be configured on a Cisco switch.

–blank.gif Optionally, a DNS server can be configured to enable CISCO-CAPWAP-CONTROLLER. Use local domain to resolve to the IP address of the management interface of your controller.

–blank.gif Your controllers are configured and reachable by the access points.

–blank.gif Your controllers are configured with the access point MAC addresses and the MAC filter list is enabled.

–blank.gif Your switch must forward DHCP requests.

  • After the access points are associated to the controller, you should change the bridge group name (BGN) from the default value. With the default BGN, the mesh access points (MAPs) can potentially try to connect with other mesh networks and slow down the convergence of the network.

Important Notes

Convergence Delays

During deployment, the access points can experience convergence delays due to various causes. The following list identifies some operating conditions that can cause convergence delays:

  • A root access point (RAP) attempts to connect to a controller using any of the wired ports (cable, fiber-optic, PoE-in). If the wired ports are operational, the RAP can potentially spend several minutes on each port prior to connecting to a controller.
  • If a RAP is unable to connect to a controller over the wired ports, it attempts to connect using the wireless network. This results in additional delays when multiple potential wireless paths are available.
  • If a MAP is unable to connect to a RAP using a wireless connection, it then attempts to connect using any available wired port. The access point can potentially spend several minutes for each connection method, before attempting the wireless network again.

Bridge Loop

The access point supports packet bridging between wired and wireless network connections. The same network must never be connected to multiple wired ports on an access point or on two bridged access points. A bridge loop causes network routing problems.

Controller DHCP Server

The controller DHCP server only assigns IP addresses to lightweight access points and wireless clients associated to an access point. It does not assign an IP address to other devices, including Ethernet bridging clients on the mesh access points.

MAP Data Traffic

If the signal on the access point backhaul channel has a high signal-to-noise ratio, it is possible for a MAP to connect to the controller, via parent node, but not be able to pass data traffic, such as pinging the access point. This can occur because the default data rate for backhaul control packets is set to 6 Mb/s, and the backhaul data rate set to auto by the user.

Controller MAC Filter List

Before activating your access point, you must ensure that the access point MAC address has been added to the controller MAC filter list and that Mac Filter List is enabled.

note.gif

Noteblank.gif The access point MAC address and barcode is located on the bottom of the unit. When two MAC addresses are shown, use the top MAC address.

To view the MAC addresses added to the controller MAC filter list, you can use the controller CLI or the controller GUI:

  • Controller CLI—Use the show macfilter summary controller CLI command to view the MAC addresses added to the controller filter list.
  • Controller GUI—Log into your controller web interface using a web browser, and choose SECURITY > AAA > MAC Filtering to view the MAC addresses added to the controller filter list.

Using DHCP Option 43

You can use DHCP Option 43 to provide a list of controller IP addresses to the access points, enabling the access point to find and join a controller. Refer to the product documentation for your DHCP server for instructions on configuring DHCP Option 43. For additional information, refer to the “Configuring DHCP Option 43” section.

Monitoring the Access Point LEDs

If your access point is not working properly, look at the LEDs on the bottom of the unit. You can use them to quickly assess the status of the unit. Figure 3-1 shows the location of the access point LEDs.

Figure 3-1 Access Point LEDs –Shown on the Bottom of AP 1532E

 

347848.eps

 

note.gif

Noteblank.gif It is expected that there will be small variations in LED color intensity and hue from unit to unit. This is within the normal range of the LED manufacturer specifications and is not a defect.

The access point LED signals are listed in Table 3-1 .

Table 3-1 Access Point LED Signals

LED Message Type

Color

Meaning

Boot loader status sequence

Blinking Green

Boot loader status sequence:

  • 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

Boot loader warnings

Blinking Amber

Configuration recovery is in progress (the MODE button has been pushed for 2-3 seconds)

Solid Red

There is an Ethernet failure or an image recovery (the MODE button has been pushed for 20-30 seconds)

Blinking Green

An image recovery is in progress (the MODE button has been released)

Boot loader errors

Solid Red

There has been a DRAM memory test failure

Blinking Red and Amber

There has been a FLASH file system failure

Blinking Red and Off

This sequence may indicate any of the following:

  • Environment variable failure
  • Bad MAC address
  • Ethernet failure during image recovery
  • Boot environment failure
  • No Cisco image file
  • Boot failure

Cisco IOS errors

Solid Red

There has been a software failure; a disconnect then reconnect of the unit power may resolve the issue

Cycling through Red, Green, Amber and Off

This is a general warning of insufficient inline power.

Association status

Chirping (short blips) Green

This status indicates a normal operating condition. The unit is joined to a controller, but no wireless client is associated with it.

Solid Green

Normal operating condition with at least one wireless client associated with the unit

Operating Status

Blinking Amber

A software upgrade is in progress

Cycling through Green, Red and Amber

Discovery/join process is in progress

Rapidly cycling through Red, Green, Amber and Off

This status indicates that the Access Point location command has been invoked.

Blinking Red

This status indicates that an Ethernet link is not operational

Alignment Mode

Color

Signal Level (dBm)

Solid Green

> –44

Fast blinking Green

–47 to –44

Medium blinking Green

–50 to –47

Solid Amber

–53 to –50

Fast blinking Amber

–57 to –53

Medium blinking Amber

–60 to –57

Slow blinking Amber

–63 to –60

Slow blinking Red

–66 to –63

Medium blinking Red

–69 to –66

Fast blinking Red

–72 to –69

Solid Red

–75 to –72

Off

< –75

 

Verifying Controller Association

To verify that your access point is associated to the controller, follow these steps:

Step 1blank.gif Log into your controller web interface using a web browser.

You can also use the controller CLI show ap summary command from the controller console port.

Step 2blank.gif Click Wireless, and verify that your access point MAC address is listed under Ethernet MAC.

Step 3blank.gif Log out of the controller, and close your web browser.

 

Changing the Bridge Group Name

The bridge group name (BGN) controls the association of the access points to a RAP. BGNs can be used to logically group the radios to avoid different networks on the same channel from communicating with each other. This setting is also useful if you have more than one RAP in your network in the same area.

If you have two RAPs in your network in the same area (for more capacity), we recommend that you configure the two RAPs with different BGNs and on different channels.

The BGN is a string of ten characters maximum. A factory-set bridge group name (NULL VALUE) is assigned during manufacturing. It is not visible to you, but allows new access point radios to join a network of new access points. The BGN can be reconfigured from the Controller CLI and GUI. After configuring the BGN, the access point reboots.

After the access points are deployed and associated to the controller, the BGN should be changed from the default value to prevent the MAPs from attempting to associate to other mesh networks.

The BGN should be configured very carefully on a live network. You should always start with the most distant access point (last node) from the RAP and move towards the RAP. If you start configuring the BGN in a different location, then the access points beyond this point (farther away) are dropped, as they have a different BGN.

To configure the BGN for the access points using the controller GUI, follow these steps:

Step 1blank.gif Log into your controller using a web browser.

Step 2blank.gif Click Wireless. When access points associates to the controller, the access point name appears in the AP Name list.

Step 3blank.gif Click on an access point name.

Step 4blank.gif Find the Mesh Information section, and enter the new BGN in the Bridge Group Name field.

Step 5blank.gif Click Apply.

Step 6blank.gif Repeat Steps 2 through 5 for each access point.

Step 7blank.gif Log out from your controller, and close your web browser.

 

Access Point Power Injector

The power injector (AIR-PWRINJ1500-2=) has three LEDs on the front end of the case (see Figure 3-2). For detailed information on the power injector, see the Cisco Aironet 1550 Series Outdoor Access Point Power Injector Installation Instructions.

Figure 3-2 Power Injector Connectors and LEDs

 

211484.eps

 

1

Mounting tabs
4

AC POWER LED
2

AP POWER LED
5

TO AP—Ethernet connector (RJ-45) to access point
(10/100/1000BASE-T)
3

FAULT LED
6

TO SWITCH—Ethernet connector (RJ-45) to switch (10/100/1000BASE-T)

Monitoring the Power Injector LEDs

You can use the power injector LEDs to check the power injector status. The LEDs provide the following status information:

  • AP POWER—Turns solid green after successful discovery; indicates that power injector is supplying power to the access point.
  • FAULT—Turns solid red when a fault occurs during discovery mode or power-up. Check Ethernet cables and connections before contacting your support organization for assistance.
  • AC POWER—Turns solid green when power injector is receiving AC power and is ready to provide power to the access point.

Accessing the Console Port and the Reset Button

The access point has a console port and a reset button located on the left side of the enclosure, inside the Console-Reset port, under the hex-shaped sealed plug.

caut.gif
Caution blank.gif Inspect the seal of the plug and properly tighten it every time the plug is removed and replaced. Tighten the plug to 15 lbf-in.

Figure 3-3 Reset Button Location - Models AIR-CAP1552E-x-K9 and AIR-CAP1552EU-x-K9

 

352055.eps

 

1

Console Port
2

Reset Button

Resetting the Access Point

Using the Reset button you can either return the AP back to its default factory-shipped configuration or download the latest software image from the default TFTP servers.

To use the Reset button:

Step 1blank.gif Using a wrench, remove the hex-shaped plug from the Console-Reset port. Do not loose the seal around the plug.

Step 2blank.gif To press and hold the Reset button, use a straightened paperclip or a small screwdriver or a pen.

    • To reset the AP back to its default factory-shipped configuration, during power cycle, press and hold the Reset button (for about 2 to 3 seconds) until the LED blinks amber.
    • To download the software image (ap1g3-k9w7-tar.default) from the default TFTP servers (servers with IP address in the range of 10.0.0.2 to 10.0.0.30), during power cycle, press and hold the Reset button (for about 20 to 30 seconds) until the LED turns red.

Step 3blank.gif Inspect the hex-shaped plug attached to the lanyard for any damage to the sealing face and the gasket. If the gasket has any signs of damage, it should be replaced to avoid water leakage into the unit.

Step 4blank.gif Replace the hex-shaped plug back and tighten it to 15 lbf-in.