Table Of Contents
Guidelines for Using the Access Points
Misconfigured Bridge Shared Secret Key
Misconfigured MESH Access Point IP address
Verifying Controller Association
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/en/US/products/hw/wireless/tsd_products_support_category_home.html
Sections in this chapter include:
•
Guidelines for Using the Access Points
•
•
•
Guidelines for Using the Access Points
You should keep these guidelines in mind when you use the access points:
•
•
•
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. Layer 3 operation is scalable and is recommended by Cisco. 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 LWAPP communications. The route to the primary, secondary, and tertiary controllers must allow IP packet fragments.
•
–
–
–
–
–
–
Controller MAC Filter List
Prior to activating your access point, you must ensure that the access point MAC address has been added to the controller MAC Filter list. To view the MAC addresses added to the controller MAC filter list, you can use the controller CLI or the controller GUI:
•
•
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 on page G-1.
Misconfigured Bridge Shared Secret Key
If an access point has a misconfigured bridge shared secret key, it is not allowed to join the mesh network. If Enable Zero Touch Configuration is checked on your controller, the access point can obtain the shared secret key from the controller or a neighbor access point.
If Enable Zero Touch Configuration is not checked, you might need to check the feature to allow the access point to get a new bridge shared secret key (refer to the "Enabling Zero Touch Configuration on the Controller" section on page 2-10).
Misconfigured MESH Access Point IP address
IP address misconfiguration can occur when you are re-addressing a segment of your mesh network and your first IP address change is the IP addresses of the RAP connected to the wired network. To avoid this problem, always start the IP addressing changes from the farthest access point and work your way back to the RAP. This problem might also happen if you move equipment; for example, you uninstall an access point and redeploy it in another physical location on the mesh network with a different IP subnet.
Another option to fix this misconfigured IP address is to physically take a controller in L2 mode with a RAP to the location of the misconfigured MAP. Set the bridge group name for the RAP to match the misconfigured MAP. Add the MAP's MAC address to the controller's filter list and check Enable Zero Tough Configuration. When the misconfigured MAP displays on the controller's Summary page, you can properly configure the access point.
Verifying Controller Association
To verify that your access point is associated to the controller, follow these steps:
Step 1
Note
Step 2
Step 3
Access Point Power
The access point does not have an LED to indicate available power.
Caution
To ensure that your access point has power after installation, perform these steps:
Step 1
Step 2
Note
Step 3
Step 4
