<div>
Thank you, David.<br />
<br />
I actually stumbled onto my answer about the same time I was reading your response. &nbsp;I did a &quot;debug pm pki enable&quot; and started getting messages about setting the date and time on the controller.<br />
<br />
Needless to say, after I set the date to something more realistic (it was January of 2000), CAPWAP started working.<br />
<br />
This is a demo controller I received from Cisco.
</div>


Thank you, David.

I actually stumbled onto my answer about the same time I was reading your response.  I did a "debug pm pki enable" and started getting messages about setting the date and time on the controller.

Needless to say, after I set the date to something more realistic (it was January of 2000), CAPWAP started working.

This is a demo controller I received from Cisco.

<div>
<div class="content wysiwyg-content">
I have a Cisco WLC 2504 and a few 702W LAPs that I am trying to get configured to work together. &nbsp;I cannot seem to get the LWAPP/CAPWAP discovery to work. &nbsp;I've attached the output I get after issuing a &quot;debug capwap packet enable&quot; command.<br />
<br />
The WLC's management interface and the LAPs are on the same subnet. &nbsp;No firewalls exist between the two devices. &nbsp;I can ping from the WLC to the LAP and vice versa.<br />
<br />
Any ideas what my issue might be?<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/12_w49/886373/DEBUG-CAPWAP-PACKET-ENABLE.txt" target="_blank" class="file-inline" title="debug_capwap_packet_enable.txt (12 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DEBUG-CAPWAP-PACKET-ENABLE.txt</a>
</div>
</div>


DEBUG-CAPWAP-PACKET-ENABLE.txt

I have a Cisco WLC 2504 and a few 702W LAPs that I am trying to get configured to work together.  I cannot seem to get the LWAPP/CAPWAP discovery to work.  I've attached the output I get after issuing a "debug capwap packet enable" command.

The WLC's management interface and the LAPs are on the same subnet.  No firewalls exist between the two devices.  I can ping from the WLC to the LAP and vice versa.

Any ideas what my issue might be?

Cisco LWAPP/CAPWAP Not Working

Wireless networking is a method by which homes, telecommunications networks and enterprise (business) installations avoid the costly process of introducing cables into a building, or as a connection between various equipment locations. Wireless telecommunications networks are generally implemented and administered using radio communication. This implementation takes place at the physical level (layer) of the OSI model network structure. The key hardware components of a wireless computer network include adapters, routers and access points, antennas and repeaters.

Wireless Hardware

Wireless networking is anything related to the transfer of data between two (or more) devices without the use of a physical connection, ranging from getting advice on a new Bluetooth headset to configuring sophisticated enterprise level networks.

Wireless Networking

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.