topic Re: debug capwap console cli not working in Wireless

debug capwap console cli not working

davinci — Mon, 05 Jul 2021 17:15:38 GMT

I'm trying to manually add SNMP config to a WAP. cisco tac recommended debug capwap console cli then conf t and adding the SNMP config but I can't get that far. where do I go from here?

WAP#debug capwap console cli
^
% Invalid input detected at '^' marker.
WAP#debug capwap
client CAPWAP Client debugs
WAP#debug capwap client
avc CAPWAP client AVC
detail CAPWAP detail
efficient-upgrade Smart image download debugging
error CAPWAP error
events CAPWAP events
flexconnect CAPWAP flexconnect mode event
info CAPWAP info
keepalive CAPWAP keepalive
payload CAPWAP payload
pmtu CAPWAP Path MTU debugging
qos CAPWAP qos
reassembly CAPWAP reassembly
security CAPWAP security

WAP#debug capwap client

WAP#show version
Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c) of the Commercial
Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

This product contains some software licensed under the
"GNU General Public License, version 2" provided with
ABSOLUTELY NO WARRANTY under the terms of
"GNU General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

This product contains some software licensed under the
"GNU Library General Public License, version 2" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Library
General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

This product contains some software licensed under the
"GNU Lesser General Public License, version 2.1" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Lesser
General Public License, version 2.1", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html

Cisco AP Software, (ap3g3), [wnbu-bld-lnx8:/san/BUILD/workspace/83MR4_Repost_Cheetah_CCO/label/barbados]
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Mon Jun 4 23:25:52 PDT 2018

ROM: Bootstrap program is U-Boot boot loader
BOOTLDR: U-Boot boot loader Version 2013.01-gad8bd06 (Sep 28 2017 - 17:03:04)

ALDLEG-6-WAP07-6302-D552 uptime is 0 days, 6 hours, 45 minutes
Last reload time : Thu Apr 4 21:09:33 UTC 2019
Last reload reason : unknown

cisco AIR-AP3802I-B-K9 ARMv7 Processor rev 1 (v7l) with 1030640/710480K bytes of memory.
Processor board ID FCW2243NFQP
AP Running Image : 8.3.143.0
Primary Boot Image : 8.3.143.0
Backup Boot Image : 8.2.166.0
1 Multigigabit Ethernet interfaces
1 Gigabit Ethernet interfaces
2 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version :

Base ethernet MAC Address : F4:DB:E6:9D:D5:52
Part Number : 73-018550-02
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC22415XWY
Top Assembly Part Number : 068-100730-02
Top Assembly Serial Number : FCW2243NFQP
Top Revision Number : E0
Product/Model Number : AIR-AP3802I-B-K9

Re: debug capwap console cli not working

patoberli — Tue, 16 Apr 2019 12:20:05 GMT

It's running in CAPWAP mode, so I don't think it's possible to add SNMP configuration on the AP direct. You will have to do that on the WLC, only for the WLC.
What do you actually try to achieve?
Debug capwap is for debugging association event between the AP and the WLC. You actually get most of those events by simply attaching a console cable to the AP and reboot it. The other messages are on the WLC, where you have to enable it by 'debug capwap events' (there are more variations for debug capwap).

Re: debug capwap console cli not working

Rich R — Tue, 16 Apr 2019 14:56:45 GMT

That's a COS (ClickOS) AP (Wave 2 and later). I recall seeing that that command is only valid for the older IOS based APs.
Suggest you go back to TAC.
Like Pat I would also question why you're even trying to configure SNMP on a CAPWAP AP - you should be polling the WLC not the AP - that's the whole purpose of the CAPWAP design. If you want a locally managed AP you may want to consider ME (Mobility Express) where the AP effectively becomes a mini WLC + AP (autonomous IOS is not available for these APs).

Re: debug capwap console cli not working

Scott Fella — Tue, 16 Apr 2019 16:12:53 GMT

Like others mentioned, that command is only valid of the Wave1 and older AP's. SNMP is done from the controller and not individual access points.

Re: debug capwap console cli not working

davinci — Thu, 02 May 2019 15:11:14 GMT

Ok I get the WAPS pull configs from WLC but my WAPs keep losing SNMP config after reboot so clearly they're not retrieving SNMP config from WLC

Re: debug capwap console cli not working

patoberli — Thu, 02 May 2019 15:43:09 GMT

That I don't know. Normally, with a WLC, you only query the WLC with snmp, not the APs. You might want to open a TAC.

Re: debug capwap console cli not working

Rich R — Thu, 02 May 2019 15:46:08 GMT

As we've already explained, you should NOT be SNMP polling CAPWAP APs.
The config you're adding locally is evidently unsupported and therefore gets overwritten every time the WLC updates the config.
The only supported method for using SNMP with CAPWAP APs is to poll the WLC, not the AP.

Re: debug capwap console cli not working

OddievenInc — Tue, 02 Jun 2020 17:16:18 GMT

How to identify whether an AP is COS or not?

Re: debug capwap console cli not working

Rich R — Tue, 02 Jun 2020 20:14:11 GMT

Every model since the Wave 2 APs is COS - eg the 3802 example you gave above:
Cisco AP Software, (ap3g3), [wnbu-bld-lnx8:/san/BUILD/workspace/83MR4_Repost_Cheetah_CCO/label/barbados]
The older APs (eg 3702) run IOS so when you do show ver it will say IOS 🙂

Re: debug capwap console cli not working

Rasika Nayanajith — Tue, 02 Jun 2020 20:49:39 GMT

Yes, all wave2 AP models are based on COS. In summary following series of AP models

1540/1560/1800/2800/3800/4800/9100.

You can check AP is wave2 support from this page

https://www.cisco.com/c/en/us/products/wireless/access-point-controller-selector.html?

Here is another useful FAQ page about Wave2 APs

https://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/802-11ac-solution/q-and-a-c67-734152.html

HTH

Rasika

*** Pls rate all useful responses ***

Re: debug capwap console cli not working

OddievenInc — Wed, 03 Jun 2020 02:24:45 GMT

Thanks for that. Yesterday I converted AP 1702 from autonomous to CAPWAP. @Rasika Your blog post was very helpful indeed : ) However after the conversion the command "debug capwap console cli" isn't recognised. Does that mean I have converted the AP into a COS ? If that's so, does wave 1 and older APs support COS? Sorry for all the questions. I got into Wireless only a year ago, and all these new facts have only made my interest go up. Appreciate your help.

Re: debug capwap console cli not working

Rasika Nayanajith — Wed, 03 Jun 2020 03:45:44 GMT

"However after the conversion the command "debug capwap console cli" isn't recognised."

That command is only intended to use when AP got a lightweight image. Once you converted to Autonomous, it does not require it. You can simply go to configuration mode by "config t" CLI command.

Hope you understand, still 1702 is wave 1 AP and running Cisco IOS image (irrespective of lightweight vs autonomous image in it)

"Sorry for all the questions. I got into Wireless only a year ago, and all these new facts have only made my interest go up. Appreciate your help."

No need to apologies, we all being in that learning curve and understand where you coming from. We are happy to help in this forum as much as we can.

HTH

Rasika