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)filefrom an APIC upon initial SR creation, as well as highlight the value of the other 2 techsupport tar files generated per Node.
Adv GUI: On-Demand Techsupport Policy
Creating an On-Demand Techsupport Policy
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.
In the menu bar, click Admin.
In the submenu bar, click Import/Export.
In the Navigation pane, expand Export Policies.
Right-click On-demand TechSupport and choose Create On-demand TechSupport. The Create On-demand TechSupport dialog box appears.
Enter the appropriate values in the fields of the Create On-demand TechSupport dialog box.
If a remote location is not available, check Export to Controller. Generated Techsupports will be available via the Operational Tab of the GUI once generated.
Check Include All Controllers in TechSupport to generate APIC Techsupports
The Source Nodes field allows you to specify switch nodes will generate a Techsupport
Click Submit to create the On-Demand Techsupport Policy.
Creating On-Demand Techsupport Policy Screenshots
GUI Techsupport Policy Creation: Steps 1-4
GUI Techsupport Policy Creation: Steps 5 and 6
Generating an On-Demand Techsupport
Navigate to an existing On-Demand Techsupport Policy. Created policies can be found at Admin > Import/Export > Export Policies > On-demand TechSupport
Expand the On-demand TechSupport Folder then right-click on the policy to be used and choose Collect Tech Supports.
Or, left-clickthe On-Demand Techsupport Policy to bring it up in the Main pane, then click on the Wrench/Hammer icon then select Collect Tech Supports
Choose Yes to begin collecting tech support information.
Generating On-Demand Techsupport Screenshots
GUI Techsupport Generation
Collecting the generated Techsupport
If Export to Controller was not enabled during Techsupport generation, the Export Destination (Remote Location) should be checked for all techsupport files.
If Export to Controller was enabled, navigate to the On-Demand Techsupport Policy that the techsupports were generated against. Created policies can be found at Admin > Import/Export > Export Policies > On-demand TechSupport
The generated techsupports can be found within the Operational Tab of that On-Demand Techsupport Policy. Each file will have a link to download it via http/https. Each node will have 3 links, one link tied to each file.
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.
Collecting On-Demand Techsupport Screenshots
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.
Techsupport Files Explained
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:
Upload upon initial case opening?
TAC requested or for RCA
TAC requested or for RCA
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.
Cisco SR Upload Tool
The main tool to upload these files to Cisco SRs is the following
Hi, I'm trying to understand under which scenarios it is recommended to enable GARP (and hence, ARP Floding). According to the ACI Fabric Endpoint Learning White Paper: Cisco ACI can detect MAC and IP address movement between leaf switch po...
HiI have a Problem in symmetric hashing on port channel in nexus 3172PQ.in my design i want to use two Nexus 3172PQ that ether channel together. between these switches, there is a layer 2 devices that capture traffic flow. But when enable port channel on ...
Hello, we have a DCNM 11.1(1) classic LAN installation. On our environment we have Nexus 5K with FEX N2K-C2248TP-E-1GE and Nexus 7K with FEX N2K-C2348TQ-10G-E. DCNM Monitor > LAN > Ethernet shows the interfaces for the N2K-C2248TP-E-...
Hello, we have 5672UP with N2K-C2232PP-10GE and a numbering of the FEX like this:Rack 56: FEX 156, now I need in a Rack a second FEX.Can I use the slot-command to enable slot 2, so I had Interfaces 156/1/x and 156/2/x ? there is not mu...