C9800 Module 3 Verify The Config Troubleshooting Basics and Tools
C9800 Module 3 Verify The Config Troubleshooting Basics and Tools
C9800 Module 3 Verify The Config Troubleshooting Basics and Tools
Valuable
troubleshooting tools
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3
My APs are not joining !
Did you define a wireless management interface, is it correct and did
you define the proper trustpoint for it?
myc9800-CL#show wireless interface summary
Interface Name Interface Type VLAN ID IP Address IP Netmask NAT-IP Address MAC Address
--------------------------------------------------------------------------------------------------
GigabitEthernet1 Management 0 172.31.46.79 255.255.240.0 52.29.98.144 061a.4aa6.625c
Demo
later on
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6
New config model
Verifying applied configuration – AP CLI
<snip>
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7
New config model
Verifying applied configuration – Web UI
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 8
My clients are acting weird!
The client monitoring page is a good place to check the current state
of clients as well as if client is getting excluded
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9
My clients are acting weird!
The client detail page has more tabs, but take the time to dig to verify
all the ACLs and policies applied to the client to validate they are
what you want
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10
9800 Always-on Logging
• ERROR level represent abnormal situations. We want to raise the user attention to these
• WARNING represent an incident that could potentially lead to an error (or not…)
• NOTICE is the default logging level for binos daemons. It captures significant events if they are
normal working conditions. (client connect, failover)
• INFO contains details about state machines and the communication flow
DEBUG contains traces needed to root cause failure conditions
•
2-Critical
• VERBOSE : 3-Error
4-Warning
5-Notice
6-Info
7-Debug
8-Verbose
• INTERNAL is not a level but a flag on any log line when it is not meant to be understood by mere
mortals but only by developers
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11
9800 Always-on Logging
• This means you can collect logs at notice level for any client or any
AP or any event even after the facts, and for days or weeks !
• You can also activate debugging (called RadioActive tracing) for AP
or client mac to get debug level logs.
• Here’s an example for troubleshooting an AP join :
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 12
9800 Logging
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 13
9800 RadioActive Tracing
• Add mac addresses, start debugging, generate log files when ready
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14
9800 RadioActive Tracing
• Logs on the box persist as long as there is space, but when clicking
Generate you decide for what time period you want to compile
them
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 15
9800 Logs : CLI
There are 2 unrelated activities one can do :
• Get the logs : #show logging profile wireless (filter mac <mac>)
start last <x> minutes/hours to-file bootflash:decodedlogs.txt
• Enable radioactive trace (debug level) : #debug platform condition
feature wireless mac <mac of client or ap> + #debug platform
condition start
• Or use the macro “debug wireless mac <mac>” which will run
debugs for 30 minutes and produce the output file automatically
after that or when you “no” the command.
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16
9800 Troubleshooting page
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17
9800 Troubleshooting page
“show tech-
support”
“show tech-
support wireless”
# show tech wireless # show tech wireless client #show tech wireless qos
# show tech memory. # show tech wireless multicast #show tech wireless datapath
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 18
9800 Troubleshooting tools
https://developer.cisco.com/docs/wireless-troubleshooting-tools/
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 19
9800 Sniffing
• Export to Wireshark
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 20
9800 Sniffing
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 21
9800 Sniffing
• Although EPC can be collected easily from Web UI and most of the time options provided there are
sufficient for certain troubleshooting tasks, CLI provides more granular settings for EPC configuration.
It can be configured to match inner identity (currently mac-address only) which allows to focus on
traffic related to specific client event when CAPWAP encapsulated.
• monitor capture client_inner_mac inner mac f0c1.f10b.8ac1 interface vlan39 both control-plane
both
• monitor capture client_inner_mac match any
• monitor capture client_inner_mac start
• monitor capture client_inner_mac stop
• monitor capture client_inner_mac export bootflash:inner-mac.pcap
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 22
9800 Sniffing
Collected captures can be either uploaded to some file server in the
network or downloaded from WLC web interface directly.
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 23
9800 AP Sniffing
• When using DNAC, Intelligent Capture takes a full wireless sniffer trace on
the client serving radio without disrupting operation. It also automatically
takes capture when a anomaly is detected. This is the best way to go
• The AP Packet capture in the troubleshooting page refers to an older radio
tracing feature of IOS APs. Not the way forward
• Putting an AP in sniffer mode is the simplest way to go if you only own a
9800
• CLI : APs can take wired sniffer traces as well as control-plane trace on the
radio. https://www.cisco.com/c/en/us/support/docs/wireless/aironet-2800-
series-access-points/214560-troubleshoot-wave-2-aps.html
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 24
9800 AP Sniffing
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 25
9800 AP Sniffing
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 26
9800 AP Sniffing
• ”decode as …”
PEEKREMOTE
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 27
Conclusion : troubleshooting recap
Step 1 : Health Monitoring
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 28
Conclusion : troubleshooting recap
Step 2 : Basic logging tracking
# show log
Dec 18 13:38:18.228: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap1, changed state to down
Dec 18 13:38:18.205: %CAPWAPAC_SMGR_TRACE_MESSAGE-3-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in Session-
IP: 192.168.16.134[5264] Mac: 7069.5a51.46e0 Heartbeat timer expiry for AP. Close CAPWAP DTLS session
Dec 18 13:38:18.231: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP
Name: 4802paolo, MAC: 4c77.6d9e.60e4 Disjoined
Dec 21 06:19:45.425: %HTTP-4-SERVER_CONN_RATE_EXCEED: Number of connections per minute has exceeded the
maximum limit(500)as specified by the platform.
..Dec 21 06:20:00.748: %HTTP-4-SERVER_CONN_RATE_EXCEED: Number of connections per minute has exceeded the
maximum limit(500)as specified by the platform.
.Dec 21 06:20:00.785: %HTTP-4-SERVER_CONN_RATE_EXCEED: Number of connections per minute has exceeded the
maximum limit(500)as specified by the platform.
.Dec 21 06:20:15.616: %HTTP-4-SERVER_CONN_RATE_EXCEED: Number of connections per minute has exceeded the
maximum limit(500)as specified by the platform.
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 29
Conclusion : troubleshooting recap
Step 3 : Pull always on data for a client/AP
• Or in Web UI Radioactive Trace page, add the mac and generate the logs immediately
without clicking start.
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 30
Conclusion : troubleshooting recap
Step 4 : More information needed? RA Traces
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 31
Conclusion : troubleshooting recap
Step 5 : TAC case
• RA-trace output (internal level, while we’re at it) or show logging profile wireless
of always-on output filtered for the problematic mac or timestamp
• Relevant show techs (at least show tech + show tech wireless)
• Core dump files from the web UI troubleshooting page (if the problem is a crash)
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 32
References
If you want more troubleshooting info
• BRKEWN-3013 Cisco Live Barcelona 2020
• March TAC workshop on SalesConnect
• https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-
wireless-controllers/213949-wireless-debugging-and-log-collection-on.html
• https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-
wireless-controllers/213970-catalyst-9800-wireless-controllers-commo.html
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 33