on
02-18-2021
11:47 AM
- edited on
02-18-2021
11:49 AM
by
Hilda Arteaga
This event had place on Thursday 14th, Janaury at 9:30 hrs PDT
-This Support Talk event is a special session of the “TAC Tools Explained Series”-
This event provides a practical introduction to Cisco’s TAC Wireless tools, their features, capabilities, and usage. Wireless logs and configuration files can be tedious and verbose to consume. Wireless Debug Analyzer, Wireless Config Analyzer Express (WCAE), and Wireless Config Converter are popular tools widely adopted by a range of customers and partners today for their configuration, migration, and troubleshooting needs.
For more information, visit the Cisco Support & Downloads page.
You can download the slides of the presentation in PDF format here and the video of the session here.
A: Please have a look here: https://developer.cisco.com/docs/wireless-troubleshooting-tools/
A: You need "sh tech wireless" for 9800 and "sh run-config" for AIreOS.
A: There is no data retention. Tool is certified by Cisco Infosec team, and there is no longer storage or collection of any data provided. Data is lost as soon as file is processed.
A: Currently, there is no 11v data present on sh tech wireless/sh run. In general, we avoid client individual values in those files, for scalability and privacy reason. We will check if we can incorporate summary data for analysis, thanks for your suggestion.
A: Yes, there are some plans to add graphs and graphical representations on these files. They’re not on the cloud version but on the mini version.
A: DNAC does not have the same config checks. it is a very different toolset. WCAE is oriented towards troubleshooting/problem finding, DNAC is an overall management system.
A: No, it is different. Nevertheless, we have worked together with the DNA people and there is more collaboration that's going to happen in future regarding their health scores. We are participating as well on the design of some of the initial DNA scenarios.
A: Please use the following https://cway.cisco.com/wireless-config-analyzer/
A: Yes, there is no problem. The tool has sufficient time, maximum 10 minutes, and we have tested the tool with files of 220 megabytes and the compress goes about 10 something megabytes. But you can go outside, the tool itself it doesn’t have a limit and will run as much family as possible and get them executed. Unless you have something extremely large it will take longer, so make sure you use files in ZIP it will make things easier.
A: Yes it does.
A: RF Index is an older version of the RF Health. it is a way to highlight APs that have metrics which are a lot worse than other APs around. There is no upper limit, and basically you would use to see if one or more APs have some very high value, when compared to their neighbors, as it would indicate something is wrong. In general, it is better to use the RF Health indicator, as it would highlight "why" something is wrong. RF index is kept for historical reasons.
A: It is a different approach. We have shared the feedback to DNAC team, and there will be some interesting surprises in future.
A: There is a 600 sec processing timeout in the back end script (AFAIK). This includes the upload/processing. So, the script should technically error out in 10 min post a processing error.
A: Please use the following: https://cway.cisco.com/wireless-config-analyzer/
A: Maybe it’s related to the setting is on "country channels", so the check is reporting to move to all. Anyway, if you see it is not matching, please write me email jacontre@cisco.com with the zip of the file, and I will be happy to test and correct if there is a defect on the detection code.
A: Yes, it is planned.
A: The idea for the initial phase is to split connection attempts into logical sequence (L1, L2, L3) . Interpreting state machine is part of the process. But we are planning to print simplified summary and not the verbose length of the logs.
A: So, what the conflict converter helps convert is the wireless portion of the configuration, per se if you have an arrow part of or fabric, we use the converter tool. Those mappings will get directly translated but in terms of the mapping list, please check the unmapped or unsupported section in case anything gets listed there. The primary goal is the wireless confing conversion, that is where most of the 9800 was. Nevertheless, you will personally need to validate the fabric piece alone.
A: Coverged access are older versions (3.x) running over 3700 or similar switches. It is not the same.
They are not supported on the tools. The tool supports eCA (4000 switches, running wireless over 16.x/17.x IOS-XE).
A: You can find more details here https://blogs.cisco.com/networking/after-15-years-cisco-wireless-aireos-controllers-are-going-away?oid=pstwls024839&_lrsc=5ee3af2f-896c-4881-a9ed-efd29c825176&dtid=osolin001080
A: So, the way we see each other is through the NDP, then the network discovery protocol sends frames in a regular basis which are detected by the other AP.
In the normal way, a piece is doing a channel scan every X number of milliseconds which depends on which band and how many channels you set to scan and the period you configure for the RMS scan timer. They’re going to move into an X channel that’s going to send the NDP frame there, which is going to be received by the APs that are resigning on that channel because we know of which channel the NDP was sent. And we know what the pass loss is, it gave us an understanding of how far is that AP from us and which channel is operating, and if it is an unknown AP in my RF domain or well my mobility network. So, that so the way they see each other.
A: Find the answer at the Ask Me Anything forum session of this event, here.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: