Cisco Cisco 2000 Series Wireless LAN Controller Guia De Resolução De Problemas
Troubleshoot a Lightweight Access Point Not
Joining a Wireless LAN Controller
Joining a Wireless LAN Controller
Document ID: 119286
Contents
Introduction
Prerequisites
Requirements
Conventions
Prerequisites
Requirements
Conventions
Overview of the Wireless LAN Controller (WLC) Discovery and Join Process
Debug from the Controller
debug lwapp events enable
debug pm pki enable
Debug from the LAP
Avoiding DHCP Related Issues
Using Syslog Servers to Troubleshoot the LAP Join Process
LAP Does Not Join the Controller, Why?
Check the Basics First
Problem 1: The controller time is outside the certificate validity interval
Problem 2: Mismatch in Regulatory domain
Problem 3: Error Message AP cannot join because the maximum number of APs on interface 2 is reached
Problem 4: With SSC APs, the SSC AP policy is disabled
Problem 5: AP authorization list enabled on the WLC; LAP not in the authorization list
Problem 6: The SSC public key-hash is wrong or missing
Problem 7: There is a certificate or public key corruption on the AP
Problem 8: The controller might be working in Layer 2 mode
Problem 9: You receive this error message on the AP after conversion to LWAPP
Problem 10: Controller receives AP discovery message on wrong VLAN (you see the discovery message
debug, but not response)
Problem 11: 1250 LAP Not Able to Join WLC
Problem 12: AP Not Able to Join the WLC, Firewall Blocking Necessary Ports
Problem 13: Duplicate IP address in the network
Problem 14: LWAPP APs do not join WLC if network MTU is less than 1500 bytes
Problem 15: 1142 series LAP not joining the WLC, Error message on WLC : lwapp_image_proc: unable
to open tar file
Problem 16: 1000 series LAPs not able to join the Wireless LAN controller, WLC runs version 5.0
Problem 17: LAPs with Mesh image not able to join WLC
Problem 18: Error Message - Dropping primary discovery request from AP XX:AA:BB:XX:DD:DD -
maximum APs joined 6/6
Related Information
Debug from the Controller
debug lwapp events enable
debug pm pki enable
Debug from the LAP
Avoiding DHCP Related Issues
Using Syslog Servers to Troubleshoot the LAP Join Process
LAP Does Not Join the Controller, Why?
Check the Basics First
Problem 1: The controller time is outside the certificate validity interval
Problem 2: Mismatch in Regulatory domain
Problem 3: Error Message AP cannot join because the maximum number of APs on interface 2 is reached
Problem 4: With SSC APs, the SSC AP policy is disabled
Problem 5: AP authorization list enabled on the WLC; LAP not in the authorization list
Problem 6: The SSC public key-hash is wrong or missing
Problem 7: There is a certificate or public key corruption on the AP
Problem 8: The controller might be working in Layer 2 mode
Problem 9: You receive this error message on the AP after conversion to LWAPP
Problem 10: Controller receives AP discovery message on wrong VLAN (you see the discovery message
debug, but not response)
Problem 11: 1250 LAP Not Able to Join WLC
Problem 12: AP Not Able to Join the WLC, Firewall Blocking Necessary Ports
Problem 13: Duplicate IP address in the network
Problem 14: LWAPP APs do not join WLC if network MTU is less than 1500 bytes
Problem 15: 1142 series LAP not joining the WLC, Error message on WLC : lwapp_image_proc: unable
to open tar file
Problem 16: 1000 series LAPs not able to join the Wireless LAN controller, WLC runs version 5.0
Problem 17: LAPs with Mesh image not able to join WLC
Problem 18: Error Message - Dropping primary discovery request from AP XX:AA:BB:XX:DD:DD -
maximum APs joined 6/6
Related Information
Introduction
This document gives an overview of the Wireless LAN Controller (WLC) Discovery and Join Process. This
document also provides information on some of the issues why a Lightweight Access Point (LAP) fails to join
a WLC and how to troubleshoot the issues.
document also provides information on some of the issues why a Lightweight Access Point (LAP) fails to join
a WLC and how to troubleshoot the issues.