I have a customer requesting assistance with the CLI Analyzer 3.2.1 on Windows 7. They have two Catalyst 3850s, one of them is unable to connect with the tool while the other one has no issues. No other devices in their IB is exhibiting ...
I am working with a customer using Cisco's Common Services Platform Collector and we ran into this bug. Can you conform the workaround to disable/re-enable snmp-server commands are as follows please?
Disabling the SNMP Agent
Perform this tas...
I have a customer using a Cisco collector, and they have noticed their N9Ks' host names are being cut off after 32 characters. I found several bug IDs that are similar to this issue but all are for older versions of OS, they are running 7.0(3...
Please post your question to https://community.cisco.com/t5/network-security/bd-p/discussions-network-security as the Cisco CLI Analyzer Community is not related to your topic.
Hello @Matt A
The ASA Traceback Analyzer script on the backend is being updated to use Python 3, our other scripts using Python 2 will also fail with the 403 error. Please allow us some time to resolve this issue.
The data shared through the CLI Analyzer is determined by your device configuration rather than just a generic SW version or device PID. The system diagnostics should be the most current data regarding your device.
Tentatively the release for 3.6.8 will be available in the next week or two. If you wish to be notified when it's available please edit your notifications in the Software Downloads page. https://software.cisco.com/download/home/286...