11-13-2017 03:21 PM - edited 04-16-2019 11:01 AM
The purpose of this document is to guide a user through the steps of generating techsupports and outlining the different files generated by the techsupport. This is to highlight the value associated with TAC having a copy of a Database Dump (2of3) file from an APIC upon initial SR creation, as well as highlight the value of the other 2 techsupport tar files generated per Node.
NOTE: Do not specify a TechSupport Time Range unless explicitly asked to by TAC. Depending on log churn, doing so may cause the loss of logs which will severely impact the ability of TAC to provide a timely RCA.
GUI Techsupport Policy Creation: Steps 5 and 6
GUI Techsupport Generation
NOTE: If you are running a pre 2.2 version, you are required to use the local "admin" user account in order to download Techsupports via the UI. Otherwise you can use any other local account that has admin privileges. Remote users will not be able to download techsupports via the UI in this manner, and should instead utilize sftp or another method to pull the techsupport files from the "/data/techsupport/" directory on the corresponding APICs.
GUI Techsupport Collection
NOTE: The number in the URL of the techsupport bundle is an indicator of which APIC the file resides on.
Example: "files/2/techsupport.tgz" implies that this specific bundle can be found on APIC 2's "/data/techsupport/" directory.
If the Techsupports have been generated with the Export to Controller option, the GUI will show 3 URLs per ACI node (APIC node or Switch node). Each URL is a different log file type and contains unique information. This means that TAC will typically require all 3 files to be uploaded per node in order to get all logging for a complete analysis.
Each URL maps to one of the 3 filetypes:
Category | Typical Suffix | Useful for: | File Size | Upload upon initial case opening? |
Export | _1of3.tgz | Audit/Fault Logs | Small-Med | TAC requested or for RCA |
Logs | _logs_3of3.tgz |
Process Logs |
Largest | TAC requested or for RCA |
DB | _db_2of3.tgz | MO Dump | Small | **Always** |
NOTE: If an Export Destination was selected instead of Export to Controller, the defined Remote Location will have a folder that contains the above 3 files per node.
The main tool to upload these files to Cisco SRs is the following
https://cway.cisco.com/csc/index.html
If this method has problems, please work with your TAC engineer to agree on another method.
If you are interested in other methods to generate a techsupport, the following documentation outlines additional options:
Thanks for sharing this. I found it super useful.
This is Great Post. Its Really help full thanks a lot and great job.
Thanks for sharing this. I found it super useful. Great !!!!
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: