- Introduction to the Cisco ASA FirePOWER Module
- Managing Reusable Objects
- Managing Device Configuration
- Getting Started with Access Control Policies
- Blacklisting Using Security Intelligence IP Address Reputation
- Tuning Traffic Flow Using Access Control Rules
- Controlling Traffic with Network-Based Rules
- Controlling Traffic with Reputation-Based Rules
- Access Control Rules: Realms and Users
- Access Control Rules: Custom Security Group Tags
- Controlling Traffic Using Intrusion and File Policies
- Intelligent Application Bypass
- Access Control Using Content Restriction
- Understanding Traffic Decryption
- Getting Started with SSL Policies
- Getting Started with SSL Rules
- Tuning Traffic Decryption Using SSL Rules
- Understanding Network Analysis and Intrusion Policies
- Using Layers in a Network Analysis or Intrusion Policy
- Customizing Traffic Preprocessing
- Getting Started with Network Analysis Policies
- Using Application Layer Preprocessors
- Configuring SCADA Preprocessing
- Configuring Transport & Network Layer Preprocessing
- AC Adaptive Profiles
- Getting Started with Intrusion Policies
- Tuning Intrusion Policies Using Rules
- Detecting Specific Threats
- Globally Limiting Intrusion Event Logging
- Understanding and Writing Intrusion Rules
- Introduction to Identity Data
- Realms and Identity Policies
- User Identity Sources
- DNS Policies
- Blocking Malware and Prohibited Files
- Logging Connections in Network Traffic
- Viewing Events
- Configuring External Alerting
- Configuring External Alerting for Intrusion Rules
- Using the ASA FirePOWER Dashboard
- Using ASA FirePOWER Reporting
- Scheduling Tasks
- Managing System Policies
- Configuring ASA FirePOWER Module Settings
- Licensing the ASA FirePOWER Module
- Updating ASA FirePOWER Module Software
- Monitoring the System
- Using Backup and Restore
- Generating Troubleshooting Files
- Importing and Exporting Configurations
- Viewing the Status of Long-Running Tasks
- Security, Internet Access, and Communication Ports
ASA with FirePOWER Services Local Management Configuration Guide, Version 6.2.2
- Updated:
- September 5, 2017
Chapter: Generating Troubleshooting Files
Generating Troubleshooting Files
In some cases, if you have a problem with your appliance, Support may ask you to generate troubleshooting files to help them diagnose the problem. You can select any of the options listed in the following table to customize the troubleshooting data that the ASA FirePOWER module reports.
Note that some options overlap in terms of the data they report, but the troubleshooting files will not contain redundant copies, regardless of what options you select.
Generating Appliance Troubleshooting Files
Use the following procedure to generate customized troubleshooting files that you can send to Support.
To generate troubleshooting files:
Step 1 In ASDM, select Configuration > ASA FirePOWER Configuration > Tools > Troubleshooting .
Step 2 Click Generate Troubleshooting Files .
The Troubleshooting Options pop-up window appears.
Step 3 Select All Data to generate all possible troubleshooting data, or select individual check boxes to customize your report. For more information, see the Selectable Troubleshoot Options table.
The ASA FirePOWER module generates the troubleshooting files. You can monitor the file generation process in the task queue ( Monitoring > ASA FirePOWER Monitoring > Task Status ).
Step 5 Continue with the procedure in the next section, Downloading Troubleshooting Files.
Downloading Troubleshooting Files
Use the following procedure to download copies of your generated troubleshooting files.
To download troubleshooting files:
Step 1 In ASDM, select Monitoring > ASA FirePOWER Monitoring > Task Status .
Step 2 Find the task that corresponds to the troubleshooting files you generated.
Step 3 After the appliance generates the troubleshooting files and the task status changes to
Completed
, click
Click to retrieve generated files
.
Step 4 Follow your browser’s prompts to download the files.
The files are downloaded in a single
.tar.gz
file.
Step 5 Follow the directions from Support to send the troubleshooting files to Cisco.
Feedback