Introduction
When facing issues with Cisco ACI, collecting the correct technical support data is crucial for timely resolution. This guide details the procedures for obtaining necessary outputs, whether through the Cisco Intersight Portal, the APIC User Interface (UI), or the Command Line Interface (CLI). It covers common scenarios and specific requirements for different ACI components.
For more detailed information and foundational resources, refer to the Cisco community documents:
Key Collection Methods
- Cisco Intersight Portal: Recommended for automated and efficient collection, especially when ACI Fabric is registered.
- APIC UI: Allows for on-demand techsupport policy creation and generation.
- CLI: Useful for direct collection from individual ACI nodes (APIC or switches) when UI access is limited or for specific troubleshooting scenarios.
- CIMC Techsupport: For gathering hardware-level logs from the APIC's chassis.
Common Issues & Data to Collect
The following table outlines common issues and the corresponding data TAC typically requires:
- Upgrade Issues: Show techs from nodes experiencing the issue.
- Connectivity Issues: Show techs from source and destination nodes, plus basic TAC outputs.
- Clustering Issues: Show techs from all relevant nodes and controllers, plus basic TAC outputs.
- Routing Issues: Show techs from controllers and affected border leaf nodes, plus basic TAC outputs.
- Crashes: Show techs from affected nodes, core files, and basic TAC outputs.
Further Information
For detailed step-by-step instructions on each method, please refer to the respective sections within this document.
ACI: Collecting a local techsupport from an APIC or Switch - Cisco Community
Cisco Intersight
Cisco Network Insights Base Application for Cisco APIC User Guide, Release 2.0.x - Using Cisco Network Insights Base [Cisco Network Insights for Data Center] - Cisco
